@Fuseteam With main menu I mean the hamburger menu with the three lines.

Made some videos for some of the things.

1: Solo USB key, it's supposed to turn blue when an auth request comes to it. Idk if it needs some kind of usb permission: https://youtube.com/shorts/EIjAkhwfOOw
2. Drop down boxes in the settings page, I think this might be related to the on screen keyboard because it starts working after a menu opens: https://youtube.com/shorts/o5OpgXKtTWk
3. Broken auto complete in the url bar: This time it seems to have learned not to auto correct "about:", but backspace still autocompletes quite broken stuff: https://youtube.com/shorts/Uc5UlPfpEXg

I got Volla Quintus with Ubuntu Touch today and naturally wanted to install the latest updates straight away. But the “Ubuntu touch” “version 3” update fails.

See screenshot for error message. I think umount: /dev/block/dm-1: Invalid argument or /dev/block/dm-1 has unsupported feature(s): FEATURE_C12 will be the problem. Maybe e2fsck in the recovery/update installer is older than the one that created the the Ubuntu Touch file system?

What is the best way to solve this? Is it possible to simply deactivate the “FEATURE_C12” in the live ubuntu touch system before the update and/or does this have any negative effects? I only found that if you do it with tune2fs -O ^orphan_file the filesystem needs to be unmounted. I'm new to ubuntu touch, not sure how I would do that.

@ChromiumOS-Guy Thanks, extensions are accessible now. Form filling from the browser's saved passwords doesn't work, I guess it's because of copy&paste not working? But the bitwarden extension can fill form fields so it's good enough for me.

For my point 9. I found the privacy settings and that by default it deletes a lot of stuff on exit. Might be good to call these defaults out in the readme.

Not sure if this is for location access https://github.com/ChromiumOS-Guy/uWolf/commit/c27cf41b4b3bd9d1e84519ca0c7abe17637ac19c#diff-9f6e9f7df1d5f0a60e077fa35efd7d122e78595f3852769e59834397b9860c07R3-R5 but still only the browser itself asks for its internal location access permission, it still doesn't ask the OS. I think you should be able to test this far even without the smartphone actually being able to get a fix, right?

That reminds me that I wanted to make a MR for this: https://gitlab.com/ubports/docs/docs.ubports.com/-/merge_requests/659

i.e.:

If connecting fails with the message ::

kex_exchange_identification: read: Connection reset by peer

check the log on the UBports device ::

journalctl | grep sshd

If you see a message about missing hostkeys such as ::

sshd: no hostkeys available -- exiting.

You need to generate host keys with the following command ::

sudo ssh-keygen -A