[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
This bug was fixed in the package ubuntu-keyring - 2021.03.26 --- ubuntu-keyring (2021.03.26) hirsute; urgency=medium * Remove expiry of the ddebs.ubuntu.com key. LP: #1920640 * Remove previous signatures from the ddebs.ubuntu.com key to minimize keyring size. * Remove encryption subkeys from cloud-archive & cloud-images keyrings, only signing keys are needed. -- Dimitri John Ledkov Fri, 26 Mar 2021 23:37:35 + ** Changed in: ubuntu-keyring (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Committed Status in ubuntu-keyring source package in Focal: Fix Committed Status in ubuntu-keyring source package in Groovy: Fix Committed Status in ubuntu-keyring source package in Hirsute: Fix Released Bug description: [Impact] * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-dbgsym-keyring package [Test Plan] * Install ubuntu-dbgsym-keyring package * Add ddebs.ubuntu.com repository for your release * sudo apt update must be successful [Where problems could occur] * At the moment the signature was bumped by one year * Meaning this issue will occur again in 2022 * Instead the key must be set to not expire & new round of SRUs issued [Other Info] * Original bug report The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+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 1905166] Re: systemd-shutdown cannot detach DM
> for those affected, does this happen every boot/shutdown? Yes, I'm getting the following messages on Hirsute at the end of every shut down (or reboot): [ OK ] Reached target Reboot. [ timestamp] XFS: attr2 mount option is deprecated. [ timestamp] sd-umoun[2337]: Failed to unmount /oldroot: Device or resource busy [ timestamp] sd-umoun[2337]: Failed to unmount /oldroot/sys: Device or resource busy [ timestamp] shutdown[1]: Could not detach DM /dev/dm-1: Device or resource busy [ timestamp] shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy [ timestamp] shutdown[1]: Failed to finalize file systems, DM devices, ignoring. > is this a 'standard' installation, using the standard iso? Yes, this was installed using a nightly hirsute-live-server-amd64.iso, with disk encryption enabled during installation. > what do you have mounted? what's the output of 'mount' and the output of 'lsblk'? # mount ... /dev/mapper/ubuntu--vg-ubuntu--lv on / type xfs (rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/nvme0n1p2 on /boot type ext4 (rw,relatime) /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) ... Full mount output at https://gist.githubusercontent.com/joliss/c13e728ee039a2440e98f7ba6dd7ecd8/raw/25678bdaa17707a41b81b61c0fc648e01968ca90/mount # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 99.2M 1 loop /snap/core/10908 loop1 7:10 25.9M 1 loop /snap/heroku/4037 loop2 7:20 72M 1 loop /snap/lxd/19766 loop3 7:30 55.5M 1 loop /snap/core18/1988 loop4 7:40 32.3M 1 loop /snap/snapd/11107 loop5 7:50 32.3M 1 loop /snap/snapd/11402 loop6 7:60 68.7M 1 loop /snap/lxd/19823 nvme0n1 259:00 1.8T 0 disk ├─nvme0n1p1 259:10 512M 0 part /boot/efi ├─nvme0n1p2 259:201G 0 part /boot └─nvme0n1p3 259:30 1.8T 0 part └─dm_crypt-0 253:00 1.8T 0 crypt └─ubuntu--vg-ubuntu--lv 253:10 1.8T 0 lvm / -- 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/1905166 Title: systemd-shutdown cannot detach DM Status in systemd package in Ubuntu: Incomplete Bug description: when powering down the system systemd cannot unmount / systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy systemd-shutdown[1]: Failed to finalize DM devices, ignoring reboot: Power down as a result at each startup the filesystem is checked: Press Ctrl+C to cancel all filesystem checks in progress If systemd cannot unmount / that might not be a problem but it should be less noisy and not result in a filesystem check after each reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 11:40:05 2020 MachineType: Dell Inc. Latitude 7410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0M5G57 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd10/11/2020:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn0M5G57:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09CD dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+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 1413232] Re: [systemd] dhclient causes apparmor warnings against /run/systemd/journal/dev-log
@tubastuff that is definitely not the same problem, please see https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1918410 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1413232 Title: [systemd] dhclient causes apparmor warnings against /run/systemd/journal/dev-log Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Bug description: When running a system with systemd, the logs get filled with dhclient getting denied access to the below. Example dmesg output: [ 28.037120] audit: type=1400 audit(1421846274.704:51): apparmor="DENIED" operation="sendmsg" profile="/sbin/dhclient" name="/run/systemd/journal/dev-log" pid=1678 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [ 45.367871] audit: type=1400 audit(1421846292.048:52): apparmor="DENIED" operation="sendmsg" profile="/sbin/dhclient" name="/run/systemd/journal/dev-log" pid=1678 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: isc-dhcp-client 4.3.1-5ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 Date: Wed Jan 21 09:26:16 2015 DhclientLeases: InstallationDate: Installed on 2015-01-08 (12 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150108) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1413232/+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 1921597] [NEW] locks up
Public bug reported: I don't know what would be useful for you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Mar 27 15:06:57 2021 DistUpgraded: 2020-12-23 16:47:59,374 DEBUG /openCache(), new cache size 63671 DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] InstallationDate: Installed on 2015-04-03 (2184 days ago) InstallationMedia: Edubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130214) MachineType: LENOVO 765818U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-136-generic root=UUID=e7e9746b-52c2-49ae-ab18-189b8d46be33 ro drm.debug=0xe nopat vesafb.invalid=1 plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-12-23 (93 days ago) dmi.bios.date: 12/27/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETA9WW (2.09 ) dmi.board.name: 765818U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETA9WW(2.09):bd12/27/2007:svnLENOVO:pn765818U:pvrThinkPadT61:rvnLENOVO:rn765818U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T61 dmi.product.name: 765818U dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Mar 26 14:45:08 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.8 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1921597 Title: locks up Status in xorg package in Ubuntu: New Bug description: I don't know what would be useful for you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Mar 27 15:06:57 2021 DistUpgraded: 2020-12-23 16:47:59,374 DEBUG /openCache(), new cache size 63671 DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] InstallationDate: Installed on 2015-04-03 (2184 days ago) InstallationMedia: Edubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130214) MachineType: LENOVO 765818U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-136-generic root=UUID=e7e9746b-52c2-49ae-ab18-189b8d46be33 ro drm.debug=0xe nopat vesafb.invalid=1 plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-12-23 (93 days ago) dmi.bios.date: 12/27/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETA9WW (2.09 ) dmi.board.name: 765818U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10
[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_f
This bug was fixed in the package gtk+3.0 - 3.24.25-1ubuntu3 --- gtk+3.0 (3.24.25-1ubuntu3) hirsute; urgency=medium * d/p/x11-dnd-Ignore-XErrors-from-the-COW.patch: - Ignore XErrors from the COW (LP: #1911036) * d/p/cssshadowvalue-Apply-device-scale-to-the-offset-when.patch: - Apply device scale to the offset when blurring text (LP: #1919404) -- Daniel van Vugt Thu, 25 Mar 2021 16:17:15 +0100 ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1911036 Title: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_window) Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk4 package in Ubuntu: Fix Committed Bug description: For many months now, whenever any mouse drag is attempted in an application using the gtk tool kit, the application immediately crashes. I've noticed this at least in Firefox and thunar. It also occurs when displaying these applications from a Virtualbox machine or from another server running something other than Ubuntu. The VM was running CentOS 8 and the remote server was running Mageia. Both Firefox and thunar run fine with Mageia's Xorg. It seems like the issue may be with the Xorg server on Ubuntu. I tried setting the GDK_SYNCHRONIZE variable to various settings but was unable to produce further debug output. The only other debug output I was able to gather is when running thunar with the --gtk- debug parameter (attached). I also tried running thunar with GDB but without recompiling it, it doesn't produce much information other than it's stopping in glib. Let me know what other information I can provide. (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ExceptionHandler::GenerateDump cloned child 110611 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. [1]+ Trace/breakpoint trap (core dumped) firefox (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) $ ldd /bin/thunar linux-vdso.so.1 (0x7ffc0c8cc000) libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 (0x7fdbb548c000) libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 (0x7fdbb544f000) libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x7fdbb5442000) libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 (0x7fdbb5437000) libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000) libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000) libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 (0x7fdbb53f3000) libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 (0x7fdbb4c42000) libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 (0x7fdbb4b3d000) libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x7fdbb4b13000) libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 (0x7fdbb49f) libgdk_pixbuf-2.0.so.0 => /lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000) libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 (0x7fdbb49b4000) libxfconf-0.so.3 =>
[Touch-packages] [Bug 1919404] Re: Desktop icon shadows are broken at scale 200%
This bug was fixed in the package gtk+3.0 - 3.24.25-1ubuntu3 --- gtk+3.0 (3.24.25-1ubuntu3) hirsute; urgency=medium * d/p/x11-dnd-Ignore-XErrors-from-the-COW.patch: - Ignore XErrors from the COW (LP: #1911036) * d/p/cssshadowvalue-Apply-device-scale-to-the-offset-when.patch: - Apply device scale to the offset when blurring text (LP: #1919404) -- Daniel van Vugt Thu, 25 Mar 2021 16:17:15 +0100 ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1919404 Title: Desktop icon shadows are broken at scale 200% Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: Desktop icon shadows are broken at scale 200%. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1919404/+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 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake
is this a pulseaudio bug ? If so where are reported the bug upstream, someone has a link? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: Pulseaudio breaks HDMI audio on sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1765832] Re: Two finger scrolling not working after suspend
*** This bug is a duplicate of bug 1722478 *** https://bugs.launchpad.net/bugs/1722478 I am also having this problem on a Thinkpad T450s with OS: elementary 5.1.7 Hera (built on Ubuntu 18.04.4 LTS) Kern: Linux 5.4.0-70-generic The driver "restart" solution (sudo modprobe -r psmouse && sudo modprobe psmouse) worked for me as well -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765832 Title: Two finger scrolling not working after suspend Status in xorg package in Ubuntu: Confirmed Bug description: When waking up my laptop, two finger scrolling is not working anymore. Running: $ modprobe -r psmouse $ modprobe psmouse restores the functionality. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 20 08:23:33 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2227] InstallationDate: Installed on 2018-04-10 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: LENOVO 20BTS09800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET26W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS09800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET26W(1.04):bd01/23/2015:svnLENOVO:pn20BTS09800:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS09800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS09800 dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765832/+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 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)
This bug was fixed in the package mutter - 3.38.4-1ubuntu1 --- mutter (3.38.4-1ubuntu1) hirsute; urgency=medium * Merge with debian, containing new upstream release. * debian/tests: Adapt autopkgtest name and linked library to current soname * debian/tests/control: Update references to libmutter-7-dev * debian/patches: Remove Input Thread backport patches. It has been fun, but we decided to revert this, so here it is. (LP: #1918874, LP: #1919310) * debian/control: Set breaks on gnome-shell 3.38.4. That's the first version on which we'll remove the input thread patches * debian/libmutter-7-0.symbols: Revert symbol changes due to input thread * debian/patches: Add support for ABFR2101010 in v3d used by Raspberry Pi 4 (LP: #1896171) * debian/patches: Handle NVIDIA's zero presentation times (LP: #1880086) * debian/patches: Properly handle configuration events on windows (LP: #191793) * Remaining changes with debian: - debian/gbp.conf: update upstream branch to point to ubuntu/master - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr mutter (3.38.4-1) unstable; urgency=medium * Team upload * New upstream release - Fix Wayland spec compliance when reordering subsurfaces. This is likely to be required by future Firefox versions in native Wayland mode. - Many other fixes that we already had via debian/patches * Drop most patches, included in the new upstream release mutter (3.38.3-5) unstable; urgency=medium * Team upload [ Marco Trevisan (Treviño) ] * debian/patches: Include a missing commit from upstream gnome-3-38 branch to fix X11 UI stutters mutter (3.38.3-4) unstable; urgency=medium * Team upload [ Marco Trevisan (Treviño) ] * debian/patches: cherry-pick more upstream gnome-3-38 fixes - Correctly restore focus to applications that use globally active input handling, such as AWT/Swing Java apps - Disable double buffered shadow buffering, which was intended to improve performance with e.g. llvmpipe but currently makes it worse * debian/tests: Adapt autopkgtest name and linked library to current soname * debian/tests/control: Update references to libmutter-7-dev [ Simon McVittie ] * d/patches: Update to commit 3.38.3-26-g30c542ddc from gnome-3-38 branch - Fix X11 frame timing getting stuck if frames are skipped, resulting in X11 applications not always being redrawn when they should be - Fix a crash when clicking below titlebar with broken GTK themes -- Marco Trevisan (Treviño) Fri, 26 Mar 2021 07:17:54 +0100 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1896171 Title: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver) Status in Mutter: Unknown Status in mesa package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Bug description: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver). Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1896171/+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 1832019] Re: Error when going to 'Tools -> Preferences -> Keyboard shortcuts' in Spyder3 in Bionic
** Changed in: spyder (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1832019 Title: Error when going to 'Tools -> Preferences -> Keyboard shortcuts' in Spyder3 in Bionic Status in spyderlib: Unknown Status in pyqt5 package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: Invalid Status in qtstyleplugins-src package in Ubuntu: Invalid Status in spyder package in Ubuntu: Fix Released Bug description: In Ubuntu 18.04 LTS Steps: 1. Install spyder3 and qt5-style-plugins (sudo apt install spyder3 qt5-style-plugins) 2. Run spyder3 3. Go to Tools → Preferences → General → Appearance 4. Change the Qt window style to cleanlooks, gtk2 or plastique 5. Go to Tools → Preferences → Keyboard shortcuts 6. Error (or crash in case of gtk2) Keyboard shortcuts are not accessible. Here is the error: File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most recent call last): File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments Traceback (most
[Touch-packages] [Bug 1918880] Re: pulseaudio threaded-ml suspend issue
I haven't encountered the problem in over a week after switching to a 5.10 kernel (from linux-image-oem-20.04-edge). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1918880 Title: pulseaudio threaded-ml suspend issue Status in linux-oem-5.6 package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: My laptop failed to suspend overnight and was unresponsive when I opened it back up. This is on Ubuntu 20.04.2 LTS with kernel 5.6.0-1048-oem and pulseaudio:amd64/focal-updates 1:13.99.1-1ubuntu3.10 uptodate. In syslog, I found a stream of suspend attempts with pulseaudio-related issues repeating in a 40s cycle, so reporting this as a PA issue. Mar 12 00:08:31 churn systemd[1]: Reached target Sleep. Mar 12 00:08:31 churn upowerd[1698]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running Mar 12 00:08:31 churn systemd[1]: Starting Suspend... Mar 12 00:08:31 churn ModemManager[1427]: [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running Mar 12 00:08:31 churn kernel: [883904.845262] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM Mar 12 00:08:31 churn ModemManager[1427]: Couldn't check support for device '/sys/devices/pci:00/:00:14.3': Device support check task already available for device '/sys/devices/pci:00/:00:14.3' Mar 12 00:08:31 churn systemd-sleep[516395]: Suspending system... Mar 12 00:08:31 churn kernel: [883904.853576] PM: suspend entry (s2idle) Mar 12 00:08:51 churn kernel: [883904.856917] Filesystems sync: 0.003 seconds Mar 12 00:08:51 churn kernel: [883904.857284] Freezing user space processes ... Mar 12 00:08:51 churn kernel: [883904.991749] iwlwifi :00:14.3: FW already configured (0) - re-configuring Mar 12 00:08:51 churn kernel: [883924.868069] Freezing of tasks failed after 20.010 seconds (1 tasks refusing to freeze, wq_busy=0): Mar 12 00:08:51 churn kernel: [883924.868160] threaded-ml D0 3306 2128 0x80004326 Mar 12 00:08:51 churn kernel: [883924.868166] Call Trace: Mar 12 00:08:51 churn kernel: [883924.868183] __schedule+0x2d8/0x760 Mar 12 00:08:51 churn kernel: [883924.868188] schedule+0x55/0xc0 Mar 12 00:08:51 churn kernel: [883924.868195] do_exit.cold+0x9f/0xb5 Mar 12 00:08:51 churn kernel: [883924.868200] rewind_stack_do_exit+0x17/0x20 Mar 12 00:08:51 churn kernel: [883924.868205] RIP: 0033:0x7fc8a96ebcb9 Mar 12 00:08:51 churn kernel: [883924.868216] Code: Bad RIP value. Mar 12 00:08:51 churn kernel: [883924.868219] RSP: 002b:7fc899504850 EFLAGS: 0293 ORIG_RAX: 0007 Mar 12 00:08:51 churn kernel: [883924.868223] RAX: fdfc RBX: 208bbe357f60 RCX: 7fc8a96ebcb9 Mar 12 00:08:51 churn kernel: [883924.868225] RDX: 7530 RSI: 0003 RDI: 208bbe357f60 Mar 12 00:08:51 churn kernel: [883924.868227] RBP: 0003 R08: R09: 1587756a Mar 12 00:08:51 churn kernel: [883924.868229] R10: 0f90 R11: 0293 R12: 7530 Mar 12 00:08:51 churn kernel: [883924.868231] R13: 7530 R14: 208bbe3285d0 R15: 7fff6f13d440 Mar 12 00:08:51 churn kernel: [883924.868427] OOM killer enabled. Mar 12 00:08:51 churn rtkit-daemon[1608]: The canary thread is apparently starving. Taking action. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1026] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed') Mar 12 00:08:51 churn rtkit-daemon[1608]: Demoting known real-time threads. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1036] manager: NetworkManager state is now DISCONNECTED Mar 12 00:08:51 churn rtkit-daemon[1608]: Demoted 0 threads. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1039] manager: sleep: sleep requested (sleeping: no enabled: yes) Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1039] device (wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 12 00:08:51 churn pulseaudio[2134]: q overrun, queuing locally Mar 12 00:08:51 churn kernel: [883924.868429] Restarting tasks ... done. Mar 12 00:08:51 churn pulseaudio[2134]: message repeated 4 times: [ q overrun, queuing locally] Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1245] device (p2p-dev-wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1247] manager: NetworkManager state is now ASLEEP Mar 12 00:08:51 churn
[Touch-packages] [Bug 1918410] Re: isc-dhcp-client denied by apparmor
Okay adding the suggested rule
works for me. So it would seem dhclient is treating denied access to comm as a
fatal error.
Interestingly I also had it throw a rejection for capability sys_module
[ 1645.480546] audit: type=1400 audit(1616847221.859:73):
apparmor="DENIED" operation="capable" profile="/{,usr/}sbin/dhclient"
pid=3380 comm="dhclient" capability=16 capname="sys_module"
which should not generally be required anymore. See
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1759032
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1918410
Title:
isc-dhcp-client denied by apparmor
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
Hi, I get weird errors in the audit log, seeing dhclient is being
denied reading its comm or the comm of one of its tasks:
[1383307.827378] audit: type=1400 audit(1615367094.054:162):
apparmor="DENIED" operation="open" profile="/{,usr/}sbin/dhclient"
name="/proc/1095210/task/1095213/comm" pid=1095210 comm="dhclient"
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
This might or might not be linked with the fact that I can't get an
IPv4 on this interface. Note that it happened to other, see this
comment:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1413232/comments/8
Or even an article recommending disabling apparmor for dhclient(!):
https://blog.anthony-jacob.com/perte-dip-v4-sous-ubuntu-20-04-apparmor-et-dhclient/
As I said, I'm not sure this is the root cause of the lack of IPv4 renewal,
because running it manually *does* succeed in getting an IP. And running it in
strace shows the EACCES failure:
[pid 1095210] openat(AT_FDCWD, "/proc/self/task/1095211/comm", O_RDWRstrace:
Process 1095211 attached
) = -1 EACCES (Permission non accordée)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1918410/+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 1918410] Re: isc-dhcp-client denied by apparmor
To further elaborate on why dhclient is accessing the comm
$ pstree -at 3395
dhclient ens3
├─{isc-socket}
├─{isc-timer}
└─{isc-worker}
where 3395 is the process. It has 3 additional threads and it is
providing functional names for them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1918410
Title:
isc-dhcp-client denied by apparmor
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
Hi, I get weird errors in the audit log, seeing dhclient is being
denied reading its comm or the comm of one of its tasks:
[1383307.827378] audit: type=1400 audit(1615367094.054:162):
apparmor="DENIED" operation="open" profile="/{,usr/}sbin/dhclient"
name="/proc/1095210/task/1095213/comm" pid=1095210 comm="dhclient"
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
This might or might not be linked with the fact that I can't get an
IPv4 on this interface. Note that it happened to other, see this
comment:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1413232/comments/8
Or even an article recommending disabling apparmor for dhclient(!):
https://blog.anthony-jacob.com/perte-dip-v4-sous-ubuntu-20-04-apparmor-et-dhclient/
As I said, I'm not sure this is the root cause of the lack of IPv4 renewal,
because running it manually *does* succeed in getting an IP. And running it in
strace shows the EACCES failure:
[pid 1095210] openat(AT_FDCWD, "/proc/self/task/1095211/comm", O_RDWRstrace:
Process 1095211 attached
) = -1 EACCES (Permission non accordée)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1918410/+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 1921574] Re: package libpam-systemd:amd64 246.6-1ubuntu1.2 failed to install/upgrade: installed libpam-systemd:amd64 package post-installation script subprocess returned error ex
** Tags removed: need-duplicate-check -- 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/1921574 Title: package libpam-systemd:amd64 246.6-1ubuntu1.2 failed to install/upgrade: installed libpam-systemd:amd64 package post- installation script subprocess returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: I have no extra information. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libpam-systemd:amd64 246.6-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 23 18:28:20 2021 ErrorMessage: installed libpam-systemd:amd64 package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-12-07 (110 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: systemd Title: package libpam-systemd:amd64 246.6-1ubuntu1.2 failed to install/upgrade: installed libpam-systemd:amd64 package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1921574/+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 1921574] [NEW] package libpam-systemd:amd64 246.6-1ubuntu1.2 failed to install/upgrade: installed libpam-systemd:amd64 package post-installation script subprocess returned error
Public bug reported: I have no extra information. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libpam-systemd:amd64 246.6-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 23 18:28:20 2021 ErrorMessage: installed libpam-systemd:amd64 package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-12-07 (110 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: systemd Title: package libpam-systemd:amd64 246.6-1ubuntu1.2 failed to install/upgrade: installed libpam-systemd:amd64 package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- 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/1921574 Title: package libpam-systemd:amd64 246.6-1ubuntu1.2 failed to install/upgrade: installed libpam-systemd:amd64 package post- installation script subprocess returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: I have no extra information. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libpam-systemd:amd64 246.6-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 23 18:28:20 2021 ErrorMessage: installed libpam-systemd:amd64 package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-12-07 (110 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: systemd Title: package libpam-systemd:amd64 246.6-1ubuntu1.2 failed to install/upgrade: installed libpam-systemd:amd64 package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1921574/+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
Re: [Touch-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
sound fine on 5.8.0-48-generic #54~20.04.1-Ubuntu On 3/27/21 10:00 AM, Steph Gosling wrote: > On a 9300 with 5.4.0-70-generic #78 (running kubuntu) it appears every > other login I have no sound and the repeated message: > > [ 257.488549] snd_hda_intel :00:1f.3: DSP detected with PCI > class/subclass/prog-if info 0x040380 > [ 257.494305] snd_hda_intel :00:1f.3: enabling device ( -> 0002) > [ 257.494512] snd_hda_intel :00:1f.3: bound :00:02.0 (ops > i915_audio_component_bind_ops [i915]) > [ 257.521021] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC289: > line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker > [ 257.521023] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 > (0x0/0x0/0x0/0x0/0x0) > [ 257.521025] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 > (0x21/0x0/0x0/0x0/0x0) > [ 257.521026] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 > [ 257.521026] snd_hda_codec_realtek hdaudioC0D0:inputs: > [ 257.521028] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 > [ 257.521029] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1b > [ 257.521030] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 > [ 279.240059] snd_hda_intel :00:1f.3: azx_get_response timeout, > switching to polling mode: last cmd=0x202f8100 > [ 280.243100] snd_hda_intel :00:1f.3: No response from codec, disabling > MSI: last cmd=0x202f8100 > [ 281.255097] snd_hda_intel :00:1f.3: No response from codec, resetting > bus: last cmd=0x202f8100 > [ 282.259095] snd_hda_intel :00:1f.3: No response from codec, resetting > bus: last cmd=0x202f8100 > [ 283.267252] snd_hda_intel :00:1f.3: No response from codec, resetting > bus: last cmd=0x20170500 > > > however on a log out and back in (i.e. not a reboot, but end and start an X > session) and the audio initialises fine the second time. > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: kernel 5.4.0-47-generic #51 upgraded today to this new kernel sound is now totally broken kern.org and syslog are filling with those messages every second, in loop, with no end to it : Sep 8 19:42:34 orion kernel: [ 147.398030] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 8 19:42:35 orion kernel: [ 148.410043] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 8 19:42:36 orion kernel: [ 149.413955] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 8 19:42:37 orion kernel: [ 150.421890] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 8 19:42:38 orion kernel: [ 151.453799] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:39 orion kernel: [ 152.461793] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:41 orion kernel: [ 153.473734] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:42 orion kernel: [ 154.477653] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:43 orion kernel: [ 155.481576] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:44 orion kernel: [ 156.489620] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:45 orion kernel: [ 157.497553] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:46 orion kernel: [ 158.509530] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:47 orion kernel: [ 159.513471] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Because of this, machine has become very slow and response time is awful Login into the machine, even trying to launch a simple program can take up to 30 seconds of wait before anything happens. Sound was working fine with previous kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gf 1758 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 19:42:19 2020 InstallationDate: Installed on 2020-08-29 (9 days ago)
[Touch-packages] [Bug 1918410] Re: isc-dhcp-client denied by apparmor
Denying
/proc/1095210/task/1095213/comm
prevents the task from introspecting (reading), and changing (write) the
command text associated with the task. In this case it would appear one
thread is attempting to change the comm of another thread in the process
(this is generally allowed), see man 5 proc
Reading isn't considered a problem, writing is more interesting. A
process may use it to provide more info, like this is a sandbox thread,
renderer etc. But a compromised task could also use it to masquerade its
comm as another task. It won't hide the task but could make it harder to
kill or monitor if the user is looking for the default comm value.
Denying this is not directly related to lack of IPv4 (kernel wise it has
no relation), but application behavior could be such that when it fails
to access the comm field it handles the error poorly resulting in it
failing to setup IPv4.
I would recommend a modification to the above rule, changing [0-9]* to
@{pids}
@{PROC}/@{pids}/task/[0-9]*/comm rw,
Does adding the above rule fix the IPv4 issue for you? From comment #3 I
assume no, but maybe I am reading it wrong. Are there any other denials
in your logs?
As for disabling AppArmor for dhclient? It is precisely the the type of service
(network facing root service) I would not recommend disabling the apparmor
profile for. Instead updating the profile is the way to go.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1918410
Title:
isc-dhcp-client denied by apparmor
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
Hi, I get weird errors in the audit log, seeing dhclient is being
denied reading its comm or the comm of one of its tasks:
[1383307.827378] audit: type=1400 audit(1615367094.054:162):
apparmor="DENIED" operation="open" profile="/{,usr/}sbin/dhclient"
name="/proc/1095210/task/1095213/comm" pid=1095210 comm="dhclient"
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
This might or might not be linked with the fact that I can't get an
IPv4 on this interface. Note that it happened to other, see this
comment:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1413232/comments/8
Or even an article recommending disabling apparmor for dhclient(!):
https://blog.anthony-jacob.com/perte-dip-v4-sous-ubuntu-20-04-apparmor-et-dhclient/
As I said, I'm not sure this is the root cause of the lack of IPv4 renewal,
because running it manually *does* succeed in getting an IP. And running it in
strace shows the EACCES failure:
[pid 1095210] openat(AT_FDCWD, "/proc/self/task/1095211/comm", O_RDWRstrace:
Process 1095211 attached
) = -1 EACCES (Permission non accordée)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1918410/+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 1921135] Re: package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1921135 Title: package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: no further information ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Mar 18 10:34:46 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-01-23 (60 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1921135/+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 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
On a 9300 with 5.4.0-70-generic #78 (running kubuntu) it appears every other login I have no sound and the repeated message: [ 257.488549] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 257.494305] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [ 257.494512] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 257.521021] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC289: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 257.521023] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 257.521025] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 257.521026] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 257.521026] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 257.521028] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [ 257.521029] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1b [ 257.521030] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 279.240059] snd_hda_intel :00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x202f8100 [ 280.243100] snd_hda_intel :00:1f.3: No response from codec, disabling MSI: last cmd=0x202f8100 [ 281.255097] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x202f8100 [ 282.259095] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x202f8100 [ 283.267252] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20170500 however on a log out and back in (i.e. not a reboot, but end and start an X session) and the audio initialises fine the second time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: kernel 5.4.0-47-generic #51 upgraded today to this new kernel sound is now totally broken kern.org and syslog are filling with those messages every second, in loop, with no end to it : Sep 8 19:42:34 orion kernel: [ 147.398030] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 8 19:42:35 orion kernel: [ 148.410043] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 8 19:42:36 orion kernel: [ 149.413955] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 8 19:42:37 orion kernel: [ 150.421890] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 8 19:42:38 orion kernel: [ 151.453799] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:39 orion kernel: [ 152.461793] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:41 orion kernel: [ 153.473734] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:42 orion kernel: [ 154.477653] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:43 orion kernel: [ 155.481576] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:44 orion kernel: [ 156.489620] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:45 orion kernel: [ 157.497553] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:46 orion kernel: [ 158.509530] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:47 orion kernel: [ 159.513471] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Because of this, machine has become very slow and response time is awful Login into the machine, even trying to launch a simple program can take up to 30 seconds of wait before anything happens. Sound was working fine with previous kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gf 1758 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 19:42:19 2020 InstallationDate: Installed on 2020-08-29 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH
