Hide Forgot
Version-Release number of selected component: Thunar-1.6.3-1.fc19 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/Thunar --daemon crash_function: thunar_shortcuts_model_set_busy executable: /usr/bin/thunar kernel: 3.10.7-200.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 thunar_shortcuts_model_set_busy at thunar-shortcuts-model.c:2114 #1 thunar_shortcuts_view_unmount_finish at thunar-shortcuts-view.c:2002 #2 thunar_device_operation_finish at thunar-device.c:274 #3 g_simple_async_result_complete at gsimpleasyncresult.c:777 #4 unmount_cb at gproxymount.c:550 #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:5339 #9 g_simple_async_result_complete at gsimpleasyncresult.c:777 Potential duplicate: bug 901903
Created attachment 789558 [details] File: backtrace
Created attachment 789559 [details] File: cgroup
Created attachment 789560 [details] File: core_backtrace
Created attachment 789561 [details] File: dso_list
Created attachment 789562 [details] File: environ
Created attachment 789563 [details] File: exploitable
Created attachment 789564 [details] File: limits
Created attachment 789565 [details] File: maps
Created attachment 789566 [details] File: open_fds
Created attachment 789567 [details] File: proc_pid_status
Created attachment 789568 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate it?
Another user experienced a similar problem: Happend while copying photos from a camera (Nikon D3100). All photos sucessfully copied. reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/bin/Thunar /home/alexander/ownCloud/zeitungit crash_function: thunar_shortcuts_model_set_busy executable: /usr/bin/thunar kernel: 3.14.4-100.fc19.x86_64 package: Thunar-1.6.3-1.fc19 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.