SUMMARY If the virtual keyboard was disabled before logging out or rebooting then when logging back in again the on screen keyboard will not appear after enabling the virtual keyboard . STEPS TO REPRODUCE 1) upgrade to Plasma 5.24.0 2) make sure the virtual keyboard is disabled 3) log out or reboot 4) log in 4) enable the virtual keyboard 5) the onscreen keyboard (Maliit) does not appear when entering a text area However, it works properly under the following conditions: 1) enable the virtual keyboard and leave it enabled 2) Log out or reboot 3) log in 4) the onscreen keyboard appears like normal OBSERVED RESULT The onscreen keyboard doesn't appear after enabling the virtual keyboard if the virtual keyboard had been disabled before the previous logout or reboot. EXPECTED RESULT The onscreen keyboard should always work after enabling the virtual keyboard. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION Everything worked normally before upgrading to Plasma 5.24.0 -- I had originally submitted bug 449962: https://bugs.kde.org/show_bug.cgi?id=449962
I'm sorry, not it's not working at all again -- the behavior I reported in this bug was occurring consistently this morning, however, now I cannot get the onscreen keyboard to appear at all again.
I just upgraded to 5.24.1 Operating System: Arch Linux KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Sometimes I can get the Onscreen Keyboard (maliit-keyboard) to appear (normally I try using Kate or Konsole), but it's inconsistent... Sometimes the procedure I first outlined in the bug works to make the Onscreen Keyboard appear (and it will do so repeatedly for a while), but then sometimes the Onscreen Keyboard won't appear regardless of what I try.
I suspect it's crashing in the background. Can you use the `coredumpctl --reverse` command-line tool to look for maliit-related crashes?
Created attachment 146836 [details] Output of coredumpctl --reverse I've attached the output of coredumpctl -- reverse, and there doesn't seem to be any sign of a maliit related crash.
It's behaving consistently now. So long as the Virtual Keyboard is enabled when I log out, it works properly on my next login. However, if it was disabled when I last logged out it won't work when I enable it.
I just tested and couldn't reproduce. This is what I tested: - get the keyboard (maliit) active, go on a text field: shows ✅ - deactivate the keyboard on the plasmoid: doesn't show ✅ - log out - log back in: doesn't show, it's still deactivated ✅ - activate the keyboard on the plasmoid, go on a text field: shows ✅ I tested it on kwin master
I can reproduce this with Plasma 5.25.5 Wayland and Maliit 2.3.0, on Arch, following exactly the steps @Matthiew Adie gave. I can also add the following observation: after logging out and back in while the virtual keyboard is disabled (so it does not work anymore, even after trying to reenable it), launching a maliit-server brings the virtual keyboard back. Of course, killing the maliit-server breaks the virtual keyboard again. I assume that when it works nominally, the maliit-server is run through its dbus service, right? So there may be an issue with the handling of this service.
(In reply to Benjamin Hennion from comment #7) > I can reproduce this with Plasma 5.25.5 Wayland and Maliit 2.3.0, on Arch, > following exactly the steps @Matthiew Adie gave. Actually, like in @Matthew Adie's case, the behaviour is quite inconsistent. It seems it sometimes works, and sometimes doesn't. I'll use it for a couple of days and report if I find any sort of pattern.
I cannot reproduce this anymore. It may be that my testing protocol was not precise enough, and that https://bugs.kde.org/show_bug.cgi?id=458998 was the actual source of the problem for me. I think it is safe to disregard my previous messages on this ticket.
Matthew, can you try again with Plasma 5.25.5 (or 2.6, which will be released in about a month)? Thanks!
(In reply to Nate Graham from comment #10) > Matthew, can you try again with Plasma 5.25.5 (or 2.6, which will be > released in about a month)? Thanks! I tested it again 5.25.5 and my problem seems to be resolved. I'll loop back and check again when 5.26 comes out. Thanks for all the hard work :) Matthew
It's working properly now. Thanks! Matthew