I believe this to be a bug with Avogadro / my setup
Environment Information
Avogadro version: 1.99.0 nightly
Operating system and version: OpenSuSE 15.6
Actual Behavior
If I go to Extensions → Download Plugins, I get an error of “Error downloading plugin data” and the resulting windows are empty.
I’m using a Conda provided version of Python, and I believe Avogadro is pointing to this correctly. No error messages are output to the terminal when I attempt to get to the download plugins menu.
I’m not sure this is an error in the Avogadro code.
Flatpak offers the ability to downgrade apps, so I have gone through every version of the beta Flatpak and the same error occurs on all of them. I went back as far as the commit I made on the 10th November, which I know for a fact worked historically because that specific update fixed the plugin downloader on Qt6. The fact that it doesn’t work now indicates to me that the problem lies somewhere else.
I can think of three possibilities immediately, though I imagine there are more:
It’s something to do with openSUSE, which I also run – counterarguments are that Tumbleweed (my system) and Leap (@JGrantHill’s) are fairly far apart (e.g. Leap 15.6 has Qt 6.6.3 from late March, current is 6.8.1) and that changes to openSUSE shouldn’t affect the Flatpak much at all. But still, maybe it’s the knock-on effect of some fix for e.g. openSSL that has been backported to Leap and to the KDE Flatpak runtime (but it would have to have been backported by KDE to 6.7 and 6.8)
It’s something to do with KDE (but again the change would have had to have been backported to many different things) – but are you even using KDE @JGrantHill ?
It’s something to do with the website and/or the plugin list that it serves – but a cursory glance at https://avogadro.cc/plugins.json shows the data is accessible and nothing weird immediately jumps out at me; besides which, the Python script that generates it hasn’t been changed since the end of October
I’d definitely be keen to hear from other Linux users as to whether it works for them and which distro and DE they are running.
I also experience the same bug on Fedora. Doesn’t rule out that there’s been some fix to some library that caused this, but at least doesn’t seem to be restricted to openSUSE.