** Description changed: - This happened after my network died while having a smb share connected. - Bug #1195946 (currently still hidden) is related, as gvfs-smb crashed - just before this nautilus error came up. + [Impact] + Reconnecting to servers using nautilus causes a crash. - ProblemType: Crash - DistroRelease: Ubuntu 13.10 - Package: nautilus 1:3.8.2-0ubuntu1 - ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 - Uname: Linux 3.10.0-2-generic x86_64 - NonfreeKernelModules: wl nvidia - ApportVersion: 2.10.2-0ubuntu4 - Architecture: amd64 - AssertionMessage: ERROR:nautilus-bookmark.c:350:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file)) - Date: Wed Jul 17 13:18:09 2013 - ExecutablePath: /usr/bin/nautilus - GsettingsChanges: - b'org.gnome.nautilus.window-state' b'geometry' b"'854x561+126+61'" - b'org.gnome.nautilus.window-state' b'sidebar-width' b'198' - MarkForUpload: True - ProcCmdline: nautilus -n - Signal: 6 - SourcePackage: nautilus - StacktraceTop: - _g_log_abort () at /build/buildd/glib2.0-2.37.3/./glib/gmessages.c:255 - g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x503443 "nautilus-bookmark.c", line=line@entry=350, func=func@entry=0x503a50 "nautilus_bookmark_connect_file", message=<optimized out>) at /build/buildd/glib2.0-2.37.3/./glib/gtestutils.c:2075 - g_assertion_message_expr (domain=0x0, file=0x503443 "nautilus-bookmark.c", line=350, func=0x503a50 "nautilus_bookmark_connect_file", expr=<optimized out>) at /build/buildd/glib2.0-2.37.3/./glib/gtestutils.c:2086 - ?? () - ?? () - Title: nautilus assert failure: ERROR:nautilus-bookmark.c:350:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file)) - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo + [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.
** Summary changed: - nautilus assert failure: ERROR:nautilus-bookmark.c:350:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file)) + Nautilus crashes when reconnecting to network file server -- 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: Confirmed Status in “nautilus” package in Ubuntu: In Progress Status in “nautilus” source package in Trusty: In Progress 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
