[Bug 852551] New: No KDE notification of USB mass-storage device (camera Revio KD-200Z)
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c0 Summary: No KDE notification of USB mass-storage device (camera Revio KD-200Z) Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: f.gruber@eduhi.at QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 KDE shows no notification after the digital camera model KD-200Z and also KD-410Z are plugged in over USB. But the devices are recognized by the system. fdisk -l shows the device e.g. as /dev/sdd1 57 29119 4531+ 1 FAT12 But it takes some time after fdisk -l shows this device. The program stops for many seconds before recognizing this device. lsusb -v shows all information about the device. I am able to mount the device as root. This problem occurs since openSuse 12.3 (after some Updates). It did not occur on new installed Suse 12.3. It occurs on several machines with openSuse 12.3 and now I detected this bug also in Suse 13.1 Reproducible: Always Steps to Reproduce: 1. 2. 3. Please look at my forum posting (in German): http://www.linux-club.de/viewtopic.php?f=92&t=118417&sid=ca393683fa632eeb4610f6986d83f1c2&p=750839#p750253 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c1 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |kde-maintainers@suse.de, | |rmilasan@suse.com InfoProvider| |rmilasan@suse.com --- Comment #1 from Dr. Werner Fink <werner@suse.com> 2013-11-28 08:11:01 UTC --- Adding maintainers of digikam (the KDE tool for digital photo management) and the udev expert to Carbon Copy list. @ Robert: Are there any known problem with this digital camera models? It seems that those models provide a USB storage protocol but udev fails to detect them with latest openSUSE 12.3 and current openSUSE 13.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c2 Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|rmilasan@suse.com | --- Comment #2 from Robert Milasan <rmilasan@suse.com> 2013-11-28 08:16:19 UTC --- This is similar to an issue that I saw some time ago, but it was related to kernel and usb subsystem. As I know, it was suppose to be fixed (the kernel that is). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c3 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO CC| |oneukum@suse.com, | |werner@suse.com InfoProvider| |oneukum@suse.com --- Comment #3 from Dr. Werner Fink <werner@suse.com> 2013-11-28 09:00:04 UTC --- Hmmm ... there only problem is the re-assigning to the kernels people will not fix this bug within next few months. I'll add Oliver to Carbon Copy list, let's ask him about this problem. @ Oliver : Are you aware about problems with some USB devices belonging to digital camera models like KD-200Z and KD-410Z? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c4 --- Comment #4 from Robert Milasan <rmilasan@suse.com> 2013-11-28 09:10:40 UTC --- Ferdinand, can you run: udevadm test /sys/device/block/sdd and attach the output information to the bug? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c5 Ferdinand Gruber <f.gruber@eduhi.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|oneukum@suse.com | --- Comment #5 from Ferdinand Gruber <f.gruber@eduhi.at> 2013-11-28 09:37:57 UTC --- (In reply to comment #4)
Ferdinand, can you run:
udevadm test /sys/device/block/sdd
This is the output of the above command: calling: test version 208 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. === trie on-disk === tool version: 208 file size: 5968358 bytes header size 80 bytes strings 1302262 bytes nodes 4666016 bytes load module index read rules file: /usr/lib/udev/rules.d/10-dm.rules read rules file: /run/udev/rules.d/10-root-symlink.rules read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules read rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules read rules file: /usr/lib/udev/rules.d/40-usb_modeswitch.rules read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules read rules file: /usr/lib/udev/rules.d/50-euvccam.rules read rules file: /usr/lib/udev/rules.d/50-firmware.rules read rules file: /usr/lib/udev/rules.d/50-udev-default.rules read rules file: /usr/lib/udev/rules.d/51-android.rules read rules file: /usr/lib/udev/rules.d/51-lirc.rules read rules file: /etc/udev/rules.d/55-libsane.rules read rules file: /usr/lib/udev/rules.d/56-idedma.rules read rules file: /etc/udev/rules.d/56-sane-backends-autoconfig.rules read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules read rules file: /usr/lib/udev/rules.d/60-keyboard.rules read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules read rules file: /usr/lib/udev/rules.d/60-vboxdrv.rules read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules read rules file: /usr/lib/udev/rules.d/61-msft.rules read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules read rules file: /usr/lib/udev/rules.d/64-btrfs.rules read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules read rules file: /usr/lib/udev/rules.d/65-xorg-wacom.rules read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules read rules file: /usr/lib/udev/rules.d/69-libmtp.rules read rules file: /usr/lib/udev/rules.d/69-xorg-vmmouse.rules read rules file: /etc/udev/rules.d/70-kpartx.rules read rules file: /etc/udev/rules.d/70-persistent-net.rules read rules file: /usr/lib/udev/rules.d/70-power-switch.rules read rules file: /usr/lib/udev/rules.d/70-printers.rules read rules file: /usr/lib/udev/rules.d/70-uaccess.rules read rules file: /usr/lib/udev/rules.d/71-seat.rules read rules file: /usr/lib/udev/rules.d/73-seat-late.rules read rules file: /usr/lib/udev/rules.d/73-seat-numlock.rules read rules file: /usr/lib/udev/rules.d/75-net-description.rules read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules read rules file: /usr/lib/udev/rules.d/75-tty-description.rules read rules file: /usr/lib/udev/rules.d/77-mm-ericsson-mbm.rules read rules file: /usr/lib/udev/rules.d/77-mm-huawei-net-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-longcheer-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-nokia-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-pcmcia-device-blacklist.rules read rules file: /usr/lib/udev/rules.d/77-mm-platform-serial-whitelist.rules read rules file: /usr/lib/udev/rules.d/77-mm-simtech-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-usb-device-blacklist.rules read rules file: /usr/lib/udev/rules.d/77-mm-usb-serial-adapters-greylist.rules read rules file: /usr/lib/udev/rules.d/77-mm-x22x-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-zte-port-types.rules read rules file: /usr/lib/udev/rules.d/77-network.rules read rules file: /usr/lib/udev/rules.d/77-nm-olpc-mesh.rules read rules file: /usr/lib/udev/rules.d/78-sound-card.rules read rules file: /usr/lib/udev/rules.d/80-drivers.rules read rules file: /usr/lib/udev/rules.d/80-hotplug-cpu-mem.rules read rules file: /usr/lib/udev/rules.d/80-mm-candidate.rules read rules file: /usr/lib/udev/rules.d/80-net-name-slot.rules read rules file: /usr/lib/udev/rules.d/80-udisks.rules read rules file: /usr/lib/udev/rules.d/80-udisks2.rules read rules file: /usr/lib/udev/rules.d/81-mount.rules read rules file: /usr/lib/udev/rules.d/85-regulatory.rules read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules read rules file: /usr/lib/udev/rules.d/90-libgpod.rules read rules file: /usr/lib/udev/rules.d/90-pulseaudio.rules read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules read rules file: /usr/lib/udev/rules.d/95-udev-late.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules read rules file: /usr/lib/udev/rules.d/97-hid2hci.rules read rules file: /etc/udev/rules.d/99-iwlwifi-led.rules read rules file: /usr/lib/udev/rules.d/99-systemd.rules rules contain 393216 bytes tokens (32768 * 12 bytes), 36120 bytes strings 22843 strings (195627 bytes), 19731 de-duplicated (162620 bytes), 3113 trie nodes used unable to open device '/sys/device/block/sdd' unload module index -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c6 Oliver Neukum <oneukum@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |f.gruber@eduhi.at --- Comment #6 from Oliver Neukum <oneukum@suse.com> 2013-11-28 09:40:04 UTC --- Was the device plugged in? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c7 --- Comment #7 from Robert Milasan <rmilasan@suse.com> 2013-11-28 09:40:36 UTC --- Thats my question too :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c8 --- Comment #8 from Ferdinand Gruber <f.gruber@eduhi.at> 2013-11-28 09:42:07 UTC --- (In reply to comment #6)
Was the device plugged in?
yes -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c9 --- Comment #9 from Ferdinand Gruber <f.gruber@eduhi.at> 2013-11-28 09:44:44 UTC --- (In reply to comment #3)
Hmmm ... there only problem is the re-assigning to the kernels people will not fix this bug within next few months. I'll add Oliver to Carbon Copy list, let's ask him about this problem.
@ Oliver :
Are you aware about problems with some USB devices belonging to digital camera models like KD-200Z and KD-410Z?
No, this devices are shown e.g. by Puppy Linux in the GUI. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c10 --- Comment #10 from Oliver Neukum <oneukum@suse.com> 2013-11-28 09:48:12 UTC --- (In reply to comment #3)
@ Oliver :
Are you aware about problems with some USB devices belonging to digital camera models like KD-200Z and KD-410Z?
No. It looks like the error handler needs to do something before the device can be read from. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c11 --- Comment #11 from Oliver Neukum <oneukum@suse.com> 2013-11-28 09:54:26 UTC --- Please attach dmesg after the device is plugged in. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c12 --- Comment #12 from Ferdinand Gruber <f.gruber@eduhi.at> 2013-11-28 10:15:49 UTC --- (In reply to comment #11)
Please attach dmesg after the device is plugged in.
3465.531154] usb 2-5.2: new full-speed USB device number 8 using ehci-pci [ 3465.611530] usb 2-5.2: New USB device found, idVendor=04c8, idProduct=0723 [ 3465.611535] usb 2-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3465.611538] usb 2-5.2: Product: KD-200Z [ 3465.611541] usb 2-5.2: Manufacturer: Konica [ 3465.613939] usb-storage 2-5.2:1.0: USB Mass Storage device detected [ 3465.614139] scsi8 : usb-storage 2-5.2:1.0 [ 3466.627031] scsi 8:0:0:0: Direct-Access Konica KD-200Z 1.00 PQ: 0 ANSI: 0 CCS [ 3466.629154] sd 8:0:0:0: Attached scsi generic sg4 type 0 [ 3466.630609] sd 8:0:0:0: [sdd] 29025 512-byte logical blocks: (14.8 MB/14.1 MiB) [ 3466.635059] sd 8:0:0:0: [sdd] Write Protect is off [ 3466.635063] sd 8:0:0:0: [sdd] Mode Sense: bc 00 00 bc [ 3466.639688] sd 8:0:0:0: [sdd] No Caching mode page found [ 3466.639691] sd 8:0:0:0: [sdd] Assuming drive cache: write through [ 3466.658231] sd 8:0:0:0: [sdd] No Caching mode page found [ 3466.658243] sd 8:0:0:0: [sdd] Assuming drive cache: write through [ 3466.759618] sdd: sdd1 [ 3466.759625] sdd: p1 size 29063 extends beyond EOD, enabling native capacity [ 3466.772323] sd 8:0:0:0: [sdd] No Caching mode page found [ 3466.772327] sd 8:0:0:0: [sdd] Assuming drive cache: write through [ 3466.872444] sdd: sdd1 [ 3466.872450] sdd: p1 size 29063 extends beyond EOD, truncated [ 3466.960182] sd 8:0:0:0: [sdd] No Caching mode page found [ 3466.960185] sd 8:0:0:0: [sdd] Assuming drive cache: write through [ 3466.960189] sd 8:0:0:0: [sdd] Attached SCSI removable disk -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c13 --- Comment #13 from Robert Milasan <rmilasan@suse.com> 2013-11-28 10:24:57 UTC --- Sorry, gave you the wrong command: udevadm test /sys/block/sdd and attach the output to the bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c14 --- Comment #14 from Ferdinand Gruber <f.gruber@eduhi.at> 2013-11-28 10:32:19 UTC --- (In reply to comment #13)
Sorry, gave you the wrong command:
udevadm test /sys/block/sdd
and attach the output to the bug.
This is the output of udevadm test /sys/block/sdd: calling: test version 208 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. === trie on-disk === tool version: 208 file size: 5968358 bytes header size 80 bytes strings 1302262 bytes nodes 4666016 bytes load module index read rules file: /usr/lib/udev/rules.d/10-dm.rules read rules file: /run/udev/rules.d/10-root-symlink.rules read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules read rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules read rules file: /usr/lib/udev/rules.d/40-usb_modeswitch.rules read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules read rules file: /usr/lib/udev/rules.d/50-euvccam.rules read rules file: /usr/lib/udev/rules.d/50-firmware.rules read rules file: /usr/lib/udev/rules.d/50-udev-default.rules read rules file: /usr/lib/udev/rules.d/51-android.rules read rules file: /usr/lib/udev/rules.d/51-lirc.rules read rules file: /etc/udev/rules.d/55-libsane.rules read rules file: /usr/lib/udev/rules.d/56-idedma.rules read rules file: /etc/udev/rules.d/56-sane-backends-autoconfig.rules read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules read rules file: /usr/lib/udev/rules.d/60-keyboard.rules read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules read rules file: /usr/lib/udev/rules.d/60-vboxdrv.rules read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules read rules file: /usr/lib/udev/rules.d/61-msft.rules read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules read rules file: /usr/lib/udev/rules.d/64-btrfs.rules read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules read rules file: /usr/lib/udev/rules.d/65-xorg-wacom.rules read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules read rules file: /usr/lib/udev/rules.d/69-libmtp.rules read rules file: /usr/lib/udev/rules.d/69-xorg-vmmouse.rules read rules file: /etc/udev/rules.d/70-kpartx.rules read rules file: /etc/udev/rules.d/70-persistent-net.rules read rules file: /usr/lib/udev/rules.d/70-power-switch.rules read rules file: /usr/lib/udev/rules.d/70-printers.rules read rules file: /usr/lib/udev/rules.d/70-uaccess.rules read rules file: /usr/lib/udev/rules.d/71-seat.rules read rules file: /usr/lib/udev/rules.d/73-seat-late.rules read rules file: /usr/lib/udev/rules.d/73-seat-numlock.rules read rules file: /usr/lib/udev/rules.d/75-net-description.rules read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules read rules file: /usr/lib/udev/rules.d/75-tty-description.rules read rules file: /usr/lib/udev/rules.d/77-mm-ericsson-mbm.rules read rules file: /usr/lib/udev/rules.d/77-mm-huawei-net-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-longcheer-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-nokia-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-pcmcia-device-blacklist.rules read rules file: /usr/lib/udev/rules.d/77-mm-platform-serial-whitelist.rules read rules file: /usr/lib/udev/rules.d/77-mm-simtech-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-usb-device-blacklist.rules read rules file: /usr/lib/udev/rules.d/77-mm-usb-serial-adapters-greylist.rules read rules file: /usr/lib/udev/rules.d/77-mm-x22x-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-zte-port-types.rules read rules file: /usr/lib/udev/rules.d/77-network.rules read rules file: /usr/lib/udev/rules.d/77-nm-olpc-mesh.rules read rules file: /usr/lib/udev/rules.d/78-sound-card.rules read rules file: /usr/lib/udev/rules.d/80-drivers.rules read rules file: /usr/lib/udev/rules.d/80-hotplug-cpu-mem.rules read rules file: /usr/lib/udev/rules.d/80-mm-candidate.rules read rules file: /usr/lib/udev/rules.d/80-net-name-slot.rules read rules file: /usr/lib/udev/rules.d/80-udisks.rules read rules file: /usr/lib/udev/rules.d/80-udisks2.rules read rules file: /usr/lib/udev/rules.d/81-mount.rules read rules file: /usr/lib/udev/rules.d/85-regulatory.rules read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules read rules file: /usr/lib/udev/rules.d/90-libgpod.rules read rules file: /usr/lib/udev/rules.d/90-pulseaudio.rules read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules read rules file: /usr/lib/udev/rules.d/95-udev-late.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules read rules file: /usr/lib/udev/rules.d/97-hid2hci.rules read rules file: /etc/udev/rules.d/99-iwlwifi-led.rules read rules file: /usr/lib/udev/rules.d/99-systemd.rules rules contain 393216 bytes tokens (32768 * 12 bytes), 36120 bytes strings 22843 strings (195627 bytes), 19731 de-duplicated (162620 bytes), 3113 trie nodes used GROUP 6 /usr/lib/udev/rules.d/50-udev-default.rules:50 IMPORT builtin 'usb_id' /usr/lib/udev/rules.d/60-persistent-storage.rules:37 /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-5/2-5.2/2-5.2:1.0: if_class 8 protocol 6 LINK 'disk/by-id/usb-Konica_KD-200Z-0:0' /usr/lib/udev/rules.d/60-persistent-storage.rules:42 IMPORT builtin 'path_id' /usr/lib/udev/rules.d/60-persistent-storage.rules:59 LINK 'disk/by-path/pci-0000:00:1d.7-usb-0:5.2:1.0-scsi-0:0:0:0' /usr/lib/udev/rules.d/60-persistent-storage.rules:60 IMPORT builtin 'blkid' /usr/lib/udev/rules.d/60-persistent-storage.rules:74 error: /dev/sdd: No such device or address IMPORT '/usr/bin/sg_inq -p di --export /dev/sdd' /usr/lib/udev/rules.d/61-msft.rules:5 starting '/usr/bin/sg_inq -p di --export /dev/sdd' '/usr/bin/sg_inq -p di --export /dev/sdd' [3390] exit with return code 15 IMPORT 'udisks-part-id /dev/sdd' /usr/lib/udev/rules.d/80-udisks.rules:88 starting 'udisks-part-id /dev/sdd' 'udisks-part-id /dev/sdd' [3391] exit with return code 0 handling device node '/dev/sdd', devnum=b8:48, mode=0660, uid=0, gid=6 set permissions /dev/sdd, 060660, uid=0, gid=6 preserve already existing symlink '/dev/block/8:48' to '../sdd' found 'b8:48' claiming '/run/udev/links/\x2fdisk\x2fby-id\x2fusb-Konica_KD-200Z-0:0' creating link '/dev/disk/by-id/usb-Konica_KD-200Z-0:0' to '/dev/sdd' preserve already existing symlink '/dev/disk/by-id/usb-Konica_KD-200Z-0:0' to '../../sdd' found 'b8:48' claiming '/run/udev/links/\x2fdisk\x2fby-path\x2fpci-0000:00:1d.7-usb-0:5.2:1.0-scsi-0:0:0:0' creating link '/dev/disk/by-path/pci-0000:00:1d.7-usb-0:5.2:1.0-scsi-0:0:0:0' to '/dev/sdd' preserve already existing symlink '/dev/disk/by-path/pci-0000:00:1d.7-usb-0:5.2:1.0-scsi-0:0:0:0' to '../../sdd' ACTION=add DEVLINKS=/dev/disk/by-id/usb-Konica_KD-200Z-0:0 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:5.2:1.0-scsi-0:0:0:0 DEVNAME=/dev/sdd DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb2/2-5/2-5.2/2-5.2:1.0/host8/target8:0:0/8:0:0:0/block/sdd DEVTYPE=disk ID_BUS=usb ID_INSTANCE=0:0 ID_MODEL=KD-200Z ID_MODEL_ENC=KD-200Z\x20\x20\x20\x20\x20\x20\x20\x20\x20 ID_MODEL_ID=0723 ID_PATH=pci-0000:00:1d.7-usb-0:5.2:1.0-scsi-0:0:0:0 ID_PATH_TAG=pci-0000_00_1d_7-usb-0_5_2_1_0-scsi-0_0_0_0 ID_REVISION=1.00 ID_SERIAL=Konica_KD-200Z-0:0 ID_TYPE=disk ID_USB_DRIVER=usb-storage ID_USB_INTERFACES=:080650: ID_USB_INTERFACE_NUM=00 ID_VENDOR=Konica ID_VENDOR_ENC=Konica\x20\x20 ID_VENDOR_ID=04c8 MAJOR=8 MINOR=48 SUBSYSTEM=block TAGS=:systemd: UDISKS_PRESENTATION_NOPOLICY=0 USEC_INITIALIZED=3566520440 unload module index -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c15 --- Comment #15 from Robert Milasan <rmilasan@suse.com> 2013-11-28 10:38:49 UTC --- This seems to work as expected. Please run also: ls -l /dev/disk/{by-id,by-path}/ |grep sdd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c16 --- Comment #16 from Ferdinand Gruber <f.gruber@eduhi.at> 2013-11-28 11:01:54 UTC --- The command(In reply to comment #15)
This seems to work as expected. Please run also:
This is the output of ls -l /dev/disk/{by-id,by-path}/ |grep sdd ls -l /dev/disk/{by-id,by-path}/ |grep sdd lrwxrwxrwx 1 root root 9 28. Nov 11:55 usb-Konica_KD-200Z-0:0 -> ../../sdd lrwxrwxrwx 1 root root 9 28. Nov 11:55 pci-0000:00:1d.7-usb-0:5.2:1.0-scsi-0:0:0:0 -> ../../sdd It may take too long time that this device appears ... Sometimes there is a delay in fdisk -l -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c17 --- Comment #17 from Oliver Neukum <oneukum@suse.com> 2013-11-28 11:50:24 UTC --- (In reply to comment #12)
(In reply to comment #11)
Please attach dmesg after the device is plugged in.
3465.531154] usb 2-5.2: new full-speed USB device number 8 using ehci-pci [ 3465.611530] usb 2-5.2: New USB device found, idVendor=04c8, idProduct=0723 [ 3465.611535] usb 2-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3465.611538] usb 2-5.2: Product: KD-200Z [ 3465.611541] usb 2-5.2: Manufacturer: Konica [ 3465.613939] usb-storage 2-5.2:1.0: USB Mass Storage device detected [ 3465.614139] scsi8 : usb-storage 2-5.2:1.0 [ 3466.627031] scsi 8:0:0:0: Direct-Access Konica KD-200Z 1.00 PQ: 0 ANSI: 0 CCS [ 3466.629154] sd 8:0:0:0: Attached scsi generic sg4 type 0 [ 3466.630609] sd 8:0:0:0: [sdd] 29025 512-byte logical blocks: (14.8 MB/14.1 MiB)
There we probably have the problem. Just for the record, I don't suppose you really dug up an antique 14MB disk? Let me guess, it has a size of about 2TB? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c18 --- Comment #18 from Ferdinand Gruber <f.gruber@eduhi.at> 2013-11-28 14:44:34 UTC --- (In reply to comment #17)
(In reply to comment #12)
(In reply to comment #11)
Please attach dmesg after the device is plugged in.
3465.531154] usb 2-5.2: new full-speed USB device number 8 using ehci-pci [ 3465.611530] usb 2-5.2: New USB device found, idVendor=04c8, idProduct=0723 [ 3465.611535] usb 2-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3465.611538] usb 2-5.2: Product: KD-200Z [ 3465.611541] usb 2-5.2: Manufacturer: Konica [ 3465.613939] usb-storage 2-5.2:1.0: USB Mass Storage device detected [ 3465.614139] scsi8 : usb-storage 2-5.2:1.0 [ 3466.627031] scsi 8:0:0:0: Direct-Access Konica KD-200Z 1.00 PQ: 0 ANSI: 0 CCS [ 3466.629154] sd 8:0:0:0: Attached scsi generic sg4 type 0 [ 3466.630609] sd 8:0:0:0: [sdd] 29025 512-byte logical blocks: (14.8 MB/14.1 MiB)
There we probably have the problem. Just for the record, I don't suppose you really dug up an antique 14MB disk? Let me guess, it has a size of about 2TB?
It is an old camera model with a tiny SD card. It has really only 16 MB. But the same problem occurs with another model (Konica KD410Z) which has a bigger SD Card. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c19 --- Comment #19 from Oliver Neukum <oneukum@suse.com> 2013-11-28 15:04:05 UTC --- Please post "fdisk -l" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c20 --- Comment #20 from Ferdinand Gruber <f.gruber@eduhi.at> 2013-11-28 17:15:34 UTC --- (In reply to comment #19)
Please post "fdisk -l"
Disk /dev/sdd: 14 MB, 14860800 bytes, 29025 sectors Units = Sektoren of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x00000000 Gerät boot. Anfang Ende Blöcke Id System /dev/sdd1 57 29119 14531+ 1 FAT12 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c21 John Harrison <JHarrison@seadog.reno.nv.us> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |JHarrison@seadog.reno.nv.us --- Comment #21 from John Harrison <JHarrison@seadog.reno.nv.us> 2013-11-30 06:19:51 UTC --- I have a similar problem. Prior to 13.1 my camera was detected when I was using openSuse 12.2 on this same computer. Now on v13.1 and camera is not detected in device notifier. I am running KDE openSuse 13.1x64. This was an upgrade, not a fresh install. In Dolphin I can input 'camera:/' on the location bar and access my camera & photos. If I click through to my photos and then click on the location bar this is what it returns: "Camera:/USB%2520PTP%2520Class%2520Camera@usb:001,017/store_00010001/DCIM/100NIKON/" As far as I can tell the system responds the same in root as $USER. lsusb: Bus 001 Device 017: ID 04b0:0329 Nikon Corp. fdisk -l only detects my hard drive, not the usb device. usb hard drives are detected and mounted properly, opening Dolphin. dmesg: [29001.746464] usb 1-1.1: new high-speed USB device number 17 using ehci-pci [29001.832719] usb 1-1.1: New USB device found, idVendor=04b0, idProduct=0329 [29001.832723] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [29001.832726] usb 1-1.1: Product: NIKON DSC COOLPIX S4300-PTP [29001.832728] usb 1-1.1: Manufacturer: NIKON [29001.832729] usb 1-1.1: SerialNumber: 000030015973 When running a VM Apple client on this machine and the camera is detected in the usb passthru to the client VM. Also, just discovered that I can add an entry in Dolphin for 'Places'. Adding Camera:/ allows me to access my photo's without typing on the location bar. I do not know if this will stick through a eject of camera or reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c22 --- Comment #22 from John Harrison <JHarrison@seadog.reno.nv.us> 2013-11-30 06:34:42 UTC --- I forgot to mention that the camera is detected in Configure Desktop -> Hardware -> Digital Camera. Clicking Test, Configure, & Information return info. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c23 Dean Martin <deano_ferrari@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |deano_ferrari@hotmail.com --- Comment #23 from Dean Martin <deano_ferrari@hotmail.com> 2013-12-27 05:03:49 UTC --- I'm reporting an issue with knotify4 and PTP cameras. I am observing the same issue with a Canon PowerShot A1000 IS and SX150 IS models. The following is observed dmesg|tail [ 4443.446113] usb 2-5: new high-speed USB device number 8 using ehci-pci [ 4443.562928] usb 2-5: New USB device found, idVendor=04a9, idProduct=318e [ 4443.562938] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4443.562946] usb 2-5: Product: Canon Digital Camera [ 4443.562952] usb 2-5: Manufacturer: Canon Inc. [ 4443.562958] usb 2-5: SerialNumber: A5CA3EBD60C64724BEA85059B71F7A6B The udevent is captured udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[4480.648936] add /devices/pci0000:00/0000:00:1d.7/usb2/2-5 (usb) KERNEL[4480.649029] add /devices/pci0000:00/0000:00:1d.7/usb2/2-5/2-5:1.0 (usb) UDEV [4480.657733] add /devices/pci0000:00/0000:00:1d.7/usb2/2-5 (usb) UDEV [4480.658858] add /devices/pci0000:00/0000:00:1d.7/usb2/2-5/2-5:1.0 (usb) but solid-hardware listen reports nothing about the deivce solid-hardware listen Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) and the udi is absent in solid-hardware list: solid-hardware list Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) udi = '/org/kde/solid/udev/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4' udi = '/org/kde/solid/udev/sys/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input3' udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/ttyUSB0/tty/ttyUSB0' udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/ttyUSB1/tty/ttyUSB1' udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/ttyUSB2/tty/ttyUSB2' udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0' udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D1' udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1b.0/sound/card0/pcmC0D0c' udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1b.0/sound/card0/pcmC0D0p' udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1b.0/sound/card0/controlC0' udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1c.1/0000:10:00.0/ssb0:0/net/wlan0' udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1c.2/0000:18:00.0/net/ens1' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS0' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS1' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS10' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS11' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS12' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS13' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS14' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS15' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS16' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS17' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS18' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS19' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS2' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS20' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS21' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS22' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS23' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS24' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS25' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS26' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS27' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS28' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS29' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS3' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS30' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS31' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS4' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS5' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS6' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS7' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS8' udi = '/org/kde/solid/udev/sys/devices/platform/serial8250/tty/ttyS9' udi = '/org/kde/solid/udev/sys/devices/system/cpu/cpu0' udi = '/org/kde/solid/udev/sys/devices/system/cpu/cpu1' udi = '/org/kde/solid/udev/sys/devices/virtual/net/lo' udi = '/org/kde/solid/udev/sys/devices/virtual/sound/seq' udi = '/org/kde/solid/udev/sys/devices/virtual/sound/timer' udi = '/org/freedesktop/UDisks2/block_devices/sda1' udi = '/org/freedesktop/UDisks2/block_devices/sda7' udi = '/org/freedesktop/UDisks2/block_devices/sda6' udi = '/org/freedesktop/UDisks2/block_devices/sda5' udi = '/org/freedesktop/UDisks2/block_devices/sda' udi = '/org/freedesktop/UDisks2/block_devices/sda2' udi = '/org/freedesktop/UDisks2/drives/Hitachi_HTS542525K9SA00_080402BB3F00WDD6EV6C' udi = '/org/freedesktop/UDisks2/drives/Optiarc_DVD_RW_AD_7561A_30647850_1894265Q111' udi = '/org/freedesktop/UPower' udi = '/org/freedesktop/UPower/devices/line_power_C239' udi = '/org/freedesktop/UPower/devices/battery_C23B' udi = '/org/kde/fstab' We have a thread open in openSUSE Forums: https://forums.opensuse.org/english/get-technical-help-here/hardware/493692-... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c24 --- Comment #24 from Oliver Neukum <oneukum@suse.com> 2013-12-28 07:53:42 UTC --- Please run the test described in comment#13 (you may have to adjust the device name) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c25 --- Comment #25 from Dean Martin <deano_ferrari@hotmail.com> 2013-12-29 02:49:20 UTC --- (In reply to comment #24)
Please run the test described in comment#13 (you may have to adjust the device name)
Okay, well udevadm monitor reported monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[3656.894940] add /devices/pci0000:00/0000:00:1d.7/usb2/2-6 (usb) KERNEL[3656.895040] add /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0 (usb) UDEV [3656.901417] add /devices/pci0000:00/0000:00:1d.7/usb2/2-6 (usb) UDEV [3656.902956] add /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0 (usb) Using the device path '/devices/pci0000:00/0000:00:1d.7/usb2/2-6', I get udevadm test /devices/pci0000:00/0000:00:1d.7/usb2/2-6 calling: test version 208 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. === trie on-disk === tool version: 208 file size: 5968358 bytes header size 80 bytes strings 1302262 bytes nodes 4666016 bytes load module index read rules file: /usr/lib/udev/rules.d/10-dm.rules read rules file: /run/udev/rules.d/10-root-symlink.rules read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules read rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules read rules file: /usr/lib/udev/rules.d/40-usb_modeswitch.rules read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules read rules file: /etc/udev/rules.d/50-brother.rules read rules file: /usr/lib/udev/rules.d/50-euvccam.rules read rules file: /usr/lib/udev/rules.d/50-firmware.rules read rules file: /usr/lib/udev/rules.d/50-udev-default.rules read rules file: /usr/lib/udev/rules.d/51-android.rules read rules file: /usr/lib/udev/rules.d/51-lirc.rules read rules file: /etc/udev/rules.d/55-libsane.rules read rules file: /usr/lib/udev/rules.d/56-idedma.rules read rules file: /etc/udev/rules.d/56-sane-backends-autoconfig.rules read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules read rules file: /usr/lib/udev/rules.d/60-fprint-autosuspend.rules read rules file: /usr/lib/udev/rules.d/60-keyboard.rules read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules read rules file: /usr/lib/udev/rules.d/61-msft.rules read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules read rules file: /usr/lib/udev/rules.d/64-btrfs.rules read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules read rules file: /usr/lib/udev/rules.d/65-xorg-wacom.rules read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules read rules file: /usr/lib/udev/rules.d/69-libmtp.rules read rules file: /usr/lib/udev/rules.d/69-xorg-vmmouse.rules read rules file: /etc/udev/rules.d/70-kpartx.rules skip empty file: /etc/udev/rules.d/70-persistent-net.rules read rules file: /usr/lib/udev/rules.d/70-power-switch.rules read rules file: /usr/lib/udev/rules.d/70-printers.rules read rules file: /usr/lib/udev/rules.d/70-uaccess.rules read rules file: /usr/lib/udev/rules.d/71-seat.rules read rules file: /usr/lib/udev/rules.d/73-seat-late.rules read rules file: /usr/lib/udev/rules.d/73-seat-numlock.rules read rules file: /usr/lib/udev/rules.d/75-net-description.rules read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules read rules file: /usr/lib/udev/rules.d/75-tty-description.rules read rules file: /usr/lib/udev/rules.d/77-mm-ericsson-mbm.rules read rules file: /usr/lib/udev/rules.d/77-mm-huawei-net-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-longcheer-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-nokia-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-pcmcia-device-blacklist.rules read rules file: /usr/lib/udev/rules.d/77-mm-platform-serial-whitelist.rules read rules file: /usr/lib/udev/rules.d/77-mm-simtech-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-usb-device-blacklist.rules read rules file: /usr/lib/udev/rules.d/77-mm-usb-serial-adapters-greylist.rules read rules file: /usr/lib/udev/rules.d/77-mm-x22x-port-types.rules read rules file: /usr/lib/udev/rules.d/77-mm-zte-port-types.rules read rules file: /usr/lib/udev/rules.d/77-network.rules read rules file: /usr/lib/udev/rules.d/77-nm-olpc-mesh.rules read rules file: /usr/lib/udev/rules.d/78-sound-card.rules read rules file: /usr/lib/udev/rules.d/80-drivers.rules read rules file: /usr/lib/udev/rules.d/80-hotplug-cpu-mem.rules read rules file: /usr/lib/udev/rules.d/80-mm-candidate.rules read rules file: /usr/lib/udev/rules.d/80-net-name-slot.rules read rules file: /usr/lib/udev/rules.d/80-udisks2.rules read rules file: /usr/lib/udev/rules.d/81-mount.rules read rules file: /usr/lib/udev/rules.d/85-regulatory.rules read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules read rules file: /etc/udev/rules.d/90-gphoto.rules read rules file: /usr/lib/udev/rules.d/90-libgpod.rules read rules file: /usr/lib/udev/rules.d/90-pulseaudio.rules read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules read rules file: /usr/lib/udev/rules.d/95-udev-late.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules read rules file: /usr/lib/udev/rules.d/97-hid2hci.rules read rules file: /etc/udev/rules.d/99-iwlwifi-led.rules read rules file: /usr/lib/udev/rules.d/99-systemd.rules rules contain 393216 bytes tokens (32768 * 12 bytes), 38360 bytes strings 31474 strings (251044 bytes), 27784 de-duplicated (216375 bytes), 3691 trie nodes used IMPORT builtin 'usb_id' /usr/lib/udev/rules.d/50-udev-default.rules:9 IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:9 MODE 0664 /usr/lib/udev/rules.d/50-udev-default.rules:36 PROGRAM '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6 2 9' /usr/lib/udev/rules.d/69-libmtp.rules:1381 starting '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6 2 9' '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6 2 9' [3177] exit with return code 0 IMPORT builtin 'path_id' /usr/lib/udev/rules.d/71-seat.rules:43 RUN 'uaccess' /usr/lib/udev/rules.d/73-seat-late.rules:15 PROGRAM 'check-ptp-camera 06/01/01' /etc/udev/rules.d/90-gphoto.rules:1533 starting 'check-ptp-camera 06/01/01' 'check-ptp-camera 06/01/01' [3178] exit with return code 2 handling device node '/dev/bus/usb/002/009', devnum=c189:136, mode=0664, uid=0, gid=0 preserve permissions /dev/bus/usb/002/009, 020664, uid=0, gid=0 preserve already existing symlink '/dev/char/189:136' to '../bus/usb/002/009' unable to create temporary db file '/run/udev/data/c189:136.tmp': Permission denied ACTION=add BUSNUM=002 DEVNAME=/dev/bus/usb/002/009 DEVNUM=009 DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb2/2-6 DEVTYPE=usb_device DRIVER=usb ID_BUS=usb ID_FOR_SEAT=usb-pci-0000_00_1d_7-usb-0_6 ID_MODEL=Canon_Digital_Camera ID_MODEL_ENC=Canon\x20Digital\x20Camera ID_MODEL_FROM_DATABASE=PowerShot A1000 IS ID_MODEL_ID=318e ID_PATH=pci-0000:00:1d.7-usb-0:6 ID_PATH_TAG=pci-0000_00_1d_7-usb-0_6 ID_REVISION=0002 ID_SERIAL=Canon_Inc._Canon_Digital_Camera_A5CA3EBD60C64724BEA85059B71F7A6B ID_SERIAL_SHORT=A5CA3EBD60C64724BEA85059B71F7A6B ID_USB_INTERFACES=:060101: ID_VENDOR=Canon_Inc. ID_VENDOR_ENC=Canon\x20Inc. ID_VENDOR_FROM_DATABASE=Canon, Inc. ID_VENDOR_ID=04a9 MAJOR=189 MINOR=136 PRODUCT=4a9/318e/2 SUBSYSTEM=usb TAGS=:seat:uaccess: TYPE=0/0/0 USEC_INITIALIZED=3656893831 run: 'uaccess' unload module index -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c26 --- Comment #26 from Dean Martin <deano_ferrari@hotmail.com> 2013-12-29 03:00:59 UTC --- (In reply to comment #25) If I use the second device path (not sure which was applicable for PTP device) udevadm test /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0 I get slightly different output at the end rules contain 393216 bytes tokens (32768 * 12 bytes), 38360 bytes strings 31474 strings (251044 bytes), 27784 de-duplicated (216375 bytes), 3691 trie nodes used IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:11 RUN 'kmod load $env{MODALIAS}' /usr/lib/udev/rules.d/80-drivers.rules:5 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0 DEVTYPE=usb_interface ID_MODEL_FROM_DATABASE=PowerShot A1000 IS ID_VENDOR_FROM_DATABASE=Canon, Inc. INTERFACE=6/1/1 MODALIAS=usb:v04A9p318Ed0002dc00dsc00dp00ic06isc01ip01in00 PRODUCT=4a9/318e/2 SUBSYSTEM=usb TYPE=0/0/0 USEC_INITIALIZED=13051522 run: 'kmod load usb:v04A9p318Ed0002dc00dsc00dp00ic06isc01ip01in00' unload module index -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c27 --- Comment #27 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-02 08:46:17 UTC --- After a bit of research which I have documented in the following thread https://forums.opensuse.org/english/get-technical-help-here/hardware/493692-... I have established that the lack of notification was as a result of missing environment variables being set. Even though libgphoto2 is installed, it is necessary to run /usr/lib64/libgphoto2/print-camera-list udev-rules to get the camera rules instated like this /usr/lib64/libgphoto2/print-camera-list udev-rules version 0.98 group video mode 0666 > /etc/udev/rules.d/90-gphoto.rules However, I found (from searching around online), that it no longer includes the following lines ENV{ID_USB_INTERFACES}=="", IMPORT{program}="usb_id --export %p" ENV{ID_USB_INTERFACES}=="*:08*:*", GOTO="libgphoto2_usb_end" ENV{ID_USB_INTERFACES}=="*:060101:*", ENV{ID_GPHOTO2}="1", ENV{GPHOTO2_DRIVER}="PTP", GOTO="libgphoto2_usb_end" Once I had added the lines above, I found that 'solid-hardware listen' was able to report my camera with appropriate udi and the KDE notifier works as expected. A minimal PTP camera rules file (for notification purposes) # udev rules file for libgphoto2 devices (for udev 0.98 version) # Created from this library: # libgphoto2 2.5.2.1 all camlibs, gcc, ltdl, EXIF # libgphoto2_port 0.10.0 gcc, ltdl, USB, serial lockdev locking # # this file is autogenerated, local changes will be LOST on upgrades ACTION!="add", GOTO="libgphoto2_rules_end" SUBSYSTEM!="usb|usb_device", GOTO="libgphoto2_usb_end" ENV{ID_USB_INTERFACES}=="", IMPORT{program}="usb_id --export %p" ENV{ID_USB_INTERFACES}=="*:08*:*", GOTO="libgphoto2_usb_end" ENV{ID_USB_INTERFACES}=="*:060101:*", ENV{ID_GPHOTO2}="1", ENV{GPHOTO2_DRIVER}="PTP", GOTO="libgphoto2_usb_end" #Camera model entries can go here eg #ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="3234", MODE="0666", GROUP="video" LABEL="libgphoto2_usb_end" LABEL="libgphoto2_rules_end" All that I have removed is the individual camera model entries for setting modes, which are not required for viewing/downloading files. So, maybe libgphoto2 should provide a minimal rules file by default? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c28 --- Comment #28 from John Harrison <JHarrison@seadog.reno.nv.us> 2014-01-03 03:41:02 UTC --- Dean: Thanks so much for your work and the comment #27. I'm the user you worked with in the forum back in late Nov. Thanks for all the research to make this work. I ran the command to create rule 90 and added the ENV statements to the rule. As I commented in #21, my camera is a Nikon. I see other 04b0 vendor lines but not with the correct productID. So I added the following line at the top of the long list of ATTRS. #Camera model entries can go here eg ATTRS{idVendor}=="04b0", ATTRS{idProduct}=="0329", MODE="0666", GROUP="video" I did not add the 2 LABEL statements that follow in your example because they exist further down in the file. I suppose I'd get a faster response if I added them at the top. kNotify offers me several options and it works like it used to when I was running v12.2 Thanks again, Jon -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c29 --- Comment #29 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-03 04:37:40 UTC --- (In reply to comment #28) Glad to have been of help Jon. Just to be clear, the minimal udev rules file outlined above is sufficient, or a more comprehensive file (suitable for newer udev versions) can be generated with something like /usr/lib64/libgphoto2/print-camera-list udev-rules version 175 group video mode 0666 > /lib/udev/rules.d/40-libgphoto2.rules -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c30 --- Comment #30 from Frederic Crozat <fcrozat@suse.com> 2014-01-06 10:03:09 UTC --- Do not use /lib/udev/rules.d for storing rules, either use /usr/lib/udev/rules.d or (better, since those are not packaged rules), /etc/udev/rules.d Second, starting with 13.1, libgphoto udev rules have been replaced with hwdb rules, for better performance. PTP cameras should be hanlded properly. Non ptp camera needs to be added to /usr/lib/udev/hwdb.d/20-gphoto.hwdb (which should be done automatically by libgphoto package, when support is added there). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c31 --- Comment #31 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-06 19:14:55 UTC --- (In reply to comment #30)
Do not use /lib/udev/rules.d for storing rules, either use /usr/lib/udev/rules.d or (better, since those are not packaged rules), /etc/udev/rules.d
Actually /lib/udev/ is just a link to /usr/lib/udev anyway. # ls -l /lib/udev lrwxrwxrwx 1 root root 13 Dec 14 09:27 /lib/udev -> /usr/lib/udev
Second, starting with 13.1, libgphoto udev rules have been replaced with hwdb rules, for better performance.
PTP cameras should be hanlded properly. Non ptp camera needs to be added to /usr/lib/udev/hwdb.d/20-gphoto.hwdb (which should be done automatically by libgphoto package, when support is added there).
Yes, but PTP cameras are not being handled properly. They are not added to 20-gphoto.hwdb dynamically. So, maybe this is still work in progress? FWIW, I have the following installed libgphoto2-6-2.5.2.1-2.2.1.x86_64 libgphoto2-6-32bit-2.5.2.1-2.2.1.x86_64 It seems to me that there is no corresponding udev rule yet to update the database automatically, or am I missing something? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c32 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com InfoProvider|f.gruber@eduhi.at |meissner@suse.com AssignedTo|systemd-maintainers@suse.de |meissner@suse.com --- Comment #32 from Frederic Crozat <fcrozat@suse.com> 2014-01-07 18:02:33 UTC --- (In reply to comment #31)
(In reply to comment #30)
Do not use /lib/udev/rules.d for storing rules, either use /usr/lib/udev/rules.d or (better, since those are not packaged rules), /etc/udev/rules.d
Actually /lib/udev/ is just a link to /usr/lib/udev anyway.
I know, I took care of the migration, but it is better to have everybody use the new path, even in their example ;)
Second, starting with 13.1, libgphoto udev rules have been replaced with hwdb rules, for better performance.
PTP cameras should be hanlded properly. Non ptp camera needs to be added to /usr/lib/udev/hwdb.d/20-gphoto.hwdb (which should be done automatically by libgphoto package, when support is added there).
Yes, but PTP cameras are not being handled properly. They are not added to 20-gphoto.hwdb dynamically. So, maybe this is still work in progress?
Hmm, after doing a quick check on libgphoto2 code which is generating the hwdb rules (and before, the udev rules), it looks like it doesn't prefill the hwdb rules set with a generic rule for PTP (but I'm not 100% sure this kind of rules can be done in hwdb or if it should be done in udev rules) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c33 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com --- Comment #33 from Marcus Meissner <meissner@suse.com> 2014-01-08 10:37:04 UTC --- There is this rule that actually should capture it: # USB PTP Class Camera usb:v*p*d*dc06dsc01p01*" GPHOTO2_DRIVER=PTP ID_GPHOTO2=1 I wonder if it is correct, but probably not. what is the correct syntax for an Interface match of 6/1/1 ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c34 --- Comment #34 from Marcus Meissner <meissner@suse.com> 2014-01-08 10:38:30 UTC --- looking at usb:v04A9p318Ed0002dc00dsc00dp00ic06isc01ip01in00' it should probably be ic06isc01ip01 in the matcher. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c35 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|meissner@suse.com | --- Comment #35 from Marcus Meissner <meissner@suse.com> 2014-01-09 09:57:59 UTC --- did some testing and I think I fixed it. new libgphoto2-6 RPMs for testing in: http://download.opensuse.org/update/13.1-test/ will be released next week Also, the Canon SX150IS reporter, what are its USB ids, so I can add them to the libgphoto2 database? ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c36 --- Comment #36 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-10 00:45:25 UTC --- (In reply to comment #35)
did some testing and I think I fixed it.
new libgphoto2-6 RPMs for testing in:
Thanks Marcus. I'll test it now.
Also, the Canon SX150IS reporter, what are its USB ids, so I can add them to the libgphoto2 database? ;)
Bus 002 Device 003: ID 04a9:3234 Canon, Inc. PowerShot SX150 IS and the Canon PowerShot A1000 IS chipset Bus 002 Device 004: ID 04a9:318e Canon, Inc. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c37 --- Comment #37 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-10 01:06:24 UTC --- (In reply to comment #36)
(In reply to comment #35)
did some testing and I think I fixed it.
new libgphoto2-6 RPMs for testing in:
Thanks Marcus. I'll test it now.
Tested and confirmed as working. :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c38 --- Comment #38 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-10 22:11:11 UTC --- Just to clarify, even with the new package, I want to mention that 1) the required udev rules file is not generated automatically at install time (as I'd expect it be.) My understanding is that the RPM spec file should be taking care of this...? So, I still have to run the following for detection to work. /usr/lib64/libgphoto2/print-camera-list udev-rules version 175 group video mode 0666 > /usr/lib/udev/rules.d/40-libgphoto2.rules 2) it doesn't seem to make a difference as to whether /usr/lib/udev/hwdb.d/20-gphoto.hwdb is present or not. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c39 --- Comment #39 from Marcus Meissner <meissner@suse.com> 2014-01-10 22:22:57 UTC --- The udev rules in libgphoto2 are replaced by the hwdb database/rules. Neither are "group video" or "Mode 666" correct here, this is all handled by acls these days. What exaxctly is the symptom you see / not see? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c40 --- Comment #40 from Bernhard Wiedemann <bwiedemann@suse.com> 2014-01-11 00:00:14 CET --- This is an autogenerated message for OBS integration: This bug (852551) was mentioned in https://build.opensuse.org/request/show/213549 Factory / libgphoto2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c41 --- Comment #41 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-11 04:13:08 UTC --- (In reply to comment #39)
The udev rules in libgphoto2 are replaced by the hwdb database/rules.
Okay, if that is so, they are not working as expected. That is, the generic PTP entry does not do the job.
Neither are "group video" or "Mode 666" correct here, this is all handled by acls these days.
Fair enough. Actually, all that I'm trying to illustrate is that I need to generate a rules file containing at least the following # udev rules file for libgphoto2 devices (for udev 175 version) # Created from this library: # libgphoto2 2.5.2.1 all camlibs, gcc, ltdl, EXIF # libgphoto2_port 0.10.0 gcc, ltdl, USB, serial lockdev locking # # this file is autogenerated, local changes will be LOST on upgrades ACTION!="add", GOTO="libgphoto2_rules_end" SUBSYSTEM!="usb", GOTO="libgphoto2_usb_end" ENV{DEVTYPE}!="usb_device", GOTO="libgphoto2_usb_end" ENV{ID_USB_INTERFACES}=="", IMPORT{builtin}="usb_id" ENV{ID_USB_INTERFACES}=="*:08*:*", GOTO="libgphoto2_usb_end" ENV{ID_USB_INTERFACES}=="*:060101:*", ENV{ID_GPHOTO2}="1", ENV{GPHOTO2_DRIVER}="PTP", MODE="0666", GROUP="video", GOTO="libgphoto2_usb_end" LABEL="libgphoto2_usb_end" LABEL="libgphoto2_rules_end"
What exaxctly is the symptom you see / not see?
The KDE notifier (and solid-hardware listen) do not pick up the PTP camera, unless I have the rule above present. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c42 --- Comment #42 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-11 08:19:24 UTC --- I think the problem is with the wildcards in # USB PTP Class Camera usb:v*p*d*ic06isc01p01* GPHOTO2_DRIVER=PTP ID_GPHOTO2=1 However, this works # USB PTP Class Camera usb:*ic06isc01ip01* GPHOTO2_DRIVER=PTP ID_GPHOTO2=1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c43 --- Comment #43 from Marcus Meissner <meissner@suse.com> 2014-01-11 08:32:03 UTC --- my entry missed an "i" before the "p" apparetntly ... argh weird as I tested that :/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c44 --- Comment #44 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-11 08:38:03 UTC --- There is one other side-effect with having the generic rule, and that is that for cameras with device-specific rule entries, there are two matches, and so two 'Camera' instances then appear in the notifier. (I found this out when I constructed a rule for my camera.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c45 --- Comment #45 from Marcus Meissner <meissner@suse.com> 2014-01-11 10:22:09 UTC --- i dont think hwdb has logic to avoid multiple matches, so it should be handled by higher layers (in the solid kde framework I suspect) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c46 --- Comment #46 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-11 19:42:21 UTC --- (In reply to comment #45)
i dont think hwdb has logic to avoid multiple matches, so it should be handled by higher layers (in the solid kde framework I suspect)
That's what I suspected. (The older existing udev rules have the necessary logic to cope with this.) I guess we need to let the KDE libsolid maintainers know about the possible effects of this change with using udev's hwdb. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c47 --- Comment #47 from Marcus Meissner <meissner@suse.com> 2014-01-13 14:43:23 UTC --- new libgphoto2 update is in test http://download.opensuse.org/update/13.1-test/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c48 --- Comment #48 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-13 20:14:02 UTC --- (In reply to comment #47)
new libgphoto2 update is in test http://download.opensuse.org/update/13.1-test/
Okay, now works as expected. :) Just to let you know that both my Canon cameras work with # Canon PowerShot SX150 IS usb:v04A9p3234* GPHOTO2_DRIVER=PTP SUPPORTED=1 ID_GPHOTO2=1 # Canon PowerShot A1000 IS usb:v04A9p318E* GPHOTO2_DRIVER=PTP ID_GPHOTO2=1 Can they be added to the list? (For now, I have them in /etc/udev/hwdb.d/canon.hwdb) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c49 --- Comment #49 from Swamp Workflow Management <swamp@suse.de> 2014-01-14 16:04:22 UTC --- openSUSE-RU-2014:0060-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 852551 CVE References: Sources used: openSUSE 13.1 (src): libgphoto2-2.5.2.1-2.14.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c50 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #50 from Marcus Meissner <meissner@suse.com> 2014-01-14 16:18:38 UTC --- I added those in the libgphoto2 2.5.3 release, so 13.2 will get them directly. (until then PTP matcher shouzld be sufficient ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=852551 https://bugzilla.novell.com/show_bug.cgi?id=852551#c51 --- Comment #51 from Dean Martin <deano_ferrari@hotmail.com> 2014-01-14 20:11:24 UTC --- Yes, it is, an(In reply to comment #50)
I added those in the libgphoto2 2.5.3 release, so 13.2 will get them directly.
(until then PTP matcher shouzld be sufficient ;)
I don't mind either way. I've deliberately added the device-specific entries for now, as now that the generic matcher is working, I can notify the KDE people about the side-effect of multiple matching occurring. ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com