This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 767447 - Launching the fusion-icon causes the system to crash
Launching the fusion-icon causes the system to crash
Product: Fedora
Classification: Fedora
Component: fusion-icon (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Karol Trzcionka
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-12-13 23:43 EST by David Batson
Modified: 2012-08-07 12:43 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-07 12:43:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:

Attachments (Terms of Use)
After running compiz --replace *** in terminal here is the output when launching fusion-icon (2.83 KB, application/octet-stream)
2011-12-13 23:43 EST, David Batson
no flags Details
After running compiz --replace *** in terminal here is the output when launching fusion icon from Applications menu (1.71 KB, application/octet-stream)
2011-12-13 23:48 EST, David Batson
no flags Details

  None (edit)
Description David Batson 2011-12-13 23:43:44 EST
Created attachment 546521 [details]
After running compiz --replace *** in terminal here is the output when launching fusion-icon

Description of problem:
F15 system fully updated.
On system boot up, compiz is running fine.
Launch the Compiz Fusion Icon from the Applications menu (or from terminal) and the system crashes not accepting any keyboard input.  Mouse works partially.  Cannot logout or shutdown system except by holding down the power button (hard shutdown).

Version-Release number of selected component (if applicable):

How reproducible:
Launch Compiz Fusion Icon after booting up.  System crashes.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
If I do the following first, the Compiz Fusion Icon will usually launch without crashing, and I can start ccsm from it, however "Reload Window Manager" from the fusion icon crashes the system.
$ compiz --replace --sm-disable ccp & gtk-window-decorator --replace &

Sometimes when I do the above in terminal and get a crash after launching the fusion icon, the following is displayed:
*** glibc detected *** compiz: corrupted double-linked list: 0x0000000001e0b640 ***
Comment 1 David Batson 2011-12-13 23:48:34 EST
Created attachment 546522 [details]
After running compiz --replace *** in terminal here is the output when launching fusion icon from Applications menu

Installed compiz rpms.

$ rpm -qa | grep compiz

$ rpm -qa | grep fusion
Comment 2 Fedora End Of Life 2012-08-07 12:43:04 EDT
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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:

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