Bug 367343 – crash in CD/DVD Creator: logging in

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 367343 - crash in CD/DVD Creator: logging in


Summary:	crash in CD/DVD Creator: logging in


Status:	RESOLVED DUPLICATE of bug 351713

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 02:09 UTC by redhat
Modified:	2006-10-30 11:19 UTC

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

Description redhat 2006-10-30 02:09:57 UTC

What were you doing when the application crashed?
logging in


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 96485376 vsize: 0 resident: 96485376 share: 0 rss: 23138304 rss_rlim: 0
CPU usage: start_time: 1162174176 rtime: 0 utime: 103 stime: 0 cutime:90 cstime: 0 timeout: 13 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 -1209083136 (LWP 6596)]
(no debugging symbols found)
0x00fbb402 in __kernel_vsyscall ()

+ Trace 80178

Thread 1 (Thread -1209083136 (LWP 6596))

#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 nautilus_directory_async_state_changed
#5 nautilus_file_get_uri
#6 nautilus_file_get_uri
#7 nautilus_file_has_volume
#8 nautilus_icon_container_request_update_all
#9 fm_directory_view_bump_zoom_level
#10 gtk_tree_model_get_value
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_tree_view_column_cell_set_cell_data
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_tree_view_get_hadjustment
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /lib/libgobject-2.0.so.0
#16 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#18 g_signal_emit
from /lib/libgobject-2.0.so.0
#19 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#21 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#22 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#23 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#24 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#25 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#26 g_main_context_check
from /lib/libglib-2.0.so.0
#27 g_main_loop_run
from /lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 POA_Nautilus_MetafileMonitor__init
#30 __libc_start_main
from /lib/libc.so.6
#31 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-30 02:18:54 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 351713 ***

Comment 2 redhat 2006-10-30 04:37:02 UTC

This may be a hal bug.  My Motorola Slvr was plugged in to the USB cable to get charged.  Upon plugging in (non-root), the phone was automounted as a mass storage device.  I had then logged in as root, performed tasks, logged out, and came back as a normal user.  Nautilus crashed repeatedly until the device was unmounted/unplugged.

Comment 3 Karsten Bräckelmann 2006-10-30 11:19:56 UTC

The stacktrace does not show hal being involved at all. Duplicate, again.


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