Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
On Thu, 2021-11-04 at 11:35 +, Joel wrote: > Tanu - > > Briefly, from the systemctl status reports, errors for the two > machines where system-wide pulseaudio, failed that appear to be the > most significant are as follows: > > ASUS-based desktop (linux-3): line 50. Nov 01 15:53:43 linux-3.home > pulseaudio[7348]: Denied access to client with invalid authentication > data. That's printed when a client tries to connect but is not allowed. Is your user in the pulse-access group? > > Dell laptop (linux-7): line 74. Job for pulseaudio.service failed > because the control process exited with error code. Something went wrong in the startup. If you try running (as root) "pulseaudio --system -vv", does that fail, and if it does, what is the error message (and the preceding log messages)? The command starts pulseaudio in the terminal with verbose logging and logs go to the terminal too. If the startup succeeds, use ctrl-c to stop pulseaudio. -- Tanu
Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
Tanu - Briefly, from the systemctl status reports, errors for the two machines where system-wide pulseaudio, failed that appear to be the most significant are as follows: ASUS-based desktop (linux-3): line 50. Nov 01 15:53:43 linux-3.home pulseaudio[7348]: Denied access to client with invalid authentication data. Dell laptop (linux-7): line 74. Job for pulseaudio.service failed because the control process exited with error code. Here is a link to the journalctl -xe report for the Dell laptop, which lists in part issues that appear to concern the network: https://susepaste.org/42129174 Joel 973 736 8306 From: Joel Sent: Wednesday, November 3, 2021 2:48 PM To: General PulseAudio Discussion Subject: Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met Tanu - Since getting pulseaudio running system-wide on one machine (an HP desktop; linux-6), I've attempted to replicate the configuration on two other machines, a Dell laptop (linux-7) and a desktop with an ASUS motherboard (linux-3). Both attempts and subsequent retries failed. The susepaste text file (https://susepaste.org/66650689) sets out the results of systemctl status showing a wide variety of errors, including errors reported on the machine where pulseaudio is working system-wide. The last listing, another ASUS-based desktop, was not modified and pulseaudio runs in root as (I believe) a session daemon with the command # pulseaudio --system -D, but I can't get pulseaudio running in the same fashion on either the Dell laptop (linux-7) or the other ASUS-based desktop (linux-3). In all cases, VLC still works and pulseaudio runs if I log into a user (non-root) session. I don't know how to proceed from here (or if I should, given that parts of the system, i.e., the various machines, work). Joel 973 736 8306
Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
Tanu - Since getting pulseaudio running system-wide on one machine (an HP desktop; linux-6), I've attempted to replicate the configuration on two other machines, a Dell laptop (linux-7) and a desktop with an ASUS motherboard (linux-3). Both attempts and subsequent retries failed. The susepaste text file (https://susepaste.org/66650689) sets out the results of systemctl status showing a wide variety of errors, including errors reported on the machine where pulseaudio is working system-wide. The last listing, another ASUS-based desktop, was not modified and pulseaudio runs in root as (I believe) a session daemon with the command # pulseaudio --system -D, but I can't get pulseaudio running in the same fashion on either the Dell laptop (linux-7) or the other ASUS-based desktop (linux-3). In all cases, VLC still works and pulseaudio runs if I log into a user (non-root) session. I don't know how to proceed from here (or if I should, given that parts of the system, i.e., the various machines, work). Joel 973 736 8306
Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
Hi. I've made a note on the blog post you cited, saying that `ConditionUser=!root` should not be added. The point of the system service *is* after all to be started by root. On 11/10/2021 21.41, Joel Miller wrote: OS: openSuSE Leap 15.3; KDE plasma desktop To enable a system instance of pulseaudio, I made the following file modifications suggested on the freedesktop.org (https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/SystemWide/) and rudd-o websites (https://rudd-o.com/linux-and-free-software/how-to-make-pulseaudio-run-once-at-boot-for-all-your-users): Per freedesktop.org: set autospawn = no in /etc/pulse/client.conf added "root" and "jm" to pulse-access Per rudd-o: in /etc/systemd/system/pulseaudio.service, modified text for [service] and [Install] (see rudd-o) used systemctl to enable, start, and check the status of pulseaudio The status request yields the following: linux-6:/etc/systemd/system # systemctl --system status pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/etc/systemd/system/pulseaudio.service; enabled; vendor preset: disabled) Active: inactive (dead) TriggeredBy: ● pulseaudio.socket Condition: start condition failed at Wed 2021-10-06 12:16:38 EDT; 4s ago └─ ConditionUser=!root was not met * * * Your suggestions and advice are welcome. Joel 973 736 8306 -- Rudd-O https://rudd-o.com/ OpenPGP_signature Description: OpenPGP digital signature
Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
Hi Colin! On Thu, 2021-10-14 at 13:18 +0100, Colin Guthrie wrote: > Tanu Kaskinen wrote on 13/10/2021 20:25: > > On Wed, 2021-10-13 at 14:51 +, Joel wrote: > > > Tanu - > > > > > > Thank you. I made the changes you suggested (removed > > > pulseaudio.socket from two locations where I found the file: > > > /etc/systemd/system/and /etc/systemd/system/sockets.targets.wants. > > > In the file pulseaudio.service, I commented out the lines > > > "Requires=pulseaudio.socket"; "ConditionUser=!root" and > > > "Also=pulseaudio.socket". Please note that there also two > > > occurrences of this file: /etc/systemd/system/and > > > /etc/systemd/system/multi-user.targets.wants. Perhaps the second > > > occurrences are system-generated. > > > > > > I then had sound from the web browser! VLC was still providing sound > > > as before (but I gather not using pulsesaudio). After logging out > > > then logging back in (not rebooting), there was no web browser sound > > > and a new error: Failed to load module "module-x11-publish". This > > > also occurred after rebooting and booting from a cold start. After > > > the reboot, a further error arose: Error opening PCM device front:0: > > > Device or resource busy. Also, the /var/run/.pulse cookie does > > > exist. The systemctl status reports in full are at > > > https://susepaste.org/99540079 . I'm unable to determine what I did > > > to cause these errors. > > > > The module-x11-publish error is probably caused by > > /etc/xdg/autostart/pulseaudio.desktop, which is loaded on login, > > causing /usr/bin/start-pulseaudio-x11 to be run. You could try removing > > the pulseaudio.desktop file (take a backup if you want). You shouldn't > > lose any essential functionality by doing that (and since PulseAudio > > was unable to connect to X11, whatever PulseAudio wanted to do didn't > > succeed anyway). > > > > If you see "Device or resource busy", something else is using the ALSA > > device. You can check with "lsof /dev/snd/*" what programs are using > > the ALSA devices. > > Forgive my ignorance since it's been *years* since I did any PA hacking > (just a drive by message on the list as I clicked on the folder in my > email client!) but do you really want your system-wide PA instance > running as root (that's what the systemd unit files suggests!) > > Wouldn't you want a User=pulse in there in the system unit (and make > sure the user pulse can access the audio devices via suitable ACLs/group > ownerships) PulseAudio does the user switch from root to pulse by itself, I don't know if PulseAudio can handle it if you start it directly as the pulse user. > It would be fine to have a system-wide pulseaudio.socket here that > started up the system-wide pulseaudio.service? Yes, it would be fine, if you configure it right. > Or have things changed so much that the system-wide pulseaudio instance > no longer runs as the pulse user? Nope, I don't think there has been much changes to the system-wide mode at all :) -- Tanu
Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
Tanu Kaskinen wrote on 13/10/2021 20:25: On Wed, 2021-10-13 at 14:51 +, Joel wrote: Tanu - Thank you. I made the changes you suggested (removed pulseaudio.socket from two locations where I found the file: /etc/systemd/system/and /etc/systemd/system/sockets.targets.wants. In the file pulseaudio.service, I commented out the lines "Requires=pulseaudio.socket"; "ConditionUser=!root" and "Also=pulseaudio.socket". Please note that there also two occurrences of this file: /etc/systemd/system/and /etc/systemd/system/multi-user.targets.wants. Perhaps the second occurrences are system-generated. I then had sound from the web browser! VLC was still providing sound as before (but I gather not using pulsesaudio). After logging out then logging back in (not rebooting), there was no web browser sound and a new error: Failed to load module "module-x11-publish". This also occurred after rebooting and booting from a cold start. After the reboot, a further error arose: Error opening PCM device front:0: Device or resource busy. Also, the /var/run/.pulse cookie does exist. The systemctl status reports in full are at https://susepaste.org/99540079 . I'm unable to determine what I did to cause these errors. The module-x11-publish error is probably caused by /etc/xdg/autostart/pulseaudio.desktop, which is loaded on login, causing /usr/bin/start-pulseaudio-x11 to be run. You could try removing the pulseaudio.desktop file (take a backup if you want). You shouldn't lose any essential functionality by doing that (and since PulseAudio was unable to connect to X11, whatever PulseAudio wanted to do didn't succeed anyway). If you see "Device or resource busy", something else is using the ALSA device. You can check with "lsof /dev/snd/*" what programs are using the ALSA devices. Forgive my ignorance since it's been *years* since I did any PA hacking (just a drive by message on the list as I clicked on the folder in my email client!) but do you really want your system-wide PA instance running as root (that's what the systemd unit files suggests!) Wouldn't you want a User=pulse in there in the system unit (and make sure the user pulse can access the audio devices via suitable ACLs/group ownerships) It would be fine to have a system-wide pulseaudio.socket here that started up the system-wide pulseaudio.service? Or have things changed so much that the system-wide pulseaudio instance no longer runs as the pulse user? Col
Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
On Wed, 2021-10-13 at 14:51 +, Joel wrote: > Tanu - > > Thank you. I made the changes you suggested (removed > pulseaudio.socket from two locations where I found the file: > /etc/systemd/system/and /etc/systemd/system/sockets.targets.wants. > In the file pulseaudio.service, I commented out the lines > "Requires=pulseaudio.socket"; "ConditionUser=!root" and > "Also=pulseaudio.socket". Please note that there also two > occurrences of this file: /etc/systemd/system/and > /etc/systemd/system/multi-user.targets.wants. Perhaps the second > occurrences are system-generated. > > I then had sound from the web browser! VLC was still providing sound > as before (but I gather not using pulsesaudio). After logging out > then logging back in (not rebooting), there was no web browser sound > and a new error: Failed to load module "module-x11-publish". This > also occurred after rebooting and booting from a cold start. After > the reboot, a further error arose: Error opening PCM device front:0: > Device or resource busy. Also, the /var/run/.pulse cookie does > exist. The systemctl status reports in full are at > https://susepaste.org/99540079 . I'm unable to determine what I did > to cause these errors. The module-x11-publish error is probably caused by /etc/xdg/autostart/pulseaudio.desktop, which is loaded on login, causing /usr/bin/start-pulseaudio-x11 to be run. You could try removing the pulseaudio.desktop file (take a backup if you want). You shouldn't lose any essential functionality by doing that (and since PulseAudio was unable to connect to X11, whatever PulseAudio wanted to do didn't succeed anyway). If you see "Device or resource busy", something else is using the ALSA device. You can check with "lsof /dev/snd/*" what programs are using the ALSA devices. -- Tanu
Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
Tanu - Thank you. I made the changes you suggested (removed pulseaudio.socket from two locations where I found the file: /etc/systemd/system/and /etc/systemd/system/sockets.targets.wants. In the file pulseaudio.service, I commented out the lines "Requires=pulseaudio.socket"; "ConditionUser=!root" and "Also=pulseaudio.socket". Please note that there also two occurrences of this file: /etc/systemd/system/and /etc/systemd/system/multi-user.targets.wants. Perhaps the second occurrences are system-generated. I then had sound from the web browser! VLC was still providing sound as before (but I gather not using pulsesaudio). After logging out then logging back in (not rebooting), there was no web browser sound and a new error: Failed to load module "module-x11-publish". This also occurred after rebooting and booting from a cold start. After the reboot, a further error arose: Error opening PCM device front:0: Device or resource busy. Also, the /var/run/.pulse cookie does exist. The systemctl status reports in full are at https://susepaste.org/99540079 . I'm unable to determine what I did to cause these errors. Joel 973 736 8306 From: pulseaudio-discuss on behalf of Tanu Kaskinen Sent: Tuesday, October 12, 2021 5:16 AM To: General PulseAudio Discussion Subject: Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met On Mon, 2021-10-11 at 22:19 +, Joel wrote: > Tanu - > > Thank you for your response. Please note - I have very little experience > with pulseaudio and alsa, except as a user. When it comes to the > configuration, I'm a complete novice and concluded that I made a mistake > somewhere by copying these files. > > Yes, I copied the file from user library and it does contain the following > lines (16 & 17): > >Requires=pulseaudio.socket >ConditionUser=!root > > Here is a link to the complete pulseaudio.service file: > https://susepaste.org/20298491 > > I gather that the comments preceding those lines hint at the problem I > created. > > For completeness, here is a link to the modified client.conf file: > https://susepaste.org/83477827 > > What do you suggest I do here? You don't need pulseaudio.socket if you're starting pulseaudio at boot, so remove that file and from pulseaudio.service remove the "Requires=pulseaudio.socket" and "Also=pulseaudio.socket" lines. Also remove the "ConditionUser=!root" line. -- Tanu
Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
On Mon, 2021-10-11 at 22:19 +, Joel wrote: > Tanu - > > Thank you for your response. Please note - I have very little experience > with pulseaudio and alsa, except as a user. When it comes to the > configuration, I'm a complete novice and concluded that I made a mistake > somewhere by copying these files. > > Yes, I copied the file from user library and it does contain the following > lines (16 & 17): > >Requires=pulseaudio.socket >ConditionUser=!root > > Here is a link to the complete pulseaudio.service file: > https://susepaste.org/20298491 > > I gather that the comments preceding those lines hint at the problem I > created. > > For completeness, here is a link to the modified client.conf file: > https://susepaste.org/83477827 > > What do you suggest I do here? You don't need pulseaudio.socket if you're starting pulseaudio at boot, so remove that file and from pulseaudio.service remove the "Requires=pulseaudio.socket" and "Also=pulseaudio.socket" lines. Also remove the "ConditionUser=!root" line. -- Tanu
Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
Tanu - Thank you for your response. Please note - I have very little experience with pulseaudio and alsa, except as a user. When it comes to the configuration, I'm a complete novice and concluded that I made a mistake somewhere by copying these files. Yes, I copied the file from user library and it does contain the following lines (16 & 17): Requires=pulseaudio.socket ConditionUser=!root Here is a link to the complete pulseaudio.service file: https://susepaste.org/20298491 I gather that the comments preceding those lines hint at the problem I created. For completeness, here is a link to the modified client.conf file: https://susepaste.org/83477827 What do you suggest I do here? Joel 973 736 8306 From: pulseaudio-discuss on behalf of Tanu Kaskinen Sent: Monday, October 11, 2021 6:03 PM To: General PulseAudio Discussion Subject: Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met On Mon, 2021-10-11 at 15:41 -0400, Joel Miller wrote: > OS: openSuSE Leap 15.3; KDE plasma desktop > > To enable a system instance of pulseaudio, I made the following file > modifications suggested on the freedesktop.org > (https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/SystemWide/) > and rudd-o websites > (https://rudd-o.com/linux-and-free-software/how-to-make-pulseaudio-run-once-at-boot-for-all-your-users): > > Per freedesktop.org: >set autospawn = no in /etc/pulse/client.conf >added "root" and "jm" to pulse-access > > Per rudd-o: >in /etc/systemd/system/pulseaudio.service, modified text for [service] > and [Install] (see rudd-o) >used systemctl to enable, start, and check the status of pulseaudio > > The status request yields the following: > > linux-6:/etc/systemd/system # systemctl --system status pulseaudio.service > ● pulseaudio.service - Sound Service > Loaded: loaded (/etc/systemd/system/pulseaudio.service; enabled; > vendor preset: disabled) > Active: inactive (dead) > TriggeredBy: ● pulseaudio.socket >Condition: start condition failed at Wed 2021-10-06 12:16:38 EDT; 4s ago > └─ ConditionUser=!root was not met > > * * * > > Your suggestions and advice are welcome. > > Joel > 973 736 8306 Does /etc/systemd/system/pulseaudio.service contain "ConditionUser=!root"? The systemctl status output looks like it does, but that doesn't make sense in a system service (and the rudd-o page doesn't contain that line, so I don't know why you would have that, unless you copied the user service to the system service, but in your list of modifications you didn't say that you did so). The systemctl output also indicates that pulseaudio.service was triggered by pulseaudio.socket, so check also that (the system version of) pulseaudio.socket doesn't contain "ConditionUser=!root". Again, rudd-o doesn't instruct you to set up a socket activation unit, nor did you mention doin that in your message, so I don't understand why pulseaudio.socket would be involved at all. -- Tanu
Re: [pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
On Mon, 2021-10-11 at 15:41 -0400, Joel Miller wrote: > OS: openSuSE Leap 15.3; KDE plasma desktop > > To enable a system instance of pulseaudio, I made the following file > modifications suggested on the freedesktop.org > (https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/SystemWide/) > > and rudd-o websites > (https://rudd-o.com/linux-and-free-software/how-to-make-pulseaudio-run-once-at-boot-for-all-your-users): > > Per freedesktop.org: > set autospawn = no in /etc/pulse/client.conf > added "root" and "jm" to pulse-access > > Per rudd-o: > in /etc/systemd/system/pulseaudio.service, modified text for [service] > and [Install] (see rudd-o) > used systemctl to enable, start, and check the status of pulseaudio > > The status request yields the following: > > linux-6:/etc/systemd/system # systemctl --system status pulseaudio.service > ● pulseaudio.service - Sound Service > Loaded: loaded (/etc/systemd/system/pulseaudio.service; enabled; > vendor preset: disabled) > Active: inactive (dead) > TriggeredBy: ● pulseaudio.socket >Condition: start condition failed at Wed 2021-10-06 12:16:38 EDT; 4s ago > └─ ConditionUser=!root was not met > > * * * > > Your suggestions and advice are welcome. > > Joel > 973 736 8306 Does /etc/systemd/system/pulseaudio.service contain "ConditionUser=!root"? The systemctl status output looks like it does, but that doesn't make sense in a system service (and the rudd-o page doesn't contain that line, so I don't know why you would have that, unless you copied the user service to the system service, but in your list of modifications you didn't say that you did so). The systemctl output also indicates that pulseaudio.service was triggered by pulseaudio.socket, so check also that (the system version of) pulseaudio.socket doesn't contain "ConditionUser=!root". Again, rudd-o doesn't instruct you to set up a socket activation unit, nor did you mention doin that in your message, so I don't understand why pulseaudio.socket would be involved at all. -- Tanu
[pulseaudio-discuss] Start condition failed - ConditionUser=!root not met
OS: openSuSE Leap 15.3; KDE plasma desktop To enable a system instance of pulseaudio, I made the following file modifications suggested on the freedesktop.org (https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/SystemWide/) and rudd-o websites (https://rudd-o.com/linux-and-free-software/how-to-make-pulseaudio-run-once-at-boot-for-all-your-users): Per freedesktop.org: set autospawn = no in /etc/pulse/client.conf added "root" and "jm" to pulse-access Per rudd-o: in /etc/systemd/system/pulseaudio.service, modified text for [service] and [Install] (see rudd-o) used systemctl to enable, start, and check the status of pulseaudio The status request yields the following: linux-6:/etc/systemd/system # systemctl --system status pulseaudio.service ● pulseaudio.service - Sound Service Loaded: loaded (/etc/systemd/system/pulseaudio.service; enabled; vendor preset: disabled) Active: inactive (dead) TriggeredBy: ● pulseaudio.socket Condition: start condition failed at Wed 2021-10-06 12:16:38 EDT; 4s ago └─ ConditionUser=!root was not met * * * Your suggestions and advice are welcome. Joel 973 736 8306
