Bug 469769 – crash in Home Folder: copiando arquivos. copy...

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 469769 - crash in Home Folder: copiando arquivos. copy...


Summary:	crash in Home Folder: copiando arquivos. copy...


Status:	RESOLVED DUPLICATE of bug 434337

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-08-24 00:37 UTC by darkstrikerd
Modified:	2007-09-06 12:26 UTC

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

Description darkstrikerd 2007-08-24 00:37:38 UTC

What were you doing when the application crashed?
copiando arquivos.

copying files.


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: Gentle
Icon Theme: SphereCrystal

Memory status: size: 116543488 vsize: 116543488 resident: 58642432 share: 15818752 rss: 58642432 rss_rlim: 4294967295
CPU usage: start_time: 1187910831 rtime: 7323 utime: 6538 stime: 785 cutime:1066 cstime: 42 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 -1226331856 (LWP 5114)]
[New Thread -1278076016 (LWP 7715)]
(no debugging symbols found)
0xb7fad7f2 in ?? () from /lib/ld-linux.so.2

+ Trace 157502

Thread 2 (Thread -1278076016 (LWP 7715))

#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 ??
#5 gnome_vfs_find_directory
from /usr/lib/libgnomevfs-2.so.0
#6 gnome_vfs_get_file_info_from_handle_cancellable
from /usr/lib/libgnomevfs-2.so.0
#7 gnome_vfs_get_file_info_from_handle
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 (7 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
** Message: drive = 0
** Message: volume = 0
Xlib: unexpected async reply (sequence 0xa62f7)!
--------------------------------------------------

Comment 1 palfrey 2007-09-06 12:26:19 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 434337 ***