On Sat, Oct 17, 2015 at 08:19:13PM +0200, Daniel Bauer wrote:
Am 17.10.2015 um 20:11 schrieb Marcus Meissner:
On Sat, Oct 17, 2015 at 07:59:02PM +0200, Daniel Bauer wrote:
Am 17.10.2015 um 19:50 schrieb Marcus Meissner:
Hi,
what is the device? USB ids?
Does mtp-detect work?
This is what I get:
venus:~ # mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.7
Listing raw device(s) Device 0 (VID=1782 and PID=4001) is UNKNOWN. Please report this VID/PID and the device model to the libmtp development team Found 1 device(s): 1782:4001 @ bus 2, dev 48 Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
:-( ???
(ID is in 1.1.9 libmtp release, but as you run as root it should work ...)
1.1.7 is the latest I see in Yast... (I only run these commands in a root console to be sure it'snot because of a user restriction)
Can you try: ps auxw|grep mtp
this: venus:~ # ps auxw|grep mtp daniel 10323 0.0 0.0 186892 5436 ? Sl Oct13 0:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor root 25608 0.0 0.0 9268 1628 pts/3 S+ 20:16 0:00 grep --color=auto mtp
The /usr/lib/gvfs/gvfs-mtp-volume-monitor might block the device. Can you kill this process and see if that helps? Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org