-
-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Regression: first item in ordered plugin dialog is empty #1632
Comments
This issue has been mentioned on Avogadro Discussion. There might be relevant details there: https://discuss.avogadro.cc/t/regression-first-item-in-ordered-plugin-dialog-is-empty/5320/1 |
This issue has been mentioned on Avogadro Discussion. There might be relevant details there: https://discuss.avogadro.cc/t/xtb-plugin-installation/6340/15 |
Still bizarrely remains the case that the version of Avogadro that I have compiled myself doesn't have this issue, but all other versions apparently do. Could this be a bug that was fixed in very recent Qt5 versions? I compiled against 5.15.15, whereas the nightly AppImage is compiled against 5.15.2. |
That's certainly possible. Is the qt6 version able to run the plugins? If so, does that fix the bug? My feeling is that it's probably better to push ahead with migrating to qt6 sooner. |
No, sadly. That's actually the only thing I've been able to spot that doesn't work in my Qt6 build. |
|
@matterhorn103 - why don't you post something on the forum. Maybe a few others would be willing to help with porting. IIRC some of that has to do with context highlighting in the input generators, which isn't so crucial. That could be |
Just to check in - does this still happen with the current HEAD? |
Yep, still happens, this is a bug in Qt 5.15.2 that was fixed in some later release. If I build from source against Qt 5.15.15 or Qt 6 it's fine, but the AppImage and nightly binaries for Windows/Mac still have the issue because 5.15.2 is the only Qt5 binary available. |
With #1908 now merged, all the distributed Linux builds of Avogadro are built against Qt6, so this issue will be fixed on Linux in the upcoming 1.100 release. Migration to Qt6 on Windows and Mac has been postponed until after 1.100, in time for the subsequent (likely summer) release, so the bug will unfortunately still raise its head on those platforms for now. Leaving this open until then. |
This issue has been mentioned on Avogadro Discussion. There might be relevant details there: |
Avogadro version: (please complete the following information from the About box):
Desktop version: (please complete the following information):
Describe the bug
The bug that I described and fixed here seems to be back.
Weirdly, it doesn't occur on my personal build of Avogadro from the latest codebase. However, it does in the 1.99 AppImage, I get the impression it's also happening on Windows, and @JGrantHill also reports it happening on macOS (ARM).
To Reproduce
Steps to reproduce the behavior:
Avogadro/commands/avo_xtb/config.json
The text was updated successfully, but these errors were encountered: