xfce4-terminal

xfce4-terminal freezes on mouse input

Bug #1023826 reported by Eric Druid
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xfce4-terminal
Incomplete
Medium
xfce4-terminal (Debian)
Confirmed
Unknown
xfce4-terminal (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I have experienced this bug a few times but it's hard to reproduce.

What I do is I have an xfce4-terminal window open with a long scrollback, I then scroll rapidly (I have a mouse where the mouse wheel can set my scrollwheel spinning) then I (acidentaly) right clicked
This resulted in all my xfce4-windoows freezing, or rather not accepting any mouse or keyboard input, programs kept running and windows respond well to resize events etc, however they will not respond to any keyboard or mouse actions (including window close action)

My guess would be that the menu responds badly to a Scroll wheel button relese event or simular and freezes the UI thread (this guess is totaly without knowing the program =) )

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xfce4-terminal 0.4.8-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Thu Jul 12 11:41:47 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214.2)
SourcePackage: xfce4-terminal
UpgradeStatus: Upgraded to precise on 2012-06-08 (33 days ago)

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

Hey,

as noted on irc, I had a report from a coworker, confirmed by a debian bug report (at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624684). It's not completely clear but it seems that, somehow randomly, Terminal will stop accepting input (in any opened window/tab).

strace and gdb seems to show an endless loop in poll() but I'm not too sure where it's stuck.

I was never able to reproduce it but the reporter in Debian experiences it regularly (though he's not able to reproduce it at will).

You should be able to reach him by mail (on the downstream bug report) if needed, traces are there too.

Regards,

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

Ok, it seems that the Debian reported manage to fully reproduce it when pressing the “menu“ key on his german keyboard.

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624684#45 for the complete info.

Revision history for this message
In , Jrschulz+xfce (jrschulz+xfce) wrote :

Hi,

I am the reporter of the bug in the Debian BTS. Is there any other information I should provide?

Regards,
Jochen.

Revision history for this message
In , 8-nick (8-nick) wrote :

Looks like something in vte or the xserver. Does this also happen with the vte application? Or gnome-terminal?

Revision history for this message
In , Jrschulz+xfce (jrschulz+xfce) wrote :

(In reply to comment #3)
> Looks like something in vte or the xserver. Does this also happen with the vte
> application? Or gnome-terminal?

NACK. I tried lxterminal and gnome-terminal. Both continue to work fine after pressing the menu key.

J.

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

I just reproduced it, I don't think I ever touched the menu key. In case it helps, I can wait a bit more before killing the process, in case you want me to do some experiments (I can be reached on irc too).

Revision history for this message
Eric Druid (eric-druid+ubuntu) wrote :
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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xfce4-terminal (Ubuntu):
status: New → Confirmed
Revision history for this message
Ralf-Peter (ralfpeter-rohbeck) wrote :

This just happened to me with xfce4-terminal 0.4.8-1+b1 on Debian.
Not quite sure what I did, but I think I clicked both mouse buttons and tried to mark some text.

Revision history for this message
In , Jrschulz+xfce (jrschulz+xfce) wrote :

Hi,

I am the reporter of the bug in the Debian BTS and noticed that the bug disappeared in version 0.6.2-1 of the Debian package. The menu key does not open the context menu anymore, but this may be intended and I do not miss that functionality. Right-click still works to open the context menu.

As far as I am concerned, this bug may be closed.

Thanks,
Jochen.

Revision history for this message
David McKen (david-mcken) wrote :

I just had this happen, it also happened twice yesterday.

Right now I'm going to say it has something to do with creation of a new window (maybe tab as well). Whether its mouse or key combination both seem to be affected. Issue doesn't happen every time I create a new terminal window / tab.

First solution was to logout and back in but I've since found that finding and terminating the xfce4-terminal process (there are 2 on my machine, this time I killed the one with an icon in system monitor and it also shows memory usage the second process shows the memory usage as N/A). This obviously killed my terminals but when I opened it back up the terminals work fine.

Revision history for this message
Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount) wrote :

Similar report on the Debian bug tracker:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624684

Is this bug still reproducible in the new stable release of Ubuntu (14.04)?

Bug Watch Updater (bug-watch-updater)
Changed in xfce4-terminal:
importance: Unknown → Medium
status: Unknown → Incomplete
Bug Watch Updater (bug-watch-updater)
Changed in xfce4-terminal (Debian):
status: Unknown → Confirmed
Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)
Changed in xfce4-terminal (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Unit 193 (unit193) wrote :

According to https://bugzilla.xfce.org/show_bug.cgi?id=7587, this issue has been fixed. Closing.

Changed in xfce4-terminal (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.