Not sure if this is the way it works or it could work: To deliver proper consolekit functionality even with audio group members present: If consolekit is installed and enabled, disable (udev?) to set the ownership of sound devices to the audio group. (policy: "give precedence to console users")
Then, if the console user is a member of the audio, let consolekit set the sound device ownership to the private group of the console user (root:<user>) This should avoid the conflict and not give access to unprivileged console users, yet enable exclusive access for one privileged console user, which may still individually decide to share its pulseaudio? socket with other users. Remember there may be multiple seats per machine. In this case, the first console user to login may be given exclusive access by default, but each console user should be able to request exclusive access from devicekit? and get it if the device is not used. If the device is in use, access depends on the permissions the first user grants to others. Additionally, a "shared-console"? group could be introduced to provide the option to grant all console users shared group access to the sound device? Consolekit checking against the group and adding the members to ACLs? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
