[Kernel-packages] [Bug 1784008] Re: brightness keys incorrectly mapped for ProBook 455 G5

2018-09-06 Thread James Buren
Issue resolved by BIOS update.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1781763] Re: HP ProBook 455 G5 needs mute-led-gpio fixup

2018-08-07 Thread James Buren
Tested. It works.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781763

Title:
  HP ProBook 455 G5 needs mute-led-gpio fixup

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Justification ==
  The audio mute LED does not work on HP ProBook 455 G5, James Buren found out 
this issue can be fixed by applying an existing cxt5066_fixups quirk.

  == Test ==
  After adding the ID to the patch_conexant.c, the audio mute LED works as 
expected. The reporter has also confirmed that this issue will gone with a 
patched test kernel.

  == Regression Potential ==
  Very low.
  Just a small quick with ID specific to this laptop was added.

  --

  I noticed that the audio LEDs on this model's keyboard were not
  functioning. After a great deal of research, I found I needed to patch
  the kernel to apply an existing fixup for my particular model. I built
  a custom kernel to test it, and it does indeed fix my problem. I would
  appreciate it if this patch could be included in a future kernel
  build. Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781763/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] Re: brightness keys incorrectly mapped for ProBook 455 G5

2018-08-01 Thread James Buren
Done. https://bugzilla.kernel.org/show_bug.cgi?id=200699

** Bug watch added: Linux Kernel Bug Tracker #200699
   https://bugzilla.kernel.org/show_bug.cgi?id=200699

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] Re: brightness keys incorrectly mapped for ProBook 455 G5

2018-07-31 Thread James Buren
I did some further testing with ATKBD's softraw parameter to see how it
changed showkey's output. Here are my findings.

When ATKBD's softraw parameter is set to 1, showkey -s says that all 3
keys map to this scancode sequence: 0x5a 0xda

When ATKBD's softraw parameter is set to 0, showkey -s shows that the
brightness keys map to this scancode sequence: 0xe0 0x01 0xe0 0x81,
while the microphone mute key maps to this scancode sequence: 0xe0 0x01
0xe0 0x81 0xc2

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] Re: brightness keys incorrectly mapped for ProBook 455 G5

2018-07-27 Thread James Buren
Did this issue start happening after an update/upgrade? No.

Was there a prior kernel version where you were not having this
particular problem? No.

Also, I finished testing the mainline kernel build, version 4.18-rc6.
The issue is still present. I have marked the bug as requested.


** Tags added: kernel-bug-exists-upstream

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] Re: brightness keys incorrectly mapped for ProBook 455 G5

2018-07-27 Thread James Buren
acpidump binary output

** Attachment added: "AcpiTables.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+attachment/5168641/+files/AcpiTables.tar.xz

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] Re: brightness keys incorrectly mapped for ProBook 455 G5

2018-07-27 Thread James Buren
acpidump output

** Attachment added: "AcpiTables.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+attachment/5168640/+files/AcpiTables.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] RfKill.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1784008/+attachment/5168636/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] ProcCpuinfoMinimal.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1784008/+attachment/5168631/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] ProcCpuinfo.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1784008/+attachment/5168630/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] ProcEnviron.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1784008/+attachment/5168632/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] CurrentDmesg.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1784008/+attachment/5168626/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] AlsaInfo.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1784008/+attachment/5168624/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] CRDA.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1784008/+attachment/5168625/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] Lsusb.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1784008/+attachment/5168629/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] Lspci.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1784008/+attachment/5168628/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] ProcModules.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1784008/+attachment/5168634/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] ProcInterrupts.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1784008/+attachment/5168633/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] UdevDb.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1784008/+attachment/5168637/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] PulseList.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1784008/+attachment/5168635/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] IwConfig.txt

2018-07-27 Thread James Buren
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1784008/+attachment/5168627/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784008

