sudo apt install libfreerdp2-2
Can you try purging the broken package ? : sudo dpkg -P libfreerdp2-2
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
sudo apt install libfreerdp2-2
Can you try purging the broken package ? : sudo dpkg -P libfreerdp2-2
I purged the broken package with sudo dpkg -P libfreerdp2-2 and immediately afterwards I executed sudo apt get upgrade. It unleashed a list of 96 packages to upgrade totaling 900 MB of data.
However, if I press yes on ‘do you want to continue?’ wlan seems to be off:
E: failed to fetch http… initramfs-tools-core… could not connect to 127.0.0.1, connection refused.
(I can write the whole address if you need it)
how do I enable wlan as root from initramfs?
I purged the broken package with sudo dpkg -P libfreerdp2-2 and immediately afterwards I executed sudo apt get upgrade.
Cool.
how do I enable wlan as root from initramfs?
I'd run nmtui
and then use the key to navigate between the items and go for "Activate" to enable your WiFi connection. It will show no pop up or something when it successfully activates the connection. I think it will just show a * sign next to the connection item. When that is done use to navigate out of nmtui and test your connection.
Error 127 is "command not found".
Here, at the end of the reply, the solution was to rename the postinst-file of the package and go on with apt update
and dpkg --configure -a
.
No. Likely just a broken package.
I highly recommend doing a system snapshot before an upgrade to prevent stuff like that.
Because of that I highly recommend atomic Fedora where this is fully automated. Or at least OpenSUSE tumbleweed. Also Ubuntu will be able to do this.