compiz.real crashed with SIGSEGV in removeDisplay()

Bug #275465 reported by Taylor "Ripps" LeMasurier-Wren
10
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: compiz

Intrepid Ibex. Trying to use the gconf backend.

ProblemType: Crash
Architecture: i386
Disassembly: 0xb791b2c0:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/compiz.real
Package: compiz-core 1:0.7.7+git20080807-0ubuntu10
ProcAttrCurrent: unconfined
ProcCmdline: compiz --replace --sm-disable --ignore-desktop-hints ccp --indirect-rendering
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/distcc/bin:/home/username/bin:/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: compiz
Stacktrace:
 #0 0xb791b2c0 in ?? ()
 #1 0x0805575f in removeDisplay ()
 #2 0x08052e28 in finiCore ()
 #3 0x0805282a in main ()
StacktraceTop:
 ?? ()
 removeDisplay ()
 finiCore ()
 main ()
Title: compiz.real crashed with SIGSEGV in removeDisplay()
Uname: Linux 2.6.27-4-generic i686
UserGroups: adm admin audio cdrom dialout dip ebox floppy fuse lpadmin mythtv netdev plugdev polkituser powerdev pulse pulse-access pulse-rt sambashare scanner users video

Revision history for this message
Taylor "Ripps" LeMasurier-Wren (ripps818) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
removeDisplay (d=0xb7ffeff4) at ../../src/display.c:2634
finiCore () at ../../src/core.c:223
main (argc=6, argv=0xbfa3c6e4) at ../../src/main.c:442

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in compiz:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) 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.