Description of problem: had an smb share mounted (from an openmediavault server), was trying to unmount it by clicking the eject icon in the file system browser. Version-Release number of selected component: nemo-2.2.0-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: nemo -n crash_function: _g_log_abort executable: /usr/bin/nemo kernel: 3.14.2-200.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 nemo_bookmark_connect_file at nemo-bookmark.c:256 #6 nemo_bookmark_get_location at nemo-bookmark.c:565 #7 set_displayed_location at nemo-window-manage-views.c:115 #8 update_for_new_location at nemo-window-manage-views.c:1379 #9 location_has_really_changed at nemo-window-manage-views.c:1210 #10 nemo_window_report_load_underway at nemo-window-manage-views.c:1087 #11 finish_loading at nemo-view.c:10123 #12 ready_callback_call at nemo-directory-async.c:1287 #13 call_ready_callbacks_at_idle at nemo-directory-async.c:1857
Created attachment 894208 [details] File: backtrace
Created attachment 894209 [details] File: cgroup
Created attachment 894210 [details] File: core_backtrace
Created attachment 894211 [details] File: dso_list
Created attachment 894212 [details] File: environ
Created attachment 894213 [details] File: limits
Created attachment 894214 [details] File: maps
Created attachment 894215 [details] File: open_fds
Created attachment 894216 [details] File: proc_pid_status
Created attachment 894217 [details] File: var_log_messages
Another user experienced a similar problem: Mounting and unmounting an .iso image that may be corrupted. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: nemo -n crash_function: _g_log_abort executable: /usr/bin/nemo kernel: 3.14.7-200.fc20.x86_64 package: nemo-2.2.2-1.fc20 reason: nemo 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.