Bug 678218 - [abrt] rawtherapee-3.0-0.27.a1.fc14: Process /usr/bin/rt was killed by signal 6 (SIGABRT)
Summary: [abrt] rawtherapee-3.0-0.27.a1.fc14: Process /usr/bin/rt was killed by signal...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rawtherapee
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thibault North
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a24420a97babec7950fd211bc35...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-17 07:02 UTC by ryo fujita
Modified: 2011-03-20 17:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-20 17:41:14 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (8.69 KB, text/plain)
2011-02-17 07:02 UTC, ryo fujita 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description ryo fujita 2011-02-17 07:02:56 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: rt '/home/rio/\xe3\x83\x87\xe3\x82\xb9\xe3\x82\xaf\xe3\x83\x88\xe3\x83\x83\xe3\x83\x97/100EOS7D/IMG_5821.CR2'
component: rawtherapee
crash_function: Glib::ConvertError::throw_func
executable: /usr/bin/rt
kernel: 2.6.35.10-74.fc14.x86_64
package: rawtherapee-3.0-0.27.a1.fc14
rating: 4
reason: Process /usr/bin/rt was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297925888
uid: 500

How to reproduce
-----
1. Executed 'rt' command from the context menu in Nautilus
2.
3.
Comment 1 ryo fujita 2011-02-17 07:02:59 UTC 
Created attachment 479273 [details]
File: backtrace
Comment 2 Evgenij Kutyavin 2011-03-20 05:15:39 UTC 
Package: rawtherapee-3.0-0.27.a1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Using Shotwell and Rawtherapee/
2.
3.
Comment 3 Thibault North 2011-03-20 17:41:14 UTC 
It seems that currently rawtherapee won't directly load your file given as argument. However, it should not crash.
Next release does not have that bug (at least for me). Please reopen if you have problems again.
Thanks,
Note You need to log in before you can comment on or make changes to this bug.