xfce4-terminal slow after jaunty upgrade

Bug #367455 reported by Andy Walker on 2009-04-26
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xfwm4 (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: xfwm4

I'm running Xubuntu Jaunty after an upgrade, and I'm having some major problems with the default terminal app (xfce4-terminal). Namely that it's running slow and eating up cpu usage.

To test this, I opened an xterm window and put top in it. Then, I opened another xterm and an xfce4-terminal window. If I enter into the xterm and hold down enter, Xorg spikes to maybe 7% or 8% CPU usage. If I enter into the xfce4-terminal window and hold down enter, Xorg spikes to between 40% and 50% CPU usage and stays there until I release the enter key.

It is also slow to refresh and resize, unlike xterm. If I run top in xfce4-terminal and return to the window, it can take up to a full second to redraw.

Obviously, there is some sort of problem here.

WORKAROUND:
Adding the following to your xorg.conf should do the trick:

Section "Extensions"
         # Workaround for slow xfce-terminal redraw times
         Option "Composite" "Disable"
EndSection

Rob Gallagher (rob-gallagher) wrote :

You need to disable compositing due to this bug:

http://bugzilla.xfce.org/show_bug.cgi?id=2792

Adding the following to your xorg.conf should do the trick:

Section "Extensions"
         # Workaround for slow xfce-terminal redraw times
         Option "Composite" "Disable"
EndSection

Rolf Leggewie (r0lf) wrote :

confirming a per Rob's comment

Changed in xfwm4 (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Rolf Leggewie (r0lf) wrote :

actually, I'm seeing this myself.

Stephen Day (sd) wrote :

This bug is also present on Maverick.
This bug likely affects a very large number of people who have not realized it.

description: updated

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version.

Changed in xfwm4 (Ubuntu):
status: Confirmed → Incomplete

Expired.

Changed in xfwm4 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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