Frequent compiz crashes in libwobbly.so

Bug #501149 reported by Ryan Beasley
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: compiz

I see this bug semi frequently (but not 100%) when doing things such as maximizing windows. This system was upgraded from Jaunty to Karmic, /and/ I have upgrade my NVIDIA driver to 190.53. I haven't yet tested with an older NVIDIA driver.

I'll attach a stacktrace.

ryanb@agata ~> lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

ryanb@agata ~> apt-cache policy compiz
compiz:
  Installed: 1:0.8.4-0ubuntu2
  Candidate: 1:0.8.4-0ubuntu2
  Version table:
 *** 1:0.8.4-0ubuntu2 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: amd64
CompizPlugins: [core,move,resize,place,decoration,animation,ccp,gnomecompat,session,png,extrawm,text,svg,workarounds,vpswitch,imgjpeg,video,neg,mousepoll,dbus,resizeinfo,shift,regex,snap,wall,wobbly,expo,fade,scale,scaleaddon,staticswitcher]
Date: Mon Dec 28 14:13:23 2009
DistroRelease: Ubuntu 9.10
MachineType: Gateway GM5478
NonfreeKernelModules: nvidia
Package: compiz 1:0.8.4-0ubuntu2
PackageArchitecture: all
PciDisplay: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1)
ProcCmdLine: root=UUID=4491a344-f190-4d58-831c-daf1fbdc24be ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-16.53-server
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu10
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: compiz
Uname: Linux 2.6.31-16-server x86_64
dmi.bios.date: 12/04/2007
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.15A.0296.2007.1204.2131
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DG33SXG2
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD94468-402
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.15A.0296.2007.1204.2131:bd12/04/2007:svnGateway:pnGM5478:pvr:rvnIntelCorporation:rnDG33SXG2:rvrAAD94468-402:cvn:ct2:cvr:
dmi.product.name: GM5478
dmi.sys.vendor: Gateway
system: distro = Ubuntu, architecture = x86_64, kernel = 2.6.31-16-server

Revision history for this message
Ryan Beasley (ryan-beasley) wrote :
Revision history for this message
Ryan Beasley (ryan-beasley) wrote :

Stacktrace obtained by logging in from a second machine, attaching GDB to compiz.real, and then waiting until the next crash occurred.

In the meantime, I've disabled the wobbly effect as a (hopeful) workaround. If additional reproductions/details are needed, just ask.

Thanks. =)

Revision history for this message
Ryan Beasley (ryan-beasley) wrote :

Also, FYI, I think that ubuntu-bug/apport ended up selecting the wrong X configuration and log files. (I have 3 servers running--long story, don't ask.) If they're relevant, I can attach them later.

Revision history for this message
Y.Z. (y-zinch) wrote :

i can confirm same problem on Ubuntu 9.10 x86_64, Nvidia driver version 185.18.36.

tags: added: compiz-0.8
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in compiz (Ubuntu):
status: New → 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.