Is this command, which is in Endeavouros Titan, available in Bugzilla? systemctl --user enable --now pipewire.service
Thanks
If so, why hasn’t it been fixed in an update? I just reinstalled Titan Neo and the same thing is happening again.
What thing is happening? I ask because when I ran the exact same command a few weeks ago, it worked perfectly.
It turns out I reinstalled EndeavourOS Titan Neo (new SSD) and I’m finding that it has the same problem as before: it hasn’t been updated/repaired, and I still have to use the same command/instruction. What’s going on? Is Endeavour not updating to fix this error? Thanks.
What problem? You haven’t explained what the issue is that you refer to. There is no need to run this command on an install. If you have a specific issue what you need to to is create a new post explaining your issue and posting the complete hardware output. Also include the install logs. As far as the pipewire service mine doesn’t show that it is running and i have no issues.
[ricklinux@rick-ms7c91 ~]$ systemctl --user status pipewire
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
Active: active (running) since Mon 2026-05-11 07:50:05 EDT; 2min 57s ago
Invocation: ab82696e0a574134b7055201a95a28f1
TriggeredBy: ● pipewire.socket
Main PID: 5218 (pipewire)
Tasks: 3 (limit: 38369)
Memory: 8M (peak: 9.4M)
CPU: 57ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─5218 /usr/bin/pipewire
May 11 07:50:05 rick-ms7c91 systemd[5206]: Started PipeWire Multimedia Service.
[ricklinux@rick-ms7c91 ~]$ systemctl --user status pipewire-pulse
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: enabled)
Active: active (running) since Mon 2026-05-11 07:50:06 EDT; 3min 12s ago
Invocation: 36ce9367415b47d1bbf82af945bbaaf2
TriggeredBy: ● pipewire-pulse.socket
Main PID: 5549 (pipewire-pulse)
Tasks: 3 (limit: 38369)
Memory: 6.5M (peak: 7.4M)
CPU: 51ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
└─5549 /usr/bin/pipewire-pulse
May 11 07:50:06 rick-ms7c91 systemd[5206]: Started PipeWire PulseAudio.
[ricklinux@rick-ms7c91 ~]$ systemctl --user list-units | grep -E "pipewire|pulse|wireplumber"
pipewire-pulse.service loaded active running PipeWire PulseAudio
pipewire.service loaded active running PipeWire Multimedia Service
wireplumber.service loaded active running Multimedia Service Session Manager
pipewire-pulse.socket loaded active running PipeWire PulseAudio
pipewire.socket loaded active running PipeWire Multimedia System Sockets
Ah, well, on my PC, I say this because I already posted a similar message before asking why the Endeavour startup sound wasn’t working, and I was told to type `systemctl --user enable --now pipewire.service` and it worked (not all PCs are the same). So, just because you don’t see a problem doesn’t mean there isn’t one. I’m just complaining or noticing that the problem I described hasn’t been fixed, NOTHING MORE!!!
RRead this >>>> https://forum.endeavouros.com/t/sound-does-not-play-at-the-start-of-kde-plasma/79047/4
The sound DOES WORK. WHAT DOESN’T WORK (which I’ve now fixed with the command) is that WHEN I STARTED PLASMA, THE STARTUP SOUND DIDN’T PLAY. (Call me picky, but I like things to work.)
And that’s it.
If you are using a custom wav for your start up file, you may have a problem when it is not properly encoded. You can test this with aplay path/to/your/wav.
If it gives you the message aplay: test_wavefile:1086: can't play WAVE-file format 0x0055 which is not PCM or FLOAT encoded, you need to reencode the wav. You can do this with ffmpeg by running ffmpeg -i path/to/existing.wav -acodec pcm_s16le path/to/new.wav
Finally you explained what the issue is. Now wasn’t that much easier? Picky yes! 
What you don’t seem to understand is that there is no such thing as an Endeavour startup sound, it is something of Plasma , if this is not working you should blaim KDE and complain there. And there is no need to shout 
I don’t want to repeat myself: you don’t understand. If it’s not necessary (or if that command… why do you have to enter that command to activate the KDE Plasma startup sound?) And that way it’s over faster. I don’t want to have to enter that command on every computer I install EndeavourOS on, plain and simple. Oh, and I’m not shouting, I’m just raising my voice. Cheers.
I would guess that over 90% of people don’t need that command run because they are not using a startup sound. Why would it be done by default?
That wasn’t it, but thanks.
Could it be related to this KDE Plasma “bug”?
So, since he doesn’t use it, he doesn’t fix it. Great! 
I also wonder if it’s related to either SDDM or Plasma Login Manager?
Which are you running @Miguel1964 ?
yay -Q | grep -E 'sddm|plasma-login'
Remember Arch and Endeavour are supposed to be build and configure it yourself distros. Endeavour just gives you a better starting point than Arch.
We are using plasma log in manager now.
[ricklinux@rick-ms7c91 ~]$ yay -Q | grep -E 'sddm|plasma-login'
plasma-login-manager 6.6.4-2
Yeah I wonder if previously under SDDM, it may not have been an issue.
Exactly, thats is my problem, thank you, Thanks, you and My nameisrichard understood me perfectly. I’m marking it as resolved. Now all that’s left is for the Bugzilla team to fix it. Apologies for… My “outbursts.” Best regards.
I don’t know. I have never ever had a log in sound on KDE.