Ubuntu Touch 24.04-2.0 call for testing

messayisto

@pparent exactly, not crashing anymore, but no keyboard.

projectmoon

I think the keyboard thing is definitely something that needs to be fixed before July.

Ida_

@klh I tried reporting it with my limited knowledge of the components involved, I may have used some wrong words to describe the problem and/or reported it in the wrong place. https://gitlab.com/ubports/development/core/packaging/qt6-base/-/work_items/2

pparent

@klh said:

immodules.cache hack

Here is an interesting test that can be done to see if the bug is specific to the use of immodules.cache or not. It is possible to start a QML app in XWayland mode.

Here is an example on how to do it with "Maps exporter", but it can be adapted with any QML app: You can enter those commands in abd or in the terminal

WARNING: this will run the app unconfined, only do that with an app that you fully trust, only for testing purposes, and run it preferably only on a testing device with no personal data rather than on your daily driver

export QT_QPA_PLATFORM=xcb
export DISPLAY=:0
export QT_SCALE_FACTOR=2 
export QT_IM_MODULE=maliit
cd /opt/click.ubuntu.com/mapsexporter.pparent/current/
qmlscene app/Main.qml

What I observe on 24.04-1.x is that the application starts in XWayland mode and the On-Screen-Keyboard do work, but sometimes it works only after refocusing on the window: by switching to another windows and going back, or by locking and unlocking the phone.(This points once again towards something working wierdly with the focus detection of XWayland windows)

It would be extremely interesting to know how this behaves on 24.04-2.x, if someone can test. Can we get the OSK with a QML app sarted in XWayland mode (with the above commands)?

Also I'm wondering if on existing XWayland apps ( like uWolf, or Min browser or Signal UT ) refocusing on the window ( by switching to another windows and going back, or by locking and unlocking the phone ) could possibly allow to have the OSK appear again in 24.04-2.x , in any way shape or form?

@messayisto @gpatel-fr @equareo @ida_ ?

Ida_

Also I'm wondering if on existing XWayland apps ( like uWolf, or Min browser or Signal UT ) refocusing on the window ( by switching to another windows and going back, or by locking and unlocking the phone ) could possibly allow to have the OSK appear again in 24.04-2.x , in any way shape or form?

I've tried leaving Signal UT open right after clicking the message box while locking and opening the screen again, this does not trigger the OSK. I have also tried switching between Signal UT and various apps like Morph, Cinny, Music Recognition, but no OSK unfortunately.

Ida_

@pparent I tried your little experiment with Maps Exporter. The app launched in an x11 window, and the OSK was gone! This was a fresh install for me as I don't use Google Maps, but I verified that the OSK worked first when I launched it as a click the usual way by pressing the icon.

I really really hope we can find a solution to this that can be included in 2.0.

pparent

@Ida_ said:

@pparent I tried your little experiment with Maps Exporter. The app launched in an x11 window, and the OSK was gone! This was a fresh install for me as I don't use Google Maps, but I verified that the OSK worked first when I launched it as a click the usual way by pressing the icon.

Ok so when you launch "Maps exporter" it in XWayland mode with the commands above you have no keyboard. Can you confirm it still is the case after refocusing on the XWayland window created by the adb/terminal commands ( by switching to another windows and going back, or by locking and unlocking the phone )?

@ida_ Thank you very much!

@klh said:
immodules.cache hack

It seems to show that the bug is not specific to the "immodules.cache" configuration or even to maliit-inputcontext-gtk, but concerns any XWayland window using maliit.

Ida_

@pparent Switching windows or locking/unlocking does not trigger the keyboard here either. Here is the output, in case it is relevant: https://pastebin.com/CG7sJg7T

klh

@pparent maybe inform the people you are asking to run random commands that this will run said app unconfined.

Launching apps outside lomiri-app-launch is not going to help debug things, you are introducing a whole lot of additional uncertainties. I asked about immodules to know where to look, not assuming it's the reason.

Someone will look into it.

@ida_ thanks! Looks like it was missed in the packaging repos. You can generally file things in https://gitlab.com/ubports/development/ubuntu-touch/-/work_items if you are unsure where to put them.

pparent

@klh said:

@pparent maybe inform the people you are asking to run random commands that this will run said app unconfined.

I've added a warning notice on my previous posts. Thank you for reporting!

pparent

@klh said:

Launching apps outside lomiri-app-launch is not going to help debug things, you are introducing a whole lot of additional uncertainties. I asked about immodules to know where to look, not assuming it's the reason.

Then we can always create a .click that will launch and XWayland Qml app. I suspect it will be the same result, but it could be tested to be sure.

@klh said:

Someone will look into it.

Great!

Nick

I can confirm the on screen keyboard doesn't show inside of Xwayland apps.
Tested in Whatsnew, the app runs fine, but no on screen keyboard ever appears when tapping any text input field.

domubpkm

@pparent You asked to @naz.r why he use XWayland on Mererhyvo and no problem with the virtual keyboard with 24.04-2.x.

pparent

@domubpkm said:

@pparent You asked to @naz.r why he use XWayland on Mererhyvo and no problem with the virtual keyboard with 24.04-2.x.

Cos he implemented his own keyboard inside the app, and never has used the Ubuntu Touch Keyboard in the first place!

domubpkm

@pparent Exact