Red Hat Bugzilla – Bug 482806
compiz segfault in libstartup-notification-1.so.0.0.0
Last modified: 2018-04-11 04:17:42 EDT
Description of problem:
Found in /var/log/messages random hex data, one example is
compiz: segfault at 78feb60 ip 078feb60 sp bf81e1e4 error 4 in libstartup-notification-1.so.0.0.0[7fef000+8000]
Version-Release number of selected component (if applicable):
How reproducible: don't know; appears regularly in /var/log/messages
Steps to Reproduce:
1. don't know
Could we get that /var/log/messages attached to this bug as a separate uncompressed attachment, please?
Created attachment 330300 [details]
Request from Matej Cepl <email@example.com> for /var/log/messages
Enabled *testing* repos and upgraded machine. Now getting segfaults in glxinfo and glx_tfp_test. Compiz no longer works (it did previously). Will attach the new /var/log/messages.
How do I add an attachment here? Thanks.
(In reply to comment #4)
> How do I add an attachment here? Thanks.
In the table Attachments (just above this box), there is a link "Add an attachment".
Created attachment 330695 [details]
Wiped drive; reinstalled F10 and upgraded. Now getting the following error messages:-
kernel: compiz: segfault at d63b60 ip 00d63b60 sp bf9baaf4 error 4 in libICE.so.6.3.0[dd8000+17000]
Will attach /var/log/messages.
Created attachment 331547 [details]
I am seeing this on a fully updated F10 system. Entry in /var/log/dmesg reads
"compiz: segfault at 37d1b60 ip 037d1b60 sp bfc10754 error 4 in
Video device is a rather old "ATI Technologies Inc Radeon R100 QD [Radeon 7200] rev 0". The system's SMOLT profile is located at
Installed packages include:
I have updated to F11 and am getting segfault errors in compiz, but in libSM.so.6.0.0 this time.
I am running the proprietary nvidia module from rpmfusion-nonfree. The following is a list of installed software.
I will attach /var/log/messages
Created attachment 349173 [details]
/var/log/messages from F11 clean install, then upgraded via PackageKit.
Switching incorrect assignees to the default one.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.
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 10'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 10 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:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.