Comment 12 for bug 1023826

Revision history for this message
In , Yves-Alexis Perez (corsac) wrote :

Created attachment 4554
gdb backtrace

A Debian user reproduced it (using the menu key) and managed to provide a gdb backtrace (attached). He said the following:

On sam., 2012-07-21 at 12:28 -0400, P. J. McDermott wrote:
> I just hit this bug a second time in version 0.4.8-1+b1.
>
> I accidentally pressed the context menu button (on a US keyboard) and no
> menu appeared. Now all of my terminal windows (and all 149 tabs!) have
> stopped accepting input (keyboard or mouse). They still draw output,
> however (my IRC client and a clock in GNU Screen's status line are still
> updating).
>
> Attached is a full backtrace from GDB, in which one can see that GTK+ is
> running the main loop that Terminal's terminal_widget_context_menu()
> created in the input thread. AFAICT there's no way to end the context
> menu main loop so that Terminal's input thread can return to normal
> execution, so my only recourse is to kill xfce4-terminal.