Description of problem: I don't know what happened. I was using Nautilus to look for a file and nautilus crashed while doing so. I don't even recall using the CD/DVD creator. Version-Release number of selected component: nautilus-3.8.1-1.fc19 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/nautilus --no-default-window crash_function: nautilus_bookmark_connect_file executable: /usr/bin/nautilus kernel: 3.9.0-301.fc19.x86_64 runlevel: N 5 uid: 1000 var_log_messages: May 6 23:31:23 Illuminatus-1 abrt[4755]: Saved core dump of pid 2171 (/usr/bin/nautilus) to /var/tmp/abrt/ccpp-2013-05-06-23:31:22-2171 (112062464 bytes) Truncated backtrace: Thread no. 1 (10 frames) #4 nautilus_bookmark_connect_file at nautilus-bookmark.c:350 #5 nautilus_bookmark_constructed at nautilus-bookmark.c:549 #7 g_object_new_valist at gobject.c:1836 #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 #12 location_has_really_changed at nautilus-window-slot.c:2389 #13 view_begin_loading_cb at nautilus-window-slot.c:2310 #18 finish_loading at nautilus-view.c:9144 #19 finish_loading_if_all_metadata_loaded at nautilus-view.c:9203
Created attachment 744569 [details] File: backtrace
Created attachment 744570 [details] File: cgroup
Created attachment 744571 [details] File: core_backtrace
Created attachment 744572 [details] File: dso_list
Created attachment 744573 [details] File: environ
Created attachment 744574 [details] File: limits
Created attachment 744575 [details] File: maps
Created attachment 744576 [details] File: open_fds
Created attachment 744577 [details] File: proc_pid_status
Created attachment 744578 [details] File: xsession_errors
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Just got this while using a bookmarked SSH connection in Nautilus.
Random crash when adding paired Bluetooth device "obex://[00:00:00:00:00:00]/" in "Enter Location..." dialog. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: nautilus crash_function: nautilus_bookmark_connect_file executable: /usr/bin/nautilus kernel: 3.9.9-302.fc19.x86_64 package: nautilus-3.8.2-1.fc19 reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000 xsession_errors:
I get this each time I unmount windows (samba) share from Files
browsing an sftp server: initially, home directory was shown. upper location did not reflrect actual path. instead, it said I am on root. after opening symlink directory in home, real path was shown, then i changed to root. after doing this second time, it crashed at last step reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: nautilus_bookmark_connect_file executable: /usr/bin/nautilus kernel: 3.10.5-201.fc19.x86_64 package: nautilus-3.8.2-1.fc19 reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
I was using nautilus to access my digital camera (Canon Powershot S100V). The image transfer failed. Then after I clicked the eject icon, the nautilus window disappeared, and bailed out this notification. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: nautilus --no-desktop crash_function: nautilus_bookmark_connect_file executable: /usr/bin/nautilus kernel: 3.9.5-301.fc19.x86_64 package: nautilus-3.8.2-1.fc19 reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
Same error when I unmounted a network share in Nautilus after copying files across a network.
Загрузка файла в google chrome reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: nautilus_bookmark_connect_file executable: /usr/bin/nautilus kernel: 3.10.10-200.fc19.i686 package: nautilus-3.8.2-1.fc19 reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
I saw this crash too. Filed upstream at: https://bugzilla.gnome.org/show_bug.cgi?id=708282
Got today.
I do not see this problem anymore. nautilus-3.11.92-1.fc20.x86_64 I wousay, this report can be closed.
I do not see this problem anymore. nautilus-3.11.92-1.fc20.x86_64 I would say, this report can be closed.
Another user experienced a similar problem: sorry, i don't know exactly perhaps it terminates, if connected with smb://<server> reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: nautilus_bookmark_connect_file executable: /usr/bin/nautilus kernel: 3.14.15-100.fc19.x86_64 package: nautilus-3.8.2-2.fc19 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.