Bug 376474 – crash in Open Folder: Moviendo unas fotos

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 376474 - crash in Open Folder: Moviendo unas fotos


Summary:	crash in Open Folder: Moviendo unas fotos


Status:	RESOLVED DUPLICATE of bug 364335

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-11-17 21:52 UTC by girls_teame_23
Modified:	2006-11-17 23:06 UTC

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

Description girls_teame_23 2006-11-17 21:52:55 UTC

What were you doing when the application crashed?
Moviendo unas fotos


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

Memory status: size: 121638912 vsize: 0 resident: 121638912 share: 0 rss: 34484224 rss_rlim: 0
CPU usage: start_time: 1163792418 rtime: 0 utime: 12044 stime: 0 cutime:11170 cstime: 0 timeout: 874 it_real_value: 0 frequency: 747

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 -1226475856 (LWP 23737)]
[New Thread -1338926176 (LWP 30155)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 87329

Thread 1 (Thread -1226475856 (LWP 23737))

#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_ref
#9 nautilus_directory_ref
#10 nautilus_directory_ref
#11 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#12 ??
#13 ??
#14 ??
#15 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#16 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 POA_Nautilus_MetafileMonitor__init
#22 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#23 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-11-17 23:06:47 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 364335 ***