Admins have been notified, don't worry - you didn't get banned, something just broke.

Errors like these when trying to login:

@Ida_ ok, now I got it - leave it on Norwegian, lock the screen, unlock and type in your passcode - will be broken. issue link

@Ida_ I just reproduced this by mistake on FP4, I wonder if it has something to do with the Norwegian one because it only happened after I enabled it to check. It also has a bit different symbol layout than English.

Ok I think I can actually pretty consistently reproduce this with the Norwegian layout.

@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.

@Vlad-Nirky afaik you can't switch during a call anyway, so if it tried it would have ended the call anyway.

@wouterx said:

Lomiri greeter: I set a numeric PIN and when opening the keyboard appears where previously a numeric keypad showed.

Not only that, but at least here (FP5) I can't change it in settings either, looks like some polkit issues (ignore the date, didn't connect to WiFi yet):

Apr 29 22:26:28 ubuntu-phablet polkitd[2091]: Identity `unix-group:admin' is not valid, ignoring: No UNIX group with name admin: Success
Apr 29 22:26:28 ubuntu-phablet systemd[1]: Starting polkit-agent-helper@2-4794-32011.service - Authorization Manager Agent Helper (PID 4794/UID 32011)...
Apr 29 22:26:28 ubuntu-phablet maliit-server[4473]: inputMethod::reset()
Apr 29 22:26:28 ubuntu-phablet maliit-server[4473]: in clear preedit.. clearing word engine
Apr 29 22:26:28 ubuntu-phablet polkit-agent-helper-1[4802]: Pidfd not supported on this platform, disable polkit-agent-helper.socket and use setuid helper
Apr 29 22:26:28 ubuntu-phablet polkitd[2091]: Operator of unix-process:4794:8093 FAILED to authenticate to gain authorization for action org.freedesktop.accounts.change-own-password for system-bus-name::1.113 [/usr/lib/aarch64-linux-gnu/lomiri-system-settings/private/Lomiri/SystemSettings/SecurityPrivacy/LomiriSecurityPrivacyHelper] (owned by unix-user:phablet)
Apr 29 22:26:28 ubuntu-phablet lomiri-system-settings[4643]: "/usr/lib/aarch64-linux-gnu/lomiri-system-settings/private/Lomiri/SystemSettings/SecurityPrivacy/LomiriSecurityPrivacyHelper" failed to run with exit status: 1
Apr 29 22:26:28 ubuntu-phablet passwd[4804]: pam_extrausers(passwd:chauthtok): unrecognized ENCRYPT_METHOD value [YESCRYPT]
Apr 29 22:26:28 ubuntu-phablet passwd[4804]: pam_extrausers(passwd:chauthtok): unrecognized ENCRYPT_METHOD value [YESCRYPT]
Apr 29 22:26:28 ubuntu-phablet passwd[4804]: pam_unix(passwd:chauthtok): user "phablet" does not exist in /etc/passwd
Apr 29 22:26:28 ubuntu-phablet systemd[1]: polkit-agent-helper@2-4794-32011.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 22:26:28 ubuntu-phablet systemd[1]: polkit-agent-helper@2-4794-32011.service: Failed with result 'exit-code'.
Apr 29 22:26:28 ubuntu-phablet systemd[1]: Failed to start polkit-agent-helper@2-4794-32011.service - Authorization Manager Agent Helper (PID 4794/UID 32011).

@pparent have you reported the issue anywhere? Not sure if anyone worked on that. Did this testing result in any logs or anything that could point us to a cause? Are these apps still using my immodules.cache hack from back in xenial?

@messayisto Use the installer, make sure none of the checkboxes are selected and install 24.04-1.x

@alagirialagiri the Android version doesn't matter here.

miatoll is on the second list for a reason - it turned out to be broken last minute and had to be disabled, the number of variants meant it took a while to verify - it will also most likely go in the RC.

merlin was updated too late to make the cut for beta, it will have to wait for RC. You can try the instructions as this device is not on either of the lists:

@peat_psuwit said:

3. Devices that are not in either of the list above. We don't have enough information to determine if they'll work on 24.04-2.x, so we need testing from you. To do so, make sure you're on a spare device, then follow the same instructions above but switch to Daily channel instead of Release Candidate channel. The possible results are:

• Your device upgrade successfully. In such case, congratulations, your device should be working with 24.04-2.x. Please report back to us, and we'll enable your device to receive 24.04-2.0 RC and 24.04-2.0, or if not possible in time, for 24.04-2.1 or subsequent releases.
• Your device fails to upgrade. In such case, please use UBports Installer to restore 24.04-1.x on your device, and then also report to us to disable updates to these devices too.

In case anyone finds this in 2026 and beyond:

NONE OF THIS IS NECESSARY SINCE FOCAL, WAYDROID COMES PREINSTALLED, YOU JUST NEED TO INITIALIZE IT

Would be nice if the post was deleted / edited though as people are still finding and trying to follow it and others like it.

@peat_psuwit do you have a spec for the Thai EBS? Looks like they require a working SIM card?

I still maintain that we'll need a CB topic database from e.g. Android and should not not rely on hardcoded set of topics from a non-regional specification.

In theory we should only need the table from 9.4.1.2.2 of 3GPP TS 23.041.

Unfortunately, the test today is inconclusive on whether we need to explicitly subscribe to topic "4370" or not.

We don't already? According to the same table, 4370 is not supposed to be settable by the user and always subscribed (I'm kind of extending the 3GPP definition of MMI here) so this shouldn't be a question - since afaik it's not required to be implemented at modem level, we should check what ofono reports and subscribe to the missing ones.

@CiberSheep the dream of Waydroid-less UT died with every bank under the sun choosing to implement PSD2 with custom apps

@pparent iirc my immodules hack won't work for Wayland, and you won't get an onscreen keyboard in Mir 1.8 because it's missing all the IME protocols.

I haven't looked at what electron-only features the signal-desktop app uses, but you could look into packaging Node.js and running the back-end parts there with a shim in WebEngine to communicate with that. Not trivial, but would give you near-perfect integration with the OS.

@pparent your store description is a bit misleading

• The application is somewhat slugish because it is not GPU-accelerated (because apparmor prevents the app from accessing the GPU)

It's sluggish because you run it under Xorg - which is your choice, not a system limitation.

• It is not possible to copy and paste text from other applications (should be solved with Mir 2.0)

It won't be solved by Mir 2 because you are running it under Xorg, and the difference with Mir 2 is that it supports the Wayland clipboard protocol.

If you are going to support ContentHub at some point, clipboard is easy and handled by the same service.

@FixOne said in It's done! KDE Connect finally works on UT:

ATTENTION! KDE Connect can only be installed via APT. Do not attempt to install it in Libertine or nix (Cracle), as it will not work or will be extremely unstable. If you are concerned that the application will break your system, you can relax (but backups are still important). Changes to the system will be minimal.

Please don't give guarantees you can't keep. Using apt will break the OS at some point, it's not the question of "if" but "when".

Your script also installs avahi and enables it unconditionally, which is a very bad idea for a mobile device that might connect to public hotspots - you should at least put a warning in your post.

@CiberSheep fyi this has nothing to do with app development.

@t12392n said in App security (new KeepassRX app):

A local Keepass should not talk to the internet.

Where did you get the idea that it does?

@arubislander said in App security (new KeepassRX app):

If the app is confined (as this one is) you don't need to blindly trust that the package in the open store was compiled by the code that is linked, to be sure it doesn't phone home. If you know what to look for, you can download the .click package and examine the contents.

All versions of OpenStore also show the permissions list and that should be the first thing people check, can't expect non-technical users to unpack clicks before installation.

Kind of related, we should probably update the popup when you install from a local .click file to show more info and definitely show permissions.

Interesting, though it needs Qt 6 afaict. Still nice, I was waiting for servo to get a bit better scores on the WPT tests before trying to run it on UT, but maybe it's worth looking into for some simpler sites.

@reeered start by restoring your device with Xiaomi's tool: https://forum.xda-developers.com/t/miflash-guide-use-xiaomi-flash-tool.4262425/