gvfs-gphoto2-volume-monitor crashed with SIGSEGV in libusb_handle_events_timeout_completed()

Bug #1504353 reported by Jack Pogorelsky Jr.
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

gvfs-gphoto2-volume-monitor crashed with SIGSEGV in libusb_handle_events_timeout_completed()

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: gvfs-backends 1.24.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic i686
ApportVersion: 2.19.1-0ubuntu2
Architecture: i386
Date: Thu Oct 8 20:52:38 2015
ExecutablePath: /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
InstallationDate: Installed on 2015-09-26 (12 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150825)
ProcCmdline: /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
SegvAnalysis:
 Segfault happened at: 0xb5b9f39c: mov (%esi),%eax
 PC (0xb5b9f39c) ok
 source "(%esi)" (0x79a63af8) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libusb-1.0.so.0
 ?? () from /lib/i386-linux-gnu/libusb-1.0.so.0
 ?? () from /lib/i386-linux-gnu/libusb-1.0.so.0
 ?? () from /lib/i386-linux-gnu/libusb-1.0.so.0
 libusb_handle_events_timeout_completed () from /lib/i386-linux-gnu/libusb-1.0.so.0
Title: gvfs-gphoto2-volume-monitor crashed with SIGSEGV in libusb_handle_events_timeout_completed()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip fax floppy lpadmin plugdev sambashare sudo tape video

Revision history for this message
Jack Pogorelsky Jr. (cska1911) 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 #1497610, 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.

information type: 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.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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