Thanks Martin, your solution to disable systemd-resolve allowed me to
finally resolve hosts on my local network again... I was using a
temporary workaround of replacing "echo 'nameserver 192.168.1.1' >
/etc/resolv.conf", however that doesn't survive reboots.
This issue should be addressed by Ubun
I was able to work around this stupidity by temporarily pulling the
execute bit from setxkbmap as follows:
/var/cache/apt/archives⟫ which setxkbmap
/usr/bin/setxkbmap
/var/cache/apt/archives⟫ sudo chmod -x /usr/bin/setxkbmap
/var/cache/apt/archives⟫ sudo dpkg -i
keyboard-configuration_1.108ubun
/usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info
/keyboard-configuration.postinst configure 1.108ubuntu15
This crap is blocking me from properly updating my system, I'm
attempting to upgrade over ssh inside a byobu session.
adding set -x to the script /var/lib/dpkg/info/keyboard-
c
This is still broken in 16.04 / Xenial.
I'm going to try using a root cronjob to catch and recover:
*/5 * * * * if [ $(ps -ef | grep /usr/sbin/sshd | grep -v grep
| wc -l) -eq 0 ]; then /usr/sbin/service ssh start; fi
--
You received this bug notification because you are a member of Ub
This should be reopened.
This is a potentially serious regression that broke on my machine
upgrading from 14.10 to 15.04. The way in which it broke left me
looking at a shell that told me despite my FS being mounted "rw"
according to "mount", all commands were failing because of "Read-only
file
5 matches
Mail list logo