10000 KDE lockscreen: onscreen keyboard doesn't show up · Issue #5600 · getsolus/packages · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

KDE lockscreen: onscreen keyboard doesn't show up #5600

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
1 of 2 tasks
Qronikarz opened this issue May 8, 2025 · 10 comments
Open
1 of 2 tasks

KDE lockscreen: onscreen keyboard doesn't show up #5600

Qronikarz opened this issue May 8, 2025 · 10 comments
Labels
Bug Something isn't working Packaging Problem Building the package as-is fails ("FTBFS"), or other problem with the packaging of software
Milestone
Solus 4.8 Epoch

Comments

@Qronikarz
Copy link
Qronikarz commented May 8, 2025 •
edited
Loading

Please confirm there isn't an open report for this issue

  • I have searched through bug reports

Summary

"Onscreen keyboard" button doesn't do anything in the lockscreen of Solus KDE Plasma. It isn't a big deal on desktop where you always have access to normal keyboard, but laptops with detachable keyboard may not always have physical keyboard. That's why it is important that the onscreen keyboard works so users can log in.

Not only does it not work on default Solus install, but also installing Mallit keyboard and choosing it in Plasma settings still doesn't make it work. "onscreen keyboard" button in the bottom left corner remains useless.

(tested on a PC and a laptop)

Steps to reproduce

  1. Power on the PC or lock it if it's already powered on
  2. Click on "onscreen keyboard" (or smth like that) in the bottom left corner

Expected result

Onscreen keyboard shows up

Actual result

Onscreen keyboard doesn't show up

Environment

  • Is system up to date?

Repo

Shannon (stable)

Desktop Environment

Plasma

System details

