After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 740477 - Crash when accessing a boomarked gvfs smb mount twice in a row
Crash when accessing a boomarked gvfs smb mount twice in a row
Status: RESOLVED DUPLICATE of bug 693950
Product: nautilus
Classification: Core
Component: Bookmarks
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-11-21 07:37 UTC by Uwe Helm
Modified: 2016-06-09 11:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
bugfix (604 bytes, patch)
2014-11-21 07:37 UTC, Uwe Helm
committed Details | Review
Revert commit 552ad342df7306f95bf6959af36e2b5737d36d9c (982 bytes, patch)
2014-12-27 20:46 UTC, Nelson Benitez
committed Details | Review

Description Uwe Helm 2014-11-21 07:37:56 UTC
Created attachment 291140 [details] [review]
bugfix

Nautilus crashes when a bookmarked smb share is accessed twice in a row (click to mount -> unmount -> click to mount again -> CRASH)

This is the error:

ERROR:nautilus-bookmark.c:338:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file))

It looks like file->details->is_gone is set to TRUE after the bookmark is accessed the first time, and nautilus expects it to be FALSE during the subsequent access. 

Attached is a fix that resets file->details->is_gone in nautilus_file_clear_info(). Please check it before you apply, i'm not very familiar with the code and there may be a better approach.


Nautilus version: 3.14.1
Arch Linux

Stacktrace:

Program received signal SIGABRT, Aborted.
0x00007ffff3de7967 in raise () from /usr/lib/libc.so.6
(gdb) bt
  • #0 raise
    from /usr/lib/libc.so.6
  • #1 abort
    from /usr/lib/libc.so.6
  • #2 g_assertion_message
    from /usr/lib/libglib-2.0.so.0
  • #3 g_assertion_message_expr
    from /usr/lib/libglib-2.0.so.0
  • #4 nautilus_bookmark_connect_file
    at nautilus-bookmark.c line 338
  • #5 nautilus_bookmark_constructed
    at nautilus-bookmark.c line 536
  • #6 ??
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #9 nautilus_bookmark_new
    at nautilus-bookmark.c line 743
  • #10 nautilus_window_slot_update_bookmark
    at nautilus-window-slot.c line 1848
  • #11 nautilus_window_slot_update_for_new_location
    at nautilus-window-slot.c line 2131
  • #12 location_has_really_changed
    at nautilus-window-slot.c line 2409
  • #13 view_begin_loading_cb
    at nautilus-window-slot.c line 2264
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #18 finish_loading
    at nautilus-view.c line 9160
  • #19 finish_loading_if_all_metadata_loaded
    at nautilus-view.c line 9219
  • #20 metadata_for_directory_as_file_ready_callback
    at nautilus-view.c line 9239
  • #21 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1798
  • #22 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #23 ??
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #25 g_application_run
    from /usr/lib/libgio-2.0.so.0
  • #26 main
    at nautilus-main.c line 103

Comment 1 tyang 2014-12-02 03:34:07 UTC
I can confirm this bug while connecting a sftp server...
Comment 2 Cosimo Cecchi 2014-12-22 01:54:48 UTC
Review of attachment 291140 [details] [review]:

Nice patch - looks good to me.
Comment 3 Cosimo Cecchi 2014-12-22 08:25:58 UTC
Pushed to master.
Comment 4 tyang 2014-12-23 06:59:38 UTC
Hi,guys, I had tried this patch and it works for me.

But I met another issue since I added this patch into nautilus and following are steps:

1.plug an USB stick
2.open the USB folder
3.unplug the USB stick

result:
all the desktop icon disappear.

Does this issue happen only to me? Could you guys try these?

Thanks
Comment 5 tyang 2014-12-24 06:16:01 UTC
Hi,guys, I had tried this patch and it works for me.

But I met another issue since I added this patch into nautilus and following are steps:

1.plug an USB stick
2.open the USB folder
3.unplug the USB stick

result:
all the desktop icon disappear.

Does this issue happen only to me? Could you guys try these?

Thanks
Comment 6 Nelson Benitez 2014-12-27 20:36:48 UTC
The patch committed here is causing serious regression for me:

1. Select some file
2. Press Shift+DEL to delete file
3. Confirm deletion dialog

Expected result: File is deleted and cleared from view, navigating to other folder doesn't cause a crash.

Actual result: File is not cleared from view after deletion, trying to navigate to other folder causes a crash.


Besides, the patch is wrong according to existent nautilus logic, because the function nautilus_file_mark_gone() in nautilus_file.c is the function responsible to set 'is_gone' to TRUE, and the same function also calls nautilus_file_clear_info (file) which, by means of this patch, is reverting 'is_gone' to FALSE again.

So nautilus_file_mark_gone() is setting 'is_gone' to TRUE and to FALSE again, which is obviously not the intended behaviour.

I think this patch should be reverted, and then try to find the real fix for this bug.
Comment 7 Nelson Benitez 2014-12-27 20:46:22 UTC
Created attachment 293380 [details] [review]
Revert commit 552ad342df7306f95bf6959af36e2b5737d36d9c

Patch for revert.
Comment 8 Cosimo Cecchi 2014-12-28 05:32:30 UTC
Review of attachment 293380 [details] [review]:

Thanks, Nelson. Let's revert the original patch.
Comment 9 Nelson Benitez 2014-12-28 06:44:10 UTC
Comment on attachment 293380 [details] [review]
Revert commit 552ad342df7306f95bf6959af36e2b5737d36d9c

Committed
Comment 10 Volker Sobek (weld) 2015-01-05 20:51:38 UTC
Maybe this is related to bug 708282 which fixed a similar problem?
Comment 11 Nelson Benitez 2015-01-06 23:07:06 UTC
(In reply to comment #10)
> Maybe this is related to bug 708282 which fixed a similar problem?

It seems same bug as this, but the fix on 708282 was introduced in nautilus 3.13.2 and reporter of this bug was using nautilus 3.14.1 so it seems the complete bug is still unfixed.

I could not reproduced this bug with a http share (webdav server).

Tyang can you confirm you are getting this bug with a sftp server? and state your nautilus version?

A possibility could be this bug is fixed for http shares but not for smb shares..

Uwe, before I get to install and configure a smb share, could you confirm you are still getting this bug with a recent nautilus? and state your nautilus version? in bug summary you say you're using nautilus 3.14.1 while current version on git is only 3.14.0 so maybe you confused versions?
Comment 12 tyang 2015-01-09 05:37:35 UTC
(In reply to comment #11)
> (In reply to comment #10)
> > Maybe this is related to bug 708282 which fixed a similar problem?
> 
> It seems same bug as this, but the fix on 708282 was introduced in nautilus
> 3.13.2 and reporter of this bug was using nautilus 3.14.1 so it seems the
> complete bug is still unfixed.
> 
> I could not reproduced this bug with a http share (webdav server).
> 
> Tyang can you confirm you are getting this bug with a sftp server? and state
> your nautilus version?
> 
> A possibility could be this bug is fixed for http shares but not for smb
> shares..
> 
> Uwe, before I get to install and configure a smb share, could you confirm you
> are still getting this bug with a recent nautilus? and state your nautilus
> version? in bug summary you say you're using nautilus 3.14.1 while current
> version on git is only 3.14.0 so maybe you confused versions?

I got nautilus version 3.10.1 with the patch commited in bug#708282.
I thought if this single patch can fix this bug, then there should be no problem with old version and provided patch.
Comment 13 tyang 2015-01-15 11:18:06 UTC
Any update? I still can reproduce this issue by connecting a sftp server...

Although I had version on nautilus-3.10.1 with patch provided in the bug#708282, this does not work.

I had searched other commited patches with no result...
Comment 14 Bastien Nocera 2016-06-09 11:21:02 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 693950 ***