Bug 596754 - [abrt] crash in metacity-2.30.0-2.fc13: raise: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)
[abrt] crash in metacity-2.30.0-2.fc13: raise: Process /usr/bin/metacity was ...
Status: CLOSED DUPLICATE of bug 596747
Product: Fedora
Classification: Fedora
Component: metacity (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Owen Taylor
Fedora Extras Quality Assurance
abrt_hash:92990d99f1e8b0fa16f8e2cea20...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-27 09:07 EDT by Jan Kratochvil
Modified: 2010-07-08 14:11 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-08 14:11:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (15.54 KB, text/plain)
2010-05-27 09:07 EDT, Jan Kratochvil
no flags Details

  None (edit)
Description Jan Kratochvil 2010-05-27 09:07:38 EDT
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: metacity
component: metacity
crash_function: raise
executable: /usr/bin/metacity
global_uuid: 92990d99f1e8b0fa16f8e2cea206eb606d83182c
kernel: 2.6.33.4-95.fc13.x86_64
package: metacity-2.30.0-2.fc13
rating: 4
reason: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

comment
-----
There is probably a second bug in wnck-applet.
In /apps/metacity/workspace_names the highest is name_16 despite /apps/metacity/general/num_workspaces is 24.

How to reproduce
-----
1. Create 24 workspaces (in two rows, 12 per row).
2. Use F-12 for half a year.
3. Upgrade to F-13.
Comment 1 Jan Kratochvil 2010-05-27 09:07:41 EDT
Created attachment 417235 [details]
File: backtrace
Comment 2 Owen Taylor 2010-07-08 14:11:20 EDT

*** This bug has been marked as a duplicate of bug 596747 ***

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