Hello all, I’ve been using KDE Plasma for about a year now and loved the software. But over time a collection of bugs in KDE software have piled up, and I figured it was about time I become a part of the community and try to get them squashed.
I understand that
bugs.kde.org is the correct place to file bug reports, but there’s a myriad of subsystems and sections and I’m unaware where any of the bugs I’ve found would fit within them. So I’m posting them all here to hopefully try and get them to in front of the correct maintainers. After that I’m happy to investigate further with their help.
All of the following bugs are under this system:
Operating System: Arch Linux
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.5.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 PRO 5850U with Radeon Graphics
Memory: 22.3 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Product Name: 20XK001AUS
System Version: ThinkPad T14 Gen 2a
Bug: Krita fractional scaling is disabled
I actually did file this one on
bugs.kde.org, but it seems like it got buried, so I’m reposting it here to hopefully try and dig it up. Krita has an option to enable fractional scaling, but it’s greyed out and cannot be clicked on. I dug through the source code and couldn’t figure out what was missing to enable it. Here’s my original bug report.
Bug/User Error?: Lock screen breaks when entering sleep mode without unlocking
If I exit sleep mode, by pressing the power button, opening the laptop lid or by any other means, if I put the system to sleep (by pressing the “sleep mode” button, closing the lid or by any other means) before unlocking the system, when I next wake the system the lock screen ignores all attempts to unlock.
In particular, it appears to be responsive, but attempts to unlock via fingerprint have no response, and although the password field can be typed in, pressing the enter key or clicking on the on-screen “enter” button have no response. The sleep and switch user buttons remain functional.
Sometimes switching to a TTY, logging in, and typing
loginctl unlock-session is enough to kick it back to life, but other times my session is completely lost.
I suspect that this could be due to my PAM configuration, however the faulty behavior didn’t appear until a few months ago so it might be a regression. I spent quite a lot of time trying to get lock screen with fingerprint working since it does not work out of the box at least on Arch. I eventually cobbled together this config:
[factsphere ~]$ cat /etc/pam.d/sddm #%PAM-1.0 auth [success=1 new_authtok_reqd=1 default=ignore] pam_unix.so try_first_pass likeauth nullok auth sufficient pam_fprintd.so auth include system-login -auth optional pam_gnome_keyring.so -auth optional pam_kwallet5.so account include system-login password include system-login -password optional pam_gnome_keyring.so use_authtok session optional pam_keyinit.so force revoke session include system-login -session optional pam_gnome_keyring.so auto_start -session optional pam_kwallet5.so auto_start
Bug/User Error?: Lock screen randomly does not allow fingerprint login
Sometimes I am not presented with the option to unlock with my fingerprint at all.
Bug: The power button does not behave correctly at the lock screen
This one at least is known… And has been for over five years. It drives me nuts. I’d like to bring some more attention to it. The issue is that the lock screen does not honor the action the power button should take— so you can use the power button to wake the system, but you can’t use it to put it back to sleep!
Bug: Caps Lock key mapped to Backspace works correctly on Wayland apps but not on XWayland apps
This isn’t a KDE bug, but I experience it while using KDE software so I feel it’s worth bringing up.
A bug somewhere in the X server prevents the “Caps Lock key is Backspace” setting (Found in Settings → Keyboard → Advanced → Caps lock behavior) from repeating backspace entries. So if an app is running under XWayland, it cannot interpret my backspace entries correctly. This has been known for at least 11 years now and it seems that no progress has been made tracking it down.
These aren’t the greatest bug reports, but it’s my first time in this community and you have to start somewhere. Help me make these reports better and as a result make KDE better!