[Touch-packages] [Bug 1981117] [NEW] Bluetooth icon appears and disappears after reboot
Public bug reported: This morning I tried to use my laptop. I think it was suspended, but not deep suspended (screen off, but was attached to AC). When I tried resuming it, the screen went on, but instead of the gnome login, I was greeted by a black screen with some errors. ``` Bluetooth: hci0: Timed out waiting for suspend events Bluetooth: hci0: Suspend timeout bit: 6 Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` As I could do nothing, I rebooted the laptop (force off with power button and turned on). As I logged in, the Bluetooth indicator in the top right panel started appearing and disappearing continuously. I normally have a Bluetooth mouse connected, so I thought it was trying to pair with it. So I went into the Bluetooth tab from Settings and I was asked permission to pair the device. After allowing that permission appear / disappear issue went out. I think something is wrong with this flow. I think the service for the Bluetooth should handle these issues better, not blinking, but asking such permission that it required from the beginning. As it is it looks broken and poorly discoverable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 10:31:18 2022 InstallationDate: Installed on 2020-04-03 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 84:C5:A6:94:9C:96 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:233857 acl:2324 sco:0 events:14387 errors:0 TX bytes:892713 acl:1283 sco:0 commands:8484 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1981117 Title: Bluetooth icon appears and disappears after reboot Status in bluez package in Ubuntu: New Bug description: This morning I tried to use my laptop. I think it was suspended, but not deep suspended (screen off, but was attached to AC). When I tried resuming it, the screen went on, but instead of the gnome login, I was greeted by a black screen with some errors. ``` Bluetooth: hci0: Timed out waiting for suspend events Bluetooth: hci0: Suspend timeout bit: 6 Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` As I could do nothing, I rebooted the laptop (force off with power button and turned on). As I logged in, the Bluetooth indicator in the top right panel started appearing and disappearing continuously. I normally have a Bluetooth mouse connected, so I thought it was trying to pair with it. So I went into the Bluetooth tab from Settings and I was asked permission to pair the device. After allowing that permission appear / disappear issue went out. I think something is wrong with this flow. I think the service for the Bluetooth should handle these issues better, not blinking, but asking such permission that it required from the beginning. As it is it looks broken and poorly discoverable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 10:31:18 2022 InstallationDate: Installed on 2020-04-03 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 Sourc
[Touch-packages] [Bug 1981117] Re: Bluetooth icon appears and disappears after reboot
** Attachment added: "Clip showing the icon appearing / disappearing" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1981117/+attachment/5602108/+files/2022-07-09%2010-27-38.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1981117 Title: Bluetooth icon appears and disappears after reboot Status in bluez package in Ubuntu: New Bug description: This morning I tried to use my laptop. I think it was suspended, but not deep suspended (screen off, but was attached to AC). When I tried resuming it, the screen went on, but instead of the gnome login, I was greeted by a black screen with some errors. ``` Bluetooth: hci0: Timed out waiting for suspend events Bluetooth: hci0: Suspend timeout bit: 6 Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` As I could do nothing, I rebooted the laptop (force off with power button and turned on). As I logged in, the Bluetooth indicator in the top right panel started appearing and disappearing continuously. I normally have a Bluetooth mouse connected, so I thought it was trying to pair with it. So I went into the Bluetooth tab from Settings and I was asked permission to pair the device. After allowing that permission appear / disappear issue went out. I think something is wrong with this flow. I think the service for the Bluetooth should handle these issues better, not blinking, but asking such permission that it required from the beginning. As it is it looks broken and poorly discoverable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 10:31:18 2022 InstallationDate: Installed on 2020-04-03 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 84:C5:A6:94:9C:96 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:233857 acl:2324 sco:0 events:14387 errors:0 TX bytes:892713 acl:1283 sco:0 commands:8484 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1981117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981117] Re: Bluetooth icon appears and disappears after reboot
** Attachment added: "Dialog asking pairing permission" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1981117/+attachment/5602107/+files/Screenshot%20from%202022-07-09%2010-28-36.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1981117 Title: Bluetooth icon appears and disappears after reboot Status in bluez package in Ubuntu: New Bug description: This morning I tried to use my laptop. I think it was suspended, but not deep suspended (screen off, but was attached to AC). When I tried resuming it, the screen went on, but instead of the gnome login, I was greeted by a black screen with some errors. ``` Bluetooth: hci0: Timed out waiting for suspend events Bluetooth: hci0: Suspend timeout bit: 6 Bluetooth: hci0: Suspend notifier action (3) failed: -110 ``` As I could do nothing, I rebooted the laptop (force off with power button and turned on). As I logged in, the Bluetooth indicator in the top right panel started appearing and disappearing continuously. I normally have a Bluetooth mouse connected, so I thought it was trying to pair with it. So I went into the Bluetooth tab from Settings and I was asked permission to pair the device. After allowing that permission appear / disappear issue went out. I think something is wrong with this flow. I think the service for the Bluetooth should handle these issues better, not blinking, but asking such permission that it required from the beginning. As it is it looks broken and poorly discoverable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 10:31:18 2022 InstallationDate: Installed on 2020-04-03 (826 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 84:C5:A6:94:9C:96 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:233857 acl:2324 sco:0 events:14387 errors:0 TX bytes:892713 acl:1283 sco:0 commands:8484 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1981117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1977630] Re: machinectl pull-tar/pull-raw Operation not permitted
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1977630 Title: machinectl pull-tar/pull-raw Operation not permitted Status in systemd package in Ubuntu: Confirmed Bug description: There is a bug in systemd 249, where one can't pull any images. This was fixed in version 250, and never got backported. (FIX: https://github.com/systemd/systemd/commit/c40d82abf7b23803aa7394a7a7e24c40c32af851) Hopefully this can be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-container 249.11-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 04:51:42 2022 InstallationDate: Installed on 2022-06-01 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854621] Re: ubuntu 20.04 daily boots with no (or warped) background, selecting other background has warped wallpaper
I've had the same issue, have the same GPU. Has persisted to 22.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1854621 Title: ubuntu 20.04 daily boots with no (or warped) background, selecting other background has warped wallpaper Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 daily - verified (check disc for defects) prior to boot. dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) On booting, the 20.04 daily has no background when desktop is loaded? (ie. top panel is there, dock on left side on black screen) When changing background (to any already installed), they are warped when selected and made the bacground as if corrupted (but small image where selection is made looks valid). This issue may relate to video card [radeon] ubuntu@ubuntu:~$ sudo lshw -C video *-display:0 description: VGA compatible controller product: RV516 [Radeon X1300/X1550 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e ioport:dc00(size=256) memory:c-d *-display:1 UNCLAIMED description: Display controller product: RV516 [Radeon X1300/X1550 Series] (Secondary) vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress bus_master cap_list configuration: latency=0 resources: memory:fe9f-fe9f ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.440 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CasperVersion: 1.432 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 1 11:58:33 2019 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981119] [NEW] The Desktop gets stuck when selecting Utilities
You have been subscribed to a public bug: Steps to reproduce: 1. Click "Show Applications" on the bottom left. 2. Click "All" at the bottom. 3. Click Utilities. 4. Click the Desktop to close Utilities. 5. The system gets stuck. This might happen on the second or third try of step 3. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189 Uname: Linux 5.4.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 13:05:32 2022 InstallationDate: Installed on 2019-04-03 (1192 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_IL:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-08-12 (695 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- The Desktop gets stuck when selecting Utilities https://bugs.launchpad.net/bugs/1981119 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981119] Re: The Desktop gets stuck when selecting Utilities
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1981119 Title: The Desktop gets stuck when selecting Utilities Status in ubuntu-meta package in Ubuntu: New Bug description: Steps to reproduce: 1. Click "Show Applications" on the bottom left. 2. Click "All" at the bottom. 3. Click Utilities. 4. Click the Desktop to close Utilities. 5. The system gets stuck. This might happen on the second or third try of step 3. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189 Uname: Linux 5.4.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 9 13:05:32 2022 InstallationDate: Installed on 2019-04-03 (1192 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_IL:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-08-12 (695 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1981119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
(In reply to Philipp Jungkamp from comment #645)
> Created attachment 301327 [details]
> Patch for the ALC287 on the Lenovo Yoga 14IAP7
>
> I did not include the FIXUP_THINKPAD_ACPI quirk in the fixup chain as I
> don't understand what it does. Could someone explain why it is done on other
> Lenovo Hardware and whether it could be needed on the Yoga9i?
Is this a kernel patch that fixes the yoga 9i gen7 issue? That would be
amazing! Thank you Philipp!
One last request, I am not sure how to patch the kernel, would it be
possible to have that patch in the form of a sh script that simply
rewires the hda-verbs so I can test it (and implement it on each boot
while the kernel gets patched)?
I was experimenting with a script like this:
hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x10
hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0320
hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x24
hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0041
hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x24
hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0041
{ ... and so on ...}
But I didn't get anywhere.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019
Title:
[Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
sound at all
Status in sound-2.6 (alsa-kernel):
Confirmed
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
internal speakers, but it work by headphones connected to standard
jack aux.
uname -r
5.11.0-44-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: i3draven 1266 F pulseaudio
/dev/snd/controlC0: i3draven 1266 F pulseaudio
/dev/snd/controlC1: i3draven 1266 F pulseaudio
/dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 15 15:10:53 2022
InstallationDate: Installed on 2021-10-11 (96 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio
Generic
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: i3draven 1266 F pulseaudio
/dev/snd/controlC0: i3draven 1266 F pulseaudio
/dev/snd/controlC1: i3draven 1266 F pulseaudio
/dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2021
dmi.bios.release: 1.49
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN49WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 7 16ACHg6
dmi.ec.firmware.release: 1.49
dmi.modalias:
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1973306] Re: packages freezes on authentification with Wayland
** Description changed: I want to report an issue which might well have been reported already, although i could not find it. A few weeks ago I switched from Ubuntu LTS 20.04 towards the LTS 22.04 with Wayland as default. I discovered that there is a sort of incompatibility between the software-properties-package and the Wayland protocol, which occurs systematically and never occurs when switching back to Xorg. When one tries to add or change a rule in ‘other software’ the application always freezes when the user is asked to authenticate. As soon a one cancels the authentification procedure it unfreezes almost immediately, but freezes again when the user retries to complete the adding or alteration procedure. As said, this error never occurs if the user switches back to an Xorg session. See screenshot: the window with the communication 'software & updates does not respond' and with the choice to close or to wait is hidden behind the authentification window. I am not really sure whether this bug has to be reported as a security issue, but certainly the software-properties-package is of utmost importance for a stable and secure OS. My system: - OS: Ubuntu 22.04 LTS x86_64 - Kernel: 5.15.0-30-generic - Uptime: 13 mins + OS: Ubuntu 22.04 LTS x86_64 + Kernel: 5.15.0-30-generic + Uptime: 13 mins Packages: 1940 (dpkg), 17 (flatpak), - Shell: bash 5.1.16 - Resolution: 1920x1080 - DE: GNOME 42.0 - WM: Mutter - WM Theme: Adwaita - Theme: Adwaita [GTK2/3] - Icons: Numix [GTK2/3] - Terminal: gnome-terminal - CPU: Intel i7-10510U (8) @ 4.900GHz + Shell: bash 5.1.16 + Resolution: 1920x1080 + DE: GNOME 42.0 + WM: Mutter + WM Theme: Adwaita + Theme: Adwaita [GTK2/3] + Icons: Numix [GTK2/3] + Terminal: gnome-terminal + CPU: Intel i7-10510U (8) @ 4.900GHz GPU: Intel CometLake-U GT2 [UHD Grap Memory: 2992MiB / 64007MiB -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1973306 Title: packages freezes on authentification with Wayland Status in software-properties package in Ubuntu: New Bug description: I want to report an issue which might well have been reported already, although i could not find it. A few weeks ago I switched from Ubuntu LTS 20.04 towards the LTS 22.04 with Wayland as default. I discovered that there is a sort of incompatibility between the software-properties-package and the Wayland protocol, which occurs systematically and never occurs when switching back to Xorg. When one tries to add or change a rule in ‘other software’ the application always freezes when the user is asked to authenticate. As soon a one cancels the authentification procedure it unfreezes almost immediately, but freezes again when the user retries to complete the adding or alteration procedure. As said, this error never occurs if the user switches back to an Xorg session. See screenshot: the window with the communication 'software & updates does not respond' and with the choice to close or to wait is hidden behind the authentification window. I am not really sure whether this bug has to be reported as a security issue, but certainly the software-properties-package is of utmost importance for a stable and secure OS. My system: OS: Ubuntu 22.04 LTS x86_64 Kernel: 5.15.0-30-generic Uptime: 13 mins Packages: 1940 (dpkg), 17 (flatpak), Shell: bash 5.1.16 Resolution: 1920x1080 DE: GNOME 42.0 WM: Mutter WM Theme: Adwaita Theme: Adwaita [GTK2/3] Icons: Numix [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-10510U (8) @ 4.900GHz GPU: Intel CometLake-U GT2 [UHD Grap Memory: 2992MiB / 64007MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
(Former VTE developer here) A terminal emulator's job is to execute the precise instructions it receives from the connected application (e.g. bash), and in this case, VTE does that correctly. It's bash (or some other readline app) that asks the terminal to print the prompt over and over again, and VTE does so. There's one thing that VTE does differently than some other terminal emulators, though. Upon resizing the width, it rewraps the contents. I'd argue that this "rewrap on resize" is the single best improvement VTE received during the last decade, it improves the experience of using the terminal so much... well, improves the experience except for the shell prompt. What happens is: The terminal rewraps the existing lines on a resize, and then the shell (which is notified by the resize) assumes that the terminal did not rewrap the lines and it reprints the prompt according to this assumption. Unfortunately this assumption is false, the cursor is not where bash believes it to be, and thus reprinting the prompt goes wrong. (Note: This feature was released in VTE in spring 2014. Since then, there was one particular bash version (4.3 or 4.4, can't recall) that didn't reprint its prompt when the window got resized, therefore the bug didn't occur there.) What could be done to fix this situation? In GNOME Terminal you can disable rewrapping on resize. In dconf-editor navigate to /org/gnome/terminal/legacy/profiles: followed by the Profile ID, there you'll find the config option. While it fixes the prompt's behavior, you'll notice that it also modifies the behavior on earlier lines to a less fortunate one. In case anyone would suggest that VTE should do some "magic": try to figure out if the last line is a shell prompt, and rewrap everything except that last line: No, any approach like this would lead to an utter chaos that is fragile, somewhat working (but there'd always be cases that are still handled incorrectly), different in every terminal, unmaintainable... No, not going to happen. So, what would be the real solution? The only real solution is for bash/readline to introduce the possibility (config option) to assume that the terminal has already rewrapped the lines, thus it doesn't need to reprint the prompt (or if it wishes to reprint then takes into account the rewrapping that has already happened). VTE is not the only terminal out there rewrapping the lines on resize. It wasn't the first one to do this, and wasn't the last one to add this feature either. More and more terminals can do this, and for every newly appearing terminal emulator engine this behavior is pretty much the expectation nowadays. bash needs to catch up with this widespread change that happened in the terminal world. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in readline package in Ubuntu: Confirmed Status in tilix package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824260] Re: wrong kerning in SS-5 PDF form fields
Affects me using fully updated Ubuntu 20.04.4 LTS I used the changes noted in your fontconfig merge request (applied to files in /etc/fonts/conf.avail/ 30-metric-aliases.conf and 45-latin.conf) and it cleared up kerning issues I was having with a different PDF form! Thanks Gunnar and xiota! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1824260 Title: wrong kerning in SS-5 PDF form fields Status in Fontconfig: Fix Released Status in fontconfig package in Ubuntu: Fix Released Bug description: What I expected to happen: I am filling out the SS-5 Social Security Administration form (see attached). I entered "John Jacob Smith" into the "First", "Full Middle Name", and "Last" fields on page 5. What happened instead: I can enter the text without issue, but some of the letters are wrongly positioned, i.e. the kerning is wrong. For example, the letter "i" overlaps with the letter "m" in "Smith" (see attached image). It looks like the font in the fields might be displaying a variable width font when it is supposed to be a fixed-wdith font. Discussion: Since this bug is also present in xpdf and Okular (but not mupdf), I'm guessing this isn't a bug in Evince itself. However, I am reporting it here as a courtesy to other users (since Evince is the default PDF reader) and because I'm not sure which dependency is responsible. (I'm also not sure if it's a direct dependency problem or if it's something else like a font configuration issue.) Here is the output for pdffonts ss-5.pdf: name type encoding emb sub uni object ID - --- --- --- - IHPIKC+ArialMT CID TrueType Identity-H yes yes yes824 0 ArialMT TrueType WinAnsi no no no 826 0 Arial-BoldMT TrueType WinAnsi no no no 828 0 CourierStd Type 1WinAnsi no no no 145 0 HelveticaType 1WinAnsi no no no 197 0 MyriadPro-RegularType 1WinAnsi no no no 198 0 ZapfDingbats Type 1ZapfDingbats no no no 199 0 I asked about this in an Ask Ubuntu question nearly a year ago, but received no response, so I am reporting a bug now instead: https://askubuntu.com/questions/1031235/wrong-letter-positioning-and- font-in-pdf-form Ubuntu version: Description: Ubuntu 18.04.2 LTS Release: 18.04 evince version: $ apt-cache policy evince evince: Installed: 3.28.4-0ubuntu1 Candidate: 3.28.4-0ubuntu1 Version table: *** 3.28.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 10 21:27:11 2019 InstallationDate: Installed on 2018-12-12 (119 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/1824260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981138] [NEW] libpcre32-3 is built against x64
Public bug reported: libpcre32-3 is built against x64, not x86 same for libpcre2-32-0 $ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 $ apt-cache policy libpcre32-3 libpcre32-3: Installed: 2:8.39-13ubuntu0.22.04.1 Candidate: 2:8.39-13ubuntu0.22.04.1 Version table: *** 2:8.39-13ubuntu0.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2:8.39-13build5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ file /usr/lib/x86_64-linux-gnu/libpcre32.so.3.13.3 /usr/lib/x86_64-linux-gnu/libpcre32.so.3.13.3: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=871ad459a4e3c0d2ecbe378d3be72e796483c33d, stripped $ apt-cache policy libpcre2-32-0 libpcre2-32-0: Installed: 10.39-3build1 Candidate: 10.39-3build1 Version table: *** 10.39-3build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status $ file /usr/lib/x86_64-linux-gnu/libpcre2-32.so.0.10.4 /usr/lib/x86_64-linux-gnu/libpcre2-32.so.0.10.4: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=c4c90c16fbe03c6b7ac2d4facef8e6f47ad71ae6, stripped ** Affects: pcre3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcre3 in Ubuntu. https://bugs.launchpad.net/bugs/1981138 Title: libpcre32-3 is built against x64 Status in pcre3 package in Ubuntu: New Bug description: libpcre32-3 is built against x64, not x86 same for libpcre2-32-0 $ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 $ apt-cache policy libpcre32-3 libpcre32-3: Installed: 2:8.39-13ubuntu0.22.04.1 Candidate: 2:8.39-13ubuntu0.22.04.1 Version table: *** 2:8.39-13ubuntu0.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2:8.39-13build5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ file /usr/lib/x86_64-linux-gnu/libpcre32.so.3.13.3 /usr/lib/x86_64-linux-gnu/libpcre32.so.3.13.3: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=871ad459a4e3c0d2ecbe378d3be72e796483c33d, stripped $ apt-cache policy libpcre2-32-0 libpcre2-32-0: Installed: 10.39-3build1 Candidate: 10.39-3build1 Version table: *** 10.39-3build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status $ file /usr/lib/x86_64-linux-gnu/libpcre2-32.so.0.10.4 /usr/lib/x86_64-linux-gnu/libpcre2-32.so.0.10.4: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=c4c90c16fbe03c6b7ac2d4facef8e6f47ad71ae6, stripped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1981138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873519] Re: Package should own adduser.conf
** Description changed: - Right now /etc/adduser.conf is generated by a postinst script, which - means the file doesn't end up getting listed as owned by adduser. + /etc/adduser.conf isn't recorded as belonging to the package, but this + is addressed easily by adding adduser.conf to the debian/install file. + + adduser.conf is generated by a postinst script, so it isn't covered by + the normal install stuff. Regardless, it seems to become registered by + just adding it to the install file on the same line as deluser.conf, + which is already there. I often customize deployments using the config-package-dev extension to Debhelper, but this relies on package ownership to manage config files. - Maybe this is an easy request, to add /etc/adduser.conf as an owned file - instead of a generated one? It seems odd that it isn't owned already. + Hopefully this is a trivial suggestion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1873519 Title: Package should own adduser.conf Status in adduser package in Ubuntu: New Bug description: /etc/adduser.conf isn't recorded as belonging to the package, but this is addressed easily by adding adduser.conf to the debian/install file. adduser.conf is generated by a postinst script, so it isn't covered by the normal install stuff. Regardless, it seems to become registered by just adding it to the install file on the same line as deluser.conf, which is already there. I often customize deployments using the config-package-dev extension to Debhelper, but this relies on package ownership to manage config files. Hopefully this is a trivial suggestion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1873519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981139] [NEW] Power Management > Energy Saving > Screen Energy Saving: When monitor goes to sleep, it can't be woken
Public bug reported: The problem is suspected with this package or xserver-xorg-video-amdgpu. After starting to sleep, the monitor no longer got input to turn back on. Problem was fixed by adding the PPA oibaf/graphics-drivers and updating packages; I purged the PPA to recreate the problem for this report. Error is on Kubuntu 22.04 LTS x86_64, packages info: libdrm-amdgpu1: Installed: 2.4.110-1ubuntu1 Candidate: 2.4.110-1ubuntu1 Version table: *** 2.4.110-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-video-amdgpu: Installed: 22.0.0-1build1 Candidate: 22.0.0-1build1 Version table: *** 22.0.0-1build1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Corresponding journal logs (journalctl -b -1 -e) from after the failure of the monitor to get input again post-rest: Jul 09 22:10:41 hostname dbus-daemon[1166]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper' Jul 09 22:10:46 hostname systemd[2376]: app-systemsettings-2339f639598c454385bf2d1b4ef2aebf.scope: Consumed 4.349s CPU time. Jul 09 22:10:53 hostname systemd[1]: Started Getty on tty2. Jul 09 22:11:37 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:11:51 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:12:02 hostname rtkit-daemon[2567]: Supervising 8 threads of 5 processes of 1 users. Jul 09 22:12:02 hostname rtkit-daemon[2567]: Supervising 8 threads of 5 processes of 1 users. Jul 09 22:12:04 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:12:31 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:13:06 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: refused to change power state from D3hot to D0 Jul 09 22:13:10 hostname kernel: pcieport :00:02.0: AER: Multiple Uncorrected (Non-Fatal) error received: :04:00.1 Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: device [1002:73ff] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: device [1002:ab28] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: Error of this Agent is reported first Jul 09 22:13:10 hostname kernel: [drm] PCI error: detected callback, state(1)!! Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: can't recover (no error_detected callback) Jul 09 22:13:10 hostname kernel: pcieport :03:00.0: AER: device recovery failed Jul 09 22:13:10 hostname kernel: [drm] PCI error: detected callback, state(1)!! Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: can't recover (no error_detected callback) Jul 09 22:13:10 hostname kernel: pcieport :03:00.0: AER: device recovery failed Jul 09 22:13:10 hostname kernel: pcieport :00:02.0: AER: Uncorrected (Non-Fatal) error received: :04:00.1 Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: device [1002:ab28] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10 hostname kernel: [drm] PCI error: detected callback, state(1)!! Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: can't recover (no error_detected callback) Jul 09 22:13:10 hostname kernel: pcieport :03:00.0: AER: device recovery failed Jul 09 22:13:10 hostname kernel: pcieport :00:02.0: AER: Multiple Uncorrected (Non-Fatal) error received: :04:00.1 Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type
[Touch-packages] [Bug 1981139] Re: Power Management > Energy Saving > Screen Energy Saving: When monitor goes to sleep, it can't be woken
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1981139 Title: Power Management > Energy Saving > Screen Energy Saving: When monitor goes to sleep, it can't be woken Status in libdrm package in Ubuntu: New Bug description: The problem is suspected with this package or xserver-xorg-video- amdgpu. After starting to sleep, the monitor no longer got input to turn back on. Manually rebooting the computer was necessary. Problem was fixed by adding the PPA oibaf/graphics-drivers and updating packages; I purged the PPA to recreate the problem for this report. Error is on Kubuntu 22.04 LTS x86_64, packages info: libdrm-amdgpu1: Installed: 2.4.110-1ubuntu1 Candidate: 2.4.110-1ubuntu1 Version table: *** 2.4.110-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-video-amdgpu: Installed: 22.0.0-1build1 Candidate: 22.0.0-1build1 Version table: *** 22.0.0-1build1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Before the screen saver worked correctly after adding the PPA and updating, it was also necessary to run apt autoremove, which did "remove libllvm13:amd64 1:13.0.1-2ubuntu2 " Corresponding journal logs (journalctl -b -1 -e) from after the failure of the monitor to get input again post-rest & reboot: Jul 09 22:10:41 hostname dbus-daemon[1166]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper' Jul 09 22:10:46 hostname systemd[2376]: app-systemsettings-2339f639598c454385bf2d1b4ef2aebf.scope: Consumed 4.349s CPU time. Jul 09 22:10:53 hostname systemd[1]: Started Getty on tty2. Jul 09 22:11:37 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:11:51 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:12:02 hostname rtkit-daemon[2567]: Supervising 8 threads of 5 processes of 1 users. Jul 09 22:12:02 hostname rtkit-daemon[2567]: Supervising 8 threads of 5 processes of 1 users. Jul 09 22:12:04 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:12:31 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:13:06 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: refused to change power state from D3hot to D0 Jul 09 22:13:10 hostname kernel: pcieport :00:02.0: AER: Multiple Uncorrected (Non-Fatal) error received: :04:00.1 Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: device [1002:73ff] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: device [1002:ab28] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: Error of this Agent is reported first Jul 09 22:13:10 hostname kernel: [drm] PCI error: detected callback, state(1)!! Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: can't recover (no error_detected callback) Jul 09 22:13:10 hostname kernel: pcieport :03:00.0: AER: device recovery failed Jul 09 22:13:10 hostname kernel: [drm] PCI error: detected callback, state(1)!! Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: can't recover (no error_detected callback) Jul 09 22:13:10 hostname kernel: pcieport :03:00.0: AER: device recovery failed Jul 09 22:13:10 hostname kernel: pcieport :00:02.0: AER: Uncorrected (Non-Fatal) error received: :04:00.1 Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: device [1002:ab28] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: snd_hda_intel 0
[Touch-packages] [Bug 1981139] Re: Power Management > Energy Saving > Screen Energy Saving: When monitor goes to sleep, it can't be woken
** Description changed: The problem is suspected with this package or xserver-xorg-video-amdgpu. After starting to sleep, the monitor no longer got input to turn back - on. + on. Manually rebooting the computer was necessary. Problem was fixed by adding the PPA oibaf/graphics-drivers and updating packages; I purged the PPA to recreate the problem for this report. Error is on Kubuntu 22.04 LTS x86_64, packages info: libdrm-amdgpu1: - Installed: 2.4.110-1ubuntu1 - Candidate: 2.4.110-1ubuntu1 - Version table: - *** 2.4.110-1ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 2.4.110-1ubuntu1 + Candidate: 2.4.110-1ubuntu1 + Version table: + *** 2.4.110-1ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + 100 /var/lib/dpkg/status xserver-xorg-video-amdgpu: - Installed: 22.0.0-1build1 - Candidate: 22.0.0-1build1 - Version table: - *** 22.0.0-1build1 500 - 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages - 100 /var/lib/dpkg/status - - - Corresponding journal logs (journalctl -b -1 -e) from after the failure of the monitor to get input again post-rest: - + Installed: 22.0.0-1build1 + Candidate: 22.0.0-1build1 + Version table: + *** 22.0.0-1build1 500 + 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + 100 /var/lib/dpkg/status + + Before the screen saver worked correctly after adding the PPA and + updating, it was also necessary to run apt autoremove, which did "remove + libllvm13:amd64 1:13.0.1-2ubuntu2 " + + Corresponding journal logs (journalctl -b -1 -e) from after the failure + of the monitor to get input again post-rest & reboot: Jul 09 22:10:41 hostname dbus-daemon[1166]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper' Jul 09 22:10:46 hostname systemd[2376]: app-systemsettings-2339f639598c454385bf2d1b4ef2aebf.scope: Consumed 4.349s CPU time. Jul 09 22:10:53 hostname systemd[1]: Started Getty on tty2. Jul 09 22:11:37 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:11:51 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:12:02 hostname rtkit-daemon[2567]: Supervising 8 threads of 5 processes of 1 users. Jul 09 22:12:02 hostname rtkit-daemon[2567]: Supervising 8 threads of 5 processes of 1 users. Jul 09 22:12:04 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:12:31 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:13:06 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: refused to change power state from D3hot to D0 Jul 09 22:13:10 hostname kernel: pcieport :00:02.0: AER: Multiple Uncorrected (Non-Fatal) error received: :04:00.1 Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: device [1002:73ff] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: device [1002:ab28] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: Error of this Agent is reported first Jul 09 22:13:10 hostname kernel: [drm] PCI error: detected callback, state(1)!! Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: can't recover (no error_detected callback) Jul 09 22:13:10 hostname kernel: pcieport :03:00.0: AER: device recovery failed Jul 09 22:13:10 hostname kernel: [drm] PCI error: detected callback, state(1)!! Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: can't recover (no error_detected callback) Jul 09 22:13:10 hostname kernel: pcieport :03:00.0: AER: device recovery failed Jul 09 22:13:10 hostname kernel: pcieport :00:02.0: AER: Uncorrected (Non-Fatal) error received: :04:00.1 Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: PCIe B
[Touch-packages] [Bug 1981139] Re: Power Management > Energy Saving > Screen Energy Saving: When monitor goes to sleep, it can't be woken
** Description changed: The problem is suspected with this package or xserver-xorg-video-amdgpu. After starting to sleep, the monitor no longer got input to turn back on. Manually rebooting the computer was necessary. Problem was fixed by adding the PPA oibaf/graphics-drivers and updating packages; I purged the PPA to recreate the problem for this report. Error is on Kubuntu 22.04 LTS x86_64, packages info: libdrm-amdgpu1: Installed: 2.4.110-1ubuntu1 Candidate: 2.4.110-1ubuntu1 Version table: *** 2.4.110-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-video-amdgpu: Installed: 22.0.0-1build1 Candidate: 22.0.0-1build1 Version table: *** 22.0.0-1build1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Before the screen saver worked correctly after adding the PPA and updating, it was also necessary to run apt autoremove, which did "remove libllvm13:amd64 1:13.0.1-2ubuntu2 " - Corresponding journal logs (journalctl -b -1 -e) from after the failure - of the monitor to get input again post-rest & reboot: + Corresponding journal logs (journalctl -b -1 -e) from reboot after the + failure of the monitor to get input again post-rest: Jul 09 22:10:41 hostname dbus-daemon[1166]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper' Jul 09 22:10:46 hostname systemd[2376]: app-systemsettings-2339f639598c454385bf2d1b4ef2aebf.scope: Consumed 4.349s CPU time. Jul 09 22:10:53 hostname systemd[1]: Started Getty on tty2. Jul 09 22:11:37 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:11:51 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:12:02 hostname rtkit-daemon[2567]: Supervising 8 threads of 5 processes of 1 users. Jul 09 22:12:02 hostname rtkit-daemon[2567]: Supervising 8 threads of 5 processes of 1 users. Jul 09 22:12:04 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:12:31 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:13:06 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: refused to change power state from D3hot to D0 Jul 09 22:13:10 hostname kernel: pcieport :00:02.0: AER: Multiple Uncorrected (Non-Fatal) error received: :04:00.1 Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: device [1002:73ff] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: device [1002:ab28] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: Error of this Agent is reported first Jul 09 22:13:10 hostname kernel: [drm] PCI error: detected callback, state(1)!! Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: can't recover (no error_detected callback) Jul 09 22:13:10 hostname kernel: pcieport :03:00.0: AER: device recovery failed Jul 09 22:13:10 hostname kernel: [drm] PCI error: detected callback, state(1)!! Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: can't recover (no error_detected callback) Jul 09 22:13:10 hostname kernel: pcieport :03:00.0: AER: device recovery failed Jul 09 22:13:10 hostname kernel: pcieport :00:02.0: AER: Uncorrected (Non-Fatal) error received: :04:00.1 Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: device [1002:ab28] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10
[Touch-packages] [Bug 1981139] Re: Power Management > Energy Saving > Screen Energy Saving: When monitor goes to sleep, it can't be woken
** Description changed: The problem is suspected with this package or xserver-xorg-video-amdgpu. After starting to sleep, the monitor no longer got input to turn back on. Manually rebooting the computer was necessary. Problem was fixed by adding the PPA oibaf/graphics-drivers and updating packages; I purged the PPA to recreate the problem for this report. Error is on Kubuntu 22.04 LTS x86_64, packages info: libdrm-amdgpu1: Installed: 2.4.110-1ubuntu1 Candidate: 2.4.110-1ubuntu1 Version table: *** 2.4.110-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-video-amdgpu: Installed: 22.0.0-1build1 Candidate: 22.0.0-1build1 Version table: *** 22.0.0-1build1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Before the screen saver worked correctly after adding the PPA and updating, it was also necessary to run apt autoremove, which did "remove libllvm13:amd64 1:13.0.1-2ubuntu2 " + + == UPDATE == + It turns out the packages from the PPA did not fix the problem. They only made it possible to wake the screen back up a few seconds after it goes to sleep. Corresponding journal logs (journalctl -b -1 -e) from reboot after the failure of the monitor to get input again post-rest: Jul 09 22:10:41 hostname dbus-daemon[1166]: [system] Successfully activated service 'org.kde.powerdevil.chargethresholdhelper' Jul 09 22:10:46 hostname systemd[2376]: app-systemsettings-2339f639598c454385bf2d1b4ef2aebf.scope: Consumed 4.349s CPU time. Jul 09 22:10:53 hostname systemd[1]: Started Getty on tty2. Jul 09 22:11:37 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:11:51 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:12:02 hostname rtkit-daemon[2567]: Supervising 8 threads of 5 processes of 1 users. Jul 09 22:12:02 hostname rtkit-daemon[2567]: Supervising 8 threads of 5 processes of 1 users. Jul 09 22:12:04 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:12:31 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:13:06 hostname wpa_supplicant[1200]: wlp7s0: WPA: Group rekeying completed with 04:92:26:5e:63:f9 [GTK=CCMP] Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: refused to change power state from D3hot to D0 Jul 09 22:13:10 hostname kernel: pcieport :00:02.0: AER: Multiple Uncorrected (Non-Fatal) error received: :04:00.1 Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: device [1002:73ff] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: amdgpu :04:00.0: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: device [1002:ab28] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: TLP Header: 4001 000c f04c Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: Error of this Agent is reported first Jul 09 22:13:10 hostname kernel: [drm] PCI error: detected callback, state(1)!! Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: can't recover (no error_detected callback) Jul 09 22:13:10 hostname kernel: pcieport :03:00.0: AER: device recovery failed Jul 09 22:13:10 hostname kernel: [drm] PCI error: detected callback, state(1)!! Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: can't recover (no error_detected callback) Jul 09 22:13:10 hostname kernel: pcieport :03:00.0: AER: device recovery failed Jul 09 22:13:10 hostname kernel: pcieport :00:02.0: AER: Uncorrected (Non-Fatal) error received: :04:00.1 Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: device [1002:ab28] error status/mask=0010/ Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1:[20] UnsupReq (First) Jul 09 22:13:10 hostname kernel: snd_hda_intel :04:00.1: AER: TLP Header: 40
