I'd do one of these:
a) restore from the backup I had prior to the problem
or
b) reinstall a fresh OS
YMMV.
3 weeks ago was Nov 29th .... since I do daily, versioned, backups ... let's see ...
Code:
...
Tue Dec 3 00:07:03 2019 83.3 MB 19.7 GB
Mon Dec 2 00:07:04 2019 36.9 MB 19.8 GB
Wed Nov 27 00:07:04 2019 118 MB 19.9 GB
Tue Nov 26 10:02:40 2019 83.9 MB 20.0 GB
Tue Nov 26 09:20:04 2019 5.99 MB 20.0 GB
Mon Nov 25 09:20:04 2019 38.7 MB 20.0 GB
Sat Nov 23 00:33:04 2019 1.14 GB 21.2 GB
...
Tue Sep 17 00:03:04 2019 90.8 MB 26.1 GB
So my laptop doesn't have a backup for 11/29 - I was travelling.
Need to check the desktop:
Code:
...
Tue Dec 3 01:15:06 2019 405 KB 5.95 GB
Mon Dec 2 01:15:11 2019 8.21 MB 5.96 GB
Sun Dec 1 01:15:11 2019 1.01 KB 5.96 GB
Sat Nov 30 01:15:11 2019 893 bytes 5.96 GB
Fri Nov 29 01:15:11 2019 5.96 KB 5.96 GB
Thu Nov 28 01:15:11 2019 2.56 KB 5.96 GB
Wed Nov 27 01:15:05 2019 26.5 KB 5.96 GB
...
Tue Sep 17 01:15:06 2019 1.97 MB 6.62 GB
Ok, we're fine there. Backup versions go back into September for both systems.
Having excellent, versioned backups, is required with malware, viruses, and dumb user mistakes. Every year I'll make at least 1, perhaps 2-3 dumb user mistakes where restoring from a backup is the best solution. Backups solve a few issues, not just the obvious things. Versioned backups solve 100x more issues.
Looking through the history, you've tried more than I would have. These are probably the real issues:
Code:
sudo update-alternatives --remove-all python
sudo update-alternatives --remove-all python3
Python is a core capability required for any server/desktop Linux OS to work. Best to never mess with it.
If you need a specific version for software development, use pyenv. Do not touch the OS versions of python, perl, php, ruby. Leave those alone. Each tool has something like pyenv, rbenv, perlbrew, etc ... to have different versions, libraries, and self-contained scripting environments for developers.
Bookmarks