Version-Release number of selected component: xfdesktop-4.10.2-2.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 26628ed26-44b0-4e34-9e04-377737e89bc4 crash_function: g_hash_table_lookup_node executable: /usr/bin/xfdesktop kernel: 3.12.7-300.fc20.x86_64 runlevel: unknown type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (6 frames) #0 g_hash_table_lookup_node at ghash.c:365 #1 g_hash_table_lookup at ghash.c:1076 #2 xfdesktop_file_icon_manager_volume_changed at xfdesktop-file-icon-manager.c:2492 #6 g_signal_emit_by_name at gsignal.c:3426 #7 signal_emit_in_idle_do at gproxyvolumemonitor.c:1056 #12 gtk_main at gtkmain.c:1257
Created attachment 852352 [details] File: backtrace
Created attachment 852353 [details] File: cgroup
Created attachment 852354 [details] File: core_backtrace
Created attachment 852355 [details] File: dso_list
Created attachment 852356 [details] File: environ
Created attachment 852357 [details] File: exploitable
Created attachment 852358 [details] File: limits
Created attachment 852359 [details] File: maps
Created attachment 852360 [details] File: open_fds
Created attachment 852361 [details] File: proc_pid_status
Created attachment 852362 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate the crash?
Unfortunately not.
I got the same while unmounting a volume using Thunar. The volume is encrypted (LUKS) and resides on an LVM. I am not sure if I can replicate it each time. Actually, I see no effect besides ABRT message about xfdesktop being killed.
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.
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.