Flatpak 1.102 Pixi bundling

Development
1

I was going to write a post asking for some help working out why I can’t get the 1.102 Flatpak working, but actually I’ve sorted I think. But it’s worth posting about because it may affect other users when they upgrade.

Essentially, if launching the Flatpak fails with console output along the lines of

> flatpak run org.openchemistry.Avogadro2
Avogadroapp version:  1.102.0
Avogadrolibs version:  1.102.0
Qt version:  6.9.3
qt.core.qobject.connect: QObject::connect(QObject, Unknown): invalid nullptr parameter
SSL version:  "OpenSSL 3.3.5 30 Sep 2025"
 registering obmm plugins
"/app/bin/obabel"  found:  "/app/bin/obabel: Open Babel 3.1.1 -- Nov 11 2011 -- 11:11:11"
Using manifest in "/home/matterhorn103/.var/app/org.openchemistry.Avogadro2/data/OpenChemistry/Avogadro"
QProcess: Destroyed while process ("/app/bin/pixi") is still running.
Using manifest in "/home/matterhorn103/.var/app/org.openchemistry.Avogadro2/data/OpenChemistry/Avogadro"
QProcess: Destroyed while process ("/app/bin/pixi") is still running.
Using manifest in "/home/matterhorn103/.var/app/org.openchemistry.Avogadro2/data/OpenChemistry/Avogadro"
QProcess: Destroyed while process ("/app/bin/pixi") is still running.

and just repeatedly reporting the same QProcess error, the solution is likely to remove all plugins by deleting /home/$USER/.var/app/org.openchemistry.Avogadro2/data/OpenChemistry and its contents.

2

Just in time for 1.102.1 :wink:

Looks like pixi is timing out? I fixed some of that logic in the last few days, but if there’s an obvious issue, it would be good to squash it soon.

1 Like
3

Not sure. As I say, just clearing out all the old plugin files made it go away.

1 Like