ivman drops additional groups for ivman user

Bug #174648 reported by Robert Penz
4
Affects Status Importance Assigned to Milestone
ivman (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: ivman

Hi!

I'm using ivman to start a script which syncs my computer automatically with an mp3 player. The syncing part works without problem but I've a problem with the user/group the ivman process is running. I want that the computer makes a beep if all is synced. For this I've put the ivman user into the audio group:

root@darksun:~# su -m ivman
ivman@darksun:~$ id
uid=111(ivman) gid=46(plugdev) groups=29(audio),46(plugdev)

but if I call "id" in a script thats called by ivman I get following output

uid=111(ivman) gid=46(plugdev)

Somehow additional groups are dropped, which makes it impossible to access devices which require the user to be in a special group. I additionally I found out that its a difference if ivman is launched at startup or (re)startet via sudo - so there is more unclean in the user/group handling.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10?

What does running `id' after `su - ivman' give you?

Changed in ivman:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in ivman:
status: Incomplete → Invalid
Revision history for this message
RandomGameR (cannedpeople) wrote :

Hello, I'm using Jaunty x64 server edition and trying to setup something that is exactly as this original bug describes. ivman is set in its config file to run as user ivman and as group cdrom. The user ivman is a member of groups private, cdrom, plugdev, and ivman. The problem is that if it is not running as group cdrom it cannot access the cdrom drive even though its permissions are set to be part of group cdrom. We want it to write to a folder only owned by group private but it cannot do that either. Our script runs fine if we make our private folder public.

Changed in ivman (Ubuntu):
status: Invalid → New
Changed in ivman (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.