Dual monitor Greeter crash

[Zerhash]

I have two computers running here with similar setups. One is an amd64 the other a centrino.

The other night i updated gutsy and both systems which were working on a dual monitor setup failed to work. Both responded with the greeter crashing. Both are using GeForce 6 series binaries and are dual headed.

I used the initial downloaded driver and it was being ignored so i stuck with the restricted driver process with displayconfig-gtk. I set both screens so that the extra monitor is on the right. It says i need to log out and when i log in again the screen flickers trying to start the display and then spits out on both screens that the greeter crashed.

Moving the mouse around on this setting will push the display off the monitor area as the screen resolution is incorrect. The right screen is at a lower resolution than the right however both are scrolling with the mouse.

Alt-Ctl F(n) doesn't take you to the prompt but to what looks like a failed X black screen.

Restarting in failsafe and returning the /etc/X11/xorg.conf.backup to the xorg.conf file will return the settings to single monitor mode.

[Zerhash (zerhash)]

This is the laptops xorg

it is a toshiba M40

laptop monitor plus a vga head connected to a samsung syncmaster 913v

NVidia 6600 GO

[Zerhash (zerhash)]

As for the desktop

it is running a nvidia 6150 dual head
1 x DVI
1 x VGA

displayconfig-gtk is unable to detect an alternate monitor. And i attempted to install the driver itself and then modify the nvidia-settings. When i restart the display it crashes with the same error.

I am speculating that nvidia doesn't write to the RandR format specification correctly.

[unf (unforcer)]

I confirm this.

[Zerhash (zerhash)]

disabling xinerama works however the theme manager doesnt load on screen 2 so there are no title bars

[Steven McCoy (dsbunny)]

With 7600GT and 2xApple 23" I see the same with the nv driver. With the restricted driver the configuration works perfectly when using nvidia-settings, saving the xorg.org without merging.

> I am speculating that nvidia doesn't write to the RandR format specification correctly.

This appears correct, output from nv driver (1:2.1.5-1ubuntu1):

Screen 0: minimum 640 x 480, current 1920 x 1200, maximum 1920 x 1200
default connected 1920x1200+0+0 0mm x 0mm
   1920x1200 60.0*
   1680x1050 60.0
   1600x1024 60.0
   1440x900 60.0
   1280x800 60.0
   1280x720 60.0
   1280x768 60.0
   800x600 60.0
   1600x1200 60.0
   1400x1050 60.0
   1280x1024 60.0
   1280x960 60.0
   1024x768 60.0
   640x480 60.0

Output from nvidia drivers (100.14.19+2.6.22.4-14.9):

Screen 0: minimum 800 x 600, current 1920 x 1200, maximum 1920 x 1200
default connected 1920x1200+0+0 0mm x 0mm
   1920x1200 50.0* 51.0 52.0
   1600x1200 53.0
   960x600 54.0
   800x600 55.0

[Steven McCoy (dsbunny)]

Trying to set dual monitors with the restricted nvidia driver using displayconfig-gtk I end up with the primary monitor with 3200x2048 virtual resolution, secondary 1:1, both at 1920x1200 real resolution. No greeter crash.

Why is the "Virtual 3200 2048" line in there?

Section "Screen"
        Identifier "Default Screen"
        Device "nVidia Corporation G70 [GeForce 7600 GT]"
        Monitor "Cinema HD"
        Defaultdepth 24
        SubSection "Display"
                Depth 24
                Virtual 3200 2048
                Modes "1920x1200@60" "2560x1600@60" "1680x1050@60"
"3200x2048@60" "1600x1024@60" "1440x900@60" "1280x800@60" "1280x720@60"
"1280x768@60" "800x600@60"
        EndSubSection
EndSection

Section "ServerLayout"
        Identifier "Default Layout"
  screen 0 "Default Screen" 0 0
  screen 1 "screen1" rightof "Default Screen"
        Inputdevice "Generic Keyboard"
        Inputdevice "Configured Mouse"

        # Uncomment if you have a wacom tablet
        # InputDevice "stylus" "SendCoreEvents"
        # InputDevice "cursor" "SendCoreEvents"
        # InputDevice "eraser" "SendCoreEvents"
EndSection

[Sebastian Heinlein (glatzor)]

Which gdm version do you use, Steven? Please fill a separate bug report for different issues in the future.

[Steven McCoy (dsbunny)]

The latest in the main/update/security repo:

gdm 2.20.0-0ubuntu
displayconfig-gtk 0.3.7
nvidia-glx-new 100.14.19+2.6.22.4-14.9
nvidia-kernel-common 20051028+1ubuntu7
xserver-xorg-video-nv 1:2.1.5-1ubuntu1

[Timo Aaltonen (tjaalton)]

Nvidia related.

[Bryce Harrington (bryce)]

Thank you for reporting this bug and for your efforts to make Ubuntu better. As Xorg has improved this past year, an unfortunate side effect of these improvements is that it has rendered several design assumptions in displayconfig-gtk obsolete. So, starting with Hardy we are no longer putting displayconfig-gtk forth as a primary configuration tool, and are putting our development focus into the Screen Resolution applet. As a result, we do not plan to fix this bug and thus are closing it.

For more background on this change, please see this page: [WWW] https://wiki.ubuntu.com/X/DisplayConfigGtk

[Jonathan Thomas (echidnaman)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Zerhash (zerhash)]

this was a long time ago. I dont think it is a problem but im no longer on
ubuntu. `

On Sun, Apr 19, 2009 at 11:40 AM, Jonathan Thomas <email address hidden>wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering if this is still an issue
> for you. Can you try with the latest Ubuntu release? Thanks in advance.
>
> ** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> Dual monitor Greeter crash
> https://bugs.launchpad.net/bugs/152544
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Sergio Zanchetta (primes2h)]

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-restricted-modules-2.6.22 task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Thanks in advance.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!