Help creating an UBSync arm64 version
Are you using my version or yours ?
@ernest Yours. I already deleted UBSync multiple times to get sure.
Hm, I will check it again...
the file creation dates of the lib files, look like the ones I created myself.
Ah no, it is definitely yours, the files where created on the 26th November 2019.
poVoq last edited by poVoq
Maybe a different library could be used? Something like this?
Edit or in Rust:
If you want to start manually the daemon this is the command:
LD_LIBRARY_PATH=/opt/click.ubuntu.com/ubsync/current/Owncloud-Sync/lib/aarch64-linux-gnu/lib/ && /opt/click.ubuntu.com/ubsync/current/lib/aarch64-linux-gnu/bin/OwncloudSyncd
You can play with it according to : https://doc.owncloud.org/desktop/2.1/advancedusage.html
An example of output.
Looking back at the code, I remember why I didn't push the arm64 ... the type of architecture is hardcoded and i don't know the c++, making the journey quite hard. So any help is welcome for that.
Interestingly the command works and my folder gets synced: https://paste.ubuntu.com/p/CXf3VWmB3n/
After executing the command, the app also shows a "last-synced" date. The service status still is "Stopped".
So the service just cannot be started by the app. Perhaps it is an AppArmor issue?!
On my side the app doesn't any issue on a fresh install ;), so I doubt apparmor.
likely while playing you messed up something.
please ensure that the file is correct, as below.
Look into .config/ubsync/ubsync.conf, ensure that your timer is different than 0
@ernest Ha, that's it!
In that file the exec was referring to the wron path: ..../arm-linux-gnueabihf/...
I changed it to "aarch64-linux-gnu" and now it works!
Obviously that file is not getting purged, when clearing app data with UT-Tweak-Tool, because it is not part of the app-directory...
Hm, but it is still not possible to trigger a sync from within the app.
There is an error that it could not find libowncloudsync.so.0: https://paste.ubuntu.com/p/Wzp55yHnvq/
But I can still trigger the sync with the terminal command.
I wouldn't be surprise there is a remaining bit of armhf code somewhere.(How were you able to install it ??? on arm64 phone)
I suggest to remove the app and search manually for any ubsync and Nextcloud or Owncloud related, then delete them.
like sudo find / -iname "ubsync"
@ernest I cleaned up everything and reinstalled your version. And now it works.
How were you able to install it ??? on arm64 phone
I built an arm64 version of ubsync... but the contained pre-compiled owncloud libraries were still armhf. And I think the qmake .pro-file did also create armhf path's and so on...
@Luksus Yes, the architecture is hardcoded everywhere in this app