Ubuntu
gvfs package

gvfsd-fuse crashed with SIGABRT in raise()

Bug #1057170 reported by Josef Hopfgartner on 2012-09-26

This bug report is a duplicate of: Bug #1053561: gvfsd-fuse assert failure: *** glibc detected *** /usr/lib/gvfs//gvfsd-fuse: double free or corruption (fasttop): 0x00007f79a0022140 ***. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gvfs (Ubuntu)	New	Undecided	Unassigned

Bug Description

error arrived
after closing down a sftp connection

ubuntu 12.10

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gvfs-fuse 1.13.9-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Wed Sep 26 23:53:46 2012
ExecutablePath: /usr/lib/gvfs/gvfsd-fuse
ProcCmdline: /usr/lib/gvfs//gvfsd-fuse -f /home/username/.gvfs
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=de_AT.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
?? () from /lib/ld-linux.so.2
raise () from /lib/i386-linux-gnu/libc.so.6
abort () from /lib/i386-linux-gnu/libc.so.6
?? () from /lib/i386-linux-gnu/libc.so.6
?? () from /lib/i386-linux-gnu/libc.so.6
Title: gvfsd-fuse crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-01-21 (249 days ago)
UserGroups: asterisk audio bacula callweaver cdrom cyberjack dialout dip disk fuse libvirtd lpadmin mldonkey mythtv netdev pcscd plugdev powerdev pulse sambashare scard video

Tags:

Revision history for this message

Josef Hopfgartner (josef-netzagentur) wrote on 2012-09-26:

Dependencies.txt Edit (5.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-26: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1053561, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.