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


Summary:	crash on Open Folder


Status:	RESOLVED DUPLICATE of bug 349551

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-03 13:17 UTC by Daniele Medri
Modified:	2006-09-03 21:50 UTC

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

Description Daniele Medri 2006-08-03 13:17:40 UTC

What were you doing when the application crashed?
nothing, just open the desktop environment and nautilus crash due a bonobo error


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.90 2006-07-24 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 73158656 vsize: 0 resident: 73158656 share: 0 rss: 13447168 rss_rlim: 0
CPU usage: start_time: 1154610999 rtime: 0 utime: 69 stime: 0 cutime:66 cstime: 0 timeout: 3 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 -1226512192 (LWP 8129)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 69937

Thread 1 (Thread -1226512192 (LWP 8129))

#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 nautilus_directory_async_state_changed
#10 nautilus_directory_async_state_changed
#11 nautilus_directory_async_state_changed
#12 nautilus_directory_async_state_changed
#13 nautilus_undo_transaction_unregister_object
#14 nautilus_directory_async_state_changed
#15 egg_recent_item_unref
#16 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#17 egg_recent_item_unref
#18 g_cclosure_marshal_VOID__POINTER
from /usr/lib/libgobject-2.0.so.0
#19 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#24 egg_recent_item_unref
#25 nautilus_marshal_BOOLEAN__POINTER
#26 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#27 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#28 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#29 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#30 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 POA_Nautilus_MetafileMonitor__init
#33 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#34 ??
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-08-08 22:21:46 UTC

Thanks for the bug report. Unfortunately, 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.

Comment 2 Sergej Kotliar 2006-09-03 21:50:41 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 349551 ***