Offline
" Il est également interdit d’utiliser l’application France identité sur un ordiphone Rooté ou Jailbreaké."
“It is also prohibited to use the France Identité app on a rooted or jailbroken smartphone.”
https://france-identite.gouv.fr/conditions-generales-utilisation/
I guess it currently does not work on rooted Android, and on custom Roms, and obviously on Waydroid.
If there is any plan to open a Spanish section, I can in Spanish as well! 
Just for the record, it seems I see a lot less the problem these days. I've experienced it again once or twice but it is rare.
My guess is that it was related to an heavy use of messagers apps ( Signal, Whatsapp, Telegram ) during the holiday seasons, and a lot of photo sending and receiving. Given the memory leak problem that we have discovered ( I think I should report it to the camera app anyway).
From my current understanding, there is some special code in the xWayland server inside UT, that automatically resize the windows to the size of the screen. In the case of a menu window, this obviously create problems.
I guess there must be exceptions for certain types of windows, or when the window has certain properties. For exemple I see the the gtk filedialogs windows in gtk do not get resized fullscreen.
It is possible that the menu windows in uWolf have different property that prevent the system from resizing them.
I will investigate that, I guess if i find a property that prevent the system from resizing the windows, I could add it to the window very fast with a script, and prevent the system from interfering.
Ok I think I can make use of the device, thank you very much! (and in any case if I don't need it anymore one day, or you need it again, I can always send it back to you.) I send you a PM.
In an ideal world Signal would provide an API for external webpush server, as telegram does, and we don't need to keep an app open ususpended to receive notifications.
From what I know all the gtk/XWayland apps are affected. Something was probably changed in the system concerning maliit. ( Chromium for UT, Min browser, Signal UT, uWolf, Rocket.chat, ect... )
For now I cannot test 24.04-2.x, maybe later. Probably system devs should know more about that problem, and what may have been changed in regard to OSK and maliit.
Well if I run the xev from the Min browser in the terminal from the phone screen, somehow it gets killed while I navigate in the Min Browser. So I indeed cannot see the same log, but the cause seems to be totally different, simply that xev is not running anymore.
Anyway it seems better to me to run xev directly from adb/ssh as I showed before.
Yes but did you try to reproduce with the method I posted above?
I can't reproduce yours because xev is not installed by default in the system. I guess you have installed it.
This is very strange, just tu make sure I explain the process:
1- I start The Min Browser.
2- I open an adb shell session and I do the following:
phablet@ubuntu-phablet:~$ if [ "$DISPLAY" = "" ]; then
i=0
while [ -e "/tmp/.X11-unix/X$i" ] ; do
i=$(( i + 1 ))
done
i=$(( i - 1 ))
display=":$i"
export DISPLAY=$display
fi
cd /opt/click.ubuntu.com/min.pparent/current
export LD_LIBRARY_PATH=lib/aarch64-linux-gnu/
bin/xev -root
3- I try to open the top left hand corner menu, and exactly at that time I see the following log appear in the shell
CreateNotify event, serial 18, synthetic NO, window 0x3ef,
parent 0x3ef, window 0x600013, (-53,66), width 1189, height 1433
border_width 0, override YES
MapNotify event, serial 18, synthetic NO, window 0x3ef,
event 0x3ef, window 0x600013, override YES
ConfigureNotify event, serial 18, synthetic NO, window 0x3ef,
event 0x3ef, window 0x600013, (-54,302), width 1189, height 1433,
border_width 0, above 0x800003, override YES
PropertyNotify event, serial 18, synthetic NO, window 0x3ef,
atom 0x111 (_NET_ACTIVE_WINDOW), time 9737872, state PropertyNewValue
FocusOut event, serial 18, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyNonlinearVirtual
FocusIn event, serial 18, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyDetailNone
KeymapNotify event, serial 18, synthetic NO, window 0x0,
keys: 130 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ConfigureNotify event, serial 18, synthetic NO, window 0x3ef,
event 0x3ef, window 0x600004, (0,0), width 1080, height 2277,
border_width 0, above 0x600013, override NO
PropertyNotify event, serial 18, synthetic NO, window 0x3ef,
atom 0x111 (_NET_ACTIVE_WINDOW), time 9737873, state PropertyNewValue
ConfigureNotify event, serial 18, synthetic NO, window 0x3ef,
event 0x3ef, window 0x600013, (-54,302), width 1189, height 1433,
border_width 0, above 0x600004, override YES
ConfigureNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x600013, (-54,302), width 1080, height 2277,
border_width 0, above 0x600004, override YES
UnmapNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x600013, from_configure NO
UnmapNotify event, serial 19, synthetic YES, window 0x3ef,
event 0x3ef, window 0x600013, from_configure NO
DestroyNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x600013
PropertyNotify event, serial 19, synthetic NO, window 0x3ef,
atom 0x111 (_NET_ACTIVE_WINDOW), time 9737927, state PropertyNewValue
FocusOut event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyDetailNone
FocusIn event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyNonlinearVirtual
KeymapNotify event, serial 19, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
@gpatel-fr said in XWayland: Menu windows resized full screen and crash?:
are you sure that the messages you see are coming from the menu ? What I tried is to redirect the output of xev to a file that I examined by tailing it from ssh. When the menu opened and did its particular dance, I saw nothing on my screen.
From my understanding, the window created when opening a menu is not rooted, so it's not seen when using xev -root (err, warning here, I am decidedly no X window expert)
Yes I'm sure that the window corresponding to the menu appears in xev, and in xdotools for a second. are you sure you have the exported the correct DISPLAY ? Everything seems to show that the window is instantaneously resized which is not normal for a menu window.
the window created when opening a menu is not rooted
What do you mean not rooted?
Apart of that, I have no idea on the uWolf mystery and it's indeed baffling. The only far fetched hypothesis that I can think is that this difference is not coming from the packaging but from the underlying code base (ie, Firefox vs Chrome) is not using Gtk in the same way.
Or that they have found a workaround to make it work? @chromiumos-guy @fuseteam ?
Anyone? Any info about that would of tremendous use for all Wayland/gtk apps ( Chromium UT, Min browser, Signal UT, Rocket.Chat )
@o.o. For the record, with Signal UT it's now possible to send and receive messages, photos, and audios in Signal UT without Waydroid, and to get standard UT notifications when a new message arrives even when the phone is locked.
Thank you very much for proposing, I currently have on top of my main phone:
*An old vollaphone (with broken screen, and I have datas on my waydroid session there that for now I would not like to relfash it for that reason)
*A pine-phone, that I wonder if I could use to try in-development versions (24.04.2)
*My old Nexus 5 that was my first UT device but completely outdated! 
What are you proposing?
@domubpkm said in French ID app interoperability.:
@DJac For that, I don't believe it. Community too small. No point wasting development and maintenance resources.
I do not agree:
First because interoperability is a legal requirement for public services, especially those supposed to be universal like ID. And they replied to me that they agreed on the goal of interoperability, were sorry about the issue, and were looking for solutions. ( https://eur-lex.europa.eu/eli/reg/2024/903/oj/eng )
Second because the french gouvernement is currently actively trying to reduce its dependency to foreign company (see above), in this case Apple, and Google who would have monopoly over a strategic state function as vital as identity, if this were to become a central way to verify identity.
Third because they don't need to develop a solution specific for Ubuntu Touch: they can release an App based on Qt framework, that with principally the same code will work on Windows, Mac, Linux Desktop, Android, iOS, and all Linux Mobile distributions (Ubuntu Touch, Mobian, postmarkeOs, SailfishOs, ect...); or even they can make a progressive webapp that nowadays can be compatible with NFC and will be universally compatible.
If we feel defeated before we even start the fight, or even send a short email, we will probably not go very far.
Edit: "The first step for institutions to think about it would be for the OS to be distributed pre-installed on a large scale. " -> On the other hand they will probably not do that because the state does not like this role to have direct influance on markets and choices of consumers.
Well I guess this type of gouvernemental organization will not be interested in individual feedback of individual, but it is consulting some associations, so with a lot of luck fondations like Ubports might have a word to say.
By the way, following the recent positions of the American government, the French government has launched its council for technological sovereignty ("Observatoire de la souveraineté numérique"). It might really be an opportunity for us to argue against the duopoly in the mobile world that happen to be American, and especially to argue for the public services to be inclusive with alternatives that offer sovereignty at all levels, including individual. It seems to be a period when there is an opening for change, so maybe we should take advantage of this.
Notifications are available in version v7.86.0-1 !
In order to get notifications you need to keep the application opened. Somehow you don't need to un-suspend the application in Ubuntu Tweaks, it seems the Xwayland apps are not suspended by the system. So note it might affect a bit battery life.
Next version will focus on corrections of main remaining bugs or things that display not well in the UI, because not adapted to responsive design ( left menu, search message, medias of a group ), and if possible fix bugs with contentHub.
Hello,
I would like to ask a question about the following behaviour.
In various Gtk/Xwayland apps ( in Chormium for UT, Signal UT, Min Browser, Rocket.Chat) when a secondary X window is opened (like menu window or overlay window), and I see it gets immediatly resized full screen (which is not normal). Then it bothers it and it closes immediately. This is kind of problematic.
My questions is:
1- Is there a lomiri deamon that resize automatically new XWayland windows to fullscreen
2- Is it possible to disable this behaviour, or at least for certain windows?
3- I see that in uWolf the problem does not happen how come? @fuseteam any idea?
Here are the X logs for example when I open the menu of the Min browser:
bin/xev -root
CreateNotify event, serial 18, synthetic NO, window 0x3ef,
parent 0x3ef, window 0x800013, (-53,66), width 829, height 1433
border_width 0, override YES
MapNotify event, serial 18, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013, override YES
ConfigureNotify event, serial 18, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013, (125,302), width 829, height 1433,
border_width 0, above 0xe00003, override YES
ClientMessage event, serial 18, synthetic YES, window 0x800013,
message_type 0x111 (_NET_ACTIVE_WINDOW), format 32
PropertyNotify event, serial 19, synthetic NO, window 0x3ef,
atom 0x111 (_NET_ACTIVE_WINDOW), time 635893, state PropertyNewValue
FocusOut event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyPointer
FocusOut event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyPointerRoot
FocusIn event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyDetailNone
KeymapNotify event, serial 19, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ConfigureNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800004, (0,0), width 1080, height 2277,
border_width 0, above 0x800013, override NO
PropertyNotify event, serial 19, synthetic NO, window 0x3ef,
atom 0x111 (_NET_ACTIVE_WINDOW), time 635897, state PropertyNewValue
ConfigureNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013, (125,302), width 829, height 1433,
border_width 0, above 0x800004, override YES
ConfigureNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013, (125,302), width 1080, height 2277,
border_width 0, above 0x800004, override YES
UnmapNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013, from_configure NO
UnmapNotify event, serial 19, synthetic YES, window 0x3ef,
event 0x3ef, window 0x800013, from_configure NO
DestroyNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013
PropertyNotify event, serial 19, synthetic NO, window 0x3ef,
atom 0x111 (_NET_ACTIVE_WINDOW), time 635961, state PropertyNewValue
FocusOut event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyDetailNone
FocusIn event, serial 19, synthetic NO, window 0x3ef,
mode NotifyNormal, detail NotifyNonlinearVirtual
KeymapNotify event, serial 19, synthetic NO, window 0x0,
keys: 157 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
(We see that we have a fullscreen resize here: ConfigureNotify event, serial 19, synthetic NO, window 0x3ef,
event 0x3ef, window 0x800013, (125,302), width 1080, height 2277,
border_width 0, above 0x800004, override YES )
Anyway in the long run we will hopefully switch to Wayland when Mir2.x is included in the system, and then the OSK will be handled differently that it currently is. Not sure whether the 24.04.2 branch will include Mir2.x .
@developer said in "Are we mainstream-ready yet?":
Was wondering whether it could make sense to publish a table or roadmap outlining the exact features, services and improvements that are missing to match the Android/iOS user experience. This would help potential users, as well as developers to identify quickly where to help, and possibly also funders, who could more easily understand viability.
I would say that the issue with that is that "the Android/iOS user experience" means very different things for different users, depending on how they use their phone. Some might use Android/iOS, only use some very basic phone features that have been covered for long by Ubuntu Touch, while someone might rely on this very niche Application available on Android/iOS and consider it as and an essential basic tool, while only a small minority use it. (And many different users might use different niche applications)
Some people will tolerate without problem some feature being slightly less efficient than in Andoid/iOS because they don't spend much time on their phone or use some feature very regularly, while this might be a problem for someone who use the phone intensively to loose even 1s when doing some operations.
I think all this is very subjective.
(As I've never used Android/iOS I cannot really compare anyway)