gvfsd-trash crashed with SIGSEGV in _g_dbus_append_file_attribute()

Bug #206747 reported by Charles Duffy (M1)
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs
Expired
Critical
gvfs (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

Automatically generated crash report; occurred shortly after starting a new GNOME session; do not know of any specific user actions preceding the failure.

ProblemType: Crash
Architecture: amd64
Date: Tue Mar 25 14:36:26 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
NonfreeKernelModules: nvidia
Package: gvfs-backends 0.2.1-1ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_spaw/0
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 _g_dbus_append_file_attribute ()
 _g_dbus_append_file_info ()
 ?? ()
 ?? ()
 g_closure_invoke ()
Title: gvfsd-trash crashed with SIGSEGV in _g_dbus_append_file_attribute()
Uname: Linux 2.6.24-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy kvm libvirtd lpadmin netdev plugdev powerdev sambashare scanner video

Tags: apport-crash

Related branches

Revision history for this message
Charles Duffy (M1) (cduffy-messageone) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_g_dbus_append_file_info (iter=0x42563880, info=0x63a2c0) at gvfsdaemonprotocol.c:336
create_reply (job=<value optimized out>, connection=<value optimized out>,
send_reply (job=0x65b040) at gvfsjobdbus.c:166
IA__g_closure_invoke (closure=0x63adc0, return_value=0x0, n_param_values=1,
signal_emit_unlocked_R (node=0x63d1d0, detail=0, instance=0x65b040,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gvfs:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=524517

Changed in gvfs:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in gvfs:
status: Unknown → New
Changed in gvfs:
status: New → Invalid
Revision history for this message
Pedro Villavicencio (pedro) wrote :

this is going to be fixed in jaunty since the trash backend was completely rewritten upstream, thanks in advance.

Changed in gvfs:
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gvfs - 1.1.3-0ubuntu1

---------------
gvfs (1.1.3-0ubuntu1) jaunty; urgency=low

  * New upstream version:
    - ftp: fix limited number of connections causes commands to fail
    - trash: fix parallel build doesn't work
    - trash: add trash::orig-path and trash::deletion-date info
    - trash: set files to mode 700 before deleting to deal with users trashing
      read-only directories
    - smb-browse: browsing authentication support (lp: #193232, #207072)
    - smb-browse: make backend not automounted anymore
    - New trash backend (lp: #7560, #187565, #201393, #206747, #207835, #216739)
    - Use the new shadow mount facility in gio
    - gphoto2: Use shadow mounts
    - obex: Fix icon for root directory
    - http: Fix major memory leak (lp: #225615)
    - http: Support proxies
  * debian/patches/01_maintainer_mode.patch,
    debian/patches/90_relibtoolize.patch:
    - commented debian change for now since it's not really required and create
      build issue using the jaunty libtool version
  * debian/patches/90_correct_glib_use.patch:
    - the issue is fixed in the new version

 -- Sebastien Bacher <email address hidden> Wed, 07 Jan 2009 22:52:11 +0100

Changed in gvfs:
status: Fix Committed → Fix Released
Changed in gvfs:
importance: Unknown → Critical
status: Invalid → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.