Bug 378537 – crash in Computer: deleting 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 378537 - crash in Computer: deleting folder


Summary:	crash in Computer: deleting folder


Status:	RESOLVED DUPLICATE of bug 364674

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-23 16:44 UTC by richard.davis
Modified:	2006-11-24 12:52 UTC

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

Description richard.davis 2006-11-23 16:44:24 UTC

What were you doing when the application crashed?
deleting folder


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 104673280 vsize: 0 resident: 104673280 share: 0 rss: 24289280 rss_rlim: 0
CPU usage: start_time: 1164290531 rtime: 0 utime: 7485 stime: 0 cutime:6328 cstime: 0 timeout: 1157 it_real_value: 0 frequency: 2

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208219952 (LWP 2673)]
(no debugging symbols found)
0x0031e402 in __kernel_vsyscall ()

+ Trace 88815

Thread 1 (Thread -1208219952 (LWP 2673))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/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/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 nautilus_file_is_directory
#11 nautilus_file_is_directory
#12 nautilus_file_get_uri
#13 nautilus_directory_async_state_changed
#14 nautilus_directory_async_state_changed
#15 gnome_vfs_async_get_job_limit
from /usr/lib/libgnomevfs-2.so.0
#16 gnome_vfs_async_get_job_limit
from /usr/lib/libgnomevfs-2.so.0
#17 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#19 g_main_context_check
from /lib/libglib-2.0.so.0
#20 g_main_loop_run
from /lib/libglib-2.0.so.0
#21 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#22 POA_Nautilus_MetafileMonitor__init
#23 __libc_start_main
from /lib/libc.so.6
#24 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-11-24 12:52:18 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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