Hello,
Today I wanted to move some xmas images from my digital camera,
using digikam. I hadn't done so since November last year. To my
astonishment, it didn't work any more.
Since lsusb under root showed my camera, but lsusb under my personal
account didn't, I quickly discovered that this is related to the
permission of one of /dev/usbdev*. chmod 666 on them; then lsusb and
digikam worked and I was again able to access my camera with my
personal acount.
Well, but of course this will only last only until the next boot,
when udev establishs the default access rights again.
Checking the mailing list's archive, I discovered a thread from Nov
28 where this problem was mentioned by Martin Mielke, but no
solution was posted.
So I was wondering:
-- Has this been resolved somehow and I missed the resolution?
-- Shouldn't the devices made available to the user that is logged
in on the console? I.e., shouldn't resmgr care for them?
No ACL is set on usbdev*, unlike /dev/sr0 or other devices.
And really, in /etc/resmgr.conf there is an entry for "class usb".
Hmm, but there seems to be something missing. When I call (as root)
resmgr list usb, it outputs "no devices available". hwinfo --usb
finds usb hardware, but doesn't output device files in /dev either.
Therefore my final questions:
-- Should the ACLs for the USB devices be changed by resmgr?
-- If yes, how does resmgr determine which devices shall be
changed?
-- If no, how is a desktop user expected to use a USB device?
Thanks in advance for any answer,
Joachim
PS: In case that KDE or GNOME are expected to do some magic during
login; I use neither of them.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: [EMAIL PROTECTED]
Roedermark, Germany
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
