Every time I start JuK in a new plasma session, it now starts muted, despite having previously adjusted the volume. Editing ~/.config/jukrc before launching it has no effect either. Further runs within the same plasma session work fine though. This behavior is a regression over version 20.08. If launched with valgrind (command "valgrind juk"), it keeps showing lots of error messages about "Conditional jump or move depends on uninitialised value(s)", plus some "Invalid read"s at the beginning. This is with all the KDE packages (plasma/frameworks/gears) from current debian sid, right now at versions 5.21.5, 5.85.0, and 21.08.
Hi I cannot reproduce this. Every time I start juk it is not muted. Maybe you have some special audio setup. I have manually muted it and restarted, to no avail, it always comes up unmuted. Best Norbert
The only special setup that I have is a USB sound card which I use as the default output device. If I remove this sound card (leaving only the default laptop speakers) the problem still persists however.
By the way, this and bug 993543 go away if I downgrade JuK to 20.12 from stable while the rest of the KDE gears apps stay at 21.08.
Still happening on Debian GNU/Linux 12 (bookworm) JuK Version 22.12.3 Everytime system is restarted JuK's volume to set to zero. No special audio setup. Using an MSI X570s Tomahawk mainboard. thanks
I'm getting this as well on debian 13 with Juk version 25.04.0. It's not the worst thing in the world but is annoying.