Fn keys doesn't work completely.I can only use it to control voulume

Bug #1797867 reported by blurhy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I ran `acpi_listen`.It doesn't output anything when I press a fn key that is not F1/F2/F3 (voulume)
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: blurhy 2761 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-10-10 (4 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc.
 Bus 001 Device 003: ID 13d3:5666 IMC Networks
 Bus 001 Device 002: ID 8087:0a2b Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. FX503VD
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-10-generic N/A
 linux-backports-modules-4.18.0-10-generic N/A
 linux-firmware 1.175
Tags: cosmic
Uname: Linux 4.18.0-10-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/03/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX503VD.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX503VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: FX
dmi.product.name: FX503VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
---

blurhy (blurhy)
tags: added: fn-keys
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1797867

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
blurhy (blurhy) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected cosmic
description: updated
Revision history for this message
blurhy (blurhy) wrote : CRDA.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : CurrentDmesg.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : IwConfig.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : Lspci.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcEnviron.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcInterrupts.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcModules.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : PulseList.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : RfKill.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : UdevDb.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : WifiSyslog.txt

apport information

description: updated
Revision history for this message
blurhy (blurhy) wrote : AlsaInfo.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : CRDA.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : CurrentDmesg.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : IwConfig.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : Lspci.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcEnviron.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcInterrupts.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcModules.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : PulseList.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : RfKill.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : UdevDb.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : WifiSyslog.txt

apport information

description: updated
Revision history for this message
blurhy (blurhy) wrote : AlsaInfo.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : CRDA.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : CurrentDmesg.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : IwConfig.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : Lspci.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcEnviron.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcInterrupts.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : ProcModules.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : PulseList.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : RfKill.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : UdevDb.txt

apport information

Revision history for this message
blurhy (blurhy) wrote : WifiSyslog.txt

apport information

description: updated
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
blurhy (blurhy) wrote :

ok,upgraded
acpi_listen outputs nothing.
And my nvidia doesn't work now,uh.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Does this issue still happen?

To post a comment you must log in.