← Back to team overview

desktop-packages team mailing list archive

[Bug 1202159] Re: Nautilus crashes when reconnecting to network file server

 

I'm using nautilus 1:3.10.1-0ubuntu9.5 on trusty and it looks like I
still have the similar issue after umounting a smb share and connecting
again with different credentials.

Here is my stacktrace:

#0  0x00007f99a94c8cc9 in __GI_raise (sig=sig@entry=0x6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007f99a94cc0d8 in __GI_abort () at abort.c:89
#2  0x00007f99aa004165 in g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x50127f "nautilus-bookmark.c", line=line@entry=0x15e, func=func@entry=0x501890 <__FUNCTION__.49716> "nautilus_bookmark_connect_file", message=message@entry=0x1405a60 "assertion failed: (!nautilus_file_is_gone (bookmark->details->file))") at /build/buildd/glib2.0-2.40.2/./glib/gtestutils.c:2291
#3  0x00007f99aa0041fa in g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x50127f "nautilus-bookmark.c", line=line@entry=0x15e, func=func@entry=0x501890 <__FUNCTION__.49716> "nautilus_bookmark_connect_file", expr=expr@entry=0x501590 "!nautilus_file_is_gone (bookmark->details->file)") at /build/buildd/glib2.0-2.40.2/./glib/gtestutils.c:2306
#4  0x0000000000482649 in nautilus_bookmark_connect_file (bookmark=bookmark@entry=0x7f99740041e0) at nautilus-bookmark.c:350
#5  0x0000000000482694 in nautilus_bookmark_constructed (obj=<optimized out>) at nautilus-bookmark.c:550
#6  0x00007f99aa2b438a in g_object_new_internal (class=class@entry=0x11db0b0, params=params@entry=0x7fff28f75c80, n_params=0x3) at /build/buildd/glib2.0-2.40.2/./gobject/gobject.c:1763
#7  0x00007f99aa2b64c4 in g_object_new_valist (object_type=object_type@entry=0xeb1a40, first_property_name=first_property_name@entry=0x4fd6cb "location", var_args=var_args@entry=0x7fff28f75dd8) at /build/buildd/glib2.0-2.40.2/./gobject/gobject.c:1980
#8  0x00007f99aa2b68a4 in g_object_new (object_type=0xeb1a40, first_property_name=first_property_name@entry=0x4fd6cb "location") at /build/buildd/glib2.0-2.40.2/./gobject/gobject.c:1571
#9  0x0000000000482a04 in nautilus_bookmark_new (location=location@entry=0x11dca90, custom_name=custom_name@entry=0xf6b940 "") at nautilus-bookmark.c:757
#10 0x00000000004750ab in nautilus_window_slot_update_bookmark (file=0x1472320, slot=0x100e530) at nautilus-window-slot.c:1964
#11 nautilus_window_slot_update_for_new_location (slot=0x100e530) at nautilus-window-slot.c:2249
#12 location_has_really_changed (slot=0x100e530) at nautilus-window-slot.c:2505
#13 view_begin_loading_cb (view=<optimized out>, slot=0x100e530) at nautilus-window-slot.c:2426
#14 0x00007f99aa2af3b8 in g_closure_invoke (closure=0x1217900, return_value=0x0, n_param_values=0x1, param_values=0x7fff28f760e0, invocation_hint=0x7fff28f76080) at /build/buildd/glib2.0-2.40.2/./gobject/gclosure.c:768
#15 0x00007f99aa2c0d3d in signal_emit_unlocked_R (node=node@entry=0x1033cc0, detail=detail@entry=0x0, instance=instance@entry=0x1202550, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff28f760e0) at /build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:3551
#16 0x00007f99aa2c8a29 in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fff28f76268) at /build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:3307
#17 0x00007f99aa2c8ce2 in g_signal_emit (instance=instance@entry=0x1202550, signal_id=<optimized out>, detail=detail@entry=0x0) at /build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:3363
#18 0x00000000004626db in finish_loading (view=0x1202550) at nautilus-view.c:9260
#19 finish_loading_if_all_metadata_loaded (view=view@entry=0x1202550) at nautilus-view.c:9319
#20 0x0000000000462af3 in metadata_for_directory_as_file_ready_callback (file=0x1472320, callback_data=0x1202550) at nautilus-view.c:9339
#21 0x00000000004a4d43 in call_ready_callbacks_at_idle (callback_data=<optimized out>) at nautilus-directory-async.c:1855
#22 0x00007f99a9fdfce5 in g_main_dispatch (context=0xe3dbd0) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3064
#23 g_main_context_dispatch (context=context@entry=0xe3dbd0) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3663
#24 0x00007f99a9fe0048 in g_main_context_iterate (context=context@entry=0xe3dbd0, block=block@entry=0x1, dispatch=dispatch@entry=0x1, self=<optimized out>) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3734
#25 0x00007f99a9fe00ec in g_main_context_iteration (context=0xe3dbd0, context@entry=0x0, may_block=may_block@entry=0x1) at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3795
#26 0x00007f99aa592b9c in g_application_run (application=0xe05140, argc=argc@entry=0x1, argv=argv@entry=0x7fff28f76608) at /build/buildd/glib2.0-2.40.2/./gio/gapplication.c:2115
#27 0x000000000042b561 in main (argc=0x1, argv=0x7fff28f76608) at nautilus-main.c:104

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1202159

Title:
  Nautilus crashes when reconnecting to network file server

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in nautilus source package in Trusty:
  Fix Released
Status in nautilus package in Fedora:
  Unknown

Bug description:
  [Impact]
  Reconnecting to servers using nautilus causes a crash.

  [Test Case]
  1. Open a nautilus window
  2. In sidebar, click "Connect to Network"
  3. Enter network address "ftp://ftp.debian.org/";
  4. Click connect in both dialogs
  5. Press eject button beside ftp.debian.org entry that appears in sidebar
  6. In sidebar, click "Connect to Network"
  7. Enter network address "ftp://ftp.debian.org/";
  8. Click connect in both dialogs

  Expected result:
  In both steps 4 and 8 you are reconnected to ftp.debian.org and can browse files on that server

  Observed result:
  The first connect (step 4) works and nautilus crashes on the second attempt (step 8)

  [Regression Potential]
  The fix is adding a missing unref call in the code which is a simple memory leak bug and is unlikely to have negative consequences. Could expose any existing unref bug that may be hidden by this leak.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1202159/+subscriptions