compiz.real crashed with SIGSEGV; KOrganizer crashed first

Bug #306711 reported by merekat
4
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: compiz

Running 8.10.

Have experienced this or similar bug a number of times now, seemingly with a variety of applications, since installing 8.10 for the first time 12/04/2008 (linux and ubuntu newbie). Went to submit bug reports previously but didn't realize that I only subscribed to closed or inactive threads (not so familiar yet with this bug reporting process).

This time was running only Firefox and KOrganizer. KOrganizer crashed, and the KDE crash handler produced a report. See attached text file. Then compiz crashed.

Syslogs, messages, and dmesg have shown a number of errors, but I don't know what's relevant and what's not.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/compiz.real
Package: compiz-core 1:0.7.8-0ubuntu4.1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --indirect-rendering core ccp
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: compiz
Stacktrace: #0 0x08055c8c in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: compiz.real crashed with SIGSEGV
Uname: Linux 2.6.27-9-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare scanner tape video

Revision history for this message
merekat (leahthelioness) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

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
Jonathan Thomas (echidnaman) 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.