Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 610092 - [abrt] crash in gnome-utils-1:2.30.0-1.fc13: raise: Process /usr/bin/gnome-screenshot was killed by signal 6 (SIGABRT)
[abrt] crash in gnome-utils-1:2.30.0-1.fc13: raise: Process /usr/bin/gnome-sc...
Status: CLOSED DUPLICATE of bug 545875
Product: Fedora
Classification: Fedora
Component: gnome-utils (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-07-01 10:44 EDT by Mikhail
Modified: 2010-11-09 08:34 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 08:34:26 EST
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 (23.17 KB, text/plain)
2010-07-01 10:44 EDT, Mikhail
no flags Details

  None (edit)
Description Mikhail 2010-07-01 10:44:23 EDT
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gnome-screenshot --window
component: gnome-utils
crash_function: raise
executable: /usr/bin/gnome-screenshot
global_uuid: c4100da68bbb4be343a6c4cbc72871654c2d6d71
package: gnome-utils-1:2.30.0-1.fc13
rating: 4
reason: Process /usr/bin/gnome-screenshot was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Mikhail 2010-07-01 10:44:26 EDT
Created attachment 428457 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 08:34:26 EST

*** This bug has been marked as a duplicate of bug 545875 ***
Comment 3 Karel Klíč 2010-11-09 08:34:26 EST
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #545875.

Sorry for the inconvenience.

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