Bug 366839 – crash in CD/DVD Creator: I wanted to access my us...

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 366839 - crash in CD/DVD Creator: I wanted to access my us...


Summary:	crash in CD/DVD Creator: I wanted to access my us...


Status:	RESOLVED DUPLICATE of bug 363417

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-29 13:04 UTC by jonathan_becker
Modified:	2006-10-29 15:47 UTC

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

Description jonathan_becker 2006-10-29 13:04:42 UTC

What were you doing when the application crashed?
I wanted to access my usb-drive


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

Memory status: size: 207433728 vsize: 0 resident: 207433728 share: 0 rss: 98926592 rss_rlim: 0
CPU usage: start_time: 1162119440 rtime: 0 utime: 7272 stime: 0 cutime:6480 cstime: 0 timeout: 792 it_real_value: 0 frequency: 16558

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227348304 (LWP 5292)]
[New Thread -1300169824 (LWP 5978)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79727

Thread 1 (Thread -1227348304 (LWP 5292))

#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 g_type_check_instance
from /usr/lib/libgobject-2.0.so.0
#5 g_signal_handlers_disconnect_matched
from /usr/lib/libgobject-2.0.so.0
#6 fm_directory_view_bump_zoom_level
#7 fm_directory_view_bump_zoom_level
#8 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#9 POA_Nautilus_MetafileMonitor__init
#10 POA_Nautilus_MetafileMonitor__init
#11 POA_Nautilus_MetafileMonitor__init
#12 POA_Nautilus_MetafileMonitor__init
#13 POA_Nautilus_MetafileMonitor__init
#14 nautilus_undo_transaction_unregister_object
#15 fm_directory_view_bump_zoom_level
#16 nautilus_clipboard_monitor_emit_changed
#17 nautilus_directory_async_state_changed
#18 nautilus_icon_container_request_update_all
#19 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 POA_Nautilus_MetafileMonitor__init
#25 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#26 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-10-29 15:47:21 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 363417 ***