No touch KB after update(forky)

[biketool]

Like the title says, I ran apt dist-upgrade and now I get no automatic touch keyboard on any app.
I checked that the touch virtual keyboard was enabled in the mobile settings, holding the line on the bottom just caused it to wiggle left and right like a failed login box in some distros.
It will probably be back in a day or two though I don't like being without and would like an easy way to force the touch keyboard.

[zetabeta]

Like the title says, I ran apt dist-upgrade and now I get no automatic touch keyboard on any app.
I checked that the touch virtual keyboard was enabled in the mobile settings, holding the line on the bottom just caused it to wiggle left and right like a failed login box in some distros.
It will probably be back in a day or two though I don't like being without and would like an easy way to force the touch keyboard.

i put some inaccurate info at this point.

probably phosh is switching from squeekboard into stevia. change probably confuses phosh somehow. package name is "phosh-osk-stevia", mobian package may have some differences with debian package.

[biketool]

(snip)

i put some inaccurate info at this point.

probably phosh is switching from squeekboard into stevia. change probably confuses phosh somehow. package name is "phosh-osk-stevia", mobian package may have some differences with debian package.

OK so if I recall correctly I had removed stevia KB last year as it interfered with the great squeekboard terminal keyboard, installed stevia and am rebooting now...

Not working, I am reading my way through https://manpages.debian.org/testing/phos....1.en.html
https://gitlab.gnome.org/World/Phosh/ste....48_alpha1
________________________________________________________________
also https://github.com/droidian/squeekboard
https://world.pages.gitlab.gnome.org/Phosh/squeekboard/
___________________________________________________________
tried:
In order to be used by Phosh as OSK, phosh-osk-stevia needs to be started from the /usr/share/applications/sm.puri.OSK0.desktop desktop file. On Debian systems this can be achieved by running

update-alternatives --config Phosh-OSK

as root and selecting the entry ending in sm.puri.Phosh.Stevia.desktop.
______________________________________________________________
For the keyboard to fold and unfold automatically make sure org.gnome.desktop.interface gtk-im-module is set to the empty string (''). This is the default in most distributions. If unsure check via:

gsettings get org.gnome.desktop.interface gtk-im-module
____________________________________________________________
gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled true
_______________________________________________________________
busctl call --user sm.puri.OSK0 /sm/puri/OSK0 sm.puri.OSK0 SetVisible b true
________________________________________________________________

none of these got me any kind of virtual keyboard; not stevia, not squeekboard......
______________________________________________________________
tried purge deleting stevia and squeekboard (be careful squeekboard reinstalls when uninstalling stevia as it is a dep for stevia)then installing squeekboard
_____________________________________________________________
still nothing......
____________________________________________________________
tried(now we only have squeekboard newly installed after and apt purge)
gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled true
got back
(process:1987): dconf-WARNING **: xx:xx:xx:xxx: failed to commit changes to dconf: Cannot autolaunch D-Bus without X11 $DISPLAY
_________________________________________________________
in settings "Screen Keyboard" is toggled to ON
________________________________________________________
there is a mess where purge removing squeekboard ends up installing phosh-osk-stevia package and it's deps
________________________________________________________
I am going to have to leave my phone at home and go out with my nokia candybar, this will probably require reimaging back to my 2 week old pre trixie-->forky upgrade as I need a keyboard. This is where I really get angry about my PineKB being stolen and now you cant order them anymore!

[biketool]

So I loaded the snapshot image from a few weeks ago immediately before I transitioned from Trixie to Forky.
But now how to keep this from happening again,
I want to be running on Forky,
who else is,
do you still have your KB?
It takes four hours to load the snapshot over USB(unlock calmares and mount the EMMC then use the disk utility to restore the .img file) so I can't do that every time I run into a problem.
__________________
One thing I do know is that I had removed stevia to get back my favored squeekkeyboard terminal keyboard long before the trixie to forky transation, and I had no problems for a few weeks on forky so still.... mystery....