The camera-app is crashing!

Markatrafik

Very strange. The library is in the system

/usr/lib/aarch64-linux-gnu/libubuntu_application_api_touch_mirclient.so.3.0.0

exists, but the new version of camera-app can't link the symbol in it

How can I restore previous, working version of the application?

kugiigi

@markatrafik Which device do you have? It's working on my Nexus 5.

Markatrafik

@kugiigi Xaomi Redmi Note 7

How is it possible that the compiled library has the same index:
*.so.3.0.0
but they are linked differently, what kind of practice is this?

Keneda

@kugiigi I think he's on redmi Note 7, with a GSI 9 port.

So maybe if last camera update use QT 5.12, and GSI 9 port doesn't have QT 5.12...

stanwood

@keneda I confirm new camera update works on RN7 Lavender with official port.

Keneda

@stanwood
Yes it works on my MX4 too.

Keneda

Here it goes : https://gitlab.com/ubports/apps/camera-app/-/issues/167

Markatrafik

@keneda ubports_GSI_installer_v10.zip

$ dpkg -l | grep libqt5core
ii libqt5core5a:arm64 5.9.5+dfsg-0ubports3 arm64 Qt 5 core module

Why doesn't the installer in the interface keep track of this and kill the application as a result?

~$ ldd /userdata/system-data/opt/click.ubuntu.com/com.ubuntu.camera/3.2.3/camera-app
linux-vdso.so.1 =>  (0x00000072f54c8000)
libQt5Gui.so.5 => /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5 (0x00000072f501a000)
libstdc++.so.6 => /usr/lib/aarch64-linux-gnu/libstdc++.so.6 (0x00000072f4e8b000)
libQt5Qml.so.5 => /usr/lib/aarch64-linux-gnu/libQt5Qml.so.5 (0x00000072f4aec000)
libQt5Core.so.5 => /usr/lib/aarch64-linux-gnu/libQt5Core.so.5 (0x00000072f45ae000)
libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 (0x00000072f458d000)
libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x00000072f4447000)
        /lib/ld-linux-aarch64.so.1 (0x00000072f549d000)
libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x00000072f441b000)
libGLESv2.so.2 => /usr/lib/aarch64-linux-gnu/libhybris-egl/libGLESv2.so.2 (0x00000072f43f4000)
libpng12.so.0 => /lib/aarch64-linux-gnu/libpng12.so.0 (0x00000072f43c5000)
libharfbuzz.so.0 => /usr/lib/aarch64-linux-gnu/libharfbuzz.so.0 (0x00000072f4362000)
libz.so.1 => /lib/aarch64-linux-gnu/libz.so.1 (0x00000072f433b000)
libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x00000072f428e000)
libQt5Network.so.5 => /usr/lib/aarch64-linux-gnu/libQt5Network.so.5 (0x00000072f410c000)
libicui18n.so.55 => /usr/lib/aarch64-linux-gnu/libicui18n.so.55 (0x00000072f3e9f000)
libicuuc.so.55 => /usr/lib/aarch64-linux-gnu/libicuuc.so.55 (0x00000072f3cfe000)
libdouble-conversion.so.1 => /usr/lib/aarch64-linux-gnu/libdouble-conversion.so.1 (0x00000072f3cdd000)
libdl.so.2 => /lib/aarch64-linux-gnu/libdl.so.2 (0x00000072f3cca000)
libglib-2.0.so.0 => /lib/aarch64-linux-gnu/libglib-2.0.so.0 (0x00000072f3bc3000)
libhybris-common.so.1 => /usr/lib/aarch64-linux-gnu/libhybris-common.so.1 (0x00000072f3b95000)
libfreetype.so.6 => /usr/lib/aarch64-linux-gnu/libfreetype.so.6 (0x00000072f3af8000)
libgraphite2.so.3 => /usr/lib/aarch64-linux-gnu/libgraphite2.so.3 (0x00000072f3acb000)
libicudata.so.55 => /usr/lib/aarch64-linux-gnu/libicudata.so.55 (0x00000072f2204000)
libpcre.so.3 => /lib/aarch64-linux-gnu/libpcre.so.3 (0x00000072f2193000)
librt.so.1 => /lib/aarch64-linux-gnu/librt.so.1 (0x00000072f217c000)

BTW, the application was prelinked by the short library prefix, .5 <- version 5, but could not find the Symbol already after launch.
Either you need to specify the full .5.12 index for linking, or check the dependencies in the distribution package!

How to install previous version, that linked with Qt 5.9 ?!

Keneda

@markatrafik
For now the only way would be to find the click and install it manually (with command line or using Ubuntu Touch Tweak Tool) after uninstalling the defective one.

I don't know where to find the previous clicks, an ehancement issue for openstore to allow installing previous version is open, but still not completed.

EDIT : https://gitlab.com/theopenstore/openstore-meta/-/issues/259

Keneda

If you know how to built .click package using clickable :
https://gitlab.com/ubports/apps/camera-app/-/tree/ae131c5d8b55ec2d7bb96745491b9cc9430fd36c

kugiigi

Previous versions can be requested from Brian. GSI ports are still not officially supported right?

But I'm thinking, this may have happened because clickable now defaults to building with Qt5.12 and perhaps apps that don't explicitly use the new framework will still be offered to <=OTA-15 devices.

Markatrafik

@keneda Thanks I just pressed the "Update" button and had sex with the system for hours.

Keneda

@kugiigi said in The camera-app is crashing!:

this may have happened because clickable now defaults to building with Qt5.12

That's what i guessed few posts above ^^

Markatrafik

@keneda Can the interface/installer say it won't work with these libraries instead of just overwriting the application to make it broken? Somebody should have thought of that when they did the rebuild.

I can't find my old .click package and I can't figure out how to download it from OpenStore either.

P.S. In idea it would be good for me to deploy a development environment on a PC to be able to cross-compile something for the phone, how to do this?

Keneda

@markatrafik said in The camera-app is crashing!:

I can't find my old .click package and I can't figure out how to download it from OpenStore either.

You need to download files from Git and then use clicakble to build the click, see post above.
Or you need to ask the click from @mariogrip .

@markatrafik said in The camera-app is crashing!:

In idea it would be good for me to deploy a development environment on a PC to be able to cross-compile something for the phone, how to do this?

No idea, i'm a noob for those things

Keneda

Must add that a fix should be released as soon as devs will see this issue, like the few times that kind of things comes with a core app release.

AppLee

@markatrafik
For app development, the best starting point is there:
https://docs.ubports.com/en/latest/appdev/index.html

Install clickable and try a simple hello world to figure things out.
Be aware of a noob issue, if you forgot apparmor policy then when you add it, you also have to bump the version number in order for it to get applied.

arubislander

@applee said in The camera-app is crashing!:

Be aware of a noob issue, if you forgot apparmor policy then when you add it, you also have to bump the version number in order for it to get applied.

This is no longer necessary. Newer versions of clickable uninstall the old version of the click package before installing the new one.

AppLee

@arubislander
Ooooh fancy
Nice thing, I didn't notice because I was running in auto pilot

Thanks for the info.

Markatrafik

@arubislander thank you for information