Bug 625840 - [abrt] shotwell-0.5.2-1.fc13: raise: Process /usr/bin/shotwell was killed by signal 6 (SIGABRT)
Summary: [abrt] shotwell-0.5.2-1.fc13: raise: Process /usr/bin/shotwell was killed by ...
Alias: None
Product: Fedora
Classification: Fedora
Component: shotwell (Show other bugs)
(Show other bugs)
Version: 13
Hardware: i686 Linux
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:57ce7a6ef74e2f6efffec4fabc0...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-20 15:17 UTC by WS
Modified: 2011-06-28 14:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-28 14:20:24 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (863 bytes, text/plain)
2010-08-20 15:18 UTC, WS
no flags Details

Description WS 2010-08-20 15:17:59 UTC
abrt version: 1.1.13
architecture: i686
cmdline: shotwell '/media/Art/Painting/Photo Studies/Photo studies for possible paintings - 109.jpg'
component: shotwell
crash_function: raise
executable: /usr/bin/shotwell
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)
time: 1282309853
uid: 501

[New Thread 3645]
warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/b0/92e943ad63f83804af87c5bc62b0c1a9610a8d.debug": separate debug info file has no debug info
Core was generated by `shotwell /media/Art/Painting/Photo Studies/Photo studies for possible paintings'.
Program terminated with signal 6, Aborted.
#0  0x00ea1416 in __kernel_vsyscall ()

Thread 1 (Thread 3645):
#0  0x00ea1416 in __kernel_vsyscall ()
No symbol table info available.
#1  0x00a5fd11 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
        resultvar = <value optimized out>
        resultvar = <value optimized out>
        pid = 12308468
        selftid = 3645
#2  0x00a615ea in abort () at abort.c:92
        save_stage = 2
        act = {__sigaction_handler = {sa_handler = 0xbf988254, 
            sa_sigaction = 0xbf988254}
Timeout exceeded: 60 second, killing gdb

How to reproduce
1.Plug in external hard drive
2.Open selected photo's from Art partition [hfs+]

Comment 1 WS 2010-08-20 15:18:01 UTC
Created an attachment (id=439970)
File: backtrace

Comment 2 Bug Zapper 2011-06-01 11:01:29 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 3 Bug Zapper 2011-06-28 14:20:24 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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