Hide Forgot
Version-Release number of selected component: nautilus-3.10.1-1.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.11.7-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 _g_log_abort at gmessages.c:255 #5 icon_rename_ended_cb at nautilus-canvas-view.c:1571 #6 ffi_call_unix64 at ../src/x86/unix64.S:76 #7 ffi_call at ../src/x86/ffi64.c:522 #8 g_cclosure_marshal_generic at gclosure.c:1454 #13 end_renaming_mode at nautilus-canvas-container.c:7467 #14 icon_toggle_selected at nautilus-canvas-container.c:442 #15 icon_set_selected at nautilus-canvas-container.c:486 #16 select_one_unselect_others at nautilus-canvas-container.c:2078 #17 unselect_all at nautilus-canvas-container.c:2091
Created attachment 822832 [details] File: backtrace
Created attachment 822833 [details] File: cgroup
Created attachment 822834 [details] File: core_backtrace
Created attachment 822835 [details] File: dso_list
Created attachment 822836 [details] File: environ
Created attachment 822837 [details] File: limits
Created attachment 822838 [details] File: maps
Created attachment 822839 [details] File: open_fds
Created attachment 822840 [details] File: proc_pid_status
Created attachment 822841 [details] File: var_log_messages
Another user experienced a similar problem: rename an folder on an smb share reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.15.8-200.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Crash while copying/pasting within Nautilus reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: nautilus crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.15.10-201.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Rename an folder on an smb share reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.16.3-200.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I was trying to copy some files from one window to another. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: nautilus --new-window /home/omega13a/.local/share/celestia/extras/mine crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.19.5-100.fc20.x86_64 package: nautilus-3.10.1-4.fc20 reason: nautilus killed by SIGABRT 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.