Description of problem: Tried to unmount a SMB share by clicking the "Unmount" button in the left panel. 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 nautilus_bookmark_connect_file at nautilus-bookmark.c:350 #6 nautilus_bookmark_constructed at nautilus-bookmark.c:549 #7 g_object_new_internal at gobject.c:1785 #8 g_object_new_valist at gobject.c:2002 #10 nautilus_bookmark_new at nautilus-bookmark.c:756 #11 nautilus_window_slot_update_bookmark at nautilus-window-slot.c:1841 #12 nautilus_window_slot_update_for_new_location at nautilus-window-slot.c:2126 #13 location_has_really_changed at nautilus-window-slot.c:2382 #14 view_begin_loading_cb at nautilus-window-slot.c:2303 Potential duplicate: bug 999504
Created attachment 823131 [details] File: backtrace
Created attachment 823132 [details] File: cgroup
Created attachment 823133 [details] File: core_backtrace
Created attachment 823134 [details] File: dso_list
Created attachment 823135 [details] File: environ
Created attachment 823136 [details] File: limits
Created attachment 823137 [details] File: maps
Created attachment 823138 [details] File: open_fds
Created attachment 823139 [details] File: proc_pid_status
Created attachment 823140 [details] File: var_log_messages
I believe I am getting the same problem however I tried to unmount a FTPS volume. This actually didn't occur when I clicked the unmount buttons but when I tried to reconnect via "Conntact to server" and then clicking connect. abrt believes it's the same bug, I'm getting the same kill signal 6.
Another user experienced a similar problem: Open smb://127.0.0.1 reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.12.5-302.fc20.x86_64 package: nautilus-3.10.1-2.fc20 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1001
Replace Fedora 20 with Fedora 19, or Fedora 18. Gnome is perpetually broken when it comes to unmounting a GVFS mount. @Matthias Clasen, could a few cycles be spared to actually fix this?
Another user experienced a similar problem: Just closed nautilus. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.12.5-302.fc20.i686+PAE package: nautilus-3.10.1-2.fc20 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 935800001
Another user experienced a similar problem: Tried to access a CIFS share that was mounted before reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.12.8-300.fc20.x86_64 package: nautilus-3.10.1-2.fc20 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
open sftp with nautilus. Hibernate the computer. Resume. Oops nautilus crashed. Abrt thinks it's the same bug.
I had opened FTP server connection, then just left it opened for few minutes. After connection timeout i tried to connect once again and then nautilus crashed.
Mounting Android phone via USB.
Filed upstream.
(In reply to Milan Bouchet-Valat from comment #19) > Filed upstream. upstream fixed this bug a few days ago in https://bugzilla.gnome.org/show_bug.cgi?id=708282 . As this is a very annoying one-line fix could we add a backport of this to Fedora's nautilus package?
nautilus-3.10.1-4.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/nautilus-3.10.1-4.fc20
nautilus-3.10.1-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
I just had this happen again with nautilus-3.10.1-4.fc20. It was related to SMB browsing and shares.
*** Bug 1120645 has been marked as a duplicate of this bug. ***
I'm also still seeing this on nautilus-3.10.1-4.fc20, with FTP bookmarks.
This is still occurring for me as well. (nautilus-3.10.1-4.fc20)
Happens for me, too, in nautilus-3.10.1-4.fc20.x86_64. I would LOVE to use SFTP under Nautilus, if only this feature was usable. Once I connect and use it for some time, the window turns blank: no files are being shown. All I can do is disconnect and reconnect. So, I right-click on the connection alias and select disconnect, then click on the bookmark, AND IT CRASHES. This happens even when I use it continually, so timeout cannot occur. This bug has been around for a long time. I don't know of a good way of using SFTP under Nautilus until it gets fixed.
Another user experienced a similar problem: Connect to server A via sftp:// using sshkey authentication copy some files to and fro server A keep connection alive Connect to server B via sftp:// using sshkey authentication, which leads to a crash of all open "files" windows of nautilus reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --no-default-window crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.16.4-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 tried to mount my Windows Phone on Nautilus. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.16.6-203.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.