Ubuntu Touch 24.04-2.0 call for testing

pparent

@messayisto said:

Min Broeser is crashing after it started,

@messayisto
Side note: the latest version of Min browser should not crash anymore on 24.04-2.x. (But most probably the OSK will not work anymore, like on other XWayland apps).

Luksus

I've updated my post:
https://forums.ubports.com/post/96809

For camera:
I forgot, that I was running an experimental build of the camera app , sorry ... with the regular one, everything is working.

Video playback:
is working again, though I am not sure what solved it. I can't imagine that it has something to do, with the camera app.
But while investigating, I accidentally deleted all of my .config and .local files , so that may also be the cause of fixing it.

Same goes for Morph... the strange behavior on opening links from other apps is gone.

gpatel-fr

@pparent said:

the latest version of Min browser should not crash anymore on 24.04-2.x. (But most probably the OSK will not work anymore, like on other XWayland apps)

min starts on 26.02 build 104. Log: minlog.txt

the repeated lines at the end were happening when I was tapping in the URL bar.

pparent

@gpatel-fr said:

min starts on 26.02 build 104. Log: minlog.txt

the repeated lines at the end were happening when I was tapping in the URL bar.

It starts but not OSK right?

I see on your logs and on the logs of @equareo that line:

qml: Application requested te be focused but no window for it. What should we do?

So I think your hypothesis might be right! Given that a patch was added in Maliit to "Verify an application has focus before granting it input", it seems possible that the XWayland windows are not detected correctly in Lomiri as giving the focus to the app and therefore block the virtual keyboard. This is only an hypothesis but seems very possible.

https://gitlab.com/ubports/development/core/packaging/maliit-framework/-/commit/5a767263a7d82b6194ad4c7f8548e8895bfb5d47

https://gitlab.com/ubports/development/core/packaging/maliit-framework/-/commit/6bd655621fea66af7b9bb3a477b9de072b4939db

It makes me think as well that on the left panel we still have the X icon instead of the app icon, which seems a bit strange to me as the window does now have the right icon under it, on the spread view. But it might be another sign that the XWayland apps might never really get the focus, from Lomiri standpoint.

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:

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.