Bug 622212 - [abrt] crash in metacity-2.30.0-3.fc13: raise: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in metacity-2.30.0-3.fc13: raise: Process /usr/bin/metacity was ...
Alias: None
Product: Fedora
Classification: Fedora
Component: metacity   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:1980229015c2f47ba678e6a36fc...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-08 06:11 UTC by GJahchan
Modified: 2011-06-28 14:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-28 14:51:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (15.33 KB, text/plain)
2010-08-08 06:11 UTC, GJahchan
no flags Details

Description GJahchan 2010-08-08 06:11:08 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: metacity --replace
component: metacity
crash_function: raise
executable: /usr/bin/metacity
global_uuid: 1980229015c2f47ba678e6a36fc216531a51957a
package: metacity-2.30.0-3.fc13
rating: 4
reason: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

Comment 1 GJahchan 2010-08-08 06:11:12 UTC
Created attachment 437410 [details]
File: backtrace

Comment 2 David Kovalsky 2010-08-09 12:46:10 UTC
Package: metacity-2.30.0-3.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)

How to reproduce
1. Logged in after upgrading from F12 -> F13

Comment 3 David Kovalsky 2010-08-09 14:11:25 UTC
I see this error:

metacity:ERROR:core/prefs.c:2532:meta_prefs_get_workspace_name: assertion failed: (workspace_names[i] != NULL)
Aborted (core dumped)

Wondering if it's related to the fact that I have 21 workspaces. Some have a name, some don't (21st).

Comment 4 David Kovalsky 2010-08-09 14:21:12 UTC
After using gconf-editor to change Apps/Metacity/General/num_workspaces from 21 to 20 everything magically started working. 

Big thanks to Tomas Bzatek!

Comment 5 Bug Zapper 2011-06-01 11:54: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 6 Bug Zapper 2011-06-28 14:51:06 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.