Bug 386300 – crash in CD/DVD Creator: I get an error message t...

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 386300 - crash in CD/DVD Creator: I get an error message t...


Summary:	crash in CD/DVD Creator: I get an error message t...


Status:	RESOLVED DUPLICATE of bug 373281

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:

Duplicates:	388580 (view as bug list)
Depends on:
Blocks:

Reported:	2006-12-15 20:05 UTC by trax
Modified:	2006-12-27 00:08 UTC

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

Description trax 2006-12-15 20:05:56 UTC

What were you doing when the application crashed?
I get an error message telling that nautilus cannot work ; and asking me for killing bonobo and restarting nautilus


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.2 2006-12-12 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 20783104 vsize: 0 resident: 20783104 share: 0 rss: 6807552 rss_rlim: 0
CPU usage: start_time: 1166390213 rtime: 0 utime: 14 stime: 0 cutime:12 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227167552 (LWP 12727)]
0xb7fd8410 in __kernel_vsyscall ()

+ Trace 94468

Thread 1 (Thread -1227167552 (LWP 12727))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/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/libc.so.6
#6 abort
from /lib/libc.so.6
#7 dbus_malloc
from /usr/lib/libdbus-1.so.3
#8 dbus_watch_handle
from /usr/lib/libdbus-1.so.3
#9 dbus_watch_handle
from /usr/lib/libdbus-1.so.3
#10 dbus_malloc
from /usr/lib/libdbus-1.so.3
#11 dbus_threads_init
from /usr/lib/libdbus-1.so.3
#12 dbus_threads_init
from /usr/lib/libdbus-1.so.3
#13 dbus_connection_flush
from /usr/lib/libdbus-1.so.3
#14 dbus_bus_register
from /usr/lib/libdbus-1.so.3
#15 gnome_vfs_daemon_set_current_connection
from /usr/lib/libgnomevfs-2.so.0
#16 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#17 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#18 g_object_set
from /usr/lib/libgobject-2.0.so.0
#19 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#20 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_object_new
from /usr/lib/libgobject-2.0.so.0
#22 gnome_vfs_volume_monitor_emit_pre_unmount
from /usr/lib/libgnomevfs-2.so.0
#23 gnome_vfs_get_volume_monitor
from /usr/lib/libgnomevfs-2.so.0
#24 POA_Nautilus_MetafileMonitor__init
#25 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#26 g_object_set
from /usr/lib/libgobject-2.0.so.0
#27 bonobo_object_add_interface
from /usr/lib/libbonobo-2.so.0
#28 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#29 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_object_new
from /usr/lib/libgobject-2.0.so.0
#31 POA_Nautilus_MetafileMonitor__init
#32 POA_Nautilus_MetafileMonitor__init
#33 __libc_start_main
from /lib/libc.so.6
#34 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-12-17 02:38:51 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Susana 2006-12-22 20:48:58 UTC

*** Bug 388580 has been marked as a duplicate of this bug. ***

Comment 3 Pascal Terjan 2006-12-27 00:08:41 UTC


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