On Wed, Apr 04, 2018 at 04:25:17PM -0000, Juha Sahakangas wrote:
> This bug is still happening and it absolutely certainly does not have
> anything to do with mechanical issues.
>
> Andersk already identified the exact cause in comment #31 also - and
> it's absolutely trivial to verify that the offending "setupcon --force
> --save" command is still in the "keyboard-configuration.postinst" of the
> latest 1.178ubuntu1 version of console-setup package.
That line isn't executed in the normal case. There's some weird
formatting going on, but:
if [ "$DISPLAY" ] && which setxkbmap >/dev/null; then
setxkbmap -option '' -model "$model" "$layout" "$variant" "$options" || true
# setting the font corrupts X
# setting up the keyboard breaks wayland
if type setupcon >/dev/null 2>&1; then setupcon --save-only
cat >&2 <<EOF
Your console font configuration will be updated the next time your system
boots. If you want to update it now, run 'setupcon' from a virtual console.
EOF
fi else
case "`uname`" in
GNU)
[ ! -f /var/run/hurd-console.pid ] || kill `cat /var/run/hurd-console.pid`
;;
*)
if type setupcon >/dev/null 2>&1; then setupcon --force --save
fi
;;
esac
fi
see the "fi else" - the first branch is taken if $DISPLAY is set and
sexkbmap and setupcon exists.
Is $DISPLAY not set for you when this runs?
You can add `set -x' to the top of
/var/lib/dpkg/info/keyboard-configuration.postinst and run something
like `sudo DEBIAN_FRONTEND=noninteractive dpkg-reconfigure
keyboard-configuration' to verify what happens when
keyboard-configuration is configured by dpkg.
I think we should consider maybe removing that case too, but I'd like to
know if that is the actual cause of your problem please.
On Wed, Apr 04, 2018 at 04:25:17PM -0000, Juha Sahakangas wrote: configuration. postinst" of the
> This bug is still happening and it absolutely certainly does not have
> anything to do with mechanical issues.
>
> Andersk already identified the exact cause in comment #31 also - and
> it's absolutely trivial to verify that the offending "setupcon --force
> --save" command is still in the "keyboard-
> latest 1.178ubuntu1 version of console-setup package.
That line isn't executed in the normal case. There's some weird
formatting going on, but:
if [ "$DISPLAY" ] && which setxkbmap >/dev/null; then
setupcon --save-only hurd-console. pid ] || kill `cat /var/run/ hurd-console. pid`
setupcon --force --save
setxkbmap -option '' -model "$model" "$layout" "$variant" "$options" || true
# setting the font corrupts X
# setting up the keyboard breaks wayland
if type setupcon >/dev/null 2>&1; then
cat >&2 <<EOF
Your console font configuration will be updated the next time your system
boots. If you want to update it now, run 'setupcon' from a virtual console.
EOF
fi else
case "`uname`" in
GNU)
[ ! -f /var/run/
;;
*)
if type setupcon >/dev/null 2>&1; then
fi
;;
esac
fi
see the "fi else" - the first branch is taken if $DISPLAY is set and
sexkbmap and setupcon exists.
Is $DISPLAY not set for you when this runs?
You can add `set -x' to the top of dpkg/info/ keyboard- configuration. postinst and run something FRONTEND= noninteractive dpkg-reconfigure configuration' to verify what happens when configuration is configured by dpkg.
/var/lib/
like `sudo DEBIAN_
keyboard-
keyboard-
I think we should consider maybe removing that case too, but I'd like to
know if that is the actual cause of your problem please.
subscribe laney
Cheers,
--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]