Bug 1097127

Summary: [abrt] Thunar: g_thread_abort(): thunar killed by SIGABRT
Product: [Fedora] Fedora Reporter: darton <temp-2009-09-09>
Component: ThunarAssignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: christoph.wickert, gmconsult, kevin, nonamedotc, pertusus
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/61abddcdf04e6f69afd2a3d05e82009abc326a9b
Whiteboard: abrt_hash:2e523d8b3c5d831818fc57b154abe18c20dfcbe8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:36:01 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 darton 2014-05-13 08:12:04 UTC 
Description of problem:
ABRT message just popped up while I was writing an email. No Thunar windows were present on the active workspace. It only happened once.

Version-Release number of selected component:
Thunar-1.6.3-2.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        Thunar --daemon
crash_function: g_thread_abort
executable:     /usr/bin/thunar
kernel:         3.14.3-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            500

Truncated backtrace:
Thread no. 1 (6 frames)
 #2 g_thread_abort at gthread-posix.c:79
 #3 g_mutex_lock at gthread-posix.c:214
 #4 thunar_thumbnailer_queue_async_reply at thunar-thumbnailer.c:617
 #5 thunar_thumbnailer_proxy_queue_async_callback at ../thunar/thunar-thumbnailer-proxy.h:44
 #6 complete_pending_call_and_unlock at dbus-connection.c:2314
 #13 gtk_main at gtkmain.c:1257

Potential duplicate: bug 910426
Comment 1 darton 2014-05-13 08:12:12 UTC 
Created attachment 895037 [details]
File: backtrace
Comment 2 darton 2014-05-13 08:12:14 UTC 
Created attachment 895038 [details]
File: cgroup
Comment 3 darton 2014-05-13 08:12:18 UTC 
Created attachment 895039 [details]
File: core_backtrace
Comment 4 darton 2014-05-13 08:12:20 UTC 
Created attachment 895040 [details]
File: dso_list
Comment 5 darton 2014-05-13 08:12:22 UTC 
Created attachment 895041 [details]
File: environ
Comment 6 darton 2014-05-13 08:12:24 UTC 
Created attachment 895042 [details]
File: limits
Comment 7 darton 2014-05-13 08:12:27 UTC 
Created attachment 895043 [details]
File: maps
Comment 8 darton 2014-05-13 08:12:29 UTC 
Created attachment 895044 [details]
File: open_fds
Comment 9 darton 2014-05-13 08:12:32 UTC 
Created attachment 895045 [details]
File: proc_pid_status
Comment 10 darton 2014-05-13 08:12:34 UTC 
Created attachment 895046 [details]
File: var_log_messages
Comment 11 Fedora End Of Life 2015-05-29 11:50:06 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.
Comment 12 Fedora End Of Life 2015-06-29 20:36:01 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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