Bug 612552 - [abrt] crash in metacity-2.30.0-3.fc13: Process /usr/bin/metacity was killed by signal 4 (SIGILL)
Summary: [abrt] crash in metacity-2.30.0-3.fc13: Process /usr/bin/metacity was killed ...
Alias: None
Product: Fedora
Classification: Fedora
Component: metacity
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:3b0f8ecbbe8888e4bf7937b7300...
: 612553 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-08 14:01 UTC by Vincenzo
Modified: 2011-06-29 13:49 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2011-06-29 13:49:41 UTC

Attachments (Terms of Use)
File: backtrace (16.91 KB, text/plain)
2010-07-08 14:01 UTC, Vincenzo
no flags Details

Description Vincenzo 2010-07-08 14:01:08 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: metacity
component: metacity
crash_function: meta_window_reload_properties_from_xwindow
executable: /usr/bin/metacity
global_uuid: 3b0f8ecbbe8888e4bf7937b7300bbae6d4d8798b
package: metacity-2.30.0-3.fc13
rating: 4
reason: Process /usr/bin/metacity was killed by signal 4 (SIGILL)
release: Fedora release 13 (Goddard)

How to reproduce
1after this problem:
(I'm not sure.)

Comment 1 Vincenzo 2010-07-08 14:01:11 UTC
Created attachment 430370 [details]
File: backtrace

Comment 2 Jeff Raber 2010-07-08 17:50:26 UTC
*** Bug 612553 has been marked as a duplicate of this bug. ***

Comment 3 Jeff Raber 2010-07-08 17:57:58 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information would be helpful in our diagnosis of this issue.

Please attach:
* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

Also, can you provide more detailed instructions to reproduce the issue?  Is this issue constantly reproducible?

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 4 Owen Taylor 2010-07-08 18:07:28 UTC
Jeff - thanks for the triaging, but for future reference, the only thing that's at all useful in what you are requesting is the instructions to reproduce. (Which the reporter already gave as best as they knew.) X and server configs and logs generally are irrevelant to metacity crashes.

Comment 5 Jeff Raber 2010-07-08 21:21:43 UTC
Owen - Thanks for the tip.  I am a bit of a casual 'triager', not sticking to any particular packages.  I guess I am accustomed to compiz crashes that often times involve bugs excited in graphics drivers.

NEEDINFO cleared.

Comment 6 Jeff Raber 2010-07-08 21:28:47 UTC
hmmm...I didn't intend to set the status to ASSIGNED.  Setting it back to NEW.

Comment 7 Bug Zapper 2011-06-01 14:26:20 UTC
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: 

Comment 8 Bug Zapper 2011-06-29 13:49:41 UTC
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.

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