Title:
  brightness keys incorrectly mapped for ProBook 455 G5

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.

  I did a fair amount of testing to arrive at this conclusion.
  acpi_listen reports the brightness keys as F20, same with my
  microphone mute key. showkey reveals that the scan codes are identical
  for both the brightness keys and the microphone mute key. On the off-
  chance it was some kind of userspace issue, I also performed these
  tests from other distributions, both systemd and non-systemd variants.
  The same issue is present there as well.

  The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ryuo   3305 F pulseaudio
   /dev/snd/controlC0:  ryuo   3305 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: HP HP ProBook 455 G5
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q84 Ver. 01.01.01
  dmi.board.name: 836E
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 03.16.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 455 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1784008] [NEW] brightness keys incorrectly mapped for ProBook 455 G5

2018-07-27 Thread James Buren
Public bug reported:

Hello. For unknown reasons, the brightness up and brightness down keys
on my ProBook 455 G5 are being mapped to F20, which is the microphone
mute key. Because of this, the screen brightness cannot be adjusted by
pressing the brightness keys. However, the screen brightness can still
be adjusted by software such as panel applets.

I did a fair amount of testing to arrive at this conclusion. acpi_listen
reports the brightness keys as F20, same with my microphone mute key.
showkey reveals that the scan codes are identical for both the
brightness keys and the microphone mute key. On the off-chance it was
some kind of userspace issue, I also performed these tests from other
distributions, both systemd and non-systemd variants. The same issue is
present there as well.

The only conclusion I am left with is that the kernel is not reporting the keys 
correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
--- 
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ryuo   3305 F pulseaudio
 /dev/snd/controlC0:  ryuo   3305 F pulseaudio
CurrentDesktop: MATE
DistroRelease: Ubuntu 18.04
MachineType: HP HP ProBook 455 G5
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-29-generic N/A
 linux-backports-modules-4.15.0-29-generic  N/A
 linux-firmware 1.173.1
StagingDrivers: r8822be
Tags:  bionic staging
Uname: Linux 4.15.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: kvm sudo
WifiSyslog:
 
_MarkForUpload: True
dmi.bios.date: 03/30/2018
dmi.bios.vendor: HP
dmi.bios.version: Q84 Ver. 01.01.01
dmi.board.name: 836E
dmi.board.vendor: HP
dmi.board.version: KBC Version 03.16.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ84Ver.01.01.01:bd03/30/2018:svnHP:pnHPProBook455G5:pvr:rvnHP:rn836E:rvrKBCVersion03.16.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 455 G5
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected bionic staging

** Tags added: apport-collected bionic staging

** Description changed:

  Hello. For unknown reasons, the brightness up and brightness down keys
  on my ProBook 455 G5 are being mapped to F20, which is the microphone
  mute key. Because of this, the screen brightness cannot be adjusted by
  pressing the brightness keys. However, the screen brightness can still
  be adjusted by software such as panel applets.
  
  I did a fair amount of testing to arrive at this conclusion. acpi_listen
  reports the brightness keys as F20, same with my microphone mute key.
  showkey reveals that the scan codes are identical for both the
  brightness keys and the microphone mute key. On the off-chance it was
  some kind of userspace issue, I also performed these tests from other
  distributions, both systemd and non-systemd variants. The same issue is
  present there as well.
  
- The only conclusion I am left with is that the kernel is not reporting
- the keys correctly. I haven't been able to find any other reports of a
- similar situation, so I am unsure how to proceed from here. Please
- advise me on how I can help you find a solution to my issue. Thank you.
+ The only conclusion I am left with is that the kernel is not reporting the 
keys correctly. I haven't been able to find any other reports of a similar 
situation, so I am unsure how to proceed from here. Please advise me on how I 
can help you find a solution to my issue. Thank you.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  ryuo   3305 F pulseaudio
+  /dev/snd/controlC0:  ryuo   3305 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 18.04
+ MachineType: HP HP ProBook 455 G5
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/root@/boot/vmlinuz-4.15.0-29-generic 
root=ZFS=username-laptop:0/root ro quiet splash elevator=noop
+ ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-29-generic N/A
+  linux-backports-modules-4.15.0-29-generic  N/A
+  linux-firmware 1.173.1
+ StagingDrivers: r8822be
+ Tags:  bionic staging
+ Uname: Linux 

[Kernel-packages] [Bug 1781763] Re: HP ProBook 455 G5 needs mute-led-gpio fixup

