Bug 516715 – crash in Home Folder: adding files ( dvd ) to ...

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 516715 - crash in Home Folder: adding files ( dvd ) to ...


Summary:	crash in Home Folder: adding files ( dvd ) to ...


Status:	RESOLVED DUPLICATE of bug 389760

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-02-15 18:23 UTC by chucky_2k4
Modified:	2008-02-17 01:38 UTC

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

Description chucky_2k4 2008-02-15 18:23:32 UTC

What were you doing when the application crashed?
adding files ( dvd ) to nautilus-cd-burner


Distribution: Debian 4.0
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Gion

Memory status: size: 77467648 vsize: 77467648 resident: 25833472 share: 15060992 rss: 25833472 rss_rlim: 4294967295
CPU usage: start_time: 1203099710 rtime: 103 utime: 93 stime: 10 cutime:0 cstime: 0 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 -1228876096 (LWP 6509)]
[New Thread -1246561392 (LWP 6592)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 189326

Thread 2 (Thread -1246561392 (LWP 6592))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
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 gtk_module_init
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 mapping_protocol_channel_ref
from /usr/lib/gnome-vfs-2.0/modules/libmapping.so
#12 mapping_protocol_reply_decode
from /usr/lib/gnome-vfs-2.0/modules/libmapping.so
#13 vfs_module_shutdown
from /usr/lib/gnome-vfs-2.0/modules/libmapping.so
#14 vfs_module_shutdown
from /usr/lib/gnome-vfs-2.0/modules/libmapping.so
#15 gnome_vfs_create_symbolic_link_cancellable
from /usr/lib/libgnomevfs-2.so.0
#16 gnome_vfs_create_symbolic_link
from /usr/lib/libgnomevfs-2.so.0
#17 gnome_vfs_xfer_delete_list
from /usr/lib/libgnomevfs-2.so.0
#18 gnome_vfs_xfer_uri
from /usr/lib/libgnomevfs-2.so.0
#19 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#26 ??
#27 nautilus_directory_ref
#28 gnome_vfs_async_set_job_limit
from /usr/lib/libgnomevfs-2.so.0
#29 g_thread_pool_push
from /usr/lib/libglib-2.0.so.0
#30 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#31 start_thread
from /lib/i686/cmov/libpthread.so.0
#32 clone
from /lib/i686/cmov/libc.so.6



----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0

                                        
Verbonden met daemon in 915 miliseconden.
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** ERROR **: Read E instead of R as handshake
aborting...
Xlib: unexpected async reply (sequence 0x16b2)!
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-02-17 01:38:57 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 389760 ***