Bug 355227 – crash in Open Folder:

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


Summary:	crash in Open Folder:


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-09-10 06:28 UTC by info
Modified:	2006-09-10 07:34 UTC

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

Description info 2006-09-10 06:28:38 UTC

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 78249984 vsize: 0 resident: 78249984 share: 0 rss: 18644992 rss_rlim: 0
CPU usage: start_time: 1157869310 rtime: 0 utime: 125 stime: 0 cutime:113 cstime: 0 timeout: 12 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 -1226463568 (LWP 9446)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 72020

Thread 1 (Thread -1226463568 (LWP 9446))

#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 strlen
from /lib/tls/i686/cmov/libc.so.6
#5 g_strdup
from /usr/lib/libglib-2.0.so.0
#6 nautilus_directory_async_state_changed
#7 nautilus_file_get_uri
#8 nautilus_file_get_uri
#9 nautilus_file_has_volume
#10 nautilus_icon_container_request_update_all
#11 fm_directory_view_bump_zoom_level
#12 nautilus_file_ref
#13 nautilus_icon_container_request_update_all
#14 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#19 nautilus_icon_container_request_update_all
#20 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#25 gtk_icon_info_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_icon_theme_rescan_if_needed
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_icon_theme_rescan_if_needed
from /usr/lib/libgtk-x11-2.0.so.0
#28 _gtk_icon_theme_check_reload
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_window_new
from /usr/lib/libgtk-x11-2.0.so.0
#30 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#31 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#32 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#35 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#36 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#37 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#38 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#39 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#40 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#41 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#42 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#43 POA_Nautilus_MetafileMonitor__init
#44 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#45 ??
#0 __kernel_vsyscall

Comment 1 Fabio Bonelli 2006-09-10 07:34:09 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report?


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