Re: [pulseaudio-discuss] only "dummy audio" available when many users want to use one audio card
On Sat, 21.11.09 22:18, Tomasz Chmielewski (man...@wpkg.org) wrote: > I have a multiseat workstation - two graphics cards, two > keyboards/mice, two monitors, but one audio card. > > Before pulseaudio was mainstream, I was using ALSA, and both users > could use audio. Which was a big security hole since that way evil users may eavesdrop into other users voip calls, or even use the mic for surveillance purposes. Due to that we generally consider audio devices to be part of the seat the same ways a mouse, a keyboard or a screen is. Also, I am still wondering how you manage to seat two people at the same distance from the L and R speakers... I mean, the only way how that could work is one sits on the others lap... Lennart -- Lennart PoetteringRed Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] only "dummy audio" available when many users want to use one audio card
'Twas brillig, and Tomasz Chmielewski at 25/11/09 19:02 did gyre and gimble: Colin Guthrie wrote: This is typically a permissions problem. Does the "pulse" user (which IIRC is used by system mode) have permissions to open the sound devices? All right, this was it! I wish pulsaudio with multiple users was more straightforward one day. Well it is rather simple with multiple users... just not at the same time! The multi-seat setup is still rather niche compared to the multi-user setup (e.g. OSX+Windows do the same multi-user stuff we enable OOTB too). Even on multi-seat systems, most of the time each seat has it's own dedicated device (e.g. USB speakers) or similar. This is being dealt with and will be supported with a standard pulse install reasonably soon (whenever the consolekit/udev support is there basically). So really, we're not too bad for the 99% percent of use cases :p 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/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] only "dummy audio" available when many users want to use one audio card
Colin Guthrie wrote: This is typically a permissions problem. Does the "pulse" user (which IIRC is used by system mode) have permissions to open the sound devices? All right, this was it! I wish pulsaudio with multiple users was more straightforward one day. -- Tomasz Chmielewski http://wpkg.org ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] only "dummy audio" available when many users want to use one audio card
'Twas brillig, and Tomasz Chmielewski at 25/11/09 18:27 did gyre and gimble: Colin Guthrie wrote: There should be some info kicking around about system mode PA if you google around for it. I don't have much success with getting audio for two users with pulseaudio. I start pulsaudio as root with these options: # pulseaudio --log-target=syslog --system -D --disallow-exit And get this info in syslog; both users only have "dummy audio". So it's even worse this way. Nov 25 19:23:40 dom pulseaudio[21012]: main.c: Running in system mode, but --disallow-module-loading not set! Nov 25 19:23:40 dom pulseaudio[21012]: main.c: Running in system mode, forcibly disabling SHM mode! Nov 25 19:23:40 dom pulseaudio[21012]: main.c: Running in system mode, forcibly disabling exit idle time! Nov 25 19:23:40 dom pulseaudio[21013]: main.c: OK, so you are running PA in system mode. Please note that you most likely shouldn't be doing that. Nov 25 19:23:40 dom pulseaudio[21013]: main.c: If you do it nonetheless then it's your own fault if things don't work as expected. Nov 25 19:23:40 dom pulseaudio[21013]: main.c: Please read http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode for an explanation why system mode is usually a bad idea. Nov 25 19:23:40 dom pulseaudio[21013]: module.c: module-hal-detect is deprecated: Please use module-udev-detect instead of module-hal-detect! Nov 25 19:23:40 dom pulseaudio[21013]: module-alsa-card.c: Card '0' doesn't exist: No such file or directory Nov 25 19:23:40 dom pulseaudio[21013]: module.c: Failed to load module "module-alsa-card" (argument: "device_id=0 name="pci_8086_3a3e_sound_card_0" card_name="alsa_card.pci_8086_3a3e_sound_card_0" tsched=1 card_properties="module-hal-detect.discovered=1""): initialization failed. Nov 25 19:23:40 dom pulseaudio[21013]: module-alsa-card.c: Card '2' doesn't exist: No such file or directory Nov 25 19:23:40 dom pulseaudio[21013]: module.c: Failed to load module "module-alsa-card" (argument: "device_id=2 name="pci_1002_aa38_0_sound_card_2" card_name="alsa_card.pci_1002_aa38_0_sound_card_2" tsched=1 card_properties="module-hal-detect.discovered=1""): initialization failed. Nov 25 19:23:40 dom pulseaudio[21013]: module-alsa-card.c: Card '1' doesn't exist: No such file or directory Nov 25 19:23:40 dom pulseaudio[21013]: module.c: Failed to load module "module-alsa-card" (argument: "device_id=1 name="pci_1002_aa38_sound_card_1" card_name="alsa_card.pci_1002_aa38_sound_card_1" tsched=1 card_properties="module-hal-detect.discovered=1""): initialization failed. Nov 25 19:23:40 dom pulseaudio[21013]: main.c: Failed to acquire org.pulseaudio.Server: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.122" is not allowed to own the service "org.pulseaudio.Server" due to security policies in the configuration file This is typically a permissions problem. Does the "pulse" user (which IIRC is used by system mode) have permissions to open the sound devices? 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/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] only "dummy audio" available when many users want to use one audio card
Colin Guthrie wrote: > There should be some info kicking around about system mode PA if you > google around for it. I don't have much success with getting audio for two users with pulseaudio. I start pulsaudio as root with these options: # pulseaudio --log-target=syslog --system -D --disallow-exit And get this info in syslog; both users only have "dummy audio". So it's even worse this way. Nov 25 19:23:40 dom pulseaudio[21012]: main.c: Running in system mode, but --disallow-module-loading not set! Nov 25 19:23:40 dom pulseaudio[21012]: main.c: Running in system mode, forcibly disabling SHM mode! Nov 25 19:23:40 dom pulseaudio[21012]: main.c: Running in system mode, forcibly disabling exit idle time! Nov 25 19:23:40 dom pulseaudio[21013]: main.c: OK, so you are running PA in system mode. Please note that you most likely shouldn't be doing that. Nov 25 19:23:40 dom pulseaudio[21013]: main.c: If you do it nonetheless then it's your own fault if things don't work as expected. Nov 25 19:23:40 dom pulseaudio[21013]: main.c: Please read http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode for an explanation why system mode is usually a bad idea. Nov 25 19:23:40 dom pulseaudio[21013]: module.c: module-hal-detect is deprecated: Please use module-udev-detect instead of module-hal-detect! Nov 25 19:23:40 dom pulseaudio[21013]: module-alsa-card.c: Card '0' doesn't exist: No such file or directory Nov 25 19:23:40 dom pulseaudio[21013]: module.c: Failed to load module "module-alsa-card" (argument: "device_id=0 name="pci_8086_3a3e_sound_card_0" card_name="alsa_card.pci_8086_3a3e_sound_card_0" tsched=1 card_properties="module-hal-detect.discovered=1""): initialization failed. Nov 25 19:23:40 dom pulseaudio[21013]: module-alsa-card.c: Card '2' doesn't exist: No such file or directory Nov 25 19:23:40 dom pulseaudio[21013]: module.c: Failed to load module "module-alsa-card" (argument: "device_id=2 name="pci_1002_aa38_0_sound_card_2" card_name="alsa_card.pci_1002_aa38_0_sound_card_2" tsched=1 card_properties="module-hal-detect.discovered=1""): initialization failed. Nov 25 19:23:40 dom pulseaudio[21013]: module-alsa-card.c: Card '1' doesn't exist: No such file or directory Nov 25 19:23:40 dom pulseaudio[21013]: module.c: Failed to load module "module-alsa-card" (argument: "device_id=1 name="pci_1002_aa38_sound_card_1" card_name="alsa_card.pci_1002_aa38_sound_card_1" tsched=1 card_properties="module-hal-detect.discovered=1""): initialization failed. Nov 25 19:23:40 dom pulseaudio[21013]: main.c: Failed to acquire org.pulseaudio.Server: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.122" is not allowed to own the service "org.pulseaudio.Server" due to security policies in the configuration file -- Tomasz Chmielewski http://wpkg.org ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] only "dummy audio" available when many users want to use one audio card
'Twas brillig, and Tomasz Chmielewski at 22/11/09 01:22 did gyre and gimble: Colin Guthrie wrote: To achieve what you want you need to stop running a separate PA for each user and instead one system-wide version (see the --system) argument. You then need to add each user to the pulse-access group to ensure they are allowed to talk to the PA process. What is pulse-access group? I don't have any group containing "pulse" in /etc/groups. Also, grepping for "group" in /etc/pulseaudio/ doesn't find anything. This is a compile time setting. You can change the group if you like, but see the output from ./configure. A standard "make install" will not create the group - it's up to distros to create the group on package installation. Many distros don't really support system wide mode out of the box tho seeing as 99.9% of users don't really want/need to use it (the common case being two users switching between desktops (e.g. both logged in but not physically using the machine at the same time). For this reason you may have to create the pulse-access group yourself. There should be some info kicking around about system mode PA if you google around for it. This isn't really recommended as the users will be able to see each others streams which is a privacy issue, but it may not matter too much. Yep, not an issue here. -- 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/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] only "dummy audio" available when many users want to use one audio card
Colin Guthrie wrote: To achieve what you want you need to stop running a separate PA for each user and instead one system-wide version (see the --system) argument. You then need to add each user to the pulse-access group to ensure they are allowed to talk to the PA process. What is pulse-access group? I don't have any group containing "pulse" in /etc/groups. Also, grepping for "group" in /etc/pulseaudio/ doesn't find anything. This isn't really recommended as the users will be able to see each others streams which is a privacy issue, but it may not matter too much. Yep, not an issue here. -- Tomasz Chmielewski http://wpkg.org ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] only "dummy audio" available when many users want to use one audio card
'Twas brillig, and Tomasz Chmielewski at 21/11/09 21:18 did gyre and gimble: I have a multiseat workstation - two graphics cards, two keyboards/mice, two monitors, but one audio card. Before pulseaudio was mainstream, I was using ALSA, and both users could use audio. This isn't really something supported by the default and recommended PA setup. To achieve what you want you need to stop running a separate PA for each user and instead one system-wide version (see the --system) argument. You then need to add each user to the pulse-access group to ensure they are allowed to talk to the PA process. This isn't really recommended as the users will be able to see each others streams which is a privacy issue, but it may not matter too much. 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/] ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] only "dummy audio" available when many users want to use one audio card
Daniel Chen wrote: > On Sat, Nov 21, 2009 at 4:18 PM, Tomasz Chmielewski wrote: >> Now, as my distribution started to use pulseaudio (0.9.20 since a few >> weeks), only one user can use audio. >> >> The second user only has "dummy audio device" when starting pulseaudio. > > Is module-x11-xsmp loaded? You can check via pactl list. According to the output by both user, it is: User which has audio: Module #21 Name: module-x11-xsmp Argument: display=:1 session_manager=local/dom:@/tmp/.ICE-unix/6421,unix/dom:/tmp/.ICE-unix/6421 Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "X11 session management" module.version = "0.9.20-2mdv2010.1" Client #4 Driver: module-x11-xsmp.c Owner Module: 21 Properties: application.name = "XSMP Session on KDE as 10646f6d12587088270064210017" xsmp.vendor = "KDE" xsmp.client.id = "10646f6d12587088270064210017" User which doesn't have audio: Module #19 Name: module-x11-xsmp Argument: display=:0 session_manager=local/dom:@/tmp/.ICE-unix/6423,unix/dom:/tmp/.ICE-unix/6423 Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "X11 session management" module.version = "0.9.20-2mdv2010.1" Client #4 Driver: module-x11-xsmp.c Owner Module: 19 Properties: application.name = "XSMP Session on KDE as 10646f6d12587088290064230013" xsmp.vendor = "KDE" xsmp.client.id = "10646f6d12587088290064230013" -- Tomasz Chmielewski http://wpkg.org ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] only "dummy audio" available when many users want to use one audio card
On Sat, Nov 21, 2009 at 4:18 PM, Tomasz Chmielewski wrote: > Now, as my distribution started to use pulseaudio (0.9.20 since a few > weeks), only one user can use audio. > > The second user only has "dummy audio device" when starting pulseaudio. Is module-x11-xsmp loaded? You can check via pactl list. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss