Yeah, helped, but if you are in dual boot, like Windows near Linux,
every time you boot Windows, and then Linux, the fn keys don't work, so
I have to do every time the reset power.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I had the same issue with HP Probook G8, bought this year.
Fn key worked fine when I installed Ubuntu 20.04, but later they started
behaving as described here. The brightness buttons (Fn F3 and Fn F4) started
turning on and off the digital mic.
I performed the hard reset as somebody suggested
Did u remove the battery first?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
Title:
Multiple keys have same keycode on HP ProBook 450 G6
To manage notifications about this bug go to:
Hi guys,
I'm suffering from the same issue with controlling back light through Fn+F3/F4.
Finally, I found a method to fix the problem unexpectedly!
As long as power reset your HP laptop, it will be fixed!
Note that my laptop is HP elitebook 845G7 with AMD 4700U version.
I think it will work for
I'm having the same issue with function keys for brightness on the HP
Elite Dragonfly G2. F3 and F4 both map to muting the microphone. This is
a firmware bug. It happens on the latest version of Ubuntu and on Fedora
34. Really, this needs to be fixed. If someone would take a look at the
firmware,
Hello,
I have the same issue on my HP Elitebook 850 G6.
Fn+F3 and Fn+F4 change the microphone mute status and not the LCD
brightness as they should. I could resolve this by installing a new BIOS
temporarily. But everytime I boot Windows 10 on my dual boot system it
comes back.
I will try the
Hello!
Device: HP Elite Book 840 g6, BIOS version latest
Distributor ID: Linuxmint
Description:Linux Mint 20.1
Release:20.1
Codename: ulyssa
Absolutely same problem F3-F4 (brightness up-down) - action doesn't
work.
button/f20 F20 0080 K # F3 - brightness down
release: 20.04, Focal Fossa, xubuntu
Device: HP ProBook 440 G7 2021
The same problem with F3/F4 brightness button.
#sudo acpi_listen
button/f20 F20 0080 K - F3 pressed in real (wrong)
button/f20 F20 0080 K - F4 pressed in real (wrong)
button/f20 F20 0080
as of April 2021, 01.08.02 is the latest BIOS available
https://support.hp.com/au-en/drivers/selfservice/hp-probook-440-g7
-notebook-pc/29090063 and the bug is still showing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seems like this issue caused by HP's fn key driver for windows
I own 440 G6 and had this issue for a long time
but mystically it dissapeared once after my laptop was discharged for a long
time
but after win10 installation (2nd ssd with it died, so i installed new one and
reinstalled w10) it
The Power Resest suggested by https://launchpad.net/~ssmirnoff worked perfectly
for me in a
HP Elitebook x360 1030 G3
And fixed lost laptop speaker audio after plugging and unplugging headphones,
too!
Thanks Sergey!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ok, this problem comes back from time to time. Reset of BIOS settings
didn't help. So, only updating BIOS (even if to the same version) works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
I had the same issue on HP ProBook 440 G7 and flashing the latest BIOS
has resolved this issue.
$ sudo dmidecode -s bios-version
S71 Ver. 01.06.00
But, now I think, that reset BIOS setting on defaults may also help in
that situation...
--
You received this bug notification because you are a
Seems to be hardware issue. Flashing latest BIOS haven’t resolved the
issue in my case, but power reset have: https://support.hp.com/us-
en/document/c01684768
HP Probook 450 G6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also have same problem on my HP ProBook 450 G6.
Using sudo showkey -k gave me these results:
- pressing Fn+F3: keycode 190 press keycode 190 release
- pressing Fn+F4: keycode 190 press keycode 190 release
- pressing Fn+F8: keycode 190 press keycode 190 release
--
You received this bug
Sounds similar to what I reported here:
https://bugzilla.kernel.org/show_bug.cgi?id=208347
** Bug watch added: Linux Kernel Bug Tracker #208347
https://bugzilla.kernel.org/show_bug.cgi?id=208347
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
Title:
Multiple keys have same keycode on HP ProBook 450 G6
To manage notifications
I found strange thing.
I upgraded BIOS to 01.11.10 thru BIOS Upgrade - booted Ubuntu - keys
works ok - reboot to Windows 10 - works ok - reboot to Ubuntu - bug is
back
Then I downgreaded BIOS to 01.10.00 and similar problem. Windows is the
evil. But how to prevent it? I need them for some things
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
Title:
Multiple keys have same keycode on HP ProBook 450 G6
To manage notifications
I support the findings of Jakub.
The source of the hp_wmi also suggests it is responsible for the brightness
shortcuts:
{ KE_KEY, 0x02, { KEY_BRIGHTNESSUP } },
{ KE_KEY, 0x03, { KEY_BRIGHTNESSDOWN } },
On my machine, running dmesg | grep wmi, I get:
[6.422405] hp_wmi:
The same for me, HP 450 G6, newest firmware installed through Windows.
After Googling around I wonder whether the problem might be in the "hp_wmi"
module? It might be responsible for handling those shortcuts for brightness,
but I have no idea how to debug it further. See:
I have HP 450 G6 as well.
Installing the latest firmware as described unfortunately did NOT fix the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
Title:
Multiple keys have same
I have HP 450 G6 as well.
Installing the latest firmware as described unfortunately did NOT fix the issue.
Just to clarify something with the others that have experienced and
reported the issue ...
Please confirm that you are pressing Fn+F3/F4/F8 while the little led on the Fn
key is lit.
If
I confirm, that updating BIOS to version 01.10.00 released in January
2020 fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
Title:
Multiple keys have same keycode on HP
I solved this problem.
This problem is due to old firmware.
I creat USB with frimware update on WIndows 10 and I followed the
directions.
Last frimware: https://ftp.hp.com/pub/softpaq/sp101001-101500/sp101220.exe
Instruction create USB and update notebook without Windows:
Distro release: Ubuntu 18.04.03 LTS
Device: HP ProBook 440 G6
The same problem with F3/F4 brightness button.
#sudo acpi_listen
button/f20 F20 0080 K - F3 pressed in real (wrong)
button/f20 F20 0080 K - F4 pressed in real (wrong)
button/f20 F20 0080 K - F8
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
Title:
Multiple
Sorry, not HP Probook 450 G5 but G6!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
Title:
Multiple keys have same keycode on HP ProBook 450 G6
To manage notifications about this bug go to:
Distro release: Kubuntu 18.04.03 LTS
The same with my HP Probook 450 G5. Latest Bios R71 01.08.03
The keys work normal with Win 10 Pro, but after switching to Kubuntu,
all three keys send the same keycode 198 instead of
232 BrightnessDown
233 BrightnessUp
--
You received this bug notification
See also: https://wiki.ubuntu.com/Hotkeys/Troubleshooting
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
Title:
Multiple keys have same keycode on HP ProBook 450 G6
To manage notifications
For apport commands to work you need to assign a package. Assigning a
package ensures that the bug report reaches the right developers.
Reporting against the Ubuntu project is not advised unless absolutely
necessary.
See https://wiki.ubuntu.com/Bugs/FindRightPackage
--
You received this bug
** Attachment added: "dmesg log"
https://bugs.launchpad.net/ubuntu/+bug/1841039/+attachment/5283961/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
Title:
Multiple keys
** Attachment added: "system info"
https://bugs.launchpad.net/ubuntu/+bug/1841039/+attachment/5283960/+files/report.apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
Title:
Multiple
you could try to purge apport and install it back afterwards, maybe that could
solve
your issue with apport-collect.
Your bug sounds like its ACPI related, hence why the developers would need more
info
and your dmesg logs.
--
You received this bug notification because you are a member of
the apport-collect didn't work for me, so I saved apport to file and
uploaded
bios is up do date
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841039
Title:
Multiple keys have same keycode on HP
Thank you for reporting this Bug and make Ubuntu better!
To report bugs please use: ubuntu-bug packagename (linux for example) in the
future
so relevant systeminfo & logs are pulled into the bug and developers can debug
a better way.
You can still apport-collect 1841039 in this stage to pull
36 matches
Mail list logo