2018-07-27 Thread James Buren
Hello. The patched kernel fixes the issue as I expected it would.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781763

Title:
  HP ProBook 455 G5 needs mute-led-gpio fixup

Status in linux package in Ubuntu:
  In Progress

Bug description:
  I noticed that the audio LEDs on this model's keyboard were not
  functioning. After a great deal of research, I found I needed to patch
  the kernel to apply an existing fixup for my particular model. I built
  a custom kernel to test it, and it does indeed fix my problem. I would
  appreciate it if this patch could be included in a future kernel
  build. Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781763/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1781763] Re: HP ProBook 455 G5 needs mute-led-gpio fixup

2018-07-14 Thread James Buren
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781763

Title:
  HP ProBook 455 G5 needs mute-led-gpio fixup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed that the audio LEDs on this model's keyboard were not
  functioning. After a great deal of research, I found I needed to patch
  the kernel to apply an existing fixup for my particular model. I built
  a custom kernel to test it, and it does indeed fix my problem. I would
  appreciate it if this patch could be included in a future kernel
  build. Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781763/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1781763] [NEW] HP ProBook 455 G5 needs mute-led-gpio fixup

2018-07-14 Thread James Buren
Public bug reported:

I noticed that the audio LEDs on this model's keyboard were not
functioning. After a great deal of research, I found I needed to patch
the kernel to apply an existing fixup for my particular model. I built a
custom kernel to test it, and it does indeed fix my problem. I would
appreciate it if this patch could be included in a future kernel build.
Thank you.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Attachment added: "Adds correct entry to existing fixup table"
   
https://bugs.launchpad.net/bugs/1781763/+attachment/5163740/+files/probook-455-g5-mute-gpio-led-fixup.patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781763

Title:
  HP ProBook 455 G5 needs mute-led-gpio fixup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I noticed that the audio LEDs on this model's keyboard were not
  functioning. After a great deal of research, I found I needed to patch
  the kernel to apply an existing fixup for my particular model. I built
  a custom kernel to test it, and it does indeed fix my problem. I would
  appreciate it if this patch could be included in a future kernel
  build. Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781763/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1773392] Re: zfs hangs on mount/unmount

2018-06-27 Thread James Buren
It's an issue for my server too. LXD hangs when I try to restart
containers at times. I'm switching to libvirt until this is resolved.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1773392

