Description of problem: It just finished ejecting a memory stick I had mounted and then almost immediately (maybe before it finished) I closed the window Version-Release number of selected component: Thunar-1.6.3-2.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: magazine_cache_push_magazine executable: /usr/bin/thunar kernel: 3.12.7-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_cache_push_magazine at gslice.c:706 #1 thread_memory_magazine2_unload at gslice.c:815 #2 g_slice_free1 at gslice.c:1106 #3 g_type_free_instance at gtype.c:1938 #4 gtk_menu_shell_forall at gtkmenushell.c:1113 #5 gtk_container_destroy at gtkcontainer.c:1073 #10 gtk_object_dispose at gtkobject.c:421 #12 gtk_menu_item_destroy at gtkmenuitem.c:545 #17 gtk_object_dispose at gtkobject.c:421 #19 gtk_menu_shell_forall at gtkmenushell.c:1113
Created attachment 855498 [details] File: backtrace
Created attachment 855499 [details] File: cgroup
Created attachment 855500 [details] File: core_backtrace
Created attachment 855501 [details] File: dso_list
Created attachment 855502 [details] File: environ
Created attachment 855503 [details] File: exploitable
Created attachment 855504 [details] File: limits
Created attachment 855505 [details] File: maps
Created attachment 855506 [details] File: open_fds
Created attachment 855507 [details] File: proc_pid_status
Created attachment 855508 [details] File: var_log_messages
I would gladly provide any other information you may need.
Another user experienced a similar problem: Closed Thunar window. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: magazine_cache_push_magazine executable: /usr/bin/thunar kernel: 3.14.4-200.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Thunar-1.6.3-2.fc20.x86_64 libreport-2.2.3-2.fc20.x86_64 xfwm4-4.11.2-1.fc20.x86_64 libxfcegui4-4.10.0-5.fc20.x86_64 libxfce4util-4.11.0-1.fc20.x86_64 libxfce4ui-4.11.1-1.fc20.x86_64 Is this regression due to xfce 4.11? Maybe duplication of bug #013562, as Abrt says.
Abrt suggests a duplication of bug #1013562.
gtk2-2.24.22-2.fc20.x86_64 I'll update to 2.24.24-2 as suggested in bug # 1013562 and come back if this bug is still reproducible.
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.