I recently upgraded from Fedora 43 KDE to Fedora 44 KDE, and after getting to the desktop I obviously quickly noticed the missing login system sound of the Ocean Sound Theme for KDE.
As far as I know that’s the only missing sound, that I noticed at least, audio in general works fine, and even checking the options I can play that sound from there just fine (It’s also still enabled there), though it won’t play when it actually matters.
It’s a small thing but I’d certainly like to fix it if anyone knows why this might be happening and how to have it happen again at login. I don’t know what else to put here, sorry about that.
I do, it’s Ocean, which I think is the KDE Plasma System Sounds default I believe, at least I never changed that, and is where the login sound comes from. And yes notification sounds are enabled and unmuted, both in System Sounds and in the Sound tab of settings.
Yeah they do, I mentioned that in the original post, the “I can play that sound from there”, but double checked and yes all the sounds can be played when I click play or their icons to preview them.
Works as expected on 43, and if the sound file plays when you trigger it manually there’s no reason why it should not play when triggered programmatically by a login.
Someone else who’s on 44 will undoubtedly chime in to confirm or deny. I’ll be sitting on 43 for a while though, until I’m sure that 44 is clean enough for me to take the time to upgrade.
That’s smart, I also should have waited longer too, just in case. But yeah I haven’t noticed anyone else complain about it so I don’t know. Hopefully it can eventually be fixed and get it in working order as it doesn’t feel the same for me without that little chime.
I am experiencing the same issue (I had initially done a search and this thread didn’t come up). Might be worth one of us posting this in Common Issues.
One issue I found was problems when plugging in headphones (no sound) and is apparently related to a bug with Pipewire 1.6.4, and should be fixed in version 1.6.5. Maybe this startup sound issue is also related to a bug with Pipewire 1.6.4 (during the startup / initiation process)?
Good to know I’m not alone with the issue. I don’t know much, I guess does that mean we should wait until that update comes to fedora and then check? Assuming you haven’t already manually updated it and checked or something.
Facing the same issue on Fedora 44 KDE. No sound before or during first login. After logging in all sounds work fine (system sounds, audio players, everything is fine). If i log out and log back in again, i DO hear the login system sound this time. I tried to check the AUDIO settings as fast as possible after first login and it did appear as though the system was having trouble initializing my sound card (multiple devices listed, nothing i recognized). Then it resolved itself on its own (correct sound device listed) and audio started working fine. Not sure what else to do.
I also did notice by clicking the sound icon in the taskbar as fast as I could that the sound device there is one I don’t know, maybe a default one, before a second or two later my actual sound devices appear, with the list going back to the one I recognize, with the correct sound device selected. That might be part of it, though I never checked how it was at first login in Fedora 43 KDE so I can’t say for certain.
I noticed this too after the upgrade. Then I created another user just to check if it was a config issue. The first time I logged into this new user the sound played but from the second time onwards (I keep it as a guest account) the sound didn’t play anymore.
Now, for what it’s worth, I eventually welcomed this. Unless there’s some accessibility use, for normal use it’s better with no login sound. Back in the day (like in old Windows days, especially) the login sound would signal that the desktop was ready, otherwise if you wanted to open stuff the OS could even freeze… nowadays, if you open a browser as soon as the desktop is shown it will work right away. AND, if we’re working on a public space it doesn’t bother anyone with a useless notification.
I wonder, it might have worked the first time because it wasn’t a full restart, just a log out, like the other person above tested.
To comment on your second point, you can just turn off the login sound in the settings if you don’t want it to keep it that way. (Whenever it gets fixed that is)