Screen shifted to the right with nvidia drivers and compiz

Got the same problem, some more strange behaviour that might help to identify the problem:

The glitch only occurs when I enable Compiz through System, Preferences, Appearance. Not when I enable Compiz via the Compiz Fusion Icon. Enabling or disabling with either method doesn't get rid of the glitch once it's there.

Thank you for your bug report. This is probably more likely to be a video driver issue. Could you also post the output of "xrandr" and attach your /etc/X11/xorg.conf if you have one. It would also be great if you could take a photo of the screen (although I sort-of understand the problem you're describing)

Not sure if this has anything to do with it but this is what I get when I try to use get-edid. I can't use parse-edid because it won't read the output of get-edid. I can also send other logs if you like.

Happens when I run certain screensavers also. Doesn't happen on glMatrix but happens when I try to run Star Wars, haven't tested any others.

here we are, this is my xorg.conf

Note: I tried also with a plain default xorg.conf changing only the video driver to "nvidia" and the result is the same

this is the output of xrandr after recentering the screen via nvidia-settings:

before the bug report (then I fount the nvidia-settings method), I used to recenter the screen like this:
1) bring down resolution to 1024x768 (causing gnome-settings-daemon to crash....this still happens)
2) bring up resolution to 1280x800 (without any effect)
3) manually restart gnome-settings-daemon from terminal (which applies the previous setting)

and with this method xrandr complies about Xlib missing on display 0 or something similar, but now I'm not able to reproduce this error, I'll try on next reboot without touching nvidia-settings.

following screen captures attached (sorry for the bad quality, I have only a camera phone):

(note that there is also the upper pixel-row screwed up, it's not wrapped from the bottom, it's more like the first row is displaced 'cause I can see the tip of the mouse cursor moving when this is at the top-most)

if you need more info or logs just ask!!

that error about Xlib missing on Display 0 doesn't happen anymore, maybe it was a bad xorg configuration solved later with a manual editing

another thing I noted: after clicking on shutdown, the screen shifts again to the right, but only for half a second because the usplash screen is ok

just found the nvidia-bug-report.sh script, I'm attaching the output log

here's another thread on this bug: http://www.nvnews.net/vbulletin/showthread.php?t=123852
reading the logs posted in this thread and comparing them to my own log, I can see that:
1) we all have a GeForce Go (PCI-E) graphic adapter
2) we all have different versions of the driver (all 180.* series)
3) we all are on Ubuntu (8.04 or 8.10)
4) different versions of X.Org X Server (1.4.0.90 - 1.5.2)

anyway, I'm sending this bug report to nvidia too

other thoughts:
1) after startup (with the screen shifted), if I put the system on sleep and then wake it up the screen is ok

2) like someone else noted, I also verified that if I run glxgears from terminal and than terminate it with CTRL+C the screen shifts to the right (only once, so doing it more times doesn't change anything, the shift about 20pixels absolute, and not relative to the previous position). anyway terminating glxgears simply closing its window does not shift the screen, but gives this output on the terminal:
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
         after 42 requests (42 known processed) with 0 events remaining.

3) after startup (screen shifted) I can adjust it switching to another tty console and back (CTRL+ALT+F1 -> CTRL+ALT+F7)

any news?
need other informations?

I have exactly the same issue. Also have a GeForce Go, 180.22 driver, Ubuntu 8.10 and X.Org X Server 1.5.2. Any else I can help with?

I have the same issue(GeForce 7300). Here are my sceenshots :)

I have this problem with and without compiz!

I have just upgraded from nvidia drivers v.177 to v.180 and ran into this bug, so it is definitely nvidia's fault. I do use compiz though.
The easiest way to fix this is to run nvidia-settings. Somehow the screen gets aligned right.

Confirmed here on x86_64 with nvidia 180.29 and GeForce Go 7600.

I run dual-screen with separate X sessions. The primary (screen 0) exhibits the horizontal pixel-offset/wraparound and sometimes corrupted top 1 or 2 rows too (1280x800x24).

