Testing the upgrade to Qt 5.12

lduboeuf

@dobey said in Testing the upgrade to Qt 5.12:

The app crashed? Or the shell? Sfxr seems to work mostly fine on my Nexus 4, though I have noticed a couple issues with the app itself (and I think unrelated to Qt 5.12).

Yes the app crashed. What do you mean by shell, Lomiri crash and reboot ?

dobey

@lduboeuf Yes.

danqo6

@dobey I made fix for missing images in checkindicator and spinbox, look https://github.com/ubports/qqc2-suru-style/pull/48/files

CiberSheep

@dobey said in Testing the upgrade to Qt 5.12:

Otherwise though, is your rootfs full? Did you already install some other things extra in it perhaps from Ubuntu archive?

I'll install a fresh image and try again to be sure

lduboeuf

@dobey

So, sfxr, messaging-app, teleports still crashes on BQ4.5, drawer icon number columns are fine now. Splash screen icon is shrinked:

kugiigi

I tried this on my Nexus 5. Here are my observations (some might have been reported already). Note that I don't have a sim card inserted so that might also a factor in some of these. Also, I used this as my daily driver before so it has plenty of data and may represent an upgrade from an actual daily driver device.

Splash image is not displayed correctly
App drawer only has 2 columns which was 3 before
Phone app and Fluffy Chat crashed when triggering the bottom edge
Messaging app opens fine but if you open a thread, the messages are jumbled and not displayed correctly
Calculator app opens but seems to fail to actually initialize so it's not interactive/working
Clock and Calendar app opens but crashes after a few seconds (I have google and NC calendars synced)
Contacts app works fine but dragging the bottom edge only shows the header until the drag is completed.
Dekko 2 and TELEports are blank. I have accounts configured.
PDFs are blank in Document viewer except in slideshow mode. Libreoffice files crashes the app.
Double-tapping in the OSK (cursor mover mode) is quite difficult to trigger.
It seems that Qt 5.12 is a bit less forgiving in codes like for example with layouts. My app Palitan has many warning logs and also there are some UIs not displayed which probably caused by those errors/warnings.
I also see Type error errors in JS in some apps. Probably related to the known issues with JavaScript which I believe was already discussed somewhere.
Honestly, expected a noticeable improvement in the performance but so far it's almost the same and I feel like I actually see more micro stutters but not sure though if I'm observing it right

dobey

@kugiigi said in Testing the upgrade to Qt 5.12:

Splash image is not displayed correctly

This should also be the case in stable/devel already, given the source, but fix is inbound in the 5.12 branch.

App drawer only has 2 columns which was 3 before

Fix already in.

Contacts app works fine but dragging the bottom edge only shows the header until the drag is completed.

Fixed now.

Double-tapping in the OSK (cursor mover mode) is quite difficult to trigger.

Seems to be mostly fine here on my Nexus 4, but it seems to get "stuck" after a while, and I don't see anything in the maliit-server log.

It seems that Qt 5.12 is a bit less forgiving in codes like for example with layouts. My app Palitan has many warning logs and also there are some UIs not displayed which probably caused by those errors/warnings.

Yes, in general it is a bit stricter. You'll need to fix your app.

I also see Type error errors in JS in some apps. Probably related to the known issues with JavaScript which I believe was already discussed somewhere.

There seems to be a few things that can cause this, but those apps will need to be fixed individually.

dobey

@lduboeuf said in Testing the upgrade to Qt 5.12:

So, sfxr, messaging-app, teleports still crashes on BQ4.5,

Can you get stack traces? I don't have an e4.5 and they are starting fine here on my nexus 4.

Thanks.

CiberSheep

@dobey said in Testing the upgrade to Qt 5.12:

@kugiigi said in Testing the upgrade to Qt 5.12:

Splash image is not displayed correctly

This should also be the case in stable/devel already, given the source, but fix is inbound in the 5.12 branch.

He might refer to
dev vs

Qt5.12

dobey

@CiberSheep said in Testing the upgrade to Qt 5.12:

He might refer to

