[Touch-packages] [Bug 1842284] Re: initramfs does not copy ehci-platform
Tested on x86 xenial-hwe. `update-initramfs` works and no ehci-platform in initrd. System works fine after reboot. ubuntu@zwicky:~$ sudo update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-4.15.0-65-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. update-initramfs: Generating /boot/initrd.img-4.15.0-64-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. ubuntu@zwicky:~$ ls -al /boot total 131680 drwxr-xr-x 4 root root 4096 Sep 26 04:20 . drwxr-xr-x 23 root root 4096 Sep 26 04:15 .. -rw-r--r-- 1 root root 217381 Sep 13 11:11 config-4.15.0-64-generic -rw-r--r-- 1 root root 217370 Sep 18 11:06 config-4.15.0-65-generic drwxr-xr-x 3 root root 4096 Jan 1 1970 efi drwxr-xr-x 5 root root 4096 Sep 26 04:16 grub -rw-r--r-- 1 root root 54946864 Sep 26 04:20 initrd.img-4.15.0-64-generic -rw-r--r-- 1 root root 54945126 Sep 26 04:19 initrd.img-4.15.0-65-generic -rw--- 1 root root 4061501 Sep 13 11:11 System.map-4.15.0-64-generic -rw--- 1 root root 4062077 Sep 18 11:06 System.map-4.15.0-65-generic -rw--- 1 root root 8172440 Sep 17 19:28 vmlinuz-4.15.0-64-generic -rw--- 1 root root 8181016 Sep 19 08:08 vmlinuz-4.15.0-65-generic ubuntu@zwicky:~$ sudo dpkg -l | grep initramfs-tools-core ii initramfs-tools-core 0.122ubuntu8.15 all generic modular initramfs generator (core tools) ubuntu@zwicky:~/temp$ dd if=/boot/initrd.img-4.15.0-65-generic of=initrd.img bs=512 skip=4768; zcat initrd.img | cpio -i 102546+1 records in 102546+1 records out 52503910 bytes (53 MB, 50 MiB) copied, 0.17038 s, 308 MB/s 296093 blocks ubuntu@zwicky:~/temp$ ls bin conf etc init initrd.img lib lib64 run sbin scripts usr var ubuntu@zwicky:~/temp$ find . -name '*hci*' ./lib/modules/4.15.0-65-generic/kernel/drivers/mmc/host/sdhci-pci.ko ./lib/modules/4.15.0-65-generic/kernel/drivers/mmc/host/sdhci.ko ./lib/modules/4.15.0-65-generic/kernel/drivers/mmc/host/sdhci-xenon-driver.ko ./lib/modules/4.15.0-65-generic/kernel/drivers/mmc/host/sdhci-acpi.ko ./lib/modules/4.15.0-65-generic/kernel/drivers/mmc/host/sdhci-pltfm.ko ./lib/modules/4.15.0-65-generic/kernel/drivers/usb/host/xhci-plat-hcd.ko ./lib/modules/4.15.0-65-generic/kernel/drivers/ata/acard-ahci.ko ./lib/modules/4.15.0-65-generic/kernel/drivers/ata/ahci_platform.ko ./lib/modules/4.15.0-65-generic/kernel/drivers/ata/ahci.ko ./lib/modules/4.15.0-65-generic/kernel/drivers/ata/libahci_platform.ko ./lib/modules/4.15.0-65-generic/kernel/drivers/ata/libahci.ko ./lib/modules/4.15.0-65-generic/kernel/drivers/firewire/firewire-ohci.ko ubuntu@zwicky:~/temp$ uname -a Linux zwicky 4.15.0-65-generic #74~16.04.1-Ubuntu SMP Wed Sep 18 09:51:44 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- 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/1842284 Title: initramfs does not copy ehci-platform Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Disco: Fix Released Status in initramfs-tools source package in Eoan: Fix Released Bug description: [Impact] If you install Ubuntu onto USB storage behind a Platform USB host controller, it will not be able to boot because the generated initramfs will not include the host controller driver. [Test Case] Install to a USB stick attached to platform USB controller and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] Driver is only loaded when system requires ehci-platform, minimizing the impact to all other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1842284/+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 1838146] Re: ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on *.ntp.org
[Expired for ntp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ntp (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1838146 Title: ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on *.ntp.org Status in ntp package in Ubuntu: Expired Bug description: When you install 'ntp' the /etc/ntp.conf it writes refers to the following: - *.ubuntu.ntp.org This hostname name and subdomain doesn't exist, it would be better if you just import and write http://ntp.snails.email/v1/ntp.conf alternatively make a file that randomly selects the pool and server from http://ntp.snails.email/v1/online.json --> so you download the .json, and then have somewhere on *.ubuntu.com that has a ntp.conf it will and randomly compile alist of pool items from the .json --> this will stop chronologistic buffering convulsive environments... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1838146/+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 966868] Re: plymouthd crashed with SIGABRT in __assert_fail_base()
** Changed in: xserver-xorg-video-intel Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/mesa/drm/issues #8 https://gitlab.freedesktop.org/mesa/drm/issues/8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/966868 Title: plymouthd crashed with SIGABRT in __assert_fail_base() Status in xf86-video-intel: Unknown Status in libdrm package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Invalid Bug description: After a force restart of Ubuntu, I've got a System Crash error after logging in. lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 Thanks! ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: plymouth 0.8.2-2ubuntu28 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 09:33:16 2012 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120322) MachineType: LENOVO 4284BZ4 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=f1bb4518-a890-49c0-9339-ecc3d8bd2658 ro quiet splash vt.handoff=7 ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=f1bb4518-a890-49c0-9339-ecc3d8bd2658 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Title: plymouthd crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284BZ4 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:bvr8BET56WW(1.36):bd01/19/2012:svnLENOVO:pn4284BZ4:pvrThinkPadW520:rvnLENOVO:rn4284BZ4:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4284BZ4 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/966868/+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 966868]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/drm/issues/8. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/966868 Title: plymouthd crashed with SIGABRT in __assert_fail_base() Status in xf86-video-intel: Unknown Status in libdrm package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Invalid Bug description: After a force restart of Ubuntu, I've got a System Crash error after logging in. lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 Thanks! ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: plymouth 0.8.2-2ubuntu28 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 09:33:16 2012 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120322) MachineType: LENOVO 4284BZ4 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=f1bb4518-a890-49c0-9339-ecc3d8bd2658 ro quiet splash vt.handoff=7 ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=f1bb4518-a890-49c0-9339-ecc3d8bd2658 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Title: plymouthd crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284BZ4 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:bvr8BET56WW(1.36):bd01/19/2012:svnLENOVO:pn4284BZ4:pvrThinkPadW520:rvnLENOVO:rn4284BZ4:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4284BZ4 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/966868/+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 1832421] Re: openssl reboot needed message using incorrect path to X server
Seems to work fine on disco: sarnold@millbarge:~$ sudo apt install libssl1.1 openssl Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-image-5.0.0-20-generic linux-image-5.0.0-21-generic linux-image-5.0.0-23-generic linux-modules-5.0.0-20-generic linux-modules-5.0.0-21-generic linux-modules-5.0.0-23-generic linux-modules-extra-5.0.0-20-generic linux-modules-extra-5.0.0-21-generic linux-modules-extra-5.0.0-23-generic Use 'sudo apt autoremove' to remove them. The following packages will be upgraded: libssl1.1 openssl 2 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. Need to get 1,928 kB of archives. After this operation, 15.4 kB of additional disk space will be used. Get:1 http://wopr/ubuntu disco-proposed/main amd64 libssl1.1 amd64 1.1.1b-1ubuntu2.4 [1,305 kB] Get:2 http://wopr/ubuntu disco-proposed/main amd64 openssl amd64 1.1.1b-1ubuntu2.4 [624 kB] Fetched 1,928 kB in 0s (15.5 MB/s) Preconfiguring packages ... (Reading database ... 91100 files and directories currently installed.) Preparing to unpack .../libssl1.1_1.1.1b-1ubuntu2.4_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1b-1ubuntu2.4) over (1.1.1b-1ubuntu2.1) ... Preparing to unpack .../openssl_1.1.1b-1ubuntu2.4_amd64.deb ... Unpacking openssl (1.1.1b-1ubuntu2.4) over (1.1.1b-1ubuntu2.1) ... Setting up libssl1.1:amd64 (1.1.1b-1ubuntu2.4) ... Setting up openssl (1.1.1b-1ubuntu2.4) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.29-0ubuntu2) ... sarnold@millbarge:~$ sudo apt install libssl1.1=1.1.1b-1ubuntu2.1 openssl=1.1.1b-1ubuntu2.1 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-image-5.0.0-20-generic linux-image-5.0.0-21-generic linux-image-5.0.0-23-generic linux-modules-5.0.0-20-generic linux-modules-5.0.0-21-generic linux-modules-5.0.0-23-generic linux-modules-extra-5.0.0-20-generic linux-modules-extra-5.0.0-21-generic linux-modules-extra-5.0.0-23-generic Use 'sudo apt autoremove' to remove them. The following packages will be DOWNGRADED: libssl1.1 openssl 0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 23 not upgraded. Need to get 0 B/1,921 kB of archives. After this operation, 15.4 kB disk space will be freed. Do you want to continue? [Y/n] Preconfiguring packages ... dpkg: warning: downgrading libssl1.1:amd64 from 1.1.1b-1ubuntu2.4 to 1.1.1b-1ubuntu2.1 (Reading database ... 91100 files and directories currently installed.) Preparing to unpack .../libssl1.1_1.1.1b-1ubuntu2.1_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1b-1ubuntu2.1) over (1.1.1b-1ubuntu2.4) ... dpkg: warning: downgrading openssl from 1.1.1b-1ubuntu2.4 to 1.1.1b-1ubuntu2.1 Preparing to unpack .../openssl_1.1.1b-1ubuntu2.1_amd64.deb ... Unpacking openssl (1.1.1b-1ubuntu2.1) over (1.1.1b-1ubuntu2.4) ... Setting up libssl1.1:amd64 (1.1.1b-1ubuntu2.1) ... Setting up openssl (1.1.1b-1ubuntu2.1) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.29-0ubuntu2) ... sarnold@millbarge:~$ sudo apt install libssl1.1 openssl Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-image-5.0.0-20-generic linux-image-5.0.0-21-generic linux-image-5.0.0-23-generic linux-modules-5.0.0-20-generic linux-modules-5.0.0-21-generic linux-modules-5.0.0-23-generic linux-modules-extra-5.0.0-20-generic linux-modules-extra-5.0.0-21-generic linux-modules-extra-5.0.0-23-generic Use 'sudo apt autoremove' to remove them. The following packages will be upgraded: libssl1.1 openssl 2 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. Need to get 1,928 kB of archives. After this operation, 15.4 kB of additional disk space will be used. Get:1 http://wopr/ubuntu disco-proposed/main amd64 libssl1.1 amd64 1.1.1b-1ubuntu2.4 [1,305 kB] Get:2 http://wopr/ubuntu disco-proposed/main amd64 openssl amd64 1.1.1b-1ubuntu2.4 [624 kB] Fetched 1,928 kB in 0s (68.3 MB/s) Preconfiguring packages ... (Reading database ... 91100 files and directories currently installed.) Preparing to unpack .../libssl1.1_1.1.1b-1ubuntu2.4_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1b-1ubuntu2.4) over (1.1.1b-1ubuntu2.1) ... Preparing to unpack .../openssl_1.1.1b-1ubuntu2.4_amd64.deb ... Unpacking openssl (1.1.1b-1ubuntu2.4) over (1.1.1b-1ubuntu2.1) ... Setting up libssl1.1:amd64 (1.1.1b-1ubuntu2.4) ... Setting up openssl (1.1.1b-1ubuntu2.4) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.29-0ubuntu2) ... ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu.
[Touch-packages] [Bug 1832522] Re: openssl maintainer scripts do not trigger services restart
Seems to work fine from disco: sarnold@millbarge:~$ sudo apt install libssl1.1 openssl Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-image-5.0.0-20-generic linux-image-5.0.0-21-generic linux-image-5.0.0-23-generic linux-modules-5.0.0-20-generic linux-modules-5.0.0-21-generic linux-modules-5.0.0-23-generic linux-modules-extra-5.0.0-20-generic linux-modules-extra-5.0.0-21-generic linux-modules-extra-5.0.0-23-generic Use 'sudo apt autoremove' to remove them. The following packages will be upgraded: libssl1.1 openssl 2 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. Need to get 1,928 kB of archives. After this operation, 15.4 kB of additional disk space will be used. Get:1 http://wopr/ubuntu disco-proposed/main amd64 libssl1.1 amd64 1.1.1b-1ubuntu2.4 [1,305 kB] Get:2 http://wopr/ubuntu disco-proposed/main amd64 openssl amd64 1.1.1b-1ubuntu2.4 [624 kB] Fetched 1,928 kB in 0s (15.5 MB/s) Preconfiguring packages ... (Reading database ... 91100 files and directories currently installed.) Preparing to unpack .../libssl1.1_1.1.1b-1ubuntu2.4_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1b-1ubuntu2.4) over (1.1.1b-1ubuntu2.1) ... Preparing to unpack .../openssl_1.1.1b-1ubuntu2.4_amd64.deb ... Unpacking openssl (1.1.1b-1ubuntu2.4) over (1.1.1b-1ubuntu2.1) ... Setting up libssl1.1:amd64 (1.1.1b-1ubuntu2.4) ... Setting up openssl (1.1.1b-1ubuntu2.4) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.29-0ubuntu2) ... sarnold@millbarge:~$ sudo apt install libssl1.1=1.1.1b-1ubuntu2.1 openssl=1.1.1b-1ubuntu2.1 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-image-5.0.0-20-generic linux-image-5.0.0-21-generic linux-image-5.0.0-23-generic linux-modules-5.0.0-20-generic linux-modules-5.0.0-21-generic linux-modules-5.0.0-23-generic linux-modules-extra-5.0.0-20-generic linux-modules-extra-5.0.0-21-generic linux-modules-extra-5.0.0-23-generic Use 'sudo apt autoremove' to remove them. The following packages will be DOWNGRADED: libssl1.1 openssl 0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 23 not upgraded. Need to get 0 B/1,921 kB of archives. After this operation, 15.4 kB disk space will be freed. Do you want to continue? [Y/n] Preconfiguring packages ... dpkg: warning: downgrading libssl1.1:amd64 from 1.1.1b-1ubuntu2.4 to 1.1.1b-1ubuntu2.1 (Reading database ... 91100 files and directories currently installed.) Preparing to unpack .../libssl1.1_1.1.1b-1ubuntu2.1_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1b-1ubuntu2.1) over (1.1.1b-1ubuntu2.4) ... dpkg: warning: downgrading openssl from 1.1.1b-1ubuntu2.4 to 1.1.1b-1ubuntu2.1 Preparing to unpack .../openssl_1.1.1b-1ubuntu2.1_amd64.deb ... Unpacking openssl (1.1.1b-1ubuntu2.1) over (1.1.1b-1ubuntu2.4) ... Setting up libssl1.1:amd64 (1.1.1b-1ubuntu2.1) ... Setting up openssl (1.1.1b-1ubuntu2.1) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.29-0ubuntu2) ... sarnold@millbarge:~$ sudo apt install libssl1.1 openssl Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-image-5.0.0-20-generic linux-image-5.0.0-21-generic linux-image-5.0.0-23-generic linux-modules-5.0.0-20-generic linux-modules-5.0.0-21-generic linux-modules-5.0.0-23-generic linux-modules-extra-5.0.0-20-generic linux-modules-extra-5.0.0-21-generic linux-modules-extra-5.0.0-23-generic Use 'sudo apt autoremove' to remove them. The following packages will be upgraded: libssl1.1 openssl 2 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. Need to get 1,928 kB of archives. After this operation, 15.4 kB of additional disk space will be used. Get:1 http://wopr/ubuntu disco-proposed/main amd64 libssl1.1 amd64 1.1.1b-1ubuntu2.4 [1,305 kB] Get:2 http://wopr/ubuntu disco-proposed/main amd64 openssl amd64 1.1.1b-1ubuntu2.4 [624 kB] Fetched 1,928 kB in 0s (68.3 MB/s) Preconfiguring packages ... (Reading database ... 91100 files and directories currently installed.) Preparing to unpack .../libssl1.1_1.1.1b-1ubuntu2.4_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1b-1ubuntu2.4) over (1.1.1b-1ubuntu2.1) ... Preparing to unpack .../openssl_1.1.1b-1ubuntu2.4_amd64.deb ... Unpacking openssl (1.1.1b-1ubuntu2.4) over (1.1.1b-1ubuntu2.1) ... Setting up libssl1.1:amd64 (1.1.1b-1ubuntu2.4) ... Setting up openssl (1.1.1b-1ubuntu2.4) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.29-0ubuntu2) ... ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,
[Touch-packages] [Bug 1844524] Re: text relocation of grep prevents its use under udevd
This bug was fixed in the package grep - 3.1-2build1 --- grep (3.1-2build1) bionic; urgency=medium * No change rebuild. (LP: #1844524) -- Tiago Stürmer Daitx Wed, 18 Sep 2019 15:00:16 + ** Changed in: grep (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1844524 Title: text relocation of grep prevents its use under udevd Status in grep package in Ubuntu: Fix Released Status in grep source package in Bionic: Fix Released Bug description: [Impact] grep can't be used under udev, preventing kdump-tools to be used after a memory hotplug. [Test case] Run grep with systemd-run -t --property MemoryDenyWriteExecute=yes /bin/grep crashkernel /proc/cmdline [Regression potential] The fix is a simple rebuild, so should have minimal potential for regression. - # systemd-run -t --property MemoryDenyWriteExecute=yes /bin/grep crashkernel /proc/cmdline Running as unit: run-u54.service Press ^] three times within 1s to disconnect TTY. /bin/grep: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted # Under ppc64el, grep can't be used under udev, because it restricts mapping to be Write+Execute, with MemoryDenyWriteExecute=yes. A rebuild of grep under bionic fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1844524/+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 1844524] Update Released
The verification of the Stable Release Update for grep has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1844524 Title: text relocation of grep prevents its use under udevd Status in grep package in Ubuntu: Fix Released Status in grep source package in Bionic: Fix Released Bug description: [Impact] grep can't be used under udev, preventing kdump-tools to be used after a memory hotplug. [Test case] Run grep with systemd-run -t --property MemoryDenyWriteExecute=yes /bin/grep crashkernel /proc/cmdline [Regression potential] The fix is a simple rebuild, so should have minimal potential for regression. - # systemd-run -t --property MemoryDenyWriteExecute=yes /bin/grep crashkernel /proc/cmdline Running as unit: run-u54.service Press ^] three times within 1s to disconnect TTY. /bin/grep: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted # Under ppc64el, grep can't be used under udev, because it restricts mapping to be Write+Execute, with MemoryDenyWriteExecute=yes. A rebuild of grep under bionic fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1844524/+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 1842284] Re: initramfs does not copy ehci-platform
Has there been any testing performed on the architectures on which the module is compiled in please, for example amd64? It seems to me that this is a particularly important code path to test, since it is identified as different and a bug could render regressed systems unbootable. -- 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/1842284 Title: initramfs does not copy ehci-platform Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Disco: Fix Released Status in initramfs-tools source package in Eoan: Fix Released Bug description: [Impact] If you install Ubuntu onto USB storage behind a Platform USB host controller, it will not be able to boot because the generated initramfs will not include the host controller driver. [Test Case] Install to a USB stick attached to platform USB controller and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] Driver is only loaded when system requires ehci-platform, minimizing the impact to all other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1842284/+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 1843630] Re: ubuntu-bug not opening anything in the browser
*** This bug is a duplicate of bug 1814611 *** https://bugs.launchpad.net/bugs/1814611 This is a duplicate of bug 1814611 which we are planning on fixing. If you want to be able to use ubuntu-bug in the interim you'll need to set "Send error reports to Canonical" to On. ** This bug has been marked a duplicate of bug 1814611 turning off "Send error reports to Canonical" prevents using ubuntu-bug -- 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/1843630 Title: ubuntu-bug not opening anything in the browser Status in apport package in Ubuntu: New Bug description: Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to the developers?" with the "Don't send" and "Send" buttons, but when I click on "Send" nothing happens. I have the "problem_types" line commented out in /etc/apport/crashdb.conf, though I don't know if that's relevant when I'm trying to report a bug, not a crash. I have no idea how to troubleshoot this further. Please advise. The same problem occurs for "ubuntu-bug needrestart". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+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 1845373] [NEW] Problem with wine
Public bug reported: Can't run wine64. I googled and they told me i have problem with my graphic card drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 25 21:34:07 2019 DistUpgraded: 2019-09-24 14:25:44,600 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2019-04-03 (175 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 2325SWM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=2cbc3e95-5ad2-4cf3-a14d-63d9dc958d7a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-09-24 (1 days ago) dmi.bios.date: 08/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325SWM 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET96WW(2.56):bd08/27/2013:svnLENOVO:pn2325SWM:pvrThinkPadX230:rvnLENOVO:rn2325SWM:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2325SWM dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.4-1ubuntu1~18.04~ppa3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.1.4-1ubuntu1~18.04~ppa3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Tue Sep 24 09:45:45 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages 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/1845373 Title: Problem with wine Status in xorg package in Ubuntu: New Bug description: Can't run wine64. I googled and they told me i have problem with my graphic card drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 25 21:34:07 2019 DistUpgraded: 2019-09-24 14:25:44,600 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2019-04-03 (175 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 2325SWM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=2cbc3e95-5ad2-4cf3-a14d-63d9dc958d7a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-09-24 (1 days ago) dmi.bios.date: 08/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325SWM 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: Not Available dmi.modalias:
[Touch-packages] [Bug 1845337] Re: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service
@laney maybe you know if the armhf testbeds were recently moved from lxd to lxc containers? -- 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/1845337 Title: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Status in qemu source package in Disco: New Status in systemd source package in Disco: New Bug description: Since the recent few weeks systemd autopkgtest @ armhf @ disco fail [1]. The log is very (very) long and partially interwoven due to concurrent execution. Somewhere in between we see this subcase is the one failing: root-unittests Of this test (which again has many subtests) it is: test-execute And of this again it is (always): I'll attach bad and good case full and stripped logs. The diff of those comes down to just: 1. execute a find in a shell 2. shell exits 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=0/SUCCESS vs 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=1/FAILURE 4. in the bad case that triggers an assertion The find that fails is: find / -path /var/tmp -o -path /tmp -o -path /proc -o -path /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf Good and bad case are the same most recent version systemd/240-6ubuntu5.7. Maybe something is bad in the containers we have for armhf in regard to these paths? Was there any change we'd know of? If there is nothing known, could we force-badtest it to get it out of the way of ongoing migrations? [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+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 1844853] Re: IBus no longer works in Qt applications after upgrade
** Changed in: ibus (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: Fix Released Status in ibus package in Ubuntu: Fix Released Status in ibus package in Debian: Confirmed Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+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 1845337] Re: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service
The 'good' tests have a dir being mounted '/dev/.lxd-mounts' while the 'bad' tests have a dir being mounted '/dev/.lxc' as well as '/dev/.lxc/proc'. In the 'bad' case, the test is making sure there are no unexpected writable directories other than the single one it's expecting (and other expected ones which are ignored, e.g. /tmp, /var/tmp, ...), and it's finding a writable dir under /dev/.lxc/ that it of course wasn't expecting: + test /dev/.lxc/proc/1079/fd/dev/.lxc/proc/1079/map_files/dev/.lxc/proc/1079/task/1079/fd/var/lib/private/quux/pief/var/lib/private/waldo = /var/lib/private/quux/pief/var/lib/private/waldo something (maybe lxc itself?) seems to be mounting /proc under the /dev/.lxc dir, or something like that...when using lxd, that problem doesn't seem to happen. I'd be inclined to blame lxc for this, not the test itself. Did the armhf testbeds get changed from lxd to lxc recently? -- 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/1845337 Title: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Status in qemu source package in Disco: New Status in systemd source package in Disco: New Bug description: Since the recent few weeks systemd autopkgtest @ armhf @ disco fail [1]. The log is very (very) long and partially interwoven due to concurrent execution. Somewhere in between we see this subcase is the one failing: root-unittests Of this test (which again has many subtests) it is: test-execute And of this again it is (always): I'll attach bad and good case full and stripped logs. The diff of those comes down to just: 1. execute a find in a shell 2. shell exits 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=0/SUCCESS vs 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=1/FAILURE 4. in the bad case that triggers an assertion The find that fails is: find / -path /var/tmp -o -path /tmp -o -path /proc -o -path /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf Good and bad case are the same most recent version systemd/240-6ubuntu5.7. Maybe something is bad in the containers we have for armhf in regard to these paths? Was there any change we'd know of? If there is nothing known, could we force-badtest it to get it out of the way of ongoing migrations? [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+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 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
@tf8 the patch in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/comments/8 against a live server has been working fine for us on AWS for almost a year now. -- 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/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Confirmed Status in systemd source package in Disco: Confirmed Bug description: [Impact] Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state? Application that require Name Resolution may fail while the service is being unnecessarily restarted [Test case] (1) Append make_resolv_conf to the end of the file, so it gets executed (2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example: sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart [Regression potential] The change only restarts resolved when the settings change. If there's a bug in the logic, resolved might not be restarted when it should be. Also, since there will be less restarts of resolved, it will run longer, so if there are memory leaks they will become more apparent. [Original bug report] If a cloud server is upgraded from Xenial to Bionic, the dhclient system remains in place and any DHCP lease refreshes cause a needless restart of the system-resolved daemon Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d) Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 10.226.209.105 Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors: Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 'srv-qvjhx'. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting resolvconf-pull-resolved.service... Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal in 1466 seconds. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started resolvconf-pull-resolved.service. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.25 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu Date: Mon Nov 26 16:17:52 2018 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+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 1843630] Re: ubuntu-bug not opening anything in the browser
jik@jik5:~$ sudo systemctl is-enabled whoopsie disabled -- 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/1843630 Title: ubuntu-bug not opening anything in the browser Status in apport package in Ubuntu: New Bug description: Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to the developers?" with the "Don't send" and "Send" buttons, but when I click on "Send" nothing happens. I have the "problem_types" line commented out in /etc/apport/crashdb.conf, though I don't know if that's relevant when I'm trying to report a bug, not a crash. I have no idea how to troubleshoot this further. Please advise. The same problem occurs for "ubuntu-bug needrestart". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+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 1843630] Re: ubuntu-bug not opening anything in the browser
Can you run 'systemctl is-enabled whoopsie' and paste the output? Thanks again! -- 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/1843630 Title: ubuntu-bug not opening anything in the browser Status in apport package in Ubuntu: New Bug description: Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to the developers?" with the "Don't send" and "Send" buttons, but when I click on "Send" nothing happens. I have the "problem_types" line commented out in /etc/apport/crashdb.conf, though I don't know if that's relevant when I'm trying to report a bug, not a crash. I have no idea how to troubleshoot this further. Please advise. The same problem occurs for "ubuntu-bug needrestart". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+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 1845314] Re: udisks2 fails to install in a container with systemd 243
** Changed in: systemd Status: Unknown => New -- 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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1845314/+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 90085] Re: When /tmp is mounted noexec, preconfigure fails
On Ubuntu 18.04 with noexec on /tmp running 'apt-get install -y selinux' and then doing a required reboot will give you a non-booting host. As an aside, the same security guidance (CIS Benchmarks for one) about noexec on /tmp should be applied to /var/tmp, so changing APT::ExtractTemplates::TempDir to "/var/tmp"; isn't really an option here in the long run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/90085 Title: When /tmp is mounted noexec, preconfigure fails Status in debconf package in Ubuntu: Triaged Status in debconf package in Debian: Confirmed Bug description: Binary package hint: mysql-server /tmp mounted noexec, this ensues: Preconfiguring packages ... Can't exec "/tmp/mysql-server-5.0.config.89611": Permission denied at /usr/share/perl/5.8/IPC/Open3.pm line 168. open2: exec of /tmp/mysql-server-5.0.config.89611 configure failed at /usr/share/perl5/Debconf/ConfModule.pm line 57 mysql-server-5.0 failed to preconfigure, with exit status 2 ace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/90085/+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 1845314] Re: udisks2 fails to install in a container with systemd 243
On thinking about this, it does seem the behavior change of udevadm will be highly disruptive to existing callers of udevadm trigger, so I opened upstream bug to try to address it without needing all callers to ignore its return code. ** Bug watch added: github.com/systemd/systemd/issues #13652 https://github.com/systemd/systemd/issues/13652 ** Also affects: systemd via https://github.com/systemd/systemd/issues/13652 Importance: Unknown Status: Unknown -- 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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd: Unknown Status in systemd package in Ubuntu: Confirmed Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1845314/+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 1845356] [NEW] decolorisation on my laptop display
Public bug reported: Kindly help me to rid of this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 25 22:13:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:183f] InstallationDate: Installed on 2018-11-04 (324 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic root=UUID=67b0c5c4-824b-4a8c-a3dd-fb3e69e70c4b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183F dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.2D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.17:bd11/01/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr0889110859160:rvnHewlett-Packard:rn183F:rvr56.2D:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.version: 0889110859160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages 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/1845356 Title: decolorisation on my laptop display Status in xorg package in Ubuntu: New Bug description: Kindly help me to rid of this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 25 22:13:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:183f] InstallationDate: Installed on 2018-11-04 (324 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic root=UUID=67b0c5c4-824b-4a8c-a3dd-fb3e69e70c4b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183F dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.2D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.17:bd11/01/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr0889110859160:rvnHewlett-Packard:rn183F:rvr56.2D:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC
[Touch-packages] [Bug 1845332] Re: Compose key does not create strings
Thanks for your report! Hmm... That wiki page you referred to was last edited 11 years ago and is obsolete to a large extent. Today, on an Ubuntu system, it's normally GTK (not IBus, so I'm closing this bug report) which deals with rules in the ~/.XCompose file. I can confirm that GTK does not seem to be able to handle multi character strings. But if I switch to XIM it works for me. * Open Language Support and change the "Keyboard input method system" to "XIM" * Reboot Please note, though, that replacing "IBus" with "XIM" may result in other subtle issues. ** Changed in: ibus (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1845332 Title: Compose key does not create strings Status in ibus package in Ubuntu: Invalid Bug description: According to manual https://wiki.ubuntu.com/ComposeKey it is possible to define sequences to type characters and strings with Compose key. In Ubuntu 18.04 sequences work for characters but not for strings, line like this: : "by the way" # Compose b t w seems to be ignored. $ apt-cache policy ibus ibus: Installed: 1.5.17-3ubuntu5.2 Candidate: 1.5.17-3ubuntu5.2 Version table: *** 1.5.17-3ubuntu5.2 500 500 http://mirror.isoc.org.il/pub/ubuntu bionic-updates/main amd64 Packages 500 http://mirror.isoc.org.il/pub/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.5.17-3ubuntu4 500 500 http://mirror.isoc.org.il/pub/ubuntu bionic/main amd64 Packages 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages This problem first reported at Dec 11 '18 and also exists in Kubuntu 18.04 (see https://askubuntu.com/questions/1099947/how-to-use- xcompose-to-produce-snippets). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1845332/+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 1840375] Re: groupdel doesn't support extrausers
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375
Title:
groupdel doesn't support extrausers
Status in snapd:
Triaged
Status in shadow package in Ubuntu:
Fix Released
Status in shadow source package in Xenial:
Fix Committed
Status in shadow source package in Bionic:
Fix Committed
Status in shadow source package in Disco:
Fix Committed
Bug description:
snapd needs the ability to call 'groupdel --extrausers foo' to clean
up after itself, but --extrausers is currently unsupported.
[Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
1. install the libnss-extrausers and configure it
2. run "groupadd --extrausers foo"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
* low: this adds a new (optional) option which is off by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+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 1845337] Re: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service
** Attachment added: "bad case - short log" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+attachment/5291156/+files/bad-short.log -- 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/1845337 Title: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Status in qemu source package in Disco: New Status in systemd source package in Disco: New Bug description: Since the recent few weeks systemd autopkgtest @ armhf @ disco fail [1]. The log is very (very) long and partially interwoven due to concurrent execution. Somewhere in between we see this subcase is the one failing: root-unittests Of this test (which again has many subtests) it is: test-execute And of this again it is (always): I'll attach bad and good case full and stripped logs. The diff of those comes down to just: 1. execute a find in a shell 2. shell exits 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=0/SUCCESS vs 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=1/FAILURE 4. in the bad case that triggers an assertion The find that fails is: find / -path /var/tmp -o -path /tmp -o -path /proc -o -path /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf Good and bad case are the same most recent version systemd/240-6ubuntu5.7. Maybe something is bad in the containers we have for armhf in regard to these paths? Was there any change we'd know of? If there is nothing known, could we force-badtest it to get it out of the way of ongoing migrations? [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+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 1845337] Re: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service
** Attachment added: "good case - short log" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+attachment/5291157/+files/good-short.log -- 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/1845337 Title: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Status in qemu source package in Disco: New Status in systemd source package in Disco: New Bug description: Since the recent few weeks systemd autopkgtest @ armhf @ disco fail [1]. The log is very (very) long and partially interwoven due to concurrent execution. Somewhere in between we see this subcase is the one failing: root-unittests Of this test (which again has many subtests) it is: test-execute And of this again it is (always): I'll attach bad and good case full and stripped logs. The diff of those comes down to just: 1. execute a find in a shell 2. shell exits 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=0/SUCCESS vs 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=1/FAILURE 4. in the bad case that triggers an assertion The find that fails is: find / -path /var/tmp -o -path /tmp -o -path /proc -o -path /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf Good and bad case are the same most recent version systemd/240-6ubuntu5.7. Maybe something is bad in the containers we have for armhf in regard to these paths? Was there any change we'd know of? If there is nothing known, could we force-badtest it to get it out of the way of ongoing migrations? [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+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 1845337] Re: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service
** Attachment added: "good case - full log" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+attachment/5291155/+files/good.log.gz -- 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/1845337 Title: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Status in qemu source package in Disco: New Status in systemd source package in Disco: New Bug description: Since the recent few weeks systemd autopkgtest @ armhf @ disco fail [1]. The log is very (very) long and partially interwoven due to concurrent execution. Somewhere in between we see this subcase is the one failing: root-unittests Of this test (which again has many subtests) it is: test-execute And of this again it is (always): I'll attach bad and good case full and stripped logs. The diff of those comes down to just: 1. execute a find in a shell 2. shell exits 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=0/SUCCESS vs 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=1/FAILURE 4. in the bad case that triggers an assertion The find that fails is: find / -path /var/tmp -o -path /tmp -o -path /proc -o -path /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf Good and bad case are the same most recent version systemd/240-6ubuntu5.7. Maybe something is bad in the containers we have for armhf in regard to these paths? Was there any change we'd know of? If there is nothing known, could we force-badtest it to get it out of the way of ongoing migrations? [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+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 1845337] [NEW] Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service
Public bug reported: Since the recent few weeks systemd autopkgtest @ armhf @ disco fail [1]. The log is very (very) long and partially interwoven due to concurrent execution. Somewhere in between we see this subcase is the one failing: root-unittests Of this test (which again has many subtests) it is: test-execute And of this again it is (always): I'll attach bad and good case full and stripped logs. The diff of those comes down to just: 1. execute a find in a shell 2. shell exits 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=0/SUCCESS vs 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=1/FAILURE 4. in the bad case that triggers an assertion The find that fails is: find / -path /var/tmp -o -path /tmp -o -path /proc -o -path /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf Good and bad case are the same most recent version systemd/240-6ubuntu5.7. Maybe something is bad in the containers we have for armhf in regard to these paths? Was there any change we'd know of? If there is nothing known, could we force-badtest it to get it out of the way of ongoing migrations? [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: qemu (Ubuntu Disco) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- 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/1845337 Title: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Status in qemu source package in Disco: New Status in systemd source package in Disco: New Bug description: Since the recent few weeks systemd autopkgtest @ armhf @ disco fail [1]. The log is very (very) long and partially interwoven due to concurrent execution. Somewhere in between we see this subcase is the one failing: root-unittests Of this test (which again has many subtests) it is: test-execute And of this again it is (always): I'll attach bad and good case full and stripped logs. The diff of those comes down to just: 1. execute a find in a shell 2. shell exits 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=0/SUCCESS vs 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=1/FAILURE 4. in the bad case that triggers an assertion The find that fails is: find / -path /var/tmp -o -path /tmp -o -path /proc -o -path /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf Good and bad case are the same most recent version systemd/240-6ubuntu5.7. Maybe something is bad in the containers we have for armhf in regard to these paths? Was there any change we'd know of? If there is nothing known, could we force-badtest it to get it out of the way of ongoing migrations? [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+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 1845337] Re: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service
** Attachment added: "bad case - full log" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+attachment/5291153/+files/bad.log.gz -- 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/1845337 Title: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Status in qemu source package in Disco: New Status in systemd source package in Disco: New Bug description: Since the recent few weeks systemd autopkgtest @ armhf @ disco fail [1]. The log is very (very) long and partially interwoven due to concurrent execution. Somewhere in between we see this subcase is the one failing: root-unittests Of this test (which again has many subtests) it is: test-execute And of this again it is (always): I'll attach bad and good case full and stripped logs. The diff of those comes down to just: 1. execute a find in a shell 2. shell exits 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=0/SUCCESS vs 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=1/FAILURE 4. in the bad case that triggers an assertion The find that fails is: find / -path /var/tmp -o -path /tmp -o -path /proc -o -path /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf Good and bad case are the same most recent version systemd/240-6ubuntu5.7. Maybe something is bad in the containers we have for armhf in regard to these paths? Was there any change we'd know of? If there is nothing known, could we force-badtest it to get it out of the way of ongoing migrations? [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+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 1845337] Re: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service
Also add a qemu task which is blocked by it from migrating through an SRU -- 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/1845337 Title: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service Status in qemu package in Ubuntu: New Status in systemd package in Ubuntu: New Status in qemu source package in Disco: New Status in systemd source package in Disco: New Bug description: Since the recent few weeks systemd autopkgtest @ armhf @ disco fail [1]. The log is very (very) long and partially interwoven due to concurrent execution. Somewhere in between we see this subcase is the one failing: root-unittests Of this test (which again has many subtests) it is: test-execute And of this again it is (always): I'll attach bad and good case full and stripped logs. The diff of those comes down to just: 1. execute a find in a shell 2. shell exits 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=0/SUCCESS vs 3. exec-dynamicuser-statedir.service: Main process exited, code=exited, status=1/FAILURE 4. in the bad case that triggers an assertion The find that fails is: find / -path /var/tmp -o -path /tmp -o -path /proc -o -path /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf Good and bad case are the same most recent version systemd/240-6ubuntu5.7. Maybe something is bad in the containers we have for armhf in regard to these paths? Was there any change we'd know of? If there is nothing known, could we force-badtest it to get it out of the way of ongoing migrations? [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+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 1845332] Re: Compose key does not create strings
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1845332 Title: Compose key does not create strings Status in ibus package in Ubuntu: Confirmed Bug description: According to manual https://wiki.ubuntu.com/ComposeKey it is possible to define sequences to type characters and strings with Compose key. In Ubuntu 18.04 sequences work for characters but not for strings, line like this: : "by the way" # Compose b t w seems to be ignored. $ apt-cache policy ibus ibus: Installed: 1.5.17-3ubuntu5.2 Candidate: 1.5.17-3ubuntu5.2 Version table: *** 1.5.17-3ubuntu5.2 500 500 http://mirror.isoc.org.il/pub/ubuntu bionic-updates/main amd64 Packages 500 http://mirror.isoc.org.il/pub/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.5.17-3ubuntu4 500 500 http://mirror.isoc.org.il/pub/ubuntu bionic/main amd64 Packages 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages This problem first reported at Dec 11 '18 and also exists in Kubuntu 18.04 (see https://askubuntu.com/questions/1099947/how-to-use- xcompose-to-produce-snippets). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1845332/+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 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
I can confirm this issue on 2 of our VMs running Ubuntu 18.04. Today I lost a secondary IP on one of the interfaces, after unattended upgrades installed a new systemd package. Any updates on this issue? -- 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/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces Status in systemd package in Ubuntu: Confirmed Bug description: Info: Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 2018). HP DL380 server I had this issue already twice in the past couple of months. After unattended upgrade of systemd my server's public IP address is removed from the interface. I statically configure the IP address using the interfaces file. I have opted out of the YML based network configuration. This is my apt history log: Start-Date: 2019-04-09 06:15:01 Commandline: /usr/bin/unattended-upgrade Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:07 Start-Date: 2019-04-09 06:15:12 Commandline: /usr/bin/unattended-upgrade Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:56 Start-Date: 2019-04-09 06:15:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:16:15 After that my server was unavailable from the Internet. When I logged in via out of band management and simply brought down and up the interface everything went back to normal. As said above this is the second time I had this issue. Last time it was unattended upgrades and it was systemd again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+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 1845317] Re: Add new pci-id's for CML-S, ICL
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1845317 Title: Add new pci-id's for CML-S, ICL Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in mesa source package in Bionic: New Bug description: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. There's also one ICL pci-id which was added recently (not in 5.3). [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+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 1845332] [NEW] Compose key does not create strings
Public bug reported: According to manual https://wiki.ubuntu.com/ComposeKey it is possible to define sequences to type characters and strings with Compose key. In Ubuntu 18.04 sequences work for characters but not for strings, line like this: : "by the way" # Compose b t w seems to be ignored. $ apt-cache policy ibus ibus: Installed: 1.5.17-3ubuntu5.2 Candidate: 1.5.17-3ubuntu5.2 Version table: *** 1.5.17-3ubuntu5.2 500 500 http://mirror.isoc.org.il/pub/ubuntu bionic-updates/main amd64 Packages 500 http://mirror.isoc.org.il/pub/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.5.17-3ubuntu4 500 500 http://mirror.isoc.org.il/pub/ubuntu bionic/main amd64 Packages 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages This problem first reported at Dec 11 '18 and also exists in Kubuntu 18.04 (see https://askubuntu.com/questions/1099947/how-to-use-xcompose- to-produce-snippets). ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1845332 Title: Compose key does not create strings Status in ibus package in Ubuntu: New Bug description: According to manual https://wiki.ubuntu.com/ComposeKey it is possible to define sequences to type characters and strings with Compose key. In Ubuntu 18.04 sequences work for characters but not for strings, line like this: : "by the way" # Compose b t w seems to be ignored. $ apt-cache policy ibus ibus: Installed: 1.5.17-3ubuntu5.2 Candidate: 1.5.17-3ubuntu5.2 Version table: *** 1.5.17-3ubuntu5.2 500 500 http://mirror.isoc.org.il/pub/ubuntu bionic-updates/main amd64 Packages 500 http://mirror.isoc.org.il/pub/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.5.17-3ubuntu4 500 500 http://mirror.isoc.org.il/pub/ubuntu bionic/main amd64 Packages 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages This problem first reported at Dec 11 '18 and also exists in Kubuntu 18.04 (see https://askubuntu.com/questions/1099947/how-to-use- xcompose-to-produce-snippets). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1845332/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived clusters
Alright, As this is a problem that does not only affect keepalived, but, all cluster-like softwares dealing with aliases in any existing interface, managed or not by systemd, I have tested the same test case in a pacemaker based cluster, with 3 nodes, having 1 virtual IP + a lighttpd instance running in the same resource group: (k)inaddy@kcluster01:~$ crm config show node 1: kcluster01 node 2: kcluster02 node 3: kcluster03 primitive fence_kcluster01 stonith:fence_virsh \ params ipaddr=192.168.100.205 plug=kcluster01 action=off login=stonithmgr passwd= use_sudo=true delay=2 \ op monitor interval=60s primitive fence_kcluster02 stonith:fence_virsh \ params ipaddr=192.168.100.205 plug=kcluster02 action=off login=stonithmgr passwd= use_sudo=true delay=4 \ op monitor interval=60s primitive fence_kcluster03 stonith:fence_virsh \ params ipaddr=192.168.100.205 plug=kcluster03 action=off login=stonithmgr passwd= use_sudo=true delay=6 \ op monitor interval=60s primitive virtual_ip IPaddr2 \ params ip=10.0.3.1 nic=eth3 \ op monitor interval=10s primitive webserver systemd:lighttpd \ op monitor interval=10 timeout=60 group webserver_virtual_ip webserver virtual_ip location l_fence_kcluster01 fence_kcluster01 -inf: kcluster01 location l_fence_kcluster02 fence_kcluster02 -inf: kcluster02 location l_fence_kcluster03 fence_kcluster03 -inf: kcluster03 property cib-bootstrap-options: \ have-watchdog=true \ dc-version=2.0.1-9e909a5bdd \ cluster-infrastructure=corosync \ cluster-name=debian \ stonith-enabled=true \ stonith-action=off \ no-quorum-policy=stop (k)inaddy@kcluster01:~$ cat /etc/netplan/cluster.yaml network: version: 2 renderer: networkd ethernets: eth1: dhcp4: no dhcp6: no addresses: [10.0.1.2/24] eth2: dhcp4: no dhcp6: no addresses: [10.0.2.2/24] eth3: dhcp4: no dhcp6: no addresses: [10.0.3.2/24] eth4: dhcp4: no dhcp6: no addresses: [10.0.4.2/24] eth5: dhcp4: no dhcp6: no addresses: [10.0.5.2/24] AND the virtual IP failed right after the netplan acted in systemd network interface. (k)inaddy@kcluster03:~$ sudo netplan apply (k)inaddy@kcluster03:~$ ping 10.0.3.1 PING 10.0.3.1 (10.0.3.1) 56(84) bytes of data. >From 10.0.3.4 icmp_seq=1 Destination Host Unreachable >From 10.0.3.4 icmp_seq=2 Destination Host Unreachable >From 10.0.3.4 icmp_seq=3 Destination Host Unreachable >From 10.0.3.4 icmp_seq=4 Destination Host Unreachable >From 10.0.3.4 icmp_seq=5 Destination Host Unreachable >From 10.0.3.4 icmp_seq=6 Destination Host Unreachable 64 bytes from 10.0.3.1: icmp_seq=7 ttl=64 time=0.088 ms 64 bytes from 10.0.3.1: icmp_seq=8 ttl=64 time=0.076 ms --- 10.0.3.1 ping statistics --- 8 packets transmitted, 2 received, +6 errors, 75% packet loss, time 7128ms rtt min/avg/max/mdev = 0.076/0.082/0.088/0.006 ms, pipe 4 Liked explained in this bug description. With that, virtual_ip_monitor, from pacemaker, realized the virtual IP was gone and re-started it in the same node: (k)inaddy@kcluster01:~$ crm status Stack: corosync Current DC: kcluster01 (version 2.0.1-9e909a5bdd) - partition with quorum Last updated: Wed Sep 25 13:11:05 2019 Last change: Wed Sep 25 12:49:56 2019 by root via cibadmin on kcluster01 3 nodes configured 5 resources configured Online: [ kcluster01 kcluster02 kcluster03 ] Full list of resources: fence_kcluster01 (stonith:fence_virsh): Started kcluster02 fence_kcluster02 (stonith:fence_virsh): Started kcluster01 fence_kcluster03 (stonith:fence_virsh): Started kcluster01 Resource Group: webserver_virtual_ip webserver (systemd:lighttpd): Started kcluster03 virtual_ip (ocf::heartbeat:IPaddr2): FAILED kcluster03 Failed Resource Actions: * virtual_ip_monitor_1 on kcluster03 'not running' (7): call=100, status=complete, exitreason='', last-rc-change='Wed Sep 25 13:11:05 2019', queued=0ms, exec=0ms (k)inaddy@kcluster01:~$ crm status Stack: corosync Current DC: kcluster01 (version 2.0.1-9e909a5bdd) - partition with quorum Last updated: Wed Sep 25 13:11:07 2019 Last change: Wed Sep 25 12:49:56 2019 by root via cibadmin on kcluster01 3 nodes configured 5 resources configured Online: [ kcluster01 kcluster02 kcluster03 ] Full list of resources: fence_kcluster01 (stonith:fence_virsh): Started kcluster02 fence_kcluster02 (stonith:fence_virsh): Started kcluster01 fence_kcluster03 (stonith:fence_virsh): Started kcluster01 Resource Group: webserver_virtual_ip webserver (systemd:lighttpd): Started kcluster03 virtual_ip (ocf::heartbeat:IPaddr2): Started kcluster03 Failed Resource Actions: * virtual_ip_monitor_1
[Touch-packages] [Bug 1844119]
The binutils-2_33-branch branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;h=a11b3493ca2d5aabdc218197b92026098d7e2f57 commit a11b3493ca2d5aabdc218197b92026098d7e2f57 Author: Alan Modra Date: Mon Sep 23 08:53:07 2019 +0930 PR25018, readelf crash on 32bits Pointer comparisons after adding an offset just don't work to catch overflow when the offset is a larger type than the pointer. PR 25018 * dwarf.c (get_type_signedness): Delete ineffective pointer comparison check. Properly range check uvalue offset on recursive call. (read_and_display_attr_value): Range check uvalue offset before calling get_type_signedness. (cherry picked from commit b3fe587ed2c78d46132bd33e14f42449d410354b) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1844119 Title: readelf crash on 32bit, leading to abi-monitor testsuite regression Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Invalid Bug description: readelf --debug-dump=info libjsoncpp.so.1.8.1 to reproduce dpkg -l |grep binut ii binutils2.32.51.20190905-0ubuntu1 i386 GNU assembler, linker and binary utilities ii binutils-common:i3862.32.51.20190905-0ubuntu1 i386 Common files for the GNU assembler, linker and binary utilities ii binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1 i386 GNU binary utilities, for i686-linux-gnu target ii libbinutils:i3862.32.51.20190905-0ubuntu1 i386 GNU binary utilities (private shared library) To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1844119/+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 1799265] Re: avahi-daemon high cpu, unusable networking
Also, startlingly, I seem to have thousands of ipv6 addresses assigned to enp0s8: ip addr 3: enp0s8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 08:00:27:47:xx:xx brd ff:ff:ff:ff:ff:ff inet 10.169.110.168/21 brd 10.169.111.255 scope global dynamic noprefixroute enp0s8 valid_lft 6027sec preferred_lft 6027sec inet6 2606:b400:818:61:c70:::/64 scope global temporary dynamic valid_lft 604796sec preferred_lft 86280sec inet6 2606:b400:818:61:eece:::/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 2591939sec preferred_lft 604739sec inet6 2606:b400:818:64:c70:::/64 scope global temporary dynamic valid_lft 604796sec preferred_lft 86280sec inet6 2606:b400:818:64:6745:::/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 2591996sec preferred_lft 604796sec inet6 2606:b400:818:64:d7:::0/64 scope global temporary dynamic valid_lft 604740sec preferred_lft 86224sec # ip addr | grep inet6 | cat -n 6294 inet6 2606:b400:818:64::::/64 scope global temporary deprecated dynamic 6295 inet6 2606:b400:818:61::::/64 scope global temporary deprecated dynamic 6296 inet6 2606:b400:818:61::::/64 scope global temporary deprecated dynamic 6297 inet6 2606:b400:818:64::::/64 scope global temporary deprecated dynamic 6298 inet6 2606:b400:818:64::::/64 scope global temporary deprecated dynamic 6299 inet6 2606:b400:818:61::::c/64 scope global temporary deprecated dynamic 6300 inet6 2606:b400:818:61::::/64 scope global temporary deprecated dynamic 6301 inet6 2606:b400:818:64::::/64 scope global temporary deprecated dynamic 6302 inet6 2606:b400:818:64::::/64 scope global temporary deprecated dynamic 6303 inet6 2606:b400:818:61::::/64 scope global temporary deprecated dynamic 6304 inet6 fe80::4721:::/64 scope link noprefixroute -- 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/1799265 Title: avahi-daemon high cpu, unusable networking Status in Avahi: New Status in avahi package in Ubuntu: Triaged Bug description: Currently running Kubuntu 18.10, Dell XPS 13 9350 Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been consistently hampering network performance and using CPU for long periods of time. When booting machine from off state, avahi-daemon uses an entire CPU at max load for approx 10 minutes. During this time, internet connectivity via wifi is essentially unusable. The wifi connection is good, but it seems that http transactions are cutoff mid-way so no webpage is able to load. When waking from sleep, the avahi-daemon causes similar symptoms, but with less than 1 full cpu usage, and with somewhat less degraded network performance, but still quite unusable. I have never had issues with avahi prior to the 18.10 upgrade, so I am fairly confident the issue is rooted in that change. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: avahi-daemon 0.7-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 22 10:00:34 2018 InstallationDate: Installed on 2017-07-24 (455 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LD_PRELOAD= SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/1799265/+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 1845245] Re: Behaviour change in systemd 243 breaks netplan.io ethernets autopkgtest
** Tags added: id-5d6fba2cac409d12ddb60a25 -- 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/1845245 Title: Behaviour change in systemd 243 breaks netplan.io ethernets autopkgtest Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The commit introducing the regression is this one: commit bd08ce56156751d58584a44e766ef61340cdae2d Author: Yu Watanabe Date: Mon Apr 15 17:34:00 2019 +0900 network: prevent interfaces to be initialized multiple times When a uevent is received during the relevant interface is in LINK_STATE_PENDING, then the interface may be initialized twice. To prevent that, this introduces LINK_STATE_INITIALIZED. I'll triage further and possibly revert the change in the next 243-based upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1845245/+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 1845314] Re: udisks2 fails to install in a container with systemd 243
** Tags added: id-5d6fba2cac409d12ddb60a25 -- 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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: Confirmed Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+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 1799265] Re: avahi-daemon high cpu, unusable networking
Hi, I'm hitting this quite consistently on Pop!_OS 19.04 in Virtualbox
(Windows 10 host) on Lenovo T460.
Essentially, the CPU usage goes up to 100% for avahi-daemon, and the
strace shows it stuck in a loop, reading/writing to a named pipe, like
so:
poll([{fd=6, events=POLLIN}, {fd=14, events=POLLIN}, {fd=13, events=POLLIN},
{fd=12, events=POLLIN}, {fd=11, events=POLLIN}, {fd=10, events=POLLIN}, {fd=3,
events=POLLIN}, {fd=8, events=POLLIN}], 8, 0) = 3 ([{fd=14,
revents=POLLIN|POLLERR}, {fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
write(7, "W", 1)= 1
write(7, "W", 1)= 1
read(6, "WW", 10) = 2
poll([{fd=6, events=POLLIN}, {fd=14, events=POLLIN}, {fd=13, events=POLLIN},
{fd=12, events=POLLIN}, {fd=11, events=POLLIN}, {fd=10, events=POLLIN}, {fd=3,
events=POLLIN}, {fd=8, events=POLLIN}], 8, 0) = 3 ([{fd=14,
revents=POLLIN|POLLERR}, {fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
write(7, "W", 1)= 1
write(7, "W", 1)= 1
write(7, "W", 1)= 1
write(7, "W", 1)= 1
read(6, "", 10) = 4
poll([{fd=6, events=POLLIN}, {fd=14, events=POLLIN}, {fd=13, events=POLLIN},
{fd=12, events=POLLIN}, {fd=11, events=POLLIN}, {fd=10, events=POLLIN}, {fd=3,
events=POLLIN}, {fd=8, events=POLLIN}], 8, 0) = 3 ([{fd=14,
revents=POLLIN|POLLERR}, {fd=12, revents=POLLIN}, {fd=10, revents=POLLIN}])
^Cstrace: Process 782 detached
root@pop-os:/# ls -ltr /proc/782/fd
total 0
lrwx-- 1 root root 64 Sep 25 13:03 14 -> 'socket:[20288]'
lrwx-- 1 root root 64 Sep 25 13:03 13 -> 'socket:[20287]'
lrwx-- 1 root root 64 Sep 25 13:03 12 -> 'socket:[20286]'
lr-x-- 1 root root 64 Sep 25 13:03 11 -> anon_inode:inotify
lrwx-- 1 root root 64 Sep 25 13:03 10 -> 'socket:[20154]'
l-wx-- 1 root root 64 Sep 25 13:03 9 -> 'pipe:[20153]'
lr-x-- 1 root root 64 Sep 25 13:03 8 -> 'pipe:[20153]'
l-wx-- 1 root root 64 Sep 25 13:03 7 -> 'pipe:[20152]'
lr-x-- 1 root root 64 Sep 25 13:03 6 -> 'pipe:[20152]'
lrwx-- 1 root root 64 Sep 25 13:03 5 -> 'socket:[20141]'
lrwx-- 1 root root 64 Sep 25 13:03 4 -> 'socket:[19687]'
lrwx-- 1 root root 64 Sep 25 13:03 3 -> 'socket:[17872]'
lrwx-- 1 root root 64 Sep 25 13:03 2 -> 'socket:[19192]'
lrwx-- 1 root root 64 Sep 25 13:03 1 -> 'socket:[19192]'
lr-x-- 1 root root 64 Sep 25 13:03 0 -> /dev/null
root@pop-os:/#
My avahi config is:
## /etc/avah/avahi-daemon.conf
[server]
use-ipv4=yes
use-ipv6=no
ratelimit-interval-usec=100
ratelimit-burst=1000
[wide-area]
enable-wide-area=yes
[publish]
publish-hinfo=no
publish-workstation=no
[reflector]
[rlimits]
The journal log is overgrown with messages like so: (I've replaced parts of the
ipv6 addresses with )
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:64:485e::: on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:64:28d5::: on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:61:28d5::: on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:64:fca2::: on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:61:fca2::: on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:64:90ab::: on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:61:90ab::: on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:61:5855:::9 on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:64:5855::: on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:64:94aa::: on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:61:94aa::: on enp0s8.*.
Sep 25 10:34:11 pop-os avahi-daemon[782]: Registering new address record for
2606:b400:818:64:e973::: on enp0s8.*.
I've managed to gather the 'perf' data, that was requested by lathiat.
Let me know if this info is of use.
--
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/1799265
Title:
avahi-daemon high cpu, unusable networking
Status in Avahi:
New
Status in avahi package in Ubuntu:
Triaged
Bug description:
Currently running Kubuntu 18.10, Dell XPS 13 9350
Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
[Touch-packages] [Bug 1832050] Re: chrony autopkgtest "time-sources-from-dhcp-servers" fails (produces stderr)
** Tags added: id-5d8a536c3eb49122f14145aa
--
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/1832050
Title:
chrony autopkgtest "time-sources-from-dhcp-servers" fails (produces
stderr)
Status in systemd package in Ubuntu:
Confirmed
Status in systemd source package in Eoan:
Confirmed
Bug description:
iproute2 fix in -proposed
(https://launchpad.net/ubuntu/+source/iproute2/4.18.0-1ubuntu3) has
showed regressions in chrony autopkgtest (object of this bug report).
From autopkgtest output:
"""
Generating /etc/default/isc-dhcp-server...
Created symlink
/etc/systemd/system/multi-user.target.wants/isc-dhcp-server.service →
/lib/systemd/system/isc-dhcp-server.service.
Created symlink
/etc/systemd/system/multi-user.target.wants/isc-dhcp-server6.service →
/lib/systemd/system/isc-dhcp-server6.service.
Setting up autopkgtest-satdep (0) ...
Processing triggers for systemd (240-6ubuntu9) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.29-0ubuntu2) ...
(Reading database ... 62774 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [20:50:33]: test time-sources-from-dhcp-servers:
[---
Preparing the dummy network interface and dhcpd configuration…
md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-dummy0.conf: No such file or
directory
md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-dummy0.conf: No such file or
directory
md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-dummy0.conf: No such file or
directory
md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-dummy0.conf: No such file or
directory
Done!
Check if the NTP server is made available to chronyd…
SUCCESS!
Release the current lease and check if the NTP server has been correctly
removed…
SUCCESS!
"""
It is likely that the stdout from md5sum coming out of the dhclient
command caused the "regression".
I have reproduced the issue by hand doing:
$ apt-get install isc-dhcp-server
$ modprobe dummy
$ ip link add name dummy0 type dummy
$ ip address add 192.168.1.1/24 dev dummy0
$ ip link set dev dummy0 up
cat < /etc/dhcp/dhcpd.conf
default-lease-time 600;
max-lease-time 7200;
authorative;
subnet 192.168.1.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
option broadcast-address192.168.1.255;
option ntp-servers 192.168.1.50;
range 192.168.1.42 192.168.1.100;
}
EOF
$ sed -i 's/INTERFACESv4=""/INTERFACESv4="dummy0"/' /etc/default/isc-
dhcp-server
and
$ systemctl restart isc-dhcp-server
$ dhclient dummy0 <- problem happens here
It could be a "isc-dhcp-client"problem, but I'll keep this bug linked
to another bug if that is the case.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1832050/+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 1845314] Re: udisks2 fails to install in a container with systemd 243
Hey BTW, I suspect this 'error' is due to upstream commit 97afc0351a96e0daa83964df33937967c75c644f which changed udevadm's behavior; previously it silently ignored errors writing to /sys/devices/*/uevent files, but now it logs error and returns error code. So this is likely not *actually* a new failure, it's just now being reported as failure by udevadm. There is a similar 'failure' in bug 1845319 where (only on ppc64el) it gets ENODEV when writing to /sys/devices/vio/uevent, but I checked older releases and the vio device has been returning ENODEV for a long time; udevadm was just ignoring that before now. -- 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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: Confirmed Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+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 1845314] Re: udisks2 fails to install in a container with systemd 243
Oh, and a better fix would be not calling udevadm when 'systemd-detect- virt --private-users' is true. It's a bit annoying that every udevadm caller would need to know that, however. -- 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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: Confirmed Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+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 1845314] Re: udisks2 fails to install in a container with systemd 243
And yeah, ignoring the udevadm return value with ||: could be one way to avoid the error. -- 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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: Confirmed Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+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 1845317] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1845317 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1845317 Title: Add new pci-id's for CML-S, ICL Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in mesa source package in Bionic: New Bug description: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. There's also one ICL pci-id which was added recently (not in 5.3). [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+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 1845314] Re: udisks2 fails to install in a container with systemd 243
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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: Confirmed Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+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 1845314] Re: udisks2 fails to install in a container with systemd 243
3. How we could fix it? Well, given the data I posted above, my *guess* is that we could safely ignore the udevadm non-zero exit status in the udisks2 postinst script with something like this: if [ "$1" = "configure" ]; then # we ship udev rules, so trigger an update udevadm trigger --subsystem-match=block --action=change || true fi Note the final "|| true". In case the conjecture I just made above is correct, I prepared a modified udisks2 package in a PPA which doesn't fail to install: https://launchpad.net/~panfaust/+archive/ubuntu/udisks2 If the conjecture I made and/or proposed fix are wrong, I hope at least the data I provided leads to the correct solution. Regards. -- 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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: Confirmed Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+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 1845314] Re: udisks2 fails to install in a container with systemd 243
2. Why this is happening? First of all, the udisks2 installation fails because the postinst script fails. Inspecting the postinst script of udisks2, we can see these lines: if [ "$1" = "configure" ]; then # we ship udev rules, so trigger an update udevadm trigger --subsystem-match=block --action=change fi That udevadm command fails, i.e. ends with non-zero status with systemd >= 243. This new different behaviour of udevadm makes the postinst script fail, and that makes the package installation fail. While I didn't git bisect the thing, reading the systemd git history makes me believe that the specific commit which produced this new behaviour could be this one: https://github.com/systemd/systemd/commit/0584b17a8c7d17649aef9f06a8aee304dc80eb7e -- 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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: New Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+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 1845317] Re: Add new pci-id's for CML-S, ICL
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1845317 Title: Add new pci-id's for CML-S, ICL Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in mesa source package in Bionic: New Bug description: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. There's also one ICL pci-id which was added recently (not in 5.3). [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+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 1845314] Re: udisks2 fails to install in a container with systemd 243
Hi, I'm the santa_ above, so, to explain the full picture I'm going to write 3 separate messages below trying to answer these 3 questions: 1. How to reproduce the issue? 2. Why this is happening? 3. How we could fix it? -- 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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: New Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+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 1845317] Re: Add new pci-id's for CML-S, ICL
** Summary changed: - Add new pci-id's for CML-S + Add new pci-id's for CML-S, ICL ** Description changed: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. + + There's also one ICL pci-id which was added recently (not in 5.3). [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1845317 Title: Add new pci-id's for CML-S, ICL Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in mesa source package in Bionic: New Bug description: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. There's also one ICL pci-id which was added recently (not in 5.3). [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+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 1845314] Re: udisks2 fails to install in a container with systemd 243
1. How to reproduce the issue? Very easy, you just have to create an eoan LXD container, add the ppa with systemd 243: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3801/+packages and then just do "apt dist-upgrade" to upgrate to systemd 243 and "apt install udisks2", the udisks2 installation will fail like this (obviously the devices in question could be different in your case, but the error will be similar): Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb1/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb3/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4/uevent': Permission denied Failed to write 'change' to '/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb5/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop0/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop1/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop2/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop3/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop4/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop5/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop6/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/loop7/uevent': Permission denied Failed to write 'change' to '/sys/devices/virtual/block/dm-0/uevent': Permission denied dpkg: error processing package udisks2 (--configure): installed udisks2 package post-installation script subprocess returned error exit status 1 Setting up libblockdev-crypto2:amd64 (2.22-1) ... Processing triggers for man-db (2.8.7-3) ... Processing triggers for dbus (1.12.14-1ubuntu2) ... Processing triggers for libc-bin (2.30-0ubuntu2) ... Errors were encountered while processing: udisks2 E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: New Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+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 1845317] [NEW] Add new pci-id's for CML-S
Public bug reported: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: libdrm (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1845317 Title: Add new pci-id's for CML-S Status in libdrm package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in mesa source package in Bionic: New Bug description: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+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 1844879] Re: Behaviour change in systemd 243 breaks libvirt autopkgtest
FYI: We have identified a behavioral change in libvirt, but while I'll address that it was not the reason for the issue reported here. Upstream discussion on the systemd issue continues ... ** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => Christian Ehrhardt (paelzer) -- 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/1844879 Title: Behaviour change in systemd 243 breaks libvirt autopkgtest Status in systemd: New Status in libvirt package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: With systemd 243 libvirt autopkgtest starts failing: http://autopkgtest.ubuntu.com/packages/libv/libvirt/eoan/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/libv/libvirt/20190921_104518_69667@/log.gz ... + virt-xml-validate debian/tests/smoke-lxc.xml debian/tests/smoke-lxc.xml validates + virsh define debian/tests/smoke-lxc.xml Domain sl defined from debian/tests/smoke-lxc.xml + rm -f /var/log/libvirt/lxc/sl.log + virsh start sl Domain sl started + grep -qs starting up /var/log/libvirt/lxc/sl.log + check_domain + grep/bin/ls Domain sl has been undefined -qs sl[[:space:]]\+running + virsh list + virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls + systemctl restart libvirtd + check_domain + grep -qs sl[[:space:]]\+running + virsh list + cleanup + [ -z ] + virsh destroy sl error: Failed to destroy domain sl error: Requested operation is not valid: domain is not running + true + virsh undefine sl + CLEANED_UP=1 autopkgtest [10:41:05]: test smoke-lxc: ---] autopkgtest [10:41:07]: test smoke-lxc: - - - - - - - - - - results - - - - - - - - - - smoke-lxcFAIL non-zero exit status 1 ... The behaviour change is still present in systemd master (v243-112-g984b96aa7a) I can revert the change in systemd, but it also fixes an issue reported at upstream. I will take another look later, but wanted to document my findings. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1844879/+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 1845314] [NEW] udisks2 fails to install in a container with systemd 243
Public bug reported: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1845314 Title: udisks2 fails to install in a container with systemd 243 Status in systemd package in Ubuntu: New Bug description: santa_ | rbalint: hey while systemd 243 was available in eoan I still got one of "my" issues (udisks2 fails to install in a container) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845314/+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 1840995] Re: check_stamp() function of apt.systemd.daily should not assume interval is a number
** Description changed:
+ [Impact]
+ Warning messages when using suffixes in intervals such as d for day
+
+ /usr/lib/apt/apt.systemd.daily: 87: [: Illegal number: 20h
+
+ [Test case]
+ Create 99local in apt.conf.d with
+ APT::Periodic::Update-Package-Lists "1d";
+ and run /usr/lib/apt/apt.systemd.daily - make sure no warning appears.
+
+ [Regression potential]
+ The fix replaces -eq 0 checks with = 0 checks which might have different
behavior in case -eq also accepts some values as equal to 0 that are not
literally 0 and that now no longer match. But then you'd have to do stuff like
set the interval to "+0", and it seems unrealistic people do that.
+
+ [Original bug report]
In the second half of the function there is
- # Calculate the interval in seconds depending on the unit specified
- if [ "${interval%s}" != "$interval" ] ; then
- interval="${interval%s}"
- elif [ "${interval%m}" != "$interval" ] ; then
- interval="${interval%m}"
- interval=$((interval*60))
- elif [ "${interval%h}" != "$interval" ] ; then
- interval="${interval%h}"
- interval=$((interval*60*60))
- else
- interval="${interval%d}"
- interval=$((interval*60*60*24))
- fi
+ # Calculate the interval in seconds depending on the unit specified
+ if [ "${interval%s}" != "$interval" ] ; then
+ interval="${interval%s}"
+ elif [ "${interval%m}" != "$interval" ] ; then
+ interval="${interval%m}"
+ interval=$((interval*60))
+ elif [ "${interval%h}" != "$interval" ] ; then
+ interval="${interval%h}"
+ interval=$((interval*60*60))
+ else
+ interval="${interval%d}"
+ interval=$((interval*60*60*24))
+ fi
so, a variable might hold something like "1d", "100m", etc.
Yet in the first there is a condition
- if [ "$interval" -eq 0 ]; then
- debug_echo "check_stamp: interval=0"
- # treat as no time has passed
- return 1
- fi
+ if [ "$interval" -eq 0 ]; then
+ debug_echo "check_stamp: interval=0"
+ # treat as no time has passed
+ return 1
+ fi
which treats the value as a number and leads to
/usr/lib/apt/apt.systemd.daily: 87: [: Illegal number: 20h
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1840995
Title:
check_stamp() function of apt.systemd.daily should not assume interval
is a number
Status in apt package in Ubuntu:
Fix Released
Bug description:
[Impact]
Warning messages when using suffixes in intervals such as d for day
/usr/lib/apt/apt.systemd.daily: 87: [: Illegal number: 20h
[Test case]
Create 99local in apt.conf.d with
APT::Periodic::Update-Package-Lists "1d";
and run /usr/lib/apt/apt.systemd.daily - make sure no warning appears.
[Regression potential]
The fix replaces -eq 0 checks with = 0 checks which might have different
behavior in case -eq also accepts some values as equal to 0 that are not
literally 0 and that now no longer match. But then you'd have to do stuff like
set the interval to "+0", and it seems unrealistic people do that.
[Original bug report]
In the second half of the function there is
# Calculate the interval in seconds depending on the unit specified
if [ "${interval%s}" != "$interval" ] ; then
interval="${interval%s}"
elif [ "${interval%m}" != "$interval" ] ; then
interval="${interval%m}"
interval=$((interval*60))
elif [ "${interval%h}" != "$interval" ] ; then
interval="${interval%h}"
interval=$((interval*60*60))
else
interval="${interval%d}"
interval=$((interval*60*60*24))
fi
so, a variable might hold something like "1d", "100m", etc.
Yet in the first there is a condition
if [ "$interval" -eq 0 ]; then
debug_echo "check_stamp: interval=0"
# treat as no time has passed
return 1
fi
which treats the value as a number and leads to
/usr/lib/apt/apt.systemd.daily: 87: [: Illegal number: 20h
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1840995/+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 1845201] Re: systemd root-unittests autopkgtest is failing on armhf
Well, it is failing with 241, too, so it is not a regression. Will triage it later. -- 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/1845201 Title: systemd root-unittests autopkgtest is failing on armhf Status in systemd package in Ubuntu: New Bug description: This is a regression with 242, to be fixed soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845201/+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 1845201] Re: systemd root-unittests autopkgtest is failing on armhf
Failing with 241-7ubuntu1. -- 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/1845201 Title: systemd root-unittests autopkgtest is failing on armhf Status in systemd package in Ubuntu: New Bug description: This is a regression with 242, to be fixed soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1845201/+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 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
This still looks like an issue in Ubuntu 18.04 LTS. At least on systems that was upgraded from 14.04 release. I will disable systemd-resolved and revert to good old resolv.conf but what is the actual recommended workaround while the fix is not released? -- 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/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Confirmed Status in systemd source package in Disco: Confirmed Bug description: [Impact] Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state? Application that require Name Resolution may fail while the service is being unnecessarily restarted [Test case] (1) Append make_resolv_conf to the end of the file, so it gets executed (2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example: sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart [Regression potential] The change only restarts resolved when the settings change. If there's a bug in the logic, resolved might not be restarted when it should be. Also, since there will be less restarts of resolved, it will run longer, so if there are memory leaks they will become more apparent. [Original bug report] If a cloud server is upgraded from Xenial to Bionic, the dhclient system remains in place and any DHCP lease refreshes cause a needless restart of the system-resolved daemon Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d) Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 10.226.209.105 Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors: Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 'srv-qvjhx'. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting resolvconf-pull-resolved.service... Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal in 1466 seconds. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started resolvconf-pull-resolved.service. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.25 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu Date: Mon Nov 26 16:17:52 2018 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+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 1845190]
thanks a ton for the quick fixes! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1845190 Title: binutils nm wrong output format breaks i386 nm work Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Bug description: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1845190/+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 1822118] Re: Kernel Panic while rebooting cloud instance
See above, I ran several thousand reboot tests on a lot of Basic_A3 instances, ranging from 50, 250 to 500 reboots. Only one failed. So this is *really* hard to reproduce. -- 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/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+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 1822118] Re: Kernel Panic while rebooting cloud instance
IP addr Mac AddrKernel Reboots 13.64.67.18600:0d:3a:3a:dd:04 5.0.0-1016-azure50 104.42.152.115 00:0d:3a:35:b1:e6 5.0.0-1016-azure50 65.52.121.205 00:0d:3a:3b:0f:52 5.0.0-1016-azure50 13.88.28.42 00:0d:3a:3b:c7:da 5.0.0-1016-azure50 40.118.165.237 00:0d:3a:3b:c2:4e 5.0.0-1016-azure50 40.118.190.105 00:0d:3a:36:c6:d7 5.0.0-1016-azure50 40.78.90.95 00:0d:3a:37:c0:d9 5.0.0-1016-azure50 13.83.84.15000:0d:3a:37:c0:15 5.0.0-1016-azure50 104.42.74.129 00:0d:3a:36:c2:3e 5.0.0-1016-azure50 40.85.154.162 00:0d:3a:37:cc:dd 5.0.0-1016-azure50 40.78.43.4 00:0d:3a:37:c5:07 5.0.0-1016-azure50 13.93.142.147 00:0d:3a:37:c8:5f 5.0.0-1016-azure50 40.78.44.22900:0d:3a:3b:e4:80 5.0.0-1016-azure50 40.118.189.62 00:0d:3a:3b:e8:8e 5.0.0-1016-azure50 40.78.85.10 00:0d:3a:3b:e6:37 5.0.0-1016-azure50 40.78.13.20300:0d:3a:3a:c2:b0 5.0.0-1016-azure50 104.42.112.81 00:0d:3a:30:71:fb 5.0.0-1016-azure50 40.80.156.132 00:0d:3a:30:2f:7c 5.0.0-1016-azure50 13.64.173.138 00:0d:3a:30:73:b2 5.0.0-1016-azure50 13.64.189.105 00:0d:3a:30:a4:6f 5.0.0-1016-azure50 13.64.189.127 00:0d:3a:30:a4:1f 5.0.0-1016-azure50 104.45.237.232 00:0d:3a:32:1e:3b 5.0.0-1016-azure50 104.42.233.11 00:0d:3a:32:34:68 5.0.0-1016-azure50 104.42.233.20 00:0d:3a:34:ed:42 5.0.0-1016-azure50 23.101.202.206 00:0d:3a:32:32:b0 5.0.0-1016-azure50 104.42.233.18 00:0d:3a:34:ee:ba 5.0.0-1016-azure50 104.42.233.151 00:0d:3a:34:e9:0d 5.0.0-1016-azure50 104.40.51.248 00:0d:3a:32:27:c6 5.0.0-1016-azure50 104.40.69.158 00:0d:3a:34:f1:5d 5.0.0-1016-azure50 52.160.41.9500:0d:3a:35:9f:c8 5.0.0-1016-azure50 104.42.158.74 00:0d:3a:34:c7:91 5.0.0-1016-azure50 IP addr Mac AddrKernel Reboots 40.83.145.235 00:0d:3a:5a:01:f9 5.0.0-1016-azure250 104.210.50.91 00:0d:3a:35:b2:48 5.0.0-1016-azure250 13.88.186.166 00:0d:3a:5a:0b:86 5.0.0-1016-azure250 40.118.185.194 00:0d:3a:35:b9:59 5.0.0-1016-azure250 104.42.37.175 00:0d:3a:5a:06:ff 5.0.0-1016-azure250 13.88.186.188 00:0d:3a:5a:05:da 5.0.0-1016-azure250 104.210.48.49 00:0d:3a:35:b8:a7 5.0.0-1016-azure250 104.210.50.215 00:0d:3a:35:ba:13 5.0.0-1016-azure250 40.78.52.50 00:0d:3a:35:b6:50 5.0.0-1016-azure250 40.118.186.25 00:0d:3a:35:b5:93 5.0.0-1016-azure250 13.93.233.2600:0d:3a:37:06:7e 5.0.0-1016-azure156 crashed 13.93.136.144 00:0d:3a:37:0e:2f 5.0.0-1016-azure250 40.118.241.192 00:0d:3a:32:c4:5d 5.0.0-1016-azure250 40.83.160.5200:0d:3a:37:47:48 5.0.0-1016-azure250 104.42.9.61 00:0d:3a:36:d3:a0 5.0.0-1016-azure250 IP addr Mac AddrKernel Reboots 104.40.1.50 00:0d:3a:30:8d:ae 5.0.0-1016-azure500 104.40.3.20500:0d:3a:30:81:d5 5.0.0-1016-azure500 104.40.9.37 00:0d:3a:30:86:bb 5.0.0-1016-azure500 104.40.0.24200:0d:3a:30:88:6b 5.0.0-1016-azure500 104.40.12.184 00:0d:3a:30:8e:e0 5.0.0-1016-azure500 137.135.46.72 00:0d:3a:30:ac:df 5.0.0-1016-azure500 137.135.47.169 00:0d:3a:30:9a:3f 5.0.0-1016-azure500 104.40.10.226 00:0d:3a:30:2d:fb 5.0.0-1016-azure500 104.40.10.244 00:0d:3a:30:8e:12 5.0.0-1016-azure500 104.40.15.160 00:0d:3a:30:87:4d 5.0.0-1016-azure500 40.112.132.200:0d:3a:59:b5:80 5.0.0-1016-azure500 13.64.97.59 00:0d:3a:59:b1:e7 5.0.0-1016-azure500 40.78.19.22400:0d:3a:5a:bd:99 5.0.0-1016-azure500 13.64.88.51 00:0d:3a:37:30:07 5.0.0-1016-azure500 40.118.225.110 00:0d:3a:59:b1:8f 5.0.0-1016-azure500 -- 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/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: Incomplete Status in systemd package in Ubuntu:
[Touch-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
On 2019-09-25 03:13, Bug Watch Updater wrote: > ** Changed in: ibus > Status: New => Fix Released There is no upstream fix yet. The upstream issue was closed by mistake. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: Fix Released Status in ibus package in Ubuntu: Fix Released Status in ibus package in Debian: Unknown Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+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 1845294] Re: package libpython2.7-stdlib:i386 2.7.12-1ubuntu0~16.04.8 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato insta
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1845294 Title: package libpython2.7-stdlib:i386 2.7.12-1ubuntu0~16.04.8 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. Status in python2.7 package in Ubuntu: New Bug description: once I've switched on the PC there was a notice: segnalazione crash. Si è verificato un problema durante l'installazione del software. Pacchetto: libpython2.7-stdlib:i386 2.7.12-1ubuntu0-16.04.8 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpython2.7-stdlib:i386 2.7.12-1ubuntu0~16.04.8 ProcVersionSignature: Ubuntu 4.4.0-165.193-generic 4.4.189 Uname: Linux 4.4.0-165-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: i386 Date: Thu Sep 19 17:36:53 2019 ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. InstallationDate: Installed on 2014-07-26 (1886 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: python2.7 Title: package libpython2.7-stdlib:i386 2.7.12-1ubuntu0~16.04.8 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1845294/+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 1845294] [NEW] package libpython2.7-stdlib:i386 2.7.12-1ubuntu0~16.04.8 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato ins
Public bug reported: once I've switched on the PC there was a notice: segnalazione crash. Si è verificato un problema durante l'installazione del software. Pacchetto: libpython2.7-stdlib:i386 2.7.12-1ubuntu0-16.04.8 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpython2.7-stdlib:i386 2.7.12-1ubuntu0~16.04.8 ProcVersionSignature: Ubuntu 4.4.0-165.193-generic 4.4.189 Uname: Linux 4.4.0-165-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: i386 Date: Thu Sep 19 17:36:53 2019 ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. InstallationDate: Installed on 2014-07-26 (1886 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: python2.7 Title: package libpython2.7-stdlib:i386 2.7.12-1ubuntu0~16.04.8 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1845294 Title: package libpython2.7-stdlib:i386 2.7.12-1ubuntu0~16.04.8 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. Status in python2.7 package in Ubuntu: New Bug description: once I've switched on the PC there was a notice: segnalazione crash. Si è verificato un problema durante l'installazione del software. Pacchetto: libpython2.7-stdlib:i386 2.7.12-1ubuntu0-16.04.8 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpython2.7-stdlib:i386 2.7.12-1ubuntu0~16.04.8 ProcVersionSignature: Ubuntu 4.4.0-165.193-generic 4.4.189 Uname: Linux 4.4.0-165-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: i386 Date: Thu Sep 19 17:36:53 2019 ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. InstallationDate: Installed on 2014-07-26 (1886 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: python2.7 Title: package libpython2.7-stdlib:i386 2.7.12-1ubuntu0~16.04.8 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1845294/+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 1843768] Re: [FFe] Ubiquity with zfs install option
** Summary changed: - [FFe] Ubiquity with zsys install option + [FFe] Ubiquity with zfs install option ** Description changed: Part of the 19.10 feature announcement is zfs experimental support in the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on- ubuntu-19-10-an-introduction). We modified ubiquity to present an “EXPERIMENTAL” (with warning) ZSYS install option. This option is only visible is zfsutils-linux is installed on the system. So, it won't be available for derivatives that use ubiquity but do not seed zfsutils- linux. + + Update as of 20/09/2019: the plan is to not seed zsys (security review + will take a while), but to only seed zfsutils-linux. People can then + opt-in to zsys which should be available by default next cycle. This option takes an entire disk and have a fix set of dataset installed. There is no support but we need this to make an official install option for the next LTS. The patch has been created to be as minimal as possible. Partman does a full disk partitioning, and then the script zsys-setup the first non-ESP partition and replaces with zfs pools. 4 partitions are created: 1. if GPT partitioning: ESP partition. This one is done by partman directly. 2. bpool (for boot), pool with older zfs compatible version to be readable by grub) 3. rpool (for / and userdataset) 4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on moved to the ESP) Additionaly if a swap file has been created by ubiquity, it is recreated as a ZFS volume. If the script fails to execute, the final installation is an ext4 installation on entire disk. - The script is doing the post-install of zsys (currently in universe, but - a MIR is opened: - https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1839271 and it’s - pending security review). - Note that the implementation is slightly different from the specification due to a difficult cohabitation with partman in the custom partitioning page. - - Consequently, in case the MIR doesn’t make the release, we still have an - “easy way” (once this code merged) for people to try zsys in the release - (apt install zfslinux-utils in live session and then start ubiquity). We - don’t install universe components by default unless requested/prompted - by this option (which is thus hidden by default until the MIR is acked). Please find attached the MP on ubiquity as well as the package build log. https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan- amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1843768 Title: [FFe] Ubiquity with zfs install option Status in ubiquity package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Part of the 19.10 feature announcement is zfs experimental support in the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on- ubuntu-19-10-an-introduction). We modified ubiquity to present an “EXPERIMENTAL” (with warning) ZSYS install option. This option is only visible is zfsutils-linux is installed on the system. So, it won't be available for derivatives that use ubiquity but do not seed zfsutils- linux. Update as of 20/09/2019: the plan is to not seed zsys (security review will take a while), but to only seed zfsutils-linux. People can then opt-in to zsys which should be available by default next cycle. This option takes an entire disk and have a fix set of dataset installed. There is no support but we need this to make an official install option for the next LTS. The patch has been created to be as minimal as possible. Partman does a full disk partitioning, and then the script zsys-setup the first non-ESP partition and replaces with zfs pools. 4 partitions are created: 1. if GPT partitioning: ESP partition. This one is done by partman directly. 2. bpool (for boot), pool with older zfs compatible version to be readable by grub) 3. rpool (for / and userdataset) 4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on moved to the ESP) Additionaly if a swap file has been created by ubiquity, it is recreated as a ZFS volume. If the script fails to execute, the final installation is an ext4 installation on entire disk. Note that the implementation is slightly different from the specification due to a difficult cohabitation with partman in the custom partitioning page. Please find attached the MP on ubiquity as well as the package build log. https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan- amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz To manage notifications about this bug go to:
