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


Summary:	crash in 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:	2007-04-11 20:15 UTC by oliveira.oliveira
Modified:	2007-04-13 20:54 UTC

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

Description oliveira.oliveira 2007-04-11 20:15:37 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: 102748160 vsize: 0 resident: 102748160 share: 0 rss: 15757312 rss_rlim: 0
CPU usage: start_time: 1176321816 rtime: 0 utime: 77 stime: 0 cutime:70 cstime: 0 timeout: 7 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 -1226750288 (LWP 12701)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 126977

Thread 1 (Thread -1226750288 (LWP 12701))

#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 nautilus_undo_transaction_unregister_object
#16 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#17 nautilus_undo_transaction_unregister_object
#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 nautilus_undo_transaction_unregister_object
#25 nautilus_marshal_BOOLEAN__POINTER
#26 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#27 ??
#28 ??
#29 ??
#30 ??
from /usr/lib/libgthread-2.0.so.0
#31 ??
#32 ??
from /usr/lib/libglib-2.0.so.0
#33 ??
#34 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#35 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#36 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#37 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#38 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#39 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#40 POA_Nautilus_MetafileMonitor__init
#41 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#42 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-04-13 20:54:33 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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