nVidia X Server Settings tool specifies invalid RGBPath

Bug #279222 reported by Loïc Martin
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-177 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xorg

In Intrepid Beta 1, using Nvidia X Server Settings to configure the two monitors attached to an Nvidia card (7900GS) as separate X screens, Xorg fails to start on the xorg.conf generated by the tool. After that, failsafeX shows, and allow me to use X in 1024x780 (mirror mode).

Attached are the relevant files, along with the backup created by failsafeX.
Monitors :
-first monitor : Iiyama B2403WS (1920x1200)
-second monitor : Wacom Cintiq 12wx (1280x800)

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
NonfreeKernelModules: nvidia
Package: xorg 1:7.4~2ubuntu5
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.27-5-generic (buildd@yellow) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu8) ) #1 SMP Fri Oct 3 00:36:38 UTC 2008

SourcePackage: xorg
Uname: Linux 2.6.27-5-generic x86_64
xkbcomp:

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 02)
     Subsystem: Giga-byte Technology Device [1458:5000]
01:00.0 VGA compatible controller [0300]: nVidia Corporation G71 [GeForce 7900 GS] [10de:0292] (rev a1)
     Subsystem: Giga-byte Technology Device [1458:e000]
05:00.0 VGA compatible controller [0300]: Matrox Graphics, Inc. MGA 1064SG [Mystique] [102b:051a] (rev 02)
     Subsystem: Giga-byte Technology Device [1458:1000]

Revision history for this message
Loïc Martin (loic-martin3) wrote :
Revision history for this message
elpernotador (services-elpernotador) wrote :

i have de same problem! any change in xorg.conf result in a disaster. Only a few changes are accepted.

Revision history for this message
Fabian A. Scherschel (fabsh) wrote :

I can reproduce this with Intrepid with the latest updates (this morning). nvidia-settings also gives an rror about not being able to parse the default xorg.conf that is shipped with the system.

Revision history for this message
Fabian A. Scherschel (fabsh) wrote :

Multiple users have reported this, changing to Confirmed.

Changed in nvidia-graphics-drivers-177:
status: New → Confirmed
Revision history for this message
themuddler (mike-udall) wrote :

Installed the 8.10 release candidate today and met this problem (at least I think it's this problem). On my second x screen I can move my mouse pointer over the full screen dimensions, but the portion usable by gnome is much smaller (see attached screenshot). This wasn't a problem in 8.04 and is a definite regression for me. I can attach logs etc if it will help but don't want to clutter this report unnecessarily. Thanks.

Revision history for this message
themuddler (mike-udall) wrote :

Tested with the 173 driver and the problem does not occur.

Revision history for this message
revgazza (jagdriver) wrote :

Tested with the 173 driver and problem persists. Any attempt to configure separate xscreen results in nvidia-setting crash.

Revision history for this message
Alberto Milone (albertomilone) wrote :

try removing the following lines from your xorg.conf:
Section "Files"
    RgbPath "/usr/X11R6/lib/X11/rgb"
EndSection

Revision history for this message
Loïc Martin (loic-martin3) wrote :

That section isn't at all in the xorg.conf generated at install, by dpkg-reconfigure -phigh, by jockey or any other mean. The crash also appear with default xorg.conf in Intrepid (before the user configure the second screen as activated in Twinview mode), so the presence of the section isn't a problem.

I attached the xorg.conf I'm using now (gave up on configuring the second monitor).

Revision history for this message
Alberto Milone (albertomilone) wrote :

Loïc: I meant to say that X.org will crash if you have the RgbPath line in your xorg.conf. The xorg.conf included in your report has it and the Xorg.0.log.old which you attached shows that RgbPath caused your problem:

Parse error on line 32 of section Files in file /etc/X11/xorg.conf
 "RgbPath" is not a valid keyword in this section.

And I know that Jockey doesn't add that line since I worked on xorg configuration in Jockey.

What's the output of this command?
apt-cache policy nvidia-settings

themuddler: Can you reproduce the problem if you disable the 3D effects?

Revision history for this message
Fabian A. Scherschel (fabsh) wrote :

My problem turned out to be the one covered by bug #286424 which I was able to fix with the instructions in that comment.

Changed in nvidia-graphics-drivers-177:
status: Confirmed → Incomplete
Revision history for this message
Christopher Armstrong (radix) wrote :

I just upgraded from a Hardy installation to Intrepid and this bug bit me. Hardy was the first OS installed, and I don't particularly remember having ever to change my xorg.conf.

I have no idea what wrote that "RgbPath" directive to my xorg.conf, but commenting it out allowed me to use high-res X again.

On my machine the output of 'apt-cache policy nvidia-settings' is as follows:

radix@lantern:~$ apt-cache policy nvidia-settings
nvidia-settings:
  Installed: 177.78-0ubuntu2
  Candidate: 177.78-0ubuntu2
  Version table:
 *** 177.78-0ubuntu2 0
        500 http://ubuntu.media.mit.edu intrepid/main Packages
        100 /var/lib/dpkg/status

Steve Beattie (sbeattie)
Changed in nvidia-graphics-drivers-177:
status: Incomplete → New
Bryce Harrington (bryce)
Changed in nvidia-graphics-drivers-177:
status: New → Confirmed
Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

[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.]

Revision history for this message
Bryce Harrington (bryce) wrote :

[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. Please be aware that because this
is a proprietary graphics driver, the amount of bug support we can
provide at the distro level is very limited.

Changed in nvidia-graphics-drivers-177:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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