Title:
  zfs hangs on mount/unmount

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running lxd 3.0 on ubuntu 18.04 with kernel 4.15.0-22-generic and
  4.15.0-20-generic (same behaviour) with zfs backend (0.7.5-1ubuntu16;
  also tried 0.7.9).

  Sometimes lxd hangs when I try to stop / restart or "stop && move"
  some containers. Furhter investigation showed that problem is in zfs
  mount or unmount: it just hangs and lxd just wait it. Also commands
  like "zfs list" hangs to.

  It seems that it is not lxd or zfs issue, but kernel bug?
  https://github.com/lxc/lxd/issues/4104#issuecomment-392072939

  I have one test ct that always hangs on restart, so here is info:

  dmesg:
  [ 1330.390938] INFO: task txg_sync:9944 blocked for more than 120 seconds.
  [ 1330.390994]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.391044] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.391101] txg_syncD0  9944  2 0x8000
  [ 1330.391105] Call Trace:
  [ 1330.391117]  __schedule+0x297/0x8b0
  [ 1330.391122]  schedule+0x2c/0x80
  [ 1330.391136]  cv_wait_common+0x11e/0x140 [spl]
  [ 1330.391141]  ? wait_woken+0x80/0x80
  [ 1330.391152]  __cv_wait+0x15/0x20 [spl]
  [ 1330.391234]  rrw_enter_write+0x3c/0xa0 [zfs]
  [ 1330.391306]  rrw_enter+0x13/0x20 [zfs]
  [ 1330.391380]  spa_sync+0x7c9/0xd80 [zfs]
  [ 1330.391457]  txg_sync_thread+0x2cd/0x4a0 [zfs]
  [ 1330.391534]  ? txg_quiesce_thread+0x3d0/0x3d0 [zfs]
  [ 1330.391543]  thread_generic_wrapper+0x74/0x90 [spl]
  [ 1330.391549]  kthread+0x121/0x140
  [ 1330.391558]  ? __thread_exit+0x20/0x20 [spl]
  [ 1330.391562]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 1330.391566]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 1330.391569]  ret_from_fork+0x35/0x40
  [ 1330.391582] INFO: task lxd:12419 blocked for more than 120 seconds.
  [ 1330.391630]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.391679] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.391735] lxd D0 12419  1 0x
  [ 1330.391739] Call Trace:
  [ 1330.391745]  __schedule+0x297/0x8b0
  [ 1330.391749]  schedule+0x2c/0x80
  [ 1330.391752]  rwsem_down_write_failed+0x162/0x360
  [ 1330.391808]  ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs]
  [ 1330.391814]  call_rwsem_down_write_failed+0x17/0x30
  [ 1330.391817]  ? call_rwsem_down_write_failed+0x17/0x30
  [ 1330.391821]  down_write+0x2d/0x40
  [ 1330.391825]  grab_super+0x30/0x90
  [ 1330.391901]  ? zpl_create+0x160/0x160 [zfs]
  [ 1330.391905]  sget_userns+0x91/0x490
  [ 1330.391908]  ? get_anon_bdev+0x100/0x100
  [ 1330.391983]  ? zpl_create+0x160/0x160 [zfs]
  [ 1330.391987]  sget+0x7d/0xa0
  [ 1330.391990]  ? get_anon_bdev+0x100/0x100
  [ 1330.392066]  zpl_mount+0xa8/0x160 [zfs]
  [ 1330.392071]  mount_fs+0x37/0x150
  [ 1330.392077]  vfs_kern_mount.part.23+0x5d/0x110
  [ 1330.392080]  do_mount+0x5ed/0xce0
  [ 1330.392083]  ? copy_mount_options+0x2c/0x220
  [ 1330.392086]  SyS_mount+0x98/0xe0
  [ 1330.392092]  do_syscall_64+0x73/0x130
  [ 1330.392096]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1330.392099] RIP: 0033:0x4db36a
  [ 1330.392101] RSP: 002b:00c4207fa768 EFLAGS: 0216 ORIG_RAX: 
00a5
  [ 1330.392104] RAX: ffda RBX:  RCX: 
004db36a
  [ 1330.392106] RDX: 00c4205984cc RSI: 00c420a6ee00 RDI: 
00c420a23b60
  [ 1330.392108] RBP: 00c4207fa808 R08: 00c4209d4960 R09: 

  [ 1330.392110] R10:  R11: 0216 R12: 

  [ 1330.392112] R13: 0039 R14: 0038 R15: 
0080
  [ 1330.392123] INFO: task lxd:16725 blocked for more than 120 seconds.
  [ 1330.392171]   Tainted: P   O 4.15.0-22-generic #24-Ubuntu
  [ 1330.392220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 1330.392276] lxd D0 16725  1 0x0002
  [ 1330.392279] Call Trace:
  [ 1330.392284]  __schedule+0x297/0x8b0
  [ 1330.392289]  ? irq_work_queue+0x8d/0xa0
  [ 1330.392293]  schedule+0x2c/0x80
  [ 1330.392297]  io_schedule+0x16/0x40
  [ 1330.392302]  wait_on_page_bit_common+0xd8/0x160
  [ 1330.392305]  ? page_cache_tree_insert+0xe0/0xe0
  [ 1330.392309]  __filemap_fdatawait_range+0xfa/0x160
  [ 1330.392313]  ? _cond_resched+0x19/0x40
  [ 1330.392317]  ? bdi_split_work_to_wbs+0x45/0x2c0
  [ 1330.392321]  ? _cond_resched+0x19/0x40
  [ 1330.392324]  filemap_fdatawait_keep_errors+0x1e/0x40
  [ 1330.392327]  sync_inodes_sb+0x20d/0x2b0
  [ 1330.392333]  __sync_filesystem+0x1b/0x60
  [ 1330.392336]