Package: libgphoto2-2
Followup-For: Bug #427963

Hi all!

I tracked a bit the problems with the libgphoto2-2 and udev problems.
There seem to be several bugs:

1) The check-ptp-camera uses $PHYSDEVPATH instead of $DEVPATH, so the
   program always returns 1 and the rules for PTP cameras are never
   executed. This is a pain.

2) (not sure about this) the libgphoto2.rules uses
       ATTRS{idVendor}
   etc, but AFAIS it should be
       ATTR{idVendor}
   etc.

2) Even worse, but I wasn't able to fix this even with the above fix
   applied, is the problem with the /proc/bus/usb/*/* permissions.
   Interestingly udev creates devices for my camera WITH the
   right permissions, namely 
      /dev/1-3
   (yup, strange where it is coming from). But of course gphoto2 does
   not check for this device but for /proc/bus/usb/NNN/NNN and this file
   has wrong permissions.

So please maintainer, could you at least suggest a fix to this problem,
or even better upload fixed versions.

Thanks

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-rc4 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages libgphoto2-2 depends on:
ii  adduser                       3.103      Add and remove users and groups
ii  libc6                         2.5-11     GNU C Library: Shared libraries
ii  libexif12                     0.6.15-1   library to parse EXIF files
ii  libgphoto2-port0              2.3.1-5    gphoto2 digital camera port librar
ii  libjpeg62                     6b-13      The Independent JPEG Group's JPEG 
ii  libltdl3                      1.5.22-4   A system independent dlopen wrappe

Versions of packages libgphoto2-2 recommends:
ii  udev                          0.105-4    /dev/ and hotplug management daemo

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to