Bug 419459 – 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 419459 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 365750

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:	2007-03-17 18:51 UTC by marco.gallucci
Modified:	2007-03-18 17:54 UTC

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

Description marco.gallucci 2007-03-17 18:51:03 UTC

What were you doing when the application crashed?



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

Memory status: size: 123494400 vsize: 0 resident: 123494400 share: 0 rss: 42831872 rss_rlim: 0
CPU usage: start_time: 1174136037 rtime: 0 utime: 23485 stime: 0 cutime:18075 cstime: 0 timeout: 5410 it_real_value: 0 frequency: 5729

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 -1226467664 (LWP 6438)]
[New Thread -1329239136 (LWP 16015)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 119506

Thread 1 (Thread -1226467664 (LWP 6438))

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

Comment 1 Susana 2007-03-18 17:54:45 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 365750 ***