Red Hat Bugzilla – Bug 1006277
[abrt] nautilus-3.8.2-1.fc19: g_assertion_message: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Last modified: 2015-02-17 12:07:58 EST
Description of problem:
I wanted to open a folder to my server via smb, then it crashed.
My server was under heavy load, maybe this was the issue :-)
Version-Release number of selected component:
cmdline: nautilus --new-window
runlevel: N 5
Thread no. 1 (10 frames)
#2 g_assertion_message at /lib64/libglib-2.0.so.0
#3 g_assertion_message_expr at /lib64/libglib-2.0.so.0
#4 nautilus_bookmark_connect_file at nautilus-bookmark.c:350
#5 nautilus_bookmark_constructed at nautilus-bookmark.c:549
#6 g_object_newv at /lib64/libgobject-2.0.so.0
#7 g_object_new_valist at /lib64/libgobject-2.0.so.0
#8 g_object_new at /lib64/libgobject-2.0.so.0
#9 nautilus_bookmark_new at nautilus-bookmark.c:756
#10 nautilus_window_slot_update_bookmark at nautilus-window-slot.c:1848
#11 nautilus_window_slot_update_for_new_location at nautilus-window-slot.c:2133
Created attachment 795951 [details]
Created attachment 795952 [details]
Created attachment 795953 [details]
Created attachment 795954 [details]
Created attachment 795955 [details]
Created attachment 795956 [details]
Created attachment 795957 [details]
Created attachment 795958 [details]
Created attachment 795959 [details]
Created attachment 795960 [details]
I'm getting this always, when my SFTP got disconnected..
Is this a duplicate of bug 960444 ? The failure-mode reports seem the same, and abrt seems to think so. It showed me both URLs when informing me that this problem had already been reported.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.