segfault in nux::IOpenGLFrameBufferObject::Deactivate

Bug #711396 reported by Travis Watkins
230
This bug affects 43 people
Affects Status Importance Assigned to Milestone
Nux
Fix Released
Undecided
Unassigned
Unity
Invalid
Undecided
Unassigned
glew (Ubuntu)
Fix Released
High
Unassigned
Natty
Fix Released
High
Unassigned
nux (Ubuntu)
Fix Released
Undecided
Unassigned
Natty
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

After the latest X/driver updates compiz runs but if you enable the unityshell plugin you get a crash in nux while it tries to setup FBOs. It looks like nux is unable to setup the FBO (intel issue) then crashes while trying to clean up afterward (nux issue). I've attached my compiz crash log.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-video-intel 2:2.14.0-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
DRM.card0.DVI.D.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x800
 edid-base64: AP///////wAGEFucAAAAAA4QAQOAHRJ4Cof1lFdPjCcnUFQAAAABAQEBAQEBAQEBAQEBAQEBvBsAoFAgFzAwIDYAHrMQAAAZAAAAAQAGECAAAAAAAAAAAAogAAAA/gBMVE4xMzNXMQAAAAogAAAA/ABDb2xvciBMQ0QKICAgAMY=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Tue Feb 1 12:19:08 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 4.0.2, 2.6.37-12-generic, x86_64: installed
 bcmwl, 5.100.82.38+bdcom, 2.6.37-12-generic, x86_64: installed
 bcmwl, 5.100.82.38+bdcom, 2.6.38-1-generic, x86_64: installed
GraphicsCard:
 Subsystem: Apple Computer Inc. Device [106b:00a1]
   Subsystem: Apple Computer Inc. Device [106b:00a1]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64+mac (20110104)
MachineType: Apple Inc. MacBook4,1
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic root=UUID=3fa2b187-0edf-45a7-add7-17bf24470864 ro quiet splash vesafb.sucks=1 vt.handoff=7
SourcePackage: xserver-xorg-video-intel
dmi.bios.date: 02/09/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB41.88Z.00C1.B00.0802091535
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F22788A9
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22788A9
dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9:
dmi.product.name: MacBook4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.libdrm2: libdrm2 2.4.23-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10-1ubuntu1
version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.13.2+git20110124.fadee040-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

Related branches

Revision history for this message
Travis Watkins (amaranth) wrote :
Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel (Ubuntu):
importance: Undecided → High
Revision history for this message
Kenny Strawn (realkstrawn93) wrote :

Status tracked in Natty

Revision history for this message
Kenny Strawn (realkstrawn93) wrote :

Sorry, how do I make the above comment the status of this bug in Unity?

Revision history for this message
Kenny Strawn (realkstrawn93) wrote :

Anyway, I assigned this bug to the Ayatana discussion team, since it's Unity related. Hopefully this bug will get fixed very soon. I have decided to install Unity 2D as a workaround for now.

Changed in nux (Ubuntu Natty):
assignee: nobody → Ayatana Discussion (ayatana)
Changed in unity:
assignee: nobody → Ayatana Discussion (ayatana)
Revision history for this message
David Callé (davidc3) wrote :

There is a workaround in bug description #711401 https://bugs.launchpad.net/ubuntu/+source/unity/+bug/711401

Ingo Gerth (igerth)
Changed in unity:
status: New → Confirmed
Changed in nux (Ubuntu Natty):
status: New → Confirmed
Changed in xserver-xorg-video-intel (Ubuntu Natty):
status: New → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

Comment #5 suggests this bug is caused by the recent sync of glew from debian.

Fwiw, probably not a bug in xserver-xorg-video-intel, since yesterday's update was just a no-change rebuild; the last actual change was last Thursday.

Revision history for this message
Connor Carney (cscarney) wrote :

I have the same crash with xserver-xorg-video-ati, so it seems not to be an intel-specific issue.

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

Thanks Connor, that confirms what I suspected.

affects: xserver-xorg-video-intel (Ubuntu Natty) → glew (Ubuntu Natty)
Changed in glew (Ubuntu Natty):
status: Confirmed → In Progress
Revision history for this message
Bryce Harrington (bryce) wrote :

At skaet's direction I've reverted glew back to 1.5.2. This seems to resolve the issue on my test box, and several others have confirmed the same. This solves the problem for the alpha-2 release so I'm going to go ahead and close the nux bug.

However, longer term someone should look deeper into why nux crashes on this newer glew version. Does compiz simply need a rebuild against it, or have there been ABI changes that need accounted for in nux? Hopefully it's not a deep mystery, and can be solved post-alpha-2. I'm leaving the Ayatana Unity upstream task open as a reminder for this work.

Changed in nux (Ubuntu Natty):
status: Confirmed → Fix Released
Changed in glew (Ubuntu Natty):
status: In Progress → Fix Released
Revision history for this message
Bryce Harrington (bryce) wrote :

glew (1.5.7.is.1.5.2-1ubuntu1) natty; urgency=low

  * Revert back to 1.5.2. The 1.5.7 version led to some sudden nux/compiz
    breakages that will need further investigation post-alpha-2.
    (LP: #711401, #711396)

Date: Tue, 01 Feb 2011 13:29:19 -0800
Changed-By: Bryce Harrington <email address hidden>
Maintainer: Ubuntu Developers <email address hidden>
Signed-By: Bryce Harrington <email address hidden>
https://launchpad.net/ubuntu/natty/+source/glew/1.5.7.is.1.5.2-1ubuntu1

Ted Gould (ted)
Changed in unity:
assignee: Ayatana Discussion (ayatana) → nobody
Changed in nux (Ubuntu Natty):
assignee: Ayatana Discussion (ayatana) → nobody
Revision history for this message
Kenny Strawn (realkstrawn93) wrote :

Also changed the assignee of the glew bug to Ayatana.

Changed in glew (Ubuntu Natty):
assignee: nobody → Ayatana Discussion (ayatana)
Revision history for this message
Kenny Strawn (realkstrawn93) wrote :

Sorry; had no idea that the bug Mods unassigned this bug.

Changed in glew (Ubuntu Natty):
assignee: Ayatana Discussion (ayatana) → nobody
Revision history for this message
Omer Akram (om26er) wrote :

ks64, when you report bugs you are not supposed to assign it to someone, neither there is any need to subscribe Mark Shuttleworth or canonical-dx-team. The people who should be notified already get an email when you report a bug report. The same stands for the blueprint that you register. Thanks

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Was anything done to investigate the reason for this crash? Now we have glew "1.5.7.is.1.5.2-1ubuntu1" in natty, which seems like sweeping things under the carpet. I would guess the newer glew merely triggers a bug elsewhere (nux?) and is not really at fault here. BTW, wouldn't "1.5.7-1is.1.5.2-0ubuntu1" have made more sense if for instance a 1.5.7-2 comes along?

Omer Akram (om26er)
Changed in unity:
status: Confirmed → Invalid
Changed in nux:
status: New → Fix Released
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.