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


Summary:	crash in Open Folder:


Status:	RESOLVED INCOMPLETE

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Duplicates:	381350 408943 (view as bug list)
Depends on:
Blocks:

Reported:	2006-12-01 17:35 UTC by maben
Modified:	2007-12-07 16:32 UTC

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

Description maben 2006-12-01 17:35:48 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: 113360896 vsize: 0 resident: 113360896 share: 0 rss: 37982208 rss_rlim: 0
CPU usage: start_time: 1164994117 rtime: 0 utime: 876 stime: 0 cutime:396 cstime: 0 timeout: 480 it_real_value: 0 frequency: 1303

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 -1226807632 (LWP 5130)]
[New Thread -1277936736 (LWP 7879)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 90880

Thread 1 (Thread -1226807632 (LWP 5130))

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

Comment 1 Germán Poo-Caamaño 2006-12-01 18:24:50 UTC

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

Comment 2 André Klapper 2006-12-02 02:50:52 UTC

dup of bug 369188?

Comment 3 André Klapper 2007-02-18 00:02:35 UTC

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

Comment 4 André Klapper 2007-09-13 15:41:04 UTC

Thanks for taking the time to report this bug.
Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui.

More details can be found here: http://live.gnome.org/GettingTraces

Comment 5 André Klapper 2007-12-07 16:32:27 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!