Switching workspace: redraw is slow

Bug #27919 reported by ChristofferS
10
Affects Status Importance Assigned to Milestone
xserver-xorg-video-nv (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Using dapper, nv driver.

Using default number of 4 workspaces.

1. Have epiphany open on workspace 1 (maximized).
2. Switch to workspace 2.

Result:

It takes about two seconds to redraw the desktop.

I have three png's on my desktop, a mounted harddisk icon and a FTP gnomevfs icon.

Revision history for this message
Chris Wagner (chris-wagner) wrote :

I have the same problem; I'm using the "nv" driver on dapper, on my desktop machine. I'm using dapper on two other laptops (which are not using nv driver) and there is no such problem.

It's not just switching desktops that is slow. (Re)drawing anything is really slow.

Revision history for this message
Chris Wagner (chris-wagner) wrote :

This is likely the same problem described here:
https://launchpad.net/distros/ubuntu/+source/libcairo/+bug/29497

Revision history for this message
Chris Wagner (chris-wagner) wrote :

I'm not sure we should have closed this bug so quickly. I am going to install the proprietary nvidia driver on my problematic machine. If the problem persists, then we may conclude that the problem described here is *not* due to the "nv" driver. If the problem goes away, then we need to re-open this bug, and close 29497, because the problem is most likely related to "nv" (furthermore the original reporter of 29497 has claimed that his problem went away).

Revision history for this message
Chris Wagner (chris-wagner) wrote :

This bug is not a duplicate of bug #29497 and it does in fact seem to be a problem that is specific to the xorg "nv" driver. On my system, after installing the proprietary "nvidia" driver, the problem went away.

Reading over bug #29497, I'm now realizing that it does not actually sound like the same problem.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Christoffer do you still have that issue?

Revision history for this message
ChristofferS (ubuntu-curo) wrote :

No, this issue has been fixed for me.

Chris Wagner, your issue is maybe something else.

Should I post my xorg.conf?

Revision history for this message
Chris Wagner (chris-wagner) wrote :

Christoffer, do you know if you were using the "nv" driver when you had this issue? Are you using it now? If you are not and never were using the "nv" driver, then perhaps these are separate issues (because mine seems very likely to be related to "nv").

I suppose you should post your xorg.conf. You wouldn't happen to have the xorg.conf which you were using at the time of the problem, do you? Perhaps, we could compare them to see if the configuration actually solved the problem.

Revision history for this message
ChristofferS (ubuntu-curo) wrote : xorg.conf

xorg.conf after playing with XGL. I don't have the original one.

Revision history for this message
Chris Wagner (chris-wagner) wrote :

Using the above posted xorg.conf, the problem *does* exist. Again, this xorg.conf is using the "nv" driver, so it still seems quite likely that the problem is related to that driver.

Christoffer, perhaps you upgraded some components manually, when playing with XGL (thus, accidentally fixing your problem)? Is it possible you're using a version of the "nv" driver other than that currently in the dapper repositories?

Revision history for this message
Daniel Holbach (dholbach) wrote :

'nv' works nicely with stock xorg.conf for me

Revision history for this message
Chris Wagner (chris-wagner) wrote :

Yes, it seems that not many people are having this problem. I've looked around a fair bit, checking for other bug reports that sound similar, but haven't seen any. This issue is really annoying so I'm sure people would be complaining. It makes me think the problem could be elsewhere (not in "nv").

I will try experimenting some more. I have another dapper install on that computer (long story), but I didn't think to check that that install works ok. I'll check. If that reveals nothing, I may try moving the card to another computer and performing a fresh install.

Revision history for this message
Chris Wagner (chris-wagner) wrote :

On a separate dapper install (using the same /home directory, though), on the same machine, the problem still exists. So, it seems unlikely that this is a configuration problem.

If I get the chance I will attempt to move the hard drive and video card over to another computer, to see if that makes a difference. If not, I may try a fresh install on a separate computer using the same video card. Problem is, I'm not sure if I have access to another computer, at this time, that will take that video card.

Any other suggestions?

Revision history for this message
Chris Wagner (chris-wagner) wrote :

Ok, this is pretty interesting...

I tried out the Xubuntu Live CD, out of curiousity, and noticed that the "slow drawing" problem did not exist. I checked the xorg.conf that was being used; it was using "nv".

So, I thought maybe the issue had been resolved. I downloaded a daily build of the regular Ubuntu Live CD. The problem still existed for plain-old Ubuntu.

Then, I switched back to the "nv" driver on my regular installation (I was using the proprietary "nvidia" because the problem did not exist with that). The problem still existed. So, I installed xubuntu/xfce packages on this installation, rebooted, and logged into an Xfce session => no slowness. Log out, log into GNOME => slowness.

I certainly thought this problem was probably at the X level, but now I have no idea. Perhaps it has to do with the window manager used by GNOME vs. Xfce?

Revision history for this message
Chris Wagner (chris-wagner) wrote :

My latest findings leave me very unsure as to which package is causing this bug. It seems to be related to xserver-xorg-driver-nv, but may very well be a problem somewhere else...

Revision history for this message
ChristofferS (ubuntu-curo) wrote :

I would suggest to file a new bug because the original bug is fixed.

I don't have any problems now.

Revision history for this message
Martin Bergner (martin-bergner) wrote :

Chris, is this still a problem for you?

Revision history for this message
Chris Wagner (chris-wagner) wrote :

I'll have to test this out when I get home from work. I suspect it is still a problem - at least under dapper. I will also try upgrading to edgy, to see if that helps.

Revision history for this message
Chris Wagner (chris-wagner) wrote :

This problem still exists under dapper with all updates available to present. Now I'll try edgy.

Revision history for this message
Chris Wagner (chris-wagner) wrote :

After upgrading to edgy, the problem seems to have gone away. I guess we can close this one. Do we want to set the status as "Fix Released" or "Rejected"?

Revision history for this message
Daniel Holbach (dholbach) wrote :

Closing the bug. Thanks for following up.

Changed in xserver-xorg-video-nv:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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