[Bug 1953223] Re: USB device is not detected during boot, again

2022-01-26 Thread Jarkko Toivonen
In the kernel 5.4.0-96 it worked randomly. I noticed that instead of the
suspend/resume cycle, it was enough to run 'sudo lsusb -v'. After this
the USB net stick was detected. Note that both 'sudo' and '-v' were
required to have an effect.

Version 5.4.0-97 (still in proposed state) has a proper fix: 
Focal update: v5.4.160 upstream stable release (LP: #1953387)
xhci: Fix USB 3.1 enumeration issues by increasing roothub power-on-good delay

See also 
https://patchwork.kernel.org/project/linux-mediatek/patch/20211105160036.549516-1-mathias.ny...@linux.intel.com/
Looks like it took two months for this patch to come from mainline kernel to 
Ubuntu kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953223

Title:
  USB device is not detected during boot, again

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1954746] Re: ASIX AX88179 compatible USB adapter not working

2022-01-07 Thread Jarkko Toivonen
Possibly related to #1953223 and #1939638. For me the adapter is not
recognized at all.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954746

Title:
  ASIX AX88179 compatible USB adapter not working

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1953223] Re: USB device is not detected during boot, again

2021-12-28 Thread Jarkko Toivonen
The 5.16-rc7 did boot when I gave the acpi=off parameter. The nomodeset
parameter was not required. The network stick worked. But due to acpi
being off, only one cpu was detected.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953223

Title:
  USB device is not detected during boot, again

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1953223] Re: USB device is not detected during boot, again

2021-12-28 Thread Jarkko Toivonen
I tried rc7, but it doesn't boot either.

Just to make sure I'm not doing anything wrong, I installed the mainline kernel 
5.15.11. It booted fine, even without nomodeset. And my USB net adapter seems 
to be working. At least in the two reboots that I tried. The 5.15.11 version 
seems to include your commit "xhci: Remove CONFIG_USB_DEFAULT_PERSIST to 
prevent xHCI from
runtime suspending", and the (previously) problematic part in 
drivers/usb/core/hub.h:
if (!hub->hdev->parent) /* root hub */
return delay;
else /* Wait at least 100 msec for power to become stable */
return max(delay, 100U);

So, this could fix the problem, but I guess I have to wait until the
Ubuntu version of the 5.4.x kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953223

Title:
  USB device is not detected during boot, again

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1953223] Re: USB device is not detected during boot, again

2021-12-20 Thread Jarkko Toivonen
That did not help either. I also tried rc6, but the results was the
same. No output even when quiet and splash kernel parameters were
removed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953223

Title:
  USB device is not detected during boot, again

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1953223] Re: USB device is not detected during boot, again

2021-12-14 Thread Jarkko Toivonen
I downloaded the following packages:
linux-image-unsigned-5.16.0-051600rc5-generic_5.16.0-051600rc5.202112121931_amd64.deb
linux-modules-5.16.0-051600rc5-generic_5.16.0-051600rc5.202112121931_amd64.deb

And installed them with sudo dpkg -i linux-image-
unsigned-5.16.0-051600rc5-generic_5.16.0-051600rc5.202112121931_amd64.deb
linux-
modules-5.16.0-051600rc5-generic_5.16.0-051600rc5.202112121931_amd64.deb

While trying to boot it, it stopped after "Loading initial ramdisk...".
It didn't respond to keys in any way. I read that proprietary drivers
(nvidia) could cause problems, so I selected Nouveau instead of nvidia
from "Software & updates" -> "Additional drivers". This removed the
nvidia-driver-460 package. Then I reinstalled the mainline kernel. But
still it wouldn't go any further in the boot. (Kernels 5.4.0-89 and
5.11.0-36 still booted.)

Am I doing something wrong or is the problem in the kernel?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953223

Title:
  USB device is not detected during boot, again

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1953223] [NEW] USB device is not detected during boot, again

2021-12-04 Thread Jarkko Toivonen
Public bug reported:

I have an ethernet adapter (ASIX Electronics Corp. AX88179 Gigabit
Ethernet) attached to a USB-C port of my laptop. After update to kernel
5.4.0-90-generic it stopped working again. Same problem with
5.4.0-91-generic. Detaching and reattaching the adapter doesn't help,
but after suspend and resume it starts working again, until the next
boot. I had the same problem earlier and it was fixed here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638 , but the
bug got reintroduced in kernel 5.4.0-90-generic most likely due to this
patch:

* Fix cold plugged USB device on certain PCIe USB cards (LP: #1945211)
 - Revert "UBUNTU: SAUCE: Revert "usb: core: reduce power-on-good delay time of
  root hub""

I'm running Ubuntu 20.04. USB2 ports work without problems.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-91-generic 5.4.0-91.102
ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
Uname: Linux 5.4.0-91-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jttoivon   2745 F pipewire-media-
 /dev/snd/controlC0:  jttoivon   2745 F pipewire-media-
 /dev/snd/seq:jttoivon   2744 F pipewire
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Sat Dec  4 12:46:18 2021
InstallationDate: Installed on 2020-01-23 (680 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: HP HP ZBook Studio G5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic 
root=UUID=c6b19f0f-68ff-4d8c-985a-c3ed88345389 ro quiet splash 
resume=UUID=f25913ea-6478-45dc-8f64-ea5d721a8f25 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-91-generic N/A
 linux-backports-modules-5.4.0-91-generic  N/A
 linux-firmware1.187.20
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2021
dmi.bios.vendor: HP
dmi.bios.version: Q71 Ver. 01.16.00
dmi.board.name: 8427
dmi.board.vendor: HP
dmi.board.version: KBC Version 16.4C.00
dmi.chassis.asset.tag: 5CD9495R4G
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.16.00:bd04/22/2021:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.4C.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook Studio
dmi.product.name: HP ZBook Studio G5
dmi.product.sku: 2ZC51EA#AK8
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953223

Title:
  USB device is not detected during boot, again

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939638] Re: [regression] USB device is not detected during boot

2021-11-16 Thread Jarkko Toivonen
This got broken again in 5.4.0-90 (Ubuntu 20.04). USB2 ports work but USB-C 
don't. Reattaching USB plug doesn't help, but after suspending and resuming USB 
starts working again, until the next time I restart the computer. The reason 
seems to be that the temporary fix was reverted:
* Fix cold plugged USB device on certain PCIe USB cards (LP: #1945211)
 - Revert "UBUNTU: SAUCE: Revert "usb: core: reduce power-on-good delay time of
  root hub""
And if some proper fix was made, it doesn't work in my case.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939638

Title:
  [regression] USB device is not detected during boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944019] Re: Most of the computer's memory rendered unavailable in Linux after updating BIOS

2021-09-25 Thread Jarkko Toivonen
I got it fixed! In the BIOS I ran quick diagnostic test (includes a
memory check). No problems were indicated, but the next time I booted
the machine (using Ubuntu 21.04 on a USB stick) the memory seemed normal
again. All memory available. And it has worked ever since, independent
on whether I boot from a stick or from the fixed disk.

So, most likely the diagnostic test touched something, after which it
started working. (Probably trying newer version of Ubuntu live from USB
stick had no part in this:)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944019

Title:
  Most of the computer's memory rendered unavailable in Linux after
  updating BIOS

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944019] Re: Most of the computer's memory rendered unavailable in Linux after updating BIOS

2021-09-18 Thread Jarkko Toivonen
** Attachment added: "/proc/meminfo"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944019/+attachment/5526114/+files/meminfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944019

Title:
  Most of the computer's memory rendered unavailable in Linux after
  updating BIOS

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944019] Re: Most of the computer's memory rendered unavailable in Linux after updating BIOS

2021-09-18 Thread Jarkko Toivonen
** Attachment added: "nonworking dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944019/+attachment/5526116/+files/nonworking-dmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944019

Title:
  Most of the computer's memory rendered unavailable in Linux after
  updating BIOS

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944019] Re: Most of the computer's memory rendered unavailable in Linux after updating BIOS

2021-09-18 Thread Jarkko Toivonen
** Attachment added: "Working dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944019/+attachment/5526115/+files/working-dmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944019

Title:
  Most of the computer's memory rendered unavailable in Linux after
  updating BIOS

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944019] [NEW] Most of the computer's memory rendered unavailable in Linux after updating BIOS

2021-09-18 Thread Jarkko Toivonen
Public bug reported:

I have got a HP HP ZBook Studio G5 laptop.

