Bug 367452 – crash in CD/DVD Creator: Trying to UNMOUNT my Flo...

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 367452 - crash in CD/DVD Creator: Trying to UNMOUNT my Flo...


Summary:	crash in CD/DVD Creator: Trying to UNMOUNT my Flo...


Status:	RESOLVED DUPLICATE of bug 360330

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-10-30 07:27 UTC by misfit_323
Modified:	2006-10-30 10:16 UTC

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

Description misfit_323 2006-10-30 07:27:18 UTC

What were you doing when the application crashed?
Trying to UNMOUNT my Floppy Drive.

As well the Floppy Drive takes quite awhile to Mount as well, I'd say a Good 30-45 seconds.

Then when you goto Save a file to it, it takes a Good 10-15 seconds to Start saving it to the Disk.


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

Memory status: size: 280354816 vsize: 280354816 resident: 37335040 share: 21028864 rss: 37335040 rss_rlim: -1
CPU usage: start_time: 1162188719 rtime: 1618 utime: 1514 stime: 104 cutime:8 cstime: 26 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 47099127765536 (LWP 4561)]
(no debugging symbols found)
0x00002ad61aca6eef in waitpid () from /lib/libpthread.so.0

+ Trace 80270

Thread 1 (Thread 47099127765536 (LWP 4561))

#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 gtk_container_add
from /usr/lib/libgtk-x11-2.0.so.0
#4 fm_directory_view_bump_zoom_level
#5 fm_directory_view_bump_zoom_level
#6 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#10 _gtk_action_emit_activate
from /usr/lib/libgtk-x11-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_menu_shell_append
from /usr/lib/libgtk-x11-2.0.so.0
#18 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#26 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#27 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#28 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#29 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#30 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#31 POA_Nautilus_MetafileMonitor__init
#32 __libc_start_main
from /lib/libc.so.6
#33 ??
#34 ??
#35 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-10-30 10:16:07 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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