Bug 526593 - [abrt] crash detected in compiz-0.8.2-15.fc12
Summary: [abrt] crash detected in compiz-0.8.2-15.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 531714
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fc39586970c49aba37c5d601be1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-30 22:58 UTC by Robert Laverick
Modified: 2018-04-11 12:00 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-20 18:27:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.80 KB, text/plain)
2009-09-30 22:58 UTC, Robert Laverick
no flags Details

Description Robert Laverick 2009-09-30 22:58:16 UTC
abrt detected a crash.


How to reproduce
-----
1. enable compiz
2. disable compiz
3. compiz crashes while exiting


Additional information
======


Attached files
----
backtrace

cmdline
-----
compiz --ignore-desktop-hints glib gconf gnomecompat --replace 


component
-----
compiz


executable
-----
/usr/bin/compiz


kernel
-----
2.6.31.1-56.fc12.x86_64


package
-----
compiz-0.8.2-15.fc12


reason
-----
Process was terminated by signal 11

Comment 1 Robert Laverick 2009-09-30 22:58:19 UTC
Created attachment 363257 [details]
File: backtrace

Comment 2 Francesco Frassinelli (frafra) 2009-10-06 18:08:43 UTC
+1

Comment 3 Matěj Cepl 2009-10-12 21:28:46 UTC
Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there is not a symbolic stack trace. In order to get a symbolic stack trace, the appropriate debuginfo packages need to be installed. In order to accomplish this, you can run the command: 

    debuginfo-install compiz

Please see http://fedoraproject.org/wiki/StackTraces for more information about stack traces.

Comment 4 Francesco Frassinelli (frafra) 2009-10-13 13:38:51 UTC
@Matej Cepi

After doing:
debuginfo-install compiz
debuginfo-install expat-2.0.1-7.x86_64 glib2-2.22.2-1.fc12.x86_64 libXau-1.0.5-1.fc12.x86_64 libXxf86vm-1.0.99.1-1.fc12.x86_64 libdrm-2.4.14-1.fc12.x86_64 libselinux-2.0.87-1.fc12.x86_64 libuuid-2.16-10.2.fc12.x86_64 libxcb-1.4-1.fc12.x86_64 xcb-util-0.3.6-1.fc12.x86_64
...Nothing changes: the backtrace is still the same.

I think that is not really compiz related: it could be a Desktop effect applet bug, because mutter crash also with this applet if you choose something different. See also: https://bugzilla.redhat.com/show_bug.cgi?id=527522.

Comment 5 Joachim Frieben 2009-10-23 09:33:44 UTC
Closing CLOSED INSUFFICIENT_DATA appears a bit tough to me: I can reproduce this issue reliably by merely disabling desktop effects through desktop-effects. Even after letting abrt install all debug packages it asked for, the backtrace is the same as the original one.
This is not the reporter's fault, and the issue is for real.

Comment 6 Robert Laverick 2009-10-28 00:49:29 UTC
I've tried a number of the methods in the StackTraces, and installed a lot of different debuginfo rpms and am still totally unable to get anything better out in terms of a stack trace, if I attach GDM to compiz I don't seem to be able to get it to crash, I've tried to make it work from the command line, but I can't work out how to make it crash from the command line.

this is the best backtrace I can get out of it, and I've no idea what else to try. :-(

Comment 8 Bug Zapper 2009-11-16 13:08:46 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Matěj Cepl 2009-11-17 12:02:39 UTC
Switching incorrect assignees to the default one.

Comment 10 Hamidou Dia 2009-11-20 18:27:22 UTC
Hi Robert.

Many thanks for bringing this to our attention.
Don't worry we already got a meaningful traceback available for the issue you reported.


Regards.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

*** This bug has been marked as a duplicate of bug 531714 ***


Note You need to log in before you can comment on or make changes to this bug.