Hello Yao, or anyone else affected, Accepted xorg-server into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:21.1.3-2ubuntu2.8 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xorg-server (Ubuntu) Status: In Progress => Fix Committed -- 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/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching Status in OEM Priority Project: New Status in X.Org X server: New Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Jammy: Fix Committed Status in xorg-server source package in Kinetic: Fix Committed Bug description: [ Impact ] * This change will force update keyboard LED status after calling EnableDevice, in order to resolve LED status not syncing after switching VT to a X session. * This also fixes the issue with NVIDIA driver and Xorg, that after resuming from suspend the keyboard LED is always off. [ Test Plan ] 1. Log onto an GNOME Xorg session (KDE Kwin worked this issue around) 2. Turn on NumLock on the keyboard 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop NumLock LED should be on after switching back to the desktop [ Where problems could occur ] * The changes are to push status to the device when enabling it regardless of actual keyboard state change, therefore switching between VTs and adding/removing keyboard/mouse/xinput devices should be affected by this change. [ Original Report ] Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs. This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04) To reproduce: 1. Log on a X session desktop (GNOME Xorg for example) 2. Turn on NumLock 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop Expected: NumLock LED should be on Actual: NumLock LED is off, but functions like NumLock is on. If NumLock is pressed the LED turns off as well as the function. If CapsLock is pressed the LED states sync back (LED turns back on). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
