SUMMARY KDE's popups (usually referred to as visual feedback in System Settings) do not show under KDE 6 Plasma Beta 1. These popups can be from system volume changes or display brightness changes. STEPS TO REPRODUCE 1. Open the Sound KCM in System Settings and ensure all the 'Show visual feedback for changes to...' checkboxes are checked. 2. Attempt to change the volume from anywhere, whether it be using the key bind or scrolling on the volume indicator in the System Tray. OBSERVED RESULT The 'ding' sound effect from changing the volume plays in the background, however no visual feedback is presented. EXPECTED RESULT The popup does not show as it would normally do in KDE Plasma 5. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.3-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2 Manufacturer: ASUS
Whoops, my brain failed. Correction: EXPECTED RESULT The popup *should* show as it would normally do in KDE Plasma 5.
Can't reproduce on Arch beta 1. Could you provide complete system logs when this happened? Thanks!
Created attachment 163880 [details] My first log from SDDM start to attempting to invoke OSD Sure, here's the log, attached as log-1.txt. Here's my testing procedure: 1. Stop SDDM 2. Switch to TTY3, run `sudo systemctl start sddm && journalctl -f -n 0 | tee log-1.txt` 3. Log in and attempt to invoke OSD by changing system volume with hotkeys
I notice kunifiedpush-di segfaulting in that log. I assume this is a different issue and thus should be reported separately as that's related to push notifications and not the OSD? I do not know much about how KDE is structured - but that should be handled over dbus, no?
I also noticed > Dec 04 19:52:16 the-overcooler plasmashell[13130]: kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running. which doesn't seem good. How did you install plasma 6 beta 1? From the kde-unstable repo? You also need to enable the testing repos if you do that. What theme are you using? Could you try using the default themes (breeze)? I noticed this in the log: > Dec 04 19:52:17 the-overcooler plasmashell[13130]: kf.svg: The theme "spectrum-classic-basic" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. > I notice kunifiedpush-di segfaulting in that log. I assume this is a different issue and thus should be reported separately as that's related to push notifications and not the OSD? I do not know much about how KDE is structured - but that should be handled over dbus, no? Yeah I think that should be a separate issue. It might also be a downstream packaging issue.
(In reply to fanzhuyifan from comment #5) > How did you install plasma 6 beta 1? From the kde-unstable repo? > You also need to enable the testing repos if you do that. Yes, I installed Plasma 6 through the kde-unstable repository. I did not know I needed the testing repositories also enabled; I feel as if the documentation on ArchWiki could be a bit more clear on this, as I feel like I did a fair bit of research before switching (but I understand that's not KDE's problem). Do I just need the extra-testing repository or the core-testing repository enabled as well? > What theme are you using? Could you try using the default themes (breeze)? I > noticed this in the log: > > Dec 04 19:52:17 the-overcooler plasmashell[13130]: kf.svg: The theme "spectrum-classic-basic" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. I'm using the 'Genome' / 'Spectrum' themes found in the theme store. They seem to work fine since I only really use the color palettes from the theme but I'll switch to stock Breeze and report back to you.
Created attachment 163884 [details] My desktop after selecting the 'Breeze' theme Okay, switching to Breeze technically 'fixed' the issue after a restart of Plasma, but this brought up an even stranger issue. Upon loading into the desktop, I tested the volume controls and the OSD did indeed come up. However, I noticed that the layout is seemingly broken. Attached is a screenshot of my desktop with this broken layout. Upon further investigation, I discovered that there is no 'Breeze' theme under Plasma Style. Infact, no Plasma Style was selected. Setting one caused the layout problems to fix themselves but that also means I'm using the old Spectrum Classic layout that's apparently causing problems. Interestingly, though, the OSD still works despite that.
Created attachment 163885 [details] My fixed desktop after applying a Plasma Style Here's a screenshot showing my Plasma Styles and the layout I would expect.
(In reply to jvyden from comment #6) > Yes, I installed Plasma 6 through the kde-unstable repository. I did not > know I needed the testing repositories also enabled; I feel as if the > documentation on ArchWiki could be a bit more clear on this, as I feel like > I did a fair bit of research before switching (but I understand that's not > KDE's problem). It is in the big red warning here: https://wiki.archlinux.org/title/Official_repositories#Testing_repositories > Upon further investigation, I discovered that there is no 'Breeze' theme under Plasma Style. Infact, no Plasma Style was selected. Setting one caused the layout problems to fix themselves but that also means I'm using the old Spectrum Classic layout that's apparently causing problems. Interestingly, though, the OSD still works despite that. That sounds very much a downstream packaging issue. There definitely should Breeze and Breeze Dark styles. Closing this as this is a downstream issue. Happy to help you on the arch forums, though.
(In reply to fanzhuyifan from comment #9) > It is in the big red warning here: > https://wiki.archlinux.org/title/Official_repositories#Testing_repositories Whoops, that's embarrassing, haha. I've installed the testing repositories and updated but the issue still persists. > Closing this as this is a downstream issue. Happy to help you on the arch forums, though. Sure, I made a thread on the Testing subforum: https://bbs.archlinux.org/viewtopic.php?pid=2135335#p2135335