Bug 537799 – crash in Open Folder: open network

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 537799 - crash in Open Folder: open network


Summary:	crash in Open Folder: open network


Status:	RESOLVED DUPLICATE of bug 522534

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-11 14:42 UTC by isoto
Modified:	2008-06-11 17:34 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description isoto 2008-06-11 14:42:26 UTC

Version: 2.20.0

What were you doing when the application crashed?
open network


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Alphacube GTK 0.5
Icon Theme: dlg-neu

Memory status: size: 157847552 vsize: 157847552 resident: 53784576 share: 14020608 rss: 53784576 rss_rlim: 4294967295
CPU usage: start_time: 1213080477 rtime: 9642 utime: 8948 stime: 694 cutime:218 cstime: 61 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b3f720 (LWP 2779)]
[New Thread 0xb46f2b90 (LWP 3139)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 200144

Thread 1 (Thread 0xb6b3f720 (LWP 2779))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
from /usr/lib/libglib-2.0.so.0
#11 ??
#12 ??
#13 ??
#14 ??
from /usr/lib/libglib-2.0.so.0
#15 ??
#0 __kernel_vsyscall



----------- .xsession-errors (75871 sec old) ---------------------
(gnome-www-browser:5734): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(gecko:5555): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkObject'
(gecko:5555): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
(gecko:5555): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(gecko:5555): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
(gecko:5555): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(gecko:5555): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `GtkObject'
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-06-11 17:34:05 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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