Bug 469623 – crash in Computer: I moved files from the l...

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 469623 - crash in Computer: I moved files from the l...


Summary:	crash in Computer: I moved files from the l...


Status:	RESOLVED DUPLICATE of bug 434337

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-23 15:20 UTC by pinter.sandor
Modified:	2007-08-23 17:51 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description pinter.sandor 2007-08-23 15:20:42 UTC

Version: 2.18.3

What were you doing when the application crashed?
I moved files from the local hard drive, to an external hard drive NTFS partition. I didn't have permission to move, a dialog infermed me about this. It crashed, after I closed that dialog


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 105840640 vsize: 105840640 resident: 44904448 share: 18030592 rss: 44904448 rss_rlim: 4294967295
CPU usage: start_time: 1187880887 rtime: 8533 utime: 6316 stime: 2217 cutime:484 cstime: 64 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226245568 (LWP 4945)]
[New Thread -1237668976 (LWP 6505)]
(no debugging symbols found)
0xb7fda7f2 in ?? () from /lib/ld-linux.so.2

+ Trace 157394

Thread 2 (Thread -1237668976 (LWP 6505))

#0 ??
from /lib/ld-linux.so.2
#1 __waitpid_nocancel
from /lib/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gnome_vfs_find_directory
from /usr/lib/libgnomevfs-2.so.0
#5 gnome_vfs_get_file_info_from_handle_cancellable
from /usr/lib/libgnomevfs-2.so.0
#6 gnome_vfs_get_file_info_from_handle
from /usr/lib/libgnomevfs-2.so.0
#7 gnome_vfs_xfer_delete_list
from /usr/lib/libgnomevfs-2.so.0
#8 gnome_vfs_xfer_delete_list
from /usr/lib/libgnomevfs-2.so.0
#9 gnome_vfs_xfer_delete_list
from /usr/lib/libgnomevfs-2.so.0
#10 gnome_vfs_xfer_delete_list
from /usr/lib/libgnomevfs-2.so.0
#11 gnome_vfs_xfer_uri
from /usr/lib/libgnomevfs-2.so.0
#12 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
#18 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#19 ??
#20 nautilus_file_operations_empty_trash
#21 gnome_vfs_async_set_job_limit
from /usr/lib/libgnomevfs-2.so.0
#22 g_thread_pool_push
from /usr/lib/libglib-2.0.so.0
#23 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#24 start_thread
from /lib/i686/cmov/libpthread.so.0
#25 clone
from /lib/i686/cmov/libc.so.6



----------- .xsession-errors (13 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Xlib: unexpected async reply (sequence 0xfda19)!
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------

Comment 1 André Klapper 2007-08-23 17:51:50 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 434337 ***