Bug 396643 – crash in CD/DVD Creator: Unmounting a Samba share...

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 396643 - crash in CD/DVD Creator: Unmounting a Samba share...


Summary:	crash in CD/DVD Creator: Unmounting a Samba share...


Status:	RESOLVED DUPLICATE of bug 371237

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-01-14 20:34 UTC by john
Modified:	2007-01-16 16:33 UTC

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

Description john 2007-01-14 20:34:54 UTC

What were you doing when the application crashed?
Unmounting a Samba share from the gnome desktop


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

Memory status: size: 224415744 vsize: 224415744 resident: 41152512 share: 19566592 rss: 41152512 rss_rlim: -1
CPU usage: start_time: 1168806032 rtime: 635 utime: 551 stime: 84 cutime:0 cstime: 0 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47488205027920 (LWP 7452)]
(no debugging symbols found)
0x00002b30b19a2eef in waitpid () from /lib/libpthread.so.0

+ Trace 102204

Thread 1 (Thread 47488205027920 (LWP 7452))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 g_logv
from /usr/lib/libglib-2.0.so.0
#6 g_log
from /usr/lib/libglib-2.0.so.0
#7 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#8 nautilus_file_ref
#9 fm_directory_view_bump_zoom_level
#10 fm_directory_view_bump_zoom_level
#11 POA_Nautilus_MetafileMonitor__init
#12 POA_Nautilus_MetafileMonitor__init
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#17 fm_directory_view_bump_zoom_level
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 nautilus_file_get_uri
#23 nautilus_directory_async_state_changed
#24 nautilus_clipboard_monitor_emit_changed
#25 nautilus_clipboard_monitor_emit_changed
#26 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#31 gnome_vfs_volume_monitor_emit_pre_unmount
from /usr/lib/libgnomevfs-2.so.0
#32 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#33 dbus_connection_dispatch
from /usr/lib/libdbus-1.so.3
#34 dbus_server_setup_with_g_main
from /usr/lib/libdbus-glib-1.so.2
#35 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#36 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#37 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#38 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#39 POA_Nautilus_MetafileMonitor__init
#40 __libc_start_main
from /lib/libc.so.6
#41 ??
#42 ??
#43 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 André Klapper 2007-01-16 16:33:42 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 371237 ***