Package: libmtp9
Version: 1.1.6-20-g1b9f164-1
Severity: normal
Tags: upstream
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
plugging the handset in via USB cable, selecting Media Transfer on the handset,
and attempting to look at MTP devices in vlc
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
Device 0 (VID=0421 and PID=0595) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
* What outcome did you expect instead?
*** End of the template - remove these lines ***
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500,
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.12.0-rc7 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libmtp9 depends on:
ii dpkg 1.17.1
ii libc6 2.17-93
ii libgcrypt11 1.5.3-2
ii libmtp-common 1.1.6-20-g1b9f164-1
ii libusb-1.0-0 2:1.0.17-1+b1
ii multiarch-support 2.17-93
Versions of packages libmtp9 recommends:
ii libmtp-runtime 1.1.6-20-g1b9f164-1
ii udev 204-5
libmtp9 suggests no packages.
-- debconf-show failed
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
