2006/9/11, Marcus Meissner <[EMAIL PROTECTED]>:
On Mon, Sep 11, 2006 at 01:50:56PM -0300, Juan Erbes wrote:
> Many weeks ago, upgrading with smart, it replaced mDNSResponder with
> avahi-compat-mDNSResponder, and then, Digikam has hanged, any time I
> would to connect the cam. Then I installed mDNSResponder with smart,
> and it has removed avahi-compat-mDNSResponder, and digikam worked ok.
> With the two last updates (the last was not complete), Digicam can't
> connec to the camera, but now I mean that is a permission problem,
> derived from PolicyKit, because the permissions are set only to root
> in the usb devices.
digikam will also likely crash when using avahi-compat-mDNSResponder
and camera autodetect.
I have'nt installed avahi-compat-mDNSResponder.
The message from dmesg is:
usb 5-1: new full speed USB device using uhci_hcd and address 2
usb 5-1: new device found, idVendor=04a9, idProduct=3055
usb 5-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 5-1: Product: PowerShot G2
usb 5-1: Manufacturer: Canon Inc.
usb 5-1: configuration #1 chosen from 1 choice
I do'nt know waht is "configuration #1 chosen from 1 choice"
About permission (the last connection):
ls -l /dev/bus/usb/005/005
crw-rw-r--+ 1 root root 189, 516 2006-09-11 18:11 /dev/bus/usb/005/005
With the introduction of udev in version 10.1, I got similar problems,
and the problems was with wrong permissions in this oportunity. I mean
the problem is now the same, and derived from PolicyKit.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
