Does this error exit status 127 (libfreerdp2-2) happen because my system (xubuntu 23.10) is not writable?
Does this error exit status 127 (libfreerdp2-2) happen because my system (xubuntu 23.10) is not writable?
broken upgrade to xubuntu 24.04 from xubuntu 23.10, can access initramfs as root in recovery mode:
there is a broken package I believe is the root of this whole issue: libfreerdp2-2
if I execute
sudo apt install libfreerdp2-2
I get:
you might want to run apt --fix broken install to correct these, libfreerdp2-2 has unmet dependencies, try apt --fix broken install with no packages or suggest a solution.
After trying apt --fix broken install I get error processing package install-info (--configure), installed install-info package post installation script
Does this happen because the system is only readable?
I also executed
mount -o remount,rw /
mount --all
what do I need to do to check if these commands have worked?
sudo apt install libfreerdp2-2
Can you try purging the broken package ? :
sudo dpkg -P libfreerdp2-2I 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
nmtuiand then use the <TAB> 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 <TAB> 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 updateanddpkg --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.