Hide Forgot
Version-Release number of selected component: nautilus-3.10.1-2.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 3 cmdline: nautilus --new-window '/home/gcell/\xe4\xb8\x8b\xe8\xbd\xbd' crash_function: magazine_chain_pop_head executable: /usr/bin/nautilus kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 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_slice_alloc0 at gslice.c:1042 #4 g_type_create_instance at gtype.c:1850 #5 g_object_new_internal at gobject.c:1746 #8 _g_local_file_new at glocalfile.c:304 #9 g_local_file_get_parent at glocalfile.c:483 #10 nautilus_file_get_internal at nautilus-file.c:660 #11 nautilus_file_get_existing at nautilus-file.c:716 Potential duplicate: bug 718677
Created attachment 839726 [details] File: backtrace
Created attachment 839727 [details] File: cgroup
Created attachment 839728 [details] File: core_backtrace
Created attachment 839729 [details] File: dso_list
Created attachment 839730 [details] File: environ
Created attachment 839731 [details] File: limits
Created attachment 839732 [details] File: maps
Created attachment 839733 [details] File: open_fds
Created attachment 839734 [details] File: proc_pid_status
Created attachment 839735 [details] File: var_log_messages
Created attachment 839736 [details] File: exploitable
Another user experienced a similar problem: Not sure how to reproduce this; all I know is that I was accessing a USB HDD and was browsing heavily in the same window for a long time... reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: nautilus --new-window /home/ekaljuk/Pictures crash_function: magazine_chain_pop_head executable: /usr/bin/nautilus kernel: 3.12.6-300.fc20.x86_64 package: nautilus-3.10.1-2.fc20 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Created attachment 844030 [details] File: backtrace
Another user experienced a similar problem: 1. enter S1 state (from gnome-shell). Mouse pointer disappeared upon wake. 2. systemctl rescue 3. ^D reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: magazine_chain_pop_head executable: /usr/bin/nautilus kernel: 3.12.9-301.fc20.x86_64 package: nautilus-3.10.1-2.fc20 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Nautilus was not interactively used during the crash. Files were updated inside a Folder monitored by Dropbox reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --no-default-window crash_function: magazine_chain_pop_head executable: /usr/bin/nautilus kernel: 3.15.7-200.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I was trying to access a webpage in Firefox when this happened. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: nautilus --new-window '/home/omega13a/Downloads/Bedknobs and Broomsticks (1971) [1080p]' crash_function: magazine_chain_pop_head executable: /usr/bin/nautilus kernel: 3.16.3-200.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.