Red Hat Bugzilla – Bug 967237
[abrt] Thunar-1.6.3-1.fc19: thunar_shortcuts_model_set_busy: Process /usr/bin/thunar was killed by signal 11 (SIGSEGV)
Last modified: 2015-03-20 08:53:52 EDT
Description of problem:
Attempting to eject a 16GB usb mass storage device.
Version-Release number of selected component:
cmdline: /usr/bin/Thunar --daemon
runlevel: N 5
Thread no. 1 (10 frames)
#0 thunar_shortcuts_model_set_busy at thunar-shortcuts-model.c:2114
#1 thunar_shortcuts_view_eject_finish at thunar-shortcuts-view.c:1860
#2 thunar_device_operation_finish at thunar-device.c:274
#3 g_simple_async_result_complete at gsimpleasyncresult.c:777
#4 eject_cb at gproxydrive.c:599
#5 g_simple_async_result_complete at gsimpleasyncresult.c:777
#6 reply_cb at gdbusproxy.c:2632
#7 g_simple_async_result_complete at gsimpleasyncresult.c:777
#8 g_dbus_connection_call_done at gdbusconnection.c:5333
#9 g_simple_async_result_complete at gsimpleasyncresult.c:777
Potential duplicate: bug 915430
Created attachment 753180 [details]
Created attachment 753181 [details]
Created attachment 753182 [details]
Created attachment 753183 [details]
Created attachment 753184 [details]
Created attachment 753185 [details]
Created attachment 753186 [details]
Created attachment 753187 [details]
Created attachment 753188 [details]
Created attachment 753189 [details]
Can you duplicate this? Or was it a one time thing?
I have seen it more than once, but it's not repeatable. Anything specific I can do/log/capture next time it happens?
Well, if you can figure out a series of steps that always causes the crash that would be great.
Sure :) I guess what I meant was I could run in gdb till it happens again or something similar.
If you like, not sure that will get too much more info in the end tho. ;)
Another user experienced a similar problem:
Unmounting an SMB share.
cmdline: Thunar --daemon
reason: thunar killed by SIGSEGV
runlevel: N 3
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.