Version-Release number of selected component: nemo-2.0.8-9.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: nemo crash_function: g_type_check_instance executable: /usr/bin/nemo kernel: 3.13.8-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance at gtype.c:4084 #1 g_signal_handlers_disconnect_matched at gsignal.c:2878 #2 nemo_bookmark_disconnect_file at nemo-bookmark.c:236 #3 nemo_bookmark_finalize at nemo-bookmark.c:351 #5 g_list_foreach at glist.c:949 #6 g_list_free_full at glist.c:187 #7 nemo_window_slot_clear_back_list at nemo-window-slot.c:730 #8 nemo_window_slot_dispose at nemo-window-slot.c:214 #10 closure_invoke_notifiers at gclosure.c:285 #11 _g_closure_invoke_va at gclosure.c:846
Created attachment 884301 [details] File: backtrace
Created attachment 884302 [details] File: cgroup
Created attachment 884303 [details] File: core_backtrace
Created attachment 884304 [details] File: dso_list
Created attachment 884305 [details] File: environ
Created attachment 884306 [details] File: exploitable
Created attachment 884307 [details] File: limits
Created attachment 884308 [details] File: maps
Created attachment 884309 [details] File: open_fds
Created attachment 884310 [details] File: proc_pid_status
Created attachment 884311 [details] File: var_log_messages
Another user experienced a similar problem: I was copying files from the Nemo Download folder to a WD USB 3 2TB hard drive reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: nemo -n crash_function: g_type_check_instance executable: /usr/bin/nemo kernel: 3.14.4-200.fc20.x86_64 package: nemo-2.2.1-1.fc20 reason: nemo killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: just looking in folders with Nemo reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: nemo -n crash_function: g_type_check_instance executable: /usr/bin/nemo kernel: 3.14.9-200.fc20.x86_64 package: nemo-2.2.2-4.fc20 reason: nemo 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.