Avogadro version: (please complete the following information from the About box):
- Avogadrolibs: 1.100.0
- Qt: 5.15.2
Desktop version: (please complete the following information):
- OS: Windows
- Version 10, 64bit
- Compiler (if you built from source)
Describe the bug
After the extraction of the installer, opting for an addition to the $PATH variable for every user of the computer, an intermediate note warns about an entry apparently too long.
To Reproduce
Steps to reproduce the behavior:
- Deinstallation of a previously well working instance of Avogadro 1.99 by Avogadro's deinstaller
- Installation of the nightly build archive from the landing page, md5sum ending with
fbc832abf.
- When asked, opt-in for both creation of a short-cut to the Desktop as well as addition to the path variable for every user of the computer.
After a completion of the installation, a double click on the desktop icon opens the application successfully though with a a noticeable delay: in the display of Windows' task manager, Avogadro2 remains for about 30s as an item of the sub list about background processes, the GUI of Avogadro shows up only after the icon is promoted to "Apps".
Expected behavior
Perhaps a fragment to trace why some users report problems launching Avogadro2 in Windows altogether (link).
Screenshots

Avogadro version: (please complete the following information from the About box):
Desktop version: (please complete the following information):
Describe the bug
After the extraction of the installer, opting for an addition to the $PATH variable for every user of the computer, an intermediate note warns about an entry apparently too long.
To Reproduce
Steps to reproduce the behavior:
fbc832abf.After a completion of the installation, a double click on the desktop icon opens the application successfully though with a a noticeable delay: in the display of Windows' task manager, Avogadro2 remains for about 30s as an item of the sub list about background processes, the GUI of Avogadro shows up only after the icon is promoted to "Apps".
Expected behavior
Perhaps a fragment to trace why some users report problems launching Avogadro2 in Windows altogether (link).
Screenshots