Bug 382777 – crash in Computer: opening nautilus with db...

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 382777 - crash in Computer: opening nautilus with db...


Summary:	crash in Computer: opening nautilus with db...


Status:	RESOLVED DUPLICATE of bug 374966

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-05 21:41 UTC by Reid Thompson
Modified:	2006-12-05 21:44 UTC

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

Description Reid Thompson 2006-12-05 21:41:40 UTC

What were you doing when the application crashed?
opening nautilus with dbus 1.0


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

Memory status: size: 28463104 vsize: 0 resident: 28463104 share: 0 rss: 13266944 rss_rlim: 0
CPU usage: start_time: 1165354827 rtime: 0 utime: 26 stime: 0 cutime:24 cstime: 0 timeout: 2 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".
[Thread debugging using libthread_db enabled]
[New Thread -1226553680 (LWP 25244)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 91884

Thread 1 (Thread -1226553680 (LWP 25244))

#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 4954
#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 Christian Kirbach 2006-12-05 21:44:35 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 ***