I feel your pain. This time, however, we cleared the hanging locks, so it should not do that again... I'd say give it no longer than an hour, though.
So I report back in an hour?
If I am still alive, I will raise a hand and wave...
2 Likes
Well... After an hour, the terminal is still running an producing the same Hardware error messages... 
If ctl+c works:
ps aux | grep mtxrun
ps aux | grep context
And relay those results here...
If ctl+c does not work, hit the X and close the terminal and open a new one - then follow the above...
Did not work, after "X" and new terminal:
=>
myself 14008 0.0 0.0 9476 2560 pts/0 S+ 13:16 0:00 grep --color=auto mtxrun
=>
myself 14057 0.0 0.0 9476 2560 pts/0 S+ 13:16 0:00 grep --color=auto context
ugh... Let's try sudo
sudo ps aux | grep dpkg
=>
myself 15201 0.0 0.0 9476 2560 pts/0 S+ 13:21 0:00 grep --color=auto dpkg
There are no running processes. All that is shown in each of those is the attempt to check running processes.
What about
sudo dpkg --audit
=>
Die folgenden Pakete sind nur halb konfiguriert, wahrscheinlich durch
Probleme während der ersten Konfiguration. Die Konfiguration sollte mit
dpkg --configure <Paket> oder mit dem Konfigurations-Menüeintrag in
dselect erneut versucht werden:
context powerful TeX format
Deepl:
The following packages are only half-configured, probably due to
problems during the initial configuration. The configuration should be retried with
dpkg --configure <package> or with the configuration menu entry in
dselect:
context powerful TeX format
Your translating them helps a lot. I wish more members did that!
sudo dmesg -D
sudo dpkg --remove --force-remove-reinstreq context
If No errros above, try
sudo apt --fix-broken install
Well that's the least I can do for all the effort you put into helping me 
You might be onto something, all commands finished without any visible errors to me...
Let's run
sudo apt update
and see if you get clean results
Seemed to do just fine, last part of the message:
Aktualisierung für 103 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
Deepl:
Updates available for 103 packages. Run “apt list --upgradable” to view them.
It is safe to run
sudo apt upgrade
Seemed to run without any problems as well 
1 Like
Great. All fixed up.
There is only one task left, now.
Get a Sledge hammer...
Have thought of other tools to fix the job as well 
Thank you so much for your help, I would have been lost without your support!
And my offer for a "compensation" through paypal (DM for details) is still there 
If I may ask you one more question:
Do you have an idea what caused this nasty problem and how I can avoid it in the future? Seemed to have something to do with my resent installs of latex related apps/ packages and fonts?
I cannot say for sure the exact cause, but looking at all of the output you posted, it appears that when attempting to install LaTeX, the ConTeXt package went out of bounds on the RAM.
The Short, short of it is that many sellers of computers will overclock them a bit, to give themselves a reputation of providing Good Fast Computers.
If there is any overclocking, then the extremely intensive running of mtxrun compiling thousands of font metric files and lua files and whatever else overheated and overburdened the RAM.
At this point, the AMD processor began protective measures to save your hardware, recalculating and correcting the faults.
You might say, "Thanks AMD" and it is accurate, but it was not about protecting your investment. It was about preventing a fire or battery combustion.
But, that mitigating of the RAM interrupted the installation process, which was the dpkg error we just beat the brains out of.
So - a Very Rare Perfect Storm of events.
1 Like
Thank you very much for that insightful explanation!
Of course now I am wondering, whether it is reasonably safe to run/ use the LaTeX packages I was originally trying to install?