'Now' I regret not keeping the notes when I setup an iPhone rule for someone last year! :/ This time I will.
On 26/11/14 14:04, Marc Shapiro wrote: > On 11/24/2014 02:39 AM, Scott Ferguson wrote: >> Thanks for the replies. >> >> On 24/11/14 05:12, Marc Shapiro wrote: >>> On 11/23/2014 12:23 AM, Scott Ferguson wrote: >>>> Briefly as it's been 40 degrees Celsius here and I've been outside >>>> working all day (almost beer o'clock) >>>> >>>> On 23/11/14 18:27, Marc Shapiro wrote: >>>>> On 11/22/2014 04:09 PM, Scott Ferguson wrote: >>>>>> On 23/11/14 09:50, Marc Shapiro wrote: >>>>>>> My daughter has recently purchased an iPod Touch and would like >>>>>>> to be >>>>>>> able to maintain it from our linux box running Wheezy. <snipped> >>> I will try the "udevadm monitor --property" command once I have the >>> device available again. >>> >>> Marc >>> >>> >> > This is the result of plugging the device in while running "udevadm > monitor --property", waiting a minute or so, and then unplugging the > device: Did you miss something? That appears to be just the tail end of the output? Make sure you have udevadm running *before* you plug the device in. My apologies if I didn't make that clear earlier. > > > UDEV [275538.578940] remove Says that udevadmn detect a device being removed... I don't understand how it can detect a removal, without previously having detected an addition. And addition (plugging the device in) is a block that begins with ([nnnnnn:nnnnnn] is time of event) this:- UDEV [nnnnnn:nnnnnn] add > /devices/pci0000:00/0000:00:16.2/usb4/4-4/4-4.4/4-4.4:4.2 (usb) > ACTION=remove > DEVPATH=/devices/pci0000:00/0000:00:16.2/usb4/4-4/4-4.4/4-4.4:4.2 > DEVTYPE=usb_interface > INTERFACE=255/253/1 > MODALIAS=usb:v05ACp12AAd0510dc00dsc00dp00icFFiscFDip01in02 > PRODUCT=5ac/12aa/510 > SEQNUM=1785 > SUBSYSTEM=usb > TYPE=0/0/0 > UDEV_LOG=7 > USEC_INITIALIZED=275538570017 > > UDEV [275538.584890] remove > /devices/pci0000:00/0000:00:16.2/usb4/4-4/4-4.4 (usb) > ACTION=remove > BUSNUM=004 > COLORD_DEVICE=1 > COLORD_KIND=camera > DEVNAME=/dev/bus/usb/004/019 there's the device > DEVNUM=019 > DEVPATH=/devices/pci0000:00/0000:00:16.2/usb4/4-4/4-4.4 > DEVTYPE=usb_device > GPHOTO2_DRIVER=PTP looks like gphoto2 (a GNOME app?) released it, note that COLORD_KIND 'had' recognised the device as a camera. Try plugging the device back in and opening gPhoto (assuming go do indeed have it installed. > ID_BUS=usb > ID_GPHOTO2=1 > ID_MODEL=iPod > ID_MODEL_ENC=iPod > ID_MODEL_ID=12aa > ID_REVISION=0510 > ID_SERIAL=Apple_Inc._iPod_ea1f2a0800d76f91f9bc0d50d6620151d249e6a9 > ID_SERIAL_SHORT=ea1f2a0800d76f91f9bc0d50d6620151d249e6a9 > ID_USB_INTERFACES=:060101:010100:010200:030000:fffe02:fffd01: > ID_VENDOR=Apple_Inc. > ID_VENDOR_ENC=Apple\x20Inc. > ID_VENDOR_ID=05ac > MAJOR=189 > MINOR=402 > PRODUCT=5ac/12aa/510 > SEQNUM=1786 > SUBSYSTEM=usb That may be the fail in the speculative udev rule I supplied in an earlier post. But I'll wait until I hear about gPhoto and look at the udevadm monitor results showing the device being added before changing that rule (I'm still concerned about battling with GNOME's vfs). > TAGS=:udev-acl: > TYPE=0/0/0 > UDEV_LOG=7 > USBMUX_SUPPORTED=1 > USEC_INITIALIZED=275471311002 > > > It's mostly Greek to me, but if it gives you any hints I will be glad to > hear it. Please see if you can grab the start of udevadm output. As a "user":- udevadm monitor --udev > ~/monitor_output_for_scott after a minute remove the device, use Ctrl+C to stop udevadm, then attach ~/monitor_output_for_scott to your reply (if it's not empty). Kind regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547597c8.7040...@gmail.com
