compiz.real crashed with SIGSEGV

Bug #152934 reported by René Brandenburger
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: compiz

sometimes, after a reboot i don't have 3d desktop anymore, seems like compiz crashes already during session startup.

ProblemType: Crash
Architecture: i386
Date: Sat Oct 13 21:19:48 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/compiz.real
NonfreeKernelModules: cdrom
Package: compiz-core 1:0.6.0+git20071008-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --indirect-rendering --sm-client-id default0 ccp
ProcCwd: /home/rbrandenburger
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_LU.UTF-8
Signal: 11
SourcePackage: compiz
Stacktrace:
 #0 0x08065c5a in ?? ()
 #1 0x080767e0 in ?? ()
 #2 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 20674):
 #0 0x08065c5a in ?? ()
 #1 0x080767e0 in ?? ()
 #2 0x00000000 in ?? ()
Title: compiz.real crashed with SIGSEGV
Uname: Linux debberlein 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev scanner video

Tags: apport-crash
Revision history for this message
René Brandenburger (rene-brandenburger) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:autoRaiseTimeout (closure=0x80767e0) at ../../src/event.c:190
handleTimeouts (tv=0xbf8224bc) at ../../src/display.c:1460
eventLoop () at ../../src/display.c:1886
main (argc=7, argv=0xbf822a34) at ../../src/main.c:441

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in compiz:
importance: Undecided → Medium
Changed in compiz:
status: New → Confirmed
Revision history for this message
Travis Watkins (amaranth) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in compiz:
status: Confirmed → Incomplete
Revision history for this message
René Brandenburger (rene-brandenburger) wrote :

I can't test it at the moment, as it is much to unstable (several complete lockups per day) and I don't have access to a testing machine at the moment.

Will retry after GA of Hardy

Revision history for this message
Travis Watkins (amaranth) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in compiz:
status: Incomplete → 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.