Bug 646180

Summary: [abrt] nautilus-2.30.1-6.fc13: killpg: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: pseudo64
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: baldpatches, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:e9c105e4cd250a0d0b2eba2a9a8d0a1480cf6e68
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 13:42:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
File: backtrace none

Description pseudo64 2010-10-24 19:52:22 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: killpg
executable: /usr/bin/nautilus
package: nautilus-2.30.1-6.fc13
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1287948234
uid: 500

How to reproduce
1.  installed FC 13
2.  Had firefox open to a few tabs
3.  Updated computer 1 (included updates to rpm, yum, and one other basic thing)
4.  UPdated computer #2 (included 400+ updates)
5.  Was asked to log out so that programs could remain secure. clicked log out.  Screen immediately faded to black then white.
6.  Moved mouse a few minutes later and saw login prompt. Logged in.  Saw the nautilus crash, and the green man icon indicating it didn't log out like I thought it did, cause it still wants to log out.

Comment 1 pseudo64 2010-10-24 19:52:25 UTC
Created attachment 455364 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 13:42:48 UTC

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

Comment 3 Karel Klíč 2010-11-09 13:42:48 UTC
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 #587508.

Sorry for the inconvenience.