[Pkg-xfce-devel] Bug#624684: Bug#624684: xfce4-terminal: stops to accept keyboard input
corsac at debian.org
Sun May 1 12:58:12 UTC 2011
On dim., 2011-05-01 at 14:15 +0200, Jochen Schulz wrote:
> Yves-Alexis Perez:
> > On sam., 2011-04-30 at 17:42 +0200, Jochen Schulz wrote:
> >> The only thing I found is the following line in ~/.xsession-errors:
> >> (xfce4-terminal:13006): Gtk-CRITICAL **: IA__gtk_widget_event:
> >> assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
> > Can't it be a problem in the shell? Do *all* terminal window/tabs stop
> > responding? Did you do something special in the shell at that time?
> Both terminals I usually use (one running a local screen session,
> another one with a remote screen session via SSH) were affected at the
> same time, so I don't think it's a shell issue. I cannot tell what
> exactly I did at the time. I only know I was typing something at both
I meant typing something in a shell might have triggered it, but yeah,
that looks unlikely.
> I am unsure whether the context menu still worked. My terminals don't
> have menubars or toolbars and I don't use tabs, so the context menu is
> my only interaction mechanism with the terminal itself (plus a few
> keyboard shortcuts I don't care to remember). I'll try this when the
> problem reappears.
> > Could you try to get a backtrace of the terminal process when this
> > happens, if you manage to reproduce it?
> How would I do this? Is attaching strace enough?
It might be helpful, but I was more thinking at attaching a gdb to the
process and get a backtrace from there, using Ctrl-C + backtrace.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 836 bytes
Desc: This is a digitally signed message part
More information about the Pkg-xfce-devel