Please consider submitting issues to GitHub which will enable tracking bug reports and suggestions. These will be closed and updated automatically when they are fixed – including notifications.
I believe this to be a bug with Avogadro:
(Please describe your bug or issue)
Environment Information
Avogadro version: 1.102.0 AppImage
Operating system and version: Fedora 42
Actual Behavior
On startup, Avogadro shows an “update available” prompt even though it’s already the latest release.
I’ll let Geoff respond in more detail but note that Pixi is included within the AppImage bundle as of 1.102, so it isn’t necessary to have it on your system.
Thanks for the bug report. I’m aware of the “update available” bug. We’ll release 1 1.102.1 to fix that one. (@matterhorn103 has suggested turning it off for Linux)
pixi is included as part of the AppImage, which is why it’s being used. Obviously it shouldn’t hang, but it would help to know:
what extension you’re trying to install
if there’s anything printed on the console / terminal
Also, it seems that Avogadro can’t load the Python extensions that are already present, for example, I can’t find the ORCA input generator.
In the terminal output there are many lines like “Cannot load script …”.
I can certainly start a build for an AppImage without pixi - the only thing I can think of is that it was unable to install the manifest to run the input generators or other scripts. So:
it finds pixi and tries to use it
it doesn’t have the pixi default environment
Since my 10 am meeting was cancelled, I’ll go spin that up.
All I did in the build was remove pixi from the AppImage. If it’s available in your path, it will try to use it. So if you’re having problems with pixi, I’d remove it from your environment.
I suspect the problem is that the default environment isn’t getting installed for pixi to use. But I don’t have time to debug that right now.
(It should be installing a pyproject.toml in the plugin directory and then using that to create a default python environment.)
Actually, I’m thinking about this a bit more. I’d be curious for some opinions.
Pixi makes a bunch of things easier .. but many people already have conda or python set up to their liking.
So maybe for a 1.102.1 release, the default should be to use conda (or mamba etc.) if found. And use pixi only as a backup for users who don’t have it installed.
Removing pixi leads to errors when trying to call it on startup. The program starts anyway, but input generators are still not showing up. They worked with previous versions and the Python scripts are already in the .local folder
Can you please include the errors you’re seeing? If you’re using the new build and don’t have pixi it should not use it and defer to your python environment.
I’m trying the latest AppImage, and now it doesn’t load any plugin.
The terminal output shows multiple lines like “Cannot load script […] Can’t find pixi in your path”
Okay, I think I found that one thanks to your help.
Should be spun up in a few minutes:
I’ll see if I can sort out another bug report about MMFF94 / GAFF force fields in the AppImage, but I’ll likely release a 1.102.1 release this weekend (including the update dialog fix).
The only errors I get now in the terminal are that it can’t find the force field parameters for GAFF and MMFF94.
Edit: I’ve also noticed another issue:
I removed the OpenChemistry folder in ~/.local/share. When I try to install the avo_xtb plugin, the message window appears “Installing dependencies with…”, but now it uses pip instead of pixi. The process hangs, and the terminal shows the following messages:
qt.core.qobject.connect: QObject::connect: No such slot Avogadro::QtPlugins::DownloaderWidget::cancelInstallation() qt.core.qobject.connect: QObject::connect: (receiver name: ‘DownloaderWidget’) qt.core.qobject.connect: QObject::connect: No such slot Avogadro::QtPlugins::DownloaderWidget::installationFinished() qt.core.qobject.connect: QObject::connect: (receiver name: ‘DownloaderWidget’)
However, I’ve noticed that if I wait for a while, then close and restart Avogadro, the XTB extension appears in the Extensions menu.
Then, when trying to install the crest or xtb plugins from the Extensions menu, their installation window closes unexpectedly without any message. The terminal shows multiple error and warning messages. I’ve attached the full output here:
Just to note that it’s not just a problem with the avo_xtb plugin, I tested with the AppImage on my system and the same error occurs when trying to install the prerequisites for nanocar-avogadro:
qt.core.qobject.connect: QObject::connect: No such slot Avogadro::QtPlugins::DownloaderWidget::cancelInstallation()
qt.core.qobject.connect: QObject::connect: (receiver name: 'DownloaderWidget')
qt.core.qobject.connect: QObject::connect: No such slot Avogadro::QtPlugins::DownloaderWidget::installationFinished()
qt.core.qobject.connect: QObject::connect: (receiver name: 'DownloaderWidget')
avo_xtb very deliberately doesn’t actually have any dependencies, so I was confused as to why the problem is even arising.
What I guess is happening is that Avogadro/Pixi is trying to install the dev dependencies group from avo_xtb’s pyproject.toml. Since these aren’t required dependencies I’m not sure why it’s doing that – maybe that’s the default behaviour of Pixi?
For now, anyone who wants to install the avo_xtb plugin can click “No” when asked whether to install dependencies. The plugin doesn’t need them.
Edit: Having said that, if you choose “no” then the plugin doesn’t currently get installed, even though it’s downloaded, which I guess makes sense if it thinks that it can’t install it without deps.