P
Offline
@DJac Ok dés que je pourrais mettre à jour mon appareil de test vers 24.04-2.x j'esserai de voir ce qu'il se passe. Ca m'etone, ça fonctionne bien sur 24.04-1.x
Est-ce que ce problème concerne seulement blablacar ou d'autres web apps? ( Exemple: Uber, google traduction, Airbnb, Vinted, .... )
I see that they have added Signal UT to this page!
Which is nice! 
But the link "Check out on Openstore" points to Cinny? Any way to report it? Maybe @moem ?
So no bug in the end?
Hello,
I just wanted to share that I'm not a big fan of snaps in the open-store, especially how it is currently done.
Most snap apps are not currently usable on a phone screen ( scaling problem, no OSK, no integration with contentHUB, no integration with URLdispatcher, interface designed exclusively for desktop, ect...)
I think it can be a bit confusing to list them for newcomers especially because:
Some snap apps, that are not usable at all on a phone screen, often get higher in the search results than some apps developed specifically for Ubuntu Touch, that have multiple positive reviews, and match completely the search terms. Sometimes there really are a lot of snap apps, I think this can mislead completely a newcomer to test a bunch of non-working snap apps, instead of testing working apps developed specifically for UT.
There is a mention of "Snap application" but this is a small text that does not allow to distinguish rapidly and visually.
Overall I think it makes things more messy and harder to find an app that works for your need. I think overall it might give to a newcomer the image of a mostly non-functional apps store.
Example:
You type "pdf" many snaps unusable on a phone are displayed before "Annotate" or "Document Viewer"
You type "Whatsapp" many snap unusable on a phone are displayed before "Whatsnew"
Hey I tried brave browser and freetube snaps avalibale on open store they work almost flawless but since they are desktop apps they don't have on screen keyboard
Is there eny way to add on screen keyboard or a workaroun?
Maybe with Mir2.x OSK could work as it implements Wayland Input protocols ( text-input-v3 , input-method ). Not sure though.
I've released v0.1.9 with the following changes:
-Correct color of added buttons: match the change upstream
Tell me if it works well for you!
I've released V8.15.0-1 with the following changes:
-Fix keyboard closing after sending a message
-Bump to Signal-Desktop 8.15.0-1 (First to officially support arm64)
En pratique, l appli est bonnes, mais je n ai pas accès aux messages :
La boite de reception ne correspond pas au contenu de celle du site. je n y trouve que les messages 'officiels' de blablacar et aucun des messages de mes passagers.
Je serai intéressé de savoir ce que donne l'application sur UT 24.04-2.x si quelqu'un test à un moment ou à un autre! Est-ce que la messagerie fonctionne? ( Ca indiquerai que l'app bénéficie du nouveau moteur Qtwebengine 6 )
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.
Someone will look into it.
Great!
@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 did you use the restart button in system settings? If so its a bug that needs to be fixed. That button should remove everything from your system. If you remember, give me more details, I'll try to reproduce it.
Anyway the only file outside the app data/cache/config directory is a unit file in your user systemd directory, you can see it by running sysremctl --user status greenline.service
Thank you for your reply, and sorry for my late reply.
What I recall having done is disconnecting my account from the greeline menu, I dont recall the exact button name. But when opening the app it proposed me to make the association again with a whatsapp account
then I have found a solution to the problem:
rm ~/.config/systemd/user/greenline.service
The file was left on the system.
I hope to have more time later to do more testing, but right now it's a bit complicated!
Thank you for your work!
@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.
Thank you very much!
Unfortunately, at the moment, this does not help me understand what happens on 24.04-2.x
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?
Thank you! What you describe is kind of expected. Currently it seems the keyboard does not work with any XWayland app on 24.04-2.x. Normally the messages are sent by typing Enter/Return on the virtual keyboard.
I could help if you give the output when you run these adb commands, and try to open the keyboard (click on the edit area)
WARNING: this will run Signal UT in an unconfined way, only do that if you fully trust Signal UT, only for testing purposes, and run it preferably only on a testing device with no personal data rather than on your daily driver
cd /opt/click.ubuntu.com/signalut.pparent/current/
export DISPLAY=:0
export LD_LIBRARY_PATH=lib/aarch64-linux-gnu/
export MALIIT_DEBUG=1
export G_MESSAGES_DEBUG=all
./launcher.sh
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.
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.
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).
For fun I tried to replace in the launcher.sh for the piano app of @pparent the qmlscene6 (provided by the app, qt6 is packaged into the app) by the system one and it failed miserably so at the moment I think that QT6 is not available for apps, at least not in a straightforward way)
Possibly it is because you are using the qmlscene6 from the system but still the Qt6 library bundled into the app. It might not be compatible. You may try to remove the libraries form the app repository (or temporarily move them elsewhere) to see if it works better.