SUMMARY volume +/- and changing KB layout rarely now shows the OSD popup STEPS TO REPRODUCE 1. Change KB layout with hotkey or increase/decrease volume OBSERVED RESULT no OSD popup to indicate the change EXPECTED RESULT OSD to show correctly as in plasma 5 Operating System: EndeavourOS KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.6.1-x64v3-xanmod1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 | NVIDIA-SMI 545.29.02 Driver Version: 545.29.02 CUDA Version: 12.3 |
Run `journalctl -f` and try to change volume/layout, is there any output which happens there? Does it also happen in X11, or is this Wayland-specific?
Works 100% for me. Intel CPU+GPU, 200% scale.
Here is journalctl -f: "ное 18 06:29:58 kodatarule plasmashell[1142]: kpipewire_logging: cannot convert spa format to fourcc 10 ное 18 06:30:13 kodatarule rtkit-daemon[949]: Supervising 10 threads of 5 processes of 1 users. ное 18 06:30:13 kodatarule rtkit-daemon[949]: Supervising 10 threads of 5 processes of 1 users. ное 18 06:30:38 kodatarule kwin_wayland[1024]: QString::arg: 2 argument(s) missing in org.kde.konsole ное 18 06:30:38 kodatarule systemd[966]: Started Konsole - Terminal. ное 18 06:30:38 kodatarule konsole[120264]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11 ное 18 06:30:38 kodatarule plasmashell[1142]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11 ное 18 06:30:38 kodatarule plasmashell[1142]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11 ное 18 06:30:38 kodatarule plasmashell[1142]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11 ное 18 06:30:38 kodatarule plasmashell[1142]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11" Nothing showed up - OSD and when I increased/decreased the journal remained the same, any other way I can debug this ?
I'm having this problem for the volume OSD in Wayland on Plasma 6 RC1 on Arch Linux (EndeavourOS kde-unstable). The volume changes, but the OSD does not work/show. Operating System: EndeavourOS KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.7.0 Kernel Version: 6.6.10-arch1-1-surface (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Microsoft Corporation Product Name: Surface Pro 8
Can you check "Show visual feedback for changes to:" settings in System Setting / Sound / Configure Volume Controls...?
I checked. All of the entries are checked, but still no volume OSD.
Can you run plasmashell with WAYLAND_DEBUG=1, press volume keys and attach the log to the bug report?
Can you also test if kcmshell6 qtquicksettings and setting the renderloop to basic fixes it. We have seen similar issues on nvidia that should be fixed by default with 6.6.2
(In reply to David Edmundson from comment #8) > Can you also test if kcmshell6 qtquicksettings and setting the renderloop to > basic fixes it. > > We have seen similar issues on nvidia that should be fixed by default with > 6.6.2 Setting the render loop to basic did not fix the issue.
(In reply to Vlad Zahorodnii from comment #7) > Can you run plasmashell with WAYLAND_DEBUG=1, press volume keys and attach > the log to the bug report? I'm going to need some help on exactly how to do this one and save the log. I ran WAYLAND_DEBUG=1 plasmashell --replace >> log.txt, but the output is not saving to the file. What should I do?
Hmm, that should work. You can also omit the ">> log.txt" part to see if it prints to the terminal window
(In reply to Nate Graham from comment #11) > Hmm, that should work. You can also omit the ">> log.txt" part to see if it > prints to the terminal window It prints to a terminal window. How do I save the output to a file, or where is the file the output is being saved to?
Copy and paste it, or else use the "Save Output As..." menu item in the hamburger menu or the file menu.
(In reply to kelnio@yahoo.com from comment #10) > (In reply to Vlad Zahorodnii from comment #7) > > Can you run plasmashell with WAYLAND_DEBUG=1, press volume keys and attach > > the log to the bug report? > > I'm going to need some help on exactly how to do this one and save the log. > I ran WAYLAND_DEBUG=1 plasmashell --replace >> log.txt, but the output is > not saving to the file. What should I do? Debug output is printed to stderr, not stdout. To redirect that use: WAYLAND_DEBUG=1 plasmashell --replace 2>> log.txt
Created attachment 165012 [details] Log text for volume up/down Ok, I ran WAYLAND_DEBUG=1 plasmashell --replace 2>> log.txt, then pressed the volume up and volume down key several times for about 10 seconds, then logged out. I can hear the volume changing notification each time but the OSD did not appear. The log.txt file is attached.
Thanks for the info!
(In reply to kelnio@yahoo.com from comment #15) > Created attachment 165012 [details] > Log text for volume up/down > > Ok, I ran WAYLAND_DEBUG=1 plasmashell --replace 2>> log.txt, then pressed > the volume up and volume down key several times for about 10 seconds, then > logged out. I can hear the volume changing notification each time but the > OSD did not appear. The log.txt file is attached. plasmashell didn't create any osd window so there's nothing for create to display. What was the window with size 759x577?
(In reply to Vlad Zahorodnii from comment #17) > (In reply to kelnio@yahoo.com from comment #15) > > Created attachment 165012 [details] > > Log text for volume up/down > > > > Ok, I ran WAYLAND_DEBUG=1 plasmashell --replace 2>> log.txt, then pressed > > the volume up and volume down key several times for about 10 seconds, then > > logged out. I can hear the volume changing notification each time but the > > OSD did not appear. The log.txt file is attached. > > plasmashell didn't create any osd window so there's nothing for create to > display. What was the window with size 759x577? That was Konsole. So any idea why the volume OSD is not displaying? Could I be missing a package?
> That was Konsole. So any idea why the volume OSD is not displaying? Could I be missing a package? I don't know. Can't answer as it's not really kwin issue.
*** Bug 481687 has been marked as a duplicate of this bug. ***