Bug 622215 - [abrt] crash in nautilus-2.30.1-6.fc13: raise: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in nautilus-2.30.1-6.fc13: raise: Process /usr/bin/nautilus was ...
Keywords:
Status: CLOSED DUPLICATE of bug 627056
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:6abf78f5fad9f3668f12c8557ac...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-08 06:49 UTC by Robert Hoekstra
Modified: 2015-03-03 22:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 13:46:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (30.60 KB, text/plain)
2010-08-08 06:49 UTC, Robert Hoekstra
no flags Details

Description Robert Hoekstra 2010-08-08 06:49:21 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: nautilus
comment: See the steps.. reproducability is not confirmed
component: nautilus
crash_function: raise
executable: /usr/bin/nautilus
global_uuid: 6abf78f5fad9f3668f12c8557acfb7a225b3ab9f
kernel: 2.6.33.6-147.2.4.fc13.i686.PAE
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)

How to reproduce
-----
1. I connected the digital camera (Canon 400D)
2. Closed (forcibly) the nautilus because I couldn't read the folder
3. started nautilus by double clicking the camera icon on the desktop
4. pressed F3 to get a new pane.

Comment 1 Robert Hoekstra 2010-08-08 06:49:23 UTC
Created attachment 437412 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 13:46:12 UTC

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

Comment 3 Karel Klíč 2010-11-09 13:46:12 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 #627056.

Sorry for the inconvenience.


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