Bug 508883 – crash in Home Folder: 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 508883 - crash in Home Folder: copy


Summary:	crash in Home Folder: copy


Status:	RESOLVED DUPLICATE of bug 355018

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:	2008-01-12 03:35 UTC by baryon
Modified:	2008-01-12 11:26 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description baryon 2008-01-12 03:35:49 UTC

What were you doing when the application crashed?
copy


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.1 #1 Thu Nov 8 16:57:44 CST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 87367680 vsize: 87367680 resident: 35774464 share: 20434944 rss: 35774464 rss_rlim: 4294967295
CPU usage: start_time: 1200096402 rtime: 5642 utime: 5278 stime: 364 cutime:320 cstime: 28 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 0xb6d426b0 (LWP 3369)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 185013

Thread 1 (Thread 0xb6d426b0 (LWP 3369))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 strcmp
from /lib/i686/cmov/libc.so.6
#7 ??
#8 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** 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: Hit unexpected error "无效的参数" while doing a file operation.
** Message: drive = 0
** Message: volume = 0
sh: mpg123: command not found
bug-buddy: /usr/local/lib/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-01-12 11:26:22 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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