Bug 614897 - [abrt] crash in nautilus-2.30.1-3.fc13: raise: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in nautilus-2.30.1-3.fc13: raise: Process /usr/bin/nautilus was ...
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:71f9b1939ed95df7d7a77bc7618...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-15 14:09 UTC by Mark
Modified: 2015-03-03 22:51 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2010-07-15 14:44:09 UTC

Attachments (Terms of Use)
File: backtrace (17.73 KB, text/plain)
2010-07-15 14:09 UTC, Mark
no flags Details

Description Mark 2010-07-15 14:09:20 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
comment: This was a second crash of Nautilus.  The first one happened two minutes earlier when I logged into Gnome.
component: nautilus
crash_function: raise
executable: /usr/bin/nautilus
global_uuid: 71f9b1939ed95df7d7a77bc76187197364b0820f
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)

Comment 1 Mark 2010-07-15 14:09:22 UTC
Created attachment 432094 [details]
File: backtrace

Comment 2 Mark 2010-07-15 14:44:09 UTC
Closing this ticket.  I rebooted and that cleared the issue.  For some reason Nautilus was hung on the first start up.

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