Description of problem:
Terminal redraws *very* slowly following upgrade of exo and Terminal.
Version-Release number of selected component (if applicable):
I did an update a couple of days ago and it made new Terminals run
*very* slowly (one can actually watch the individual redraws of
lines, background, etc.). I updated exo today and the problem
persists. I have no idea why the redraws are so slow. No other
applications have this problem -- everything else renders at the
Odd. I don't see that at all here.
Have you logged out and back on since the upgrade to 4.4.0?
Perhaps some old libraries are still in memory?
I'll try and see if I can find any way to duplicate here.
Perhaps you are hitting a vte bug?
There is a new vet in updates-testing for fc6, could you try upgrading that?
yum --enablerepo=updates-testing update vte
Let me know if that makes any difference.
Hi Kevin, I tried the above vte update and unfortunately it made no
difference -- the rendering is still painfully slow.
I wonder if it could be this, or related to this bug:
Is Composite enabled or disabled for you?
xdpyinfo | grep -i composite
should tell you if it's enabled...
Hey Ed. Is this problem still happening for you? Any word on Composite?
Hi Kevin, I'm not seeing this problem on my FC6 x86_64 laptop and I will try
it again on my FC6 i386 laptop tonight to see if it persists there.
ok. Any news on the i386 testing?
I yum update-ed the FC6-i386 laptop and the terribly slow rendering of
Terminal persists. I have no idea why its happening. Gnome-terminal
works nicely on the same machine. And Terminal works nicely on my x86_64
So, it's running 4.4.1 now? With the same issue?
I can't recall if we tried this yet, but:
can you create a brand new user, logout and login as that user and see if the
problem persists for that user?
For what it is worth, I had this same issue in FC6, and upgrading to F7 fixed
I sure wish I could figure this one out. ;(
I was unable to duplicate it on any of my FC6 boxes. ;(
Anyone have any further ideas and/or a machine where it's currently happening?
Anyone left who can duplicate this?
If not, perhaps it should just get closed?
If so, speak up and I can try and track it down some more.
ok, closing this. Feel free to reopen or file a new bug if someone is able to
Thank you for looking into this bug -- I'm unable to reproduce it on any of
my machines since they were upgraded to F7.