GLX extension not found after update

Bug #1136793 reported by Christopher Gilbert
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
virtualbox-ose (Ubuntu)
New
Undecided
Unassigned

Bug Description

Just Updated with Proposed Repo Enabled. Upon restart loss of GLX extention, and subsequently compiz.

Ubuntu 12.10
Kernel Linux 3.5.0-26-generic
xorg version 1:7.7+1ubuntu4
compiz version 1:0.9.8.6+bzr3433-0ubuntu1~test1

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-26.40-generic 3.5.7.6
Uname: Linux 3.5.0-26-generic i686
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Feb 28 20:47:09 2013
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
 awdev, 0.1, 2.6.32-41-generic, i686: built
 nvidia-current, 304.43, 3.5.0-25-generic, i686: installedError! Could not locate dkms.conf file.
 File: does not exist.

 nvidia-current, 304.43, 3.5.0-26-generic, i686: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1582]
InstallationDate: Installed on 2012-09-13 (168 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120905.2)
MachineType: ASUSTeK Computer Inc. U56E
MarkForUpload: True
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic root=UUID=64c0320e-ec06-4d16-a7a5-eec4e986dfa2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UnitySupportTest:
 Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 5: Xlib: extension "GLX" missing on display ":0.0".
 Error: GLX is not available on the system
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U56E.213
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U56E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU56E.213:bd12/21/2011:svnASUSTeKComputerInc.:pnU56E:pvr1.0:rvnASUSTeKComputerInc.:rnU56E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: U56E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.8.6+bzr3433-0ubuntu1~test1
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3

Revision history for this message
Christopher Gilbert (qcgilbert) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
Dietmar Winkler (dietmarw) wrote :

The same here. After upgrade I can not run Unity any longer. Even the fallback via llvm does only partly work since the menues (dash?) are not loaded. So basically it's desktop background without any window manager. I had to fall back to XFCE in order to get this working.

Kernel: Version: 3.5.0.17.19
Xorg: Version: 1:7.7+1ubuntu4
compiz: Version: 1:0.9.8.4-0ubuntu2

Revision history for this message
Christopher Gilbert (qcgilbert) wrote :

For some reason VirtualBox-4.2 required nVidia drivers as a dependency. When I did my update it installed the nvidia binary driver and subsequently caused compiz to crash because it saw the driver but couldnt find the nonexistent hardware. I was able to resolve the issue by uninstalling anything nvidia, which removed virtualbox-4.2, and then reinstalling virtualbox-4.2 which, oddly enough, didnt have the nvidia dependency anymore. I did all of this via aptitude (sudo apt-get aptitude) from tty1 (CTR+ALT+F1). Upon reboot all was right again.

Revision history for this message
Christopher Gilbert (qcgilbert) wrote :

Dietmar,
  To see if this is the cause of your issues take a look at your Xorg.0.log located in /var/log directory. If you see anything referencing nvidia then my explination above is valid for your situation. That is, of course, unless you have an nNvidia card.

Revision history for this message
Dietmar Winkler (dietmarw) wrote :

Christopher,

thanks removing all nvidia related packages that had no other dependencies attached helped. So also in my case the Virtual Box package update seemed to have caused the damage. Though I didn't need to remove the Virtual Box package.

Thanks again for finding out,
Dietmar

Timo Aaltonen (tjaalton)
affects: xorg (Ubuntu) → virtualbox-ose (Ubuntu)
Changed in virtualbox-ose (Ubuntu):
status: Confirmed → New
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.