[Touch-packages] [Bug 1982684] Re: ubuntu-bug launches chromium instead of my default browser
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1982684 Title: ubuntu-bug launches chromium instead of my default browser Status in apport package in Ubuntu: Expired Bug description: graingert@conscientious:~$ gconftool --get /desktop/gnome/url-handlers/http/command No value set for `/desktop/gnome/url-handlers/http/command' graingert@conscientious:~$ cat ~/.local/share/applications/mimeapps.list cat: /home/graingert/.local/share/applications/mimeapps.list: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 09:56:49 2022 InstallationDate: Installed on 2022-07-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1982684/+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 1990743] Re: resolvconf install fails upgrading from Jammy to Kinetic
resolvconf has not been installed by default in Ubuntu since before 18.04 LTS and is considered deprecated and should not be used. Is there a reason that you have the package installed? ** Changed in: resolvconf (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1990743 Title: resolvconf install fails upgrading from Jammy to Kinetic Status in resolvconf package in Ubuntu: Incomplete Bug description: Setting up resolvconf (1.91ubuntu1) ... cp: not writing through dangling symlink '/etc/resolvconf/resolv.conf.d/original' dpkg: error processing package resolvconf (--configure): installed resolvconf package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: resolvconf E: Sub-process /usr/bin/dpkg returned an error code (1) $ ls -l /etc/resolvconf/resolv.conf.d/original lrwxrwxrwx 1 root root 39 Jan 2 2019 /etc/resolvconf/resolv.conf.d/original -> ../run/systemd/resolve/stub-resolv.conf ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: resolvconf 1.91ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 18:48:31 2022 InstallationDate: Installed on 2019-01-02 (1361 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified] modified.conffile..etc.resolvconf.update.d.dnscache: [deleted] mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1990743/+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 1990064] Re: unconfined profile denies userns_create for chromium based processes
Sorry, this answer has confused me even more... heres an example of what we're currently using, perhaps you can speak to that,,, the user in this case has no special rights, certainly not cap_sys_admin. james@trinity:~$ grep james /etc/subuid james:10:65536 james@trinity:~$ ls -asl .local/share/lxc/2004test/rootfs/ | head -8 total 68 4 drwxr-xr-x 17 10 10 4096 Aug 14 2020 . 4 drwxrwx--- 3 10 james 4096 Aug 14 2020 .. 0 lrwxrwxrwx 1 10 107 Aug 14 2020 bin -> usr/bin 4 drwxr-xr-x 2 10 10 4096 Apr 15 2020 boot 4 drwxr-xr-x 3 10 10 4096 Aug 14 2020 dev 4 drwxr-xr-x 70 10 10 4096 Aug 14 2020 etc 4 drwxr-xr-x 3 10 10 4096 Aug 14 2020 home james@trinity:~$ whoami james james@trinity:~$ lxc-start -n 2004test james@trinity:~$ lxc-attach -n 2004test root@2004test:/# exit exit james@trinity:~$ lxc-stop -n 2004test james@trinity:~$ -- 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/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1990736] Re: Xorg crash
** Package changed: ubuntu => xorg (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/1990736 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: J'ai des crash répétitif depuis longtemps. Et parfois l'écran se fige je ne peux plus rien faire. J'ai déjà réinstallé 3 x. Impossible de trouver le problème. Merci beaucoup. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 22:02:01 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2650] InstallationDate: Installed on 2022-09-08 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=fr_CH:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=30b5da29-5676-4f0b-bf23-d79eef14a3c5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1990736/+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 1990638] Re: package libdebuginfod-common 0.187-3 failed to install/upgrade: installed libdebuginfod-common package post-installation script subprocess returned error exit status
I've uploaded a fix to Debian, it should be ready to be sync'ed into Ubuntu by tomorrow. ** Changed in: elfutils (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1990638 Title: package libdebuginfod-common 0.187-3 failed to install/upgrade: installed libdebuginfod-common package post-installation script subprocess returned error exit status 1 Status in elfutils package in Ubuntu: In Progress Bug description: installer crashed while doing an update. Something with updating elf dwarf libraries, asked to modify some configuration with a dialog I replied OK and then the installation crashed. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: libdebuginfod-common 0.187-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Sep 23 09:13:00 2022 DuplicateSignature: package:libdebuginfod-common:0.187-3 Setting up libdebuginfod-common (0.187-3) ... chmod: cannot access '/etc/profile.d/debuginfod.sh': No such file or directory dpkg: error processing package libdebuginfod-common (--configure): installed libdebuginfod-common package post-installation script subprocess returned error exit status 1 ErrorMessage: installed libdebuginfod-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-03-11 (195 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.2 SourcePackage: elfutils Title: package libdebuginfod-common 0.187-3 failed to install/upgrade: installed libdebuginfod-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to kinetic on 2022-09-13 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1990638/+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 1990736] [NEW] Xorg crash
You have been subscribed to a public bug: J'ai des crash répétitif depuis longtemps. Et parfois l'écran se fige je ne peux plus rien faire. J'ai déjà réinstallé 3 x. Impossible de trouver le problème. Merci beaucoup. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 22:02:01 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2650] InstallationDate: Installed on 2022-09-08 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=fr_CH:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=30b5da29-5676-4f0b-bf23-d79eef14a3c5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash jammy ubuntu wayland-session -- Xorg crash https://bugs.launchpad.net/bugs/1990736 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1990064] Re: unconfined profile denies userns_create for chromium based processes
It will affect both. The exact effect will depend on how things are set up. Unconfined privileged processes will still have access to create user namespaces as they see fit. The processes within the user namespace will be subject to similar restrictions. There is still room for refinement of the mediation being done. Whether to virtualize the sysctl (not currently done), and what restrictions on nested user namespace should be enforced (whether a stack unconfined or system level unconfined is sufficient). But generally speaking, what uid mappings are being done within a container are not being taken into account by the mediation. If this is something to be consider the current mediation can be extended to support it. The mediation is based on current confinement and whether the task has cap_sys_admin. So currently it is possible to setup a container that is confined by a system level profile but unconfined within the container, and that has cap_sys_admin and have the container setup a further namespace. If the system level confinement restricts the creation of user namespace then regardless of the application is unconfined within the container or confined and allowing access to user namespaces then access will be restricted. There currently is a lot of flexibility in what is supported. Feedback over the next cycle or two as we refine the confinement and get things packaged up will be appreciated. -- 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/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1990743] [NEW] resolvconf install fails upgrading from Jammy to Kinetic
Public bug reported: Setting up resolvconf (1.91ubuntu1) ... cp: not writing through dangling symlink '/etc/resolvconf/resolv.conf.d/original' dpkg: error processing package resolvconf (--configure): installed resolvconf package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: resolvconf E: Sub-process /usr/bin/dpkg returned an error code (1) $ ls -l /etc/resolvconf/resolv.conf.d/original lrwxrwxrwx 1 root root 39 Jan 2 2019 /etc/resolvconf/resolv.conf.d/original -> ../run/systemd/resolve/stub-resolv.conf ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: resolvconf 1.91ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 18:48:31 2022 InstallationDate: Installed on 2019-01-02 (1361 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified] modified.conffile..etc.resolvconf.update.d.dnscache: [deleted] mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144 ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1990743 Title: resolvconf install fails upgrading from Jammy to Kinetic Status in resolvconf package in Ubuntu: New Bug description: Setting up resolvconf (1.91ubuntu1) ... cp: not writing through dangling symlink '/etc/resolvconf/resolv.conf.d/original' dpkg: error processing package resolvconf (--configure): installed resolvconf package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: resolvconf E: Sub-process /usr/bin/dpkg returned an error code (1) $ ls -l /etc/resolvconf/resolv.conf.d/original lrwxrwxrwx 1 root root 39 Jan 2 2019 /etc/resolvconf/resolv.conf.d/original -> ../run/systemd/resolve/stub-resolv.conf ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: resolvconf 1.91ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 18:48:31 2022 InstallationDate: Installed on 2019-01-02 (1361 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified] modified.conffile..etc.resolvconf.update.d.dnscache: [deleted] mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1990743/+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 1954320] Re: Add privacy screen modules to the initrd
** Tags removed: fr-1938 -- 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/1954320 Title: Add privacy screen modules to the initrd Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Jammy: Confirmed Bug description: Starting with kernel 5.17 the kernel supports the builtin privacy screens built into the LCD panel of some new laptop models. This means that the drm drivers will now return -EPROBE_DEFER from their probe() method on models with a builtin privacy screen when the privacy screen provider driver has not been loaded yet. To avoid any regressions Ubuntu should modify its initrd generation tool to include privacy screen provider drivers in the initrd (at least on systems with a privacy screen), before 5.17 kernels start showing up in the Ubuntu repos. If this change is not made, then users using a graphical bootsplash (plymouth) will get an extra boot-delay of up to 8 seconds (DeviceTimeout in plymouthd.defaults) before plymouth will show and when using disk-encryption where the LUKS password is requested from the initrd, the system may fallback to text-mode after these 8 seconds. I've written a patch with the necessary changes for dracut, which might be useful as an example for how to deal with this, see: https://github.com/dracutdevs/dracut/pull/1666 ATM the only kms driver using privacy screens is the i915 driver and the only provider is the thinkpad_acpi driver. But both are likely to change (and change soon!), so the detection really should be made dynamic as has been done in the dracut patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1954320/+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 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
** Tags removed: fr-2601 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Focal: Confirmed Status in avahi source package in Jammy: Confirmed Status in avahi source package in Kinetic: Confirmed Bug description: - Description: Ubuntu Disco Dingo (development branch) Release: 19.04 - seahorse: Installed: 3.32-1 Candidate: 3.32-1 Version table: *** 3.32-1 500 500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status - I have absolutely no idea why or how. Just collected this report from apport-cli. Some times receiving "internal error" reports, no details provided, just "Cancel" or "Send report" options. So, I decided to check apport and there was this report. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: seahorse 3.32-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 18:09:01 2019 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316) ProcCmdline: /usr/bin/seahorse --gapplication-service Signal: 6 SourcePackage: seahorse StacktraceTop: __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at assert.c:101 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+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 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Jammy) 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/1965293 Title: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in linux source package in Impish: Incomplete Status in systemd source package in Impish: Won't Fix Status in linux source package in Jammy: Incomplete Status in systemd source package in Jammy: Confirmed Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-37.42 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz The "tests-in-lxd" testcase is failing with all kernels in Impish: test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service snap-lxd-22662.mount --- -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 10:01:49 UTC. -- Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for lxd, revision 22662... Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: mount failed: Operation not permitted. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: Mount process exited, code=exited, status=1/FAILURE Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: Failed with result 'exit-code'. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit for lxd, revision 22662. journal for failed service snap-snapd-15177.mount --- -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 10:01:49 UTC. -- Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for snapd, revision 15177... Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: mount failed: Operation not permitted. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: Mount process exited, code=exited, status=1/FAILURE Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: Failed with result 'exit-code'. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit for snapd, revision 15177. FAIL [...] == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", line 69, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['snap-lxd-22662.mount loaded failed fai[119 chars]177'] != [] First list contains 2 additional elements. First extra element 0: 'snap-lxd-22662.mount loaded failed failed Mount unit for lxd, revision 22662' + [] - ['snap-lxd-22662.mount loaded failed failed Mount unit for lxd, revision ' - '22662', - 'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, revision ' - '15177'] This testcase started to fail with the latest re-spin of the kernels (uploaded on mar-16), however the only patch applied between the previous kernels and the current ones is a CVE fix which is unlikely to be causing this failure: "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()" https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965293/+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 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42
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/1965293 Title: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in linux source package in Impish: Incomplete Status in systemd source package in Impish: Won't Fix Status in linux source package in Jammy: Incomplete Status in systemd source package in Jammy: Confirmed Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-37.42 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz The "tests-in-lxd" testcase is failing with all kernels in Impish: test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service snap-lxd-22662.mount --- -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 10:01:49 UTC. -- Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for lxd, revision 22662... Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: mount failed: Operation not permitted. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: Mount process exited, code=exited, status=1/FAILURE Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: Failed with result 'exit-code'. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit for lxd, revision 22662. journal for failed service snap-snapd-15177.mount --- -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 10:01:49 UTC. -- Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for snapd, revision 15177... Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: mount failed: Operation not permitted. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: Mount process exited, code=exited, status=1/FAILURE Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: Failed with result 'exit-code'. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit for snapd, revision 15177. FAIL [...] == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", line 69, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['snap-lxd-22662.mount loaded failed fai[119 chars]177'] != [] First list contains 2 additional elements. First extra element 0: 'snap-lxd-22662.mount loaded failed failed Mount unit for lxd, revision 22662' + [] - ['snap-lxd-22662.mount loaded failed failed Mount unit for lxd, revision ' - '22662', - 'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, revision ' - '15177'] This testcase started to fail with the latest re-spin of the kernels (uploaded on mar-16), however the only patch applied between the previous kernels and the current ones is a CVE fix which is unlikely to be causing this failure: "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()" https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965293/+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 1990588] Re: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 1
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/1990588 Title: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127 Status in systemd package in Ubuntu: Confirmed Bug description: updating from server 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd 249.11-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 22 19:00:53 2022 ErrorMessage: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127 InstallationDate: Installed on 2020-07-28 (786 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel IC4GG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=8859cc64-d58f-4403-a3dc-284744628c34 ro rootflags=subvol=@ debian-installer/language=es keyboard-configuration/layoutcode?=es consoleblank=60 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: systemd Title: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127 UpgradeStatus: Upgraded to focal on 2022-09-22 (0 days ago) dmi.bios.date: 07/03/2012 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 63K dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: IC4GG dmi.board.vendor: Intel dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr63K:bd07/03/2012:br0.1:svnIntel:pnIC4GG:pvr0.1:rvnIntel:rnIC4GG:rvrFAB1:cvnIntelCorporation:ct9:cvr0.1:skuSystemSKUNumber: dmi.product.family: ChiefRiver System dmi.product.name: IC4GG dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: Intel mtime.conffile..etc.systemd.logind.conf: 2020-10-22T18:57:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990588/+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 1990740] [NEW] laptop wouldn't wake from sleep
Public bug reported: Shortly after upgrading from Jammy to Kinetic my laptop went to sleep after I was idle for 20 minutes, as it is configured to do. The lid was closed when the laptop went to sleep. I was unable to wake up the laptop. Opening the lid back up should have caused it to wake up but did not. Pressing the power button should have caused it to wake up but did not. Both the LED on the lid and the power button light were cycling on and off as they do when the laptop is sleeping. I had to hold down the power button for five seconds to power off the laptop completely and then power it back on to get it to come back up. Never saw this behavior even once with Jammy. After rebooting and logging in, I put the laptop to sleep by selecting Suspend from the menu, and after _that_ it woke up immediately when I pushed the power button. I am not sure yet how reproducible this is, but I thought that even a single incidence of something like this was worth reporting. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 17:29:50 2022 InstallationDate: Installed on 2019-08-16 (1135 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) dmi.bios.date: 04/20/2019 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW 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.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:br1.38:efr1.13:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KH_BU_Think_FM_ThinkPadX1Carbon6th: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.systemd.logind.conf: 2022-09-24T15:20:56.088250 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- 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/1990740 Title: laptop wouldn't wake from sleep Status in systemd package in Ubuntu: New Bug description: Shortly after upgrading from Jammy to Kinetic my laptop went to sleep after I was idle for 20 minutes, as it is configured to do. The lid was closed when the laptop went to sleep. I was unable to wake up the laptop. Opening the lid back up should have caused it to wake up but did not. Pressing the power button should have caused it to wake up but did not. Both the LED on the lid and the power button light were cycling on and off as they do when the laptop is sleeping. I had to hold down the power button for five seconds to power off the laptop completely and then power it back on to get it to come back up. Never saw this behavior even once with Jammy. After rebooting and logging in, I put the laptop to sleep by selecting Suspend from the menu, and after _that_ it woke up immediately when I pushed the power button. I am not sure yet how reproducible this is, but I thought that even a single incidence of something like this was worth reporting. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 17:29:50 2022 InstallationDate: Installed on 2019-08-16 (1135 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) dmi.bios.date: 04/20/2019 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version:
[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
** Bug watch removed: Red Hat Bugzilla #752593 https://bugzilla.redhat.com/show_bug.cgi?id=752593 -- 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without any keyboard. [EDIT]But I can still switch back to tty1.[/EDIT] I have also tried with much lower values for vm.dirty_background_ratio and vm.dirty_ratio, but to no avail. Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not help either. More information below: $ lsb_release -rd Description: Ubuntu
[Touch-packages] [Bug 1937110] Re: dhcp option 121 & 249
** Tags removed: fr-2416 -- 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/1937110 Title: dhcp option 121 & 249 Status in subiquity: New Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Jammy: Incomplete Bug description: Hello, I'm running into issues with subiquity on a cloud provider. The cloud provider is using an on-link L3 gateway. His DHCP response looks like this: OPTION: 53 ( 1) DHCP message type 5 (DHCPACK) OPTION: 54 ( 4) Server identifier 172.31.1.1 OPTION: 51 ( 4) IP address leasetime 86400 (24h) OPTION: 1 ( 4) Subnet mask 255.255.255.255 OPTION: 3 ( 4) Routers 172.31.1.1 OPTION: 6 ( 12) DNS server OPTION: 121 ( 14) Classless Static Route20ac1f010100 ... ac1f0101 .. OPTION: 249 ( 14) MSFT - Classless route20ac1f010100 ... ac1f0101 .. Im booting the subiquity process with an patched ipxe (https://github.com/ipxe/ipxe/pull/104) like this: #!ipxe kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null initrd .../initrd boot initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso Sadly subiquity is stuck with a broken network (because of missing dhcp option 121/249 support). It happens when its running the /init from the kernel right after kernel is booted, i guess even before the subiquity is started(?). After further debugging, it looks like the provided kernel 5.4.80 #90 Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc- dhclient-4.4.1 which is lacking the given options. Would be awesome if this could be fixed.. maybe just a simple busybox compile option? To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937110/+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 1990562] Re: attempting to diff static library files raises UnicodeDecodeError
This bug was fixed in the package dh-python - 5.20220923 --- dh-python (5.20220923) unstable; urgency=medium [ Stefano Rivera ] * Run Python test suite with nose2. (closes: 1018338) * Don't attempt to diff static libs (.a), thanks Nick Rosbrook. (closes: 1020528) [ Debian Janitor ] * Bump debhelper from old 12 to 13. + Drop check for DEB_BUILD_OPTIONS containing "nocheck", since debhelper now does this. * Remove constraints unnecessary since buster (oldstable): + dh-python: Drop versioned constraint on python3 in Replaces. [ Stuart Prescott ] * pyproject plugin: Make the package's entry points available in the PATH when running the package's test suite, so that tests using the entry points can be run. -- Stefano Rivera Fri, 23 Sep 2022 09:47:57 +0200 ** Changed in: dh-python (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1990562 Title: attempting to diff static library files raises UnicodeDecodeError Status in dh-python package in Ubuntu: Fix Released Status in numpy package in Ubuntu: New Status in dh-python package in Debian: Fix Released Bug description: In verbose mode, if files differ in share_files(), dhpython will try to show a diff of the files. When these files are static libraries, this raises a UnicodeDecodeError. For example, from a recent numpy build on arm64[1]: W: dh_python3 fs:146: Paths differ: debian/python3-numpy/usr/lib/python3.10/dist-packages/numpy/random/lib/libnpyrandom.a and debian/python3-numpy/usr/lib/python3/dist-packages/numpy/random/lib/libnpyrandom.a Traceback (most recent call last): File "/usr/bin/dh_python3", line 284, in main() File "/usr/bin/dh_python3", line 210, in main fix_locations(package, interpreter, SUPPORTED, options) File "/usr/share/dh-python/dhpython/fs.py", line 53, in fix_locations share_files(srcdir, dstdir, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 149, in share_files fromlines = fp1.readlines() File "/usr/lib/python3.10/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 75: invalid start byte make[1]: *** [debian/rules:46: override_dh_python3] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:15: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 There is already logic to skip this diff for .so files, so the same should be done for .a files. [1] https://launchpadlibrarian.net/624822201/buildlog_ubuntu-kinetic- arm64.numpy_1%3A1.21.5-1build2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1990562/+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 1867204] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report
** Tags removed: fr-269 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1867204 Title: /usr/share/apport/whoopsie-upload- all:FileNotFoundError:/usr/share/apport/whoopsie-upload- all@170:collect_info:process_report Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Confirmed Bug description: [Impact] The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu19, the problem page at https://errors.ubuntu.com/problem/7a3912ff155870bdb23500abfa48a21a6cb07171 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. There were 1301 crashes reported in the last month for this bug, which makes it to number 3 of the apport bug list (despite Ubuntu 22.04 already being fixed and only older releases are still affected). [Test Plan] Check that the fixed version does not appear on https://errors.ubuntu.com/problem/3adc63930455e99063ec1f77bf461d975492e9b4. [Where problems could occur] Worst case - in any part of the bug reporting/collection procedure, since that is what's changing. [Other info] Due to the huge amount of broken autopkgtest tests, the diff for the SRUs are bigger than desired. The individual commits in https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are probably easier to review. * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1867204/+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 1990729] [NEW] gdb crashes when run from VSCode
Public bug reported: I had no pre-existing breakpoints in VSCode, then added a breakpoint, and used F5 to run the debugger to the one breakpoint. It crashed before it got there. This is a C++ executable compiled for debugging using CMAKE. I can successfully debug the program using the TUI mode of gdb, so I think the problem likes in the vscode interface to gdb. /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: Assertion `arg->contents != nullptr' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: Assertion `arg->contents != nullptr' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdb 12.0.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21 Uname: Linux 5.14.0-1051-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 11:10:11 2022 InstallationDate: Installed on 2022-02-15 (221 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdb UpgradeStatus: Upgraded to jammy on 2022-09-06 (18 days ago) ** Affects: gdb (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 gdb in Ubuntu. https://bugs.launchpad.net/bugs/1990729 Title: gdb crashes when run from VSCode Status in gdb package in Ubuntu: New Bug description: I had no pre-existing breakpoints in VSCode, then added a breakpoint, and used F5 to run the debugger to the one breakpoint. It crashed before it got there. This is a C++ executable compiled for debugging using CMAKE. I can successfully debug the program using the TUI mode of gdb, so I think the problem likes in the vscode interface to gdb. /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: Assertion `arg->contents != nullptr' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: Assertion `arg->contents != nullptr' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdb 12.0.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21 Uname: Linux 5.14.0-1051-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 11:10:11 2022 InstallationDate: Installed on 2022-02-15 (221 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdb UpgradeStatus: Upgraded to jammy on 2022-09-06 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1990729/+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]
The TAS2563 works without the firmware (tuning file). Documentation: https://www.ti.com/product/TAS2553 However there is an android driver with firmware loading support. https://git.ti.com/cgit/tas256xsw-android/tas2563-android-driver/ Or a mainline RFC: https://lkml.org/lkml/2020/6/9/800 The bass speakers can be enabled with: i2cset 3 0x4c 0x2 0 i2cset 3 0x4d 0x2 0 they are listening on 0x48 too, so in one turn: i2cset 3 0x48 0x2 0 I don't know how safe it is to use it this way. They have to be enabled after suspend, and if you plug in-out the headphone (only if auto mute is enabled). -- 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 1958019]
Created attachment 301857 attachment-28445-0.html I am currently out of the office on holiday I will be returning on Monday September 26, I will not have access to email so replies will be delayed -- 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 1958019]
I have a Lenovo Yoga 7 14ARB7 too. I think it uses an TAS2563 amplifier chip. According to the windows driver it has a firmware too. There is some support in the kernel too. https://github.com/torvalds/linux/blob/master/sound/soc/codecs/tas2562.c The ACPI part: ``` Scope (_SB.I2CD) { Device (TAS) { Name (_HID, "INT8866") // _HID: Hardware ID Name (_UID, Zero) // _UID: Unique ID Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings { Name (RBUF, ResourceTemplate () { I2cSerialBusV2 (0x004C, ControllerInitiated, 0x00061A80, AddressingMode7Bit, "\\_SB.I2CD", 0x00, ResourceConsumer, , Exclusive, ) I2cSerialBusV2 (0x004D, ControllerInitiated, 0x00061A80, AddressingMode7Bit, "\\_SB.I2CD", 0x00, ResourceConsumer, , Exclusive, ) GpioInt (Edge, ActiveLow, SharedAndWake, PullNone, 0x, "\\_SB.GPIO", 0x00, ResourceConsumer, , ) { // Pin list 0x0020 } }) Return (RBUF) /* \_SB_.I2CD.TAS_._CRS.RBUF */ } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0F) } } } ``` -- 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 1981622] Re: mtd device must be supplied (device name is empty)
I reported the bug here: https://bugs.launchpad.net/ubuntu/+bug/1990723 Seems to affect quite some people (via other discussions), please help. -- 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/1981622 Title: mtd device must be supplied (device name is empty) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [WORKAROUND] This will NOT fix a system that is not booting, because the "mtd device must be supplied (device name is empty)" message is not the cause of failed boots. This work around is only for those who are annoyed by the error message, but are otherwise not experiencing any issues. If you are not able to boot your system, but you see this error message, please open a separate bug with your journalctl and dmesg logs. # cp /{lib,etc}/systemd/system/systemd-pstore.service # sed -i 's/modprobe@mtdpstore.service //' /etc/systemd/system/systemd-pstore.service # systemctl daemon-reload [Impact] Due to mtdpstore not being properly configured as a pstore backend, when systemd-pstore.service tries to load the module, users get the following error in dmesg: [ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore... [ 18.462685] mtd device must be supplied (device name is empty) This is a distracting error for users trying to diagnose other system issues, especially if their system does not boot after a kernel crash and this is the only message displayed on the console. [Test Plan] * Force a kernel crash to populate /sys/fs/pstore, thus causing systemd-pstore.service to start on the subsequent boot: # echo 1 > /proc/sys/kernel/sysrq # echo 1 > /proc/sys/kernel/panic # echo c > /proc/sysrq-trigger * When the system reboots, observe the error in dmesg: # dmesg | grep mtd [Where problems could occur] If a system was relying on this pstore backend, and mtdpstore is built as a module, it is possible for systemd-pstore.service to trigger before mtdpstore is loaded, causing systemd-pstore to not copy the contents of /sys/fs/pstore. Note however that before the patched introduced as a result of bug 1978079, systemd-pstore.service would not attempt to load *any* kernel modules. [Original Description] After updating my 22.04 system (possibly caused by Systemd update). And now booting, dmesg has two errors: 'mtd device must be supplied (device name is empty)'. See line 8 and 134 in the included logfile. The system are booting as it should though, and the system are working like it should no errors at all. Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in systemd? I have an EFI mounted at boot but it isn't used because I have installed my system in legacy BIOS mode. Is this maybe the culprit? I could ignore the message but it isn't nice though. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1990064] Re: unconfined profile denies userns_create for chromium based processes
I'm still trying to understand the exact implications of this, since I make extensive use of LXC containers, using subuid/subgid mapping, so that users can create containers without needing access to UID 0. Are we talking about blocking namespaces where UID 0 in the container is mapped to the real UID 0, or will it also impact containers where UID 0 in the container is mapped to some other UID. -- 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/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1981622] Re: mtd device must be supplied (device name is empty)
@dbungert Updated to 249-11-0ubuntu3.6 using normal repository. The error " mtd device must be supplied (device name is empty)" disappeared. [actually with normal sudo apt upgrade nothing was being upgraded saying "The following packages have been kept back: . Solution 2 here did the job https://askubuntu.com/questions/601/the-following-packages-have-been-kept-back-why-and-how-do-i-solve-it ] Yet, I am left with an emergency terminal and no graphical interface. I can log in and use this minimal terminal. I can copy the whole output of "sudo dmesg" if helps. If I launch firefox from terminal I get (copied by hand, sorry for typos): [several errors probably not related] Error: no DISPLAY envirnoment variable specified If I launch Nautilus: org.gnome.Nautilus:1880: Gtk-warning 15:02:03.113 cannot open displays Launching spotify gives a verbose segmentation fault, output to a file in the home folder. Launching Thunderbird gives Error: nbo DISPLAY environment variable specified etc etc I will open another thread, as the initial bug seems not related to the major breakdown of the whole graphical interface. Thank you Dan in the meantime. -- 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/1981622 Title: mtd device must be supplied (device name is empty) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [WORKAROUND] This will NOT fix a system that is not booting, because the "mtd device must be supplied (device name is empty)" message is not the cause of failed boots. This work around is only for those who are annoyed by the error message, but are otherwise not experiencing any issues. If you are not able to boot your system, but you see this error message, please open a separate bug with your journalctl and dmesg logs. # cp /{lib,etc}/systemd/system/systemd-pstore.service # sed -i 's/modprobe@mtdpstore.service //' /etc/systemd/system/systemd-pstore.service # systemctl daemon-reload [Impact] Due to mtdpstore not being properly configured as a pstore backend, when systemd-pstore.service tries to load the module, users get the following error in dmesg: [ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore... [ 18.462685] mtd device must be supplied (device name is empty) This is a distracting error for users trying to diagnose other system issues, especially if their system does not boot after a kernel crash and this is the only message displayed on the console. [Test Plan] * Force a kernel crash to populate /sys/fs/pstore, thus causing systemd-pstore.service to start on the subsequent boot: # echo 1 > /proc/sys/kernel/sysrq # echo 1 > /proc/sys/kernel/panic # echo c > /proc/sysrq-trigger * When the system reboots, observe the error in dmesg: # dmesg | grep mtd [Where problems could occur] If a system was relying on this pstore backend, and mtdpstore is built as a module, it is possible for systemd-pstore.service to trigger before mtdpstore is loaded, causing systemd-pstore to not copy the contents of /sys/fs/pstore. Note however that before the patched introduced as a result of bug 1978079, systemd-pstore.service would not attempt to load *any* kernel modules. [Original Description] After updating my 22.04 system (possibly caused by Systemd update). And now booting, dmesg has two errors: 'mtd device must be supplied (device name is empty)'. See line 8 and 134 in the included logfile. The system are booting as it should though, and the system are working like it should no errors at all. Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in systemd? I have an EFI mounted at boot but it isn't used because I have installed my system in legacy BIOS mode. Is this maybe the culprit? I could ignore the message but it isn't nice though. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot
This misleading reboot message still occurs in Sep 2022. I try to upgrade from hirsute to jammy. Not sure how many minutes my upgrade stuck, but thankfully it was resumed while I read this thread. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1968845 Title: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot Status in dbus package in Ubuntu: Triaged Bug description: Upgrading on a virtual machine from 20.04 to 22.04. I have had this happen twice now, I got one upgrade done without this bug. Basically the package installation stops at dbus package asking for a reboot as it was unable to upgrade as dbus-daemon was running. And rebooting at this stage obviously will cause a non-functioning system. Added a screenshot of the upgrade window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1990562] Re: attempting to diff static library files raises UnicodeDecodeError
** Tags added: ftbfs ** Also affects: numpy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1990562 Title: attempting to diff static library files raises UnicodeDecodeError Status in dh-python package in Ubuntu: Confirmed Status in numpy package in Ubuntu: New Status in dh-python package in Debian: Fix Released Bug description: In verbose mode, if files differ in share_files(), dhpython will try to show a diff of the files. When these files are static libraries, this raises a UnicodeDecodeError. For example, from a recent numpy build on arm64[1]: W: dh_python3 fs:146: Paths differ: debian/python3-numpy/usr/lib/python3.10/dist-packages/numpy/random/lib/libnpyrandom.a and debian/python3-numpy/usr/lib/python3/dist-packages/numpy/random/lib/libnpyrandom.a Traceback (most recent call last): File "/usr/bin/dh_python3", line 284, in main() File "/usr/bin/dh_python3", line 210, in main fix_locations(package, interpreter, SUPPORTED, options) File "/usr/share/dh-python/dhpython/fs.py", line 53, in fix_locations share_files(srcdir, dstdir, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 127, in share_files share_files(fpath1, fpath2, interpreter, options) File "/usr/share/dh-python/dhpython/fs.py", line 149, in share_files fromlines = fp1.readlines() File "/usr/lib/python3.10/codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 75: invalid start byte make[1]: *** [debian/rules:46: override_dh_python3] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:15: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 There is already logic to skip this diff for .so files, so the same should be done for .a files. [1] https://launchpadlibrarian.net/624822201/buildlog_ubuntu-kinetic- arm64.numpy_1%3A1.21.5-1build2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1990562/+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