Github messages for voidlinux
 help / color / mirror / Atom feed
From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] acpid clogs syslog with arrow key events
Date: Tue, 31 Jan 2023 18:28:44 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41994@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

New issue by kruceter on void-packages repository

https://github.com/void-linux/void-packages/issues/41994

Description:
### Is this a new report?

Yes

### System Info

Void 5.15.85_1 x86_64-musl GenuineIntel uptodate hold rFFFFFFFFFFFF

### Package(s) Affected

acpid-2.0.34_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

The package is not (?) supposed to clog syslog with undefined arrow keys.

### Actual behaviour

`acpid` uses `/etc/acpid/handler.sh` to flood syslog with `ACPI group/action undefined: button/<arrow_key> / <DIRECTION>`.

### Steps to reproduce

Use acpid as a runit service.

Reproduce the behavior with `extrace` in case you do not have any system loggers installed.

Now, abuse button keys and see something like this below:

```
19226 /bin/sh /etc/acpi/handler.sh button/down DOWN 00000080 00000000 K
19227 cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
19228 cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
19229 logger 'ACPI group/action undefined: button/down / DOWN'
```

             reply	other threads:[~2023-01-31 17:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 17:28 kruceter [this message]
2023-01-31 18:28 ` gtryujb
2023-02-09 12:30 ` [ISSUE] [CLOSED] " leahneukirchen

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-41994@inbox.vuxu.org \
    --to=kruceter@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).