Don Fredl's Circus

@fredldotme
424 Followers
75 Following
606 Posts
Phone & tablet whisperer at UBports and Halium. Hobby prophet. FLOS software developer. Now with double the flavor. He/him
Websitehttps://fredl.me
LocationVienna, Austria
gl4es was special because the fix was made by ptitSeb from box64 fame, on his FP5.

Another thing brewing: I pushed changes to ship Vulkan from libhybris and gl4es for X11 acceleration. A good compromise in terms of hardware support on Ubuntu Touch.

This will be released via the hybris-2404 snap. If you require software rendering in your app you can switch it to mesa-2404 like:

sudo snap disconnect the-snap-at-hand:gpu-2404
sudo snap connect the-snap-at-hand:gpu-2404 mesa-2404

Finalizing search, installation and removal of Snaps from within the OpenStore app

- Now it lists both Clicks & Snaps in the "Installed Apps" tab
- GNOME Mahjongg

Guía para idiotas sobre el nuevo #Banksy
USB-C display out works after some changes, but HWC seems to gets stuck when unplugging #ubuntutouch #ubports #pixel9a #mobilelinux

Also I see "... the Camera app hangs for ~1 minute until the audio permission dialog pops up. Afterwards, video records fine in 4k, but the recording is missing audio."

I work on trust-prompts at the moment and would like to know more. I guess it does that because the default DBus timeout in Qt is 45s IIRC.

Over the weekend I also worked on integrating permissions for Wayland, XWayland and Snap applications. These now pop up and open right up and can be viewed/edited later on in System Settings.

For Snaps, note that we don't use the snapd policy module (so plugging & unplugging audio permissions using `snap connect` & `snap disconnect` doesn't work), but our own trust-store module in PulseAudio instead.

Could this be your desktop too? @ubports #lomiri #ubuntutouch
I will die on this hill.

I have some news about upgrading Ubuntu Touch's display stack from Mir 1.x to Mir 2.x. We will, according to current plans, ship a mixed environment where the system compositor (the thing that handles the screen) will run with Mir 1 where as the user's shell would run Mir 2, both connected over a nested Wayland session.

One major roadblock has been tackled and that is "Trust Prompts" permission dialogs, allowing to host the same permission UX as with Mir 1. Watch it in action here!