Bug 411418 – crash in CD/DVD Creator: continuously crashing on...

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 411418 - crash in CD/DVD Creator: continuously crashing on...


Summary:	crash in CD/DVD Creator: continuously crashing on...


Status:	RESOLVED DUPLICATE of bug 349840

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:	2007-02-24 00:49 UTC by will
Modified:	2007-02-24 19:41 UTC

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

Description will 2007-02-24 00:49:24 UTC

What were you doing when the application crashed?
continuously crashing on launch after unmounting an smb volume.


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

Memory status: size: 41308160 vsize: 0 resident: 41308160 share: 0 rss: 11452416 rss_rlim: 0
CPU usage: start_time: 1172277784 rtime: 0 utime: 21 stime: 0 cutime:20 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1227037008 (LWP 5911)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 113384

Thread 1 (Thread -1227037008 (LWP 5911))

#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 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 nautilus_file_get_internal
at nautilus-file.c line 207
#11 nautilus_compute_title_for_uri
at nautilus-file-utilities.c line 80
#12 nautilus_bookmark_list_load_file
at nautilus-bookmark-list.c line 81
#13 nautilus_bookmark_list_init
at nautilus-bookmark-list.c line 166
#14 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#15 g_object_set
from /usr/lib/libgobject-2.0.so.0
#16 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#17 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_object_new
from /usr/lib/libgobject-2.0.so.0
#19 nautilus_bookmark_list_new
at nautilus-bookmark-list.c line 511
#20 nautilus_get_bookmark_list
at nautilus-window-bookmarks.c line 57
#21 nautilus_window_initialize_bookmarks_menu
at nautilus-window-bookmarks.c line 303
#22 nautilus_window_init
at nautilus-window.c line 174
#23 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#24 g_object_set
from /usr/lib/libgobject-2.0.so.0
#25 nautilus_window_constructor
at nautilus-window.c line 656
#26 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#27 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#28 gtk_widget_new
from /usr/lib/libgtk-x11-2.0.so.0
#29 nautilus_desktop_window_new
at nautilus-desktop-window.c line 116
#30 nautilus_application_open_desktop
at nautilus-application.c line 776
#31 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#32 Nautilus_Shell_start_desktop
at nautilus-shell-interface-stubs.c line 144
#33 nautilus_application_startup
at nautilus-application.c line 631
#34 main
at nautilus-main.c line 360
#35 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#36 _start
#0 __kernel_vsyscall

Comment 1 will 2007-02-24 01:00:45 UTC

Deleting the .gtk-bookmarks file in my home directory fixed the crash.  The mounted smb volume which failed to unmount cleanly in the first place was x-nautilus-desktop:///Baby.volume.  Which, as you can tell by the stacktrack, was still in the bookmark file and was causing the crash when nautilus tried to launch.

Comment 2 André Klapper 2007-02-24 15:07:26 UTC

Hi Will, do you have the latest updates of Ubuntu installed? (Just asking, because this has been fixed for months, and if you have all updates installed, it's most likely that Ubuntu has not offered this fix to its users yet.)

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

Comment 3 will 2007-02-24 19:41:50 UTC

Yeah, I have the latest version of Ubuntu installed with all the packages update-to-date. They are at 2.16.1 and I see this fix is in 2.16.2.  Thanks for the info.