Compiz and glx* fail on glXCreateContext
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Just updated to Lucid Lynx beta 2
Compiz prints out this:
compiz (core) - Fatal: glXCreateContext failed
compiz (core) - Error: Failed to manage screen: 0
compiz (core) - Fatal: No manageable screens found on display :0.0
Launching fallback window manager
glx* (glxinfo, glxgears, etc) print out:
Error: glXCreateContext failed
I am using the nvidia driver on a GeForce 8600 GT.
Possibly related, nothing using OpenGL works. lightsoff, World of Goo, neverball, armagetron advanced. They all fail to create a GL context.
---
Architecture: i386
DistroRelease: Ubuntu 10.04
DkmsStatus:
virtualbox-ose, 3.1.6, 2.6.31-21-generic, i686: built
virtualbox-ose, 3.1.6, 2.6.32-19-generic, i686: installed
nvidia-current, 195.36.15, 2.6.31-21-generic, i686: built
nvidia-current, 195.36.15, 2.6.32-19-generic, i686: installed
NonfreeKernelMo
Package: nvidia-
ProcCmdLine: root=UUID=
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/usr/bin/zsh
ProcVersionSign
Tags: lucid lucid
Uname: Linux 2.6.32-19-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy git-data lpadmin netdev plugdev powerdev pulse pulse-access sambashare scanner video
dmi.bios.date: 12/27/2006
dmi.bios.vendor: Intel Corp.
dmi.bios.version: MQ96510J.
dmi.board.
dmi.board.name: DG965RY
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD41691-207
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCor
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-19-generic
affects: | ubuntu → compiz (Ubuntu) |
affects: | compiz (Ubuntu) → nvidia-graphics-drivers (Ubuntu) |
tags: | added: lucid |
Please run apport-collect 560506 to attach your logs to this bug. Off the top of my head I'm guessing you are using nouveau and did not activate the nvidia restricted drivers though, and I'd recommend disabling the nvidia-current drivers in jockey and then reenabling them and then rebooting just to be sure they are activated.