Re: [pulseaudio-discuss] multiseat and PulseAudio?
On 16.05.2011 11:37, Colin Guthrie wrote: Well in this evironment, I'd say that if you only have one card to be shared between the seats, then system wide mode is likely the right option. It's not nice generally because: 2. One user can spy on the other user monitor their VOIP streams etc. Since all users hear the same audio from loudspeakers, it's not a concern :) And we don't test it particularly heavily, but all in all it should work fine (assuming you write your own init script and/or your distro does that for you). Unfortunately, it does not work fine, and was a reason why I'm investigating running PulseAudio per-user. When I run it in system mode, it crashes (or exits? not sure). It's not something what happens very often - once every 3 days perhaps. But annoying (no music anymore, normal user can't start PA in system mode etc.). Since the documentation said I'm not likely to get any help when asking for system mode issues, I though I'm really doing something wrong and I should use it per-user. If I start PulseAudio in the user mode, only one user gets a sound card; the second one gets "Dummy Output". Yeah, that's either because the second user does not have permission to access the device (due to ConsoleKit ACLs only the "active" (ck-list-sessions) user should get the ACL, but this could actually cover both users in your setup) or due to the fact that the card can only be opened once. Normally what you'd due is define some kind of udev magic that defines "seats" and thus contextually assigns certain USB ports and/or h/w to a given seat. Then when a user (any user - it's not tied to the seat) logs in, console-kit and udev both apply the right ACLs and PA can start and only show the relevant sound cards to the relevant seats. This is how it should work in an ideal world - everyone getting their own stuff. But in a situation where you accept all the problems listed above (things like security likely don't apply when people know each other :)) then system wide is fine. Hope that helps :) Well, the theory is nice :) but from user's perspective, sound with multiseat became unreliable when distributions migrated to PulseAudio (not that the life of a multiseat user was ever easy, but still, it's yet one thing which discourages multiseat). Perhaps I'll try to see why PA crashes/exits when used by multiple users in the system mode, report it to the mailing list, and hope won't get too many "system mode is unsupported, go away" replies ;) -- 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] multiseat and PulseAudio?
On 16.05.2011 10:43, duportail wrote: Currently i use a script to set the users' default sink according the display he is on, because you do not know which user is logged in on which display. I only have one sound card for all users, so I guess your scripts wouldn't help much? -- 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] multiseat and PulseAudio?
On 16.05.2011 08:49, David Henningsson wrote: On 2011-05-14 17:46, Tomasz Chmielewski wrote: Traditionally, UNIX systems were supporting multiseat desktop sessions (i.e. multiple keyboards, video cards, monitors attached to one PC). According to: http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode What is wrong with system mode? Or with other words: if you run it that way on your desktop, then you are doing it the wrong way. What is the correct way to use PulseAudio with multiseat systems? Assuming there is also one sound card per seat, you should run one PulseAudio per seat, and as the user currently logged in to that seat. Exactly how to do that, i e set up access to the right sound card for the logged in user (with ConsoleKit etc) is beyond my knowledge though. I only have one sound card in the PC. It works fine when I start PulseAudio in the system mode, but according to documentation, this is unsupported, strongly discouraged and should only be used in some embedded setups. So I'd like to do it "the right way" - unfortunately, PulseAudio documentation does not explain how to setup PulseAudio with multiseat. If I start PulseAudio in the user mode, only one user gets a sound card; the second one gets "Dummy Output". -- Tomasz Chmielewski http://wpkg.org ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] multiseat and PulseAudio?
Traditionally, UNIX systems were supporting multiseat desktop sessions (i.e. multiple keyboards, video cards, monitors attached to one PC). According to: http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode What is wrong with system mode? Or with other words: if you run it that way on your desktop, then you are doing it the wrong way. What is the correct way to use PulseAudio with multiseat systems? -- 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
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
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
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
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 10646f6d000012587088290064230013" 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
[pulseaudio-discuss] only "dummy audio" available when many users want to use one audio card
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. 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. How can I troubleshoot what is preventing the second user from using audio? -- Tomasz Chmielewski http://wpkg.org ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
