Pulseaudio using WSL E: [(null)] pulsecore/pid.c: Daemon already running
Multi tool use
I'm fairly new on Linux, I've been playing with WSL on Windows 10 using Ubuntu, and I've managed to learn how to open GUI programs and I could take it one step further by using this tutorial which allowed me to run GUI apps even with sound, it was awesome until I ended my session and stopped the pulseaudio server, then next time I tried to run it I was met with these two error messages:
E: [(null)] pulsecore/pid.c: Daemon already running.
E: [(null)] daemon/main.c: pa_pid_file_create() failed.
I've looked everywhere without being able to find out a solution, I tried running the commands pulseaudio.exe -k --kill to kill daemon but for what I could research, these commands won't work on Windows 10. And using taskkill to end pulseaudio.exe won't end daemon properly, anyone got any idea? I'd love some help! thank you!
sound windows pulseaudio windows-10 windows-subsystem-for-linux
asked Sep 23 at 8:12
Danilo Reyes
112
add a comment |
I'm fairly new on Linux, I've been playing with WSL on Windows 10 using Ubuntu, and I've managed to learn how to open GUI programs and I could take it one step further by using this tutorial which allowed me to run GUI apps even with sound, it was awesome until I ended my session and stopped the pulseaudio server, then next time I tried to run it I was met with these two error messages:
E: [(null)] pulsecore/pid.c: Daemon already running.
E: [(null)] daemon/main.c: pa_pid_file_create() failed.
I've looked everywhere without being able to find out a solution, I tried running the commands pulseaudio.exe -k --kill to kill daemon but for what I could research, these commands won't work on Windows 10. And using taskkill to end pulseaudio.exe won't end daemon properly, anyone got any idea? I'd love some help! thank you!
sound windows pulseaudio windows-10 windows-subsystem-for-linux
asked Sep 23 at 8:12
Danilo Reyes
112
add a comment |
I'm fairly new on Linux, I've been playing with WSL on Windows 10 using Ubuntu, and I've managed to learn how to open GUI programs and I could take it one step further by using this tutorial which allowed me to run GUI apps even with sound, it was awesome until I ended my session and stopped the pulseaudio server, then next time I tried to run it I was met with these two error messages:
E: [(null)] pulsecore/pid.c: Daemon already running.
E: [(null)] daemon/main.c: pa_pid_file_create() failed.
I've looked everywhere without being able to find out a solution, I tried running the commands pulseaudio.exe -k --kill to kill daemon but for what I could research, these commands won't work on Windows 10. And using taskkill to end pulseaudio.exe won't end daemon properly, anyone got any idea? I'd love some help! thank you!
sound windows pulseaudio windows-10 windows-subsystem-for-linux
asked Sep 23 at 8:12
Danilo Reyes
112
I'm fairly new on Linux, I've been playing with WSL on Windows 10 using Ubuntu, and I've managed to learn how to open GUI programs and I could take it one step further by using this tutorial which allowed me to run GUI apps even with sound, it was awesome until I ended my session and stopped the pulseaudio server, then next time I tried to run it I was met with these two error messages:
E: [(null)] pulsecore/pid.c: Daemon already running.
E: [(null)] daemon/main.c: pa_pid_file_create() failed.
I've looked everywhere without being able to find out a solution, I tried running the commands pulseaudio.exe -k --kill to kill daemon but for what I could research, these commands won't work on Windows 10. And using taskkill to end pulseaudio.exe won't end daemon properly, anyone got any idea? I'd love some help! thank you!
sound windows pulseaudio windows-10 windows-subsystem-for-linux
sound windows pulseaudio windows-10 windows-subsystem-for-linux
asked Sep 23 at 8:12
Danilo Reyes
112
asked Sep 23 at 8:12
Danilo Reyes
112
asked Sep 23 at 8:12
Danilo Reyes
112
asked Sep 23 at 8:12
Danilo Reyes
112
asked Sep 23 at 8:12
Danilo Reyes
112
112
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Short answer: delete the file
%USERPROFILE%.pulse%USERDOMAIN%-runtimepid
(replace USERDOMAIN with USERDOMAIN_ROAMINGPROFILE if you are using a roaming profile)
Explanation:
I recently ran into this and using Sysinternals PROCMON I was able to track down the cause:
Usually GNU applications designed to run as a service adhere to a practice to setup a runtime PID file in order to avoid duplicate launch. On crash, the start/stop script of the service handles removing the stale PID file in most cases.
On this case however there is no script handling the start and stop of pulseaudio.exe so on crash the PID file remains then at next startup the app refuses to start, seeing the PID file and wrongly concludes 'oops we are already running'
(WSL IS NOT LINUX, by the way; pulseaudio.exe is a GNU application compiled to run in windows independent of WSL)
answered Dec 11 at 11:43
Costin Gușă
1235
add a comment |
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%2f1077678%2fpulseaudio-using-wsl-e-null-pulsecore-pid-c-daemon-already-running%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Short answer: delete the file
%USERPROFILE%.pulse%USERDOMAIN%-runtimepid
(replace USERDOMAIN with USERDOMAIN_ROAMINGPROFILE if you are using a roaming profile)
Explanation:
I recently ran into this and using Sysinternals PROCMON I was able to track down the cause:
Usually GNU applications designed to run as a service adhere to a practice to setup a runtime PID file in order to avoid duplicate launch. On crash, the start/stop script of the service handles removing the stale PID file in most cases.
On this case however there is no script handling the start and stop of pulseaudio.exe so on crash the PID file remains then at next startup the app refuses to start, seeing the PID file and wrongly concludes 'oops we are already running'
(WSL IS NOT LINUX, by the way; pulseaudio.exe is a GNU application compiled to run in windows independent of WSL)
answered Dec 11 at 11:43
Costin Gușă
1235
add a comment |
Short answer: delete the file
%USERPROFILE%.pulse%USERDOMAIN%-runtimepid
(replace USERDOMAIN with USERDOMAIN_ROAMINGPROFILE if you are using a roaming profile)
Explanation:
I recently ran into this and using Sysinternals PROCMON I was able to track down the cause:
Usually GNU applications designed to run as a service adhere to a practice to setup a runtime PID file in order to avoid duplicate launch. On crash, the start/stop script of the service handles removing the stale PID file in most cases.
On this case however there is no script handling the start and stop of pulseaudio.exe so on crash the PID file remains then at next startup the app refuses to start, seeing the PID file and wrongly concludes 'oops we are already running'
(WSL IS NOT LINUX, by the way; pulseaudio.exe is a GNU application compiled to run in windows independent of WSL)
answered Dec 11 at 11:43
Costin Gușă
1235
add a comment |
Short answer: delete the file
%USERPROFILE%.pulse%USERDOMAIN%-runtimepid
(replace USERDOMAIN with USERDOMAIN_ROAMINGPROFILE if you are using a roaming profile)
Explanation:
I recently ran into this and using Sysinternals PROCMON I was able to track down the cause:
Usually GNU applications designed to run as a service adhere to a practice to setup a runtime PID file in order to avoid duplicate launch. On crash, the start/stop script of the service handles removing the stale PID file in most cases.
On this case however there is no script handling the start and stop of pulseaudio.exe so on crash the PID file remains then at next startup the app refuses to start, seeing the PID file and wrongly concludes 'oops we are already running'
(WSL IS NOT LINUX, by the way; pulseaudio.exe is a GNU application compiled to run in windows independent of WSL)
answered Dec 11 at 11:43
Costin Gușă
1235
Short answer: delete the file
%USERPROFILE%.pulse%USERDOMAIN%-runtimepid
(replace USERDOMAIN with USERDOMAIN_ROAMINGPROFILE if you are using a roaming profile)
Explanation:
I recently ran into this and using Sysinternals PROCMON I was able to track down the cause:
Usually GNU applications designed to run as a service adhere to a practice to setup a runtime PID file in order to avoid duplicate launch. On crash, the start/stop script of the service handles removing the stale PID file in most cases.
On this case however there is no script handling the start and stop of pulseaudio.exe so on crash the PID file remains then at next startup the app refuses to start, seeing the PID file and wrongly concludes 'oops we are already running'
(WSL IS NOT LINUX, by the way; pulseaudio.exe is a GNU application compiled to run in windows independent of WSL)
answered Dec 11 at 11:43
Costin Gușă
1235
edited Dec 11 at 11:52
answered Dec 11 at 11:43
Costin Gușă
1235
answered Dec 11 at 11:43
Costin Gușă
1235
answered Dec 11 at 11:43
Costin Gușă
1235
1235
add a comment |
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1077678%2fpulseaudio-using-wsl-e-null-pulsecore-pid-c-daemon-already-running%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
fRA61ewLh1RdMiD,4 aGx2R gY,D,ml2gYsBnvCT,GbXewNPml4,9yh ZOjuozCtvFVNrD5k7qHLBxndcA 2nXZBE
