Bug 524000 – crash in Computer:

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 524000 - crash in Computer:


Summary:	crash in Computer:


Status:	RESOLVED DUPLICATE of bug 466867

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-03-23 16:12 UTC by geoffroy.canquelain
Modified:	2008-03-24 14:12 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description geoffroy.canquelain 2008-03-23 16:12:24 UTC

Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-486 #1 Mon Feb 11 13:52:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 79810560 vsize: 79810560 resident: 26726400 share: 17268736 rss: 26726400 rss_rlim: 4294967295
CPU usage: start_time: 1206270785 rtime: 477 utime: 421 stime: 56 cutime:8 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b3c720 (LWP 3467)]
[New Thread 0xb5e31b90 (LWP 5884)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 193145

Thread 2 (Thread 0xb5e31b90 (LWP 5884))

#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 __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 append_args_valist
at gnome-vfs-daemon-method.c line 559
#12 execute_operation
at gnome-vfs-daemon-method.c line 613
#13 do_write
at gnome-vfs-daemon-method.c line 1008
#14 _gnome_vfs_handle_do_write
at gnome-vfs-handle.c line 154
#15 gnome_vfs_write_cancellable
at gnome-vfs-cancellable-ops.c line 167
#16 gnome_vfs_write
at gnome-vfs-ops.c line 241
#17 copy_file
at gnome-vfs-xfer.c line 1271
#18 copy_items
at gnome-vfs-xfer.c line 1852
#19 gnome_vfs_xfer_uri_internal
at gnome-vfs-xfer.c line 2595
#20 _gnome_vfs_xfer_private
at gnome-vfs-xfer.c line 2681
#21 _gnome_vfs_job_execute
at gnome-vfs-job.c line 1557
#22 thread_entry_point
at gnome-vfs-job-queue.c line 65
#23 ??
from /usr/lib/libglib-2.0.so.0
#24 ??
#25 ??



----------- .xsession-errors ---------------------
** Message: Hit unexpected error "Opération non prise en charge" while doing a file operation.
** Message: Hit unexpected error "Opération non prise en charge" while doing a file operation.
** Message: Hit unexpected error "Opération non prise en charge" while doing a file operation.
process 3467: arguments to dbus_message_iter_append_fixed_array() were incorrect, assertion "n_elements >= 0" failed in file dbus-message.c line 2304.
This is normally a bug in some application using the D-Bus library.
libgnomevfs-ERROR **: Out of memory
aborting...
Xlib: unexpected async reply (sequence 0x8d1d)!
warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libgstreamer-0.10.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-03-24 14:12:00 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 466867 ***