@libremax said: The printing system is not included in the Ubuntu Touch images due to a lack of space for the root filesystem on many device models. Work is currently underway to be able to increase the size of the rootfs. Is there a way to determine if my device (Nord N10 5G) might have enough space for larger root filesystem ?

"Hi Brenno, I'm using Greenline on a Pixel 3a (Ubuntu Touch RC). I noticed that the greenline-daemon stays active and consumes significant resources even when notifications are disabled in the app settings. On older devices, this leads to OOM (Out of Memory) crashes and system reboots. Feature Request: Could you add a 'Kill Daemon on Exit' toggle for users who don't need background notifications? If notifications are off, the daemon shouldn't stay resident in memory after closing the UI."

Thanks! I dived into the issue a bit more, and it seems like the problem lies in the default mapping in /etc/subuid file. The first OS regular user created usually has the assignment 100000:65536 in /etc/subuid. I decided to assign the values (231072:65536) from the user that succeed with the podman pull command to the user with previous 100000:65536. With the new values, podman (and therefore, clickman) runs without issues. I don't see any conflict on the default range assigned, but definitely that new assignment seems to fix it. Hope it helps for those that run into it

@PerlMax said: Hello everybody, I am trying again to develop a simple pEFL test app. In libertine everything works great. Unfortunately the app won't start outside the libertine environment. Apparently, efl needs to be able to read files in the $HOME directory and some other directories (see https://sourceforge.net/p/enlightenment/mailman/message/58751741/). My idea now is to run the app in a chroot environment. Would that be possible for a normal click app? Are there any examples of other apps that do this? Or is that not such a good idea? Thanks in advance! Max You can make the application unconfined (not recommended), or use the read_path/write_path options in the apparmor file. Or, potentially better, change the library/application to read from the UT XDG data-dirs correctly.

heads up i forgot to re-enable some of the build chains during debugging so this is broken till i post the update

@brenno.almeida welcome

@oldbutndy yes that is the desktop version .....i desperately want to give you something to test but the ut version is still just too broken im going for EXACTLY the same thing in both desktop and UT versions ....that is not easy as you would think ...i promise soon i will have something for you ...im actually excited your excited

this one i really could use some feedback on as this is one of my favorite projects as well as a staple tool that is intended to make UT more useful ....there are many bugs i know ....i cant figure them out and neither can AI .... until i get more information im basically over here eating my own tail on this project

@domubpkm to handle imported files differently in messaging app, would be a task to solve there. tedit can only hand over a file to messaging app. What that does with the file is defined there. tedit has no control over that. I added the share option to read only mode page too. I simply didn't think of that yet. (Build here: https://gitlab.com/Danfro/tedit/-/jobs/14268879889/artifacts/file/build/aarch64-linux-gnu/app/tedit.danfro_3.6.1_arm64.click)

No, no change. I'll open an issue; that'll be more efficient. I've started the French translation on Weblate.

@pparent Many tries later - with a failed speechmessage too - unexpected: sending a picture works fine up to now. Later I will send you a screencast of the failed picture insert before. Btw: installing the screencast App failed... AppStore always returns to the green "installieren" button!

@domubpkm Well, if my calculation is correct that means about 2Mbits/s, it seems quite decent for Bluetooth.

but yeah alot of all this is very "fresh" so expect bugs ....i know for a fact this apps jitsi meet function is still a little borked ...ill get to it eventually

@projectmoon thanks for the feedback! Auto sync: currently UT does not have a way for apps to run background jobs, an unconfined app is required. Not planned right now due to the maintenance overhead, but maybe in the future! Sharing: yeah, the app has no sharing features, its something I plan to implement soon Slowness: strange, Ill see if I can enhance the optional debug logs to better understand this and other issues that some people report with their servers Gallery: seems a limitation with the gallery app, from the file manager you can send videos and multiple files Infinite scroll: Unfortunately this being my first UT app I did the gallery in a non optimal way and now a big refactor is needed to have this. Maybe something for the future