[Kernel-packages] [Bug 1464969] [NEW] Unable to import photos from Samsung Galaxy Note 3
Public bug reported: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a "Could not claim USB device (-53)" error, which when dismissed just displays a "Starting import please wait" message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp- detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect, device number 2 [ 28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 28.375249] usb 1-2: Product: SAMSUNG_Android [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 2. Kill any gvfs processes that might interfere with with mtp-detect msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 3. Make sure phone is unlocked and run mtp-detect: msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 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. 4. Check dmesg output: msharman@laptop-msharman:~$ dmesg | tail [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 [ 88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 88.681995] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 88.681999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 88.682000] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 [ 217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 217.885218] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 217.885227] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 217.885230] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 It looks like there could be an xhci related kernel bug? So I tried using a newer mainline kernel: http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.0-vivid/linux- image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb With this kernel I get different dmesg output but the mtp-detect still fails (following the exact same procedure as above but I'm just showing the differences here) (running kernel 4.0.0) msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): No such device outep: usb_get_endpoint_status(): No such device libusb_open() failed!: No such device LIBMTP PANIC: Could not init USB on second attempt Unable to open raw device 0 OK. msharman@laptop-msharman:~$ dmesg | tail [ 212.229605] usb 2-2: Product: SAMSUNG_Android [ 212.229608] usb 2-2: Manufacturer: SAMSUNG [ 212.229610] usb 2-2: SerialNumber: 2410ba56 [ 215.164011] usb 2-2: USB disconnect, device number 2 [ 215.503911] usb 1-2: new high-speed USB device number 5 using xhci_hcd [ 215.634182] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 215.634189] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 215.634193] usb 1-2: Product: SAMSUNG_Android [ 215.634196] usb 1-2: Manufacturer: SAMSUNG [ 215.634198] usb 1-2: SerialNumber: 2410ba56 So upgrading to kernel 4.0 hasdone something it's fixed the xhci_hcd related errors but the mtp-detect is still failing (I've tried gphoto2 -L as well and got similar results). So I'm not which package the bug is in: could kernel, libmtp, libusb or somethings else ? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USER
[Kernel-packages] [Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
sorry this is the same as https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1464968 I just wantes to make sure the correct kernel related information was submitted since I think this is likely a kernel issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 Status in linux package in Ubuntu: New Bug description: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a "Could not claim USB device (-53)" error, which when dismissed just displays a "Starting import please wait" message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp-detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect, device number 2 [ 28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 28.375249] usb 1-2: Product: SAMSUNG_Android [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 2. Kill any gvfs processes that might interfere with with mtp-detect msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 3. Make sure phone is unlocked and run mtp-detect: msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 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. 4. Check dmesg output: msharman@laptop-msharman:~$ dmesg | tail [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 [ 88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 88.681995] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 88.681999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 88.682000] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 [ 217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 217.885218] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 217.885227] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 217.885230] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 It looks like there could be an xhci related kernel bug? So I tried using a newer mainline kernel: http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.0-vivid/linux- image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb With this kernel I get different dmesg output but the mtp-detect still fails (following the exact same procedure as above but I'm just showing the differences here) (running kernel 4.0.0) msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): No such device outep: usb_get_endpoint_status(): No such device libusb_open() failed!: No such device LIBMTP PANIC: Could not init USB on second attempt Unable to open raw device 0 OK. msharman@laptop-msharman:~$ dmesg | tail [ 212.229605] usb 2-2: Product: SAMSUNG_Android [ 212.229608] usb 2-2: Manufacturer: SAMSUNG [ 212.229610] usb 2-2: SerialNumber: 2410ba56 [ 215.164011] usb 2-2: USB disconnect, device number 2 [ 215.503911] usb 1-2: new high-speed USB device number 5 using xhci_hcd [ 215.634182] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 215.634189] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 215.634193] usb 1-2: Product: SAMSUNG_Androi
[Kernel-packages] [Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
I just tried with the latest mainline kernel: 4.1.0-040100rc7-generic Got the same result but different dmesg output: [ 29.767220] usb 1-2: USB disconnect, device number 2 [ 32.307137] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 32.436267] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 32.436272] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 32.436274] usb 1-2: Product: SAMSUNG_Android [ 32.436276] usb 1-2: Manufacturer: SAMSUNG [ 32.436278] usb 1-2: SerialNumber: 2410ba56 [ 52.986605] usb 1-2: usbfs: process 2070 (mtp-detect) did not claim interface 0 before use [ 53.098907] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 53.227897] usb 1-2: usbfs: process 2070 (mtp-detect) did not claim interface 0 before use [ 53.395019] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 53.525020] usb 1-2: usbfs: process 2070 (mtp-detect) did not claim interface 0 before use [ 53.525248] usb 1-2: usbfs: process 2070 (mtp-detect) did not claim interface 0 before use [ 133.385180] usb 1-2: usbfs: process 2147 (pool) did not claim interface 0 before use [ 133.497291] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 133.627167] usb 1-2: usbfs: process 2147 (pool) did not claim interface 0 before use [ 133.793254] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 133.922914] usb 1-2: usbfs: process 2147 (pool) did not claim interface 0 before use [ 133.923082] usb 1-2: usbfs: process 2147 (pool) did not claim interface 0 before use -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 Status in linux package in Ubuntu: Confirmed Bug description: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a "Could not claim USB device (-53)" error, which when dismissed just displays a "Starting import please wait" message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp-detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect, device number 2 [ 28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 28.375249] usb 1-2: Product: SAMSUNG_Android [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 2. Kill any gvfs processes that might interfere with with mtp-detect msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 3. Make sure phone is unlocked and run mtp-detect: msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 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. 4. Check dmesg output: msharman@laptop-msharman:~$ dmesg | tail [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 [ 88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 88.681995] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 88.681999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 88.682000] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 [ 217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 217.885218] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 217.885227] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 217.885230] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 It looks like there could be an xhci related kernel bug? So I tried using a newer mainline kernel: http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.0-vivid/linux- image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb With this kernel I get different dmesg outpu
[Kernel-packages] [Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
Also tried kernel 3.12.43-031243-generic still failed, dmesg output now: [ 18.855676] usb 3-2: USB disconnect, device number 2 [ 64.721133] usb 3-2: new high-speed USB device number 4 using xhci_hcd [ 64.739469] usb 3-2: New USB device found, idVendor=04e8, idProduct=6860 [ 64.739474] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 64.739476] usb 3-2: Product: SAMSUNG_Android [ 64.739477] usb 3-2: Manufacturer: SAMSUNG [ 64.739479] usb 3-2: SerialNumber: 2410ba56 [ 132.665779] usb 3-2: usbfs: process 2073 (pool) did not claim interface 0 before use [ 132.831567] usb 3-2: reset high-speed USB device number 4 using xhci_hcd [ 132.848744] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad1c0 [ 132.848749] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad180 [ 132.848752] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad200 [ 132.849369] usb 3-2: usbfs: process 2073 (pool) did not claim interface 0 before use [ 133.015400] usb 3-2: reset high-speed USB device number 4 using xhci_hcd [ 133.032709] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad1c0 [ 133.032715] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad180 [ 133.032717] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad200 [ 133.033430] usb 3-2: usbfs: process 2073 (pool) did not claim interface 0 before use [ 133.033564] usb 3-2: usbfs: process 2073 (pool) did not claim interface 0 before use -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 Status in linux package in Ubuntu: Confirmed Bug description: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a "Could not claim USB device (-53)" error, which when dismissed just displays a "Starting import please wait" message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp-detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect, device number 2 [ 28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 28.375249] usb 1-2: Product: SAMSUNG_Android [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 2. Kill any gvfs processes that might interfere with with mtp-detect msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 3. Make sure phone is unlocked and run mtp-detect: msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 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. 4. Check dmesg output: msharman@laptop-msharman:~$ dmesg | tail [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 [ 88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 88.681995] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 88.681999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 88.682000] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 [ 217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 217.885218] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 217.885227] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 217.885230] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 It looks like there could be an xhci related kernel bug? So I tried using a newer mainline kernel: http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.0-vivid/linux- image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb
[Kernel-packages] [Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
** Attachment added: "output when mtp-detect works after resetting device" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+attachment/4415375/+files/mtp-detect-out.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 Status in linux package in Ubuntu: Confirmed Bug description: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a "Could not claim USB device (-53)" error, which when dismissed just displays a "Starting import please wait" message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp-detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect, device number 2 [ 28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 28.375249] usb 1-2: Product: SAMSUNG_Android [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 2. Kill any gvfs processes that might interfere with with mtp-detect msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 3. Make sure phone is unlocked and run mtp-detect: msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 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. 4. Check dmesg output: msharman@laptop-msharman:~$ dmesg | tail [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 [ 88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 88.681995] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 88.681999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 88.682000] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 [ 217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 217.885218] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 217.885227] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 217.885230] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 It looks like there could be an xhci related kernel bug? So I tried using a newer mainline kernel: http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.0-vivid/linux- image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb With this kernel I get different dmesg output but the mtp-detect still fails (following the exact same procedure as above but I'm just showing the differences here) (running kernel 4.0.0) msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): No such device outep: usb_get_endpoint_status(): No such device libusb_open() failed!: No such device LIBMTP PANIC: Could not init USB on second attempt Unable to open raw device 0 OK. msharman@laptop-msharman:~$ dmesg | tail [ 212.229605] usb 2-2: Product: SAMSUNG_Android [ 212.229608] usb 2-2: Manufacturer: SAMSUNG [ 212.229610] usb 2-2: SerialNumber: 2410ba56 [ 215.164011] usb 2-2: USB disconnect, device number 2 [ 215.503911] usb 1-2: new high-speed USB device number 5 using xhci_hcd [ 215.634182] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 215.634189] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 215.634193] usb 1-2: Product: SAMSUNG_Android [ 215.634196] us
[Kernel-packages] [Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
msharman@laptop-msharman:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date N56VM.214 08/28/2012 Thanks, for some reason it didn't occur to me to check for out dated BIOS. I've updated the BIOS to the 214 version which indeed has made a significant change. Ubuntu now attachs to the phone with the file manager when it is plugged in. Add if I eject the phone (to avoid the device can not be claimed error in Shotwell) then Shotwell is now able to read the previews of the photos and import the photos - which is much better. However, it isn't stable, I gave the mtp-detect process above a go after a reboot and the result is better but there were some errors I've attached the output as the file "mtp-detect-out.txt" and also there are still errors in the dmesg I've attached the complete dmesg output as "dmesg-out.txt" Interestingly after repeating the above mtp-detect hangs as it attempts to reset the device: msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ mtp-detect (output attached as mtp-detect-out.txt) dmesg output: [ 51.197549] usb 1-4: USB disconnect, device number 3 [ 54.520400] usb 1-4: new high-speed USB device number 4 using xhci_hcd [ 54.649665] usb 1-4: New USB device found, idVendor=04e8, idProduct=6860 [ 54.649672] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 54.649676] usb 1-4: Product: SAMSUNG_Android [ 54.649679] usb 1-4: Manufacturer: SAMSUNG [ 54.649682] usb 1-4: SerialNumber: 2410ba56 [ 131.389969] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use [ 131.501544] usb 1-4: reset high-speed USB device number 4 using xhci_hcd [ 131.630174] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88022409da48 [ 131.630180] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88022409da00 [ 131.630184] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88022409da90 [ 131.630628] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use [ 131.630712] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630828] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630841] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630856] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630872] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630900] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.631012] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10 Attempting to connect device(s) Seems to hang here. For reference my list of steps is now: 1. Plug in device 2. Click "Eject" when notification about device attached appears (otherwise will get an error about device being claimed). 3. Kill gvfs processes because they stop mtp-detect from working. msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 5. Make sure phone is unlocked and then run mtp-detect Works but has errors. 5. Make sure phone is unlocked and then run mtp-detect a second time. This time it hangs. As before I tried updating to the most recent mainline kernel 4.1rc7 but the same symptoms were present the dmesg output was different again (I've attached this as dmesg-out-41.rc7.txt) ** Attachment added: "dmesg output kernel 3.19.0-20" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+attachment/4415376/+files/dmesg-out.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 Status in linux package in Ubuntu: Confirmed Bug description: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a "Could not claim USB device (-53)" error, which when dismissed just displays a "Starting import please wait" message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp-detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB
[Kernel-packages] [Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
** Attachment added: "dmesg output kernel 4.1rc7 for comparison" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+attachment/4415377/+files/dmesg-out-4.1rc7.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 Status in linux package in Ubuntu: Confirmed Bug description: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a "Could not claim USB device (-53)" error, which when dismissed just displays a "Starting import please wait" message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp-detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect, device number 2 [ 28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 28.375249] usb 1-2: Product: SAMSUNG_Android [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 2. Kill any gvfs processes that might interfere with with mtp-detect msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 3. Make sure phone is unlocked and run mtp-detect: msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 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. 4. Check dmesg output: msharman@laptop-msharman:~$ dmesg | tail [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 [ 88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 88.681995] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 88.681999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 88.682000] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 [ 217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 217.885218] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 217.885227] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 217.885230] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 It looks like there could be an xhci related kernel bug? So I tried using a newer mainline kernel: http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.0-vivid/linux- image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb With this kernel I get different dmesg output but the mtp-detect still fails (following the exact same procedure as above but I'm just showing the differences here) (running kernel 4.0.0) msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 4 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): No such device outep: usb_get_endpoint_status(): No such device libusb_open() failed!: No such device LIBMTP PANIC: Could not init USB on second attempt Unable to open raw device 0 OK. msharman@laptop-msharman:~$ dmesg | tail [ 212.229605] usb 2-2: Product: SAMSUNG_Android [ 212.229608] usb 2-2: Manufacturer: SAMSUNG [ 212.229610] usb 2-2: SerialNumber: 2410ba56 [ 215.164011] usb 2-2: USB disconnect, device number 2 [ 215.503911] usb 1-2: new high-speed USB device number 5 using xhci_hcd [ 215.634182] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 215.634189] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 215
[Kernel-packages] [Bug 1966143] [NEW] Periodic glitch in LogiTech H390 headphone audio
Public bug reported: When running kernel version 5.13.0-37-generic the audio output through my Logitech H390 headphones has a periodic "glitch" every few seconds - noticable in Google Meetings and Youtube - its very distracting, its not exactly a scratch or pop; it's more like a really bad reception mobile phone call "robot voice" noise but lasts only for a moment, then maybe 30 seconds later occurs again, seems to be regularly periodic. The problem isn't present on 5.13.0-35-generic and doesn't effect my external speaker audio output just the headphones so it's not a network issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Mar 24 10:26:12 2022 InstallationDate: Installed on 2018-02-17 (1495 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-05-08 (684 days ago) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: When running kernel version 5.13.0-37-generic the audio output through my Logitech H390 headphones has a periodic "glitch" every few seconds - noticable in Google Meetings and Youtube - its very distracting, its not - exactly a scratch or pop, not sure how to describe it. + exactly a scratch or pop; it's more like a really bad reception mobile + phone call "robot voice" noise but lasts only for a moment, then maybe + 30 seconds later occurs again, seems to be regularly peridoic. The problem isn't present on 5.13.0-35-generic and doesn't effect my sound card audio output just the headphones. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Mar 24 10:26:12 2022 InstallationDate: Installed on 2018-02-17 (1495 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-05-08 (684 days ago) ** Description changed: When running kernel version 5.13.0-37-generic the audio output through my Logitech H390 headphones has a periodic "glitch" every few seconds - noticable in Google Meetings and Youtube - its very distracting, its not exactly a scratch or pop; it's more like a really bad reception mobile phone call "robot voice" noise but lasts only for a moment, then maybe - 30 seconds later occurs again, seems to be regularly peridoic. + 30 seconds later occurs again, seems to be regularly periodic. The problem isn't present on 5.13.0-35-generic and doesn't effect my - sound card audio output just the headphones. + external speaker audio output just the headphones so it's not a network + issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Mar 24 10:26:12 2022 InstallationDate: Installed on 2018-02-17 (1495 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-05-08 (684 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1966143 Title: Periodic glitch in LogiTech H390 headphone audio Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: When running kernel version 5.13.0-37-generic the audio output through my Logitech H390 headphones has a periodic "glitch" every few seconds - noticable in Google Meetings and Youtube - its very distracting, its not exactly a scratch or pop; it's more like a really bad reception mobile phone call "robot voice" noise but lasts only for a moment, then maybe 30 seconds later occurs again, seems to be regularly periodic. The problem isn't present on 5.13.0-35-generic and doesn't effect my external speaker audio output just the headphones so it's not a network issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37
