Bug 1171410

Summary: [abrt] rawstudio: g_thread_abort(): rawstudio killed by SIGABRT
Product: [Fedora] Fedora Reporter: donjoe <pbloigu>
Component: rawstudioAssignee: Gianluca Sforna <giallu>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: giallu, sergio
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4731c50cb0f643efe8624f4d95b547c8e98f05b3
Whiteboard: abrt_hash:17128479a899b8b0a217537b334109038c3638ab
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-25 16:57:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description donjoe 2014-12-06 16:32:54 UTC
Description of problem:
Just tried to open the application. The main window flashed and then it died...

Version-Release number of selected component:
rawstudio-2.0-12.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        rawstudio
crash_function: g_thread_abort
executable:     /usr/bin/rawstudio
kernel:         3.17.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_thread_abort at gthread-posix.c:79
 #3 g_mutex_lock at gthread-posix.c:214
 #4 g_source_destroy_internal at gmain.c:1210
 #5 g_source_destroy at gmain.c:1257
 #6 timeout_handler_destroy_source at dbus-gmain.c:309
 #7 _dbus_timeout_list_remove_timeout at dbus-timeout.c:347
 #8 protected_change_timeout at dbus-connection.c:848
 #9 _dbus_connection_remove_timeout_unlocked at dbus-connection.c:895
 #10 _dbus_connection_queue_received_message_link at dbus-connection.c:509
 #11 _dbus_transport_queue_messages at dbus-transport.c:1157

Comment 1 donjoe 2014-12-06 16:33:00 UTC
Created attachment 965436 [details]
File: backtrace

Comment 2 donjoe 2014-12-06 16:33:02 UTC
Created attachment 965437 [details]
File: cgroup

Comment 3 donjoe 2014-12-06 16:33:05 UTC
Created attachment 965438 [details]
File: core_backtrace

Comment 4 donjoe 2014-12-06 16:33:08 UTC
Created attachment 965439 [details]
File: dso_list

Comment 5 donjoe 2014-12-06 16:33:10 UTC
Created attachment 965440 [details]
File: environ

Comment 6 donjoe 2014-12-06 16:33:12 UTC
Created attachment 965441 [details]
File: limits

Comment 7 donjoe 2014-12-06 16:33:15 UTC
Created attachment 965442 [details]
File: maps

Comment 8 donjoe 2014-12-06 16:33:18 UTC
Created attachment 965443 [details]
File: open_fds

Comment 9 donjoe 2014-12-06 16:33:20 UTC
Created attachment 965444 [details]
File: proc_pid_status

Comment 10 donjoe 2014-12-06 16:33:22 UTC
Created attachment 965445 [details]
File: var_log_messages

Comment 11 Sergio Basto 2015-02-25 16:57:41 UTC
looks a dbus problem , lets pretend that is a duplicated .

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