abrt detected a crash. How to reproduce ----- 1. Logged in at the graphical login window 2. While the login was in progress switched to tty2 console 3. After a while on text console, switched back to graphical console and saw complete white screen. 4. Reproduceability is 50% Attached file: backtrace cmdline: compiz --sm-client-id 10da7ba3678a046c7d125859434442271400000026710030 --ignore-desktop-hints glib gconf gnomecompat component: compiz executable: /usr/bin/compiz kernel: 2.6.31.5-127.fc12.i686 package: compiz-0.8.2-19.fc12 rating: 3 reason: Process was terminated by signal 11
Created attachment 370262 [details] File: backtrace
Hi Amit, 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 could you 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 below. By the way: may I ask you to try the same with KMS disabled and report back the result. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Regards -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Hi all, I was passing again over this. And it looks like this might be a 100% compiz related issue, and hence the requested files might not needed. So I will leave it to our maintainers. @Adel, it is up to you. Regards. Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Core was generated by `compiz --sm-client-id 10da7ba3678a046c7d125859434442271400000026710030 --ignore'. Program terminated with signal 11, Segmentation fault. #0 0x080547dd in doPoll (timeout=<value optimized out>) at display.c:1211 in display.c Thread 1 (Thread 1702): #0 0x080547dd in doPoll (timeout=<value optimized out>) at display.c:1211 w = 0x3f800000 i = <value optimized out> rv = 3 #1 0x0805755b in eventLoop () at display.c:1655 ------------------------- So it can be indexed. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 551083 has been marked as a duplicate of this bug. ***
*** Bug 553503 has been marked as a duplicate of this bug. ***
*** Bug 583229 has been marked as a duplicate of this bug. ***
*** Bug 595110 has been marked as a duplicate of this bug. ***
*** Bug 538698 has been marked as a duplicate of this bug. ***
*** Bug 600645 has been marked as a duplicate of this bug. ***
Offending section of code: 01:doPoll (int timeout) 02:{ 03: int rv; 04: 05: rv = poll (core.watchPollFds, core.nWatchFds, timeout); 06: if (rv) 07: { 08: CompWatchFd *w; 09: int i; 10: 11: for (i = core.nWatchFds - 1, w = core.watchFds; w; i--, w = w->next) 12: { 13: if (core.watchPollFds[i].revents != 0 && w->callBack) 14: (*w->callBack) (w->closure); 15: } 16: } 17: 18: return rv; 19:} Crashes seem to happen at lines 11 and 13 above. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Also, I'm fairly sure that bug 551456 is related, if not the same bug. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Package: compiz-0.8.6-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Navegar 2. 3.
Package: compiz-0.8.6-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Compiz froze while adjustig ccsm. Attempting to reload compiz failed.
*** Bug 551456 has been marked as a duplicate of this bug. ***
*** Bug 610807 has been marked as a duplicate of this bug. ***
*** Bug 605824 has been marked as a duplicate of this bug. ***
*** Bug 586165 has been marked as a duplicate of this bug. ***
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 603318 has been marked as a duplicate of this bug. ***
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
Changing version to 13 as there appear to be several instances of this crash reported against F13. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Hi guys, Changing the title. Regards Hamidou -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 652153 has been marked as a duplicate of this bug. ***
Package: compiz-0.8.6-3.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.Shutdown computer 2. 3.
Package: compiz-0.8.6-3.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.Re size windows 2. 3.
Package: compiz-0.8.6-3.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.Happends before shutdown computer 2. 3.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.