gvfsd-mtp crashed with SIGSEGV in try_read()

Bug #1117729 reported by Daniel Winzen
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
Medium
Philip Langdale

Bug Description

gvfsd-mtp crashed when deleting a file on my mobile phone. Maybe the connection was broken at this time, because my usb-cable is not the best anymore.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Wed Feb 6 22:45:18 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2012-04-03 (308 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120403)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/4
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x40440b: mov 0x8(%rax),%rdi
 PC (0x0040440b) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? ()
 g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Daniel Winzen (q-d-deactivatedaccount) wrote :
information type: Private → Public
Changed in gvfs (Ubuntu):
assignee: nobody → Philip Langdale (langdalepl)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gvfs (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 try_read (backend=<optimized out>, job=<optimized out>, handle=<optimized out>, buffer=<optimized out>, bytes_requested=<optimized out>) at gvfsbackendmtp.c:1503
 do_query_info (backend=0x7f9474040d20, job=0x7f948800a9f0, filename=<optimized out>, flags=<optimized out>, info=0x7f9474042900, matcher=<optimized out>) at gvfsbackendmtp.c:1002
 g_vfs_job_run (job=0x7f948800a9f0) at gvfsjob.c:197
 job_handler_callback (data=<optimized out>, user_data=<optimized out>) at gvfsdaemon.c:184
 g_thread_pool_push (pool=0x13b15f0, data=<optimized out>, error=<optimized out>) at /build/buildd/glib2.0-2.35.7/./glib/gthreadpool.c:548

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
summary: - gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()
+ gvfsd-mtp crashed with SIGSEGV in try_read()
tags: removed: need-amd64-retrace
Revision history for this message
Philip Langdale (langdalepl) wrote :

The backtrace doesn't make any sense. do_query_info never calls try_read, and the outer frames also show clear signs of corruption, so I don't think we can rely on much in it - as such I don't think we even know what function the crash occured in.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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