[Kernel-packages] [Bug 1845214] Re: Keyboard NumLock indicator turns off on connecting another keyboard
I've noticed the same thing… both on Ubuntu, and lately on Gentoo as well, so I'm thinking maybe something in udev / kernel has changed? I use FVWM2 as my desktop on both OSes. My desktop runs Ubuntu 20.04 (AMD64). On my laptop (Panasonic CF-53, which runs Gentoo) it's particularly insidious, plugging in the YubiKey (mine's a 5C which I use with a USB- A-C adaptor) causes NumLock to be turned on, and if your PIN code uses letters over the right-side of the keyboard, guess what? You're unwittingly typing numbers now! Cue confusion when the YubiKey rejects the PIN you just entered. I've locked myself out of the YubiKey once because of that -- had to go in with the PUK and unlock it. My desktop doesn't seem to secretly turn NumLock on; the state is retained, just the LED turns off. If we can figure out what mechanism is doing it in Ubuntu, I'll chase up what's doing it Gentoo-side. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1845214 Title: Keyboard NumLock indicator turns off on connecting another keyboard Status in linux-meta-hwe package in Ubuntu: Confirmed Bug description: My USB HID keyboard has NumLock LED. It usually works fine. However, when I plug in YubiKey (hardware security token, it is also identified as a USB HID keyboard) NumLock LED turns OFF, but the NumLock feature is still ON. If I press NumLock, NumLock becomes disabled (it is displayed by DE and checked by typing). If I press NumLock again, NumLock turns back ON with LED. I originally thought that issue could be related to the fact that YubiKey does not have a NumLock led, so it reports LED as nonexisting and stuff happens. However, today I tried attaching another USB keyboard: LED on first one still goes off; but LED on second goes ON immediately after plugging in. Pressing NumLock once disables NumLock and LED on first keyboard, as with YubiKey; pressing again enabled NumLock and both LEDs. Seems like my user session (on vt2) is running Xorg while login screen (on vt1, the one that allows to choose a user and that you see before first login) is running Wayland; both are faulty. Because of this, I believe the issue is in the kernel. However, I am not sure, so you can ask for way more reports to be added, I will add those. Reproducing should be pretty easy with any cheap USB keyboards, nothing special is used by me. Operating system: Ubuntu 18.04 Bionic Beaver. Linux kernel: 18.04 HWE, 5.0.0-25. However, I think I saw this blinking before upgrading to HWE. DE: GNOME. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04 5.0.0.29.86 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 24 16:52:08 2019 SourcePackage: linux-meta-hwe UpgradeStatus: Upgraded to bionic on 2018-09-03 (386 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1845214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1313497] Re: USB keyboard unresponsive on fresh install
On 29/04/14 18:35, Stefan Bader wrote: Hi Stuart, On 29.04.2014 05:23, Stuart Longland wrote: Did the linux-3.13.0-24-generic package miss out a few files or are they in a separate package the installer forgot to install? That could be and depends on you seed. For bare-metal you should have seleced linux-server for d-i base-installer/kernel/image. In general the linux-image should not be picked directly as we indeed split up the modules into the minimum for virtual machines and a rest. linux-server, linux-generic, and linux-virtual are all meta-package which will install the right set of packages and also make sure you see kernel updates. server and generic nowadays is actually the same. So you could have installed without those and now miss the linux-image-extra package. Ahh, I have in my preseed: # The kernel image (meta) package to be installed; none can be used if no # is to be installed. d-i base-installer/kernel/image string linux-image-virtual Perhaps I mis-interpreted the intent of virtual. Is there a document that describes the image options in detail that one could refer to? Perhaps mention of it should be made in the preseed examples? It's easy to miss the bit about it being for virtual instances in the dpkg -l output, which is how I installed the image: root@host:~# dpkg -l linux-image-virtual 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) ||/ NameVersion Architecture Description +++-===--- ii linux-image-virtual 3.13.0.24.29 amd64This package will always depend on the latest minima I shall amend my preseed scripts and perhaps we can work on the documentation (which either is lacking or I missed seeing it). Regards, -- Stuart Longland Systems Engineer _ ___ \ /|_) | T: +61 7 3535 9619 \/ | \ | 38b Douglas StreetF: +61 7 3535 9699 SYSTEMSMilton QLD 4064 http://www.vrt.com.au -- 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/1313497 Title: USB keyboard unresponsive on fresh install Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I just did a fresh install of Ubuntu 14.04 LTS onto a machine here. During the installation (which is pre-seeded) and in the BIOS, my keyboard works flawlessly. However, the moment I boot the machine up, I note the keyboard is not operational. Naturally, I discover this *after* buggering up my networking settings. The offending package is linux-image-3.13.0-24-generic version 3.13.0-24.46. At one point I noticed an irq 16: nobody cared error message. Due to there being no network connectivity, I was unable to capture the message displayed. The output from `dmesg` (see attachment dmesg.txt) suggests it does see USB and the keyboard, but plugging the keyboard into any of the available ports and pressing keys has no effect on the console. The machine is a rack-mounted server, intended to run headless. The motherboard is an Intel DQ77MK. No peripheral cards are installed. root@host:~# cat /proc/version_signature Ubuntu 3.13.0-24.46-generic 3.13.9 root@host:~# lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09) Subsystem: Intel Corporation Device [8086:2035] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information: Len=0c ? 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2035] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at f780 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at e000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at f000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Address: Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1
[Kernel-packages] [Bug 1313497] UdevDb.txt
-9f-0f Kernel driver in use: e1000e 03:03.0 FireWire (IEEE 1394) [0c00]: LSI Corporation FW322/323 [TrueFire] 1394a Controller [11c1:5811] (rev 70) (prog-if 10 [OHCI]) Subsystem: Intel Corporation Device [8086:2035] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (3000ns min, 6000ns max), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at f7c0 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- I've had to do a rebuild already because of this bug (no console access then loosing network access pretty much means game over), so I can confirm 100% repeatability thus far. For interests' sake, the netboot image I used to perform this installation was downloaded this morning, and has the following checksums: 01f16ef8b1f11b29bd0ce940b0aad8ea950f5346 trusty/amd64/linux fbb74f8e7d0c1e2ce4b027fc4a0e1aca54cf0fe5 trusty/amd64/initrd.gz If there's any additional information that would be useful, please let me know. Regards, Stuart Longland --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 28 14:35 seq crw-rw 1 root audio 116, 33 Apr 28 14:35 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=c087705d-cbe4-4546-bfcd-436edfe047c8 IwConfig: Error: [Errno 2] No such file or directory Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=8c972a72-4f98-4043-b9a1-d409f02d6dbc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/20/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: MKQ7710H.86A.0054.2012.1120.1444 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ77MK dmi.board.vendor: Intel Corporation dmi.board.version: AAG39642-500 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrMKQ7710H.86A.0054.2012.1120.1444:bd11/20/2012:svn:pn:pvr:rvnIntelCorporation:rnDQ77MK:rvrAAG39642-500:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
