Ubuntu
gvfs package

gvfsd-trash crashed with SIGSEGV in g_slice_alloc()

Bug #201393 reported by Dang Kang
44
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gvfs
Expired
Critical
gvfs (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

When I try to empty the trash, the above error occurred.

Version: Hardy Alpha 6

ProblemType: Crash
Architecture: i386
Date: Wed Mar 12 20:27:35 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
NonfreeKernelModules: ath_hal
Package: gvfs-backends 0.2.0.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_spaw/1
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_SG.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 g_datalist_id_set_data_full ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? ()
Title: gvfsd-trash crashed with SIGSEGV in g_slice_alloc()
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash

Related branches

lp:ubuntu/lucid/gvfs
Revision history for this message
Dang Kang (kangdang) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_slice_free1 (mem_size=16, mem_block=0x1)
IA__g_datalist_id_set_data_full (datalist=0x80b7538, key_id=56, data=0x80ba7b8,
IA__g_object_newv (object_type=134968624, n_parameters=134742720, parameters=0x0)
IA__g_type_create_instance (type=134743240)
IA__g_object_set_property (object=0x80804c8, property_name=0x0, value=0x0)

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=522195

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

this is gonna to be fixed on jaunty anyways, since the trash backend was completely re written upstream.

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
Bug Watch Updater (bug-watch-updater)
Changed in gvfs:
importance: Unknown → Critical
status: Invalid → Expired
Revision history for this message
martin suchanek (martin-suc) wrote :

Hi,
this bug appears in 14.04 again.

Revision history for this message
Stephen Cradock (s-cradock) wrote :

Appeared again today in 14.04 2014-04-06

Revision history for this message
martin suchanek (martin-suc) wrote :

It is still in Ubuntu utopic 14.10

Revision history for this message
martin suchanek (martin-suc) wrote :

It is in vivid development branch

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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