My desktop gets "corrupted" all the time, and it happens randomly. A few applications triggers it more frequently though. Konqueror usually triggers it within seconds, so does the KDE control panel. Firefox and Evolution also seems to trigger it quite easily. I use the nv driver from Xorg on AMD64, so I guess this is were the problem is. Sometimes I can use my desktop for a day without this issue, sometimes it happens every 2 minutes, forcing me to do a CTRL-ALT-F1 - CTRL-ALT-F9. I can still use the mouse, move windows, click on things and get the expected behavior etc, but all colors on lists, backgrounds, scroll bars, buttons etc are totally messed up. I've tested several windows managers, and this happens with every one of them. Here are a few screenshots of the mess: KDE#1 http://www.automatvapen.se/screenshots/gah1.png KDE#2 http://www.automatvapen.se/screenshots/gah2.png KDE#3 http://www.automatvapen.se/screenshots/gah3.png Everything works great in Windows XP, I can play heavy games for hours, without any sign of instability or corruption. It's just rock solid. I can reproduce this on at least two machines. I'm running X.org 6.8.99.16 plus a merge of cvs diff -D20050715 -Dnow of the nv driver. Hardware specs: AMD64 3200+ Abit AX8 (VIA KT890-chipset) Nvidia Geforce 6600GT (PCI-Express)
I can see the same exact behavior with the same hardware.
Oops... didn't realize that "accept bug" doesn't change the assignee...
Created attachment 3753 [details] nv driver gives messy screen in ubuntu amd64 system too with xorg 6.8.2 I'm experiencing (the same) problems with this nv driver in xorg 6.8.2 on two different OS'es with the following hardware: AMD64 3000+ EPOX motherboard MSI Geforce 6200 GPU with nvidia chipset On Ubuntu Breezy Badger I get the same issues as described above. My screen is showing the same kind of messy colours (see attachmenet I added) On FreeBSD 6 (my preferred platform), I get the worse behaviour. There, the screen just FREEZES and I can't do anything else!! I have to log onto the machine through another computer in the network with ssh, and when I issue a top command, I see that the xorg process is eating all the cpu. All other processes are 0% and the xorg process is 99%. I then have to kill this process in order to work with the machine again. So here, on FreebSD, I can't do anything. The triggers seem to be every app I select. If I just login to X and then do nothing, nothing happens, but if I want to start to work, DISASTER strikes!! For me it's a severe problem because I can't work with my computer like this. However, on Suse 9.3, which I was running a few months ago on the same system, I had the same problems but there they were SOLVED after I had the chance to download the NVIDIA drivers through Yast2. Then I tried to install the NVIDIA driver through the ports system of FreeBSD, but the port didn't compile because it was for i386 and I have this amd64 platform. I hope this will give enough background and I'm looking forward to a solution. Brgds Robert Gilaard
I can confirm this also opens with 6.8.2 on single processor OpenBSD 3.8 -current amd64 with an Nvidia Geforce 6600 PCI-X. [On multiprocessor the mouse and keyboard lock under X in a matter of seconds, which I imagine is a race condition in the nv driver, but this means that one can't have the system running long enough to see if the screen gets corrupted or not.] There is no discernable usage pattern that causes the behaviour; it tends to happen in less than an hour of light use in general.
Robert, Laurence, Please try a newer release candidate of X.org. This problem is known to exist in 6.8.2 but is believed to be fixed in newer releases.
I'm running xserver 6.9rc2 for some days now and it seems to be gone. I guess you can close this ticket. I'll add a new comment if future proves me wrong. Thanks Aaron for your time.
That's good to hear. Joel, does 6.9rc2 (or rc3) fix the problem for you as well?
(In reply to comment #7) > That's good to hear. Joel, does 6.9rc2 (or rc3) fix the problem for you as well? Very late answer, sorry: Yes, 6.9 seems to fix everything, thanks.
Fantastic! Marking closed.
*** Bug 3768 has been marked as a duplicate of this bug. ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.