Adjusting the GPU Scaling momentarily seems to solve the offset, which suggests the driver is incorrectly initialising the device.

The secondary screen (1280x1024x24) positioning is fine *but* when the mouse is moved from it to the primary screen, an image of the mouse cursor remains on the edge of the screen whilst the cursor continues moving on the primary screen.

Are all of you experiencing this running the backported nvidia 180.xx graphics driver on Intrepid? Are any of you running a different driver, or running Jaunty? Could someone test with the 180.xx driver on Jaunty?

I'm on Intrepid (nVidia GeForce Go 7300)

$ apt-cache policy nvidia-glx-180
nvidia-glx-180:
  Installato: 180.11-0ubuntu1~intrepid1
  Candidato: 180.11-0ubuntu1~intrepid1
  Tabella versione:
 *** 180.11-0ubuntu1~intrepid1 0
        500 http://it.archive.ubuntu.com intrepid-updates/restricted Packages
        100 /var/lib/dpkg/status

I'm on Jaunty (nVidia GeForce Go 7300) and compiz running

nvidia-glx-180:
  Installato: 180.29-0ubuntu2
  Candidato: 180.29-0ubuntu2
  Tabella versione:
 *** 180.29-0ubuntu2 0
        500 http://it.archive.ubuntu.com jaunty/restricted Packages
        100 /var/lib/dpkg/status

A simplication of the work-around for the right-shift pixels and top-lines corruption. Just the act of starting nvidia-settings instantly corrects it here - I don't have to touch the GPU Scaling settings. However, the issue with the mouse cursor remains. From the upstream reports it looks like this is well-known at nvidia so I should expect it'll be fixed in newer releases.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu jaunty (development branch)
Release: 9.04
Codename: jaunty

uname -a
Linux hephaestion 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:42:34 UTC 2009 x86_64 GNU/Linux

apt-cache policy nvidia-glx-180
nvidia-glx-180:
  Installed: 180.29-0ubuntu2
  Candidate: 180.29-0ubuntu2
  Version table:
 *** 180.29-0ubuntu2 0
        500 http://gb.archive.ubuntu.com jaunty/restricted Packages
        100 /var/lib/dpkg/status

Doing a bit more digging on the nvidia forums I found a related posting about what is possibly a closely related issue with the 180.29 driver - complete screen-corruption and system lock-up requiring a forced hard reset.

It prompted to run an Open GL test with glxgears. Starting from a 'correct' screen, as soon as glxgears starts the screen image jumps to the right about 50 pixels and wraps around to the left edge.

Starting nvidia-settings doesn't fix it, but navigating to the GPU 0 > DFP - 0 page and changing the state of any of the GPU scaling options fixes it.

This is consistently reproduce-able.

Version 180.37 solves the problem for me (Compiz enabled)
Tested on Intrepid with a GeForce Go 6200

( Asus A6VC Laptop at 1280x800 resolution )

bug still here on a fresh install of Jaunty

Ubuntu 9.04 Jaunty (development branch)
Linux 2.6.28-9-generic #31-Ubuntu SMP Wed Mar 11 15:43:58 UTC 2009 i686 GNU/Linux
nvidia-glx-180: 180.35-0ubuntu1

seems solved in nvidia-glx-180 version 180.37-0ubuntu1 on Ubuntu Jaunty

Bug is fixed for me also with 180.37

fix released in version 180.37

I have this problem on my Intrepid with 177 and 180.11 drivers. And also with 180.37. I attached a picture that shows how it bugs. It gets back to normal when I run "nvidia-settings -a GPUScaling=1,3" as Daniele said.

I found out that it does only occur with DVI cables and not with analog ones.

I have Intrepid, nvidia-glx 180.37, linux 2.6.27-14 and Geforce 7950 GT.

Here is the old bug for 177: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nv/+bug/286730/

I updated to Jaunty and now I have 180.44. I still have the problem. It is very similar to this, but if this is already fixed then it must be caused by a differend reason. But really it is very similar to this. The description fits and Daniele's workaround makes it work temporarily.

I'm sorry, since nvidia 180.37 I never had this problem anymore