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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
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 Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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 Kernel
Packages, which is subscribed to linux 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/520546
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 Kernel
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 Kernel
Packages, which is subscribed to linux 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 Kernel
Packages, which is subscribed to linux 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: xorg-server (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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 Kernel
Packages, which is subscribed to linux 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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 Kernel
Packages, which is subscribed to linux 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 Kernel
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 Kernel
Packages, which is subscribed to linux 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
switch from
Experiencing the same thing lately on Ubuntu 18.04.2 LTS ...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted
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:
Also assigned to xorg-server, because Xorg should be intercepting
Alt+KEY. If Xorg fails to do so and somehow the key events get sent to
the VT then we get the unwanted VT's interpretation of Alt+KEY.
** Description changed:
+ WORKAROUND:
+
+ sudo kbd_mode -s
+
+ ORIGINAL DESCRIPTION:
+
I'm
31 matches
Mail list logo
