[plasmashell] [Bug 482082] Plasma takes an extra 33 seconds to start after entering password and logging in when choosing the Breeze Splash Screen - KDE / Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482082 --- Comment #9 from Kevin R --- (In reply to Arjen Hiemstra from comment #7) > Just to collect some extra data, can we the output of `systemd-analyze > --user blame` for those that can reproduce this bug? While there is > something going on with ksplash it'd be useful to exclude other things going > wrong. 1min 49ms drkonqi-coredump-pickup.service 2.044s xdg-desktop-portal.service 1.656s plasma-kcminit.service 1.582s xdg-desktop-portal-gtk.service 169ms plasma-powerdevil.service 143ms plasma-ksmserver.service 111ms plasma-plasmashell.service 108ms pulseaudio.service 89ms plasma-polkit-agent.service 86ms plasma-xdg-desktop-portal-kde.service 70ms plasma-kded6.service 35ms plasma-kactivitymanagerd.service 20ms plasma-ksplash-ready.service 17ms obex.service 16ms plasma-kglobalaccel.service 13ms kde-baloo.service 11ms plasma-kwin_wayland.service 8ms plasma-kcminit-phase1.service 6ms dbus.socket 6ms app-kaccess@autostart.service 6ms xdg-document-portal.service 5ms plasma-restoresession.service 5ms app-lts_eol@autostart.service 5ms app-org.kde.discover.notifier@autostart.service 4ms session-migration.service 4ms app-org.kde.kdeconnect.daemon@autostart.service 3ms xdg-desktop-portal-rewrite-launchers.service 3ms at-spi-dbus-bus.service 3ms app-org.kde.xwaylandvideobridge@autostart.service 2ms app-snap\x2duserd\x2dautostart@autostart.service 2ms dconf.service 2ms xdg-permission-store.service -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482082] Plasma takes an extra 33 seconds to start after entering password and logging in when choosing the Breeze Splash Screen - KDE / Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482082 --- Comment #10 from Kevin R --- (In reply to Arjen Hiemstra from comment #7) > Just to collect some extra data, can we the output of `systemd-analyze > --user blame` for those that can reproduce this bug? While there is > something going on with ksplash it'd be useful to exclude other things going > wrong. My previous comment was with the splash screen chosen. Below is with the splash screen as "none" and then I rebooted: 1.969s xdg-desktop-portal.service 1.667s plasma-kcminit.service 1.592s xdg-desktop-portal-gtk.service 139ms plasma-ksmserver.service 134ms plasma-powerdevil.service 92ms plasma-plasmashell.service 89ms pulseaudio.service 64ms plasma-polkit-agent.service 63ms plasma-xdg-desktop-portal-kde.service 62ms plasma-kded6.service 34ms plasma-kactivitymanagerd.service 22ms plasma-kglobalaccel.service 20ms kde-baloo.service 13ms plasma-kwin_wayland.service 8ms plasma-restoresession.service 7ms app-kaccess@autostart.service 7ms plasma-kcminit-phase1.service 6ms plasma-ksplash-ready.service 6ms dbus.socket 6ms app-lts_eol@autostart.service 6ms app-org.kde.discover.notifier@autostart.service 6ms xdg-document-portal.service 5ms app-org.kde.kdeconnect.daemon@autostart.service 4ms app-snap\x2duserd\x2dautostart@autostart.service 4ms app-org.kde.xwaylandvideobridge@autostart.service 4ms session-migration.service 4ms at-spi-dbus-bus.service 3ms obex.service 2ms xdg-desktop-portal-rewrite-launchers.service 2ms dconf.service 2ms xdg-permission-store.service -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482082] Plasma takes an extra 33 seconds to start after entering password and logging in when choosing the Breeze Splash Screen - KDE / Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482082 Kevin R changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #11 from Kevin R --- Just did a system update today and this issue appears to be resolved. I was curious as I saw a file with the name "Breeze" in it and decided to re-enable to splash screen after the update was completed. I rebooted, and lo and behold, the splash screen appeared after I entered my password for about a 1/2 second and then the desktop loaded. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482045] Custom notification sounds do not work
https://bugs.kde.org/show_bug.cgi?id=482045 --- Comment #6 from Kevin R --- (In reply to nathan from comment #5) > Even using the ocean theme, the login sound doesn't work for me (applied via > Settings > Notifications > Plasma Workspace). I can confirm this as well. I know a few years ago, sound was muted upon startup (and then un-muted after the desktop loaded). I wonder if the same thing is happening again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482045] Custom notification sounds do not work
https://bugs.kde.org/show_bug.cgi?id=482045 --- Comment #7 from Kevin R --- So, it looks like the way Plasma 6 handles sound notifications now, as opposed to previous versions of Plasma, is the sound notifications (Settings > Notifications > Plasma Workspace) are managed by sound "references" as opposed to a direct sound file. So, for example, the default Ocean Catastrophe sound references "dialog-error-serious". I assume there is a file somewhere that references this to the actual sound file itself. I did a context search for dialog-error-serious (as an example) and I was unable to find anything. So, as I mentioned earlier, it looks like the new System Sounds themes manages / overrides the traditional custom notification sounds. So, this is definitely something that needs to be fixed if custom sound notifications are still going to be an option going forward. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482045] Custom notification sounds do not work
https://bugs.kde.org/show_bug.cgi?id=482045 --- Comment #8 from Kevin R --- (In reply to Kevin R from comment #7) > So, it looks like the way Plasma 6 handles sound notifications now, as > opposed to previous versions of Plasma, is the sound notifications (Settings > > Notifications > Plasma Workspace) are managed by sound "references" as > opposed to a direct sound file. So, for example, the default Ocean > Catastrophe sound references "dialog-error-serious". I assume there is a > file somewhere that references this to the actual sound file itself. I did a > context search for dialog-error-serious (as an example) and I was unable to > find anything. So, as I mentioned earlier, it looks like the new System > Sounds themes manages / overrides the traditional custom notification sounds. > > So, this is definitely something that needs to be fixed if custom sound > notifications are still going to be an option going forward. I forgot to mention, no matter what Sound Theme event you choose (e.g. Ocean, Oxygen, FreeDesktop), Settings > Notifications > Plasma Workspace always references the same name (e.g. dialog-error-serious). So this backs up what I mentioned earlier. A data file somewhere is what changes the sound file reference itself. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482045] Custom notification sounds do not work
https://bugs.kde.org/show_bug.cgi?id=482045 --- Comment #10 from Kevin R --- I found the following file that points all sound themes to their respective sound files: /usr/share/knotifications6/plasma_workspace.notifyrc Long story short, Settings > Notifications > will always need to point to their default sound event name. For example: Login will always need to point to 'desktop-login' Logout will always need to point to 'desktop-logout' These are all defined within the above file 'plasma_workspace.notifyrc', which then directly correlates with the respective theme file that is currently chosen. For example, /usr/share/sounds/ocean/index.theme. The only way I was able to have my own "custom" sounds was to pretty much create my own theme. However, what I did to test this out beforehand was to copy a couple of my sound files over to an existing theme sound folder (/usr/share/sounds/ocean/stereo), in this case a login and a logout sound file (they also need to be OGA files). I then did the following to rename the files: sudo mv desktop-login.oga OLD-desktop-login.oga sudo mv desktop-logout.oga OLD-desktop-logout.oga sudo mv my_login_sound_file.oga desktop-login.oga sudo mv my_logout_sound_file.oga desktop-logout.oga This essentially replaced the original files with my "custom" files. I tested this out and was able to hear my custom logout sound (login still doesn't work, but I believe that is a whole different issue). So, very long story short, your custom sounds need to be named the exact names that exist within the theme sound folder. That being said, I really hope this isn't what the KDE team intended to happen, relying only on the sound theme feature. It was a pretty long process renaming all of the sound files I wanted to use. I hope a feature is added to once again allow us to use Settings > Notifications like we have always used it in the past, -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483255] New: Plasma 6 - Startup / Login sound does not play
https://bugs.kde.org/show_bug.cgi?id=483255 Bug ID: 483255 Summary: Plasma 6 - Startup / Login sound does not play Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: bassist...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Enable startup sound / Notification theme (Settings > Colors & Themes > System Sounds 2. Verify startup sound is enabled (Settings > Notifications > Configure > Plasma Workspace > Login) 3. Preview startup sound 4. Reboot laptop / computer 5. Startup / Login sound should play but does not OBSERVED RESULT No startup / login sound EXPECTED RESULT Selected startup / login sound should play upon logging in after reboot SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION There was a problem a few years back with Plasma where sound was muted during the startup / login process, but was automatically un-muted after the desktop loaded. The startup / login sound was playing, but was basically muted. Not sure if that is the case this time. Previous workarounds did not resolve this issue for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482716] Startup sound does not play
https://bugs.kde.org/show_bug.cgi?id=482716 Kevin R changed: What|Removed |Added CC||bassist...@gmail.com --- Comment #2 from Kevin R --- *** Bug 483255 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483255] Plasma 6 - Startup / Login sound does not play
https://bugs.kde.org/show_bug.cgi?id=483255 Kevin R changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Kevin R --- *** This bug has been marked as a duplicate of bug 482716 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482020] New: KDE Neon / Plasma 6 does not Shutdown, Restart or Logout via any of the application menus (Application Dashboard, Launcher, Menu or Simple Application Launcher)
https://bugs.kde.org/show_bug.cgi?id=482020 Bug ID: 482020 Summary: KDE Neon / Plasma 6 does not Shutdown, Restart or Logout via any of the application menus (Application Dashboard, Launcher, Menu or Simple Application Launcher) Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: bassist...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Click Application Menu 2. Power / Session (or via favoritesd) 3. Choose Restart, Shutdown or Logout OBSERVED RESULT Nothing happens EXPECTED RESULT System should either Restart, Shutdown or Logout, depending on which option is chosen SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION The only way I can shutdown or restart is via CLI. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482020] KDE Neon / Plasma 6 does not Shutdown, Restart or Logout via any of the application menus (Application Dashboard, Launcher, Menu or Simple Application Launcher)
https://bugs.kde.org/show_bug.cgi?id=482020 --- Comment #2 from Kevin R --- (In reply to Antonio Rojas from comment #1) > > *** This bug has been marked as a duplicate of bug 481938 *** Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482045] New: Notification sounds do not work - KDE Neon / Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482045 Bug ID: 482045 Summary: Notification sounds do not work - KDE Neon / Plasma 6 Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: bassist...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Got to Settings > Notifications > Plasma Workspace 2. Most but not all default sound previews work 3. If changing to a different (custom) sound, none of the sound previews work 4. Regardless if using default sounds or custom sounds, notifications don't produce a sound (e.g. Login, Logout, Device Plugged In, and so on) 5. All other sounds work (e.g. playing music from a media app) 6. The only "event" sound that works is the popping sound when changing the volume level 7. I have tried WAV and OGG files OBSERVED RESULT Notifications do not produce a sound, regardless if using the default sound or if changing to a custom sound EXPECTED RESULT Notifications such as Login, Logout, Device Plugged In should produce a sound if I have a sound assigned. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482082] New: Plasma takes an extra 33 seconds to start after entering password and logging in when choosing the Breeze Splash Screen - KDE / Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482082 Bug ID: 482082 Summary: Plasma takes an extra 33 seconds to start after entering password and logging in when choosing the Breeze Splash Screen - KDE / Plasma 6 Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: bassist...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY By default, the Breeze Splash screen is enabled. I noticed the system took a long time to log in after entering my password after upgrading to Neon / Plasma 6. I went to disable to splash screen in order to look at the text of what was being loaded and this time logging in to the desktop was almost instantaneous. STEPS TO REPRODUCE - Problem 1. Go to Settings > Colors & Themes > Splash Screen 2. Select Breeze 3. Reboot OBSERVED RESULT After entering password, the Breeze splash shows for about 33 seconds before the desktop appears. EXPECTED RESULT Logging in should be a LOT quicker than 33 seconds. ADDITIONAL STEPS TO REPRODUCE - Problem 1. Go to Settings > Colors & Themes > Splash Screen 2. Select None 3. Reboot OBSERVED RESULT After entering password, the desktop loads almost instantaneously. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon / Plasma 6 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION There are no "new" splash screens available yet for Plasma 6, so I was unable to test other splash screens. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482082] Plasma takes an extra 33 seconds to start after entering password and logging in when choosing the Breeze Splash Screen - KDE / Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482082 --- Comment #6 from Kevin R --- (In reply to tagwerk19 from comment #1) > Run journalctl and see if you have bluetooth related failures, see Bug 481870 I initially checked to see if this was Bluetooth related, as I when I did some google searching that is all I found was people having delayed login due to Bluetooth. However I found out my problem doesn't seem to be related. I just checked journalctl again after enabling splash and rebooting and it doesn't show any unusual errors related to Bluetooth. The only error I see (which I have always seen with previous versions of Plasma) is "Bluetooth: hci0: Malformed MSFT vendor event: 0x02". So this is "normal" for me. This just seems to be the splash screen that is delaying login for some reason. I did look through the journalctl logs and was not able to find anything that could point to the delayed login. However, I don't even know what I am looking for, so someone else might be a better candidate for looking at the logs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482045] Notification sounds do not work - KDE Neon / Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482045 --- Comment #3 from Kevin R --- (In reply to guimarcalsilva from comment #1) > Can you check if they work if you install the package 'ocean-sound-theme'? > > sudo apt install ocean-sound-theme Installing ocean-sound-theme allowed the notification sounds to work, however, they only work under Colors & Themes > System Sounds. Any sounds specified under Settings > Notifications > Plasma Workspace still do not work. I still can only preview thjose default sounds. It seems like the new "System Sounds" theme is overriding the Notifications / Plasma Workspace sound notifications. -- You are receiving this mail because: You are watching all bug changes.
