I tried to reproduce the problem in Jammy and everything seems to work
properly. Looks like 1.95.1-8 has indeed fixed the problem.
I am marking this bug as Fix Released. Please change the bug back to New if you
can still reproduce the error in Jammy.
** Changed in: avogadrolibs (Ubuntu)
S
Fwiw, jammy now has the 1.95.1-8 release
https://bugs.launchpad.net/ubuntu/+source/avogadrolibs/1.95.1-8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961519
Title:
Avogadro 1.95.1 broken, proposal
While the cherry-picked patch does contain some important fixes, it does
not contain the specific change that fixes this bug. The Debian bug was
marked as closed along with the one actually addressed by this patch,
while mistakenly missing the commit that fixed it. I notified the
confusion to the D
** Changed in: avogadrolibs (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961519
Title:
Avogadro 1.95.1 broken, proposal to cherry-pick fix
To manag
Thanks for reporting.
I found the corresponding Debian bug, and see that the new version of
avogadrolibs has been synced to Jammy
(https://launchpad.net/ubuntu/+source/avogadrolibs/1.95.1-7). It is
currently running the package regression tests, but assuming those are
ok, the new version should be
