isn't this more a udev issue ?

CC: (none) => dmorganec

IMHO yes, especially as I have no systemd running (yet), but hey, maybe that's the problem :)

anyway, if systemd should be running on my system, then it's probably a bug that it isn't ...

systemd isn't running ?   this is wanted ?

I updated from Mageia 1 to Cauldron and AFAICT, systemd was not activated ...
personally I do not care if it is systemd or sysv-init, as long as the system works

what about this bug with systemd 40 ?

so systemd 40 is supposed the change the USB device permissions?
how would I test that?

just verified with Mageia 2 Beta 1 upgraded to latest Cauldron and the issue still persists:

$ gphoto2 -L
                                                                               
*** Error ***              
An error occurred in the io-library ('I/O problem'): Could not open USB device (Permission denied).
*** Error (-7: 'I/O problem') ***       

also shotwell is not able to see/access the camera.

Priority: Normal => High
CC: (none) => herbert
Source RPM: systemd => systemd, udev

Hi Herbert,

I think Dexter's comment above was a bit of a "mass update" rather than a specific test.

I agree this is purely a udev issue, not a systemd one. It should still be fixed tho' :D

Hope you don't mind, but this is not really a "high" priority bug, so I've reset it to normal.

Can you run:

env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt -L

And attach the file generated?

Priority: High => Normal
CC: (none) => mageia
Source RPM: systemd, udev => udev

Actually looking at this it appears that this model is only supported from gphone 2.4.12 onwards:

http://gphoto.org/news/

I'll see what the maintainer thinks.

Created attachment 1865 [details]
env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt -L

note that this was captured after plugging in the camera and testing that root can indeed access the camera.

