|Summary:||[abrt] crash in compiz-0.8.2-24.fc12: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)|
|Product:||[Fedora] Fedora||Reporter:||Volans <volans2000>|
|Component:||compiz||Assignee:||Adel Gadllah <adel.gadllah>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||12||CC:||adel.gadllah, jeff.raber, tichappe|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-12-03 15:05:11 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Volans 2010-05-04 23:23:19 UTC
abrt 1.0.9 detected a crash. architecture: i686 Attached file: backtrace cmdline: compiz --ignore-desktop-hints glib gconf gnomecompat component: compiz executable: /usr/bin/compiz global_uuid: 889754f53455b34178c5b9622365491f76d172a1 kernel: 188.8.131.52-99.fc12.i686.PAE package: compiz-0.8.2-24.fc12 rating: 4 reason: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Comment 2 Jeff Raber 2010-05-04 23:46:47 UTC
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Comment 3 Tim Chappell 2010-06-07 03:40:26 UTC
Package: compiz-0.8.2-24.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Start Rythmbox 2. start firefox 3. Let run for 30 minutes. Comment ----- Using firefox and Rythmbox.
Comment 4 Jeff Raber 2010-06-07 11:35:44 UTC
Tim Chappell, Is this 100% reproducible? Can you attach a backtrace?
Comment 5 Jeff Raber 2010-06-24 05:04:23 UTC
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Comment 6 Bug Zapper 2010-11-03 15:38:14 UTC
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 7 Bug Zapper 2010-12-03 15:05:11 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.