Hmm, your report re the apt sources is weird. That should only be an issue if/when you have "multi-arch" enabled (it allows installation of 32 bit apps and libraries alongside 64 bit ones). And as our repos only have 64 bit support, the issue you are reporting should have occurred as soon as you enabled "multi-arch". Whether or not our "testing" repo is enabled or not should make no difference. Obviously it did in your case and I have no idea why. I guess at least my suggestion fixed it (although I'm surprised that just adjusting the entry in the testing sources.list fixed it too). Anyway, if it works now, no need to fight it! :)
Awesome! Thanks for testing on Bullseye and reporting back.
Thanks for your feedback. I really appreciate it.
I'll see if I can do a rebuild for the main repo for both Buster and Bullseye this week. I notice that there is a newer version out now too, so I may as well package that one instead (the newer version just has some minor bug fixes for the current version so should be fundamentally the same).
Your guidance regarding the restart makes tons of sense. Thanks again.
Hmm, your report re the apt sources is weird.
Hmm, your report re the apt sources is weird. That should only be an issue if/when you have "multi-arch" enabled (it allows installation of 32 bit apps and libraries alongside 64 bit ones). And as our repos only have 64 bit support, the issue you are reporting should have occurred as soon as you enabled "multi-arch". Whether or not our "testing" repo is enabled or not should make no difference. Obviously it did in your case and I have no idea why. I guess at least my suggestion fixed it (although I'm surprised that just adjusting the entry in the testing sources.list fixed it too). Anyway, if it works now, no need to fight it! :)
Awesome! Thanks for testing on Bullseye and reporting back.
Thanks for your feedback. I really appreciate it.
I'll see if I can do a rebuild for the main repo for both Buster and Bullseye this week. I notice that there is a newer version out now too, so I may as well package that one instead (the newer version just has some minor bug fixes for the current version so should be fundamentally the same).
Your guidance regarding the restart makes tons of sense. Thanks again.