@danqo6 said in Testing the upgrade to Qt 5.12:
@dobey would love to try, but using android9 branch. Would be possible to sneak that commit there?
OK. There are a couple other differences for android9 based devices, so I had to make a couple extra branches. To use qt 5.12 on them you'll also need to add the xenial_-_qt-5-12_-_android9 repository in the apt sources, along with xenial_-_qt-5-12.
OK. With a bit of help from Ratchanan we finally found the issue that was only happening on the bq e4.5/e5 devices, and I've made a fix for libhybris in a branch for qt 5.12 as well. I also noticed that the issue with the photo editing in gallery-app was also cleared after the fix, so the issues others have been seeing on OP3T, Nexus 6p and other devices might also be related.
Please upgrade and let us know if the issues are resolved or still occur. Thanks!
@danqo6 OK. That's quite odd. Are there any apparmor complaints in /var/log/syslog when you start either of those apps?
@danqo6 Does the working version have those lines about /run/user/.... in the logs?
@danqo6 OK, that looks like a problem with apparmor on that port. Do those apps work with current devel image? It seems like it should have the same issues.
@potet said in Testing the upgrade to Qt 5.12:
Calendar & Clock: Crashes on open (both load their interfaces before crashing)
Do you have the log files for these apps for when this happens? Thanks.
@domubpkm I'm not sure what it's doing exactly, but a quick look at the code looks like it could certainly be transitioned to Morph.Web and QtWebEngine, perhaps it also needs to use webchannels or websockets for what it's doing.
@Giiba There are already other things not working in QtWebEngine which were working in Oxide that we know of; camera, mic, webgl, hw audio/video decoding, and probably a few other integration points.
However, Oxide is years old, unmaintained, and has known security holes which have been patched in newer versions of Chromium that QtWebEngine is based on. If we keep Oxide in the rootfs and people keep making webapps that use it, we'll never be able to get rid of it. We need to get it out and free up the space, and also get it removed from the realm of concern for developers.
If there are things that worked with Ubuntu.Web import when it was using Oxide, that don't when using Morph.Web with QtWebEngine, then let's get those differences documented in open issues against morph-browser on GitHub, rather than spending our time discussing it here, so appropriate people can maybe look into how those can be resolved.
If you really need a webapp using oxide, you can probably repackage a click to include the oxide components, as a temporary solution until your issues can be resolved in Morph/QtWebEngine. No, it's not ideal, but we need to move Ubuntu Touch forward, rather than to keep slowly stepping sideways with it.
@lduboeuf We are not using systemd itself on 16.04, and the kernel version requirement is a bit of a misunderstanding. This update still doesn't mean we're using systemd for the init system. However, the systemd source provides many things which we do need, such as udev.
Newer kernels are only required for some features of systemd, and newer versions of systemd may require newer kernels, hence the comments relating those two as a concern, along with the need to upgrade to 20.04.
@UniSuperBox said in Can OTA-15 be the final release including Oxide?:
Is this timeline with OTA-16 the first non-Oxide update feasible? What else do we need to consider before its removal that we can prioritize for OTA-14 and OTA-15?
Given the release schedule we're trying to keep for stable releases, I'd even say we should remove it from OTA-15 and OTA-14 could be the last one with it. It has been widely understood for a long time that oxide is deprecated and we would be removing it. If we make appropriate announcement today that it will no longer be included as of the OTA-15 release, that should be ~8 weeks if we can keep to the desired schedule.
I think that's plenty of time.
@PhoenixLandPirat said in Testing the upgrade to Qt 5.12:
I trued updating by updating to the latest ubuntu ota, then repeating the instructions at the top, I rebooted and used sudo aa-clickhook -f and it didn't work, I tried the ubuntu-qa update command and it said everything was up to date, I tried to also use sudo aa-clickhook -f and see if it worked without rebooting, but that didn't work either, so perhaps there's extra problems with the OP3 and apparmor profiles?
OK, I'm not sure what wouldn't work here. Are there apparmor denials in /var//log/syslog that happen when you attempt to open the photo editor page? Do you have a log of the gallery app?
I couldn't view a downloaded pdf in the document viewer
Yes, this is because the PDF plug-in in docviewer is using private Qt API. I've just proposed a huge change to an updated PDF plug-in that was being worked on a few years ago, which removes the private API usage, and allows PDFs to work again on Qt 5.12.
Also the camera, if I try to take a photo, I get an error saying "Capture failed, restarting your device might fix the problem." it doesn't fix the problem, but its probably apparmor issues, that might be different on the OP3, than the devices that you're debugging on, or different between arm64 and armph?
I think the OP3/3t needs a different camera app and backend, which is not yet a default part of the system, to work properly, still. I don't think this issue is related to Qt 5.12. I don't have that device, though camera is working fine on my Nexus 4.
@PhoenixLandPirat said in Testing the upgrade to Qt 5.12:
The Gallery app shows images fine, but when I go to try and edit a image to crop, it turns black and doesnt give me the option to crop.
OK. Trying to figure out what was going on here was weird, but it lead to some issues in ubuntu-ui-extras which I fixed, and then also a change in QFile::copy in newer versions of Qt apparently was resulting in apparmor denials.
After upgrading the packages, and rebuilding the apparmor profiles (this can be done by running sudo aa-clickhook -f), it should be working again (it does here).
UT does not yet have any NFC support. Also, I'm not sure if the BQ E4.5 has any NFC hardware.
@Lakotaubp I don't think that will help, as what this person wants is clearly not UT, but traditional linux distro.
@poVoq Real web push integration for the browser would indeed be the correct/best general solution for notifications here.
The bottom line is that yes, you can run a web server on your phone if you want to, but no, it's not going to work the same as running a web server on a stationary computer with a stable network connection.
Ubuntu Touch is not a traditional PC Linux distro running on a phone. It is an OS designed for phones/tablets, including with security, privacy, and power management features suited for such use.
If what you want is to use your phone like a traditional Linux distro, as essentially an expensive and less reliable Raspberry Pi server, then you are probably going to be disappointed by Ubuntu Touch, and other distributions like postmarketOS or Mobian may be more what you are looking for.
@lduboeuf Very odd. Hopefully the e4.5 arrives here soon and I can reproduce these issues with it.
@Isaac If you are using the logviewer app, be sure to set the username to something reasonable, in the settings of the app first.
@Isaac said in Testing the upgrade to Qt 5.12:
Clock & Calendar apps go down when being launched.
Calendar app is a known issue as it was using some internal API that we needed to remove with Qt 5.12 upgrade. There is a PR waiting to be merged/released which solves the issue.
For Clock app do you have a log? It is working fine here on my Nexus 4.
Thanks.
