Bug 614896

Summary: [abrt] crash in nautilus-2.30.1-3.fc13: raise: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Mark <fc_mark>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:d2e8c22fda7fd4384b0c95e48cf9c214972c6aa5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-15 14:44:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Mark 2010-07-15 14:08:16 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: nautilus --sm-client-id 10df340f461b0885127626550511088100000019010042 --sm-client-state-file /home/mmurayam/.config/session-state/nautilus-1279199489.state
component: nautilus
crash_function: raise
executable: /usr/bin/nautilus
global_uuid: d2e8c22fda7fd4384b0c95e48cf9c214972c6aa5
kernel: 2.6.33.6-147.fc13.x86_64
package: nautilus-2.30.1-3.fc13
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Started computer.
2. Logged into Gnome desktop.
3. Received a notification that Nautilus crashed.
Comment 1 Mark 2010-07-15 14:08:19 UTC 
Created attachment 432093 [details]
File: backtrace
Comment 2 Mark 2010-07-15 14:44:27 UTC 
Closing this ticket.  I rebooted and that cleared the issue.  For some reason Nautilus was hung on the first start up.