gvfs-udisks2-volume-monitor crashed with SIGSEGV in g_simple_async_result_complete()

Bug #1245943 reported by magowiz
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

error on gnome-shell startup

$ lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10

apt-cache policy gvfs
gvfs:
  Installed: 1.18.2-0ubuntu1
  Candidate: 1.18.2-0ubuntu1
  Version table:
 *** 1.18.2-0ubuntu1 0
        500 http://it.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-daemons 1.18.2-0ubuntu1 [modified: usr/lib/gvfs/gvfs-udisks2-volume-monitor usr/lib/gvfs/gvfsd usr/lib/gvfs/gvfsd-burn usr/lib/gvfs/gvfsd-computer usr/lib/gvfs/gvfsd-localtest usr/lib/gvfs/gvfsd-metadata usr/lib/gvfs/gvfsd-trash]
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Tue Oct 22 16:22:32 2013
ExecutablePath: /usr/lib/gvfs/gvfs-udisks2-volume-monitor
ExecutableTimestamp: 1380896804
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfs-udisks2-volume-monitor
ProcCwd: /
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=it
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x4119cc: mov 0x18(%rax),%rdi
 PC (0x004119cc) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfs-udisks2-volume-monitor crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to saucy on 2013-10-17 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

StacktraceTop:
 unmount_cb (source_object=<optimized out>, res=0x1da6ec0, user_data=0x1ddb8c0) at gvfsudisks2mount.c:844
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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 libsystemd-login0: package version 204-0ubuntu19 dbgsym version 204-0ubuntu18

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
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.