Red Hat Bugzilla – Bug 1011699
[abrt] nautilus-3.9.92-1.fc20: _g_log_abort: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Last modified: 2015-06-29 08:27:10 EDT
Description of problem:
Steps to reproduce:
1. Connect to remote server
2. Bookmark it
3. Open bookmarks (C-b)
4. disconnect from remote server
Version-Release number of selected component:
cmdline: nautilus --new-window
Thread no. 1 (10 frames)
#2 _g_log_abort at gmessages.c:255
#5 nautilus_window_get_slots at nautilus-window.c:2094
#6 update_dbus_opened_locations at nautilus-application.c:1659
#7 ffi_call_unix64 at ../src/x86/unix64.S:76
#8 ffi_call at ../src/x86/ffi64.c:522
#9 g_cclosure_marshal_generic at gclosure.c:1454
#13 g_signal_emit_by_name at gsignal.c:3426
#14 nautilus_window_slot_emit_location_change at nautilus-window-slot.c:2055
#15 nautilus_window_slot_set_location at nautilus-window-slot.c:996
#16 nautilus_window_slot_update_for_new_location at nautilus-window-slot.c:2143
Created attachment 802476 [details]
Created attachment 802477 [details]
Created attachment 802478 [details]
Created attachment 802479 [details]
Created attachment 802480 [details]
Created attachment 802481 [details]
Created attachment 802482 [details]
Created attachment 802483 [details]
Created attachment 802484 [details]
Created attachment 802485 [details]
Problem still exists in nautilus-3.10.0-1.fc20.x86_64
Had same result (nautilus crash - abrt pointed me here) after trying to open ssh server saved in bookmarks from F17 and F19. Second try (after restarting "Files") was successful, Third try (after disconnecting from server) crashed Nautilus again, fourth as well. After restarting Nautilus again (#5) the server was already in bookmarks in left column, connected.
Even simpler STR for this crash, no remote server needed:
1. Open a Nautilus window
2. Open Bookmarks (Ctrl+B)
3. Double click any already existing bookmark in the list.
This happens on i686 as well.
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'
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
Thank you for reporting this bug and we are sorry it could not be fixed.