Janek Kozicki wrote: > Is there any alternative solution for that, which does not depend on > consolekit? A slightly crappy alternative would be: 1. Make sure the audio devices are group owned and group writable by e.g. an "audio" group. 2. Make sure all your users are in the audio group. 3. Assign each user to a head and hard code the default.pa file to load only the specific alsa device they should use. This is not ideal as if you swap round, your sound devices will stay as the old ones which is not very nice. Console kit is responsible for assigning ACLs to hardware for the "active" user. This is how things are working these days and I think the only proper solution is to ensure that console kit is multi-seat/head aware, allowing the tieing together of a graphics output card/port and a sound device. This is way, way beyond my knowledge of consolekit tho'.! From the original announcement, it seems that this is a goal of consolekit: http://lists.freedesktop.org/archives/hal/2007-January/006996.html I've no idea about it's current state of affairs. Perhap the hal mailing list is a good place to discuss/ask about it? Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
