Bug 363237 – crash in Open Folder: Going back to the previo...

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 363237 - crash in Open Folder: Going back to the previo...


Summary:	crash in Open Folder: Going back to the previo...


Status:	RESOLVED DUPLICATE of bug 352592

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-10-18 20:50 UTC by Juanjo Marín
Modified:	2006-10-18 20:55 UTC

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

Description Juanjo Marín 2006-10-18 20:50:58 UTC

What were you doing when the application crashed?
Going back to the previous folder


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

Memory status: size: 113414144 vsize: 0 resident: 113414144 share: 0 rss: 34603008 rss_rlim: 0
CPU usage: start_time: 1161204033 rtime: 0 utime: 889 stime: 0 cutime:842 cstime: 0 timeout: 47 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 -1227413840 (LWP 4909)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 77039

Thread 1 (Thread -1227413840 (LWP 4909))

#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 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 fm_directory_view_bump_zoom_level
#11 nautilus_marshal_VOID__OBJECT_OBJECT
#12 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#17 fm_directory_view_bump_zoom_level
#18 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#21 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#22 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#23 POA_Nautilus_MetafileMonitor__init
#24 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#25 ??
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-18 20:55:39 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 352592 ***