** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-disco verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-cosmic verification-done-disco verification-done-xenial
--
You received
Verified 1.15.5-1ubuntu5.16.04.0 on Xenial:
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Verified 2.0.4-2ubuntu1.18.04.0 on Bionic:
test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Verified 2.0.4-2ubuntu1.18.10.0 on Cosmic:
test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Verified 2.0.4-4ubuntu1.19.04.0 on Disco:
test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Hello David, or anyone else affected,
Accepted kbd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/kbd/2.0.4-2ubuntu1.18.10.0 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I see that the kbd changes didn't really get reviewed upstream yet,
right? Anyway, the change is a bit intrusive, but it does make sense
(especially with the additional patch of not erroring out), so I will
accept it for now at least into -proposed.
** Changed in: kbd (Ubuntu Disco)
This bug was fixed in the package kbd - 2.0.4-4ubuntu2
---
kbd (2.0.4-4ubuntu2) eoan; urgency=medium
* kbd_mode: Add -f option and don't perform dangerous mode switches without
it. In the back-ported fix kbd_mode exits with success, even when the
dangerous mode change is
** Description changed:
+ (kbd)
+ [Impact]
+
+ * kbd_mode -u is documented to break keyboards in modes other than xlate and
unicode, while it is still called by some scripts. Those scripts are called
transitively by maintainer scripts such as the one already fixed in
console-setup.
+ * To
This bug was fixed in the package console-setup - 1.178ubuntu2.9
---
console-setup (1.178ubuntu2.9) bionic; urgency=medium
* Call setupcon --force only when debian-installer is active
and always redirect output to /dev/null to not block. (LP: #520546)
-- Balint Reczey Tue,
This bug was fixed in the package console-setup - 1.178ubuntu12.1
---
console-setup (1.178ubuntu12.1) disco; urgency=medium
* Call setupcon --force only when debian-installer is active
and always redirect output to /dev/null to not block. (LP: #520546)
-- Balint Reczey Tue,
This bug was fixed in the package console-setup - 1.178ubuntu9.2
---
console-setup (1.178ubuntu9.2) cosmic; urgency=medium
* Call setupcon --force only when debian-installer is active
and always redirect output to /dev/null to not block. (LP: #520546)
-- Balint Reczey Tue,
Verified 1.178ubuntu2.9 on Bionic:
rbalint@yogi:~/projects/deb/unattended-upgrades$ sudo kbd_mode
The keyboard is in some unknown mode
rbalint@yogi:~$ sudo apt install console-setup console-setup-linux
keyboard-configuration
Reading package lists... Done
Building dependency tree
Reading
Verified 1.178ubuntu9.2 on Cosmic:
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode
The keyboard is in raw (scancode) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo apt install -qq
console-setup-linux console-setup keyboard-configuration
The following packages were automatically
Verified 1.178ubuntu12.1 on Disco:
root@MacBookAir-test:/home/rbalint# echo $DISPLAY
root@MacBookAir-test:/home/rbalint# kbd_mode -C /dev/tty1
The keyboard is in raw (scancode) mode
root@MacBookAir-test:/home/rbalint# apt install -qq console-setup-linux
console-setup keyboard-configuration
The
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kbd (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Adding fix for Xenial in case the issue turns out more important and we
release the fix.
The patch needs testing, but should work.
** Patch added: "console-setup_1.108ubuntu15.6.patch"
@paelzer You did not observe the mode change reported by kbd_mode either after
the reinstall?
Have you unset DISPLAY, too?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Xenial runs X on VT7 thus in default installations the postinst scripts don't
break X.
If this fix is scheduled for SRU, please also fix console-setup.postinst, not
just keyboard-configuration.postinst.
** Also affects: kbd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also
FYI:
I was affected by the issue, but there must be another way to trigger than the
(re)install of console-setup and/or keyboard-configuration as those actions
were not triggering the issue for me after I rebooted.
OTOH the time it started to happen perfectly matches a background update to
I forwarded the proposed kbd fix upstream:
https://lists.altlinux.org/pipermail/kbd/2019-April/000653.html
** Changed in: kbd (Ubuntu Eoan)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Description changed:
(console-setup)
[Impact]
* keyboard-configuration's postinst changes keyboard mode breaking X
keys.
- [Workaround]
-
- Reboot (or restart X) and the problem will go away.
-
[Test Case]
-
- [racb] Note that upgrading to the fixed package will not fix the
Xorg and the kernel are doing the right thing here.
** No longer affects: linux (Ubuntu)
** Changed in: xorg-server (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: xorg-server (Ubuntu Cosmic)
Status: Confirmed => Invalid
** Changed in: xorg-server (Ubuntu Disco)
Accepting the fix into stable releases. Note that the fix only prevents
new breakages; existing affected users will not be unbroken without
rebooting (or rebooting X).
** Description changed:
-
(console-setup)
[Impact]
- * keyboard-configuration's postinst changes keyboard mode breaking
Updated Ubuntu-18.04 LTS, rebooted and problem is gone.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or
This bug was fixed in the package console-setup - 1.191ubuntu3
---
console-setup (1.191ubuntu3) eoan; urgency=medium
* No change rebuild to include all previous changes
console-setup (1.191ubuntu2) eoan; urgency=medium
* Call setupcon --force only when debian-installer is
But scripts changing between scancode and ascii/unicode (such as for
some terminal emulation, dosbox, etc.) would break. I'm not saying they
are widespread, but I have seen this kind of use, and requiring such
flag will suddenly break them.
--
You received this bug notification because you are a
@samuel-thibault kbd_mode would check current state and only allow safe
mode switches without -f, i.e. between unicode and ascii. Scripts
changing between those modes would not have to be changed.
I fixed postinst to not pass -f to setupcon, it is in eoan-proposed.
--
You received this bug
** Description changed:
+
+ (console-setup)
+ [Impact]
+
+ * keyboard-configuration's postinst changes keyboard mode breaking X
+ keys.
+
+ [Test Case]
+
+ * Ssh to a system or open a terminal and unset DISPLAY
+
+ $ echo $DISPLAY
+
+ $
+
+ * Check kbd mode, should be raw
How will kbd_mode know whether it's safe or not?
Adding a -f option to kbd_mode will at best break some *other* existing
scripts, while this very script should really definitely *NOT* pass -f
to setupcon. That is the nonsense which needs to be fixed.
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kbd (Ubuntu Disco)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kbd (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kbd (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kbd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
I also added kbd because I plan patching kbd_mode to perform only safe
mode switches unless a new -f (force) option is passed.
** Also affects: kbd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
That is when updating the console-setup package, yes. As mentioned on
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1508146/comments/73 that's because its config script passes
--force to setupcon, it really shouldn't, as mentioned there
--
You received this bug notification because
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: console-setup (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: console-setup (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
This affects me too, after updating the following packages:
libreoffice-style-breeze:amd64 (1:6.0.7-0ubuntu0.18.04.2,
1:6.0.7-0ubuntu0.18.04.5),
libreoffice-math:amd64 (1:6.0.7-0ubuntu0.18.04.2, 1:6.0.7-0ubuntu0.18.04.5),
update-manager-core:amd64 (1:18.04.11.9, 1:18.04.11.10),
** Changed in: console-setup (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: console-setup (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
I'm on Kubuntu and it was also affected by this issue after installing
the latest updates although for me it was Super+Arrow keys that change
VT (rather than Alt+KEY as described in the issue). As mentioned,
running: `sudo kbd_mode -s` resolved it.
--
You received this bug notification because
Started experiencing this in Ubuntu 18.04 on two different computers,
since a few days ago, presumably because of a package upgrade ; both
users are using the Unity shell (if it makes any difference; I didn't
try another one) ; disabling those shortcuts is important because
Alt+arrow are very
Me too on Ubuntu 18.04.2 LTS. Dell XPS-13 laptop shipped with Ubuntu.
I can't click "Yes, it affects me" on this page -- I keep getting a
timeout error. Any idea how to fix the timeout error and add my name?
--
You received this bug notification because you are a member of Desktop
Packages,
It's back! Me too on Ubuntu 18.04.2 LTS.
Maybe it was package keyboard-configuration_1.178ubuntu2.8_all.deb?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt+KEY
Have the same problem. Ubuntu 18.04 LTS
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
switch
Experiencing the same thing lately on Ubuntu 18.04.2 LTS ...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or
Thanks for the patch. Comment #67 seems to have a more detailed patch
but even that's out of date now. Someone will need to rewrite the patch
to suit Ubuntu 19.10/19.04 and then older versions after that.
** Changed in: console-setup (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
Xorg can't do anything about intercepting Alt-key, it's the kernel which
takes the shortcut away.
Again, as mentioned on https://bugs.launchpad.net/ubuntu/+source
/console-setup/+bug/520546/comments/66
«
proposed fix:
53 matches
Mail list logo
