An advisory to help prevent a waste of time chasing problems unnecessarily. I have had multiple instances where “miniconda” directories loaded into the path ahead other directories have garbled-up updates and running of some other items. Suggest that you deactivate conda prior to updates. When going to root, use “su -” which will then only use a bare-bones root $PATH.
In gentoo linux,e.g., I found “emerge” was compiling packages using the wrong python version because it picked up python from miniconda that was in the $PATH and didn’t use right version from system. This caused total confusion when the mis-compiled package was a dependency of some other package. gentoo maintainers examining my build logs could not see how a package was compiled with wrong python until one investigator saw a miniconda path in compilation of one module.
The package dconf-editor stopped running until I found, by happinstance, that I needed to deactivate conda prior to running.
An issue to watch. Trying to just be helpful.
tom kosvic