Yes. I meant, I don't understand why this doesn't happen in dev, because the Splash.qml was specifying the source size as the same dimensions of the screen. But as I also said, it's fixed now on 5.12 branch too (well building currently).

CiberSheep

@dobey I see.
Also to note, if no splash screen is used, the app icon is shown correctly

kugiigi

@dobey Let us know when we can do an update and retest stuffs

lduboeuf

@dobey said in Testing the upgrade to Qt 5.12:

Can you get stack traces?

Which one ?. App logs don't have nothing. I can give the unity8.log but i think it is the same as my initial reply for the sfxr crash. Will do tomorrow if needed
https://paste.ubuntu.com/p/khrnt9xc2R/

danqo6

@dobey I am still getting one missing column in portrait on OnePlus 3T (getting 3, should 4), in landscape it is fixed now.

dobey

@lduboeuf I mean, if it's actually crashing, to get a stack trace you need to use gdb. I think you can do clickable debug now to debug remotely.

kugiigi

Updates after retesting:

Splash image in core apps look good now but it seems that the dimension logic is still different than the current one. My apps that use SVG splash images looks small like it's almost the same size as the icon (i.e. Palitan, Fluffy Chat). They should be displayed bigger.
Contacts bottom edge is working properly now.

Others not mentioned are still the same

CiberSheep

Today I have:

installed RC image (from System Settings)
removed some old apps
installed Dev image
Installed the updagrade

I got this warning before installing it:

Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libqgsttools-p1 libqt5multimediaquick-p5 qtdeclarative5-accounts-plugin
  qtdeclarative5-folderlistmodel-plugin qtdeclarative5-localstorage-plugin
  qtdeclarative5-online-accounts-client0.1 qtdeclarative5-particles-plugin
  qtdeclarative5-qtcontacts-plugin qtdeclarative5-qtorganizer-plugin
  qtdeclarative5-qtquick2-plugin qtdeclarative5-ubuntu-mediascanner0.1
  qtdeclarative5-ubuntu-settings-components qtdeclarative5-window-plugin
  qtdeclarative5-xmllistmodel-plugin
Use 'sudo apt autoremove' to remove them.

and this after installing:

The following packages will be REMOVED:
  libqgsttools-p1 libqt5multimediaquick-p5 qtdeclarative5-accounts-plugin
  qtdeclarative5-folderlistmodel-plugin qtdeclarative5-localstorage-plugin
  qtdeclarative5-online-accounts-client0.1 qtdeclarative5-particles-plugin
  qtdeclarative5-qtcontacts-plugin qtdeclarative5-qtorganizer-plugin
  qtdeclarative5-qtquick2-plugin qtdeclarative5-ubuntu-mediascanner0.1
  qtdeclarative5-ubuntu-settings-components qtdeclarative5-window-plugin
  qtdeclarative5-xmllistmodel-plugin
0 upgraded, 0 newly installed, 14 to remove and 0 not upgraded.
After this operation, 845 kB disk space will be freed.
Do you want to continue? [Y/n]

(I say no)
Full log: https://paste.ubuntu.com/p/ZfZdpz3MqF/

CiberSheep

I have been testing some apps:
Work:

OpenStore
Dialer
Address Book
Camera
Gallery
UTTT
System Settings
Linphone

Crash after splash:

Calendar
Calculator
Weather
Clock

I did a test with a clickable create qml app. Unconfined opens, confined crashed on start

The only difference when doing clickable logs is:
confined:
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'

unconfined:

Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
Creating a QMirClientScreen now

dobey

@CiberSheep That is not a warning, and it is correct behavior. Those packages will not be in the rootfs any more, after Qt 5.12 lands.

danqo6

I found an another issue: apps are unable to save settings, settings are not saved after app restart. Settings from .config folder are loaded fine. Happens with Podbird, OpenStore, Quickddit and more
Found in log from QQC2 Gallery app:

file:///opt/click.ubuntu.com/qqc2-gallery.ubad/1.0.7/qml/Main.qml:67:5: QML Settings: Failed to initialize QSettings instance. Status code is: 1