Axolotl on PinePhone / Mobian

[arno_nuehm]

Hi everyone.  I got my new Pinephone last Friday and have been trying to get Axolotl installed for a few days now.  I tried following arno's post from 12/16, but it's not quite working.

I installed mobian-installer-pinephone-phosh-alpha3.img and then followed the steps on the mobian wiki.

qt / qml interface

sudo apt install flatpak flatpak-builder

flatpak install org.kde.Platform//5.15
flatpak install org.kde.Sdk//5.15
flatpak install org.freedesktop.Sdk.Extension.golang//20.08
flatpak install org.freedesktop.Sdk.Extension.node12//20.08
flatpak install io.qt.qtwebengine.BaseApp//5.15

wget https://raw.githubusercontent.com/nanu-c...xolotl.yml
sudo flatpak-builder --install build org.nanuc.Axolotl.yml

Everything seemed to work properly.

However, when I tap the Axolotl icon, nothing happens. I just get the background screen.

Trying to run the cache clearing script

rm ~/.cache/QtProject/QtQmlViewer/qmlcache/* && rm -r ~/.local/share/textsecure.nanuc && rm -r ~/.config/textsecure.nanuc

I get the message that so such directory exists at home/mobian/.cache/QtProject/QtQmlViewer/qmlcache

I'm sure there's something obvious I'm missing.

Any help is appreciated, thanks.

I had the same issue, there is an issue open on Axolotl Github that I think is related (see. https://github.com/nanu-c/axolotl/issues/289) regarding flatpak file paths. I found a quick fix by making my own desktop icon as shown below. Axolot sometime fails to start the first time but otherwise has been working fairly well for me.

sudo nano /usr/share/applications/axolotl.desktop

[Desktop Entry]
Type=Application
Name=Axolotl2
GenericName=Signal Chat Client
Exec=flatpak run org.nanuc.Axolotl -e=qt
Icon=/home/mobian/build/files/share/icons/hicolor/128x128/apps/org.nanuc.Axolotl.png
Terminal=false
Categories=Network;Chat;InstantMessaging;Qt;
StartupWMClass=axolotl

Hello there,
I described the situation for manual installation not using flatpak-builder so the paths are a bit different. But I have the same issues with -e qt as described by acm006. Sometimes the app starts and sometimes it fails.
It may be related to the main .qml file which produces some error messages. Have a look here: Link.
For me, the deamonized option is still the best way to use Axolotl - regardless of the building process.

And my future idea is to have the deamon running and start the UI with qmlscene separately if needed. Good on resources...