Bug 605618 - [abrt] crash in shotwell-0.5.2-1.fc13: raise: Process /usr/bin/shotwell was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in shotwell-0.5.2-1.fc13: raise: Process /usr/bin/shotwell was k...
Keywords:
Status: CLOSED DUPLICATE of bug 585676
Alias: None
Product: Fedora
Classification: Fedora
Component: shotwell
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:32f6460a483522d7dc3c4e1ea44...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-18 12:22 UTC by Xion Luhnis
Modified: 2010-11-09 15:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 15:16:27 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (31.47 KB, text/plain)
2010-06-18 12:22 UTC, Xion Luhnis 		no flags Details
View All

Description Xion Luhnis 2010-06-18 12:22:53 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: shotwell file:///media/6261-3336
comment: Crashed before being able to see any photo
component: shotwell
crash_function: raise
executable: /usr/bin/shotwell
global_uuid: 32f6460a483522d7dc3c4e1ea44b17a5bd4ed5f0
kernel: 2.6.33.5-124.fc13.i686.PAE
package: shotwell-0.5.2-1.fc13
rating: 4
reason: Process /usr/bin/shotwell was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Plug in my phone (htc tattoo)
2. As well as my camera sd card
3. Tried to navigate them using shotwell
Comment 1 Xion Luhnis 2010-06-18 12:22:55 UTC 
Created attachment 425098 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 15:16:27 UTC 

*** This bug has been marked as a duplicate of bug 585676 ***
Comment 3 Karel Klíč 2010-11-09 15:16:27 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 #585676.

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