Rotation of second monitor produces screen artifact Ubuntu 8.10

[chadeldridge]

I have a dual monitor setup using 2x Dell 24" monitors. Monitor 0 (left monitor) is in standard horizontal position, and Monitor 1 is in a vertical 90 deg position. In 8.04 i was able to use the Option "Rotate" "CCW" in the xorg.conf file to rotate monitor 1 to this position with no issue, however with the new nvidia drivers and xorg something is no longer the same. Monitor 1 will rotate with no issue using either the Rotate option or through xrandr, but it will only draw down the screen as far as monitor 0 as. For example it stops when it hits the 1280 boundary specified by monitor 0. Since it it rotated at 90 its resolution is actually 1280x1920.

Also I should mention that although i cannot drag icons or resize windows past the black line I can move my mouse beyond it and still see the cursor.

Attached is the info from my system:

[lspci]
00:00.0 Host bridge: Intel Corporation 82975X Memory Controller Hub
     Subsystem: Dell Device 01de
01:00.0 VGA compatible controller: nVidia Corporation NV43GL [Quadro FX 540] (rev a2)
     Subsystem: nVidia Corporation Device 02d1

[chadeldridge (chadeldridge)]

Another update .. this works fine with Compiz turned off. So compiz is the issue.

[chadeldridge (chadeldridge)]

Sorry for so many bumps here just trying to give as much info as possible to whoever looks at the bug. Here is a picture to better understand what I am describing.

[Jarmo Ilonen (trewas)]

I can confirm this (apparently) compiz bug. In my case the first monitor is 1280x1024 and the second one 1360x768. On the second monitor the rightmost 80 pixels are black. Works fine without compiz.

Common points to the reporter are nvidia's proprietary driver and monitors set up without xinerama/twinview, so the screens are separate (not possible to move windows from one to other).

I'd guess compiz makes some screen size assumptions based on the first screen and when the second one is larger, a part of it appears as black.

[chadeldridge (chadeldridge)]

After discussing with the nvidia team this does seem to be a bug in the 177.80 driver. Reverting to the 173.14 driver does fix the issue for me.

[chadeldridge (chadeldridge)]

How long can I expect it to be before this is at least classified as a bug? Is there something I can do to help the process?

[chadeldridge (chadeldridge)]

This also effects the 180 drivers both ubuntu and nvidia direct drivers... seems as though no one is going to bother looking at it ever though.

[Bryce Harrington (bryce)]

[This is an automated message]

In Jaunty (9.04), we are dropping the nvidia-graphics-drivers-177 package, which
is now superseded by then nvidia-graphics-drivers-180 package.

  http://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180

To transition your bug into the new package, we need your help. Please do the following:

 a. Verify the bug occurs in Jaunty with the -180 driver
     (ISOs: http://cdimage.ubuntu.com/releases/jaunty/)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * Your /etc/X11/xorg.conf
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Under Affects, click the down arrow to the left of 'nvidia-graphics-drivers-177'
 d. Edit the Package to change 'nvidia-graphics-drivers-177' to 'nvidia-graphics-drivers-180'
 e. Click Save Changes

Thank you!

[We'll expire the remaining -177 bugs in a month or so.]

[chadeldridge (chadeldridge)]

Is there any way to confirm this bug without installing Jaunty. The issue is on a production system and I in no way have any intention of destroying a working system for alpha software. Is it possible to test via the LiveCD?

[Bryce Harrington (bryce)]

[This is an automated message]

In Jaunty (9.04) we have dropped the nvidia-graphics-driver-177 package, as
it is superseded by nvidia-graphics-drivers-180.

Because of this, we are closing this bug as expired.

You are encouraged to file your -nvidia bug reports against the
nvidia-graphics-drivers-180 package.

[Bryce Harrington (bryce)]

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

[Jarmo Ilonen (trewas)]

Just upgraded to jaunty and the bug is still there with the newest nvidia driver (180.44-0ubuntu1).

[chadeldridge (chadeldridge)]

i can confirm as well .. this is a bug with every Nvidia driver so far past 173.

[Stefan Engstrom (stefan23)]

@chadeldridge - same symptoms as you describe happened to me after I upgraded to 9.04 - after spending an hour playing with down grading the nvidia driver and alternate monitor configurations I simply went back to xinerama and adjusted the display offset in the monitor's own adjustment menu (I have a VP171b ViewSonic). The nvidia driver maps everything correctly after this... A silly solution I know and why it happened in the first place is anybody's guess but now I have my beloved 2nd portrait monitor back...

Good luck,

-S

[Bryce Harrington (bryce)]

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.