![]() ![]() x86/fpu: xstate_offset: 576, xstate_sizes: 256 x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' ![]() x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Lsusb (it's the same after booting and after reconnecting the yubikey) Kernel 5.8.14-arch1-1, Gnome 3.38.1, updated all arch packages around lunch break today. Intel i7-8700K (overclocked to 5,1GHz on all cores), Asus Prime Z-390A, 16G Ram, Arch boots from Samsung NVME which is formatted with Btrfs. Can it be a bug in KeepassXC? I personally don't think so because it works after reconnecting the yubikey and i didn't found similar bugs on their bugtracker. Can it be a bug in gnome? Who knows, because i only use gnome. Can it be a bug in some sort of library like i.e. But a search for 'linux kernel submodule list' just gives me links to the 'git submodule' command (search engines are sometimes really dumb), so where would i even get a list of the submodules of the linux kernel to at least guess which one it could be? Theoretically it could be usb, usbhid or some input module. Can it be a bug in the linux kernel? If so i just read i need to find out in which submodule of the kernel it is. So please can you help me where to file a bug that keepassxc doesn't show up in keepassxc after system startup? Since i needed hours to find this bug in gnome which only occurs because of this other bug with yubikey and keepassxc, i finally want to do something against it: I fixed this with a 2nd autostart script, which just executes the commands from the bug report. These xkb options are there to apply a custom keyboard layout that modifies the keyboard exactly as i want it (eject key is now F20 to show/hide the top-down terminal like guake or tilix, easier german umlauts, F1-F5 work without Fn key and F6-F12 need Fn Key so that they work primarly as media keys). , which just reconnects the whole usb 3 controller and it works fine afterwards.īut today i updated to Gnome 3.38 and it has this bug where it doesn't automatically apply the xkb options (org/gnome/desktop/input-sources/xkb-options in dconf-editor) after connecting a keyboard (and the keyboard gets reconnected from the above script.). I have this bug since at least 2 years and didn't really bothered because i automated this via a autostart (~/.config/autostart) scriptĮcho -n "0000:00:14.0" | tee /sys/bus/pci/drivers/xhci_hcd/unbind & echo -n "0000:00:14.0" | tee /sys/bus/pci/drivers/xhci_hcd/bind In this state where keepassxc doesn't find the yubikey, it is shown by dmesg and lsusb and even spits out a password when pressing the golden contact on the yubikey. It works when the yubikey is connected directly to one of the front ports of the pc, but it's much more convenient having the yubikey on the back of the apple keyboard since i just have to put my finger under it and touch the golden contact of the yubikey to confirm an authentication request. I have to plug the yubikey out and in again, then keepassxc finds it.Īfter a reboot of the system, the same error occurs. When the yubikey is connected to a USB Hub (either the one in my Dell U2515H Monitor or the Apple Aluminium Keyboard which has 2 USB ports on it's back), keepassxc doesn't find the yubikey after system startup (even after repeatedly pressing the refresh button) It's slot 2 is configured for SHA-1 encryption which is used by KeepassXC (password vault) for 2FA to the keepassxc database. I have a Yubikey 4 Nano (usb security key for 2FA). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |