Re: Re: gphoto2 problem: usb access for non root users

[Gianluca Cecchi]

On Tue, 31 Jan 2006 22:04:59 +0100 Gianluca Cecchi wrote:
> > Asap I'll reboot ala windows and see if anything changes...
> ;-( 
Actually I did:
- init 3
- yum update of other latest packages
- init 5
- re-login in gnome as gcecchi
- plug digicamera
- all ok now!

Gianluca

gphoto2 problem: usb access for non root users

[Jesse Barnes]

On Tuesday, January 31, 2006 2:02 pm, Gianluca Cecchi wrote:
>  On Tue, 31 Jan 2006 22:04:59 +0100 Gianluca Cecchi wrote:
>  >> Asap I'll reboot ala windows and see if anything changes... ;-(
>
>  Actually I did:
>  - init 3
>  - yum update of other latest packages
>  - init 5
>  - re-login in gnome as gcecchi
>  - plug digicamera
>  - all ok now! 
Hm, I haven't been so lucky.  When I plugin my camera, I get a popup 
under KDE asking me if I want to open a window.  If I select 'yes' the 
window comes up but times out saying it couldn't claim the usb device, 
presumably because both /proc/bus/usb and /dev/bus/usb are owned 
completely by root.  My /usr/libexec/gphoto-udev-thunk-set-my-perms 
script has the right lines to set the perms, but maybe HAL isn't 
setting the right env. vars for it when it's called?

Jesse

gphoto2 problem: usb access for non root users

[Bill Nottingham]

Jesse Barnes (jbarnes(a)virtuousgeek.org) said: 
>  Hm, I haven't been so lucky.  When I plugin my camera, I get a
> popup 
>  under KDE asking me if I want to open a window.  If I select 'yes' the 
>  window comes up but times out saying it couldn't claim the usb device, 
>  presumably because both /proc/bus/usb and /dev/bus/usb are owned 
>  completely by root.  My /usr/libexec/gphoto-udev-thunk-set-my-perms 
>  script has the right lines to set the perms, but maybe HAL isn't 
>  setting the right env. vars for it when it's called? 
What hal, udev, and libusb do you have?

Bill

gphoto2 problem: usb access for non root users

[Jesse Barnes]

On Monday, February 27, 2006 9:13 am, Bill Nottingham wrote:
>  Jesse Barnes (jbarnes(a)virtuousgeek.org) said:
>  > Hm, I haven't been so lucky.  When I plugin my camera, I get a popup
>  > under KDE asking me if I want to open a window.  If I select 'yes'
>  > the window comes up but times out saying it couldn't claim the usb
>  > device, presumably because both /proc/bus/usb and /dev/bus/usb are
>  > owned completely by root.  My
>  > /usr/libexec/gphoto-udev-thunk-set-my-perms script has the right
>  > lines to set the perms, but maybe HAL isn't setting the right env.
>  > vars for it when it's called?
>
>  What hal, udev, and libusb do you have? 
The latest rawhide bits as of Saturday (sorry can't check them directly 
right now).  I've tried several reboots and changes of init levels since 
that seemed to work for Gianluca, but no dice.

If I wanted to add some additional echo statements to 
the /usr/libexec/gphoto-set-procperm where would their output show up?  
I wanted to check and see if the environment variables were getting set 
correctly, since everything else looks ok (guess I can just redirect to 
a file to do some debugging, I'll try that when I get home).

Thanks,
Jesse

gphoto2 problem: usb access for non root users

[Bill Nottingham]

Jesse Barnes (jbarnes(a)virtuousgeek.org) said: 
>  If I wanted to add some additional echo statements to 
>  the /usr/libexec/gphoto-set-procperm where would their output show up?  
>  I wanted to check and see if the environment variables were getting set 
>  correctly, since everything else looks ok (guess I can just redirect to 
>  a file to do some debugging, I'll try that when I get home). 
set > /tmp/gphoto.$$ should be simple enough for debugging.

Bill

gphoto2 problem: usb access for non root users

[Kostas Georgiou]

On Mon, Feb 27, 2006 at 12:48:48PM -0500, Bill Nottingham wrote:

>  Jesse Barnes (jbarnes(a)virtuousgeek.org) said: 
>  > If I wanted to add some additional echo statements to 
>  > the /usr/libexec/gphoto-set-procperm where would their output show up?  
>  > I wanted to check and see if the environment variables were getting set 
>  > correctly, since everything else looks ok (guess I can just redirect to 
>  > a file to do some debugging, I'll try that when I get home).
>  
>  set > /tmp/gphoto.$$ should be simple enough for debugging. 
Well since I am home
"chown $console_user /dev/bus/usb/$bus_num/$dev_num" fails with:
chown: cannot access `/dev/bus/usb/002/018': No such file or directory
Anything that slows down the script (ls /dev/bus/usb/$bus_num, usleep 1, etc.)
seems to be enough for the device to be created.

Should the script wait for the device to be created or is there a better
way to handle this?

gphoto2 problem: usb access for non root users

[Bill Nottingham]

Kostas Georgiou (k.georgiou(a)imperial.ac.uk) said: 
>  On Mon, Feb 27, 2006 at 12:48:48PM -0500, Bill Nottingham wrote:
>  
>  > Jesse Barnes (jbarnes(a)virtuousgeek.org) said: 
>  > > If I wanted to add some additional echo statements to 
>  > > the /usr/libexec/gphoto-set-procperm where would their output show up?  
>  > > I wanted to check and see if the environment variables were getting set 
>  > > correctly, since everything else looks ok (guess I can just redirect to 
>  > > a file to do some debugging, I'll try that when I get home).
>  > 
>  > set > /tmp/gphoto.$$ should be simple enough for debugging.
>  
>  Well since I am home
>  "chown $console_user /dev/bus/usb/$bus_num/$dev_num" fails with:
>  chown: cannot access `/dev/bus/usb/002/018': No such file or directory
>  Anything that slows down the script (ls /dev/bus/usb/$bus_num, usleep 1, etc.)
>  seems to be enough for the device to be created.
>  
>  Should the script wait for the device to be created or is there a better
>  way to handle this? 
David: when do the hal callouts get run - shouldn't they be run after
the device is created?

Bill

gphoto2 problem: usb access for non root users

[Bill Nottingham]

Kostas Georgiou (k.georgiou(a)imperial.ac.uk) said: 
>  On Mon, Feb 27, 2006 at 12:48:48PM -0500, Bill Nottingham wrote:
>  
>  > Jesse Barnes (jbarnes(a)virtuousgeek.org) said: 
>  > > If I wanted to add some additional echo statements to 
>  > > the /usr/libexec/gphoto-set-procperm where would their output show up?  
>  > > I wanted to check and see if the environment variables were getting set 
>  > > correctly, since everything else looks ok (guess I can just redirect to 
>  > > a file to do some debugging, I'll try that when I get home).
>  > 
>  > set > /tmp/gphoto.$$ should be simple enough for debugging.
>  
>  Well since I am home
>  "chown $console_user /dev/bus/usb/$bus_num/$dev_num" fails with:
>  chown: cannot access `/dev/bus/usb/002/018': No such file or directory
>  Anything that slows down the script (ls /dev/bus/usb/$bus_num, usleep 1, etc.)
>  seems to be enough for the device to be created.
>  
>  Should the script wait for the device to be created or is there a better
>  way to handle this? 
Oh, BTW. Please file a bug against hal, this appears to be due to
a race between the USB device creation and the callouts.

Bill

gphoto2 problem: usb access for non root users

[Gianluca Cecchi]

I was out last week (holiday, eh eh ;-) and now I'm downloading test3 torrents.
My system is up2date at 18th of February at the moment and I work
without any problem.
I'll let you know after test3.
> From your e-mail, I presume you are in kde as DE, aren't you?
> Could it 
be that interferring in some way?
I only made my tests with gnome running and using gphoto2 comand to
debug and digikam as fe application.
Today when @home I can test with kde too, to see pop ups. In gnome I
have no automatic graphic pop ups, I have to run digikam after
inserting digicamera.
I have to open a bug because for example if you mount a filesystem
when inside gnome,
when you exit, it is automatically dismounted.... so in initialitation
phases it seems there some triggers that could interfere also in your
case, just an attempt...
Apart from the kde popups, the messages that you receive with
gphoto2 --auto-detect are the same as mine at the beginning of the
thread, with success for root and nothing for users? Other messages in
/var/log/messages or with dmesg command?
And what about exact permissions assigned to files/directories I cited
in my posts?
Gianluca
2006/2/27, Jesse Barnes <jbarnes(a)virtuousgeek.org&gt;:
>  On Monday, February 27, 2006 9:13 am, Bill Nottingham wrote:
>  > Jesse Barnes (jbarnes(a)virtuousgeek.org) said:
>  > > Hm, I haven't been so lucky.  When I plugin my camera, I get a popup
>  > > under KDE asking me if I want to open a window.  If I select 'yes'
>  > > the window comes up but times out saying it couldn't claim the usb
>  > > device, presumably because both /proc/bus/usb and /dev/bus/usb are
>  > > owned completely by root.

gphoto2 problem: usb access for non root users

[Gianluca Cecchi]

2006/2/28, Gianluca Cecchi <gianluca.cecchi(a)gmail.com&gt;:
>  Today when @home I can test with kde too, to see pop ups. 
tried
with updates at 18th of february and logged in with kde as de.

After connecting my camera (that uses ptp protocol) I get:
- window popup saying: new medium has been detected
  what do you want to do?
- I select "open in new window"
- konqueror opens positioned in system:/media/camera
- it seems very slow reading contents from digicamera
it detects only 4 items at the beginning showing 4% progress
at bottom right and then finds anything different from
four files
store_00010001
store_00020001
about.txt
summary.txt
inside kde konsole as normal user I correctly get:
[gcecchi@fedora ~]$ gphoto2 --auto-detect
Model                          Port
----------------------------------------------------------
Kodak CX7525                   usb:
Kodak CX7525                   usb:002,002

so it seems to me a problem in konqueror plugin (which one?) to read
digicamera contents.
Or perhaps you have problems only if ptp protocol is used... and
digicameras that use the other protocol (usb mass storage aka scsi
over usb) that gets the storage detected as scsi disks work better in
konqueror plugin...
BTW what are secs for your digicamera?
To debug, try install digikam from extras and see if it works.
Or use the default gnome application for this (don't remember its
name) inside kde de.
See also gphoto2 supported cameras list, to match yours:
http://www.gphoto.org/proj/libgphoto2/support.php

HIH,
Gianluca

gphoto2 problem: usb access for non root users

[Jesse Barnes]

>  so it seems to me a problem in konqueror plugin (which one?) to read
>  digicamera contents. 
Yeah, I see the same thing too if I use the system:/ kioslave.  camera:/ 
still seems to work fine though.  To summarize:
  o permissions are still set incorrectly as of my 'yum upgrade' today
  o system:/media/camera kioslave is broken and doesn't list camera
    contents correctly (folders show up as files)

I'll look around and see if the HAL callout bug has been filed and/or 
fixed.

Jesse