https://bugs.kde.org/show_bug.cgi?id=456667
--- Comment #8 from Andy <s...@gmx.de> ---
> An untested theory is some other systemd unit is also adjusting sounds.
> We're opting in to more shared systems. pulseaudio
>
> "journalctl --user -b" would tell you more.
That might be it, even tho I can't really tell from the logs cause there is no
direct conflict or error.
I just see that pipewire gets called AFTER the generated systemd startup call:
(autostarter is my super creative name ;) of the auto start script btw)
> Jul 13 14:21:47 main plasma_session[1285]: org.kde.plasma.session: Starting
> autostart service "/home/andy/.config/autostart/autostarter.desktop"
> ("/home/andy/daten/daten/dokumente/eigene_programme/scripts/autostar>
> Jul 13 14:21:47 main systemd[695]: Started PipeWire Multimedia Service.
> Jul 13 14:21:47 main systemd[695]: Started PipeWire PulseAudio.
That's why I added "sleep 5s" to begin with but in the systemd startup context
it doesn't seem to work for reasons unknown to me.
This means that startup scripts are now restricted by the systemd environment
in general tho, which is a regression/downgrade imo.
I think we can close this bug then but there should be some documentation/error
handling happening when new autostart scripts are created.
Thanks for your help guys!
--
You are receiving this mail because:
You are watching all bug changes.
