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


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 355547

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-27 10:42 UTC by geraldo.dalberto
Modified:	2006-11-27 20:45 UTC

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

Description geraldo.dalberto 2006-10-27 10:42: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: 88555520 vsize: 0 resident: 88555520 share: 0 rss: 32571392 rss_rlim: 0
CPU usage: start_time: 1161942169 rtime: 0 utime: 137856 stime: 0 cutime:93902 cstime: 0 timeout: 43954 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 -1226463568 (LWP 4440)]
[New Thread -1246311520 (LWP 7471)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 78763

Thread 1 (Thread -1226463568 (LWP 4440))

#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_directory_async_state_changed
#9 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#10 nautilus_directory_async_state_changed
#11 nautilus_directory_ref
#12 nautilus_marshal_BOOLEAN__POINTER
#13 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#14 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#15 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#16 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#17 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#18 POA_Nautilus_MetafileMonitor__init
#19 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#20 ??
#0 __kernel_vsyscall

Comment 1 Behdad Esfahbod 2006-10-31 18:14:03 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 366233 ***

Comment 2 Karsten Bräckelmann 2006-11-12 21:19:59 UTC

Don't see how these stacktraces are the same issue. REOPENing.

Comment 3 Germán Poo-Caamaño 2006-11-27 14:46:12 UTC

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

Comment 4 Germán Poo-Caamaño 2006-11-27 20:45:16 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 355547 ***