Bug 466455 – crash in Open Folder: ds

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 466455 - crash in Open Folder: ds


Summary:	crash in Open Folder: ds


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:	474065 474066 (view as bug list)
Depends on:
Blocks:

Reported:	2007-08-14 02:24 UTC by dffd
Modified:	2007-09-06 12:22 UTC

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

Description dffd 2007-08-14 02:24:03 UTC

What were you doing when the application crashed?
ds


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

Memory status: size: 79781888 vsize: 0 resident: 79781888 share: 0 rss: 34689024 rss_rlim: 0
CPU usage: start_time: 1187058208 rtime: 0 utime: 174 stime: 0 cutime:161 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/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227217232 (LWP 25179)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 155030

Thread 1 (Thread -1227217232 (LWP 25179))

#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 _gtk_icon_cache_add_icons
from /usr/lib/libgtk-x11-2.0.so.0
#5 gtk_icon_theme_list_icons
from /usr/lib/libgtk-x11-2.0.so.0
#6 nautilus_directory_ref
#7 POA_Nautilus_MetafileMonitor__init
#8 POA_Nautilus_MetafileMonitor__init
#9 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#10 g_object_set
from /usr/lib/libgobject-2.0.so.0
#11 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#12 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_object_new
from /usr/lib/libgobject-2.0.so.0
#14 POA_Nautilus_MetafileMonitor__init
#15 nautilus_marshal_BOOLEAN__POINTER
#16 POA_Nautilus_MetafileMonitor__init
#17 POA_Nautilus_MetafileMonitor__init
#18 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#19 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#24 gtk_widget_show
from /usr/lib/libgtk-x11-2.0.so.0
#25 POA_Nautilus_MetafileMonitor__init
#26 nautilus_undo_transaction_unregister_object
#27 fm_directory_view_bump_zoom_level
#28 nautilus_clipboard_monitor_emit_changed
#29 nautilus_directory_async_state_changed
#30 nautilus_directory_async_state_changed
#31 nautilus_directory_async_state_changed
#32 nautilus_directory_async_state_changed
#33 nautilus_directory_async_state_changed
#34 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
from /usr/lib/libglib-2.0.so.0
#41 ??
#42 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#43 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#44 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#45 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#46 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#47 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#48 POA_Nautilus_MetafileMonitor__init
#49 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#50 ??
#0 __kernel_vsyscall

Comment 1 Susana 2007-08-21 20:31:38 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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

Comment 2 palfrey 2007-09-06 12:22:23 UTC

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

Comment 3 palfrey 2007-09-06 12:22:32 UTC

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