[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 Matthew Adie changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #12 from Matthew Adie --- It's working properly now. Thanks! Matthew -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 --- Comment #11 from Matthew Adie --- (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 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #10 from Nate Graham --- Matthew, can you try again with Plasma 5.25.5 (or 2.6, which will be released in about a month)? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 Benjamin Hennion changed: What|Removed |Added Ever confirmed|1 |0 Status|CONFIRMED |REPORTED --- Comment #9 from Benjamin Hennion --- 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. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 --- Comment #8 from Benjamin Hennion --- (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. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 Benjamin Hennion changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||benjamin.henn...@wanadoo.fr --- Comment #7 from Benjamin Hennion --- 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. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 --- Comment #6 from Aleix Pol --- 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 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 Nate Graham changed: What|Removed |Added CC||aleix...@kde.org Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 --- Comment #5 from Matthew Adie --- 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. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 --- Comment #4 from Matthew Adie --- Created attachment 146836 --> https://bugs.kde.org/attachment.cgi?id=146836=edit 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. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 Nate Graham changed: What|Removed |Added Severity|normal |crash CC||n...@kde.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Nate Graham --- I suspect it's crashing in the background. Can you use the `coredumpctl --reverse` command-line tool to look for maliit-related crashes? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 Matthew Adie changed: What|Removed |Added Version|5.24.0 |5.24.1 --- Comment #2 from Matthew Adie --- 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. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450256] 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 it .
https://bugs.kde.org/show_bug.cgi?id=450256 --- Comment #1 from Matthew Adie --- 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. -- You are receiving this mail because: You are watching all bug changes.
