From: LeamHall <LeamHall@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Bug: udevd error calling EVIOCSKEYCODE
Date: Thu, 20 Jan 2022 13:01:15 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35133@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
New issue by LeamHall on void-packages repository
https://github.com/void-linux/void-packages/issues/35133
Description:
### System
* xuname:
Void 5.13.19_1 x86_64 GenuineIntel notuptodate rFF
### Expected behavior
No udev errors on boot.
### Actual behavior
[ 11.136077] udevd[658]: Error calling EVIOCSKEYCODE on device node '/dev/input/event2' (scan code 0xc022d, key code 103): Invalid argument
[ 11.136651] udevd[658]: Error calling EVIOCSKEYCODE on device node '/dev/input/event2' (scan code 0xc022e, key code 108): Invalid argument
### Steps to reproduce the behavior
dmesg |grep -i error
next reply other threads:[~2022-01-20 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 12:01 LeamHall [this message]
2022-06-22 2:14 ` github-actions
2022-07-07 2:14 ` [ISSUE] [CLOSED] " github-actions
2024-05-22 12:26 ` lukeflo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35133@inbox.vuxu.org \
--to=leamhall@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).