(In reply to comment #9)
> Actually looking at this it appears that this model is only supported from
> gphone 2.4.12 onwards:

s/gphone/gphoto/

> http://gphoto.org/news/

which brings up a few questions like:
 - why we are still at 2.4.11 on Cauldron?
 - why does it work as root?
 - why did it work the past 2-3 years?

> I'll see what the maintainer thinks.

appreciated.

It works as root because the udev rules simply detect the camera and set it up to have appropriate conditions.

As for why we have an old version, I don't know. This is not my package, I'm just helping to investigate the issue.

I would personally have pushed for an update, but it seems others on Cauldron mailing list didn't want to go down that route. I did try and I'll send another mail just now just in case.

As there is no maintainer, I would advice you to help us out and contribute to Mageia and become the official maintainer :D


As this is unrelated to systemd migration, I've removed it from the blocks list. This is still a valid bug however and it would be nice if someone did step forward and become maintainer.

Blocks: 2120 => (none)
Source RPM: udev => libgphoto

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

I'm seeing what appears to be the same problem on Mageia 2 release with a Canon EOS Rebel XT (350D).

Linux localhost.localdomain 3.3.6-desktop-2.mga2 #1 SMP Thu May 17 16:25:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

udev output:


Jun  4 14:23:22 localhost kernel: [18324.713044] usb 1-8: new high-speed USB device number 43 using ehci_hcd
Jun  4 14:23:22 localhost kernel: [18324.843953] usb 1-8: New USB device found, idVendor=04a9, idProduct=30ee
Jun  4 14:23:22 localhost kernel: [18324.843962] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun  4 14:23:22 localhost kernel: [18324.843968] usb 1-8: Product: Canon Digital Camera
Jun  4 14:23:22 localhost kernel: [18324.843973] usb 1-8: Manufacturer: Canon Inc.
Jun  4 14:23:22 localhost udevd[14689]: validate module index
Jun  4 14:23:22 localhost udevd[14689]: seq 2035 queued, 'add' 'usb'
Jun  4 14:23:22 localhost udevd[14689]: seq 2035 forked new worker [14799]
Jun  4 14:23:22 localhost udevd[14799]: seq 2035 running
Jun  4 14:23:22 localhost udevd[14689]: seq 2036 queued, 'add' 'usb'
Jun  4 14:23:22 localhost udevd[14799]: device 0x1a7f820 has devpath '/devices/pci0000:00/0000:00:0b.1/usb1/1-8'
Jun  4 14:23:22 localhost udevd[14799]: no db file to read /run/udev/data/c189:42: No such file or directory
Jun  4 14:23:22 localhost udevd[14799]: device 0x1a962e0 has devpath '/devices/pci0000:00/0000:00:0b.1/usb1'
Jun  4 14:23:22 localhost udevd[14799]: device 0x1a96b00 has devpath '/devices/pci0000:00/0000:00:0b.1'
Jun  4 14:23:22 localhost udevd[14799]: device 0x1a97310 has devpath '/devices/pci0000:00'
Jun  4 14:23:22 localhost udevd[14799]: IMPORT builtin 'usb_id' /lib/udev/rules.d/40-libgphoto2.rules:11
Jun  4 14:23:22 localhost udevd[14799]: ID_VENDOR=Canon_Inc.
Jun  4 14:23:22 localhost udevd[14799]: ID_VENDOR_ENC=Canon\x20Inc.
Jun  4 14:23:22 localhost udevd[14799]: ID_VENDOR_ID=04a9
Jun  4 14:23:22 localhost udevd[14799]: ID_MODEL=Canon_Digital_Camera
Jun  4 14:23:22 localhost udevd[14799]: ID_MODEL_ENC=Canon\x20Digital\x20Camera
Jun  4 14:23:22 localhost udevd[14799]: ID_MODEL_ID=30ee
Jun  4 14:23:22 localhost udevd[14799]: ID_REVISION=0001
Jun  4 14:23:22 localhost udevd[14799]: ID_SERIAL=Canon_Inc._Canon_Digital_Camera
Jun  4 14:23:22 localhost udevd[14799]: ID_BUS=usb
Jun  4 14:23:22 localhost udevd[14799]: ID_USB_INTERFACES=:ffffff:
Jun  4 14:23:22 localhost udevd[14799]: MODE 0664 /lib/udev/rules.d/50-udev-default.rules:55
Jun  4 14:23:22 localhost udevd[14799]: IMPORT builtin skip 'usb_id' /lib/udev/rules.d/50-udev-default.rules:56
Jun  4 14:23:22 localhost udevd[14799]: PROGRAM 'mtp-probe /sys/devices/pci0000:00/0000:00:0b.1/usb1/1-8 1 43' /lib/udev/rules.d/60-libmtp.rules:809
Jun  4 14:23:22 localhost udevd[14800]: starting 'mtp-probe /sys/devices/pci0000:00/0000:00:0b.1/usb1/1-8 1 43'
Jun  4 14:23:22 localhost mtp-probe: checking bus 1, device 43: "/sys/devices/pci0000:00/0000:00:0b.1/usb1/1-8"
Jun  4 14:23:22 localhost mtp-probe: bus: 1, device: 43 was not an MTP device
Jun  4 14:23:22 localhost udevd[14799]: 'mtp-probe /sys/devices/pci0000:00/0000:00:0b.1/usb1/1-8 1 43'(out) '0'
Jun  4 14:23:22 localhost udevd[14799]: 'mtp-probe /sys/devices/pci0000:00/0000:00:0b.1/usb1/1-8 1 43' [14800] exit with return code 0
Jun  4 14:23:22 localhost udevd[14799]: device 0x1a962e0 filled with db file data
Jun  4 14:23:22 localhost udevd[14799]: handling device node '/dev/bus/usb/001/043', devnum=c189:42, mode=0664, uid=0, gid=0
Jun  4 14:23:22 localhost udevd[14799]: set permissions /dev/bus/usb/001/043, 020664, uid=0, gid=0
Jun  4 14:23:22 localhost udevd[14799]: creating symlink '/dev/char/189:42' to '../bus/usb/001/043'
Jun  4 14:23:22 localhost udevd[14799]: created db file '/run/udev/data/c189:42' for '/devices/pci0000:00/0000:00:0b.1/usb1/1-8'
Jun  4 14:23:22 localhost udevd[14799]: passed -1 bytes to netlink monitor 0x1a95480
Jun  4 14:23:22 localhost udevd[14689]: seq 2035 done with 0
Jun  4 14:23:22 localhost udevd[14689]: passed 339 bytes to netlink monitor 0x1a7f5c0
Jun  4 14:23:22 localhost udevd[14799]: seq 2035 processed with 0
Jun  4 14:23:22 localhost udevd[14799]: seq 2036 running
Jun  4 14:23:22 localhost udevd[14799]: device 0x1a94b00 has devpath '/devices/pci0000:00/0000:00:0b.1/usb1/1-8/1-8:1.0'
Jun  4 14:23:22 localhost udevd[14799]: no db file to read /run/udev/data/+usb:1-8:1.0: No such file or directory
Jun  4 14:23:22 localhost udevd[14799]: device 0x1a98510 has devpath '/devices/pci0000:00/0000:00:0b.1/usb1/1-8'
Jun  4 14:23:22 localhost udevd[14799]: RUN 'usb_modeswitch --driver-bind %p %s{idVendor} %s{idProduct} %E{PRODUCT}' /lib/udev/rules.d/40-usb_modeswitch.rules:16
Jun  4 14:23:22 localhost udevd[14799]: device 0x1a957b0 has devpath '/devices/pci0000:00/0000:00:0b.1/usb1'
Jun  4 14:23:22 localhost udevd[14799]: device 0x1a96b00 has devpath '/devices/pci0000:00/0000:00:0b.1'
Jun  4 14:23:22 localhost udevd[14799]: device 0x1a94d30 has devpath '/devices/pci0000:00'
Jun  4 14:23:22 localhost udevd[14799]: device 0x1a98510 filled with db file data
Jun  4 14:23:22 localhost udevd[14799]: IMPORT builtin 'kmod' /lib/udev/rules.d/80-drivers.rules:15
Jun  4 14:23:22 localhost udevd[14799]: execute 'load' 'usb:v04A9p30EEd0001dcFFdscFFdpFFicFFiscFFipFF'
Jun  4 14:23:22 localhost udevd[14799]: no module matches 'usb:v04A9p30EEd0001dcFFdscFFdpFFicFFiscFFipFF'
Jun  4 14:23:22 localhost udevd[14801]: starting 'usb_modeswitch --driver-bind /devices/pci0000:00/0000:00:0b.1/usb1/1-8/1-8:1.0   4a9/30ee/1'
Jun  4 14:23:23 localhost udevd[14799]: 'usb_modeswitch --driver-bind /devices/pci0000:00/0000:00:0b.1/usb1/1-8/1-8:1.0   4a9/30ee/1' [14801] exit with return code 0
Jun  4 14:23:23 localhost udevd[14799]: passed -1 bytes to netlink monitor 0x1a95480
Jun  4 14:23:23 localhost udevd[14799]: seq 2036 processed with 0
Jun  4 14:23:23 localhost udevd[14689]: seq 2036 done with 0

If I attempt to access the images via Digikam as root, I have no problem, but as a normal user I'm unable to see the usb mass storage camera device.

CC: (none) => simon

Same problem also exists on a Canon EOS 7D.

udev output in debug:

Jun  4 14:27:19 localhost kernel: [18562.455056] usb 1-8: new high-speed USB device number 44 using ehci_hcd
Jun  4 14:27:20 localhost kernel: [18562.571584] usb 1-8: New USB device found, idVendor=04a9, idProduct=319a
Jun  4 14:27:20 localhost kernel: [18562.571593] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun  4 14:27:20 localhost kernel: [18562.571599] usb 1-8: Product: Canon Digital Camera
Jun  4 14:27:20 localhost kernel: [18562.571604] usb 1-8: Manufacturer: Canon Inc.
Jun  4 14:27:20 localhost udevd[14689]: validate module index
Jun  4 14:27:20 localhost udevd[14689]: seq 2039 queued, 'add' 'usb'
Jun  4 14:27:20 localhost udevd[14689]: passed 315 bytes to netlink monitor 0x1a7f5c0
Jun  4 14:27:20 localhost udevd[14799]: seq 2039 running
Jun  4 14:27:20 localhost udevd[14799]: device 0x1a94b00 has devpath '/devices/pci0000:00/0000:00:0b.1/usb1/1-8'
Jun  4 14:27:20 localhost udevd[14799]: no db file to read /run/udev/data/c189:43: No such file or directory
Jun  4 14:27:20 localhost udevd[14799]: device 0x1a7f840 has devpath '/devices/pci0000:00/0000:00:0b.1/usb1'
Jun  4 14:27:20 localhost udevd[14799]: device 0x1a95150 has devpath '/devices/pci0000:00/0000:00:0b.1'
Jun  4 14:27:20 localhost udevd[14799]: device 0x1a960a0 has devpath '/devices/pci0000:00'
Jun  4 14:27:20 localhost udevd[14799]: IMPORT builtin 'usb_id' /lib/udev/rules.d/40-libgphoto2.rules:11
Jun  4 14:27:20 localhost udevd[14689]: seq 2040 queued, 'add' 'usb'
Jun  4 14:27:20 localhost udevd[14799]: ID_VENDOR=Canon_Inc.
Jun  4 14:27:20 localhost udevd[14799]: ID_VENDOR_ENC=Canon\x20Inc.
Jun  4 14:27:20 localhost udevd[14799]: ID_VENDOR_ID=04a9
Jun  4 14:27:20 localhost udevd[14799]: ID_MODEL=Canon_Digital_Camera
Jun  4 14:27:20 localhost udevd[14799]: ID_MODEL_ENC=Canon\x20Digital\x20Camera
Jun  4 14:27:20 localhost udevd[14799]: ID_MODEL_ID=319a
Jun  4 14:27:20 localhost udevd[14799]: ID_REVISION=0002
Jun  4 14:27:20 localhost udevd[14799]: ID_SERIAL=Canon_Inc._Canon_Digital_Camera
Jun  4 14:27:20 localhost udevd[14799]: ID_BUS=usb
Jun  4 14:27:20 localhost udevd[14799]: ID_USB_INTERFACES=:060101:
Jun  4 14:27:20 localhost udevd[14799]: MODE 0664 /lib/udev/rules.d/50-udev-default.rules:55
Jun  4 14:27:20 localhost udevd[14799]: IMPORT builtin skip 'usb_id' /lib/udev/rules.d/50-udev-default.rules:56
Jun  4 14:27:20 localhost udevd[14799]: PROGRAM 'mtp-probe /sys/devices/pci0000:00/0000:00:0b.1/usb1/1-8 1 44' /lib/udev/rules.d/60-libmtp.rules:809
Jun  4 14:27:20 localhost udevd[14933]: starting 'mtp-probe /sys/devices/pci0000:00/0000:00:0b.1/usb1/1-8 1 44'
Jun  4 14:27:20 localhost mtp-probe: checking bus 1, device 44: "/sys/devices/pci0000:00/0000:00:0b.1/usb1/1-8"
Jun  4 14:27:20 localhost mtp-probe: bus: 1, device: 44 was not an MTP device
Jun  4 14:27:20 localhost udevd[14799]: 'mtp-probe /sys/devices/pci0000:00/0000:00:0b.1/usb1/1-8 1 44'(out) '0'
Jun  4 14:27:20 localhost udevd[14799]: 'mtp-probe /sys/devices/pci0000:00/0000:00:0b.1/usb1/1-8 1 44' [14933] exit with return code 0
Jun  4 14:27:20 localhost udevd[14799]: IMPORT builtin 'path_id' /lib/udev/rules.d/71-seat.rules:22
Jun  4 14:27:20 localhost udevd[14799]: ID_PATH=pci-0000:00:0b.1-usb-0:8
Jun  4 14:27:20 localhost udevd[14799]: ID_PATH_TAG=pci-0000_00_0b_1-usb-0_8
Jun  4 14:27:20 localhost udevd[14799]: device 0x1a7f840 filled with db file data
Jun  4 14:27:20 localhost udevd[14799]: RUN '/lib/systemd/systemd-uaccess $env{DEVNAME} $env{ID_SEAT}' /lib/udev/rules.d/73-seat-late.rules:15
Jun  4 14:27:20 localhost udevd[14799]: handling device node '/dev/bus/usb/001/044', devnum=c189:43, mode=0664, uid=0, gid=0
Jun  4 14:27:20 localhost udevd[14799]: set permissions /dev/bus/usb/001/044, 020664, uid=0, gid=0
Jun  4 14:27:20 localhost udevd[14799]: creating symlink '/dev/char/189:43' to '../bus/usb/001/044'
Jun  4 14:27:20 localhost udevd[14799]: created db file '/run/udev/data/c189:43' for '/devices/pci0000:00/0000:00:0b.1/usb1/1-8'
Jun  4 14:27:20 localhost udevd[14934]: starting '/lib/systemd/systemd-uaccess /dev/bus/usb/001/044 '
Jun  4 14:27:20 localhost udevd[14799]: '/lib/systemd/systemd-uaccess /dev/bus/usb/001/044 ' [14934] exit with return code 0
Jun  4 14:27:20 localhost udevd[14799]: passed -1 bytes to netlink monitor 0x1a95480
Jun  4 14:27:20 localhost udevd[14799]: seq 2039 processed with 0
Jun  4 14:27:20 localhost udevd[14689]: seq 2039 done with 0
Jun  4 14:27:20 localhost udevd[14689]: passed 327 bytes to netlink monitor 0x1a7f5c0
Jun  4 14:27:20 localhost udevd[14799]: seq 2040 running
Jun  4 14:27:20 localhost udevd[14799]: device 0x1a7fc30 has devpath '/devices/pci0000:00/0000:00:0b.1/usb1/1-8/1-8:1.0'
Jun  4 14:27:20 localhost udevd[14799]: no db file to read /run/udev/data/+usb:1-8:1.0: No such file or directory
Jun  4 14:27:20 localhost udevd[14799]: device 0x1a99bf0 has devpath '/devices/pci0000:00/0000:00:0b.1/usb1/1-8'
Jun  4 14:27:20 localhost udevd[14799]: device 0x1a97f80 has devpath '/devices/pci0000:00/0000:00:0b.1/usb1'
Jun  4 14:27:20 localhost udevd[14799]: device 0x1a94f20 has devpath '/devices/pci0000:00/0000:00:0b.1'
Jun  4 14:27:20 localhost udevd[14799]: device 0x1a957b0 has devpath '/devices/pci0000:00'
Jun  4 14:27:20 localhost udevd[14799]: device 0x1a99bf0 filled with db file data
Jun  4 14:27:20 localhost udevd[14799]: IMPORT builtin 'kmod' /lib/udev/rules.d/80-drivers.rules:15
Jun  4 14:27:20 localhost udevd[14799]: execute 'load' 'usb:v04A9p319Ad0002dc00dsc00dp00ic06isc01ip01'
Jun  4 14:27:20 localhost udevd[14799]: no module matches 'usb:v04A9p319Ad0002dc00dsc00dp00ic06isc01ip01'
Jun  4 14:27:20 localhost udevd[14799]: passed -1 bytes to netlink monitor 0x1a95480
Jun  4 14:27:20 localhost udevd[14689]: seq 2040 done with 0
Jun  4 14:27:20 localhost udevd[14799]: seq 2040 processed with 0

Found that thread on opensuse  : http://forums.opensuse.org/english/get-technical-help-here/applications/457344-digikam-i-can-only-access-camera-root-user-opensuse-11-4-kde.html

I've tried the /usr/lib/libgphoto2/print-camera-list udev-rules mode 0660 version 0.98 group lp > /etc/udev/rules.d/90-libgphoto2.rules and adding my user to lp group, reboot and it works
So perhaps there his a problem of populing the libgphoto2 rules in mageia2

@Christophe, it is all about udev rules! See my previous comments. The newer package includes new rules.

So this should be working fine in cauldron now.

I'll ask again on the cauldron list if an update is sanctioned.

I'm note using cauldron, i'm a mageia 2 x64 user. I could install manually related new package for test. Where can i fond them?

@Christophe: Updated gphoto and libgphoto packages are now available in the core/updates_testing area for Mageia 2. I'd appreciate it if you could install those packages and let me know if they work for you! Thanks.

Tested from core/updates_testing:

gphoto2-2.4.14-0.1.mga2.x86_64.rpm
lib64gphoto2-2.4.14-0.1.mga2.x86_64.rpm
libgphoto-common-2.4.14-0.1.mga2.x86_64.rpm

This does solve the permissions problem for me. I am able to view and import media from my Canon 7D via Digikam's import/cameras feature as my non priv user.

Note that I'm not getting a KDE Device Notifier pop up when I plug the camera in like I did with Mageia 1 that allows me to select an application to use for the media device.

Here's the /var/log/messages output:

Jul 10 07:42:59 localhost kernel: [ 1238.151030] usb 6-3: new high-speed USB device number 4 using ehci_hcd                                                           
Jul 10 07:42:59 localhost kernel: [ 1238.267745] usb 6-3: New USB device found, idVendor=04a9, idProduct=319a                                                         
Jul 10 07:42:59 localhost kernel: [ 1238.267749] usb 6-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0                                                    
Jul 10 07:42:59 localhost kernel: [ 1238.267752] usb 6-3: Product: Canon Digital Camera                                                                               
Jul 10 07:42:59 localhost kernel: [ 1238.267754] usb 6-3: Manufacturer: Canon Inc.                                                                                    
Jul 10 07:42:59 localhost mtp-probe: checking bus 6, device 4: "/sys/devices/pci0000:00/0000:00:13.2/usb6/6-3"                                                        
Jul 10 07:42:59 localhost mtp-probe: bus: 6, device: 4 was not an MTP device

sorry, doesn't work for me with an old Canon gé. What output do you want to see what happen for me?

No regression using my cell, i need to check my cameras though.
PTP mode does not allow adding a file by using dolphing, error is that we cannot write using ptp, but deleting a file works... odd.

here are the log from /var/log/message
Jul 11 12:47:03 localhost kernel: [ 2301.995025] usb 2-2: new full-speed USB device number 3 using uhci_hcd
Jul 11 12:47:03 localhost kernel: [ 2302.146017] usb 2-2: New USB device found, idVendor=04a9, idProduct=3055
Jul 11 12:47:03 localhost kernel: [ 2302.146021] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jul 11 12:47:03 localhost kernel: [ 2302.146024] usb 2-2: Product: PowerShot G2
Jul 11 12:47:03 localhost kernel: [ 2302.146027] usb 2-2: Manufacturer: Canon Inc.
Jul 11 12:47:04 localhost mtp-probe: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-2"
Jul 11 12:47:04 localhost mtp-probe: bus: 2, device: 3 was not an MTP device

and i put message from gphoto2 in attachement my-logfile_cb_20120711.txt

Created attachment 2552 [details]
output from gphoto2 aftter applying last tst package of gphoto2

*** Bug 6332 has been marked as a duplicate of this bug. ***

What's the status of this update? Is it ready to be handled to QA, or are there still fixes to be done?

SRPM list:
libgphoto-2.4.14-0.1.mga2.src.rpm
gphoto2-2.4.14-0.1.mga2.src.rpm

Doesn't work for me with gphoto2-2.4.14-0.1.mga2.x86_64.rpm
lib64gphoto2-2.4.14-0.1.mga2.x86_64.rpm
libgphoto-common-2.4.14-0.1.mga2.x86_64.rpm
and it does not solve my problem. Will try to verify again when possible.

@Christophe Sorry, I missed your log last time around. Can you upload the output from gphoto2 again but use LC_ALL=c first such that the log is in English and I can understand it? ;)

Many thanks.

Created attachment 2706 [details]
gphoto2 error file

@colin, here is my log file in english that time :)

OK, so looking at this more closely it seems that the udev rules do not get generated properly during the build process (works fine for me locally but not via the build system). Same issue on cauldron, and I think I know what's up generally.

Can you run the following command (as root) and see if it helps?

/usr/lib*/libgphoto2/print-camera-list udev-rules version 136 >/lib/udev/rules.d/40-libgphoto2.rules


This will regenerate the udev rules and fully populate them.

Alternatively, please try: libgphoto-2.4.14-0.2.mga2 which should be available soon via core/updates_testing.

For reference, when build via the chroot, the print-camera-list couldn't find the camera libraries and thus the udev rules generates where pretty limited and didn't include the proper devices. The fix is simply to include the CAMDIR= env var in the command run such that it knows where to look for the various camera libraries.

(PS if you are on cauldron, I've update the libgphoto package there too)

Created attachment 2712 [details]
error file from gphoto2

sorry, stil doesn't work. I've first update lib64gphoto2-2.4.14-0.2.mga2.x86_64.rpm  from ftp://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/2/x86_64/media/core/updates_testing/ then executing "env LC_ALL=c LANG=C gphoto2 --debug --debug-logfile=my-logfile_new2.txt -L" . Here is the error file
Then use your script as root, return as user and exec again gphoto and still got i/o error

Mageia 2 not access Camera USB.

I can access Camera USB only through Mageia 1, that recognizes immediately after I connect the camera in the computer USB.

Mageia Forum: Mageia 2 not access photographic camera
https://forums.mageia.org/en/viewtopic.php?f=7&t=3756

CC: (none) => terraagua

I verified that the Mageia 2 recognizes the "canon usb camera" as a regular user, but does not access the photos. As root, Mageia 2 recognizes the camera and access the photos.

Therefore I think that there is a problem of permission to access some cameras as common user in Mageia 2.

Despite this information, I could not solve the ploblema. I still can not access the photos from the camera as normal user

Mageia Forum: Mageia 2 not access photographic camera
https://forums.mageia.org/en/viewtopic.php?f=7&t=3756#p27435

@macxi are you sure you're using the updated packages in the testing repository as mentioned in comment 32?

Yes. 
I'm using all the updated packages, until today, November 7, 2012.

I did the test in Mageia 2 with repositories 1, 3, 11, 13, 21 and 23 enabled.

The Mageia 2 is with the kernel-desktop-3.3.8-2.mga2-1-1.mga2.x86_64 installed 

I also tested in Mageia 2, 32bits, and the same error occured.

@macxi, the repository numbers don't mean much I'm afraid. You need to enable the "testing" repositories" and selectively install the libgphoto related packages.

To check what version you have installed run: rpm -q libgphoto-common and I'll advise further.

(In reply to comment #39)
> @macxi, the repository numbers don't mean much I'm afraid. You need to enable
> the "testing" repositories" and selectively install the libgphoto related
> packages.
> 
> To check what version you have installed run: rpm -q libgphoto-common and I'll
> advise further.

@ macxi

Did you see the above comment from Colin?

Keywords: (none) => NEEDINFO

Marja and Colin, 

I have not installed it yet, but I saw the changelog for version of "libgphoto-common 2.4.14" indicates the error is corrected.

When installing the software digiKam, the package installed is "libgphoto-common 4.2.11" (with standard media enabled)

If enable media "Core Updates Testing" (distrib5), will be available for installation package "libgphoto-common 2.4.14",  which fixes the problem of access to Canon Camera.

See changelog:

   * "Fri 31 Aug 2012 09:00:00 EDT colin <colin> 2.4.14-0.2.mga2
         + Revision: 286671
         - Properly generate camera udev rules When building in a chroot
           (mga # 4177)"

I have not done yet because, if I enable media "Core Updates Testing" (distrib5) to install the package libgphoto-common 2.4.14, will be installed along the rpmdrake update, that is not available if you enable only the default media:

"The rpmdrake or dependencies need to be updated, after which the
rpmdrake restarts.
The following 5 programs will be installed:
- Lib64rpm2-4.9.1.3-2.1.mga2.x86_64
- Libgphoto-common-2.4.14-0.2.mga2.x86_64 <----- Digikam
- Rpm-python-4.9.1.3-2.1.mga2.x86_64
- Rpm-4.9.1.3-2.1.mga2.x86_64
- Rpmdrake-5.34.1-1.mga2.noarch
280KB of additional disk space will be used.
2.1MB in rpm packages will be downloaded."

When I get to do the test, I notice here.
Thank you

(In reply to comment #41)
> Marja and Colin, 
> 
> I have not installed it yet, but I saw the changelog for version of
> "libgphoto-common 2.4.14" indicates the error is corrected.
> 

> See changelog:
> 
>    * "Fri 31 Aug 2012 09:00:00 EDT colin <colin> 2.4.14-0.2.mga2
>          + Revision: 286671
>          - Properly generate camera udev rules When building in a chroot
>            (mga # 4177)"
> 
> I have not done yet because, if I enable media "Core Updates Testing"
> (distrib5) to install the package libgphoto-common 2.4.14, will be installed
> along the rpmdrake update, that is not available if you enable only the default
> media:
> 
Thanks for the feedback, Macxi :)

It is also possible to fetch the package directly from a mirror, e.g.:

ftp://mageia.webconquest.com/distrib/2/x86_64/media/core/updates_testing/libgphoto-common-2.4.14-0.2.mga2.x86_64.rpm

without enabling the core/updates_testing repository

Marja, 

Thanks for your help

I tested the Mageia 2 (32bit) and Mageia 2 (64bit). 

Now everything is working well. But is needed to install two packages for each of them.
___________

For Mageia 2 (32bit) is needed to install two packages:

ftp://mageia.webconquest.com/distrib/2/i586/media/core/updates_testing/libgphoto2-2.4.14-0.2.mga2.i586.rpm

ftp://mageia.webconquest.com/distrib/2/i586/media/core/updates_testing/libgphoto-common-2.4.14-0.2.mga2.i586.rpm

_____________

For Mageia 2 (64bit) is needed to install two packages:

ftp://mageia.webconquest.com/distrib/2/x86_64/media/core/updates_testing/libgphoto-common-2.4.14-0.2.mga2.x86_64.rpm

ftp://mageia.webconquest.com/distrib/2/x86_64/media/core/updates_testing/lib64gphoto2-2.4.14-0.2.mga2.x86_64.rpm

You likely also want to install:
ftp://mageia.webconquest.com/distrib/2/i586/media/core/updates_testing/gphoto2-2.4.14-0.1.mga2.i586.rpm
 or
ftp://mageia.webconquest.com/distrib/2/x86_64/media/core/updates_testing/gphoto2-2.4.14-0.1.mga2.x86_64.rpm

But as everything is working I think this should count as a validation of the pkgs!

Colin, 

I had not installed the file gphoto2-2.4.11, just the packages lib64gphoto2-2.4.14 and libgphoto-common-2.4.14,  and everything worked ok. 

After your message I installed the package gphoto2-2.4.11 and everything worked. 

And after, I instaled the package gphoto2-2.4.14, and everything worked well too (in both 32bit and 64bit):

 - I accessed the pictures from Canon camera (model EOS 300D) via the software "Digikam" and;
 - I accessed the camera model via the "System Settings" in "Digital Camera" in "sets Kamera" 

Thanks

(In reply to comment #44)
> 
> But as everything is working I think this should count as a validation of the
> pkgs!

(In reply to comment #45)
> Colin, 
> 
> I had not installed the file gphoto2-2.4.11, just the packages
> lib64gphoto2-2.4.14 and libgphoto-common-2.4.14,  and everything worked ok. 
> 

> And after, I instaled the package gphoto2-2.4.14, and everything worked well
> too (in both 32bit and 64bit):
> 
>  - I accessed the pictures from Canon camera (model EOS 300D) via the software
> "Digikam" and;
>  - I accessed the camera model via the "System Settings" in "Digital Camera" in
> "sets Kamera" 
> 

@ Colin

Do you have an advisory for QA, or is it not ready for QA because of Christophe's problem with it? (see comment 34)

Keywords: NEEDINFO => (none)

I think it's probably ready. I've double checked the rules on the mirror and they are properly generated. Certainly it can't be any worse than the version in release, so it's always going to be an improvement from there even if it's not working for every possible camera!

As far as advisory:

Advisory Text
=============

The version of libgphoto shipped with Mageia two had a packaging error which prevented the udev rules required to give an unprivileged user access to cameras from being included properly.

This updated package rectifies this issue and updates the package to a newer version which also includes support for newer cameras including the popular Canon EOS-10D



SRPMS:
gphoto2-2.4.14-0.1.mga2.src.rpm
libgphoto-2.4.14-0.2.mga2.src.rpm

Macxi has confirmed this update fixes the bug on both i586 and x86_64 so just checking the basics.

Version: Cauldron => 2
Whiteboard: MGA2TOO => (none)

RPMS:

gphoto2
libgphoto2
libgphoto-common
libgphoto-devel

Testing complete mga2 32

Before
------
# cat /lib/udev/rules.d/40-libgphoto2.rules
# udev rules file for libgphoto2 devices (for udev 136 version)
# Created from this library:
#   libgphoto2      2.4.11         gcc, ltdl, EXIF
#   libgphoto2_port 0.8.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{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"


LABEL="libgphoto2_usb_end"


LABEL="libgphoto2_rules_end"

After
-----

Lots of extra lines for the various usb id's.

Whiteboard: (none) => mga2-32-OK

Testing complete mga2 64

As above plus gphoto2 -L with camera plugged in and set to PTP mode.

Validating

Advisory and srpms in comment 47

Could sysadmin please push from core/updates_testing to core/updates

Thanks!

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs
Whiteboard: mga2-32-OK => mga2-32-OK mga2-64-OK

Update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0231

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED