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 510164 - crash in Home Folder:
crash in Home Folder:
Status: RESOLVED DUPLICATE of bug 466867
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 510176 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-17 12:26 UTC by alano.br
Modified: 2008-03-23 12:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description alano.br 2008-01-17 12:26:14 UTC
What were you doing when the application crashed?



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

System: Linux 2.6.22-3-amd64 #1 SMP Mon Nov 12 10:28:43 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: gnome

Memory status: size: 78376960 vsize: 78376960 resident: 27815936 share: 15912960 rss: 27815936 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200521186 rtime: 5563 utime: 4247 stime: 1316 cutime:0 cstime: 0 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 0xf6e156b0 (LWP 3729)]
[New Thread 0xf44e4b90 (LWP 13832)]
0xffffe405 in __kernel_vsyscall ()

Thread 2 (Thread 0xf44e4b90 (LWP 13832))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.14.3/glib/gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.14.3/glib/gspawn.c line 677
  • #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 IA__g_logv
    at /tmp/buildd/glib2.0-2.14.3/glib/gmessages.c line 497
  • #10 IA__g_log
    at /tmp/buildd/glib2.0-2.14.3/glib/gmessages.c line 517
  • #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_directory
    at gnome-vfs-xfer.c line 1680
  • #19 copy_directory
    at gnome-vfs-xfer.c line 1685
  • #20 copy_directory
    at gnome-vfs-xfer.c line 1685
  • #21 copy_items
    at gnome-vfs-xfer.c line 1858
  • #22 gnome_vfs_xfer_uri_internal
    at gnome-vfs-xfer.c line 2595
  • #23 _gnome_vfs_xfer_private
    at gnome-vfs-xfer.c line 2681
  • #24 _gnome_vfs_job_execute
    at gnome-vfs-job.c line 1557
  • #25 thread_entry_point
    at gnome-vfs-job-queue.c line 65
  • #26 g_thread_pool_thread_proxy
    at /tmp/buildd/glib2.0-2.14.3/glib/gthreadpool.c line 265
  • #27 g_thread_create_proxy
    at /tmp/buildd/glib2.0-2.14.3/glib/gthread.c line 635
  • #28 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #29 clone
    from /lib/i686/cmov/libc.so.6


----------- .xsession-errors ---------------------
** Message: Hit unexpected error "Parâmetros inválidos" while doing a file operation.
** (gnome-system-monitor:14161): WARNING **: SELinux was found but is not enabled.
** Message: Hit unexpected error "Parâmetros inválidos" while doing a file operation.
** Message: Hit unexpected error "Parâmetros inválidos" while doing a file operation.
** Message: Hit unexpected error "Tempo limite atingido" while doing a file operation.
process 3729: 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 0x1d307)!
warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4
--------------------------------------------------
Comment 1 André Klapper 2008-01-21 12:30:49 UTC
*** Bug 510176 has been marked as a duplicate of this bug. ***
Comment 2 Cosimo Cecchi 2008-03-23 12:04:05 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 ***