SUMMARY Since latest updates, the startup sound is cut off before it completes playing. STEPS TO REPRODUCE 1. Log in with startup sound activated OBSERVED RESULT My startup sound is approx 2.75s but stops playing at approx 1s. EXPECTED RESULT To play the full audio file SOFTWARE/OS VERSIONS KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION
It's completely gone here. After update to Plasma-5.19 and during the first logon I also heard a cut-off-sound as reported, but until then the logon procedure ist muted. ...and I still can't find the settings in the configuration panel where to check or change the sound. OS is Arch.
(In reply to Martin Schnitkemper from comment #1) > ...and I still can't find the settings in the configuration panel where to > check or change the sound. Ok... found it now... it's good hidden in the (new?) configuration panel, set to "Oxygen-Sys-Log-In-Short.ogg", and it is playable. Even on logon it's quiet.
*** Bug 423110 has been marked as a duplicate of this bug. ***
I can confirm this bug, happening for me on Manjaro.
*** Bug 422891 has been marked as a duplicate of this bug. ***
No login sound at all on my two openSUSE Tumbleweed installs. It looks as if the sound is muted at login, as the panel displays one can see for a very brief moment the speaker icon change from muted state to un-muted.
*** Bug 423518 has been marked as a duplicate of this bug. ***
*** Bug 423498 has been marked as a duplicate of this bug. ***
Dupes piling up, marking as VHI as this is a regression.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/124
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/127
Applied both patches and created packages for Arch, but no changes; I still get no startup sound. Sorry to tell you that this issue is not solved for me.
Hi I'm also on Arch 5.7.7, using plasma 5.19.2-1, and the startup sound still isn't working.
I have just updated KDE Neon to Plasma 5.19.3 and still no plasma start-up sound. KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2
No startup sound is not the same as cut-off. That implies it's "just" a configuration or phonon issue. Can I have output of "plasma_session" in a terminal. Note this will probably break your current session in weird ways, so only do it before you were going to do it anyway
(In reply to David Edmundson from comment #15) > No startup sound is not the same as cut-off. > That implies it's "just" a configuration or phonon issue. > > > Can I have output of "plasma_session" in a terminal. > > Note this will probably break your current session in weird ways, so only do > it before you were going to do it anyway plasma_session command doesn't look very useful: kdeinit5: Shutting down running client. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 11241, result = 0 kdeinit5: opened connection to :0 kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/kyrawertho/.gtkrc:/home/kyrawertho/.config/gtkrc' from launcher. kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/kyrawertho/.gtkrc-2.0:/home/kyrawertho/.config/gtkrc-2.0' from launcher. kdeinit5: Got SETENV 'XCURSOR_THEME=buuf-cursor-original-24' from launcher. kdeinit5: Got SETENV 'XCURSOR_SIZE=24' from launcher. 2020/07/07 17:42:34 socat[11258] E connect(5, AF=1 "/run/user/1000/kwallet5.socket", 32): Connection refused Mislukt: Module-initialisatie mislukt [1] 11226 segmentation fault plasma_session /~/.local/lib/python3.6/site-packages/autokey/qtui/common.py:38: UserWarning: Compiled Qt resources file not found. If autokey is launched directly from the source directory, this is expected and harmless. If not, this indicates a failure in the resource compilation. warnings.warn(warn_msg)
Have ran the command 'power_session' and it throws me out of my plasma session to the sddm login page. Of interest (perhaps) was that I was not getting any start-up sound before but when logging in now get a cut-off sound as per post 1.
Login sound still MIA in KDE Plasma Version: 05.19.3.
(In reply to David Edmundson from comment #15) > No startup sound is not the same as cut-off. > That implies it's "just" a configuration or phonon issue. > > > Can I have output of "plasma_session" in a terminal. > > Note this will probably break your current session in weird ways, so only do > it before you were going to do it anyway The missing login sound started with 5.19.0 as the other bug reports have indicated. I would submit my own report, but similar reports like 422891 have been marked as duplicates of this one. Here's my plasma_session output: kdeinit5: Shutting down running client. kdeinit5: preparing to launch '/usr/lib/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 1797, result = 0 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeinit5: opened connection to :0 Icon theme "gnome" not found. kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/matt/.gtkrc:/home/matt/.config/gtkrc' from launcher. kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/matt/.gtkrc-2.0:/home/matt/.config/gtkrc-2.0' from launcher. kdeinit5: Got SETENV 'XCURSOR_THEME=breeze_cursors' from launcher. kdeinit5: Got SETENV 'XCURSOR_SIZE=24' from launcher. org.kde.plasma.session: process job "kcminit_startup" finished with exit code 0 org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/polkit-kde-authentication-agent-1.desktop" ("/usr/lib/polkit-kde-authentication-agent-1") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/xembedsniproxy.desktop" ("/usr/bin/xembedsniproxy") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/baloo_file.desktop" ("/usr/bin/baloo_file") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/pam_kwallet_init.desktop" ("/usr/lib/pam_kwallet_init") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/kaccess.desktop" ("/usr/bin/kaccess") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/org.kde.plasmashell.desktop" ("/usr/bin/plasmashell") 2020/07/07 09:23:49 socat[1820] E connect(5, AF=1 "/run/user/1000/kwallet5.socket", 32): Connection refused Failed to register via dbus. Another instance is running Xlib XKB extension major= 1 minor= 0 kde.xembedsniproxy: failed to claim ownership of Systray Manager Icon theme "gnome" not found. org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop" ("/usr/lib/kdeconnectd") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/pulseaudio.desktop" ("/usr/bin/start-pulseaudio-x11") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/restore_kmix_volumes.desktop" ("/usr/bin/kmixctrl", "--restore") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/gmenudbusmenuproxy.desktop" ("/usr/bin/gmenudbusmenuproxy") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/org.kde.discover.notifier.desktop" ("/usr/lib/DiscoverNotifier") org.kde.plasma.session: Starting autostart service "/home/matt/.config/autostart/org.kde.latte-dock.desktop" ("/usr/bin/latte-dock") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/powerdevil.desktop" ("/usr/lib/org_kde_powerdevil") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/xapp-sn-watcher.desktop" ("/usr/lib/xapps/sn-watcher/xapp-sn-watcher") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/org.kde.korgac.desktop" ("/usr/bin/korgac") org.kde.plasma.session: Starting autostart service "/home/matt/.config/autostart/com.github.hluk.copyq.desktop" ("/usr/bin/copyq") org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/kmix_autostart.desktop" ("/usr/bin/kmix", "--keepvisibility") KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma_session path = /usr/bin pid = 1788 KCrash: Arguments: /usr/bin/plasma_session KCrash: Attempting to start /usr/lib/drkonqi org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic couldn't load "/usr/lib/qt/plugins/discover-notifier/DiscoverPackageKitNotifier.so" because "Cannot load library /usr/lib/qt/plugins/discover-notifier/DiscoverPackageKitNotifier.so: (libpackagekitqt5.so.1: cannot open shared object file: No such file or directory)" couldn't load "/usr/lib/qt/plugins/discover-notifier/FlatpakNotifier.so" because "Cannot load library /usr/lib/qt/plugins/discover-notifier/FlatpakNotifier.so: (libflatpak.so.0: cannot open shared object file: No such file or directory)" couldn't find any notifier backend ("/usr/lib/qt/plugins", "/usr/lib") Warning: CopyQ server is already running. Icon theme "gnome" not found. Icon theme "gnome" not found. "An instance is already running!, use --replace to restart Latte" [1]+ Stopped plasma_session
>[1] 11226 segmentation fault plasma_session That's very interesting. plasma_session is crashing. Can you run "gdb plasma_session" then when we hit the same point "type" bt to include a backtrace.
(In reply to David Edmundson from comment #20) > >[1] 11226 segmentation fault plasma_session > > That's very interesting. plasma_session is crashing. > > Can you run "gdb plasma_session" then when we hit the same point "type" bt > to include a backtrace. Not sure if I did this right. I haven't used the debugger before. Here's the output I get with backtrace: (gdb) cont Continuing. org.kde.plasma.session: Starting autostart service "/etc/xdg/autostart/restore_kmix_volumes.desktop" ("/usr/bin/kmixctrl", "--restore") [Detaching after fork from child process 7390] Thread 1 "plasma_session" hit Breakpoint 2, 0x00007ffff76c4310 in QMessageLogger::info() const () from /usr/lib/libQt5Core.so.5 (gdb) org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic org.kde.kmix: no mix devices and not dynamic bt #0 0x00007ffff76c4310 in QMessageLogger::info() const () from /usr/lib/libQt5Core.so.5 #1 0x00005555555630cf in ?? () #2 0x00007ffff78dd1d2 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #3 0x00007ffff78b0790 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #4 0x00007ffff78b32a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #5 0x00007ffff7909cf4 in ?? () from /usr/lib/libQt5Core.so.5 #6 0x00007ffff567a43c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #7 0x00007ffff56c81d9 in ?? () from /usr/lib/libglib-2.0.so.0 #8 0x00007ffff5679221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #9 0x00007ffff7909331 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #10 0x00007ffff78af13c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #11 0x00007ffff78b75c4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #12 0x000055555555d071 in ?? () #13 0x00007ffff7280002 in __libc_start_main () from /usr/lib/libc.so.6 #14 0x000055555555d0ce in _start ()
(In reply to David Edmundson from comment #20) > >[1] 11226 segmentation fault plasma_session > > That's very interesting. plasma_session is crashing. > > Can you run "gdb plasma_session" then when we hit the same point "type" bt > to include a backtrace. (gdb) run Starting program: /usr/bin/plasma_session [New Thread 0x7fffe96fb700 (LWP 3917)] Mislukt: Module-initialisatie mislukt [New Thread 0x7fffdb3e8700 (LWP 3964)] Thread 3 "NotificationThr" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe96fb700 (LWP 3917)] __GI___pthread_rwlock_rdlock (rwlock=0x28) at pthread_rwlock_rdlock.c:27 27 pthread_rwlock_rdlock.c: Bestand of map bestaat niet. (gdb) bt #0 __GI___pthread_rwlock_rdlock (rwlock=0x28) at pthread_rwlock_rdlock.c:27 #1 0x00007fffe8837a3e in vlc_vaLog () from /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #2 0x00007fffe8837b4b in vlc_Log () from /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #3 0x00007fffdb3eac4b in vlc_pa_connect () from /usr/lib/x86_64-linux-gnu/vlc/libvlc_pulse.so.0 #4 0x00007fffdb5ef2fe in ?? () from /usr/lib/x86_64-linux-gnu/vlc/plugins/audio_output/libpulse_plugin.so #5 0x00007fffe87b21c3 in ?? () from /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #6 0x00007fffe87b272a in vlc_module_load () from /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #7 0x00007fffe880255e in ?? () from /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #8 0x00007fffe87f32c4 in input_resource_GetAout () from /usr/lib/x86_64-linux-gnu/libvlccore.so.9 #9 0x00007fffe8575a8c in libvlc_media_player_new () from /usr/lib/x86_64-linux-gnu/libvlc.so.5 #10 0x00007fffe8ad2e42 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #11 0x00007fffe8acafc0 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #12 0x00007fffe8aae45a in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #13 0x00007ffff6b677fd in ?? () from /usr/lib/x86_64-linux-gnu/libphonon4qt5.so.4 #14 0x00007ffff6b77b3d in ?? () from /usr/lib/x86_64-linux-gnu/libphonon4qt5.so.4 #15 0x00007ffff6b7c30c in Phonon::MediaNodePrivate::backendObject() () from /usr/lib/x86_64-linux-gnu/libphonon4qt5.so.4 #16 0x00007ffff6b85532 in Phonon::Path::reconnect(Phonon::MediaNode*, Phonon::MediaNode*) () from /usr/lib/x86_64-linux-gnu/libphonon4qt5.so.4 #17 0x00007ffff6b858f0 in Phonon::createPath(Phonon::MediaNode*, Phonon::MediaNode*) () from /usr/lib/x86_64-linux-gnu/libphonon4qt5.so.4 #18 0x0000555555566146 in ?? () #19 0x00007ffff6473c2c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00007ffff2ddc6db in start_thread (arg=0x7fffe96fb700) at pthread_create.c:463 #21 0x00007ffff5d68a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
I just ran today's updates (KDE 5.19.3). Instead of the cut-off, is is now completely silent for me too, as others reported.
I ran the same commands using Opensuse Tumbleweed which is still on plasma 5.9.2 and the output was: garry@opensuse:~> gdb plasma_session GNU gdb (GDB; openSUSE Tumbleweed) 8.3.1 Copyright (C) 2019 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from plasma_session... (No debugging symbols found in plasma_session) Missing separate debuginfos, use: zypper install plasma5-workspace-debuginfo-5.19.2-2.1.x86_64 (gdb) bt No stack. (gdb)
With plamsa 5.19.2 no login sound Updated glib2.0 to 2.64.4 and got 1 second login sound before it cutoff With plamsa 5.19.3 no login sound again.
With plamsa 5.19.3 no login sound again. And the file for login is always empty.... wheile the file for logout is OK
Unsolved Mysteries is going to do a story about the missing login sound in KDE Plasma 5.19.3. LOL Please don't ban me.
I can confirm. The startup sound was cut-off to ca. 0,4s but after 5.19.3 update there is no startup sound at all. Operating System: Manjaro Linux KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 Kernel Version: 5.7.7-1-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530
Hi, I report this bug also affects Mageia 8 Cauldron Operating System: Mageia 8 KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 Kernel Version: 5.7.8-desktop-1.mga8 OS Type: 64-bit Notification sounds within Plasma Workspace are played very well even the logout sound. Never the login sound is played. Testing $ paplay /usr/share/sounds/Oxygen-Sys-Log-In-Short.ogg Sound is correctly played.
I don't know if this is relevant, but my laptop has a mute key with a little light on it so you can tell when the sound is muted. I notice that the light is illuminated when I start up the machine and remains illuminated while SDDM is visible. Once I log in, the light turns off, indicating that sound is no longer muted. So perhaps what's happening is that all sound is somehow getting muted, and then it un-mutes only after login?
(In reply to Nate Graham from comment #30) > ... So perhaps what's happening is that all sound is somehow > getting muted, and then it un-mutes only after login? I'm able to observe similar behaviour as seen from the speaker icon in plasma'a panel, as I noted earlier in comment #6
(In reply to Nate Graham from comment #30) > I don't know if this is relevant, but my laptop has a mute key with a little > light on it so you can tell when the sound is muted. I notice that the light > is illuminated when I start up the machine and remains illuminated while > SDDM is visible. Once I log in, the light turns off, indicating that sound > is no longer muted. So perhaps what's happening is that all sound is somehow > getting muted, and then it un-mutes only after login? I also see the same behaviour with the plasma's sound applet which seems to be muted at logon, I can see for a fraction of seconds that it is muted with the red circle and there after it is un-muted. So, there is no sound played or it is played.
I can see the bug when simply restarting plasmashell itself; the plasma-pa applet briefly displays the muted symbol before changing it to the normal volume level icon. So it seems like something in the plasma startup sequence is muting the system, then un-muting it later.
*** Bug 424521 has been marked as a duplicate of this bug. ***
After update to Plasma 5.19.4 problem escalated and there is NO SYSTEM SOUNDS. We won't hear anything when unplugging from AC, there will be no popping-sound when changing volume, etc. I checked in system settings, and none of the oxygen sounds are played when hit play button. I'm not aware about any other viable sound theme for Plasma, so I can't check if the issue is with oxygen-sounds or other Plasma components. I'm not sure if that is the same problem but worse or another bug, but if it wasn't reported, I will. But before I do it, I'll ask Manjaro community if they have the same issue or is it just me.
(In reply to Michał Dybczak from comment #35) > After update to Plasma 5.19.4 problem escalated and there is NO SYSTEM > SOUNDS. We won't hear anything when unplugging from AC, there will be no > popping-sound when changing volume, etc. > I checked in system settings, and none of the oxygen sounds are played when > hit play button. I'm not aware about any other viable sound theme for > Plasma, so I can't check if the issue is with oxygen-sounds or other Plasma > components. > > I'm not sure if that is the same problem but worse or another bug, but if it > wasn't reported, I will. But before I do it, I'll ask Manjaro community if > they have the same issue or is it just me. For me the problem is only the muting of the startup sound, other system sounds work fine. I'm not using any default Oxygen sounds but I don't think that should make a difference. When I restart the shell (kquitapp5 plasmashell && kstart5 plasmashell), the sound becomes muted and doesn't unmute by itself anymore.
False alarm. It turned out that updating of oxygen-sounds went wrong. The package couldn't update the existing files so it created /usr/share/sounds.old and then created A FILE sounds. I deleted the sounds file and renamed sounds.old to sounds directory and that brought back the sounds. The question now is: is the AUR package oxygen-sounds broken or was it just on my system that it worked so weirdly? Permissions and ownership was fine, so I have no idea why this happened. However, the startup sound is still fully muted.
Problem was, that the maintainer tried to copy a file on and not into a directory. Seems that the PKBUILD was broken, but they fixed it yesterday: https://aur.archlinux.org/cgit/aur.git/commit/?h=oxygen-sounds&id=da68b016e2525439be94614b1cc67b24f88ed443 So build your package against the latest sources.
(In reply to aureloud from comment #32) > I also see the same behaviour with the plasma's sound applet which seems to > be muted at logon, > > I can see for a fraction of seconds that it is muted with the red circle and > there after it is un-muted. > So, there is no sound played or it is played. For me, the mute indicator in the volume control plasmoid doesn't even show up during login at all unless I had the volume muted prior to the most recent logout. I already disabled the startup splash completely to make sure I can reproduce your reported behavior.
I don't see mute indicator either, but I assume that is because of the delay. When a panel shows up, sound is already unmuted. I use latte, but maybe system panel shows up quicker and someone is able to see it.
It seems, that it does not trigger the notifications for the "Login" event. To see what happen, I set beside the sound in the notification configuration now also a "Log to a file" option for the "Login" and "Logout" events. On every logout an entry has been written, but not after a login.
I had more or less similar issues with sound in KDE (first second of notifications being ragged and quiet) for some time until I managed to pinpoint the cause recently. For me it was Pulseaudio set up (by default) to suspend sinks/sources when idle. To disable Pulseaudio suspend: 1. edit /etc/pulse/default.pa 2. comment out (with #) this line: load-module module-suspend-on-idle 3. `pulseaudio -k` or restart computer Probably worth checking if this helps in your cases.
(In reply to phd from comment #42) > I had more or less similar issues with sound in KDE > (first second of notifications being ragged and quiet) > for some time until I managed to pinpoint the cause recently. > > For me it was Pulseaudio set up (by default) to suspend sinks/sources when > idle. > > To disable Pulseaudio suspend: > 1. edit /etc/pulse/default.pa > 2. comment out (with #) this line: > load-module module-suspend-on-idle > 3. `pulseaudio -k` or restart computer > > Probably worth checking if this helps in your cases. For me this didn't help. Also, the sound is now always muted after login until I manually unmute.
Proposed workaround on Comment #42 does not work. Therefore, when Plasma goes back from lock screen, I see: plasmashell[8978]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/ListItemBase.qml:151: TypeError: Cannot read property 'ports' of undefined plasmashell[8978]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor" plasmashell[8978]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/main.qml:550:39: QML DeviceListItem: Binding loop detected for property "width" Could be related. Therefore, audio works within session. No log on sound played. Log out sound and all other are OK. $ pacmd list-sinks | grep -e 'name:' -e 'index:' * index: 1 name: <alsa_output.pci-0000_00_1f.3.analog-stereo> index: 3 name: <alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1> $ pacmd list-cards 2 card(s) available. index: 0 name: <alsa_card.pci-0000_01_00.1> driver: <module-alsa-card.c> owner module: 6 properties: alsa.card = "1" alsa.card_name = "HDA NVidia" alsa.long_card_name = "HDA NVidia at 0xed080000 irq 17" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:01:00.1" sysfs.path = "/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1" device.bus = "pci" device.vendor.id = "10de" device.vendor.name = "NVIDIA Corporation" device.product.id = "1aeb" device.product.name = "TU116 High Definition Audio Controller" device.string = "1" device.description = "TU116 High Definition Audio Controller" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Sortie Digital Stereo (HDMI) (priority 5900, available: no) output:hdmi-surround: Sortie Digital Surround 5.1 (HDMI) (priority 800, available: no) output:hdmi-surround71: Sortie Digital Surround 7.1 (HDMI) (priority 800, available: no) output:hdmi-stereo-extra1: Sortie Digital Stereo (HDMI 2) (priority 5700, available: unknown) output:hdmi-stereo-extra2: Sortie Digital Stereo (HDMI 3) (priority 5700, available: no) output:hdmi-surround-extra2: Sortie Digital Surround 5.1 (HDMI 3) (priority 600, available: no) output:hdmi-surround71-extra2: Sortie Digital Surround 7.1 (HDMI 3) (priority 600, available: no) output:hdmi-stereo-extra3: Sortie Digital Stereo (HDMI 4) (priority 5700, available: no) output:hdmi-surround-extra3: Sortie Digital Surround 5.1 (HDMI 4) (priority 600, available: no) output:hdmi-surround71-extra3: Sortie Digital Surround 7.1 (HDMI 4) (priority 600, available: no) output:hdmi-stereo-extra4: Sortie Digital Stereo (HDMI 5) (priority 5700, available: no) output:hdmi-surround-extra4: Sortie Digital Surround 5.1 (HDMI 5) (priority 600, available: no) output:hdmi-surround71-extra4: Sortie Digital Surround 7.1 (HDMI 5) (priority 600, available: no) output:hdmi-stereo-extra5: Sortie Digital Stereo (HDMI 6) (priority 5700, available: no) output:hdmi-surround-extra5: Sortie Digital Surround 5.1 (HDMI 6) (priority 600, available: no) output:hdmi-surround71-extra5: Sortie Digital Surround 7.1 (HDMI 6) (priority 600, available: no) off: Éteint (priority 0, available: unknown) active profile: <output:hdmi-stereo-extra1> sinks: alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1/#3: TU116 High Definition Audio Controller Digital Stereo (HDMI 2) sources: alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1.monitor/#3: Monitor of TU116 High Definition Audio Controller Digital Stereo (HDMI 2) ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: yes) properties: device.icon_name = "video-display" device.product.name = "ED273 A" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-3: HDMI / DisplayPort 4 (priority 5600, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-4: HDMI / DisplayPort 5 (priority 5500, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-5: HDMI / DisplayPort 6 (priority 5400, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: <alsa_card.pci-0000_00_1f.3> driver: <module-alsa-card.c> owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0x2ffff20000 irq 145" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1f.3" sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "a170" device.product.name = "100 Series/C230 Series Chipset Family HD Audio Controller" device.form_factor = "internal" device.string = "0" device.description = "Audio interne" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Entrée Stéréo analogique (priority 65, available: no) output:analog-stereo: Sortie Stéréo analogique (priority 6500, available: unknown) output:analog-stereo+input:analog-stereo: Duplex stéréo analogique (priority 6565, available: no) output:analog-surround-21: Sortie Surround analogique 2.1 (priority 1300, available: unknown) output:analog-surround-21+input:analog-stereo: Sortie Surround analogique 2.1 + Entrée Stéréo analogique (priority 1365, available: no) output:analog-surround-40: Sortie Surround analogique 4.0 (priority 1200, available: unknown) output:analog-surround-40+input:analog-stereo: Sortie Surround analogique 4.0 + Entrée Stéréo analogique (priority 1265, available: no) output:analog-surround-41: Sortie Surround analogique 4.1 (priority 1300, available: unknown) output:analog-surround-41+input:analog-stereo: Sortie Surround analogique 4.1 + Entrée Stéréo analogique (priority 1365, available: no) output:analog-surround-50: Sortie Surround analogique 5.0 (priority 1200, available: unknown) output:analog-surround-50+input:analog-stereo: Sortie Surround analogique 5.0 + Entrée Stéréo analogique (priority 1265, available: no) output:analog-surround-51: Sortie Surround analogique 5.1 (priority 1300, available: unknown) output:analog-surround-51+input:analog-stereo: Sortie Surround analogique 5.1 + Entrée Stéréo analogique (priority 1365, available: no) output:iec958-stereo: Sortie Stéréo numérique (IEC958) (priority 5500, available: unknown) output:iec958-stereo+input:analog-stereo: Sortie Stéréo numérique (IEC958) + Entrée Stéréo analogique (priority 5565, available: no) off: Éteint (priority 0, available: unknown) active profile: <output:analog-stereo> sinks: alsa_output.pci-0000_00_1f.3.analog-stereo/#1: Audio interne Stéréo analogique sources: alsa_output.pci-0000_00_1f.3.analog-stereo.monitor/#1: Monitor of Audio interne Stéréo analogique ports: analog-input-front-mic: Microphone avant (priority 8500, latency offset 0 usec, available: no) properties: device.icon_name = "audio-input-microphone" analog-input-rear-mic: Microphone arrière (priority 8200, latency offset 0 usec, available: no) properties: device.icon_name = "audio-input-microphone" analog-input-linein: Entrée ligne (priority 8100, latency offset 0 usec, available: no) properties: analog-output-lineout: Sortie ligne (priority 9000, latency offset 0 usec, available: yes) properties: analog-output-headphones: Casque audio (priority 9900, latency offset 0 usec, available: no) properties: device.icon_name = "audio-headphones" iec958-stereo-output: Sortie numérique (S/PDIF) (priority 0, latency offset 0 usec, available: unknown) properties:
*** Bug 425222 has been marked as a duplicate of this bug. ***
Ok time for me to chip in again (I was on one of the marked duplicates, forget which one). Long story short, I doubt is pulse/audio settings messing up. So I tried everything: default sound, ogg file, wav file, short sound, even tried with a full 3 minute+ song and got nothing. So I got an idea and made a simple bash script to play one of my custom sounds: "ffplay <file> -nodisp -nostats -hide_banner -autoexit" and set it to autostart on login on system settings. It worked perfectly. Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.3-zen1-1-zen OS Type: 64-bit Processors: 8 × AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx Memory: 7.6 GiB of RAM Graphics Processor: AMD RAVEN
ffplay doesn't use pulseaudio, but SDL.
As I already commented in https://bugs.kde.org/show_bug.cgi?id=422948#c41, the problem seems that it does not trigger the notifications for the "Login" event. The "ffplay"-command in konsole plays the sound, but not, if it has been set as a command for notifications. I still use th "Log to a file" option for the "Login" and "Logout" events, but only logouts are written, and never a logon. To place a "ffplay"-command on autostart may be a workaround for a missing startup-sound, but is not a solution that the logon-events are not handled.
I managed this workaround: Write a .desktop file in /etc/xdg/autostart/ like this: touch /etc/xdg/autostart/org.kde.plasma_startup_sound.desktop vi /etc/xdg/autostart/org.kde.plasma_startup_sound.desktop Add this: [Desktop Entry] Exec=/usr/bin/paplay /usr/share/sounds/Oxygen-Sys-Log-In-Short.ogg Name=Plasma Desktop Startup Sound Type=Application X-KDE-StartupNotify=false OnlyShowIn=KDE; Icon=plasma NoDisplay=true Save file. Reboot. Log in. Booh. Startup sound played !! This is hacky. Needs paplay binary from PulseAudio (generaly on all Linux systems meanwhile) BUT end-user doesn't have to write this type of hack. Aurélien Mageia Bugsquad and QA Team. Operating System: Mageia 8 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.6-desktop-1.mga8 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2
Nice hack Aurélien. Even plays during the KDE Login splash. Our users were beginning to miss the doo dee doo dee dum at login. Thanks.
(In reply to Aurélien Oudelet (auroud85_fr) from comment #49) > /etc/xdg/autostart/org.kde.plasma_startup_sound.desktop I found out that this also works if you save the file to ~/.config/autostart. It's useful if you don't want to touch system files or your computer has multiple users and you want each one to play a different sound.
Nice, #49 works for me now. However, I found that some processes were blocking the sound so I had to delete the existing /etc/xdg/autostart/pulseaudio.desktop and also systemctl disable timidity.
The login sound is still muted in Plasma 5.19.5 (Arch linux and KDE Neon).
Login sound is still muted in Plasma 5.19.5 both in Arch system and KDE Neon.
Workaround from #49 no longer works in Plasma 5.19.5, sound is now again always muted on startup.
WOW it is STILL broken in 5.20.0!
I can confirm, the bug is still present in 5.20. This is taking quite a long time :( . The whole 5.19 without a fix and now a new release that is inheriting this problem.
Just updated kde neon to plasma 5.20.1 and no change still
Kubuntu upgrade from 20.04 (Plasma 5.18.x) to 20.10 (Plasma 5.19.x) meant system login sound has no effect at all. If you try to force a login sound by other means, e.g. "~/.config/autostart/login-sound.desktop" or "~/.config/autostart-scripts/login-sound.sh" the situation gets worse - often crashing plasma altogether with a black screen. At best, if a very short (nearly 1 second) audio file is used, it is played with a pause near the end, and even then sometimes causes plasma to crash.
As I told already months before, it has nothing to do with the sound, the problem is that events are not handldes correctly on sign on. You can easily verify that if you configure a another action like writing a logfile on logon-/logoff-event, and you realize that log entries are written on logoff but not on logon. Developers should watch in that direction, than always and only to a missing sound.
This is said to be fixed in 5.19.3 with this: https://invent.kde.org/plasma/plasma-workspace/-/commit/ef4b84869612318ecb3cec44bd6c713ad545114f But it is not the case. According to: (In reply to Martin Schnitkemper from comment #60) > As I told already months before, it has nothing to do with the sound, the > problem is that events are not handldes correctly on sign on. You can > easily verify that if you configure a another action like writing a logfile > on logon-/logoff-event, and you realize that log entries are written on > logoff but not on logon. > > Developers should watch in that direction, than always and only to a missing > sound. The issue is weird. Workaround in Comment 49 still work with 5.20.1 under Mageia Caulron, but seems to delay te end of KSplash to the end of the sound file to be played. This needs some testing on my side. Best regards,
Here is a workaround that plays the sound while KSplash is running: Create a script file somewhere, and insert this content: #!/bin/bash amixer -D pulse sset Master unmute play /usr/share/sounds/Oxygen-Sys-Log-In-Short.ogg Make sure 'sox' is installed, and go to System Settings > Startup and Shutdown > Autostart. Click « Add » and « Add Login Script », and select the script file you created earlier. Now, the startup sound will play correctly.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/394
I tried the patch and startup sound is back for me now. But other events like notifications or logfile entries on startup still does not work, therefore I still think that the main problem is elsewhere, than just to fix the startup sound problem.
Git commit 86e74d75dfceb4d70802861258763ece61bdb40b by David Edmundson. Committed on 27/10/2020 at 00:15. Pushed by davidedmundson into branch 'master'. [plasma-session] Fix application lifespan We want to last until all jobs are finished and the notification sound thread has finished. The design intention was to let QEventLoopLocker handle all of it implicitly, but that doesn't work when we call quit explicitly. M +5 -3 startkde/plasma-session/startup.cpp https://invent.kde.org/plasma/plasma-workspace/commit/86e74d75dfceb4d70802861258763ece61bdb40b
Git commit e67dc48ae2706dcf0a2785a37823bf54c838cac9 by David Edmundson. Committed on 27/10/2020 at 11:28. Pushed by davidedmundson into branch 'Plasma/5.20'. [plasma-session] Fix application lifespan We want to last until all jobs are finished and the notification sound thread has finished. The design intention was to let QEventLoopLocker handle all of it implicitly, but that doesn't work when we call quit explicitly. (cherry picked from commit 86e74d75dfceb4d70802861258763ece61bdb40b) M +5 -3 startkde/plasma-session/startup.cpp https://invent.kde.org/plasma/plasma-workspace/commit/e67dc48ae2706dcf0a2785a37823bf54c838cac9
(In reply to Martin Schnitkemper from comment #64) > But other events like notifications or logfile entries on startup still does > not work, therefore I still think that the main problem is elsewhere, than > just to fix the startup sound problem. Plasma doesn't use the notification system for the startup/login sound, but rather plays the configured sound file directly via Phonon. So this is somewhat intentional. I think the reason why it was done this way was that using knotifications caused hangs or other problems on login due to race conditions in the startup procedure.
I can not say, since when the notification-problem exist. I just discovered it since the "play a sound"-event is configured in the same systemsettings panel than the other events, but I didn't used them so far. After I discovered the startup sound problem, I configured in addition the "log to a file"-event to verify, if it is just a sound problem or a general problem with the notifications. And I can confirm now, that the problem affects every event, that should be triggered on startup. I configured the same events on logout, and on every logout I got an entry in the logfile, written by KNotify, but never on login. Same happen with the "show a message in a popup". If that leads into a racing condition, than this concept is unusable for any other event too, since it doesn't work. If it works on logout, why not on logon?
(In reply to Martin Schnitkemper from comment #68) > I can not say, since when the notification-problem exist. I just discovered > it since the "play a sound"-event is configured in the same systemsettings > panel than the other events, but I didn't used them so far. > > After I discovered the startup sound problem, I configured in addition the > "log to a file"-event to verify, if it is just a sound problem or a general > problem with the notifications. And I can confirm now, that the problem > affects every event, that should be triggered on startup. I configured the > same events on logout, and on every logout I got an entry in the logfile, > written by KNotify, but never on login. Same happen with the "show a > message in a popup". The special code in plasmashell that plays the login sound only supports playing a sound. It completely ignores the other options. Otherwise these notification settings are handled by knotifications, which supports things like logging or showing a message too. The point is that what you noticed is not really a bug per se (rather a missing feature), and totally unrelated to the original problem. > If that leads into a racing condition, than this concept is unusable for any > other event too, since it doesn't work. If it works on logout, why not on > logon? The specific problem here is that on login things are still being started and not everything may be running yet. That said, I don't know if that would still be a problem, but I do remember reading something like this in some other bug report about problems with the startup/login sound which led to the current solution of using Phonon directly instead of notifications.
Today I booted the system and heard the startup sound for the first time since months! :D The weird thing is, I didn't see any KDE packages in the update. The only related packages may be pulseaudio packages (6 of them). This is confusing, did I get the fix already (Manjaro testing) but I just don't recognize which package it was, or maybe some other package independently fixed the problem?
(In reply to Michał Dybczak from comment #70) > The weird thing is, I didn't see any KDE packages in the update. The only > related packages may be pulseaudio packages (6 of them). On native Arch, the version 5.20.2-1 of package plasma-workspace did the thing. There should be something similar in Manjaro
Yeah, I have plasma-workspace 5.20.2-1 since 27.10. I wonder why I heard the sound today for the first time and not the other days before? Oh, well, I hope it will stay. If not, I'll report it here, but I assume this will work now. Thank you for fixing it. We've waited long for this. There is also an issue with the shut-down sound, but that is a complete different problem, not sure if it was ever reported. The issue is simple, when having shut down sound, a whole shut down process is stopped till the sound plays out, so in effect, the sound is causing massive delay to the process. Because of that, we can't use this option. If the sound was playing while other parts of plasma are already being stopped, it would be great. Not sure if it's possible but still. What do you think? Should I report it? It's nothing essential or important, just a thing that exists in Plasma and is not really functional yet.
(In reply to Michał Dybczak from comment #72) > What do you think? Should I report it? It's nothing essential or important, > just a thing that exists in Plasma and is not really functional yet. No opinion here, but in any case it should be reported separately if it is considered important.
This issue seems to have reappeared again in 5.21.0 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.17-200.fc33.x86_64
(In reply to Colin J Thomson from comment #74) > This issue seems to have reappeared again in 5.21.0 I can't confirm this behaviour, it still works for me Operating System: Arch Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-arch1-1
I can't confirm this behavior, it still works for us. Operating System: PCLinuxOS KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.17-pclos1
OK thanks for checking. Do you have "Plasma systemd startup" enabled? systemctl --user status plasma-plasmashell.service If I disable it with: kwriteconfig5 --file startkderc --group General --key systemdBoot false And restart the login sound works fine. Operating System: Fedora
Can someone file a new bug report for this issue happening again only when using systemd startup? Thanks
Done https://bugs.kde.org/show_bug.cgi?id=433490
Created attachment 136084 [details] attachment-30891-0.html All is ok for me ! Operating System: Arch Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1650 SUPER/PCIe/SSE2 Le mar. 23 févr. 2021 à 15:46, phd <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=422948 > > phd <phd@phd.re> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > See Also| | > https://bugs.kde.org/show_b > | |ug.cgi?id=433490 > > -- > You are receiving this mail because: > You are on the CC list for the bug.
All is fine for me as well. Plasma 5.21.1. I'm not using systemd Plasma startup (it was not enabled by default and from various places I see some issues with it, so I'll stay away from it for now).
I'm using systemd startup and the login sound never plays. Is this a known issue?
(In reply to kde from comment #82) > I'm using systemd startup and the login sound never plays. > Is this a known issue? https://bugs.kde.org/show_bug.cgi?id=422948#c79
This bug has resurfaced in 5.24. Once the session login is completed the sound device operates normally. In my case the device is through my laptop HDMI port. I have replicated this behavior on my desktop HDMI port as well.
See https://bugs.kde.org/show_bug.cgi?id=449828 for 5.24
Created attachment 146808 [details] attachment-9183-0.html The same as stevmc@gmail.com for me ! This bug has resurfaced in 5.24. Le mer. 16 févr. 2022 à 02:39, Nicolas Fella <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=422948 > > Nicolas Fella <nicolas.fella@gmx.de> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |FIXED > CC| |nicolas.fella@gmx.de > Status|REOPENED |RESOLVED > > --- Comment #85 from Nicolas Fella <nicolas.fella@gmx.de> --- > See https://bugs.kde.org/show_bug.cgi?id=449828 for 5.24 > > -- > You are receiving this mail because: > You are on the CC list for the bug.
I have posted a workaround script on linuxquestions.org here: https://www.linuxquestions.org/questions/slackware-14/kde-startup-sound-muted-until-login-after-latest-plasma-5-24-updates-4175707891/
I confirm. After update to 5.24 the regression is back again. I believe it's a third time now? The symptoms are the same, but the cause may be different. The logoff sound still plays correctly.
Regression and behavior persists in 5.24.1 packages. I upgraded yesterday and verified bug has not been resolved.
Yeah, the issue is back. What is different this time (for me) is that when I reported the bug, volume got muted automatically. This doesn't seem to happen now.
Created attachment 146843 [details] attachment-11548-0.html Hello Steve ! Thanks for the workaround ! I have changed the soft for the sound ! in place of ogg123 I use gst123... better for me ! no more ! Thanks again Le mer. 16 févr. 2022 à 16:52, Steve <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=422948 > > Steve <stevmc@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Ever confirmed|1 |0 > Resolution|FIXED |--- > Status|RESOLVED |REPORTED > > --- Comment #87 from Steve <stevmc@gmail.com> --- > I have posted a workaround script on linuxquestions.org here: > > https://www.linuxquestions.org/questions/slackware-14/kde-startup-sound-muted-until-login-after-latest-plasma-5-24-updates-4175707891/ > > -- > You are receiving this mail because: > You are on the CC list for the bug.
*** Bug 449828 has been marked as a duplicate of this bug. ***
this bug still happens and the workaround doesn't work.
I just updated Plasma to 5.24.1 on both my Manjaro PCs, and I can confirm this bug as soon as I log in. Luckily, the older workaround described in comment #49 works like a charm with this version of Plasma. I haven't tried the newer workaround described in comment #87, but I think the older one is less likely to fail at least for me.
Isecond the bug. In my case, the login sound is completely gone on two different systems (running latest plasma).
*** Bug 453022 has been marked as a duplicate of this bug. ***
I don't know how & why, but since I upgraded today to KDE Plasma Version 5.25.0 and KDE Frameworks Version 5.95.0 the startup sound is back again on all systems after months of absence.
(In reply to Martin Schnitkemper from comment #97) > I don't know how & why, but since I upgraded today to KDE Plasma Version > 5.25.0 and KDE Frameworks Version 5.95.0 the startup sound is back again on > all systems after months of absence. Confirmed, startup sound is back again with 5.25.0
KDE login sound is still dead with 5.25.0 and 5.95.0 on PCLinuxOS. :'(
(In reply to Texstar from comment #99) > KDE login sound is still dead with 5.25.0 and 5.95.0 on PCLinuxOS. :'( Wild guess: It has something to with PCLinuxOS not using systemd. I am on Archlinux with systemd .
It still doesn't work on KDE neon ! ! ! ? ? ? So I have to keep using that autostart script to play it at least two seconds after login. Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.13.0-51-generic (64-bit) Graphics Platform: X11 No other audio issues!..
(In reply to Georg Wolfram from comment #100) > I am on Archlinux with systemd . It doesn't seem to work on Manjaro though. KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.5-1-MANJARO (64-bit) Graphics Platform: X11
(In reply to smow from comment #102) > (In reply to Georg Wolfram from comment #100) > > > I am on Archlinux with systemd . > > It doesn't seem to work on Manjaro though. > After rebooting once more looks like it works just fine now!
I'm on Manjaro and the startup sound is back after the 5.25 upgrade :).
(In reply to Georg Wolfram from comment #100) > (In reply to Texstar from comment #99) > > KDE login sound is still dead with 5.25.0 and 5.95.0 on PCLinuxOS. :'( > > Wild guess: It has something to with PCLinuxOS not using systemd. > > I am on Archlinux with systemd . Are you saying I need systemd just to play a silly login sound? WOW! That is jacked up.
No, it's just that the systemd boot feature (which was turned on by default in Plasma 5.25) introduces a race condition that causes a bug with the existing functionality to play the startup sound. So people who opted in before 5.25 experienced this bug, then we failed to fix it in time, now everyone whose distro uses systemd and who hasn't explicitly opted out is experiencing it.
(In reply to Nate Graham from comment #106) > No, it's just that the systemd boot feature (which was turned on by default > in Plasma 5.25) introduces a race condition that causes a bug with the > existing functionality to play the startup sound. So people who opted in > before 5.25 experienced this bug, then we failed to fix it in time, now > everyone whose distro uses systemd and who hasn't explicitly opted out is > experiencing it. It's the other way around. Using systemd-boot *fixes* the issue, that's why for most people it appears fixed
(In reply to Nicolas Fella from comment #107) > (In reply to Nate Graham from comment #106) > > No, it's just that the systemd boot feature (which was turned on by default > > in Plasma 5.25) introduces a race condition that causes a bug with the > > existing functionality to play the startup sound. So people who opted in > > before 5.25 experienced this bug, then we failed to fix it in time, now > > everyone whose distro uses systemd and who hasn't explicitly opted out is > > experiencing it. > > It's the other way around. Using systemd-boot *fixes* the issue, that's why > for most people it appears fixed Does this mean that I still have the same issue going on after upgrading KDE neon from 5.24 to 5.25 because *systemd boot feature wasn't turned on* somehow during the upgrade process? How can I turn it on at least to check and confirm this please? Thank you.
Git commit a8eeac81550f32003a0609adad4965e311d86866 by Nicolas Fella, on behalf of Jolene K. Committed on 09/11/2022 at 16:22. Pushed by nicolasfella into branch 'master'. startkde/plasma-session: fix playing startup sound Attaching the Phonon objects to the Startup object and then immediately deleting the Startup object leads to the Phonon objects being deleted too and no sound will play. I have no idea how that ever worked, maybe Phonon used to work differently in the past or maybe it depends on the backend. Since the MediaObject is configured to autodelete itself after it finishes playing, it doesn't need to be parented to anything. M +1 -1 startkde/plasma-session/startup.cpp M +4 -4 startkde/startplasma.cpp M +1 -1 startkde/startplasma.h https://invent.kde.org/plasma/plasma-workspace/commit/a8eeac81550f32003a0609adad4965e311d86866
Git commit c27f2a5ef1156ffc10018327426cbf03de9945a1 by Nicolas Fella, on behalf of Jolene K. Committed on 09/11/2022 at 16:24. Pushed by nicolasfella into branch 'Plasma/5.26'. startkde/plasma-session: fix playing startup sound Attaching the Phonon objects to the Startup object and then immediately deleting the Startup object leads to the Phonon objects being deleted too and no sound will play. I have no idea how that ever worked, maybe Phonon used to work differently in the past or maybe it depends on the backend. Since the MediaObject is configured to autodelete itself after it finishes playing, it doesn't need to be parented to anything. (cherry picked from commit a8eeac81550f32003a0609adad4965e311d86866) M +1 -1 startkde/plasma-session/startup.cpp M +4 -4 startkde/startplasma.cpp M +1 -1 startkde/startplasma.h https://invent.kde.org/plasma/plasma-workspace/commit/c27f2a5ef1156ffc10018327426cbf03de9945a1
The above commit fixes startup sound for those that are not using systemd boot
I can confirm this commit fixes KDE Plasma login sound on non-systemd distributions. Thank you and the users of PCLinuxOS thank you too!
*** Bug 463076 has been marked as a duplicate of this bug. ***
Look like this is happening again. We're tracking it now in Bug 482716 since it may have a different root cause than this bug, and require a different fix.