libgl1-mesa-glx conflicts with nvidia-current (nvidia-304)

[Brenton Fletcher]

NOTES:
I am NOT using the xorg-edgers PPA.
I am NOT using the non-package binary driver from nvidia.com
I am NOT using nouveau.

When the libgl1-mesa-glx package is installed and the nvidia-current (i.e. nvidia-304) package is also installed, something is running

update-alternatives --set x86_64-linux-gnu_gl_conf /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf

on what seems to be every boot. This is problematic, because in fact the alternative should be set like:

update-alternatives --set x86_64-linux-gnu_gl_conf /usr/lib/nvidia-304/ld.so.conf

Having the alternative set to mesa prevents the nvidia kernel and xorg modules from being loaded, which causes X to fall back to the built-in intel GPU and driver, which doesn't work.

The result on boot is either:

1. A black screen with a couple of notices e.g.:

[ 14.475147] i915 0000:00:02.0: Invalid ROM contents

2. A purple screen with no other content, but the "lightdm has started the greeter and is waiting for your password" noise is heard.

Neither of these is a good result; in case 1 I can switch to different VT but I do not get a login prompt on any of them, and in case 2 I _cannot switch VT_.

If the alternative is set to the nvidia conf and then the gui is started, for example by:

1. boot
2. enter recovery mode
3. fsck
4. drop to root prompt
5. update-alternatives --set x86_64-linux-gnu_gl_conf /usr/lib/nvidia-304/ld.so.conf
6. exit
7. resume normal boot.

Everything works perfectly. AFAICT this is _NOT_ a bug in the NVidia binary driver, the wrong alternative is simply being used.

I am reporting this issue against the libgl1-mesa-glx package, as that package provides the mesa ld.so.conf file in question.

Extra details:
Hardware: MacBookPro9,1
Ubuntu version: Raring x86_64

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
Uname: Linux 3.8.0-30-generic x86_64
NonfreeKernelModules: nvidia wl
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.88 Wed Mar 27 14:26:46 PDT 2013
 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1)
.tmp.unity.support.test.0:

ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Sep 24 23:19:52 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.20.155.1+bdcom, 3.8.0-19-generic, x86_64: installed
 bcmwl, 6.20.155.1+bdcom, 3.8.0-30-generic, x86_64: installed
 nvidia-304, 304.88, 3.8.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Once a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: I don't know
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:00fb]
 NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:00fc]
InstallationDate: Installed on 2013-09-17 (7 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Apple Inc. MacBookPro9,1
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=9d41d1bf-0a1a-4969-8be4-bb0f4bdeb0a4 ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D3.B08.1208081132
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-4B7AC7E43945597E
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-4B7AC7E43945597E
dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E:
dmi.product.name: MacBookPro9,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.43-0ubuntu1.1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Sep 24 23:01:03 2013
xserver.configfile: default
xserver.errors:
 Failed to load module "nouveau" (module does not exist, 0)
 Failed to load module "nouveau" (module does not exist, 0)
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.13.3-0ubuntu6

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.