Bug 414626 – crash in Computer: launching nautilus from ...

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 414626 - crash in Computer: launching nautilus from ...


Summary:	crash in Computer: launching nautilus from ...


Status:	RESOLVED DUPLICATE of bug 374966

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-04 16:33 UTC by tanim.islam
Modified:	2007-03-04 22:16 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description tanim.islam 2007-03-04 16:33:18 UTC

Version: 2.17.92

What were you doing when the application crashed?
launching nautilus from a broken gnome session


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 21909504 vsize: 0 resident: 21909504 share: 0 rss: 8024064 rss_rlim: 0
CPU usage: start_time: 1173025972 rtime: 0 utime: 28 stime: 0 cutime:18 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0

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)
[Thread debugging using libthread_db enabled]
[New Thread -1227086160 (LWP 18000)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 115780

Thread 1 (Thread -1227086160 (LWP 18000))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 _dbus_abort
at dbus-sysdeps.c line 84
#8 _dbus_warn_check_failed
#9 dbus_connection_add_filter
at dbus-connection.c line 4955
#10 oobs_object_commit
from /usr/lib/liboobs-1.so.2
#11 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#12 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_object_new
from /usr/lib/libgobject-2.0.so.0
#14 oobs_smb_config_get
from /usr/lib/liboobs-1.so.2
#15 nautilus_shares_register_type
from /usr/lib/nautilus/extensions-1.0/libnautilus-gst-shares.so
#16 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#17 g_object_set
from /usr/lib/libgobject-2.0.so.0
#18 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#19 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_object_new
from /usr/lib/libgobject-2.0.so.0
#21 nautilus_marshal_BOOLEAN__POINTER
#22 nautilus_marshal_BOOLEAN__POINTER
#23 POA_Nautilus_MetafileMonitor__init
#24 POA_Nautilus_MetafileMonitor__init
#25 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#26 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-03-04 22:16:12 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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