[Kernel-packages] [Bug 1892012] Re: Bluetooth doesn't turn on
@alexhung That's what I thought, even if I did tried powering off my laptop and unplug the charger for several minutes. Yet, I didn't take off the battery. I did happen again few days ago, althought that time a simple `shutdown -r now` was enought to get it to work. -- 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/1892012 Title: Bluetooth doesn't turn on Status in linux package in Ubuntu: Confirmed Bug description: UPDATE == I tried another kernel (`5.4.0-40-generic` and it didn't worked. Trying to reboot (and get back to the latest kernel) it didn't shutdown, so I hard shutdown it, and restart with the `5.4.0-42-generic`. And now, it works. I hope the logs below may help you to find out what happened, and help others to fix their issue if it's similar to this one. --- Hello, For now, everything worked fine, until this morning when Bluetooth stop working. Ubuntu 20.04 **What expected to happen :** Bluetooth turn on on start, and if it's off it turns on when I turn it on. **What happens :** it doesn't turn on. ``` $ dmesg | grep -i blue [2.433133] Bluetooth: Core ver 2.22 [2.433147] Bluetooth: HCI device and connection manager initialized [2.433149] Bluetooth: HCI socket layer initialized [2.433151] Bluetooth: L2CAP socket layer initialized [2.433153] Bluetooth: SCO socket layer initialized [3.559082] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.559083] Bluetooth: BNEP filters: protocol multicast [3.559088] Bluetooth: BNEP socket layer initialized [4.456149] Bluetooth: hci0: command 0xfc05 tx timeout [4.456167] Bluetooth: hci0: Reading Intel version information failed (-110) ``` Last `/var/log/dpkg.log` logs (previous were from 3 days ago) ``` 2020-08-18 01:06:02 startup archives unpack 2020-08-18 01:06:03 install python3-blessings:all 1.6-3 2020-08-18 01:06:03 status half-installed python3-blessings:all 1.6-3 2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3 2020-08-18 01:06:03 install python3-pynvml:amd64 7.352.0-3 2020-08-18 01:06:03 status half-installed python3-pynvml:amd64 7.352.0-3 2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3 2020-08-18 01:06:03 install gpustat:all 0.6.0-1 2020-08-18 01:06:03 status half-installed gpustat:all 0.6.0-1 2020-08-18 01:06:03 status unpacked gpustat:all 0.6.0-1 2020-08-18 01:06:03 startup packages configure 2020-08-18 01:06:03 configure python3-blessings:all 1.6-3 2020-08-18 01:06:03 status unpacked python3-blessings:all 1.6-3 2020-08-18 01:06:03 status half-configured python3-blessings:all 1.6-3 2020-08-18 01:06:03 status installed python3-blessings:all 1.6-3 2020-08-18 01:06:03 configure python3-pynvml:amd64 7.352.0-3 2020-08-18 01:06:03 status unpacked python3-pynvml:amd64 7.352.0-3 2020-08-18 01:06:03 status half-configured python3-pynvml:amd64 7.352.0-3 2020-08-18 01:06:04 status installed python3-pynvml:amd64 7.352.0-3 2020-08-18 01:06:04 configure gpustat:all 0.6.0-1 2020-08-18 01:06:04 status unpacked gpustat:all 0.6.0-1 2020-08-18 01:06:04 status half-configured gpustat:all 0.6.0-1 2020-08-18 01:06:04 status installed gpustat:all 0.6.0-1 ``` ``` $ dpkg -l | grep -i blue ii bluez 5.53-0ubuntu3 amd64Bluetooth tools and daemons ii bluez-cups5.53-0ubuntu3 amd64Bluetooth printer driver for CUPS ii bluez-obexd 5.53-0ubuntu3 amd64bluez obex daemon ii gir1.2-gnomebluetooth-1.0:amd64 3.34.1-1 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth 3.34.1-1 amd64GNOME Bluetooth tools ii libbluetooth3:amd64 5.53-0ubuntu3 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd643.34.1-1 amd64GNOME Bluetooth tools - support library ii libkf5bluezqt-data5.68.0-0ubuntu1 all data files for bluez-qt ii libkf5bluezqt6:amd64 5.68.0-0ubuntu1 amd64Qt wrapper for bluez ii node-bluebird 3.5.1+dfsg2-2build1 all Fully featured Promises/A+ implementation for Node.js ii pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.5 amd64Bluetooth module for PulseAudio sound server ii qml-module-org-kde-bluezqt:amd64 5.68.0-0ubuntu1
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@John Hoff > Mike, depending on your answers to my many questions from today, if the only way we know to proceed is to build and test a patch, could you help with building the patch (or at least the basic framework of the patch so I can just plug in the CORB values)? Absolutely. I'll write a patch and test it on my machine, after which I'll share it with you. In the mean time you could try Early Patching. Your Early Patching file will have an enormous [verb] section which will look like this [verb] 0x1a 0x707 0xc5 . . . Each line contains three space-separated hex values: Node ID, Verb ID, and Payload. You will have one line for each verb in the CORB dump, so that could be 1000s of lines. I think hda-verb < Early Patching < kernel patch, in the sense that a kernel patch has the highest-probability of success, hda-verb has the lowest, and Early Patching is somewhere in between. This is because I think that some codec values are read-write at initialization time but then become read-only at runtime (only Realtek, the ALC298 manufacturer, knows for sure*). A kernel patch allows us to write values at codec initialization time, whereas hda-verb is at runtime, and Early Patching is somewhere in between. *Perhaps we can know: I found a datasheet for the ALC269 [1]. I think the ALC269 is very similar to the ALC298 codec in our laptops. Among other things, the datasheet describes verb semantics. It's a nice supplement to the Intel HDA spec. I don't recall seeing anything about initialization-time vs runtime, but perhaps I have not read it closely enough - the datasheet is only somewhat less dense and technical than the Intel HDA spec so it's not an easy read! :) [1] https://www.hardwaresecrets.com/datasheets/alc269.pdf -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0,
[Kernel-packages] [Bug 1892827] Re: device doesn't boot with kernel older than v5.7.7 on a usb key: hang at efi_tpm_eventlog_init
SRU v2: https://lists.ubuntu.com/archives/kernel-
team/2020-August/112992.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892827
Title:
device doesn't boot with kernel older than v5.7.7 on a usb key: hang
at efi_tpm_eventlog_init
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.6 source package in Focal:
In Progress
Bug description:
[SRU Justification]
[Impact]
Some systems may hang at boot. With "earlycon=efifb", more debug
messages for EFI are dumpped. Last call trace as:
RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
...
Call Trace:
efi_config_parse_tables+0x12d/0x213
efi_init+0x218/0x36b
? e820__print_table+0x65/0x6e
setup_arch+458/0xa84
This affects all mainline kernel since v5.2 to v5.7.6. Fix available in
v5.8-rc3 and has been backported to v5.7.7, v5.4.50.
[Fix]
Commit ea3cdcaa43b0 ("efi/tpm: Verify event log header before parsing")
fixes commit 6b0326190205 ("efi: Attempt to get the TCG2 event log in
the boot stub").
[Test Case]
So far it can be easily reproduced with a green installation of Focal on
USB key on a few Dell platforms.
[Regression Potential]
Low. This checks validity of tmp event log header before parsing them,
so it affects only platforms might generate invalid entries only.
[Other Info]
This affects -generic for eoan and oem-5.6 for focal, but the former has
be EOL-ed.
== Original Bug Description ==
[Summary] device doesn't boot with kernel older than v5.7.7 on USB key
[Steps to reproduce]
1. Try to boot a green installation of Ubuntu Focal on a USB key.
[Expected result]
Boot up normally.
[Actual result]
Stuck at "loading initial ramdisk". With "earlycon=efifb", more debug
messages for EFI are dumpped. Last call trace as:
RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
...
Call Trace:
efi_config_parse_tables+0x12d/0x213
efi_init+0x218/0x36b
? e820__print_table+0x65/0x6e
setup_arch+458/0xa84
[Failure rate]
10/10
[Additional information]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea3cdcaa43b08c9a747639f545b0ed5cca47f87e
("efi/tpm: Verify event log header before parsing") fixes in 6b0326190205
("efi: Attempt to get the TCG2 event log in the boot stub").
The fix is in linux-5.7.y and v5.8-rc3, and focal 5.4 and oem-5.6 are
affected.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-16-generic 5.8.0-16.17
ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
Uname: Linux 5.8.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2',
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p',
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
Date: Tue Aug 25 02:51:58 2020
InstallationDate: Installed on 2020-07-21 (35 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Inspiron 3500
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-16-generic
root=UUID=7c53c615-c466-43d7-9ca3-f8b8d895b7b0 ro initcall_debug debug
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.8.0-16-generic N/A
linux-backports-modules-5.8.0-16-generic N/A
linux-firmware1.187.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2020
dmi.bios.release: 0.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.3
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr0.4.3:bd08/05/2020:br0.4:svnDellInc.:pnInspiron3500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3500
dmi.product.sku: 0A25
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892827/+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 1892827] Re: device doesn't boot with kernel older than v5.7.7 on a usb key: hang at efi_tpm_eventlog_init
No change resubmit, so PPA not rebuilt.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892827
Title:
device doesn't boot with kernel older than v5.7.7 on a usb key: hang
at efi_tpm_eventlog_init
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.6 source package in Focal:
In Progress
Bug description:
[SRU Justification]
[Impact]
Some systems may hang at boot. With "earlycon=efifb", more debug
messages for EFI are dumpped. Last call trace as:
RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
...
Call Trace:
efi_config_parse_tables+0x12d/0x213
efi_init+0x218/0x36b
? e820__print_table+0x65/0x6e
setup_arch+458/0xa84
This affects all mainline kernel since v5.2 to v5.7.6. Fix available in
v5.8-rc3 and has been backported to v5.7.7, v5.4.50.
[Fix]
Commit ea3cdcaa43b0 ("efi/tpm: Verify event log header before parsing")
fixes commit 6b0326190205 ("efi: Attempt to get the TCG2 event log in
the boot stub").
[Test Case]
So far it can be easily reproduced with a green installation of Focal on
USB key on a few Dell platforms.
[Regression Potential]
Low. This checks validity of tmp event log header before parsing them,
so it affects only platforms might generate invalid entries only.
[Other Info]
This affects -generic for eoan and oem-5.6 for focal, but the former has
be EOL-ed.
== Original Bug Description ==
[Summary] device doesn't boot with kernel older than v5.7.7 on USB key
[Steps to reproduce]
1. Try to boot a green installation of Ubuntu Focal on a USB key.
[Expected result]
Boot up normally.
[Actual result]
Stuck at "loading initial ramdisk". With "earlycon=efifb", more debug
messages for EFI are dumpped. Last call trace as:
RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
...
Call Trace:
efi_config_parse_tables+0x12d/0x213
efi_init+0x218/0x36b
? e820__print_table+0x65/0x6e
setup_arch+458/0xa84
[Failure rate]
10/10
[Additional information]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea3cdcaa43b08c9a747639f545b0ed5cca47f87e
("efi/tpm: Verify event log header before parsing") fixes in 6b0326190205
("efi: Attempt to get the TCG2 event log in the boot stub").
The fix is in linux-5.7.y and v5.8-rc3, and focal 5.4 and oem-5.6 are
affected.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-16-generic 5.8.0-16.17
ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
Uname: Linux 5.8.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2',
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p',
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
Date: Tue Aug 25 02:51:58 2020
InstallationDate: Installed on 2020-07-21 (35 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Inspiron 3500
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-16-generic
root=UUID=7c53c615-c466-43d7-9ca3-f8b8d895b7b0 ro initcall_debug debug
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.8.0-16-generic N/A
linux-backports-modules-5.8.0-16-generic N/A
linux-firmware1.187.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2020
dmi.bios.release: 0.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.3
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr0.4.3:bd08/05/2020:br0.4:svnDellInc.:pnInspiron3500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3500
dmi.product.sku: 0A25
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892827/+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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
This is a kernel bug so not sure if it's wise to fix it from userspace... -- 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in gnome-control-center: Unknown Status in Linux: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+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
