[kwin] [Bug 470185] Maximized windows not covering entire screen in some circumstances

https://bugs.kde.org/show_bug.cgi?id=470185 --- Comment #7 from Aaron Kelley <09_strays_fli...@icloud.com> --- > ...on Wayland? On Wayland it seems to maximize and properly cover the entire screen. > ...if you make your panel always visible? If the panel is always visible (and on th

[plasma-pa] [Bug 391578] Have kded or plasmashell handle volume-related keyboard shortcuts so they don't stop working when all Audio Volume applet/widget instances are removed

https://bugs.kde.org/show_bug.cgi?id=391578 Aaron Kelley <09_strays_fli...@icloud.com> changed: What|Removed |Added CC||09_stra

[kwin] [Bug 470185] Maximized windows not covering entire screen in some circumstances

https://bugs.kde.org/show_bug.cgi?id=470185 --- Comment #5 from Aaron Kelley <09_strays_fli...@icloud.com> --- Poking around a bit more. If I take the bottom panel out of autohide, I get a one-pixel space ABOVE the panel and BELOW the maximized window. If I move the panel to the right s

[kwin] [Bug 470185] Maximized windows not covering entire screen in some circumstances

https://bugs.kde.org/show_bug.cgi?id=470185 --- Comment #4 from Aaron Kelley <09_strays_fli...@icloud.com> --- I set scaling to 200% through Settings → Display and Monitor → Display Configuration → Global scale. It does not look like the PLASMA_USE_QT_SCALING environment variable is

[kwin] [Bug 470185] Maximized windows not covering entire screen in some circumstances

https://bugs.kde.org/show_bug.cgi?id=470185 Aaron Kelley <09_strays_fli...@icloud.com> changed: What|Removed |Added Resolution|WAITINGF

[kwin] [Bug 470185] New: Maximized windows not covering entire screen in some circumstances

https://bugs.kde.org/show_bug.cgi?id=470185 Bug ID: 470185 Summary: Maximized windows not covering entire screen in some circumstances Classification: Plasma Product: kwin Version: 5.27.5 Platform: Kubuntu

[kscreenlocker] [Bug 469951] With fingerprint login, odd behaviors if you do not perform a scan promptly

https://bugs.kde.org/show_bug.cgi?id=469951 --- Comment #3 from Aaron Kelley <09_strays_fli...@icloud.com> --- (As a note for anyone who may look into this. libpam-fprintd documentation suggests that setting "-1" for an "unlimited" timeout is allowed, but that is *a

[kscreenlocker] [Bug 469951] With fingerprint login, odd behaviors if you do not perform a scan promptly

https://bugs.kde.org/show_bug.cgi?id=469951 --- Comment #2 from Aaron Kelley <09_strays_fli...@icloud.com> --- I would suggest that kscreenlocker should just go with whatever timeout PAM is configured to use. Since PAM is used in more places than just kscreenlocker, it isn't really K

[kscreenlocker] [Bug 469951] New: With fingerprint login, odd behaviors if you do not perform a scan promptly

https://bugs.kde.org/show_bug.cgi?id=469951 Bug ID: 469951 Summary: With fingerprint login, odd behaviors if you do not perform a scan promptly Classification: Plasma Product: kscreenlocker Version: git-stable-Plasma/5.27