Bug 351471 – crash on 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 351471 - crash on Open Folder


Summary:	crash on Open Folder


Status:	RESOLVED DUPLICATE of bug 350037

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-08-15 14:50 UTC by martin.men
Modified:	2006-08-15 14:55 UTC

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

Description martin.men 2006-08-15 14:50:37 UTC

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.91 2006-08-08 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 76701696 vsize: 0 resident: 76701696 share: 0 rss: 17567744 rss_rlim: 0
CPU usage: start_time: 1155653431 rtime: 0 utime: 140 stime: 0 cutime:136 cstime: 0 timeout: 4 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 -1226557776 (LWP 23244)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 70494

Thread 1 (Thread -1226557776 (LWP 23244))

#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_strdup
from /usr/lib/libglib-2.0.so.0
#5 nautilus_directory_async_state_changed
#6 nautilus_file_get_uri
#7 nautilus_file_get_uri
#8 nautilus_file_has_volume
#9 nautilus_icon_container_request_update_all
#10 _shortcuts_model_filter_get_type
#11 POA_Nautilus_MetafileMonitor__init
#12 POA_Nautilus_MetafileMonitor__init
#13 nautilus_marshal_BOOLEAN__POINTER
#14 POA_Nautilus_MetafileMonitor__init
#15 POA_Nautilus_MetafileMonitor__init
#16 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#17 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 gtk_widget_show
from /usr/lib/libgtk-x11-2.0.so.0
#23 _shortcuts_model_filter_get_type
#24 nautilus_undo_transaction_unregister_object
#25 fm_directory_view_bump_zoom_level
#26 nautilus_clipboard_monitor_emit_changed
#27 nautilus_directory_async_state_changed
#28 nautilus_icon_container_request_update_all
#29 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#30 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#31 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#32 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#33 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#34 POA_Nautilus_MetafileMonitor__init
#35 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#36 ??
#0 __kernel_vsyscall

Comment 1 Rob Bradford 2006-08-15 14:55:27 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.

In particular that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Please add the feedback to #350037.

Thanks!

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