My usual route is to pick one of the more readable error messages and
google that, e.g. "LIBMTP ERROR: couldnt parse extension samsung.com"

On Fri, Mar 2, 2018 at 10:29 AM, Chuck Hast <wch...@gmail.com> wrote:
> Folks,
> I used to be able to access my cell when I plugged it into this machine.
> There
> was and upgrade some time back and after that it would not allow access. I
> am trying to figure out what is going on but no joy.
>
> I know this is a lot of crap, I am trying to figure out what to google to
> see if
> I can resolve it. I usually just plug it into one of my laptops which DO
> see the
> phone and then just move the files off of the phone onto a session with a
> remote screen of the computer that will not see the phone.
>
> ------------------------------- Begin big load of log stuff
> -------------------------------------
>
>
>
> Mar  2 12:19:25 kp4djt64 kernel: [11834.772141] usb 2-1.7.2: new high-speed
> USB device number 11 using ehci-pci
> Mar  2 12:19:25 kp4djt64 kernel: [11834.882834] usb 2-1.7.2: New USB device
> found, idVendor=04e8, idProduct=6860
> Mar  2 12:19:25 kp4djt64 kernel: [11834.882842] usb 2-1.7.2: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
> Mar  2 12:19:25 kp4djt64 kernel: [11834.882845] usb 2-1.7.2: Product:
> SAMSUNG_Android
> Mar  2 12:19:25 kp4djt64 kernel: [11834.882849] usb 2-1.7.2: Manufacturer:
> SAMSUNG
> Mar  2 12:19:25 kp4djt64 kernel: [11834.882852] usb 2-1.7.2: SerialNumber:
> ce0817186b237e2f02
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.GPhoto2VolumeMonitor[4105]:
> (process:4178): GVFS-GPhoto2-WARNING **: device (null) has no BUSNUM
> property, ignoring
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.GPhoto2VolumeMonitor[1912]:
> (process:3220): GVFS-GPhoto2-WARNING **: device (null) has no BUSNUM
> property, ignoring
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.Daemon[1912]: PTP: reading event an
> error 0x02ff occurredDevice 0 (VID=04e8 and PID=6860) is a Samsung Galaxy
> models (MTP).
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.Daemon[4105]: Device 0 (VID=04e8 and
> PID=6860) is a Samsung Galaxy models (MTP).
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.Daemon[4105]: ignoring
> libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying
> again after resetting USB interface
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.Daemon[4105]: LIBMTP libusb: Attempt
> to reset device
> Mar  2 12:19:26 kp4djt64 kernel: [11835.485849] usb 2-1.7.2: usbfs: process
> 27583 (pool) did not claim interface 0 before use
> Mar  2 12:19:26 kp4djt64 kernel: [11835.572113] usb 2-1.7.2: reset
> high-speed USB device number 11 using ehci-pci
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.Daemon[1912]: LIBMTP PANIC: Unable to
> read device information on device 11 on bus 2, trying to continue
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.Daemon[1912]: ** (gvfsd:2939): WARNING
> **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Unable to
> open MTP device '[usb:002,011]'
> Mar  2 12:19:26 kp4djt64 kernel: [11835.682046] usb 2-1.7.2: usbfs: process
> 27583 (pool) did not claim interface 0 before use
> Mar  2 12:19:26 kp4djt64 kernel: [11835.682113] usb 2-1.7.2: usbfs: process
> 27580 (pool) did not claim interface 0 before use
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.Daemon[4105]: LIBMTP ERROR: couldnt
> parse extension samsung.com/devicestatus:1
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.Daemon[4105]: Error 1: Get Storage
> information failed.
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.Daemon[4105]: (process:4370):
> GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)'
> failed
>
>
>
> Mar  2 12:19:43 kp4djt64 kernel: [11853.006731] usb 2-1.7.2: USB
> disconnect, device number 11
> Mar  2 12:19:43 kp4djt64 kernel: [11853.207485] usb 2-1.7.2: new high-speed
> USB device number 12 using ehci-pci
> Mar  2 12:19:44 kp4djt64 kernel: [11853.302885] usb 2-1.7.2: New USB device
> found, idVendor=04e8, idProduct=6860
> Mar  2 12:19:44 kp4djt64 kernel: [11853.302891] usb 2-1.7.2: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3
> Mar  2 12:19:44 kp4djt64 kernel: [11853.302895] usb 2-1.7.2: Product:
> SAMSUNG_Android
> Mar  2 12:19:44 kp4djt64 kernel: [11853.302898] usb 2-1.7.2: Manufacturer:
> SAMSUNG
> Mar  2 12:19:44 kp4djt64 kernel: [11853.302901] usb 2-1.7.2: SerialNumber:
> ce0817186b237e2f02
> Mar  2 12:19:26 kp4djt64 org.gtk.vfs.Daemon[4105]: message repeated 2
> times: [ (process:4370): GLib-GObject-CRITICAL **: g_object_unref:
> assertion 'G_IS_OBJECT (object)' failed]
> Mar  2 12:19:44 kp4djt64 org.gtk.vfs.GPhoto2VolumeMonitor[1912]:
> (process:3220): GVFS-GPhoto2-WARNING **: device (null) has no BUSNUM
> property, ignoring
> Mar  2 12:19:44 kp4djt64 org.gtk.vfs.GPhoto2VolumeMonitor[4105]:
> (process:4178): GVFS-GPhoto2-WARNING **: device (null) has no BUSNUM
> property, ignoring
> Mar  2 12:19:44 kp4djt64 org.gtk.vfs.Daemon[1912]: Device 0 (VID=04e8 and
> PID=6860) is a Samsung Galaxy models (MTP).
> Mar  2 12:19:44 kp4djt64 org.gtk.vfs.Daemon[4105]: PTP: reading event an
> error 0x02ff occurredDevice 0 (VID=04e8 and PID=6860) is a Samsung Galaxy
> models (MTP).
> Mar  2 12:19:44 kp4djt64 org.gtk.vfs.Daemon[1912]: ignoring
> libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying
> again after resetting USB interface
> Mar  2 12:19:44 kp4djt64 org.gtk.vfs.Daemon[1912]: LIBMTP libusb: Attempt
> to reset device
> Mar  2 12:19:44 kp4djt64 kernel: [11853.920256] usb 2-1.7.2: usbfs: process
> 27671 (pool) did not claim interface 0 before use
> Mar  2 12:19:44 kp4djt64 kernel: [11854.007407] usb 2-1.7.2: reset
> high-speed USB device number 12 using ehci-pci
> Mar  2 12:19:44 kp4djt64 org.gtk.vfs.Daemon[4105]: PTP_ERROR_IO: failed to
> open session, trying again after resetting USB interface
> Mar  2 12:19:44 kp4djt64 org.gtk.vfs.Daemon[4105]: LIBMTP libusb: Attempt
> to reset device
> Mar  2 12:19:44 kp4djt64 kernel: [11854.120185] usb 2-1.7.2: usbfs: process
> 27671 (pool) did not claim interface 0 before use
> Mar  2 12:19:44 kp4djt64 kernel: [11854.199399] usb 2-1.7.2: reset
> high-speed USB device number 12 using ehci-pci
> Mar  2 12:19:45 kp4djt64 kernel: [11854.310451] usb 2-1.7.2: usbfs: process
> 27671 (pool) did not claim interface 0 before use
> Mar  2 12:19:45 kp4djt64 kernel: [11854.310635] usb 2-1.7.2: usbfs: process
> 27671 (pool) did not claim interface 0 before use
> Mar  2 12:19:45 kp4djt64 org.gtk.vfs.Daemon[1912]: outep:
> usb_get_endpoint_status(): Device or resource busy
> Mar  2 12:19:45 kp4djt64 org.gtk.vfs.Daemon[1912]: ignoring
> libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second
> attempt
> Mar  2 12:19:45 kp4djt64 org.gtk.vfs.Daemon[1912]: ** (gvfsd:2939): WARNING
> **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Unable to
> open MTP device '[usb:002,012]'
> Mar  2 12:19:45 kp4djt64 org.gtk.vfs.Daemon[4105]: LIBMTP ERROR: couldnt
> parse extension samsung.com/devicestatus:0
> Mar  2 12:19:45 kp4djt64 org.gtk.vfs.Daemon[4105]: (process:4370):
> GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)'
> failed
>
> ----------------------------------- End of big load of log stuff
> ------------------------
>
> I have looked at several options based on what I see but no joy...
>
>
> --
>
> Chuck Hast  -- KP4DJT --
> I can do all things through Christ which strengtheneth me.
> Ph 4:13 KJV
> Todo lo puedo en Cristo que me fortalece.
> Fil 4:13 RVR1960
> _______________________________________________
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
_______________________________________________
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to