*** This bug is a duplicate of bug 1497610 ***
https://bugs.launchpad.net/bugs/1497610
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.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1568766/+attachment/4632427/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1568766/+attachment/4632429/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1568766/+attachment/4632431/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1568766/+attachment/4632432/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1568766/+attachment/4632433/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1568766/+attachment/4632434/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1568766/+attachment/4632435/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of private bug 1497610
** Information type changed from Private to Public
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1568766
Title:
gvfs-gphoto2-volume-monitor crashed with SIGSEGV in
libusb_handle_events_timeout_completed()
Status in gvfs package in Ubuntu:
New
Bug description:
This just popped up, did not notice anything specific. I have my
lenovo w540 in a dock with two monitors attached, that might be
causing the issue.
The auto generated summary still looks like something related to the
fact that I am charging my phone with a usb cable.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gvfs-backends 1.27.92-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 11 11:40:03 2016
ExecutablePath: /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
InstallationDate: Installed on 2016-03-14 (27 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
ProcCmdline: /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
ProcEnviron:
XDG_RUNTIME_DIR=<set>
SHELL=/bin/bash
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f02bfdf47a0: mov (%rbx),%rdi
PC (0x7f02bfdf47a0) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed
readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
libusb_handle_events_timeout_completed () from
/lib/x86_64-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 dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1568766/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
