Bug 384277 – crash in CD/DVD Creator: clicked 'places / netwro...

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 384277 - crash in CD/DVD Creator: clicked 'places / netwro...


Summary:	crash in CD/DVD Creator: clicked 'places / netwro...


Status:	RESOLVED DUPLICATE of bug 363289

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:

Duplicates:	384278 (view as bug list)
Depends on:
Blocks:

Reported:	2006-12-10 07:15 UTC by ubuntu
Modified:	2006-12-10 23:12 UTC

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

Description ubuntu 2006-12-10 07:15:28 UTC

What were you doing when the application crashed?
clicked 'places / netwrok servers'  then this came up.  Will report if repeatable.


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

Memory status: size: 115453952 vsize: 0 resident: 115453952 share: 0 rss: 23502848 rss_rlim: 0
CPU usage: start_time: 1165634716 rtime: 0 utime: 7959 stime: 0 cutime:6980 cstime: 0 timeout: 979 it_real_value: 0 frequency: 12135

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 -1226938704 (LWP 4645)]
(no debugging symbols found)
0xb7662c21 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 92962

Thread 1 (Thread -1226938704 (LWP 4645))

#0 __waitpid_nocancel
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 _gtk_icon_cache_add_icons
from /usr/lib/libgtk-x11-2.0.so.0
#4 gtk_icon_theme_list_icons
from /usr/lib/libgtk-x11-2.0.so.0
#5 nautilus_directory_ref
#6 POA_Nautilus_MetafileMonitor__init
#7 POA_Nautilus_MetafileMonitor__init
#8 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#9 g_object_set
from /usr/lib/libgobject-2.0.so.0
#10 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#11 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_object_new
from /usr/lib/libgobject-2.0.so.0
#13 POA_Nautilus_MetafileMonitor__init
#14 nautilus_marshal_BOOLEAN__POINTER
#15 POA_Nautilus_MetafileMonitor__init
#16 POA_Nautilus_MetafileMonitor__init
#17 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#18 g_value_set_boxed
from /usr/lib/libgobject-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_show
from /usr/lib/libgtk-x11-2.0.so.0
#24 POA_Nautilus_MetafileMonitor__init
#25 nautilus_undo_transaction_unregister_object
#26 fm_directory_view_bump_zoom_level
#27 nautilus_clipboard_monitor_emit_changed
#28 nautilus_directory_async_state_changed
#29 nautilus_icon_container_request_update_all
#30 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#34 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#35 POA_Nautilus_MetafileMonitor__init
#36 __libc_start_main
from /lib/libc.so.6
#37 ??
#0 __waitpid_nocancel
from /lib/libpthread.so.0

Comment 1 Susana 2006-12-10 14:14:11 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 363289 ***

Comment 2 André Klapper 2006-12-10 23:12:16 UTC

*** Bug 384278 has been marked as a duplicate of this bug. ***