gvfsd-afc crashed with SIGABRT in g_assertion_message()

Bug #1260921 reported by Saikrishna Arcot
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
Undecided
Ricardo Luiz

Bug Description

I plugged in an iPod Touch, and two windows came up regarding what to do with the two connected volumes. I tried to close them, but at least one crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-backends 1.18.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Fri Dec 13 22:50:21 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-afc
InstallationDate: Installed on 2012-10-19 (420 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-afc --spawner :1.6 /org/gtk/gvfs/exec_spaw/3
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gvfsd-afc crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to saucy on 2013-10-19 (55 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo video wireshark

Revision history for this message
Saikrishna Arcot (saiarcot895) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? () from /tmp/apport_sandbox_8WMoBj/usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gvfs (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libudev1: package version 204-0ubuntu19 dbgsym version 204-0ubuntu18
outdated debug symbol package for libp11-kit-gnome-keyring: package version 3.8.2-0ubuntu3.1 dbgsym version 3.8.2-0ubuntu3

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
Ricardo Luiz (rluiz) wrote :

tHIS CRASH OCCURRED ON THE uBUNTU 14.04 bETA fINAL DISTRIBUTION, VERSION dESKTOP 64X.

Changed in gvfs (Ubuntu):
assignee: nobody → Ricardo Luiz (rluiz)
status: Invalid → Confirmed
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.