https://bugs.kde.org/show_bug.cgi?id=490033
BOF <bugs_kde_org.5.k...@spamgourmet.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Ever confirmed|1 |0
Status|NEEDSINFO |REPORTED
--- Comment #7 from BOF <bugs_kde_org.5.k...@spamgourmet.com> ---
(In reply to Nate Graham from comment #6)
> This seems like it might be a hardware or firmware issue on your machine,
> BOF.
>
> Can you check to see if it reproduces in a new clean user account on the
> same machine with no customizations?
I have no idea how I would test this issue with the same device, but different
firmware.
Further tests:
- I tested the bug on an ASUS ROG Strix G15 laptop (Not the bug report laptop).
This laptop has dedicated single-use buttons to increase/decrease the volume.
With this laptop I can not reproduce this bug. It's like TraceyC described it:
When held down the volume changes, when released the change stops.
- I tested the bug on the Lenovo ThinkBook 16 G6 ABP (The bug report laptop),
but with with a live USB using _neon-user-20240725-0828.iso_ (latest user build
as of today). I get the exact same problem. It doesn't matter if I use FnLock
or not. The strange thing: With the 'clean' install of KDE 6.1 I have the
system sounds back again and I hear that the volume increase is still ongoing
after I release the button. The change only stops when I press a button. Rapid
pressing of the button has the exact same effect as holding it down.
General comments:
- No, my buttons are not stuck as there would certainly *have* to be an effect
on the rest of the system. If a button in mixed use is stuck, it's not only
stuck for one application. As I'm using Krunner with Alt+F2 and rename files in
Dolphin with F2 I can hardly imagine that any button would be stuck.
Furthermore the F2 as well as the F3 button would have to be stuck as they show
the exact same behaviour.
- I don't think that it's the firmware or hardware of my system as this problem
started to occur after an update (Though I have no idea which update it was).
I'm almost certain that this bug did not occur under 6.0, but I have no idea
where I would get an old version of KDEneon to test it.
(-> I will test it with other distros (KDE + others) as well and see if there
is a problem with them as well as they should suffer from the same problem if
it was my hardware or my firmware)
--
You are receiving this mail because:
You are watching all bug changes.
