Bug 627047 - [abrt] nautilus-2.30.1-6.fc13: raise: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Summary: [abrt] nautilus-2.30.1-6.fc13: raise: Process /usr/bin/nautilus was killed by...
Status: CLOSED DUPLICATE of bug 593962
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9f7b2ba47d6ef30a6c156221546...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-24 23:20 UTC by nomnex
Modified: 2015-03-03 22:52 UTC (History)
4 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-11-08 18:17:44 UTC


Attachments (Terms of Use)
File: backtrace (17.81 KB, text/plain)
2010-08-24 23:20 UTC, nomnex
no flags Details

Description nomnex 2010-08-24 23:20:00 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: nautilus
comment: Doing some directory management. I opened a extra pane (F3). When I selected the the extra pane by right clicking, Nautilus crashed. It happens not frequently but quite regularily on my system.
component: nautilus
crash_function: raise
executable: /usr/bin/nautilus
kernel: 2.6.33.8-149.fc13.i686
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: 1282691579
uid: 500

How to reproduce
-----
1. Opening extra pane (F3)
2. Selecting the pane by mouse clicking (Why is there not a keyboard shortcut to do this?)
3. Nautilus crashed

Comment 1 nomnex 2010-08-24 23:20:02 UTC
Created an attachment (id=440792)
File: backtrace

Comment 2 Karel Klíč 2010-11-08 18:17:44 UTC

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

Comment 3 Karel Klíč 2010-11-08 18:17:44 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 #593962.

Sorry for the inconvenience.


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