After updating BIOS from "BIOS Q71 Ver. 01.15.00 12/28/2020" to version
"BIOS Q71 Ver. 01.16.00 04/22/2021" most of the memory got unavailable
in Linux.  The system has 16 GiB of memory, but now free -h shows only
total of 1.5 GiB. In Windows all memory seems available. No other
indication of the problem in /proc/meminfo and /proc/iomem (will attach)
is shown except that the total memory is 1.5 GiB. No large area is shown
as reserved in /proc/iomem. But there is now an error message in dmesg
that didn't use to be there: "kernel: efi: memattr: Failed to map EFI
Memory Attributes table @ 0x72f69018". Also that EFI MEMATTR address
seems to have changed after the BIOS update. I will also attach an
earlier dmesg prior to update and a one after the update, since I
updated the BIOS two weeks ago, and after that the kernel has also got
updated.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-84-generic 5.4.0-84.94
ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
Uname: Linux 5.4.0-84-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jttoivon   2725 F pipewire-media-
 /dev/snd/controlC0:  jttoivon   2725 F pipewire-media-
 /dev/snd/seq:jttoivon   2724 F pipewire
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Sat Sep 18 08:53:18 2021
InstallationDate: Installed on 2020-01-23 (603 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: HP HP ZBook Studio G5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic 
root=UUID=c6b19f0f-68ff-4d8c-985a-c3ed88345389 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-84-generic N/A
 linux-backports-modules-5.4.0-84-generic  N/A
 linux-firmware1.187.16
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2021
dmi.bios.vendor: HP
dmi.bios.version: Q71 Ver. 01.16.00
dmi.board.name: 8427
dmi.board.vendor: HP
dmi.board.version: KBC Version 16.4C.00
dmi.chassis.asset.tag: 5CD9495R4G
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.16.00:bd04/22/2021:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.4C.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook Studio
dmi.product.name: HP ZBook Studio G5
dmi.product.sku: 2ZC51EA#AK8
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "/proc/iomem"
   https://bugs.launchpad.net/bugs/1944019/+attachment/5526094/+files/iomem.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944019

Title:
  Most of the computer's memory rendered unavailable in Linux after
  updating BIOS

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1923377] Re: Automatically installed systemd:i386 makes graphical boot hang

2021-05-19 Thread Jarkko Toivonen
Since nobody else seems to have this problem, and I managed to fix my
system, I suggest that this can be closed. For the record, I suspect
that the inclusion of i386 packages started with the installation of the
wine package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923377

Title:
  Automatically installed systemd:i386 makes graphical boot hang

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1923377] [NEW] Automatically installed systemd:i386 makes graphical boot hang

2021-04-11 Thread Jarkko Toivonen
Public bug reported:

1)
Description:Ubuntu 20.04.2 LTS
Release:20.04
2)
systemd:i386 (245.4-4ubuntu3.6, automatic)
systemd:amd64 (245.4-4ubuntu3.6, automatic)
3)
I expected that letting the system install/upgrade packages it suggested would 
cause no harm.
4)
Harm was caused. Graphical boot got stuck after the grub menu. But I could 
access virtual console be pressing alt-F1.

I accepted the upgrade on Saturday, on Sunday, when tried to boot the
machine, the machine hung up. I suspect that one of the problematic
packages was systemd:i386. I have no idea why a 32bit version of this
got installed, and other 32bit versions as well. I attached an excerpt
from /var/log/apt/history.log showing the problematic upgrade.

One of the results was that the binaries /usr/bin/systemctl and
/lib/systemd/systemd were 32bit executables, and they could not load
appropriate the pam modules (which were still 64bit). But as I could log
in from the virtual terminal just fine, this showed that pam itself was
working, systemd was the problem.

After long struggle I managed to fix this by reinstalling systemd, which
overwrote the above binaries with their 64bit versions. Removing
systemd:i386 would have deleted systemd altogether. After that I purged
various 32bit packages I suspected were causing problems. And I
installed the packages removed by the upgrade on Saturday, such as
snapd. Now the system boots up in graphical mode just fine.

But why did the 32bit versions of systemd etc got installed
automatically?

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

** Attachment added: "Part from /var/log/apt/history.log containing the 
problematic update"
   
https://bugs.launchpad.net/bugs/1923377/+attachment/5486631/+files/short-apt-history.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923377

Title:
  Automatically installed systemd:i386 makes graphical boot hang

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys

2020-02-27 Thread Jarkko Toivonen
Hi,

The same happens to me as well. Since I rarely boot to Windows,
I only discovered it now. There does not seem to be any other visible difference
between the working and non-working states, though. There
are no (essential) differences between 'dmesg' or 'sudo fwts acpidump -'
results. So, maybe Windows initialises some device in a weird way,
and this is only reset after a power reset. I don't know how to debug
this further.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852071

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function keys

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys

2020-02-18 Thread Jarkko Toivonen
Hi Marcin,

Try to perform a power reset: https://support.hp.com/ph-en/document/c01684768
That is: turn the computer off, remove all cables, press and hold down
the power button for 15 seconds. Turn the computer on and reconnect
the cables. The brightness buttons should start working.

Worked for me with the exactly same computer with Ubuntu 19.10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852071

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function keys

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs