It's Qt 5.12 time.
-
It's been a long time coming, but we're finally merging Qt 5.12 into Ubuntu Touch.
This is a process that will take a few days. During that time, updates to the
develchannel of Ubuntu Touch will be pinned to an older rootfs release. Changes to Android compatibility images will be shipped, but changes to packages in the system will not.So, you will still see updates available on some devices (like the Nexus 5, Volla Phone...) but not on others (Bq E5, E4.5...). Don't be alarmed!
This is only a notification, no action is needed on your part.
-
And PLEASE avoid doing any upgrade on your devices with apt if you were doing that at any point, until further notice. Your device will almost certainly break currently if you do, requiring you to flash again with the installer.
Thanks!
-
@dobey ubports-qa is concerned?
-
@lduboeuf Yes, as it attempts to do an upgrade which pulls in other packages. It should not be used currently either.
-
@dobey maybe a post on ubports-qa and dev Telegram group is needed
-
@dobey Is
crossbuildersafe? -
@jezek Not for building against Ubuntu Touch. Anything using the Ubuntu Touch apt repositories will be problematic until Qt 5.12 transition is done.
-
@dobey Ok, I will stop using
crossbuilderfor deployment to phone, cause it uses apt repositories, for a while. Will look forward for a notification when it's safe. Thanks. -
Will there be a quick guide for qt app developers on what has changed and suggestions on how to updated your apps?
-
@povoq with latest Clickable you can test your app in Desktop Mode with
CLICKABLE_QT_VERSION=5.12 clickable desktop. That env var works for debugging on device as well, given you got Qt 5.12 installed there. -
OK. All the necessary PRs have been merged (there will still be more fixes to come as well though). We should have new
develchannel images available for updating your devices soon.Anyone who used
ubports-qato test thexenial_-_qt-5-12and related branches should reset their devices by flashing again with the installer, or switching torcchannel in settings to get a full flash. Those branches are no longer valid. There's still a little rebase work needed for mainline and possibly android9 devices, but should be done soon. -
@dobey Is it pushed already?
Not sure if related, but the 196 update on my OnePlus3 just failed to install and now I am stuck at the boot logo with a broken install (error seems to have been: "couldn't load bitmap icon_error (error -7)" which is also shown in the ubports recovery now).
-
@povoq Yes. It seems like maybe some delta images were messed up somehow (unrelated to Qt 5.12 itself).
Can you flash the device again with the installer?
-
Dekko2 seems to be partially broken with 5.12? Notifications still come in, but launching it results in a white screen only on my phone.
-
@povoq Might be wrong, but I think that that is an issue that Dekko developers have to fix?
There are a few extra issues with the OnePlus 3 also, such as the camera, and lack of message bubbles in the messaging app.
-
@phoenixlandpirat Yeah I guess. I wish Dekko2 was treated a bit more like a core app, as it really is more or less one.
Fairphone 5 (waiting for port)
-
@povoq There are several core apps that don't have maintainers that don't get updates, or only once in a blue moon, unfortunately.
-
@povoq They were made away of the issue at the same time as Teleports (which has been fixed). Dekko is using qbs and doing a few things a little differently though, so I'm not sure how to correctly update the quickflux dep there.
-
Anyone also noticed that forcing the screen to stay on seems to have stopped working? At least on Puremaps the navigation is broken because of the screen turning off after a short while.
Fairphone 5 (waiting for port)
-
The issue on splash screen seems to be back or is that something that developers has to adjust? My apps use SVG and they are displayed small unlike before.