Operating System: Solus 4.7
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.3
Kernel Version: 6.12.23-317.current (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-3470 CPU @ 3.20GHz
Memory: 7.7 GiB of RAM
Graphics Processor: AMD Radeon RX 570 Series

Other comments

Forgot to add, but when I was testing Nobara KDE few months ago, the onscreen keyboard worked so it is possible.
@Qronikarz Qronikarz added the Bug Something isn't working label May 8, 2025
@github-project-automation github-project-automation bot moved this to Triage in Solus May 8, 2025
@TraceyC77 TraceyC77 moved this from Triage to Needs More Info in Solus May 12, 2025
@TraceyC77
Copy link
Contributor

Can you test this with a live USB of another distribution? This likely is a bug in KDE and not in our packaging of it. Testing with another distro will help us determine that. Thanks.

@Qronikarz
Copy link
Author
Qronikarz commented May 13, 2025 •
edited
Loading

garuda-mokka-linux-zen-250308
Plasma 6.3.
It worked, but I noticed that it somehow booted to X11 on live USB so I switched to Wayland and it stopped working.

Nobara-41-Official-2024-12-31
Plasma 6.2.
Booted automatically into Wayland and the onscreen keyboard didn't work. Which is weird because I am certain that I used Wayland and onscreen keyboard was working since it was required on a touchscreen laptop without keyboard.

Nvm. I have tested a new Nobara iso.

Nobara-42-Official-2025-05-13
Plasma 6.3
Booted into Wayland on live USB. For some reason it set up the fractional scaling to 145% instead of 175% (but that doesn't matter here) after I clicked on log out (don't click switch user because it crashes all 3 ISOs - nobara and garuda) the onscreen keyboard showed up and was working.
Here more info from Nobara settings:

Operating System: Nobara Linux 42
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.6-200.nobara.fc42.x86_64 (64-bit)
Graphics Platform: Wayland

So there are some differences.

@TraceyC77
Copy link
Contributor

There is an upstream issue on the KDE bug tracker about maliit not working with the lock screen. What virtual keyboard does Nobara-42 have installed?

@Qronikarz
Copy link
Author

Maliit is pretty much the only virtual keyboard that I know about that works in Wayland.

Nobara 42 mallit:

bash-5.2$ rpm -qa | grep maliit
maliit-framework-2.3.0-9.fc42.x86_64
maliit-framework-qt5-2.3.0-9.fc42.x86_64
maliit-keyboard-2.3.1-10.fc42.x86_64

I also checked Solus after today's sync and it still doesn't work. Maybe it's because maliit was installed by default on Nobara and I had to install it manually on Solus 4.7 KDE + choose it in settings.

@TraceyC77
Copy link
Contributor

Thanks for the extra details. I did a little more digging and found that Nobara does install Maliit, and does some configuration to make the VK work on their distro.

The root cause is this upstream bug, I've verified this on my system. The "Virtual Keyboard" button does not respond to clicks, it only responds to a touch. There's an aging patch to fix this that still has to be merged. I've poked them about this in that report.

Does the system you're using this on have a touch screen? Does the virtual keyboard show up if you tap on the Virtual Keyboard button? It does on my touchscreen laptop.

A potential workaround is to edit ~/.config/kwinrc, in the section [Wayland] add this line

VirtualKeyboardEnabled=true

and then reboot

@TraceyC77
Copy link
Contributor
TraceyC77 commented May 18, 2025 •
edited
Loading

From the point of view of Solus mitigating this for our users, I think we should look at what Nobara did.

  • Enable maliit by default
  • Make it work with both mouse and touch

This is aligned with our goal for improving the user experience on 2-in-1 devices

@TraceyC77 TraceyC77 added the Packaging Problem Building the package as-is fails ("FTBFS"), or other problem with the packaging of software label May 18, 2025
@EbonJaeger
Copy link
Member

Do you still have the links to what Nobara does regarding configuration?

@Qronikarz
Copy link
Author

Does the system you're using this on have a touch screen? Does the virtual keyboard show up if you tap on the Virtual Keyboard button? It does on my touchscreen laptop.

Ok. So I might overcomplicate it, but here we go.

Device that I need virtual keyboard on is Surface Go (so a detachable laptop which means you don't need the keyboard). The PC from my main report doesn't need virtual keyboard because it always has it keyboard near.

When I made this report both computers were behaving the same (not weird since they have nearly exactly the same configuration and packages) - "virtual keyboard" button never worked and it only moved the lockscreen above when you clicked it. Surface also has maliit installed but it behaved the same way. (note: Solus 4.7 KDE didn't have the maliit installed by default)

Now, after last Friday's updates I noticed that there is one instance where the virtual keyboard shows up on the lockscreen, but I need to explain more.

So Solus KDE for me currently has these states when it comes to unlocking it:

  1. disk encrypted by luks on boot - a black terminal with password prompt. My PC uses this method with autologin so I only need to input one password on boot.
  2. password login on boot - KDE lockscreen with no fractional scaling. I need to use this on Surface Go, because it can work without keyboard since it has a touchscreen (but virtual keyboard doesn't work right now). Ideally I would like to use method from point 1. with autologin, but I never even saw a linux whole disk encryption that had a working touchscreen keyboard to input the password
  3. locked after login - shows when you lock it manually or it locks automatically. It uses fractional scaling and has the exact behaviour that you described - when touching the button, the virtual keyboard shows up. When you use touchpad it just moves the lockscreen up.
  4. logged out after login - same situation as point 2.
  5. switched user after login - same situation as point 2.
  6. sleep after login - same situation as point 3.
  7. hibernate after login - same situation as point 3.

Well that's a long reply. I could write even longer review of Solus on this device (I encountered some things that I don't know where to report), but there's no place for it like in Mint's GitHub discussions (they have laptop review section there). And I don't want to make a forum account.

Anyway, back to the topic. I read that Plasma 6.5 will have a revamped login manager which might get rid of point 2. which I hope for.
https://blog.davidedmundson.co.uk/blog/a-roadmap-for-a-modern-plasma-login-manager/
It still leaves the topic of whole disk encryption, but that's not the point of this issue report.

So tl;dr I agree:

  1. Add maliit keyboard to Solus KDE default packages
  2. Set it up

@TraceyC77 TraceyC77 moved this from Needs More Info to Ready in Solus May 18, 2025
@TraceyC77 TraceyC77 added this to the Solus 4.8 Epoch milestone May 18, 2025
@TraceyC77
Copy link
Contributor

Do you still have the links to what Nobara does regarding configuration?

I had just done a brief search on their repo and found this, mostly those are for setting up the ISO. I don't know if / how they're patching the package to make it work with mouse clicks.

@TraceyC77
Copy link
Contributor

@Qronikarz , thanks for detailing your use cases. This is good information for us as we consider our implementation of the maliit install and configuration.

"virtual keyboard" button never worked and it only moved the lockscreen above when you clicked it

I saw this as well on a Lenovo Flex 2-in-1 with Plasma built from git-master

cc: @ReillyBrogan as one of our Plasma maintainers, who also has a Surface to test with.

Sign up for free to jo 503D in this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Something isn't working Packaging Problem Building the package as-is fails ("FTBFS"), or other problem with the packaging of software
Projects
Solus
Status: Ready
Milestone
Solus 4.8 Epoch
Development

No branches or pull requests
3 participants
@EbonJaeger @TraceyC77 @Qronikarz
0