info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon
451 views
Skip to first unread message
Vincent Lefevre
Sep 19, 2016, 1:50:02 PM9/19/16
to
Some additional information. In "journalctl -b" output after reboot:
[...]
Sep 19 19:10:11 zira keyboard-setup.sh[401]: cannot open file /tmp/tmpkbd.qR4ecU
[...]
Sep 19 19:10:11 zira keyboard-setup.sh[401]: setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]
--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
[...]
Sep 19 19:10:11 zira keyboard-setup.sh[401]: cannot open file /tmp/tmpkbd.qR4ecU
[...]
Sep 19 19:10:11 zira keyboard-setup.sh[401]: setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
Sep 19 19:10:11 zira console-setup.sh[631]: setupcon: The keyboard model is unknown, assuming 'pc105'. Keyboard may be configured incorrectly.
[...]
--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Anton Zinoviev
Sep 21, 2016, 6:40:03 PM9/21/16
to
On Mon, Sep 19, 2016 at 07:31:12PM +0200, Vincent Lefevre wrote:
>
> Just after the upgrade of keyboard-configuration from 1.148 to 1.149,
> I could see that my previous configuration was lost. More precisely,
> config.dat changed in the following way:
When /etc/default/keyboard is ok, config.dat is ignored by console-setup
(default values are set before asking questions).
> and /etc/default/keyboard changed in the following way:
If this file becomes corrupted during upgrade, then this is certainly a
bad thing.
> -XKBMODEL="pc105"
> +XKBMODEL=""
> XKBLAYOUT="gb"
> XKBVARIANT=""
> XKBOPTIONS=""
This doesn't look as a file created by console-setup. Because of the
missing XKBMODEL, it looks like a file created by systemd-localed.service.
Would you experiment with the command
# localectl set-keymap ....
and
# localectl set-x11-keymap ...
and see if it corrupts /etc/default/keyboard.
> I don't know the possible consequences, though. The
> /usr/share/doc/keyboard-configuration/changelog.gz file just says:
>
> console-setup (1.149) unstable; urgency=medium
>
> [ Updated translations ]
> * Danish (da.po) by Joe Hansen
If I am right that the file was corrupted by systemd-localed, then
/etc/default/keyboard must have been corrupted after the upgrade of
console-setup. If this file was corrupted before the upgrade, then
console-setup would have repaired it.
> Note: I have
>
> -rw-r--r-- 1 root root 145 2016-09-19 19:03:19 /etc/default/keyboard
>
> Thus this file was modified when keyboard-configuration was upgraded
> (and before this upgrade of the Linux kernel and the nvidia packages).
Do you know what other packages were upgraded after console-setup and
before the Linux kernel and nvidia?
> This error message is just a consequence of this bug.
Yes. The error message was added in version 1.138 after I became aware
that other packages modify the configuration file of console-setup.
Anton Zinoviev
>
> Just after the upgrade of keyboard-configuration from 1.148 to 1.149,
> I could see that my previous configuration was lost. More precisely,
> config.dat changed in the following way:
When /etc/default/keyboard is ok, config.dat is ignored by console-setup
(default values are set before asking questions).
> and /etc/default/keyboard changed in the following way:
If this file becomes corrupted during upgrade, then this is certainly a
bad thing.
> -XKBMODEL="pc105"
> +XKBMODEL=""
> XKBLAYOUT="gb"
> XKBVARIANT=""
> XKBOPTIONS=""
This doesn't look as a file created by console-setup. Because of the
missing XKBMODEL, it looks like a file created by systemd-localed.service.
Would you experiment with the command
# localectl set-keymap ....
and
# localectl set-x11-keymap ...
and see if it corrupts /etc/default/keyboard.
> I don't know the possible consequences, though. The
> /usr/share/doc/keyboard-configuration/changelog.gz file just says:
>
> console-setup (1.149) unstable; urgency=medium
>
> [ Updated translations ]
> * Danish (da.po) by Joe Hansen
If I am right that the file was corrupted by systemd-localed, then
/etc/default/keyboard must have been corrupted after the upgrade of
console-setup. If this file was corrupted before the upgrade, then
console-setup would have repaired it.
> Note: I have
>
> -rw-r--r-- 1 root root 145 2016-09-19 19:03:19 /etc/default/keyboard
>
> Thus this file was modified when keyboard-configuration was upgraded
> (and before this upgrade of the Linux kernel and the nvidia packages).
Do you know what other packages were upgraded after console-setup and
before the Linux kernel and nvidia?
> This error message is just a consequence of this bug.
Yes. The error message was added in version 1.138 after I became aware
that other packages modify the configuration file of console-setup.
Anton Zinoviev
Vincent Lefevre
Sep 22, 2016, 5:25:19 AM9/22/16
to
On 2016-09-22 01:29:12 +0300, Anton Zinoviev wrote:
> On Mon, Sep 19, 2016 at 07:31:12PM +0200, Vincent Lefevre wrote:
> > -XKBMODEL="pc105"
> > +XKBMODEL=""
> > XKBLAYOUT="gb"
> > XKBVARIANT=""
> > XKBOPTIONS=""
>
> This doesn't look as a file created by console-setup.
It is created by "dpkg-reconfigure keyboard-configuration".
> On Mon, Sep 19, 2016 at 07:31:12PM +0200, Vincent Lefevre wrote:
> > -XKBMODEL="pc105"
> > +XKBMODEL=""
> > XKBLAYOUT="gb"
> > XKBVARIANT=""
> > XKBOPTIONS=""
>
> This doesn't look as a file created by console-setup.
If I start with the original /etc/default/keyboard file
(which was the file after the installation of the machine):
------------------------------------------------------------
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="gb"
XKBVARIANT=""
XKBOPTIONS=""
BACKSPACE="guess"
------------------------------------------------------------
I can reproduce the issue with:
dpkg-reconfigure -fnoninteractive keyboard-configuration
I get:
------------------------------------------------------------
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL=""
XKBLAYOUT="gb"
XKBVARIANT=""
XKBOPTIONS=""
BACKSPACE="guess"
------------------------------------------------------------
> Because of the missing XKBMODEL, it looks like a file created by
> systemd-localed.service.
>
> Would you experiment with the command
>
> # localectl set-keymap ....
> and
>
> # localectl set-x11-keymap ...
>
> and see if it corrupts /etc/default/keyboard.
# localectl set-x11-keymap foo
# cat /etc/default/keyboard
XKBLAYOUT=foo
BACKSPACE=guess
> > I don't know the possible consequences, though. The
> > /usr/share/doc/keyboard-configuration/changelog.gz file just says:
> >
> > console-setup (1.149) unstable; urgency=medium
> >
> > [ Updated translations ]
> > * Danish (da.po) by Joe Hansen
>
> If I am right that the file was corrupted by systemd-localed, then
> /etc/default/keyboard must have been corrupted after the upgrade of
> console-setup. If this file was corrupted before the upgrade, then
> console-setup would have repaired it.
>
> > Note: I have
> >
> > -rw-r--r-- 1 root root 145 2016-09-19 19:03:19 /etc/default/keyboard
> >
> > Thus this file was modified when keyboard-configuration was upgraded
> > (and before this upgrade of the Linux kernel and the nvidia packages).
>
> Do you know what other packages were upgraded after console-setup and
> before the Linux kernel and nvidia?
Aptitude 0.8.3: log report
Mon, Sep 19 2016 19:00:23 +0200
IMPORTANT: this log only lists intended actions; actions which fail
due to dpkg problems may not be completed.
Will install 94 packages, and remove 0 packages.
1169 kB of disk space will be freed
========================================
[HOLD, DEPENDENCIES] libegl-nvidia0:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libegl1-glvnd-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgl1-nvidia-glx:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgldispatch0-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgles-nvidia1:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgles-nvidia2:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgles1-glvnd-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgles2-glvnd-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libglx-nvidia0:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libglx0-glvnd-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libnvidia-cfg1:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libnvidia-glcore:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libnvidia-ml1:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libopengl0-glvnd-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] linux-compiler-gcc-5-x86:amd64 4.7.2-1
[HOLD, DEPENDENCIES] linux-doc-4.7:amd64 4.7.2-1
[HOLD, DEPENDENCIES] linux-headers-4.7.0-1-amd64:amd64 4.7.2-1
[HOLD, DEPENDENCIES] linux-headers-4.7.0-1-common:amd64 4.7.2-1
[HOLD, DEPENDENCIES] linux-kbuild-4.7:amd64 4.7.2-1
[HOLD, DEPENDENCIES] linux-libc-dev:amd64 4.7.2-1
[HOLD, DEPENDENCIES] nvidia-alternative:amd64 361.45.18-2
[HOLD, DEPENDENCIES] nvidia-driver:amd64 361.45.18-2
[HOLD, DEPENDENCIES] nvidia-driver-libs:amd64 361.45.18-2
[HOLD, DEPENDENCIES] nvidia-kernel-support:amd64 361.45.18-2
[HOLD, DEPENDENCIES] nvidia-legacy-check:amd64 361.45.18-2
[HOLD, DEPENDENCIES] nvidia-vdpau-driver:amd64 361.45.18-2
[HOLD, DEPENDENCIES] xserver-xorg-video-nvidia:amd64 361.45.18-2
[HOLD] gcc-snapshot:amd64 20160508-1
[HOLD] libnvidia-eglcore:amd64 361.45.18-2
[HOLD] nvidia-driver-bin:amd64 361.45.18-2
[HOLD] nvidia-kernel-dkms:amd64 361.45.18-2
[UPGRADE] bash:amd64 4.3-15 -> 4.4-1
[UPGRADE] console-setup:amd64 1.148 -> 1.149
[UPGRADE] console-setup-linux:amd64 1.148 -> 1.149
[UPGRADE] fonts-noto:amd64 20160724-2 -> 20160724-3
[UPGRADE] fonts-noto-hinted:amd64 20160724-2 -> 20160724-3
[UPGRADE] fonts-noto-mono:amd64 20160724-2 -> 20160724-3
[UPGRADE] fonts-noto-unhinted:amd64 20160724-2 -> 20160724-3
[UPGRADE] fonts-opensymbol:amd64 2:102.7+LibO5.2.1-2 -> 2:102.7+LibO5.2.1-3
[UPGRADE] fop:amd64 1:2.1-3 -> 1:2.1-4
[UPGRADE] gedit:amd64 3.21.90-2 -> 3.22.0-1
[UPGRADE] gedit-common:amd64 3.21.90-2 -> 3.22.0-1
[UPGRADE] gir1.2-gtksource-3.0:amd64 3.21.6-1 -> 3.22.0-1
[UPGRADE] gnome-terminal:amd64 3.21.92-1 -> 3.22.0-1
[UPGRADE] gnome-terminal-data:amd64 3.21.92-1 -> 3.22.0-1
[UPGRADE] ifupdown:amd64 0.8.13 -> 0.8.14
[UPGRADE] iio-sensor-proxy:amd64 1.1-1 -> 1.3-1
[UPGRADE] julia:amd64 0.4.6-1+b1 -> 0.4.7-1
[UPGRADE] julia-common:amd64 0.4.6-1 -> 0.4.7-1
[UPGRADE] julia-doc:amd64 0.4.6-1 -> 0.4.7-1
[UPGRADE] keyboard-configuration:amd64 1.148 -> 1.149
[UPGRADE] libclutter-gtk-1.0-0:amd64 1.8.0-2 -> 1.8.2-1
[UPGRADE] libdebconfclient0:amd64 0.215 -> 0.216
[UPGRADE] libfop-java:amd64 1:2.1-3 -> 1:2.1-4
[UPGRADE] libglew2.0:amd64 2.0.0-2 -> 2.0.0-3
[UPGRADE] libgtksourceview-3.0-1:amd64 3.21.6-1 -> 3.22.0-1
[UPGRADE] libgtksourceview-3.0-common:amd64 3.21.6-1 -> 3.22.0-1
[UPGRADE] libio-socket-ssl-perl:amd64 2.037-1 -> 2.038-1
[UPGRADE] libmm-glib0:amd64 1.6.0-1 -> 1.6.2-1
[UPGRADE] libopenlibm2:amd64 0.5.3+dfsg-1 -> 0.5.4+dfsg-1
[UPGRADE] libopts25:amd64 1:5.18.10-4 -> 1:5.18.12-2
[UPGRADE] libpadwalker-perl:amd64 2.2-1+b1 -> 2.2-2
[UPGRADE] libpcap0.8:amd64 1.7.4-2 -> 1.7.4-3
[UPGRADE] libreoffice:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-avmedia-backend-gstreamer:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-base:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-base-core:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-base-core-dbgsym:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-base-dbgsym:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-base-drivers:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-calc:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-calc-dbgsym:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-common:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-core:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-core-dbgsym:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-draw:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-draw-dbgsym:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-gtk3:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-gtk3-dbgsym:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-impress:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-impress-dbgsym:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-java-common:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-librelogo:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-math:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-math-dbgsym:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-nlpsolver:amd64 0.9+LibO5.2.1-2 -> 0.9+LibO5.2.1-3
[UPGRADE] libreoffice-ogltrans:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-pdfimport:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-report-builder:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-report-builder-bin:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-script-provider-bsh:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-script-provider-js:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-script-provider-python:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-sdbc-firebird:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-sdbc-hsqldb:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-sdbc-postgresql:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-style-galaxy:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-style-tango:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libreoffice-wiki-publisher:amd64 1.2.0+LibO5.2.1-2 -> 1.2.0+LibO5.2.1-3
[UPGRADE] libreoffice-writer:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] libservlet3.1-java:amd64 8.0.36-3 -> 8.0.37-1
[UPGRADE] libsmi2ldbl:amd64 0.4.8+dfsg2-12 -> 0.4.8+dfsg2-13
[UPGRADE] libsys-info-base-perl:amd64 0.7804-1 -> 0.7804-2
[UPGRADE] libtommath1:amd64 1.0-2 -> 1.0-3
[UPGRADE] libvte-2.91-0:amd64 0.45.92-1 -> 0.46.0-1
[UPGRADE] libvte-2.91-common:amd64 0.45.92-1 -> 0.46.0-1
[UPGRADE] libwacom-bin:amd64 0.19-1 -> 0.22-1
[UPGRADE] libwacom-common:amd64 0.19-1 -> 0.22-1
[UPGRADE] libwacom2:amd64 0.19-1 -> 0.22-1
[UPGRADE] login:amd64 1:4.2-3.1 -> 1:4.2-3.2
[UPGRADE] modemmanager:amd64 1.6.0-1 -> 1.6.2-1
[UPGRADE] ngrep:amd64 1.45.ds2-13 -> 1.45.ds2-14
[UPGRADE] pandoc:amd64 1.17.2~dfsg-1+b2 -> 1.17.2~dfsg-1+b3
[UPGRADE] passwd:amd64 1:4.2-3.1 -> 1:4.2-3.2
[UPGRADE] python3-uno:amd64 1:5.2.1-2 -> 1:5.2.1-3
[UPGRADE] task-english:amd64 3.35 -> 3.36
[UPGRADE] task-laptop:amd64 3.35 -> 3.36
[UPGRADE] task-ssh-server:amd64 3.35 -> 3.36
[UPGRADE] tasksel:amd64 3.35 -> 3.36
[UPGRADE] tasksel-data:amd64 3.35 -> 3.36
[UPGRADE] tcpdump:amd64 4.7.4-2 -> 4.7.4-3
[UPGRADE] uno-libs3:amd64 5.2.1-2 -> 5.2.1-3
[UPGRADE] uno-libs3-dbgsym:amd64 5.2.1-2 -> 5.2.1-3
[UPGRADE] ure:amd64 5.2.1-2 -> 5.2.1-3
[UPGRADE] ure-dbgsym:amd64 5.2.1-2 -> 5.2.1-3
========================================
Vincent Lefevre
Sep 22, 2016, 5:40:21 AM9/22/16
to
On 2016-09-22 11:10:45 +0200, Vincent Lefevre wrote:
> On 2016-09-22 01:29:12 +0300, Anton Zinoviev wrote:
> > On Mon, Sep 19, 2016 at 07:31:12PM +0200, Vincent Lefevre wrote:
> > > -XKBMODEL="pc105"
> > > +XKBMODEL=""
> > > XKBLAYOUT="gb"
> > > XKBVARIANT=""
> > > XKBOPTIONS=""
> >
> > This doesn't look as a file created by console-setup.
>
> It is created by "dpkg-reconfigure keyboard-configuration".
[...]
> On 2016-09-22 01:29:12 +0300, Anton Zinoviev wrote:
> > On Mon, Sep 19, 2016 at 07:31:12PM +0200, Vincent Lefevre wrote:
> > > -XKBMODEL="pc105"
> > > +XKBMODEL=""
> > > XKBLAYOUT="gb"
> > > XKBVARIANT=""
> > > XKBOPTIONS=""
> >
> > This doesn't look as a file created by console-setup.
>
> It is created by "dpkg-reconfigure keyboard-configuration".
I have a 3rd machine (which doesn't use systemd).
ypig:~> cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="gb"
XKBVARIANT=""
XKBOPTIONS=""
BACKSPACE="guess"
So, this is OK before the upgrade. Then, I upgraded only the
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="gb"
XKBVARIANT=""
XKBOPTIONS=""
BACKSPACE="guess"
following with aptitude:
Preconfiguring packages ...
(Reading database ... 556584 files and directories currently installed.)
Preparing to unpack .../0-console-setup-linux_1.149_all.deb ...
Unpacking console-setup-linux (1.149) over (1.148) ...
Preparing to unpack .../1-console-setup_1.149_all.deb ...
Unpacking console-setup (1.149) over (1.148) ...
Preparing to unpack .../2-keyboard-configuration_1.149_all.deb ...
Unpacking keyboard-configuration (1.149) over (1.148) ...
Setting up keyboard-configuration (1.149) ...
Processing triggers for systemd (231-7) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up console-setup-linux (1.149) ...
Setting up console-setup (1.149) ...
I got a question:
Configuring keyboard-configuration
The current keyboard layout in the configuration file
/etc/default/keyboard is defined as XKBLAYOUT="gb" and
XKBVARIANT="".
Please choose whether you want to keep it. If you choose this
option, no questions about the keyboard layout will be asked
and the current configuration will be preserved.
Keep the current keyboard layout in the configuration file?
<Yes> <No>
I chose "Yes", so that I didn't expect any change. But now:
ypig:~> cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL=""
XKBLAYOUT="gb"
XKBVARIANT=""
XKBOPTIONS=""
BACKSPACE="guess"
which is wrong!!! And /var/cache/debconf/config.dat changed in the
# Consult the keyboard(5) manual page.
XKBMODEL=""
XKBLAYOUT="gb"
XKBVARIANT=""
XKBOPTIONS=""
BACKSPACE="guess"
same way as the other machines.
Note: I don't remember getting this question on the other machines,
but the effect was the same.
Vincent Lefevre
Sep 22, 2016, 6:50:02 AM9/22/16
to
In the keyboard-configuration 1.148 binary package, one has:
-rwxr-xr-x 1 1862421 2016-07-29 08:06:33 DEBIAN/config
But in the 1.149 version:
-rwxr-xr-x 1 48945 2016-09-18 17:53:38 DEBIAN/config
The diff:
--- keyboard-configuration_1.148_all/DEBIAN/config 2016-07-29 08:06:33.000000000 +0200
+++ keyboard-configuration_1.149_all/DEBIAN/config 2016-09-18 17:53:38.000000000 +0200
@@ -159,33732 +159,6 @@
all_kbdnames () {
cat <<'EOF'
-C*model*a4techKB21*A4Tech KB-21
-C*model*a4techKBS8*A4Tech KBS-8
-C*model*a4_rfkb23*A4Tech Wireless Desktop RFKB-23
[...]
-zh_TW*layout*sn*渥魯夫語
-zh_TW*variant*sn**渥魯夫語
EOF
}
Couldn't this be the cause of the problem?
-rwxr-xr-x 1 1862421 2016-07-29 08:06:33 DEBIAN/config
But in the 1.149 version:
-rwxr-xr-x 1 48945 2016-09-18 17:53:38 DEBIAN/config
The diff:
--- keyboard-configuration_1.148_all/DEBIAN/config 2016-07-29 08:06:33.000000000 +0200
+++ keyboard-configuration_1.149_all/DEBIAN/config 2016-09-18 17:53:38.000000000 +0200
@@ -159,33732 +159,6 @@
all_kbdnames () {
cat <<'EOF'
-C*model*a4techKB21*A4Tech KB-21
-C*model*a4techKBS8*A4Tech KBS-8
-C*model*a4_rfkb23*A4Tech Wireless Desktop RFKB-23
[...]
-zh_TW*layout*sn*渥魯夫語
-zh_TW*variant*sn**渥魯夫語
EOF
}
Couldn't this be the cause of the problem?
Debian Bug Tracking System
Sep 22, 2016, 7:20:02 AM9/22/16
to
Processing control commands:
> found -1 1.150
Bug #838310 [keyboard-configuration] keyboard-configuration: user configuration lost + error message from setupcon
Marked as found in versions console-setup/1.150.
--
838310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
> found -1 1.150
Bug #838310 [keyboard-configuration] keyboard-configuration: user configuration lost + error message from setupcon
Marked as found in versions console-setup/1.150.
--
838310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Vincent Lefevre
Sep 22, 2016, 7:20:02 AM9/22/16
to
Control: found -1 1.150
On 2016-09-22 12:45:09 +0200, Vincent Lefevre wrote:
> In the keyboard-configuration 1.148 binary package, one has:
>
> -rwxr-xr-x 1 1862421 2016-07-29 08:06:33 DEBIAN/config
>
> But in the 1.149 version:
>
> -rwxr-xr-x 1 48945 2016-09-18 17:53:38 DEBIAN/config
Version 1.150, which has just appeared in unstable, has the same
issue. And upgrading doesn't fix the problem.
On 2016-09-22 12:45:09 +0200, Vincent Lefevre wrote:
> In the keyboard-configuration 1.148 binary package, one has:
>
> -rwxr-xr-x 1 1862421 2016-07-29 08:06:33 DEBIAN/config
>
> But in the 1.149 version:
>
> -rwxr-xr-x 1 48945 2016-09-18 17:53:38 DEBIAN/config
issue. And upgrading doesn't fix the problem.
Anton Zinoviev
Sep 22, 2016, 11:50:02 AM9/22/16
to
tags 838310 +help
thanks
On Thu, Sep 22, 2016 at 02:17:54PM +0200, Sven Joachim wrote:
>
> I'm pretty sure it is. The list of keyboard models is generated by
> running "./kbdnames-maker KeyboardNames.pl" from the Keyboard/
> directory, and currently this command does not print anything. I
> tracked the problem down to the removal of the current directory from
> @INC in perl, running "perl -I. kbdnames-maker KeyboardNames.pl" gives
> the long list of keyboard models again.
I am adding to this bug a 'help' tag because the bug is grave and at the
moment I don't have updated Debian machine so I can not debug.
Conceivably, the fix will be trivial. I don't know if the following
will fix the bug and if this is the right thing to do, but it seems
simple to change the first line
#!/usr/bin/perl
of Keyboard/kbdcompiler and Keyboard/kbdnames-maker to
#!/usr/bin/perl -I.
Anton Zinoviev
thanks
On Thu, Sep 22, 2016 at 02:17:54PM +0200, Sven Joachim wrote:
>
> I'm pretty sure it is. The list of keyboard models is generated by
> running "./kbdnames-maker KeyboardNames.pl" from the Keyboard/
> directory, and currently this command does not print anything. I
> tracked the problem down to the removal of the current directory from
> @INC in perl, running "perl -I. kbdnames-maker KeyboardNames.pl" gives
> the long list of keyboard models again.
I am adding to this bug a 'help' tag because the bug is grave and at the
moment I don't have updated Debian machine so I can not debug.
Conceivably, the fix will be trivial. I don't know if the following
will fix the bug and if this is the right thing to do, but it seems
simple to change the first line
#!/usr/bin/perl
of Keyboard/kbdcompiler and Keyboard/kbdnames-maker to
#!/usr/bin/perl -I.
Anton Zinoviev
Vincent Lefevre
Sep 22, 2016, 12:40:02 PM9/22/16
to
This also introduces the following change in
"/usr/share/console-setup/kbdnames-maker":
@@ -1,4 +1,4 @@
-#!/usr/bin/perl
+#!/usr/bin/perl -I.
use warnings 'all';
use strict;
I suppose that this is OK if /usr/share/console-setup/kbdnames-maker
is expected to be run with /usr/share/console-setup as the current
working directory. Otherwise, I'm wondering... What is the goal of
this script here?
0 new messages