GNOME Bugzilla – Bug 166811
Crash while mounting/viewing Windows share
Last modified: 2006-07-03 17:29:43 UTC
Distribution: Debian 3.1 Package: nautilus Severity: normal Version: GNOME2.9.91 unspecified Gnome-Distributor: Ubuntu Synopsis: Crash while mounting/viewing Windows share Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.9.1) Description: Description of the crash: While attempting to mount a Windows share on the local network network, Nautilus crashed. After it restarted the share was shown on the desktop but any attempt to open it resulted in Nautilus crashing again Steps to reproduce the crash: 1. Places | Connect to server... 2. Service type: Windows share; Server: 192.168.0.6; Share: Anime; User Name: GUEST 3. Connect How often does this happen? Every time. Additional Information: Using Gnome 2.9.91 in Ubuntu testing branch, Kernel 2.6.10 and Samba 3.0.10. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225034240 (LWP 11876)] [New Thread -1239856208 (LWP 11879)] [New Thread -1236288592 (LWP 11878)] [New Thread -1226888272 (LWP 11877)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 55508
Thread 4 (Thread -1226888272 (LWP 11877))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-09 11:12 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was sjmorgan@gmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
could you paste a backtrace of the bug with nautilus-dbg installed ?
Hope this helps: Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1225042432 (LWP 8003)] [New Thread -1236984912 (LWP 8031)] [New Thread -1236325456 (LWP 8028)] [New Thread -1226925136 (LWP 8018)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 55613
Thread 4 (Thread -1226925136 (LWP 8018))
thanks for the backtrace. Could you download this package: http://pkg-gnome.alioth.debian.org/nautilus_2.9.91-0ubuntu1_i386.deb and: - sudo dpkg -i nautilus_2.9.91-0ubuntu1_i386.deb - gnome-session-remove nautilus - nautilus - open the share to get the crash and paste the output messages here
(nautilus:11836): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkWindow' (nautilus:11836): Gtk-CRITICAL **: gtk_window_set_icon: assertion `GTK_IS_WINDOW (window)' failed (nautilus:11836): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkWidget' (nautilus:11836): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (nautilus:11836): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (nautilus:11836): GLib-GObject-CRITICAL **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (nautilus:11836): GLib-GObject-CRITICAL **: g_object_notify: assertion `G_IS_OBJECT (object)' failed (nautilus:11836): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:11836): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (nautilus:11836): GLib-GObject-CRITICAL **: g_signal_emit_by_name: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** (nautilus:11836): CRITICAL **: fm_directory_view_begin_loading: assertion `FM_IS_DIRECTORY_VIEW (view)' failed /usr/share/bug-buddy/gdb-cmd:2: Error in sourced command file: Previous frame inner to this frame (corrupt stack?)
weird. You should have some lines starting with "IS_WINDOW" and "Titles" with this package. Do you have that in ~/.xession-errors ?
Sorry about that, I assumed they were of no use since they weren't generated by the crash so I left them out. Here's the output after I repeated the same steps: simon@charlie:~ $ nautilus IS_WINDOW:1 Titles: (null) Desktop IS_WINDOW:1 Titles: (null) IS_WINDOW:1 Titles: simon IS_WINDOW:1 Titles: Desktop Desktop IS_WINDOW:1 Titles: simon simon IS_WINDOW:1 Titles: Desktop Desktop IS_WINDOW:1 Titles: simon simon IS_WINDOW:1 Titles: Desktop Desktop IS_WINDOW:1 Titles: (null) IS_WINDOW:1 Titles: Anime on 192.168.0.6 IS_WINDOW:0 [Invalid UTF-8] Titles: (\xaf$\x08 Anime on 192.168.0.6 (nautilus:13949): GLib-GObject-WARNING **: invalid unclassed type `(null)' in class cast to `NautilusWindow' (nautilus:13949): GLib-GObject-WARNING **: invalid unclassed type `(null)' in class cast to `NautilusWindow'
right we have a "IS_WINDOW:0" which is the output of NAUTILUS_IS_WINDOW (window) in nautilus_window_set_title (). nautilus_window_set_title () should probably have a g_return_if_fail (NAUTILUS_IS_WINDOW (window));. thanks a lot for the debug on this.
*** Bug 168563 has been marked as a duplicate of this bug. ***
This can still happend with Nautilus 2.12. Patch available under: http://mail.gnome.org/archives/nautilus-list/2005-September/msg00222.html
While a g_return_if_fail patch may avoid a crash (and i've commited this patch) its not really a full fix. We shouldn't call these functions with invalid arguments, and we shouldn't spew errors on stdout.
Simon: Are you still able to reproduce this with a recent Nautilus version, i.e. after upgrading to the latest Breezy?
I don't have GNOME installed and that particular network share is long gone.
closing as incomplete due to the last comment. thanks for reporting, anyway. :-)