Pulseaudio fail to start at boot
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
When I boot PA does not start. Syslog show this:
$ grep 'pulseaudio' /var/log/syslog
Mar 26 08:08:30 MX systemd[1171]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:30 MX systemd[1331]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:31 MX systemd[1331]: pulseaudio.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Unit -d.socket not found.
Mar 26 08:08:31 MX systemd[1331]: pulseaudio.socket: Failed with result 'resources'.
Mar 26 08:08:41 MX systemd[1788]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:42 MX systemd[1788]: pulseaudio.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Unit -d.socket not found.
Mar 26 08:08:42 MX systemd[1788]: pulseaudio.socket: Failed with result 'resources'.
Mar 26 08:08:43 MX pulseaudio.desktop[2060]: Connection failure: Connection refused
Mar 26 08:08:43 MX pulseaudio.desktop[2060]: pa_context_connect() failed: Connection refused
Mar 26 08:08:43 MX gnome-session[1820]: gnome-session-binary[1820]: WARNING: App 'pulseaudio.desktop' exited with code 1
Mar 26 08:08:43 MX gnome-session-binary[1820]: WARNING: App 'pulseaudio.desktop' exited with code 1
When I log in, the service is not running and nothing is under Sound in Settings.
However. Starting PA manually after I have logged in works fine:
$ pulseaudio --start
And no additional errors are logged in syslog.
Looks like there might be some "Invalid argument" somewhere. How to find? Or is there an easy way to reset PA back to defaults?
As it is system default audio I am a bit hesitant to uninstall it (for then to reinstall) if something should be lost, or things become even worse. Have experienced that before.
pulseaudio systemd
asked Mar 26 at 7:37
user3342816user3342816
84
add a comment |
When I boot PA does not start. Syslog show this:
$ grep 'pulseaudio' /var/log/syslog
Mar 26 08:08:30 MX systemd[1171]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:30 MX systemd[1331]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:31 MX systemd[1331]: pulseaudio.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Unit -d.socket not found.
Mar 26 08:08:31 MX systemd[1331]: pulseaudio.socket: Failed with result 'resources'.
Mar 26 08:08:41 MX systemd[1788]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:42 MX systemd[1788]: pulseaudio.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Unit -d.socket not found.
Mar 26 08:08:42 MX systemd[1788]: pulseaudio.socket: Failed with result 'resources'.
Mar 26 08:08:43 MX pulseaudio.desktop[2060]: Connection failure: Connection refused
Mar 26 08:08:43 MX pulseaudio.desktop[2060]: pa_context_connect() failed: Connection refused
Mar 26 08:08:43 MX gnome-session[1820]: gnome-session-binary[1820]: WARNING: App 'pulseaudio.desktop' exited with code 1
Mar 26 08:08:43 MX gnome-session-binary[1820]: WARNING: App 'pulseaudio.desktop' exited with code 1
When I log in, the service is not running and nothing is under Sound in Settings.
However. Starting PA manually after I have logged in works fine:
$ pulseaudio --start
And no additional errors are logged in syslog.
Looks like there might be some "Invalid argument" somewhere. How to find? Or is there an easy way to reset PA back to defaults?
As it is system default audio I am a bit hesitant to uninstall it (for then to reinstall) if something should be lost, or things become even worse. Have experienced that before.
pulseaudio systemd
asked Mar 26 at 7:37
user3342816user3342816
84
add a comment |
When I boot PA does not start. Syslog show this:
$ grep 'pulseaudio' /var/log/syslog
Mar 26 08:08:30 MX systemd[1171]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:30 MX systemd[1331]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:31 MX systemd[1331]: pulseaudio.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Unit -d.socket not found.
Mar 26 08:08:31 MX systemd[1331]: pulseaudio.socket: Failed with result 'resources'.
Mar 26 08:08:41 MX systemd[1788]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:42 MX systemd[1788]: pulseaudio.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Unit -d.socket not found.
Mar 26 08:08:42 MX systemd[1788]: pulseaudio.socket: Failed with result 'resources'.
Mar 26 08:08:43 MX pulseaudio.desktop[2060]: Connection failure: Connection refused
Mar 26 08:08:43 MX pulseaudio.desktop[2060]: pa_context_connect() failed: Connection refused
Mar 26 08:08:43 MX gnome-session[1820]: gnome-session-binary[1820]: WARNING: App 'pulseaudio.desktop' exited with code 1
Mar 26 08:08:43 MX gnome-session-binary[1820]: WARNING: App 'pulseaudio.desktop' exited with code 1
When I log in, the service is not running and nothing is under Sound in Settings.
However. Starting PA manually after I have logged in works fine:
$ pulseaudio --start
And no additional errors are logged in syslog.
Looks like there might be some "Invalid argument" somewhere. How to find? Or is there an easy way to reset PA back to defaults?
As it is system default audio I am a bit hesitant to uninstall it (for then to reinstall) if something should be lost, or things become even worse. Have experienced that before.
pulseaudio systemd
asked Mar 26 at 7:37
user3342816user3342816
84
When I boot PA does not start. Syslog show this:
$ grep 'pulseaudio' /var/log/syslog
Mar 26 08:08:30 MX systemd[1171]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:30 MX systemd[1331]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:31 MX systemd[1331]: pulseaudio.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Unit -d.socket not found.
Mar 26 08:08:31 MX systemd[1331]: pulseaudio.socket: Failed with result 'resources'.
Mar 26 08:08:41 MX systemd[1788]: /usr/lib/systemd/user/pulseaudio.service:16: Failed to add dependency on pulseaudio, ignoring: Invalid argument
Mar 26 08:08:42 MX systemd[1788]: pulseaudio.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Unit -d.socket not found.
Mar 26 08:08:42 MX systemd[1788]: pulseaudio.socket: Failed with result 'resources'.
Mar 26 08:08:43 MX pulseaudio.desktop[2060]: Connection failure: Connection refused
Mar 26 08:08:43 MX pulseaudio.desktop[2060]: pa_context_connect() failed: Connection refused
Mar 26 08:08:43 MX gnome-session[1820]: gnome-session-binary[1820]: WARNING: App 'pulseaudio.desktop' exited with code 1
Mar 26 08:08:43 MX gnome-session-binary[1820]: WARNING: App 'pulseaudio.desktop' exited with code 1
When I log in, the service is not running and nothing is under Sound in Settings.
However. Starting PA manually after I have logged in works fine:
$ pulseaudio --start
And no additional errors are logged in syslog.
Looks like there might be some "Invalid argument" somewhere. How to find? Or is there an easy way to reset PA back to defaults?
As it is system default audio I am a bit hesitant to uninstall it (for then to reinstall) if something should be lost, or things become even worse. Have experienced that before.
pulseaudio systemd
pulseaudio systemd
asked Mar 26 at 7:37
user3342816user3342816
84
asked Mar 26 at 7:37
user3342816user3342816
84
edited Mar 26 at 7:54
user3342816
asked Mar 26 at 7:37
user3342816user3342816
84
asked Mar 26 at 7:37
user3342816user3342816
84
asked Mar 26 at 7:37
user3342816user3342816
84
84
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1128753%2fpulseaudio-fail-to-start-at-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1128753%2fpulseaudio-fail-to-start-at-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
