Hide Forgot
Version-Release number of selected component: Thunar-1.6.3-2.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/Thunar crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.12.5-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 5000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:545 #1 thread_memory_magazine1_alloc at gslice.c:848 #2 g_slice_alloc at gslice.c:1007 #3 g_string_sized_new at gstring.c:126 #4 g_string_new at gstring.c:152 #5 g_utf8_casefold at guniprop.c:1196 #6 thunar_file_info_reload at thunar-file.c:944 #7 thunar_file_load at thunar-file.c:1060 #8 thunar_file_reload at thunar-file.c:3744 #9 thunar_folder_monitor at thunar-folder.c:749
Created attachment 838568 [details] File: backtrace
Created attachment 838569 [details] File: cgroup
Created attachment 838570 [details] File: core_backtrace
Created attachment 838571 [details] File: dso_list
Created attachment 838572 [details] File: environ
Created attachment 838573 [details] File: exploitable
Created attachment 838574 [details] File: limits
Created attachment 838575 [details] File: maps
Created attachment 838576 [details] File: open_fds
Created attachment 838577 [details] File: proc_pid_status
Created attachment 838578 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate it?
Nothing in Thunar. I think I was just browsing the web. If I had a better idea I would have included it in the report.
Another user experienced a similar problem: Thunar wasn't even in the foreground when this happened. reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: thunar crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.12.8-300.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 500
Another user experienced a similar problem: Eject external hdd or usb sctick reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/Thunar --daemon crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.13.6-200.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Thunar had been open for a while, and I was away from computer when crash happened. reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/Thunar crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.13.6-200.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Try to copy some dirs to an upper dir, same tree reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/Thunar crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.17.8-200.fc20.x86_64 package: Thunar-1.6.4-1.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Thunar unpredictably crashes while a copy of a file with [Ctrl]_[C] – [Ctl]_[V] is made. The crash can happened when you try to copy a file from one Thunar window to another as well. Thunar version: Thunar-1.6.4-1.fc20.x86_64 Downgrade to the previous version (1.6.3-2) solves the issue.
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.