linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: bp@alien8.de
Subject: [Bug 216933] New: brightness keys not working on Lenovo ideapad 3
Date: Sun, 15 Jan 2023 14:19:19 +0000	[thread overview]
Message-ID: <bug-216933-6385@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=216933

            Bug ID: 216933
           Summary: brightness keys not working on Lenovo ideapad 3
           Product: Platform Specific/Hardware
           Version: 2.5
    Kernel Version: 6.1.5
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: x86-64
          Assignee: platform_x86_64@kernel-bugs.osdl.org
          Reporter: tuxuser@quantentunnel.de
        Regression: No

System: Lenovo ideapad 3
OS: openSUSE Leap 15.4, all updates installed
Kernel: 6.1.5, 5.14.21-150400.38-default

Brightness keys are not working. When pressing these in kde plasma no
brightness increase / decrease indicator is shown.
The brightness system itself is working: When changing the brightness using the
plasma battery applet, the brightness changes as expected.

Changing to runlevel 3 showkey and evtest don't respond to pressing these keys.
They only respond to other keys.
evtest displays
/dev/input/event1 is Video Bus
Here it displays Event code 224 for KEY_BRIGHTNESSDOWN and Event code 225 for
KEY_BRIGHTNESSUP. But pressing the buttons leads to no response.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

                 reply	other threads:[~2023-01-15 15:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-216933-6385@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=bp@alien8.de \
    /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).