gvfsd-fuse crashed with SIGABRT in raise()

Bug #1053810 reported by Mark Campbell
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

This happened when clicking on the eject icon in the Nautilus sidebar that was associated with a server to which a connection had been established. The item for the server in the Nautilus sidebar did correctly disappear. The network connection on the server had been disconnected before clicking on the icon, but this has been the case many times before without causing a crash (so I don't know if that factor is related to the crash). This system is running 12.10 with all updates.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gvfs-fuse 1.13.9-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Thu Sep 20 23:51:47 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-fuse
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120811.1)
ProcCmdline: /usr/lib/gvfs//gvfsd-fuse -f /home/username/.gvfs
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 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
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gvfsd-fuse crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Mark Campbell (campbemw) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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.

visibility: private → public
tags: removed: need-i386-retrace
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.