[Touch-packages] [Bug 1820001] Re: vgcfgbackup stuck in kernel, causing lvm and udevd block forever
It seems that simple
`ls -la /dev/disk/by-path`
freezes `ls` process.
However, /dev listing normally, as well as /dev/disk/{by-id,by-
label,etc} (except `by-path`).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1820001
Title:
vgcfgbackup stuck in kernel, causing lvm and udevd block forever
Status in lvm2 package in Ubuntu:
New
Bug description:
Hello
I am using lvm snapshots over sofware raid with 4 devices for rsync
backups.
Recently I found out that it is stuck and any operaton with lvm is stuck as
well.
This also causes 1000+ processes of systemd-udevd to be in interpretable
sleep and cannot be killed.
My backup script looks like this:
/sbin/vgcfgbackup -qq main
/sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root
mount /dev/mapper/main-backup /mnt/root_snapshot
*rsync stuff*
umount /mnt/root_snapshot
/sbin/lvremove -yqq /dev/mapper/main-backup
Launching as not root `pvs --unbuffered --readonly -t -` is stuck at:
#filters/filter-persistent.c:51 Wiping cache of LVM-capable devices
Launching as not root `lvs - --unbuffered --readonly -` us stuck at:
#toollib.c:3736 Get list of VGs on system
I have a lot of processes stucked (total number ~1000):
root 756 0.0 0.0 56400 8428 ?Dфев26 0:00
/sbin/vgcfgbackup -qq main
root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00
/lib/systemd/systemd-udevd
root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00
/lib/systemd/systemd-udevd
root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00
/lib/systemd/systemd-udevd
root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm
--monitor --scan --oneshot
root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs
root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd
admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs -
-dd --readonly -t --unbuffered
In dmesg I have following logs:
[16983388.190818] general protection fault: [#41] SMP PTI
[16987988.464353] general protection fault: [#42] SMP PTI
In system journal:
Mar 14 06:47:35 - systemd[1]: systemd-udevd.service: Found left-over process
17886 (systemd-udevd) in control group while starting unit. Ignoring.
Mar 14 06:47:35 - systemd[1]: This usually indicates unclean termination of a
previous run, or service implementation deficiencies.
Mar 14 06:47:35- systemd[1]: systemd-udevd.service: Found left-over process
17887 (systemd-udevd) in control group while starting unit. Ignoring.
Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116768
'/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1'
is taking a long time
Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116780
'/devices/pci:00/:00:1f.2/ata2/host1/target1:0:1/1:0:1:0/block/sdc/sdc1'
is taking a long time
lvmdump hangs at `Gathering /dev listening`, but I was able to terminate it.
mdstat:
md0 : active raid10 sdb1[1] sdc1[2] sda1[0] sdd1[3]
1953259520 blocks super 1.2 512K chunks 2 near-copies [4/4] []
bitmap: 1/15 pages [4KB], 65536KB chunk
OS: Ubuntu 18.04.1 LTS
Kernel: 4.15.0-29-generic
lvm2: 2.02.176-4.1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+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 1820001] Re: vgcfgbackup stuck in kernel, causing lvm and udevd block forever
ps axu | awk '$8 ~ /^D/' ** Attachment added: "stuck processes (D)" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245990/+files/stucked_processes.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1820001 Title: vgcfgbackup stuck in kernel, causing lvm and udevd block forever Status in lvm2 package in Ubuntu: New Bug description: Hello I am using lvm snapshots over sofware raid with 4 devices for rsync backups. Recently I found out that it is stuck and any operaton with lvm is stuck as well. This also causes 1000+ processes of systemd-udevd to be in interpretable sleep and cannot be killed. My backup script looks like this: /sbin/vgcfgbackup -qq main /sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root mount /dev/mapper/main-backup /mnt/root_snapshot *rsync stuff* umount /mnt/root_snapshot /sbin/lvremove -yqq /dev/mapper/main-backup Launching as not root `pvs --unbuffered --readonly -t -` is stuck at: #filters/filter-persistent.c:51 Wiping cache of LVM-capable devices Launching as not root `lvs - --unbuffered --readonly -` us stuck at: #toollib.c:3736 Get list of VGs on system I have a lot of processes stucked (total number ~1000): root 756 0.0 0.0 56400 8428 ?Dфев26 0:00 /sbin/vgcfgbackup -qq main root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm --monitor --scan --oneshot root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs - -dd --readonly -t --unbuffered In dmesg I have following logs: [16983388.190818] general protection fault: [#41] SMP PTI [16987988.464353] general protection fault: [#42] SMP PTI In system journal: Mar 14 06:47:35 - systemd[1]: systemd-udevd.service: Found left-over process 17886 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:47:35 - systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 14 06:47:35- systemd[1]: systemd-udevd.service: Found left-over process 17887 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116768 '/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1' is taking a long time Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116780 '/devices/pci:00/:00:1f.2/ata2/host1/target1:0:1/1:0:1:0/block/sdc/sdc1' is taking a long time lvmdump hangs at `Gathering /dev listening`, but I was able to terminate it. mdstat: md0 : active raid10 sdb1[1] sdc1[2] sda1[0] sdd1[3] 1953259520 blocks super 1.2 512K chunks 2 near-copies [4/4] [] bitmap: 1/15 pages [4KB], 65536KB chunk OS: Ubuntu 18.04.1 LTS Kernel: 4.15.0-29-generic lvm2: 2.02.176-4.1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+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 1820001] Re: vgcfgbackup stuck in kernel, causing lvm and udevd block forever
** Attachment removed: "journalctl" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245988/+files/journalctl-part.txt ** Attachment added: "journalctl" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245989/+files/journalctl-part.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1820001 Title: vgcfgbackup stuck in kernel, causing lvm and udevd block forever Status in lvm2 package in Ubuntu: New Bug description: Hello I am using lvm snapshots over sofware raid with 4 devices for rsync backups. Recently I found out that it is stuck and any operaton with lvm is stuck as well. This also causes 1000+ processes of systemd-udevd to be in interpretable sleep and cannot be killed. My backup script looks like this: /sbin/vgcfgbackup -qq main /sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root mount /dev/mapper/main-backup /mnt/root_snapshot *rsync stuff* umount /mnt/root_snapshot /sbin/lvremove -yqq /dev/mapper/main-backup Launching as not root `pvs --unbuffered --readonly -t -` is stuck at: #filters/filter-persistent.c:51 Wiping cache of LVM-capable devices Launching as not root `lvs - --unbuffered --readonly -` us stuck at: #toollib.c:3736 Get list of VGs on system I have a lot of processes stucked (total number ~1000): root 756 0.0 0.0 56400 8428 ?Dфев26 0:00 /sbin/vgcfgbackup -qq main root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm --monitor --scan --oneshot root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs - -dd --readonly -t --unbuffered In dmesg I have following logs: [16983388.190818] general protection fault: [#41] SMP PTI [16987988.464353] general protection fault: [#42] SMP PTI In system journal: Mar 14 06:47:35 - systemd[1]: systemd-udevd.service: Found left-over process 17886 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:47:35 - systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 14 06:47:35- systemd[1]: systemd-udevd.service: Found left-over process 17887 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116768 '/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1' is taking a long time Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116780 '/devices/pci:00/:00:1f.2/ata2/host1/target1:0:1/1:0:1:0/block/sdc/sdc1' is taking a long time lvmdump hangs at `Gathering /dev listening`, but I was able to terminate it. mdstat: md0 : active raid10 sdb1[1] sdc1[2] sda1[0] sdd1[3] 1953259520 blocks super 1.2 512K chunks 2 near-copies [4/4] [] bitmap: 1/15 pages [4KB], 65536KB chunk OS: Ubuntu 18.04.1 LTS Kernel: 4.15.0-29-generic lvm2: 2.02.176-4.1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+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 1819996] Re: package tzdata 2018i-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 29
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: tzdata (Ubuntu) Importance: Undecided => Low ** Changed in: tzdata (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1819996 Title: package tzdata 2018i-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 29 Status in tzdata package in Ubuntu: Invalid Bug description: system error window appears when opening ubuntu ProblemType: Package DistroRelease: Ubuntu 18.10 Package: tzdata 2018i-0ubuntu0.18.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Thu Mar 14 02:21:47 2019 DuplicateSignature: package:tzdata:2018i-0ubuntu0.18.10 Setting up libssl1.0.0:amd64 (1.0.2n-1ubuntu6.2) ... Can't locate object method "new" via package "Text::Iconv" at /usr/share/perl5/Debconf/Encoding.pm line 65. dpkg: error processing package libssl1.0.0:amd64 (--configure): installed libssl1.0.0:amd64 package post-installation script subprocess returned error exit status 29 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 29 InstallationDate: Installed on 2019-03-13 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: tzdata Title: package tzdata 2018i-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 29 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1819996/+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 1615381] Re: apt-get autoremove may remove current kernel
** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => High ** Changed in: unattended-upgrades (Ubuntu Artful) Importance: Undecided => High ** Changed in: unattended-upgrades (Ubuntu Trusty) Importance: Undecided => Low -- 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/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Won't Fix Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: Won't Fix Status in unattended-upgrades source package in Trusty: New Status in apt source package in Xenial: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Committed Status in apt source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Bug description: This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified] mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-07-30T12:15:32.706300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+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 1820001] Re: vgcfgbackup stuck in kernel, causing lvm and udevd block forever
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245981/+files/dmesg-part.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1820001 Title: vgcfgbackup stuck in kernel, causing lvm and udevd block forever Status in lvm2 package in Ubuntu: New Bug description: Hello I am using lvm snapshots over sofware raid with 4 devices for rsync backups. Recently I found out that it is stuck and any operaton with lvm is stuck as well. This also causes 1000+ processes of systemd-udevd to be in interpretable sleep and cannot be killed. My backup script looks like this: /sbin/vgcfgbackup -qq main /sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root mount /dev/mapper/main-backup /mnt/root_snapshot *rsync stuff* umount /mnt/root_snapshot /sbin/lvremove -yqq /dev/mapper/main-backup Launching as not root `pvs --unbuffered --readonly -t -` is stuck at: #filters/filter-persistent.c:51 Wiping cache of LVM-capable devices Launching as not root `lvs - --unbuffered --readonly -` us stuck at: #toollib.c:3736 Get list of VGs on system I have a lot of processes stucked (total number ~1000): root 756 0.0 0.0 56400 8428 ?Dфев26 0:00 /sbin/vgcfgbackup -qq main root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm --monitor --scan --oneshot root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs - -dd --readonly -t --unbuffered In dmesg I have following logs: [16983388.190818] general protection fault: [#41] SMP PTI [16987988.464353] general protection fault: [#42] SMP PTI In system journal: Mar 14 06:47:35 - systemd[1]: systemd-udevd.service: Found left-over process 17886 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:47:35 - systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 14 06:47:35- systemd[1]: systemd-udevd.service: Found left-over process 17887 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116768 '/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1' is taking a long time Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116780 '/devices/pci:00/:00:1f.2/ata2/host1/target1:0:1/1:0:1:0/block/sdc/sdc1' is taking a long time lvmdump hangs at `Gathering /dev listening`, but I was able to terminate it. mdstat: md0 : active raid10 sdb1[1] sdc1[2] sda1[0] sdd1[3] 1953259520 blocks super 1.2 512K chunks 2 near-copies [4/4] [] bitmap: 1/15 pages [4KB], 65536KB chunk OS: Ubuntu 18.04.1 LTS Kernel: 4.15.0-29-generic lvm2: 2.02.176-4.1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+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 1820001] Re: vgcfgbackup stuck in kernel, causing lvm and udevd block forever
** Attachment added: "lvs -" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245983/+files/lvs_.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1820001 Title: vgcfgbackup stuck in kernel, causing lvm and udevd block forever Status in lvm2 package in Ubuntu: New Bug description: Hello I am using lvm snapshots over sofware raid with 4 devices for rsync backups. Recently I found out that it is stuck and any operaton with lvm is stuck as well. This also causes 1000+ processes of systemd-udevd to be in interpretable sleep and cannot be killed. My backup script looks like this: /sbin/vgcfgbackup -qq main /sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root mount /dev/mapper/main-backup /mnt/root_snapshot *rsync stuff* umount /mnt/root_snapshot /sbin/lvremove -yqq /dev/mapper/main-backup Launching as not root `pvs --unbuffered --readonly -t -` is stuck at: #filters/filter-persistent.c:51 Wiping cache of LVM-capable devices Launching as not root `lvs - --unbuffered --readonly -` us stuck at: #toollib.c:3736 Get list of VGs on system I have a lot of processes stucked (total number ~1000): root 756 0.0 0.0 56400 8428 ?Dфев26 0:00 /sbin/vgcfgbackup -qq main root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm --monitor --scan --oneshot root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs - -dd --readonly -t --unbuffered In dmesg I have following logs: [16983388.190818] general protection fault: [#41] SMP PTI [16987988.464353] general protection fault: [#42] SMP PTI In system journal: Mar 14 06:47:35 - systemd[1]: systemd-udevd.service: Found left-over process 17886 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:47:35 - systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 14 06:47:35- systemd[1]: systemd-udevd.service: Found left-over process 17887 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116768 '/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1' is taking a long time Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116780 '/devices/pci:00/:00:1f.2/ata2/host1/target1:0:1/1:0:1:0/block/sdc/sdc1' is taking a long time lvmdump hangs at `Gathering /dev listening`, but I was able to terminate it. mdstat: md0 : active raid10 sdb1[1] sdc1[2] sda1[0] sdd1[3] 1953259520 blocks super 1.2 512K chunks 2 near-copies [4/4] [] bitmap: 1/15 pages [4KB], 65536KB chunk OS: Ubuntu 18.04.1 LTS Kernel: 4.15.0-29-generic lvm2: 2.02.176-4.1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+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 1820001] Re: vgcfgbackup stuck in kernel, causing lvm and udevd block forever
** Attachment added: "vgcfgbackup -qq main" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245982/+files/lvm-configuration.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1820001 Title: vgcfgbackup stuck in kernel, causing lvm and udevd block forever Status in lvm2 package in Ubuntu: New Bug description: Hello I am using lvm snapshots over sofware raid with 4 devices for rsync backups. Recently I found out that it is stuck and any operaton with lvm is stuck as well. This also causes 1000+ processes of systemd-udevd to be in interpretable sleep and cannot be killed. My backup script looks like this: /sbin/vgcfgbackup -qq main /sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root mount /dev/mapper/main-backup /mnt/root_snapshot *rsync stuff* umount /mnt/root_snapshot /sbin/lvremove -yqq /dev/mapper/main-backup Launching as not root `pvs --unbuffered --readonly -t -` is stuck at: #filters/filter-persistent.c:51 Wiping cache of LVM-capable devices Launching as not root `lvs - --unbuffered --readonly -` us stuck at: #toollib.c:3736 Get list of VGs on system I have a lot of processes stucked (total number ~1000): root 756 0.0 0.0 56400 8428 ?Dфев26 0:00 /sbin/vgcfgbackup -qq main root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm --monitor --scan --oneshot root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs - -dd --readonly -t --unbuffered In dmesg I have following logs: [16983388.190818] general protection fault: [#41] SMP PTI [16987988.464353] general protection fault: [#42] SMP PTI In system journal: Mar 14 06:47:35 - systemd[1]: systemd-udevd.service: Found left-over process 17886 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:47:35 - systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 14 06:47:35- systemd[1]: systemd-udevd.service: Found left-over process 17887 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116768 '/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1' is taking a long time Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116780 '/devices/pci:00/:00:1f.2/ata2/host1/target1:0:1/1:0:1:0/block/sdc/sdc1' is taking a long time lvmdump hangs at `Gathering /dev listening`, but I was able to terminate it. mdstat: md0 : active raid10 sdb1[1] sdc1[2] sda1[0] sdd1[3] 1953259520 blocks super 1.2 512K chunks 2 near-copies [4/4] [] bitmap: 1/15 pages [4KB], 65536KB chunk OS: Ubuntu 18.04.1 LTS Kernel: 4.15.0-29-generic lvm2: 2.02.176-4.1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+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 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly
** Tags added: patch-accepted-upstream patch-forwarded-debian -- 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/1818282 Title: systemd-networkd - RoutingPolicyRule does not apply correctly Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Status in systemd package in Debian: New Bug description: [Impact] When attaching multiple IPs on secondary interface the routing policy rules do not apply for all IPs. The rules that are applied after restarting networkd are random. The issue has been reported and addressed upstream. [Test Case] Attach multiple IPs to secondary interface, config file: $ cat /etc/systemd/network/ens8.network [Match] Name=ens8 [Network] Address=172.31.28.195/20 Address=172.31.24.151/20 Address=172.31.24.152/20 Address=172.31.24.153/20 [Route] Destination=0.0.0.0/0 Gateway=172.31.16.1 Table=1000 [Route] Destination=172.31.24.153 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.28.195 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.24.151 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.24.152 Gateway=0.0.0.0 Scope=link Table=1000 [RoutingPolicyRule] From=172.31.24.153 Table=1000 [RoutingPolicyRule] From=172.31.28.195 Table=1000 [RoutingPolicyRule] From=172.31.24.152 Table=1000 [RoutingPolicyRule] From=172.31.24.151 Table=1000 $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 32766:from all lookup main 32767:from all lookup default - restart networkd $ sudo systemctl restart systemd-networkd $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 0:from 172.31.24.153 lookup 1000 0:from 172.31.28.195 lookup 1000 32766:from all lookup main 32767:from all lookup default - restart again $ sudo systemctl restart systemd-networkd $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 0:from 172.31.24.152 lookup 1000 32766:from all lookup main 32767:from all lookup default The behaviour is random [Regression Potential] May impact the systemd-networkd service functionality. [Other] Affects Disco Bionic and Cosmic. Upstream bug : https://github.com/systemd/systemd/issues/11280 Upstream fix : https://github.com/systemd/systemd/pull/11795/commits $ lsb_release -rd Description: Ubuntu Disco Dingo (development branch) Release: 19.04 Systemd version : systemd: Installed: 240-6ubuntu1 Candidate: 240-6ubuntu1 Version table: *** 240-6ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818282/+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 1820001] Re: vgcfgbackup stuck in kernel, causing lvm and udevd block forever
** Attachment added: "pvs -" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245984/+files/pvs_.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1820001 Title: vgcfgbackup stuck in kernel, causing lvm and udevd block forever Status in lvm2 package in Ubuntu: New Bug description: Hello I am using lvm snapshots over sofware raid with 4 devices for rsync backups. Recently I found out that it is stuck and any operaton with lvm is stuck as well. This also causes 1000+ processes of systemd-udevd to be in interpretable sleep and cannot be killed. My backup script looks like this: /sbin/vgcfgbackup -qq main /sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root mount /dev/mapper/main-backup /mnt/root_snapshot *rsync stuff* umount /mnt/root_snapshot /sbin/lvremove -yqq /dev/mapper/main-backup Launching as not root `pvs --unbuffered --readonly -t -` is stuck at: #filters/filter-persistent.c:51 Wiping cache of LVM-capable devices Launching as not root `lvs - --unbuffered --readonly -` us stuck at: #toollib.c:3736 Get list of VGs on system I have a lot of processes stucked (total number ~1000): root 756 0.0 0.0 56400 8428 ?Dфев26 0:00 /sbin/vgcfgbackup -qq main root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm --monitor --scan --oneshot root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs - -dd --readonly -t --unbuffered In dmesg I have following logs: [16983388.190818] general protection fault: [#41] SMP PTI [16987988.464353] general protection fault: [#42] SMP PTI In system journal: Mar 14 06:47:35 - systemd[1]: systemd-udevd.service: Found left-over process 17886 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:47:35 - systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 14 06:47:35- systemd[1]: systemd-udevd.service: Found left-over process 17887 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116768 '/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1' is taking a long time Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116780 '/devices/pci:00/:00:1f.2/ata2/host1/target1:0:1/1:0:1:0/block/sdc/sdc1' is taking a long time lvmdump hangs at `Gathering /dev listening`, but I was able to terminate it. mdstat: md0 : active raid10 sdb1[1] sdc1[2] sda1[0] sdd1[3] 1953259520 blocks super 1.2 512K chunks 2 near-copies [4/4] [] bitmap: 1/15 pages [4KB], 65536KB chunk OS: Ubuntu 18.04.1 LTS Kernel: 4.15.0-29-generic lvm2: 2.02.176-4.1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+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 1820001] Re: vgcfgbackup stuck in kernel, causing lvm and udevd block forever
** Attachment added: "journalctl" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245988/+files/journalctl-part.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1820001 Title: vgcfgbackup stuck in kernel, causing lvm and udevd block forever Status in lvm2 package in Ubuntu: New Bug description: Hello I am using lvm snapshots over sofware raid with 4 devices for rsync backups. Recently I found out that it is stuck and any operaton with lvm is stuck as well. This also causes 1000+ processes of systemd-udevd to be in interpretable sleep and cannot be killed. My backup script looks like this: /sbin/vgcfgbackup -qq main /sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root mount /dev/mapper/main-backup /mnt/root_snapshot *rsync stuff* umount /mnt/root_snapshot /sbin/lvremove -yqq /dev/mapper/main-backup Launching as not root `pvs --unbuffered --readonly -t -` is stuck at: #filters/filter-persistent.c:51 Wiping cache of LVM-capable devices Launching as not root `lvs - --unbuffered --readonly -` us stuck at: #toollib.c:3736 Get list of VGs on system I have a lot of processes stucked (total number ~1000): root 756 0.0 0.0 56400 8428 ?Dфев26 0:00 /sbin/vgcfgbackup -qq main root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm --monitor --scan --oneshot root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs - -dd --readonly -t --unbuffered In dmesg I have following logs: [16983388.190818] general protection fault: [#41] SMP PTI [16987988.464353] general protection fault: [#42] SMP PTI In system journal: Mar 14 06:47:35 - systemd[1]: systemd-udevd.service: Found left-over process 17886 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:47:35 - systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 14 06:47:35- systemd[1]: systemd-udevd.service: Found left-over process 17887 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116768 '/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1' is taking a long time Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116780 '/devices/pci:00/:00:1f.2/ata2/host1/target1:0:1/1:0:1:0/block/sdc/sdc1' is taking a long time lvmdump hangs at `Gathering /dev listening`, but I was able to terminate it. mdstat: md0 : active raid10 sdb1[1] sdc1[2] sda1[0] sdd1[3] 1953259520 blocks super 1.2 512K chunks 2 near-copies [4/4] [] bitmap: 1/15 pages [4KB], 65536KB chunk OS: Ubuntu 18.04.1 LTS Kernel: 4.15.0-29-generic lvm2: 2.02.176-4.1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+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 1820001] [NEW] vgcfgbackup stuck in kernel, causing lvm and udevd block forever
Public bug reported: Hello I am using lvm snapshots over sofware raid with 4 devices for rsync backups. Recently I found out that it is stuck and any operaton with lvm is stuck as well. This also causes 1000+ processes of systemd-udevd to be in interpretable sleep and cannot be killed. My backup script looks like this: /sbin/vgcfgbackup -qq main /sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root mount /dev/mapper/main-backup /mnt/root_snapshot *rsync stuff* umount /mnt/root_snapshot /sbin/lvremove -yqq /dev/mapper/main-backup Launching as not root `pvs --unbuffered --readonly -t -` is stuck at: #filters/filter-persistent.c:51 Wiping cache of LVM-capable devices Launching as not root `lvs - --unbuffered --readonly -` us stuck at: #toollib.c:3736 Get list of VGs on system I have a lot of processes stucked (total number ~1000): root 756 0.0 0.0 56400 8428 ?Dфев26 0:00 /sbin/vgcfgbackup -qq main root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm --monitor --scan --oneshot root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs - -dd --readonly -t --unbuffered In dmesg I have following logs: [16983388.190818] general protection fault: [#41] SMP PTI [16987988.464353] general protection fault: [#42] SMP PTI In system journal: Mar 14 06:47:35 - systemd[1]: systemd-udevd.service: Found left-over process 17886 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:47:35 - systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 14 06:47:35- systemd[1]: systemd-udevd.service: Found left-over process 17887 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116768 '/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1' is taking a long time Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116780 '/devices/pci:00/:00:1f.2/ata2/host1/target1:0:1/1:0:1:0/block/sdc/sdc1' is taking a long time lvmdump hangs at `Gathering /dev listening`, but I was able to terminate it. mdstat: md0 : active raid10 sdb1[1] sdc1[2] sda1[0] sdd1[3] 1953259520 blocks super 1.2 512K chunks 2 near-copies [4/4] [] bitmap: 1/15 pages [4KB], 65536KB chunk OS: Ubuntu 18.04.1 LTS Kernel: 4.15.0-29-generic lvm2: 2.02.176-4.1ubuntu3 ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Package changed: skype (Ubuntu) => lvm2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1820001 Title: vgcfgbackup stuck in kernel, causing lvm and udevd block forever Status in lvm2 package in Ubuntu: New Bug description: Hello I am using lvm snapshots over sofware raid with 4 devices for rsync backups. Recently I found out that it is stuck and any operaton with lvm is stuck as well. This also causes 1000+ processes of systemd-udevd to be in interpretable sleep and cannot be killed. My backup script looks like this: /sbin/vgcfgbackup -qq main /sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root mount /dev/mapper/main-backup /mnt/root_snapshot *rsync stuff* umount /mnt/root_snapshot /sbin/lvremove -yqq /dev/mapper/main-backup Launching as not root `pvs --unbuffered --readonly -t -` is stuck at: #filters/filter-persistent.c:51 Wiping cache of LVM-capable devices Launching as not root `lvs - --unbuffered --readonly -` us stuck at: #toollib.c:3736 Get list of VGs on system I have a lot of processes stucked (total number ~1000): root 756 0.0 0.0 56400 8428 ?Dфев26 0:00 /sbin/vgcfgbackup -qq main root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm --monitor --scan --oneshot root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs - -dd --readonly -t
[Touch-packages] [Bug 1820001] Re: vgcfgbackup stuck in kernel, causing lvm and udevd block forever
** Attachment added: "apt list --installed" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+attachment/5245979/+files/apt_list_installed.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1820001 Title: vgcfgbackup stuck in kernel, causing lvm and udevd block forever Status in lvm2 package in Ubuntu: New Bug description: Hello I am using lvm snapshots over sofware raid with 4 devices for rsync backups. Recently I found out that it is stuck and any operaton with lvm is stuck as well. This also causes 1000+ processes of systemd-udevd to be in interpretable sleep and cannot be killed. My backup script looks like this: /sbin/vgcfgbackup -qq main /sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root mount /dev/mapper/main-backup /mnt/root_snapshot *rsync stuff* umount /mnt/root_snapshot /sbin/lvremove -yqq /dev/mapper/main-backup Launching as not root `pvs --unbuffered --readonly -t -` is stuck at: #filters/filter-persistent.c:51 Wiping cache of LVM-capable devices Launching as not root `lvs - --unbuffered --readonly -` us stuck at: #toollib.c:3736 Get list of VGs on system I have a lot of processes stucked (total number ~1000): root 756 0.0 0.0 56400 8428 ?Dфев26 0:00 /sbin/vgcfgbackup -qq main root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm --monitor --scan --oneshot root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs - -dd --readonly -t --unbuffered In dmesg I have following logs: [16983388.190818] general protection fault: [#41] SMP PTI [16987988.464353] general protection fault: [#42] SMP PTI In system journal: Mar 14 06:47:35 - systemd[1]: systemd-udevd.service: Found left-over process 17886 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:47:35 - systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 14 06:47:35- systemd[1]: systemd-udevd.service: Found left-over process 17887 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116768 '/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1' is taking a long time Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116780 '/devices/pci:00/:00:1f.2/ata2/host1/target1:0:1/1:0:1:0/block/sdc/sdc1' is taking a long time lvmdump hangs at `Gathering /dev listening`, but I was able to terminate it. mdstat: md0 : active raid10 sdb1[1] sdc1[2] sda1[0] sdd1[3] 1953259520 blocks super 1.2 512K chunks 2 near-copies [4/4] [] bitmap: 1/15 pages [4KB], 65536KB chunk OS: Ubuntu 18.04.1 LTS Kernel: 4.15.0-29-generic lvm2: 2.02.176-4.1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1820001/+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 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
** No longer affects: gnome-software (Ubuntu Artful) ** No longer affects: gnome-software (Ubuntu) ** Changed in: unattended-upgrades (Ubuntu Xenial) Importance: Undecided => High ** No longer affects: apt (Ubuntu Artful) ** No longer affects: apt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-manager source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in update-manager source package in Artful: Fix Released Bug description: [Impact] * Update-manager and unattended-upgrades install many kernel packages during the lifetime of a release but does not remove them automatically leading to those packages filling disk space potentially completely filling /boot and making the system unable to install updates or even boot. * Stable release users are impacted by this bug for years and their systems already collected many autoremovable unused kernel packages, thus they would benefit from backporting the fix greatly. * The bug is fixed by removing autoremovable (not currently booted) kernel packages when running unattended-upgrades or update-manager. Update manager offers the kernel removals when there are other updates to be installed. [Test Case] 1. Install kernel packages to be removed, mark them auto-installed and run apt's kernel hook script to make apt consider them autoremovable: sudo apt install -y linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic sudo apt-mark auto linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic sudo /etc/kernel/postinst.d/apt-auto-removal 2. Also downgrade a package to be upgraded: sudo apt-get install -y --allow-downgrades ca- certificates=20160104ubuntu1 3. (update-manager). Run update-manager and observe that kernel packages are offered for removal in Details of updates. sudo update-manager 4. (update-manager) Click on Install Now and observe that the kernel packages are removed. 3. (unattended-upgrades, the fix comes in an update of u-u) Run unattended-upgrades manually and observe the removal of the autoremovable kernel packages: sudo unattended-upgrade -v [Regression Potential] The change may cause update-manager or unattanded-upgrades to remove used kernel packages or fail to install other package updates. [Other Info] The unattended-upgrades fix is uploaded with many other fixes and those may cause regressions in other areas in unattended-upgrades. [Original bug text] When using default settings for unattended-upgrade i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, unattended-upgrade is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because unattended-upgrade compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. Consequently, if user installs new kernels using e.g. update-manager, the excessive kernels will not be removed by unattended-upgrade, and eventually (small) /boot will become full. Expected behavior: handle removing of unused packages differently at least until other package management software installed by default can handle removing of new unused packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624644/+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 1820001] [NEW] vgcfgbackup stuck in kernel, causing lvm and udevd block forever
You have been subscribed to a public bug: Hello I am using lvm snapshots over sofware raid with 4 devices for rsync backups. Recently I found out that it is stuck and any operaton with lvm is stuck as well. This also causes 1000+ processes of systemd-udevd to be in interpretable sleep and cannot be killed. My backup script looks like this: /sbin/vgcfgbackup -qq main /sbin/lvcreate -qq --size 20G --snapshot --name backup /dev/mapper/main-root mount /dev/mapper/main-backup /mnt/root_snapshot *rsync stuff* umount /mnt/root_snapshot /sbin/lvremove -yqq /dev/mapper/main-backup Launching as not root `pvs --unbuffered --readonly -t -` is stuck at: #filters/filter-persistent.c:51 Wiping cache of LVM-capable devices Launching as not root `lvs - --unbuffered --readonly -` us stuck at: #toollib.c:3736 Get list of VGs on system I have a lot of processes stucked (total number ~1000): root 756 0.0 0.0 56400 8428 ?Dфев26 0:00 /sbin/vgcfgbackup -qq main root 21723 0.0 0.0 36940 1860 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21724 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 21728 0.0 0.0 36940 1808 ?Dмар13 0:00 /lib/systemd/systemd-udevd root 14541 0.0 0.0 7780 2524 ?D06:25 0:00 /sbin/mdadm --monitor --scan --oneshot root 8792 0.0 0.0 56548 8308 ?D05:59 0:00 lvs root 11343 0.0 0.0 119424 7632 ?S06:10 0:00 sudo lvs -vd admin12112 0.0 0.0 56596 8368 ?D06:14 0:00 lvs - -dd --readonly -t --unbuffered In dmesg I have following logs: [16983388.190818] general protection fault: [#41] SMP PTI [16987988.464353] general protection fault: [#42] SMP PTI In system journal: Mar 14 06:47:35 - systemd[1]: systemd-udevd.service: Found left-over process 17886 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:47:35 - systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Mar 14 06:47:35- systemd[1]: systemd-udevd.service: Found left-over process 17887 (systemd-udevd) in control group while starting unit. Ignoring. Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116768 '/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1' is taking a long time Mar 14 06:50:28 - systemd-udevd[20282]: seq 1116780 '/devices/pci:00/:00:1f.2/ata2/host1/target1:0:1/1:0:1:0/block/sdc/sdc1' is taking a long time lvmdump hangs at `Gathering /dev listening`, but I was able to terminate it. mdstat: md0 : active raid10 sdb1[1] sdc1[2] sda1[0] sdd1[3] 1953259520 blocks super 1.2 512K chunks 2 near-copies [4/4] [] bitmap: 1/15 pages [4KB], 65536KB chunk OS: Ubuntu 18.04.1 LTS Kernel: 4.15.0-29-generic lvm2: 2.02.176-4.1ubuntu3 ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- vgcfgbackup stuck in kernel, causing lvm and udevd block forever https://bugs.launchpad.net/bugs/1820001 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401474] Re: [Dell Inspiron 7737] The power indicator won't be available until the adapter connected / disconnected
I have faced the same situation with my MacOS after so I contacted https://applesupportnumber.net/ for the solution and they told me to update the device but after updating the device the problem remains the same. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1401474 Title: [Dell Inspiron 7737] The power indicator won't be available until the adapter connected / disconnected Status in indicator-power package in Ubuntu: Confirmed Bug description: CID: 201306-13869 Dell Inspiron 7737 The power indicator on this system only appears after you connect or disconnect it from the adapter. After it appears, reboot it will make the indicator disappear again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Dec 11 05:06:39 2014 InstallationDate: Installed on 2014-12-11 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1401474/+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 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used
** Tags removed: rls-z-incoming verification-needed wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1544942 Title: Marks unneeded packages as manually installed, if --dry-run is used Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Bug description: $ sudo unattended-upgrade --dry-run -d Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=wily-security'] pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] Option --dry-run given, *not* performing real actions Packages that will be upgraded: marking linux-headers-4.2.0-16-generic for remove marking linux-headers-4.2.0-16 for remove marking linux-image-4.2.0-16-generic for remove marking linux-image-extra-4.2.0-16-generic for remove Packages that are auto removed: 'linux-headers-4.2.0-16-generic linux-headers-4.2.0-16 linux-image-4.2.0-16-generic linux-image-extra-4.2.0-16-generic' /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64 /usr/bin/dpkg --status-fd 11 --configure --pending Packages were successfully auto-removed InstCount=0 DelCount=4 BrokenCount=0 $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux- headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux- image-4.2.0-16-generic:amd64 $ sudo unattended-upgrade --dry-run -d Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=wily-security'] pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] No packages found that can be upgraded unattended and no pending auto-removals Expect the packages to remain automatically installed after each `sudo unattended-upgrade --dry-run -d`. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unattended-upgrades 0.86.2ubuntu1.1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Feb 12 13:58:29 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-24 (18 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2016-02-12T13:53:13.426454 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1544942/+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 1787460] Re: Unattended upgrades removed linux-image-generic
** Changed in: apt (Ubuntu Cosmic) Importance: Undecided => Critical ** Changed in: apt (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => High ** Changed in: apt (Ubuntu Trusty) Importance: Undecided => High -- 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/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Trusty: Fix Committed Status in linux-meta source package in Trusty: New Status in linux-meta-hwe source package in Trusty: New Status in apt source package in Xenial: Fix Committed Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Released Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1819996] Re: package tzdata 2018i-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 29
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1819996 Title: package tzdata 2018i-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 29 Status in tzdata package in Ubuntu: New Bug description: system error window appears when opening ubuntu ProblemType: Package DistroRelease: Ubuntu 18.10 Package: tzdata 2018i-0ubuntu0.18.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Thu Mar 14 02:21:47 2019 DuplicateSignature: package:tzdata:2018i-0ubuntu0.18.10 Setting up libssl1.0.0:amd64 (1.0.2n-1ubuntu6.2) ... Can't locate object method "new" via package "Text::Iconv" at /usr/share/perl5/Debconf/Encoding.pm line 65. dpkg: error processing package libssl1.0.0:amd64 (--configure): installed libssl1.0.0:amd64 package post-installation script subprocess returned error exit status 29 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 29 InstallationDate: Installed on 2019-03-13 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: tzdata Title: package tzdata 2018i-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 29 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1819996/+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 1819996] [NEW] package tzdata 2018i-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 29
Public bug reported: system error window appears when opening ubuntu ProblemType: Package DistroRelease: Ubuntu 18.10 Package: tzdata 2018i-0ubuntu0.18.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Thu Mar 14 02:21:47 2019 DuplicateSignature: package:tzdata:2018i-0ubuntu0.18.10 Setting up libssl1.0.0:amd64 (1.0.2n-1ubuntu6.2) ... Can't locate object method "new" via package "Text::Iconv" at /usr/share/perl5/Debconf/Encoding.pm line 65. dpkg: error processing package libssl1.0.0:amd64 (--configure): installed libssl1.0.0:amd64 package post-installation script subprocess returned error exit status 29 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 29 InstallationDate: Installed on 2019-03-13 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: tzdata Title: package tzdata 2018i-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 29 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1819996 Title: package tzdata 2018i-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 29 Status in tzdata package in Ubuntu: New Bug description: system error window appears when opening ubuntu ProblemType: Package DistroRelease: Ubuntu 18.10 Package: tzdata 2018i-0ubuntu0.18.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Thu Mar 14 02:21:47 2019 DuplicateSignature: package:tzdata:2018i-0ubuntu0.18.10 Setting up libssl1.0.0:amd64 (1.0.2n-1ubuntu6.2) ... Can't locate object method "new" via package "Text::Iconv" at /usr/share/perl5/Debconf/Encoding.pm line 65. dpkg: error processing package libssl1.0.0:amd64 (--configure): installed libssl1.0.0:amd64 package post-installation script subprocess returned error exit status 29 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 29 InstallationDate: Installed on 2019-03-13 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: tzdata Title: package tzdata 2018i-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 29 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1819996/+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 1819909] Re: No border around windows, no resizing buttons (max, min, close). Windows cannot be moved or resized.
It sounds like the XFCE window manager has crashed, but I'm not sure. It might be a good idea to follow these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Summary changed: - Problem with windows + No border around windows, no resizing buttons (max, min, close). Windows cannot be moved or resized. ** Package changed: xorg (Ubuntu) => xfce4 (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/1819909 Title: No border around windows, no resizing buttons (max, min, close). Windows cannot be moved or resized. Status in xfce4 package in Ubuntu: New Bug description: No border around windows, no resizing buttons (max, min, close). Windows cannot be moved or resized. Alt+tab and Alt+F4 have no effect, but some other keyboard shortcuts, e.g. ctrl+alt+T and ctrl+Q, seem to work ok. Only closing a window changes focus; even clicking with mouse doesn't. For instance, I can use ctrl+alt+t to open a terminal, and click in it all I want, but even though it is on top, whatever I type just goes into this window. When I close the browser, however, it will gain focus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Wed Mar 13 08:30:21 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [17aa:3809] InstallationDate: Installed on 2018-09-10 (184 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:a745 IMC Networks Bus 001 Device 003: ID 0cf3:e360 Atheros Communications, Inc. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80T7 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/28/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 1GCN12WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: 00RD15IPG076 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15IBR dmi.modalias: dmi:bvnLENOVO:bvr1GCN12WW:bd02/28/2016:svnLENOVO:pn80T7:pvrLenovoideapad110-15IBR:rvnLENOVO:rn00RD15IPG076:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15IBR: dmi.product.family: IDEAPAD dmi.product.name: 80T7 dmi.product.version: Lenovo ideapad 110-15IBR dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1819909/+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 1458204] Re: removing kernels should not require a restart afterward
** Tags removed: rls-aa-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1458204/+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 1812014] Re: keyboard not responding after suspend after some time
I'm not sure how the Nvidia driver could be related. Although this looks relevant to keyboard problems. This appears a few times in your log (comment #22): sty 27 21:03:24 br00net gnome-shell[2527]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got undefined setEngine@resource:///org/gnome/shell/misc/ibusManager.js:212:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 activateInputSource@resource:///org/gnome/shell/ui/status/keyboard.js:490:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _emit@resource:///org/gnome/gjs/modules/signals.js:128:27 activate@resource:///org/gnome/shell/ui/status/keyboard.js:65:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _inputSourcesChanged@resource:///org/gnome/shell/ui/status/keyboard.js:620:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 reload@resource:///org/gnome/shell/ui/status/keyboard.js:369:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _ibusSetContentType@resource:///org/gnome/shell/ui/status/keyboard.js:691:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _emit@resource:///org/gnome/gjs/modules/signals.js:128:27 _setContentType@resource:///org/gnome/shell/misc/ibusManager.js:188:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1812014] Re: keyboard not responding after suspend after some time
Although ^^^ the above error ^^^ is already covered by bug 1812593. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1794033]
Hmm...`cp` in xterm is a pretty clear indicator that this issue is random and not triggered by a specific workload. Lionel suggested that it would be good to have a feedback from the kernel about what didn't pass validation. There is a kernel option to generate debug traces for that but you have to recompile your kernel with that option. Lionel, can you provide some details? It would be a good data point to see if a much older kernel produces this error (eg 4.9, 4.4). I can't deploy those kernels in Mesa i965 CI because they lack features needed to run our Vulkan test suites. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Confirmed Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1794033]
(In reply to Mark Janes from comment #20) > Yoshinori: Mesa i965 team is seeking a way to reproduce this bug, so we can > analyze and fix it. > > How often does this occur in your product? If it is reproducible, then > perhaps we can use an apitrace to investigate the root cause. While I operated in about 1month * 4 machines, I saw this problem only once. So, I don't know how to reproduce this. But when I saw this, I executed 'cp' command on xterm for copy some files. (I think that I do not matter.) I keep operating machine to know frequency. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Confirmed Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1819747] Re: dhclient does not work with busybox ip
This bug was fixed in the package busybox - 1:1.27.2-2ubuntu6 --- busybox (1:1.27.2-2ubuntu6) disco; urgency=medium * debian/patches/handle-ip-valid_lft.patch: Don't choke on ip addr add [...] valid_lft [...] preferred_lft. Closes LP: #1819747. -- Steve Langasek Tue, 12 Mar 2019 15:52:41 -0700 ** Changed in: busybox (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1819747 Title: dhclient does not work with busybox ip Status in busybox package in Ubuntu: Fix Released Status in cloud-initramfs-tools package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in isc-dhcp package in Ubuntu: Fix Released Status in busybox source package in Disco: Fix Released Status in cloud-initramfs-tools source package in Disco: Invalid Status in initramfs-tools source package in Disco: Invalid Status in isc-dhcp source package in Disco: Fix Released Bug description: After isc-dhcp update from 4.3.5 to 4.4.1, dhclient-script uses valid_lft option when adding an IPv4 address. When used on the initrd generated by initramfs-tools, this will fail because busybox ip does not support this option. This affects the use of cloud-initramfs-dyn-netconf and ip= command line option, which breaks initramfs-tools testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1819747/+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 1818953] Re: mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by executing perl script, multiple architectures
@ntyni excellent analysis! i like it a lot, and the patch is clean and
easy to understand.
Are you going to make a debian upload soon, or should I cherrypick that
for Ubuntu now?
** Also affects: perl (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924517
Importance: Unknown
Status: Unknown
** Also affects: perl (Ubuntu Disco)
Importance: Critical
Assignee: Canonical Foundations Team (canonical-foundations)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1818953
Title:
mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by
executing perl script, multiple architectures
Status in The Ubuntu-power-systems project:
Confirmed
Status in perl package in Ubuntu:
Confirmed
Status in perl source package in Disco:
Confirmed
Status in perl package in Debian:
Unknown
Bug description:
== Comment: #0 - NAGENDRA P. DONTAMSETTY - 2019-02-28
00:14:49 ==
---Problem Description---
Perl core dumping core on UBUNTU 19.04 by executing perl script
---uname output---
root@p8ct1p13:/tmp# uname -a Linux p8ct1p13.in.ibm.com 4.19.0-13-generic
#14-Ubuntu SMP Thu Feb 7 21:50:00 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = ppc64le and power8
---Debugger Data---
root@p8ct1p13:/tmp# file core
core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0,
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
---Steps to Reproduce---
Description: Perl core dumpinmg core on UBUNTU 19.04 by exec cmd "mkrsrc"
root@p8ct1p13:/tmp# uname -a
Linux p8ct1p13.in.ibm.com 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:50:00
UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
root@p8ct1p13:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="19.04 (Disco Dingo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Disco Dingo (development branch)"
VERSION_ID="19.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco
root@p8ct1p13:~# ctversion -bv
RSCT_Build_Name=rsholxs002a 3.2.4.2 RSCT_Build_Time=19043.16:11:49
RSCT_Build_Context=ppc64le_linux_2
root@p8ct1p13:/tmp# mkrsrc IBM.Ray Name="fvt1"
NodeNameList={"p8ct1p09.in.ibm.com"} ManualMode=0 Int32=00 String="Initial Test
String 2"
perl: mbrtowc.c:105: __mbrtowc: Assertion `__mbsinit (data.__statep)' failed.
Aborted (core dumped)
root@p8ct1p13:/tmp# file core
core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0,
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
root@p8ct1p13:/tmp# which mkrsrc
/usr/bin/mkrsrc
root@p8ct1p13:/tmp# file /usr/bin/mkrsrc
/usr/bin/mkrsrc: symbolic link to /opt/rsct/bin/mkrsrc
root@p8ct1p13:/tmp# file /opt/rsct/bin/mkrsrc
/opt/rsct/bin/mkrsrc: Perl script text executable
Contact Information = Nagendra Dontamsetty/ndont...@in.ibm.com,
Anirban/anirb...@in.ibm.com
Userspace tool common name: perl 5
The userspace tool has the following bit modes: 64bit
Userspace rpm: ii perl 5.28.1-4
ppc64el
Userspace tool obtained from project website: na
*Additional Instructions for Nagendra Dontamsetty/ndont...@in.ibm.com,
Anirban/anirb...@in.ibm.com:
-Post a private note with access information to the machine that is currently
in the debugger.
-Attach ltrace and strace of userspace application.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818953/+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 1819983] Re: package libtiffxx5 4.0.6-1ubuntu0.6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from ot
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1819983 Title: package libtiffxx5 4.0.6-1ubuntu0.6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from other instances of package libtiffxx5:i386 Status in tiff package in Ubuntu: New Bug description: installing from update manager, an apt problem? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libtiffxx5 4.0.6-1ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Mar 14 01:05:47 2019 DuplicateSignature: package:libtiffxx5:4.0.6-1ubuntu0.6 Unpacking libtiffxx5:i386 (4.0.6-1ubuntu0.6) over (4.0.6-1ubuntu0.5) ... dpkg: error processing archive /var/cache/apt/archives/libtiffxx5_4.0.6-1ubuntu0.6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from other instances of package libtiffxx5:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from other instances of package libtiffxx5:i386 InstallationDate: Installed on 2016-04-19 (1058 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: tiff Title: package libtiffxx5 4.0.6-1ubuntu0.6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from other instances of package libtiffxx5:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1819983/+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 1819983] [NEW] package libtiffxx5 4.0.6-1ubuntu0.6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from
Public bug reported: installing from update manager, an apt problem? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libtiffxx5 4.0.6-1ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Mar 14 01:05:47 2019 DuplicateSignature: package:libtiffxx5:4.0.6-1ubuntu0.6 Unpacking libtiffxx5:i386 (4.0.6-1ubuntu0.6) over (4.0.6-1ubuntu0.5) ... dpkg: error processing archive /var/cache/apt/archives/libtiffxx5_4.0.6-1ubuntu0.6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from other instances of package libtiffxx5:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from other instances of package libtiffxx5:i386 InstallationDate: Installed on 2016-04-19 (1058 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: tiff Title: package libtiffxx5 4.0.6-1ubuntu0.6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from other instances of package libtiffxx5:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tiff (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1819983 Title: package libtiffxx5 4.0.6-1ubuntu0.6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from other instances of package libtiffxx5:i386 Status in tiff package in Ubuntu: New Bug description: installing from update manager, an apt problem? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libtiffxx5 4.0.6-1ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Mar 14 01:05:47 2019 DuplicateSignature: package:libtiffxx5:4.0.6-1ubuntu0.6 Unpacking libtiffxx5:i386 (4.0.6-1ubuntu0.6) over (4.0.6-1ubuntu0.5) ... dpkg: error processing archive /var/cache/apt/archives/libtiffxx5_4.0.6-1ubuntu0.6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from other instances of package libtiffxx5:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from other instances of package libtiffxx5:i386 InstallationDate: Installed on 2016-04-19 (1058 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: tiff Title: package libtiffxx5 4.0.6-1ubuntu0.6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libtiffxx5/changelog.Debian.gz', which is different from other instances of package libtiffxx5:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1819983/+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 151062]
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * KBL: igt@perf_pmu@rc6 - fail - Failed assertion: (double)(idle - prev) = (1.0 + (tolerance)) * (double)(ts[1] - ts[0]) (double)(idle - prev) = (1.0 - (tol - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_241/fi-kbl-guc/igt@perf_...@rc6.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/151062 Title: Evince does not show certain images Status in Poppler: Fix Released Status in poppler package in Ubuntu: Fix Released Bug description: Binary package hint: evince I have some pdf that does not show some images in evince (they show correctly in kpf and acroread). ProblemType: Bug Architecture: i386 Date: Tue Oct 9 14:48:08 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/evince Package: evince 2.20.0-0ubuntu3 PackageArchitecture: i386 ProcCmdline: evince /home/miguel/Documentos/BJB/bjb\ catalogue\ 2004-2007.pdf ProcCwd: /home/miguel ProcEnviron: PATH=/home/miguel/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=es_MX.UTF-8 SHELL=/bin/bash SourcePackage: evince Uname: Linux miguel-laptop 2.6.22-14-generic #1 SMP Tue Oct 9 09:51:52 GMT 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/151062/+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 1817799] Re: [FFe] apparmor 2.13
** Description changed: FFe paperwork still in progress Feature Freeze exception for AppArmor 2.13.2 The security team is pushing to get AppArmor 2.13 into 19.04 since we want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally update to it to test the new features that are available now and make the overall experience better tested and less disruptive. The release is primarily incremental improvements in the parser, libapparmor, userspace tooling and policy improvements and Debian started preparing 2.13 in experimental last June where the first upload to unstable was made in July. Since then, Debian has worked closely with upstream and Ubuntu devs to shake out bugs and improve the packaging. There are no new mediation rules so the chance of regression in terms of parser/kernel/policy updates is considered low. IME, the primary points of interest for the FFe surround the following: - * apparmor_parser in 2.13 now creates subdirectories in /var/cache/apparmor with the subdir name based on the kernel features. This improves the experience when booting between kernels with different feature sets + * apparmor_parser in 2.13 now creates subdirectories in the cache directory with the subdir name based on the kernel features. This improves the experience when booting between kernels with different feature sets * /etc/apparmor.d/cache is moved to /var/cache/apparmor (first upload with this change in August) - * the init process now uses proper systemd unit instead of calling out to SysV init script. This an rc.apparmor.functions cleanups were done in coordination with Ubuntu devs (first upload in December) + * the init process now uses proper systemd unit instead of calling out to SysV init script. This and rc.apparmor.functions cleanups were done in coordination with Ubuntu devs (first upload in December) Debian has been very active in improving the packaging since the plan is to release with AppArmor by default in Buster. A version of 2.13.2 has been in Debian testing (Buster) since January with the 2.13.2-9 version that this FFe is based on migrating last week. Debian improved autopkgtests throughout Buster, worked with upstream and Ubuntu devs throughout. Because of the extensive baking in Debian, I think it is reasonable to consider granting the exception (indeed, part of why we missed Disco's freeze was because we were working with Debian on improving the package for Buster's freeze). While most software in Ubuntu doesn't care about the systemd or cache changes, it was known that snapd manages snap cache files on snap remove, and snapd needed to be changed to account for this[2]. This update is included in snapd 2.38 which should be uploaded to Disco very soon (I'm told this week). Because of the change in the apparmor cache, I have introduced a Breaks: snapd (<< 2.38~) in the apparmor package since snaps cannot be removed (snapd aborts the removal when the cache file is not found; which is a little strict IMO, but I digress). In terms of testing, we exercised our test plan, like normal[1]. This includes upgrade testing, verifying profile load on boot and software with apparmor integration continue to work (snapd, lxc, lxd, libvirt, docker, etc). The source tarball does not contain a changelog, instead the upstream release notes can be found here: * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.1 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.2 [1]https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [2]https://github.com/snapcore/snapd/pull/6549 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1817799 Title: [FFe] apparmor 2.13 Status in apparmor package in Ubuntu: In Progress Bug description: FFe paperwork still in progress Feature Freeze exception for AppArmor 2.13.2 The security team is pushing to get AppArmor 2.13 into 19.04 since we want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally update to it to test the new features that are available now and make the overall experience better tested and less disruptive. The release is primarily incremental improvements in the parser, libapparmor, userspace tooling and policy improvements and Debian started preparing 2.13 in experimental last June where the first upload to unstable was made in July. Since then, Debian has worked closely with upstream and Ubuntu devs to shake out bugs and improve the packaging. There are no new mediation rules so the chance of regression in terms of parser/kernel/policy updates is considered low. IME, the primary points of interest for the FFe surround the following: * apparmor_parser in 2.13 now creates
[Touch-packages] [Bug 1817799] Re: [FFe] apparmor 2.13
** Attachment added: "upgrade.log" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+attachment/5245939/+files/upgrade.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1817799 Title: [FFe] apparmor 2.13 Status in apparmor package in Ubuntu: In Progress Bug description: FFe paperwork still in progress Feature Freeze exception for AppArmor 2.13.2 The security team is pushing to get AppArmor 2.13 into 19.04 since we want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally update to it to test the new features that are available now and make the overall experience better tested and less disruptive. The release is primarily incremental improvements in the parser, libapparmor, userspace tooling and policy improvements and Debian started preparing 2.13 in experimental last June where the first upload to unstable was made in July. Since then, Debian has worked closely with upstream and Ubuntu devs to shake out bugs and improve the packaging. There are no new mediation rules so the chance of regression in terms of parser/kernel/policy updates is considered low. IME, the primary points of interest for the FFe surround the following: * apparmor_parser in 2.13 now creates subdirectories in /var/cache/apparmor with the subdir name based on the kernel features. This improves the experience when booting between kernels with different feature sets * /etc/apparmor.d/cache is moved to /var/cache/apparmor (first upload with this change in August) * the init process now uses proper systemd unit instead of calling out to SysV init script. This an rc.apparmor.functions cleanups were done in coordination with Ubuntu devs (first upload in December) Debian has been very active in improving the packaging since the plan is to release with AppArmor by default in Buster. A version of 2.13.2 has been in Debian testing (Buster) since January with the 2.13.2-9 version that this FFe is based on migrating last week. Debian improved autopkgtests throughout Buster, worked with upstream and Ubuntu devs throughout. Because of the extensive baking in Debian, I think it is reasonable to consider granting the exception (indeed, part of why we missed Disco's freeze was because we were working with Debian on improving the package for Buster's freeze). While most software in Ubuntu doesn't care about the systemd or cache changes, it was known that snapd manages snap cache files on snap remove, and snapd needed to be changed to account for this[2]. This update is included in snapd 2.38 which should be uploaded to Disco very soon (I'm told this week). Because of the change in the apparmor cache, I have introduced a Breaks: snapd (<< 2.38~) in the apparmor package since snaps cannot be removed (snapd aborts the removal when the cache file is not found; which is a little strict IMO, but I digress). In terms of testing, we exercised our test plan, like normal[1]. This includes upgrade testing, verifying profile load on boot and software with apparmor integration continue to work (snapd, lxc, lxd, libvirt, docker, etc). The source tarball does not contain a changelog, instead the upstream release notes can be found here: * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.1 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.2 [1]https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [2]https://github.com/snapcore/snapd/pull/6549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+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 1817799] Re: [FFe] apparmor 2.13
Here is the upgrade log. Note that these parser errors are unrelated to apparmor 2.13 and an issue with the snapd packaging: AppArmor parser error for /etc/apparmor.d in /etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open '/var/lib/snapd/apparmor/snap-confine' AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not open '/var/lib/snapd/apparmor/snap-confine' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1817799 Title: [FFe] apparmor 2.13 Status in apparmor package in Ubuntu: In Progress Bug description: FFe paperwork still in progress Feature Freeze exception for AppArmor 2.13.2 The security team is pushing to get AppArmor 2.13 into 19.04 since we want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally update to it to test the new features that are available now and make the overall experience better tested and less disruptive. The release is primarily incremental improvements in the parser, libapparmor, userspace tooling and policy improvements and Debian started preparing 2.13 in experimental last June where the first upload to unstable was made in July. Since then, Debian has worked closely with upstream and Ubuntu devs to shake out bugs and improve the packaging. There are no new mediation rules so the chance of regression in terms of parser/kernel/policy updates is considered low. IME, the primary points of interest for the FFe surround the following: * apparmor_parser in 2.13 now creates subdirectories in /var/cache/apparmor with the subdir name based on the kernel features. This improves the experience when booting between kernels with different feature sets * /etc/apparmor.d/cache is moved to /var/cache/apparmor (first upload with this change in August) * the init process now uses proper systemd unit instead of calling out to SysV init script. This an rc.apparmor.functions cleanups were done in coordination with Ubuntu devs (first upload in December) Debian has been very active in improving the packaging since the plan is to release with AppArmor by default in Buster. A version of 2.13.2 has been in Debian testing (Buster) since January with the 2.13.2-9 version that this FFe is based on migrating last week. Debian improved autopkgtests throughout Buster, worked with upstream and Ubuntu devs throughout. Because of the extensive baking in Debian, I think it is reasonable to consider granting the exception (indeed, part of why we missed Disco's freeze was because we were working with Debian on improving the package for Buster's freeze). While most software in Ubuntu doesn't care about the systemd or cache changes, it was known that snapd manages snap cache files on snap remove, and snapd needed to be changed to account for this[2]. This update is included in snapd 2.38 which should be uploaded to Disco very soon (I'm told this week). Because of the change in the apparmor cache, I have introduced a Breaks: snapd (<< 2.38~) in the apparmor package since snaps cannot be removed (snapd aborts the removal when the cache file is not found; which is a little strict IMO, but I digress). In terms of testing, we exercised our test plan, like normal[1]. This includes upgrade testing, verifying profile load on boot and software with apparmor integration continue to work (snapd, lxc, lxd, libvirt, docker, etc). The source tarball does not contain a changelog, instead the upstream release notes can be found here: * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.1 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.2 [1]https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [2]https://github.com/snapcore/snapd/pull/6549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+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 1817799] Re: [FFe] apparmor 2.13
Here is the sbuild build log ** Attachment added: "apparmor_2.13.2-9ubuntu1_amd64-2019-03-13T21:48:49Z.build" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+attachment/5245940/+files/apparmor_2.13.2-9ubuntu1_amd64-2019-03-13T21%3A48%3A49Z.build -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1817799 Title: [FFe] apparmor 2.13 Status in apparmor package in Ubuntu: In Progress Bug description: FFe paperwork still in progress Feature Freeze exception for AppArmor 2.13.2 The security team is pushing to get AppArmor 2.13 into 19.04 since we want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally update to it to test the new features that are available now and make the overall experience better tested and less disruptive. The release is primarily incremental improvements in the parser, libapparmor, userspace tooling and policy improvements and Debian started preparing 2.13 in experimental last June where the first upload to unstable was made in July. Since then, Debian has worked closely with upstream and Ubuntu devs to shake out bugs and improve the packaging. There are no new mediation rules so the chance of regression in terms of parser/kernel/policy updates is considered low. IME, the primary points of interest for the FFe surround the following: * apparmor_parser in 2.13 now creates subdirectories in /var/cache/apparmor with the subdir name based on the kernel features. This improves the experience when booting between kernels with different feature sets * /etc/apparmor.d/cache is moved to /var/cache/apparmor (first upload with this change in August) * the init process now uses proper systemd unit instead of calling out to SysV init script. This an rc.apparmor.functions cleanups were done in coordination with Ubuntu devs (first upload in December) Debian has been very active in improving the packaging since the plan is to release with AppArmor by default in Buster. A version of 2.13.2 has been in Debian testing (Buster) since January with the 2.13.2-9 version that this FFe is based on migrating last week. Debian improved autopkgtests throughout Buster, worked with upstream and Ubuntu devs throughout. Because of the extensive baking in Debian, I think it is reasonable to consider granting the exception (indeed, part of why we missed Disco's freeze was because we were working with Debian on improving the package for Buster's freeze). While most software in Ubuntu doesn't care about the systemd or cache changes, it was known that snapd manages snap cache files on snap remove, and snapd needed to be changed to account for this[2]. This update is included in snapd 2.38 which should be uploaded to Disco very soon (I'm told this week). Because of the change in the apparmor cache, I have introduced a Breaks: snapd (<< 2.38~) in the apparmor package since snaps cannot be removed (snapd aborts the removal when the cache file is not found; which is a little strict IMO, but I digress). In terms of testing, we exercised our test plan, like normal[1]. This includes upgrade testing, verifying profile load on boot and software with apparmor integration continue to work (snapd, lxc, lxd, libvirt, docker, etc). The source tarball does not contain a changelog, instead the upstream release notes can be found here: * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.1 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.2 [1]https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [2]https://github.com/snapcore/snapd/pull/6549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+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 1817799] Re: [FFe] apparmor 2.13
** Description changed: - TODO + FFe paperwork still in progress + + Feature Freeze exception for AppArmor 2.13.2 + + The security team is pushing to get AppArmor 2.13 into 19.04 since we + want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally + update to it to test the new features that are available now and more + the overall experience better tested and less disruptive. + + The release is primarily incremental improvements in the parser, + libapparmor, userspace tooling and policy improvements and Debian + started preparing 2.13 in experimental last June where the first upload + to unstable was made in July. Since then, Debian has worked closely with + upstream and Ubuntu devs to shake out bugs and improve the packaging. + There are no new mediation rules so the chance of regression in terms of + parser/kernel/policy updates is considered low. + + IME, the primary points of interest for the FFe surround the following: + * apparmor_parser in 2.13 now creates subdirectories in /var/cache/apparmor with the subdir name based on the kernel features. This improves the experience when booting between kernels with different feature sets + * /etc/apparmor.d/cache is moved to /var/cache/apparmor (first upload with this change in August) + * the init process now uses proper systemd unit instead of calling out to SysV init script. This an rc.apparmor.functions cleanups were done in coordination with Ubuntu devs (first upload in December) + + Debian has been very active in improving the packaging since they desire + to turn on AppArmor by default in Buster. A version of 2.13.2 has been + in Debian testing (Buster) since January with the 2.13.2-9 version that + this FFe is based on migrating last week. Debian improved autopkgtests + throughout Buster, worked with upstream and Ubuntu devs throughout. + + Because of the extensive baking in Debian, I consider granting an + Exception as possible (indeed, we were working with Debian on improving + the package for Buster's freeze which is why we missed Disco's freeze + date). + + While most software in Ubuntu don't care about the systemd or cache + changes, it was known that snapd manages snap cache files on snap + remove, and snapd needed to be changed to account for this[2] and this + is included in snapd 2.38 which should be uploaded to Disco very soon + (I'm told this week). Because the change in the apparmor cache, I have + introduced a Breaks: snapd (<< 2.38~) in the apparmor package since + snaps cannot be removed (snapd aborts the removal when the cache file is + not found; which is a little strict IMO, but I digress). + + In terms of testing, we exercised our test plan, like normal[1]. This + includes upgrade testing, verifying profile load on boot and software + with apparmor integration continue to work (lxc, lxd, libvirt, docker, + etc). + + The source tarball does not contain a changelog, instead the upstream release notes can be found here: + * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13 + * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.1 + * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.2 + + [1]https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor + [2]https://github.com/snapcore/snapd/pull/6549 ** Description changed: FFe paperwork still in progress Feature Freeze exception for AppArmor 2.13.2 The security team is pushing to get AppArmor 2.13 into 19.04 since we want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally - update to it to test the new features that are available now and more + update to it to test the new features that are available now and make the overall experience better tested and less disruptive. The release is primarily incremental improvements in the parser, libapparmor, userspace tooling and policy improvements and Debian started preparing 2.13 in experimental last June where the first upload to unstable was made in July. Since then, Debian has worked closely with upstream and Ubuntu devs to shake out bugs and improve the packaging. There are no new mediation rules so the chance of regression in terms of parser/kernel/policy updates is considered low. IME, the primary points of interest for the FFe surround the following: - * apparmor_parser in 2.13 now creates subdirectories in /var/cache/apparmor with the subdir name based on the kernel features. This improves the experience when booting between kernels with different feature sets - * /etc/apparmor.d/cache is moved to /var/cache/apparmor (first upload with this change in August) - * the init process now uses proper systemd unit instead of calling out to SysV init script. This an rc.apparmor.functions cleanups were done in coordination with Ubuntu devs (first upload in December) + * apparmor_parser in 2.13 now creates subdirectories in /var/cache/apparmor with the subdir name based on the kernel features. This improves the experience
[Touch-packages] [Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken
@ddstreet: > are you upstream nameservers not reachable from your system? upstream servers have no clue about local LXC/LXD (linuxcontainers.org) DNS names. Configuration basically done via systemd-resolve --interface lxdbr0 --set-dns 10.145.28.1 --set-domain lxd This gets broken by the update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title: Package resolvconf=1.79ubuntu10.18.04.1 broken Status in resolvconf package in Ubuntu: Confirmed Status in resolvconf source package in Bionic: Fix Committed Status in resolvconf source package in Cosmic: Fix Committed Bug description: The package resolveconf version 1.79ubuntu10.18.04.1 is broken. Installing the package breaks DNS resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.1 Uname: Linux 4.15.0-46-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1819625/+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 1819747] Re: dhclient does not work with busybox ip
This bug was fixed in the package isc-dhcp - 4.4.1-2ubuntu4 --- isc-dhcp (4.4.1-2ubuntu4) disco; urgency=medium * Write pidfile before informing parent of success. (LP: #1819747) -- Michael Hudson-Doyle Wed, 13 Mar 2019 14:26:56 +1300 ** Changed in: isc-dhcp (Ubuntu Disco) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1819747 Title: dhclient does not work with busybox ip Status in busybox package in Ubuntu: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in isc-dhcp package in Ubuntu: Fix Released Status in busybox source package in Disco: Fix Committed Status in cloud-initramfs-tools source package in Disco: Invalid Status in initramfs-tools source package in Disco: Invalid Status in isc-dhcp source package in Disco: Fix Released Bug description: After isc-dhcp update from 4.3.5 to 4.4.1, dhclient-script uses valid_lft option when adding an IPv4 address. When used on the initrd generated by initramfs-tools, this will fail because busybox ip does not support this option. This affects the use of cloud-initramfs-dyn-netconf and ip= command line option, which breaks initramfs-tools testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1819747/+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 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
The resolvconf SRU also introduces regressions (LP: #1819625) and is in the process of being reverted. ** Changed in: resolvconf (Ubuntu Bionic) Status: Fix Released => Triaged ** Changed in: resolvconf (Ubuntu Cosmic) Status: Fix Released => Triaged -- 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/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf Status in resolvconf package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in resolvconf source package in Trusty: Invalid Status in systemd source package in Trusty: Invalid Status in resolvconf source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in resolvconf source package in Bionic: Triaged Status in systemd source package in Bionic: Invalid Status in resolvconf source package in Cosmic: Triaged Status in systemd source package in Cosmic: Invalid Status in resolvconf source package in Disco: Fix Released Status in systemd source package in Disco: Invalid Bug description: [impact] systems upgraded from pre-Bionic releases to Bionic or later will continue to use ifupdown/resolvconf for network conf and management, but resolvconf has a new systemd service in Bionic and later that pulls systemd-resolved stub-resolv.conf into its local configuration. With the recent addition of edns0 option to the stub resolver conf in systemd to fix bug 1811471, this means resolvconf now sets up the /etc/resolv.conf file to include upstream servers but also use edns. For any systems where the upstream resolver(s) don't support edns, dns lookups will break. [test case] == upgrade from pre-bionic (e.g. xenial) to bionic or later == 1) create a xenial system with ifupdown/resolvconf. The ifupdown config needs to include an upstream name server (must be static). At this point, once the network is configured and up, the resolvconf should have put the upstream name server(s) and search domain into the /etc/resolv.conf. As is usual for pre-systemd releases, there should be no local dns resolver in /etc/resolv.conf (i.e. 127.0.0.53 should not be included) at this point. 2) upgrade the system to bionic (alternately it should be possible to install bionic, then remove netplan and install/configure ifupdown and resolvconf, but I have not specifically tested this). The upgrade will retain the ifupdown/resolvconf configuration, and will not change to netplan/systemd-networkd. After upgrade is finished, the /etc/resolv.conf will contain: a) the upstream name server(s) b) options edns0 c) the local stub resolver (127.0.0.53) d) search domain the fixed resolvconf will remove (b) and (c), and restore /etc/resolv.conf to what it contained in Xenial release, before the upgrade to Bionic. As mentioned, this case also should cover the situation of a native Bionic install, where netplan is removed and ifupdown/resolvconf is manually installed. == bionic or later install == with a bionic install, ifupdown is not installed, instead netplan /systemd-networkd handle networking. In this case, systemd-networkd manages the /etc/resolv.conf, and symlinks it to networkd's stub- resolv.conf which always contains only the local stub resolver (127.0.0.53) and (recently) options edns0, and local search domain. If resolvconf is installed while systemd-networkd is managing the network, then currently the resolv.conf contents will remain completely unchanged, still pointing to the local stub resolver. This resolvconf change will alter that, to revert the /etc/resolv.conf to Xenial's contents; specifically, the upstream name server(s) and search domain. It will no longer include the local stub resolver nor edns0. [regression potential] Regressions due to this change would likely be seen in dns query failures with other system configurations. Additionally, for the case where systemd-networkd is actually managing the network, this change will stop sending dns traffic to the local stub resolver, and instead send it to the upstream name server(s). This will increase outgoing dns traffic (since it's no longer cached locally), but will matches the behavior from Xenial. Additionally, resolvconf should not be needed when systemd-networkd is managing the network (and thus systemd-resolved is managing dns), and resolvconf can simply be uninstalled from the system to move back to normal use of the local stub resolver. [other info] This affects only Bionic and later; in Xenial and earlier, resolvconf does not include the 'resolvconf-pull-resolved' service to pull in the systemd-resolved stub config, which is what causes this problem. This also does not affect Debian, as it does not include the
[Touch-packages] [Bug 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken
Hello Boris, or anyone else affected, Accepted resolvconf into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/resolvconf/1.79ubuntu10.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: resolvconf (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title: Package resolvconf=1.79ubuntu10.18.04.1 broken Status in resolvconf package in Ubuntu: Confirmed Status in resolvconf source package in Bionic: Fix Committed Status in resolvconf source package in Cosmic: Fix Committed Bug description: The package resolveconf version 1.79ubuntu10.18.04.1 is broken. Installing the package breaks DNS resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.1 Uname: Linux 4.15.0-46-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1819625/+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 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken
Hello Boris, or anyone else affected, Accepted resolvconf into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/resolvconf/1.79ubuntu10.18.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: resolvconf (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title: Package resolvconf=1.79ubuntu10.18.04.1 broken Status in resolvconf package in Ubuntu: Confirmed Status in resolvconf source package in Cosmic: Fix Committed Bug description: The package resolveconf version 1.79ubuntu10.18.04.1 is broken. Installing the package breaks DNS resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.1 Uname: Linux 4.15.0-46-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1819625/+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 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken
On a desktop system continuously upgraded from pre-xenial (through non- LTS releases), I have the following before upgrade: $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 27 Mar 29 2012 /etc/resolv.conf -> /run/resolvconf/resolv.conf $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. domain $mydom search $mysearch nameserver 127.0.0.53 search $mysearch buildd enablement external internal options edns0 $ After upgrade: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. domain $mydom search $mysearch nameserver 10.172.64.1 nameserver 75.75.75.75 nameserver 75.75.76.76 search $mysearch buildd enablement external internal $ This is evidently what the SRU is intended to do, but the problem is that it regresses systems that have split DNS (e.g. my 10.172.64.1 nameserver is on a VPN, which is NOT where I want my DNS to go by default and it should NOT be treated round-robin with the other DNS servers), and have the resolvconf package installed. In practice, I noticed this problem because my VPN connection dropped but systemd-resolved + resolvconf didn't get the message, and all DNS requests were going to an unreachable DNS server. But the underlying behavior is still wrong per se, and one of the things that systemd- resolved was introduced to address. We can't trade one DNS misbehavior for another in SRU. I will be reverting this SRU. The right solution is to fix systems to that they ALWAYS point to 127.0.0.53 as their local resolver. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title: Package resolvconf=1.79ubuntu10.18.04.1 broken Status in resolvconf package in Ubuntu: Confirmed Bug description: The package resolveconf version 1.79ubuntu10.18.04.1 is broken. Installing the package breaks DNS resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.1 Uname: Linux 4.15.0-46-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1819625/+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 1818953] Re: mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by executing perl script, multiple architectures
On Sat, Mar 09, 2019 at 03:59:22PM -, bugproxy wrote:
> This perl script will cause an error on Ubuntu 19.04:
>
> # perl test.pl
> Calling mblen with str=data
> perl: mbrtowc.c:105: __mbrtowc: Assertion `__mbsinit (data.__statep)' failed.
> Aborted
I've reported this bug upstream at
https://rt.perl.org/Ticket/Display.html?id=133928
with a proposed patch.
It's also https://bugs.debian.org/924517
--
Niko Tyni nt...@debian.org
** Bug watch added: rt.perl.org/ #133928
https://rt.perl.org/Ticket/Display.html?id=133928
** Bug watch added: Debian Bug tracker #924517
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924517
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1818953
Title:
mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by
executing perl script, multiple architectures
Status in The Ubuntu-power-systems project:
Confirmed
Status in perl package in Ubuntu:
Confirmed
Bug description:
== Comment: #0 - NAGENDRA P. DONTAMSETTY - 2019-02-28
00:14:49 ==
---Problem Description---
Perl core dumping core on UBUNTU 19.04 by executing perl script
---uname output---
root@p8ct1p13:/tmp# uname -a Linux p8ct1p13.in.ibm.com 4.19.0-13-generic
#14-Ubuntu SMP Thu Feb 7 21:50:00 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = ppc64le and power8
---Debugger Data---
root@p8ct1p13:/tmp# file core
core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0,
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
---Steps to Reproduce---
Description: Perl core dumpinmg core on UBUNTU 19.04 by exec cmd "mkrsrc"
root@p8ct1p13:/tmp# uname -a
Linux p8ct1p13.in.ibm.com 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:50:00
UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
root@p8ct1p13:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="19.04 (Disco Dingo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Disco Dingo (development branch)"
VERSION_ID="19.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco
root@p8ct1p13:~# ctversion -bv
RSCT_Build_Name=rsholxs002a 3.2.4.2 RSCT_Build_Time=19043.16:11:49
RSCT_Build_Context=ppc64le_linux_2
root@p8ct1p13:/tmp# mkrsrc IBM.Ray Name="fvt1"
NodeNameList={"p8ct1p09.in.ibm.com"} ManualMode=0 Int32=00 String="Initial Test
String 2"
perl: mbrtowc.c:105: __mbrtowc: Assertion `__mbsinit (data.__statep)' failed.
Aborted (core dumped)
root@p8ct1p13:/tmp# file core
core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0,
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
root@p8ct1p13:/tmp# which mkrsrc
/usr/bin/mkrsrc
root@p8ct1p13:/tmp# file /usr/bin/mkrsrc
/usr/bin/mkrsrc: symbolic link to /opt/rsct/bin/mkrsrc
root@p8ct1p13:/tmp# file /opt/rsct/bin/mkrsrc
/opt/rsct/bin/mkrsrc: Perl script text executable
Contact Information = Nagendra Dontamsetty/ndont...@in.ibm.com,
Anirban/anirb...@in.ibm.com
Userspace tool common name: perl 5
The userspace tool has the following bit modes: 64bit
Userspace rpm: ii perl 5.28.1-4
ppc64el
Userspace tool obtained from project website: na
*Additional Instructions for Nagendra Dontamsetty/ndont...@in.ibm.com,
Anirban/anirb...@in.ibm.com:
-Post a private note with access information to the machine that is currently
in the debugger.
-Attach ltrace and strace of userspace application.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818953/+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 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken
@bruno-42 are you upstream nameservers not reachable from your system? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title: Package resolvconf=1.79ubuntu10.18.04.1 broken Status in resolvconf package in Ubuntu: Confirmed Bug description: The package resolveconf version 1.79ubuntu10.18.04.1 is broken. Installing the package breaks DNS resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.1 Uname: Linux 4.15.0-46-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1819625/+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 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title: Package resolvconf=1.79ubuntu10.18.04.1 broken Status in resolvconf package in Ubuntu: Confirmed Bug description: The package resolveconf version 1.79ubuntu10.18.04.1 is broken. Installing the package breaks DNS resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.1 Uname: Linux 4.15.0-46-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1819625/+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 1819969] [NEW] gdb-multiarch does not include RISC-V architecture
Public bug reported: This issue was recently fixed in Debian, but seems to have not been pulled into Ubuntu: https://salsa.debian.org/gdb- team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175 Description:Ubuntu Disco Dingo (development branch) Release:19.04 gdb-multiarch: Installed: 8.2.90-0ubuntu1 Candidate: 8.2.90-0ubuntu1 Version table: *** 8.2.90-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1819969 Title: gdb-multiarch does not include RISC-V architecture Status in gdb package in Ubuntu: New Bug description: This issue was recently fixed in Debian, but seems to have not been pulled into Ubuntu: https://salsa.debian.org/gdb- team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175 Description: Ubuntu Disco Dingo (development branch) Release: 19.04 gdb-multiarch: Installed: 8.2.90-0ubuntu1 Candidate: 8.2.90-0ubuntu1 Version table: *** 8.2.90-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1819969/+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 1812014] Re: keyboard not responding after suspend after some time
Hi, I have no unusual extensions installed and even though I disabled all gnom extensions the problem remained. After checking that, I did what I should have done at the beginning - I changed display driver to X.Org X Server nouveau and since then I have got no problems with the keyboard at all. So it clearly indicates that the problem is with nvidia-driver-390. As I haven't played any video games recently it doesn't' bother me, but it would be nice to have this driver working correctly. Regards Krzysztof -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1782709] Re: Updating systemd kills network on bionic
I recently installed a fresh system with 18.04 as well and have experienced this exact issue when attempting to "apt dist-upgrade" from ssh. In the two instances where systemd was being updated (a few weeks ago and today), my ssh connection was dropped and I'm unable to re- connect to the server. I started the upgrade from a screen session this time and will investigate further when I can get to the console this evening. -- 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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+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 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)
** Description changed: [Impact] On Ubuntu Core we recently hit the a race in daemon-reload and systemctl twice. This race is fixed in systemd upstream: "fix race between daemon-reload and other commands #8803". + + Note that this is a general problem in systemd with daemon-reload and + systemctl commands, we just happen to hit it more often on Ubuntu Core + but the test-case below explodes just fine on a normal Ubuntu release + like 16.04 or 18.04 (not on 18.10+ as its fixed there). [TEST CASE] To reproduce its enough to run: for i in $(seq 50); do systemctl daemon-reload & systemctl start ssh & done This will result in "systemctl start ssh" hanging in ppoll. With the patch applied the hangs go away. [REGRESSION POTENTIAL] Low, this change is already in the systemd upstream and in use cosmic and later. The upstream fix is https://github.com/systemd/systemd/pull/8803 + Full spread run with the fixed systemd in the "core" snap and a regression test: https://github.com/snapcore/snapd/pull/6595 -- 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/1819728 Title: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18) Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Bug description: [Impact] On Ubuntu Core we recently hit the a race in daemon-reload and systemctl twice. This race is fixed in systemd upstream: "fix race between daemon-reload and other commands #8803". Note that this is a general problem in systemd with daemon-reload and systemctl commands, we just happen to hit it more often on Ubuntu Core but the test-case below explodes just fine on a normal Ubuntu release like 16.04 or 18.04 (not on 18.10+ as its fixed there). [TEST CASE] To reproduce its enough to run: for i in $(seq 50); do systemctl daemon-reload & systemctl start ssh & done This will result in "systemctl start ssh" hanging in ppoll. With the patch applied the hangs go away. [REGRESSION POTENTIAL] Low, this change is already in the systemd upstream and in use cosmic and later. The upstream fix is https://github.com/systemd/systemd/pull/8803 Full spread run with the fixed systemd in the "core" snap and a regression test: https://github.com/snapcore/snapd/pull/6595 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+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 1819961] [NEW] binutils: Bug 23465 - wrongly scale non-8-bit x86 displacements
Public bug reported: Due to following bug in binutils - gnu assembler compiled code optimised for AVX512 will not work correctly. binutils: Bug 23465 - wrongly scale non-8-bit x86 displacements https://sourceware.org/bugzilla/show_bug.cgi?id=23465 it is fixed in binutils 2.31 but bug exist in 2.30 which is release used in xenial. Please consider backporting this bugfix to xenial. ** Affects: binutils (Ubuntu) Importance: Undecided Status: New -- 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/1819961 Title: binutils: Bug 23465 - wrongly scale non-8-bit x86 displacements Status in binutils package in Ubuntu: New Bug description: Due to following bug in binutils - gnu assembler compiled code optimised for AVX512 will not work correctly. binutils: Bug 23465 - wrongly scale non-8-bit x86 displacements https://sourceware.org/bugzilla/show_bug.cgi?id=23465 it is fixed in binutils 2.31 but bug exist in 2.30 which is release used in xenial. Please consider backporting this bugfix to xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1819961/+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 1742714] Re: MIR: mesa-vulkan-drivers FFE: install by default
This bug was fixed in the package xorg - 1:7.7+19ubuntu10 --- xorg (1:7.7+19ubuntu10) disco; urgency=medium * control: Add mesa-vulkan-drivers to xserver-xorg Recommends. (LP: #1742714) -- Timo Aaltonen Wed, 13 Mar 2019 13:54:57 +0200 ** Changed in: xorg (Ubuntu) Status: New => Fix Released -- 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/1742714 Title: MIR: mesa-vulkan-drivers FFE: install by default Status in mesa package in Ubuntu: New Status in vulkan-loader package in Ubuntu: Invalid Status in xorg package in Ubuntu: Fix Released Bug description: MIR mesa-vulkan-drivers: - is from mesa, which is already in main - maintained just as mesa is, by ubuntu-x-swat MIR vulkan-loader: https://bugs.launchpad.net/ubuntu/+source/vulkan-loader/+bug/1742711 FFE: - new packages in the default install (mesa-vulkan-drivers, libvulkan1) -> no chance of regressing anything -- A Vulkan related bug was filed at https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in a related note, having mesa-vulkan-drivers moved from Universe to Main and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten mature and since the OpenGL drivers are installed, it will very complimentary. Having this available will aid game developers and users who load up a Vulkan application and get errors. They may not know to enable Universe in their Software Manager and to manually install mesa- vulkan-drivers for their video card. They may just load up that Vulkan application, find out it doesn't work, and then give up on it. We cannot have that for future adoption of the API. Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV are implementing experimental support for Vulkan. For Ubuntu being a leader for the desktop and a base for GNU/Linux gaming, shouldn't it be painless for Ubuntu 18.04? Especially since it is a long term release for 5 years. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1742714/+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 1806263] Re: MariaDB 10.1 server won't start when MySQL 5.7 server has been previously installed
Thank you so much for the solution.
Xubuntu 18.04.02. In the progress to install LAMP.
Decided to switch to MariaDB after install mysql-server/client with apt.
I forgot to purge mysql before "apt install mariadb-server/client", but it
seems to be fine.
Trying to run "mysel_secure_installation" and found that the server is not up.
Hit this problem when trying to launch.
Thank you for the "apparmor_parser" solution so I don't have to reboot
the system, and I could start the server.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1806263
Title:
MariaDB 10.1 server won't start when MySQL 5.7 server has been
previously installed
Status in apparmor package in Ubuntu:
Won't Fix
Status in mariadb-10.1 package in Ubuntu:
New
Status in mysql-5.7 package in Ubuntu:
Won't Fix
Bug description:
If you purge MySQL 5.7 server, then install MariaDB 10.1, that last
won't start due to wrong AppArmor profile.
CURRENT RESULT ON mariadb-server-10.1 package installation
...
Job for mariadb.service failed because a timeout was exceeded.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
...
# LANG=C systemctl status mariadb
* mariadb.service - MariaDB 10.1.34 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor
preset: enabled)
Active: failed (Result: timeout) since Sun 2018-12-02 17:26:09 UTC; 59s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Main PID: 23245 (code=exited, status=0/SUCCESS)
Dec 02 17:24:37 bionic systemd[1]: Starting MariaDB 10.1.34 database server...
Dec 02 17:24:37 bionic mysqld[23245]: 2018-12-02 17:24:37 139820621216896
[Note] /usr/sbin/mysqld (mysqld 10.1.34-MariaDB-0ubuntu0.18.04.1) starting as
process 23245 ...
Dec 02 17:26:07 bionic systemd[1]: mariadb.service: Start operation timed
out. Terminating.
Dec 02 17:26:09 bionic systemd[1]: mariadb.service: Failed with result
'timeout'.
Dec 02 17:26:09 bionic systemd[1]: Failed to start MariaDB 10.1.34 database
server.
EXPECTED RESULT
MariaDB 10.1 server starting as expected.
HOWTO REPRODUCE
apt-get install mysql-server-5.7 mysql-client-5.7
apt-get purge mysql-server-5.7 mysql-client-5.7
apt-get install mariadb-server-10.1 mariadb-client-10.1
DISCUSSION
The mysql-server-5.7 package install an
/etc/apparmor.d/usr.sbin.mysqld APPARMOR(7) profile:
# dpkg -S /etc/apparmor.d/usr.sbin.mysqld
mysql-server-5.7: /etc/apparmor.d/usr.sbin.mysqld
When purging the mysql-server-5.7 server package get purged, the
/etc/apparmor.d/usr.sbin.mysqld profile is also removed but, it is
still loaded:
# aa-status | grep 'mysqld'
/usr/sbin/mysqld
This lead to MariaDB 1.0 server not being able to start due to MySQL
5.7 APPARMOR(7) profile that is still loaded.
Furthermore, the mariadb-server-10.1 also comes with an APPARMOR(7)
profile which as per it header comments is "intensionally empty to
disable apparmor by default for newer versions of MariaDB".
This is a big mistake as such a profile is simply wrong in regard of
APPARMOR_PARSER(8) and as such, won't be unloaded:
# apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
# aa-status | grep 'mysqld'
/usr/sbin/mysqld
while:
# echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld
# apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
Removal succeeded for "/usr/sbin/mysqld".
# aa-status | grep 'mysqld'
FIX PROPOSAL
1. When mysql-server-5.7 package is being removed/purged, the APPARMOR(7)
profile should be unloaded and removed ranther than be simply removed.
2. The profile provided by the mariadb-server-10.1 package should have
correct syntax in regard of APPARMOR_PARSER(8)
3. The mariadb-server-10.1 package postinst/postrm maintainer scripts should
handle apparmor profile (load/unload)
Env Ubuntu Bionic Beaver (18.04)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1806263/+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 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies
Tested with 1.1ubuntu1.18.04.7~16.04.2: ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: feh libid3tag0 libimlib2 libjpeg-progs libjpeg9 linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39 0 upgraded, 0 newly installed, 8 to remove and 192 not upgraded. After this operation, 2.452 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security Using (^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*) regexp to find kernel packages Using (^linux-image-4\.15\.0\-39\-generic$|^linux-headers-4\.15\.0\-39\-generic$|^linux-image-extra-4\.15\.0\-39\-generic$|^linux-modules-4\.15\.0\-39\-generic$|^linux-modules-extra-4\.15\.0\-39\-generic$|^linux-signed-image-4\.15\.0\-39\-generic$|^kfreebsd-image-4\.15\.0\-39\-generic$|^kfreebsd-headers-4\.15\.0\-39\-generic$|^gnumach-image-4\.15\.0\-39\-generic$|^.*-modules-4\.15\.0\-39\-generic$|^.*-kernel-4\.15\.0\-39\-generic$|^linux-backports-modules-.*-4\.15\.0\-39\-generic$|^linux-modules-.*-4\.15\.0\-39\-generic$|^linux-tools-4\.15\.0\-39\-generic$|^linux-cloud-tools-4\.15\.0\-39\-generic$) regexp to find running kernel packages Checking: avahi-autoipd ([, ]) Checking: avahi-daemon ([, ]) ... All upgrades installed marking linux-cloud-tools-common for removal Keeping the following auto-removable package(s) because they include linux-cloud-tools-4.15.0-39-generic which package is related to the running kernel: linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39 marking libjpeg-progs for removal marking feh for removal marking libjpeg9 for removal marking libimlib2 for removal marking linux-cloud-tools-4.15.0-39-generic for removal Keeping the following auto-removable package(s) because they include linux-cloud-tools-4.15.0-39-generic which package is related to the running kernel: linux-cloud-tools-4.15.0-39-generic marking linux-hwe-cloud-tools-4.15.0-39 for removal Keeping the following auto-removable package(s) because they include linux-cloud-tools-4.15.0-39-generic which package is related to the running kernel: linux-cloud-tools-4.15.0-39-generic linux-hwe-cloud-tools-4.15.0-39 marking libid3tag0 for removal Packages that were successfully auto-removed: Packages that are kept back: linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39 InstCount=0 DelCount=0 BrokenCount=0 ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1698159 Title: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in unattended-upgrades source package in Trusty: New Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] When running kernel version 4.4.0-78 (for example) and the unattended-upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels. The linux-cloud-tools package has the hyper-v integration services daemons in it, so it's deletion leaves some of the integration not working. Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other hyper-v users aren't caught out by this? Thanks, Ian. [Test case (apt)] Make sure that linux-cloud-tools for protected kernels are listed
[Touch-packages] [Bug 1747878] Re: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provide
I installed the "ofono" package because it wasn't installed by default on Linux Mint 19.1 XFCE. And now I don't see an error message anymore. Thanks, Daniel van Vugt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1747878 Title: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Status in pulseaudio package in Ubuntu: Won't Fix Bug description: This is logged since a while on that desktop (default ubuntu install) [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Googling about it: https://stackoverflow.com/questions/37132033/ofono-dbus-introspection-method-not-found https://github.com/pulseaudio/pulseaudio/blob/master/src/modules/bluetooth/backend-ofono.c Also note Debian has more recent version: http://metadata.ftp-master.debian.org/changelogs/main/p/pulseaudio/pulseaudio_11.1-4_changelog note: that install has no 'ofono' package installed; and sound works as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1319 F pulseaudio CurrentDesktop: GNOME Date: Wed Feb 7 10:49:34 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.00 dmi.board.name: B150M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1747878/+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 1737635] Re: Invalid UTF-8 characters in dpkg's log crash unattended-upgrade.
Tested with 1.1ubuntu1.18.04.7~16.04.2: The crash does not seem to be occurring even in different form: https://errors.ubuntu.com/?release=Ubuntu%2016.04=unattended-upgrades=year=1.1ubuntu1.18.04.7~16.04.2 ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1737635 Title: Invalid UTF-8 characters in dpkg's log crash unattended-upgrade. Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: [Impact] * Unattended-upgrades crashes at the end of its run before sending out upgrade report email when dpkg's log contains invalid UTF-8 characters. [Test Case] * Observe https://errors.ubuntu.com/problem/4617feba656f6ec216996b0f1f662ae13904b9f8 not occurring again [Regression Potential] * The fix is minimal, only replacing invalid characters with �. Regressions in u-u are unlikely but tools may break consuming unattended-upgrades output in case they can't handle the replacement marker. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/2fa32547e0d8e7186a0a805e3db6f50317c0dafa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1706, in main(options) File "/usr/bin/unattended-upgrade", line 1619, in main log_content = get_dpkg_log_content(logfile_dpkg, install_start_time) File "/usr/bin/unattended-upgrade", line 1229, in get_dpkg_log_content for line in fp.readlines(): File "/usr/lib/python3.6/codecs.py", line 321, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 7912-7913: invalid continuation byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1737635/+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 1737442] Re: /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-upgrade@1706:main:__init__:__init__:open
Tested with 1.1ubuntu1.18.04.7~16.04.2: The crash does not seem to be occurring even in different form: https://errors.ubuntu.com/?release=Ubuntu%2016.04=unattended-upgrades=year=1.1ubuntu1.18.04.7~16.04.2 ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1737442 Title: /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended- upgrade@1706:main:__init__:__init__:open Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: [Impact] * Unattended-upgrades crashes when initializing the cache preventing security updates to be applied. * The fix prints an error message then exits [Test Case] * Observe https://errors.ubuntu.com/problem/cb12eff1497c73b95a2a51f4213bc3f30f2ac4d5 not happening in fixed releases [Regression Potential] * The fix is simply catching the error and exiting, there is little room for regressions. In the worst case u-u crashes differently when printing the error. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/933de54e4841d617eb5c73ab02bb2d3be522a6ff contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1737442/+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 1737717] Re: unattended-upgrade-shutdown crashes with apt_pkg.Error: E:Syntax error /etc/apt/apt.conf:2: Extra junk at end of file
There were no relevant changes between .1 and .2 thus marking this bug as verified on Xenial again. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1737717 Title: unattended-upgrade-shutdown crashes with apt_pkg.Error: E:Syntax error /etc/apt/apt.conf:2: Extra junk at end of file Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: [Impact] * Unattended-upgrades-shutdown service fails to stop printing a crash * The fix would not warrant an SRU itself but it is part of the full backport SRU tracked in LP: #1702793. [Test Case] * Buggy version: root@x-uu-1702793:~# echo extra-junk >> /etc/apt/apt.conf.d/50unattended-upgrades root@x-uu-1702793:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2019-02-08 12:55:16 UTC; 39s ago Docs: man:unattended-upgrade(8) Tasks: 0 Memory: 0B CPU: 0 Feb 08 12:55:16 x-uu-1702793 systemd[1]: Started Unattended Upgrades Shutdown. root@x-uu-1702793:~# service unattended-upgrades stop root@x-uu-1702793:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2019-02-08 12:56:02 UTC; 2s ago Docs: man:unattended-upgrade(8) Process: 602 ExecStop=/usr/share/unattended-upgrades/unattended-upgrade-shutdown (code=exited, status=1/FAILURE) Feb 08 12:55:16 x-uu-1702793 systemd[1]: Started Unattended Upgrades Shutdown. Feb 08 12:56:02 x-uu-1702793 systemd[1]: Stopping Unattended Upgrades Shutdown... Feb 08 12:56:02 x-uu-1702793 unattended-upgrade-shutdown[602]: Traceback (most recent call last): Feb 08 12:56:02 x-uu-1702793 unattended-upgrade-shutdown[602]: File "/usr/share/unattended-upgrades/unattended-up Feb 08 12:56:02 x-uu-1702793 unattended-upgrade-shutdown[602]: apt_pkg.init_config() Feb 08 12:56:02 x-uu-1702793 unattended-upgrade-shutdown[602]: SystemError: E:Syntax error /etc/apt/apt.conf.d/50un Feb 08 12:56:02 x-uu-1702793 systemd[1]: unattended-upgrades.service: Control process exited, code=exited status=1 Feb 08 12:56:02 x-uu-1702793 systemd[1]: Stopped Unattended Upgrades Shutdown. Feb 08 12:56:02 x-uu-1702793 systemd[1]: unattended-upgrades.service: Unit entered failed state. Feb 08 12:56:02 x-uu-1702793 systemd[1]: unattended-upgrades.service: Failed with result 'exit-code'. root@x-uu-1702793:~# service unattended-upgrades start root@x-uu-1702793:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2019-02-08 12:56:28 UTC; 2s ago Docs: man:unattended-upgrade(8) Process: 602 ExecStop=/usr/share/unattended-upgrades/unattended-upgrade-shutdown (code=exited, status=1/FAILURE) * Fixed version: root@dd-uu-ref:~# echo extra-junk >> /etc/apt/apt.conf.d/50unattended-upgrades root@dd-uu-ref:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-02-08 08:59:58 UTC; 3h 42min ago Docs: man:unattended-upgrade(8) Main PID: 259 (unattended-upgr) Tasks: 2 (limit: 4915) Memory: 12.4M CGroup: /system.slice/unattended-upgrades.service └─259 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal Feb 08 08:59:58 dd-uu-ref systemd[1]: Started Unattended Upgrades Shutdown. root@dd-uu-ref:~# service unattended-upgrades stop root@dd-uu-ref:~# cat /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2019-02-07 16:08:14,675 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgrades only if it is running root@dd-uu-ref:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: inactive (dead) since Fri 2019-02-08 12:50:35 UTC; 7min ago Docs: man:unattended-upgrade(8) Process: 760 ExecStart=/usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
[Touch-packages] [Bug 1719630] Re: unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial: root@x-uu-lp-1260041:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==--=== ii unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all automatic installation of security upgrades root@x-uu-lp-1260041:~# grep dpkg-dev /var/lib/dpkg/info/unattended-upgrades.* ; echo $? 1 root@x-uu-lp-1260041:~# ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1719630 Title: unattended-upgrades uses dpkg-vendor but doesn't depend on dpkg-dev Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Artful: Fix Released Bug description: [Impact] * Unattended-upgrades may fail to install due to missing dpkg-vendor command. * The fix is using lsb_release which is provided by dependencies. [Test Case] * Install unattended-upgrades, then check the maintainer scripts to not have reference to dpkg-dev: $ grep dpkg-dev /var/lib/dpkg/info/unattended-upgrades.* ; echo $? 1 [Regression Potential] * lsb_release may fail but that would be a different, bigger issue affecting many other programs. This is unlikely. * Changed maintainer scripts may fail due to errors introduced with the fix. Since those scripts had extensive testing in later releases by now it looks like unlikely to occur, too. [Original Bug Text] in its postinst script unattended-upgrade uses dpkg-vendor from dpkg- dev but does not depends on dpkg-dev which results in the following error: # apt-get update && apt-get upgrade Installing the packages goes well, except for, getting this warning. Setting up unattended-upgrades (0.97ubuntu1) ... /var/lib/dpkg/info/unattended-upgrades.postinst: 65: /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found /var/lib/dpkg/info/unattended-upgrades.postinst: 66: /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found /var/lib/dpkg/info/unattended-upgrades.postinst: 124: /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found /var/lib/dpkg/info/unattended-upgrades.postinst: 125: /var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: unattended-upgrades 0.97ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 26 10:01:05 2017 InstallationDate: Installed on 2013-09-03 (1483 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified] mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2017-09-05T01:34:04.573213 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1719630/+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 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial: root@x-uu-lp-1260041:~# apt-mark auto linux-image-extra-4.8.0-56-generic linux-image-extra-4.8.0-58-generic linux-image-extra-4.8.0-54-generic linux-image-extra-4.8.0-53-generic linux-image-extra-4.8.0-56-generic set to automatically installed. linux-image-extra-4.8.0-58-generic set to automatically installed. linux-image-extra-4.8.0-54-generic set to automatically installed. linux-image-extra-4.8.0-53-generic set to automatically installed. root@x-uu-lp-1260041:~# unattended-upgrade --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates Removing unused kernel packages: linux-image-extra-4.8.0-54-generic linux-image-4.8.0-54-generic Keeping auto-removable linux-image-extra-4.8.0-54-generic package(s) because it would also remove the following packages which should be kept in this step: libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev (Reading database ... 53554 files and directories currently installed.) Removing linux-image-extra-4.8.0-54-generic (4.8.0-54.57~16.04.1) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic update-initramfs: Generating /boot/initrd.img-4.8.0-54-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic Removing linux-image-4.8.0-54-generic (4.8.0-54.57~16.04.1) ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic update-initramfs: Deleting /boot/initrd.img-4.8.0-54-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic Packages that were successfully auto-removed: linux-image-4.8.0-54-generic linux-image-extra-4.8.0-54-generic Packages that are kept back: linux-image-extra-4.8.0-54-generic Packages that will be upgraded: libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../systemd-sysv_229-4ubuntu21.17_amd64.deb ... Unpacking systemd-sysv (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd-sysv (229-4ubuntu21.17) ... Log ended: 2019-03-13 17:17:36 Log started: 2019-03-13 17:17:36 (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../udev_229-4ubuntu21.17_amd64.deb ... Unpacking udev (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Preparing to unpack .../libudev1_229-4ubuntu21.17_amd64.deb ... Unpacking libudev1:amd64 (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for systemd (229-4ubuntu21.16) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... Setting up libudev1:amd64 (229-4ubuntu21.17) ... Setting up udev (229-4ubuntu21.17) ... addgroup: The group `input' already exists as a system group. Exiting. update-initramfs: deferring update (trigger activated) Processing triggers for libc-bin (2.23-0ubuntu11) ... Processing triggers for initramfs-tools (0.122ubuntu8.14) ... update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Log ended: 2019-03-13 17:17:44 Log started: 2019-03-13 17:17:45 (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../libpam-systemd_229-4ubuntu21.17_amd64.deb ... Unpacking libpam-systemd:amd64 (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Preparing to unpack .../libsystemd0_229-4ubuntu21.17_amd64.deb ... Unpacking libsystemd0:amd64 (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... Setting up libsystemd0:amd64 (229-4ubuntu21.17) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu21.17_amd64.deb ... Unpacking systemd (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up systemd (229-4ubuntu21.17) ... addgroup: The
[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial: root@x-uu-lp-1260041:~# apt-mark auto linux-image-extra-4.8.0-56-generic linux-image-extra-4.8.0-58-generic linux-image-extra-4.8.0-54-generic linux-image-extra-4.8.0-53-generic linux-image-extra-4.8.0-56-generic set to automatically installed. linux-image-extra-4.8.0-58-generic set to automatically installed. linux-image-extra-4.8.0-54-generic set to automatically installed. linux-image-extra-4.8.0-53-generic set to automatically installed. root@x-uu-lp-1260041:~# unattended-upgrade --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates Removing unused kernel packages: linux-image-extra-4.8.0-54-generic linux-image-4.8.0-54-generic Keeping auto-removable linux-image-extra-4.8.0-54-generic package(s) because it would also remove the following packages which should be kept in this step: libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev (Reading database ... 53554 files and directories currently installed.) Removing linux-image-extra-4.8.0-54-generic (4.8.0-54.57~16.04.1) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic update-initramfs: Generating /boot/initrd.img-4.8.0-54-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic Removing linux-image-4.8.0-54-generic (4.8.0-54.57~16.04.1) ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic update-initramfs: Deleting /boot/initrd.img-4.8.0-54-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic Packages that were successfully auto-removed: linux-image-4.8.0-54-generic linux-image-extra-4.8.0-54-generic Packages that are kept back: linux-image-extra-4.8.0-54-generic Packages that will be upgraded: libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../systemd-sysv_229-4ubuntu21.17_amd64.deb ... Unpacking systemd-sysv (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd-sysv (229-4ubuntu21.17) ... Log ended: 2019-03-13 17:17:36 Log started: 2019-03-13 17:17:36 (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../udev_229-4ubuntu21.17_amd64.deb ... Unpacking udev (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Preparing to unpack .../libudev1_229-4ubuntu21.17_amd64.deb ... Unpacking libudev1:amd64 (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for systemd (229-4ubuntu21.16) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... Setting up libudev1:amd64 (229-4ubuntu21.17) ... Setting up udev (229-4ubuntu21.17) ... addgroup: The group `input' already exists as a system group. Exiting. update-initramfs: deferring update (trigger activated) Processing triggers for libc-bin (2.23-0ubuntu11) ... Processing triggers for initramfs-tools (0.122ubuntu8.14) ... update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Log ended: 2019-03-13 17:17:44 Log started: 2019-03-13 17:17:45 (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../libpam-systemd_229-4ubuntu21.17_amd64.deb ... Unpacking libpam-systemd:amd64 (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Preparing to unpack .../libsystemd0_229-4ubuntu21.17_amd64.deb ... Unpacking libsystemd0:amd64 (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... Setting up libsystemd0:amd64 (229-4ubuntu21.17) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu21.17_amd64.deb ... Unpacking systemd (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up systemd (229-4ubuntu21.17) ... addgroup: The
[Touch-packages] [Bug 1680599] Re: unattended-upgrades crashes without writing to the log on invalid config file entries
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial: root@x-uu-lp-1260041:~# unattended-upgrade --dry-run --debug Unable to parse Unattended-Upgrade::Allowed-Origins. Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1565, in main allowed_origins = get_allowed_origins() File "/usr/bin/unattended-upgrade", line 475, in get_allowed_origins allowed_origins = get_allowed_origins_legacy() File "/usr/bin/unattended-upgrade", line 454, in get_allowed_origins_legacy (distro_id, distro_codename) = s.split() ValueError: not enough values to unpack (expected 2, got 1) root@x-uu-lp-1260041:~# cat /var/log/unattended-upgrades/unattended-upgrades.log 2019-03-13 17:23:53,035 ERROR Unable to parse Unattended-Upgrade::Allowed-Origins. root@x-uu-lp-1260041:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==--=== ii unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all automatic installation of security upgrades ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1680599 Title: unattended-upgrades crashes without writing to the log on invalid config file entries Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: If Unattended-Upgrade::Allowed-Origins in 50unattended-upgrades contains an invalid entry, such as "invalid", unattended-upgrades crashes without writing to /var/log/unattended-upgrades/unattended- upgrades.log. # unattended-upgrades --debug Traceback (most recent call last): File "/usr/bin/unattended-upgrades", line 1536, in main(options) File "/usr/bin/unattended-upgrades", line 1202, in main allowed_origins = get_allowed_origins() File "/usr/bin/unattended-upgrades", line 343, in get_allowed_origins allowed_origins = get_allowed_origins_legacy() File "/usr/bin/unattended-upgrades", line 328, in get_allowed_origins_legacy (distro_id, distro_codename) = s.split() ValueError: not enough values to unpack (expected 2, got 1) 0.92ubuntu1.2 on 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1680599/+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 1190344] Re: Daemon end of session/greeter pipes not closed
Still seeing this issue with package and tracking FIFO on log in log out
lightdm.x86_64 1.25.0-1.el7
lightdm-gobject.x86_64 1.25.0-1.el7
lightdm-gtk.x86_64 1.8.5-19.el7
lightdm-gtk-common.noarch 1.8.5-19.el7
[root@caeusadm tmp]# lightdm -v
lightdm 1.25.0
[root@caeusadm tmp]# lsof -p 13696 | grep FIFO | wc -l
188
[root@caeusadm tmp]# lsof -p 13696 | grep FIFO | wc -l
190
Increments by 2 for every log in log out and never frees them up.
When it passes open file limit (currently 1024) lightdm crashes and all
users lose session.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1190344
Title:
Daemon end of session/greeter pipes not closed
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Precise:
Fix Released
Status in lightdm source package in Trusty:
Fix Released
Status in lightdm source package in Utopic:
Fix Released
Status in lightdm source package in Vivid:
Fix Released
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes and greeters. This means each session/greeter that is
created leaks two file descriptors eventually leading to the system stopping it
from creating new pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+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 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Committed Status in qtbase-opensource-src source package in Cosmic: Fix Committed Bug description: [Impact] All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. [Test Case] 1) Install a printer that can duplex and configure it to do duplex with long-edge binding from the printer setup dialog. 2) Open a PDF with okular, and open the print dialog. Select the printer above. 3) Press the "Options" button to enlarge the dialog to also present the options. Select the "options" tab, right of "copies". Verify that Duplex Printing is preset to "None" This is wrong, because the printer was configured to do duplex with long-edge binding. 4) Print and close okular. 5) Reopen okular (with the same or another PDF file). Open again the print dialog and select the same printer. 6) Redo 3). Again see that Duplex Printing is preset to "None", instead of being at the default or at the previously used setup. [Regression Potential] The proposed patch only changes the default settings. The regression potential may be that the values are wrong, although they are already wrong. In case there is some bug it may lead to crashes. But this code is in the latest stable Qt release and I am not aware of any such crashes reported. [Other Info] The proposed patch is a backport of the following upstream commits: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e [Original Description] See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1599646] Re: E-mail report contains repeated "Reading database ... NN%" lines
Verified with unattended-upgrades/1.1ubuntu1.18.04.7~16.04.2 on Xenial: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/amd64/u/unattended- upgrades/20190228_150449_11313@/log.gz ... Packages with upgradable origin but kept back: isc-dhcp-client isc-dhcp-common Packages that were auto-removed: libmircommon5 Package installation log: Log started: 2019-02-28 14:34:48 Preparing to unpack .../distro-info-data_0.28ubuntu0.9_all.deb ... Unpacking distro-info-data (0.28ubuntu0.9) over (0.28) ... Setting up distro-info-data (0.28ubuntu0.9) ... Log ended: 2019-02-28 14:34:48 Log started: 2019-02-28 14:34:49 Preparing to unpack .../procps_2%3a3.3.10-4ubuntu2.4_amd64.deb ... Running in chroot, ignoring request. Unpacking procps (2:3.3.10-4ubuntu2.4) over (2:3.3.10-4ubuntu2) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu4) ... Setting up procps (2:3.3.10-4ubuntu2.4) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Log ended: 2019-02-28 14:34:50 ... ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1599646 Title: E-mail report contains repeated "Reading database ... NN%" lines Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Released Status in apt package in Debian: New Bug description: [Impact] * Unattended-upgrades sends the following repeating dpkg progress lines with almost no informational value in the email report: ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 60486 files and directories currently installed.) ... * This makes the report email too verbose and makes harder to spot real problems. [Test Case] * Run package autopkgtest and observe no such lines in the echoed email in upgrade-all-security and upgrade-between-snapshots tests. [Regression Potential] * The fix filters dpkg's output only and in the worst case other lines could be missing or u-u could crash. Since the applied hard- coded regex pattern is fairly simple and we observed no crashes in the tests those regressions are unlikey to occur. [Originial Bug Text] This concerns unattended-upgrades 0.90 in Xenial. Here is an excerpt from an e-mail report sent out by u-u after the upgrade process is completed: Package installation log: Log started: 2016-07-06 17:24:21 Preconfiguring packages ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 314949 files and directories currently installed.) Preparing to unpack .../tzdata_2016f-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2016f-0ubuntu0.16.04) over (2016d-0ubuntu0.16.04) ... Preparing to unpack .../libgimp2.0_2.8.16-1ubuntu1.1_i386.deb ... All but the last "Reading database ..." line should be elided from the message. As a matter of fact, those lines do not appear in messages mailed out from current Trusty systems (u-u version 0.82.1ubuntu2.4), so this appears to be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1599646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1602536] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
*** This bug is a duplicate of bug 1260041 ***
https://bugs.launchpad.net/bugs/1260041
** This bug has been marked a duplicate of bug 1260041
Unattended-Upgrades crashes with a dpkg error
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1602536
Title:
/usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin
/unattended-
upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
Status in python-apt package in Ubuntu:
Fix Committed
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in python-apt source package in Xenial:
New
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
New
Status in unattended-upgrades source package in Bionic:
Fix Released
Bug description:
[Impact]
* Unattended-upgrades fails to autoremove packages after installing
updates or fails to install updates due to a parallel process
acquiring apt or dpkg lock while u-u is running.
[Test Case]
* Set up a system with packages (> 30) to be upgraded. In case of
Bionic -security has a low number of updates, thus set up the system
to install -updates to have more packages for u-u to upgrade:
echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51-updates
* Set up two shells to run commands in parallel
* In shell "A" run sudo apt update && sudo unattended-upgrade --dry-run
--verbose --debug
* After u-u started run the following command in shell "B":
while sleep 1; do python3 -c 'import apt; import apt_pkg;
print(apt_pkg.pkgsystem_lock())' ; done
* Observe the following exception repeated while running u-u and True being
printed after u-u is finished:
...
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
True
Traceback (most recent call last):
File "", line 1, in
apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable), E:Unable to lock the administration directory
(/var/lib/dpkg/), is another process using it?
True
True
True
True
...
[Regression Potential WIP]
* Unattended-upgrade may crash
[Other Info]
It looks like python-apt also releases the lock sometimes unexpectedly
thus the both packages need to be fixed to avoid loosing the lock.
[Original Bug Text]
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unattended-upgrades. This problem was most recently seen
with version 0.90, the problem page at
https://errors.ubuntu.com/problem/19f99745d7dce5aea118eb31bfffcbdcdf238c4f
contains more details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1602536/+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 1771300] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1927:main:do_auto_remove:cache_commit:commit:_fetch_archives
*** This bug is a duplicate of bug 1260041 *** https://bugs.launchpad.net/bugs/1260041 ** This bug is no longer a duplicate of bug 1602536 /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives ** This bug has been marked a duplicate of bug 1260041 Unattended-Upgrades crashes with a dpkg error -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1771300 Title: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin /unattended- upgrade@1927:main:do_auto_remove:cache_commit:commit:_fetch_archives Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1, the problem page at https://errors.ubuntu.com/problem/33db55f3a084a7957ca1ec76f7ac2870614f17fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1771300/+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 1458204] Re: removing kernels should not require a restart afterward
Tested 1.1ubuntu1.18.04.7~16.04.2 on Xenial. root@x-uu-lp-1260041:~# yes no |apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-image-4.8.0-53-generic linux-image-extra-4.8.0-53-generic 0 upgraded, 0 newly installed, 2 to remove and 10 not upgraded. After this operation, 234 MB disk space will be freed. Do you want to continue? [Y/n] Abort. root@x-uu-lp-1260041:~# ls /var/run/reboot* ls: cannot access '/var/run/reboot*': No such file or directory root@x-uu-lp-1260041:~# apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-image-4.8.0-53-generic linux-image-extra-4.8.0-53-generic 0 upgraded, 0 newly installed, 2 to remove and 10 not upgraded. After this operation, 234 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 53554 files and directories currently installed.) Removing linux-image-extra-4.8.0-53-generic (4.8.0-53.56~16.04.1) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.8.0-53-generic /boot/vmlinuz-4.8.0-53-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.8.0-53-generic /boot/vmlinuz-4.8.0-53-generic update-initramfs: Generating /boot/initrd.img-4.8.0-53-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.8.0-53-generic /boot/vmlinuz-4.8.0-53-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.8.0-53-generic /boot/vmlinuz-4.8.0-53-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.8.0-53-generic /boot/vmlinuz-4.8.0-53-generic Removing linux-image-4.8.0-53-generic (4.8.0-53.56~16.04.1) ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.8.0-53-generic /boot/vmlinuz-4.8.0-53-generic update-initramfs: Deleting /boot/initrd.img-4.8.0-53-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.8.0-53-generic /boot/vmlinuz-4.8.0-53-generic root@x-uu-lp-1260041:~# ls /var/run/reboot* ls: cannot access '/var/run/reboot*': No such file or directory root@x-uu-lp-1260041:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==--=== ii unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all automatic installation of security upgrades ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat
[Touch-packages] [Bug 1577215] Re: Origin pattern is unexpected on dpkg-reconfigure
Verified with 1.1ubuntu1.18.04.7~16.04.2 on Xenial.
root@x-uu-lp-1260041:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all automatic
installation of security upgrades
root@x-uu-lp-1260041:~# dpkg-reconfigure unattended-upgrades
root@x-uu-lp-1260041:~# env DEBIAN_FRONTEND=readline dpkg-reconfigure
unattended-upgrades
Configuring unattended-upgrades
---
Applying updates on a frequent basis is an important part of keeping systems
secure. By default, updates need to be applied manually using package
management tools.
Alternatively, you can choose to have this system automatically download and
install important updates.
Automatically download and install stable updates? [yes/no] yes
root@x-uu-lp-1260041:~#
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1577215
Title:
Origin pattern is unexpected on dpkg-reconfigure
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Bug description:
In testing out the new unattended-upgrades behaviour I was asked an
unexpected question about the "unattended-upgrades Origin-Pattern".
This is not a great experience, it doesn't match anything other than
internal code patterns.
For example, the default offered does NOT look like a sensible Ubuntu
default for Ubuntu users:
"origin=Debian,codename=${distro_codename},label=Debian-
Security";___
Is that correct, or a mistake?
What I would expect is simply this:
Install security updates (Y/N)
Install performance and reliability updates (Y/N)
Install updates from unofficial archives (Y/N)
The latter would map to all PPAs etc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1577215/+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 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Ext4... the last two messages in that thread direct me to open a new bug, so I have. -- 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/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+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 1458204] Re: removing kernels should not require a restart afterward
@bhkolts: Yes, not sending an email when only kernel autoremovals took place is a regression - or an incomplete part of the kernel autoremoval. It is fixed in 19.04, but the fix is somewhat intrusive thus it may not be back-ported. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1458204/+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 1260041] Re: Unattended-Upgrades crashes with a dpkg error
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial: root@x-uu-lp-1260041:~# unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates Using (^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*) regexp to find kernel packages Using (^linux-image-4\.18\.0\-16\-generic$|^linux-headers-4\.18\.0\-16\-generic$|^linux-image-extra-4\.18\.0\-16\-generic$|^linux-modules-4\.18\.0\-16\-generic$|^linux-modules-extra-4\.18\.0\-16\-generic$|^linux-signed-image-4\.18\.0\-16\-generic$|^kfreebsd-image-4\.18\.0\-16\-generic$|^kfreebsd-headers-4\.18\.0\-16\-generic$|^gnumach-image-4\.18\.0\-16\-generic$|^.*-modules-4\.18\.0\-16\-generic$|^.*-kernel-4\.18\.0\-16\-generic$|^linux-backports-modules-.*-4\.18\.0\-16\-generic$|^linux-modules-.*-4\.18\.0\-16\-generic$|^linux-tools-4\.18\.0\-16\-generic$|^linux-cloud-tools-4\.18\.0\-16\-generic$) regexp to find running kernel packages Checking: cloud-init ([]) adjusting candidate version: cloud-init=18.5-21-g8ee294d5-0ubuntu1~16.04.1 Checking: distro-info-data ([]) pkg distro-info-data not in allowed origin sanity check failed Checking: libpam-systemd ([]) Checking: libsystemd0 ([]) Checking: libudev1 ([]) Checking: snapd ([]) adjusting candidate version: snapd=2.34.2ubuntu0.1 Checking: systemd ([]) Checking: systemd-sysv ([]) Checking: ubuntu-core-launcher ([]) adjusting candidate version: ubuntu-core-launcher=2.34.2ubuntu0.1 Checking: udev ([]) pkgs that look like they should be upgraded: libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd-sysv_229-4ubuntu21.17_amd64.deb' ID:0 ErrorText: ''> check_conffile_prompt(/var/cache/apt/archives/systemd-sysv_229-4ubuntu21.17_amd64.deb) found pkg: systemd-sysv No conffiles in deb /var/cache/apt/archives/systemd-sysv_229-4ubuntu21.17_amd64.deb (There is no member named 'conffiles') http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/libpam-systemd_229-4ubuntu21.17_amd64.deb' ID:0 ErrorText: ''> check_conffile_prompt(/var/cache/apt/archives/libpam-systemd_229-4ubuntu21.17_amd64.deb) found pkg: libpam-systemd No conffiles in deb /var/cache/apt/archives/libpam-systemd_229-4ubuntu21.17_amd64.deb (There is no member named 'conffiles') http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/libsystemd0_229-4ubuntu21.17_amd64.deb' ID:0 ErrorText: ''> check_conffile_prompt(/var/cache/apt/archives/libsystemd0_229-4ubuntu21.17_amd64.deb) found pkg: libsystemd0 No conffiles in deb /var/cache/apt/archives/libsystemd0_229-4ubuntu21.17_amd64.deb (There is no member named 'conffiles') http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd_229-4ubuntu21.17_amd64.deb' ID:0 ErrorText: ''> check_conffile_prompt(/var/cache/apt/archives/systemd_229-4ubuntu21.17_amd64.deb) found pkg: systemd conffile line: /etc/dbus-1/system.d/org.freedesktop.hostname1.conf f55c94d000b5d62b5f06d38852977dd1 current md5: f55c94d000b5d62b5f06d38852977dd1 conffile line: /etc/dbus-1/system.d/org.freedesktop.locale1.conf 5893ab03e7e96aa3759baceb4dd04190 current md5: 5893ab03e7e96aa3759baceb4dd04190 conffile line: /etc/dbus-1/system.d/org.freedesktop.login1.conf 4aac4fe1a99c9fca83c85b80e4e0c2ba current md5: 4aac4fe1a99c9fca83c85b80e4e0c2ba conffile line: /etc/dbus-1/system.d/org.freedesktop.network1.conf 162e9a90d8f824f79ef2c6390827ec7b current md5: 162e9a90d8f824f79ef2c6390827ec7b conffile line: /etc/dbus-1/system.d/org.freedesktop.resolve1.conf 6969148b4616c56a5c9065cec5ab0775 current md5: 6969148b4616c56a5c9065cec5ab0775 conffile line: /etc/dbus-1/system.d/org.freedesktop.systemd1.conf 846824928e39a465c06c3aae53510535 current md5: 846824928e39a465c06c3aae53510535 conffile line: /etc/dbus-1/system.d/org.freedesktop.timedate1.conf 682369fbf3de26b21e775732c89a2bbe current md5: 682369fbf3de26b21e775732c89a2bbe conffile line: /etc/dhcp/dhclient-exit-hooks.d/timesyncd a891f21f45b0648b7082d999bf424591 current md5: a891f21f45b0648b7082d999bf424591 conffile line: /etc/pam.d/systemd-user 3bdb96b18046bd209135cdfe73421db6 current md5: 3bdb96b18046bd209135cdfe73421db6 conffile line: /etc/systemd/bootchart.conf
[Touch-packages] [Bug 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)
I uploaded both the xenial and bionic version to -proposed 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/1819728 Title: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18) Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Bug description: [Impact] On Ubuntu Core we recently hit the a race in daemon-reload and systemctl twice. This race is fixed in systemd upstream: "fix race between daemon-reload and other commands #8803". [TEST CASE] To reproduce its enough to run: for i in $(seq 50); do systemctl daemon-reload & systemctl start ssh & done This will result in "systemctl start ssh" hanging in ppoll. With the patch applied the hangs go away. [REGRESSION POTENTIAL] Low, this change is already in the systemd upstream and in use cosmic and later. The upstream fix is https://github.com/systemd/systemd/pull/8803 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+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 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)
The version for xenial link in comment #9 did successfully run a full spread run with UC16. This includes the regression test that systemctl start is not hanging. -- 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/1819728 Title: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18) Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Bug description: [Impact] On Ubuntu Core we recently hit the a race in daemon-reload and systemctl twice. This race is fixed in systemd upstream: "fix race between daemon-reload and other commands #8803". [TEST CASE] To reproduce its enough to run: for i in $(seq 50); do systemctl daemon-reload & systemctl start ssh & done This will result in "systemctl start ssh" hanging in ppoll. With the patch applied the hangs go away. [REGRESSION POTENTIAL] Low, this change is already in the systemd upstream and in use cosmic and later. The upstream fix is https://github.com/systemd/systemd/pull/8803 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+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 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Thank you for your bug report, what filesystem do you use? There are similar warnings in bug #1804603 -- 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/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+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 1819189] Re: gtk_label_set_attributes core dump
Thank you for your bug report. Do you have a code example trigger the problem?
Also that should be reported upstream rather, can you send it to
https://gitlab.gnome.org/GNOME/gtk/issues ?
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Low
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1819189
Title:
gtk_label_set_attributes core dump
Status in gtk+3.0 package in Ubuntu:
Invalid
Bug description:
Program terminated with signal SIGSEGV, Segmentation fault.
in gtk_label_set_attributes () from libgtk-3.so.0
gtk/gtklabel.c
void
gtk_label_set_attributes (GtkLabel *label,
PangoAttrList*attrs)
{
GtkLabelPrivate *priv = label->priv;
g_return_if_fail (GTK_IS_LABEL (label));
to
void
gtk_label_set_attributes (GtkLabel *label,
PangoAttrList*attrs)
{
GtkLabelPrivate *priv;
g_return_if_fail (GTK_IS_LABEL (label));
priv = label->priv;
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1819189/+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 1818516] Re: FFe: Mesa 19.0.x for disco
tested the ppa version (19.0 rc7) on AMD Ryzen / Vega Mobile now, works fine (desktop, glxgears, vkcube) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1818516 Title: FFe: Mesa 19.0.x for disco Status in mesa package in Ubuntu: New Bug description: Mesa 19.0.0 will be soon released, and we should get that for disco, and then follow point-releases until the last one is released (roughly next July, will need an SRU). We'll also migrate it to use LLVM 8. New features according to upstream release notes: GL_AMD_texture_texture4 on all GL 4.0 drivers. GL_EXT_shader_implicit_conversions on all drivers (ES extension). GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension). GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension). GL_EXT_render_snorm on gallium drivers (ES extension). GL_EXT_texture_view on drivers supporting texture views (ES extension). GL_OES_texture_view on drivers supporting texture views (ES extension). GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only). Shader-based software implementations of GL_ARB_gpu_shader_fp64, GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot on i965. VK_ANDROID_external_memory_android_hardware_buffer on Intel Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV VK_EXT_scalar_block_layout on Intel and RADV VK_KHR_depth_stencil_resolve on Intel VK_KHR_draw_indirect_count on Intel VK_EXT_conditional_rendering on Intel VK_EXT_memory_budget on RADV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+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 1396787] Re: checking trust of archives eats a lot of cpu
Verified with 1.1ubuntu1.18.04.7~16.04.2, measured times are similar to .1, verified previously. https://objectstorage.prodstack4-5.canonical.com /v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/u/unattended-upgrades/20190228_150449_11313@/log.gz ... Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial Packages that will be upgraded: 4.62user 0.16system 0:04.83elapsed 99%CPU (0avgtext+0avgdata 78264maxresident)k 0inputs+124024outputs (0major+38540minor)pagefaults 0swaps new packages marked as manually installed (should be none) ... ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1396787 Title: checking trust of archives eats a lot of cpu Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] * Unattended-upgrades consumes tens of seconds or even minutes of CPU time to verify the origin of the packages * Using excessive amount of CPU is unpleasant for desktop/laptop users and also wastes computation time on servers/cloud instances. * Unattended-upgrades' algorithm for checking and adjusting package origins is redesigned to visit and adjust less packages. [Test Case] * The added upgrade-all-security autopkgtest measure the time u-u needs for upgrading security updates on the tested release starting with no security updates applied to the point where all security updates are applied but all packages are left upgradable from -updates. The test also measures the time needed for --dry-run to find no updates to be installed unattended. * Please run autopkgtests and look for the to time results: ... All upgrades installed 44.41user 3.06system 0:48.35elapsed 98%CPU (0avgtext+0avgdata 164872maxresident)k 208inputs+192376outputs (0major+642657minor)pagefaults 0swaps ... No packages found that can be upgraded unattended and no pending auto-removals 2.83user 0.11system 0:02.98elapsed 98%CPU (0avgtext+0avgdata 79308maxresident)k [Regression Potential] * Due to algorithm redesign there is a risk that packages from allowed origins are not upgraded. There were unit tests for testing the selection of the right packages to upgrade already, but a new autopkgtest is also introduce to verify u-u's behavior on current real-life security-updates. [Original bug text] (System: Ubuntu 14.04, up to date packages) I noticed that unattended-upgrades spends a significant amount of time in phases where it runs at 100% cpu. On a slower machine (core 2 t7200 2GHz) this goes on for minutes rather than seconds. This interferes with using the machine for other tasks. Using the --debug option to unattended-upgrades shows that the program outputs a lot of lines like the following during these 100% cpu phases: matching 'a'='trusty-updates' against ' From this output I guess the operation executed is not so complicated that it should require so much cpu power. ?? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Nov 26 21:53:57 2014 InstallationDate: Installed on 2014-08-28 (90 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1396787/+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
** Also affects: systemd (Ubuntu Disco) Importance: Low Status: In Progress ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => Confirmed ** Changed in: systemd (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: systemd (Ubuntu Disco) Status: In Progress => 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/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Bionic: Confirmed 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? [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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
Exactly. I did the "verification-done-bionic" step for 18.2.2 in comment #12 above; and unfortunately I don't have an affected school nearby, where I could test 18.2.8 in cosmic, and installing cosmic in a remote school would be hard. Thanks a lot Timo! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Bump. -- 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/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+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 1815089] Re: 100% CPU / usr / lib / tracker / tracker-extract
The / usr / lib / tracker / tracker-extract is using almost 100% CPU resources see attached image ** Attachment added: "100% de recursos da CPU" https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1815089/+attachment/5245857/+files/Captura%20de%20tela%20de%202019-03-13%2011-16-25.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1815089 Title: 100% CPU / usr / lib / tracker / tracker-extract Status in tracker package in Ubuntu: Incomplete Bug description: The / usr / lib / tracker / tracker-extract is using almost 100% CPU resources see attached image After updates on today's date 07/02/2019 has improved the crashes, but the hunger for CPU continues. ** O /usr/lib/tracker/tracker-extract está usando quase 100% de recursos da CPU vide imagem em anexo Após atualizações na data de hoje 07/02/2019 melhorou os travamentos, mas a fome por CPU continua. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1815089/+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 1230246] Re: Add Auto-Submitted header to email report
Tested with 1.1ubuntu1.18.04.7~16.04.2: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/amd64/u/unattended- upgrades/20190228_150449_11313@/log.gz ... To: root@autopkgtest Auto-Submitted: auto-generated MIME-Version: 1.0 ... ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1230246 Title: Add Auto-Submitted header to email report Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: Please add the header Auto-Submitted: auto-generated to the emails generated by the unattended-upgrade process. This would assist in both the mail filtering for receivers and the correct processing for "vacation" auto-responders. Further technical details are given in: http://tools.ietf.org/html/rfc3834#section-5 http://tools.ietf.org/html/rfc5230#page-8 https://www.iana.org/assignments/auto-submitted-keywords/auto-submitted-keywords.xhtml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1230246/+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 1775307] Re: Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1 version
Tested 1.1ubuntu1.18.04.7~16.04.2 on Xenial. root@x-uu-upgrade:~# unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial Using (^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*) regexp to find kernel packages Using (^linux-image-4\.18\.0\-16\-generic$|^linux-headers-4\.18\.0\-16\-generic$|^linux-image-extra-4\.18\.0\-16\-generic$|^linux-modules-4\.18\.0\-16\-generic$|^linux-modules-extra-4\.18\.0\-16\-generic$|^linux-signed-image-4\.18\.0\-16\-generic$|^kfreebsd-image-4\.18\.0\-16\-generic$|^kfreebsd-headers-4\.18\.0\-16\-generic$|^gnumach-image-4\.18\.0\-16\-generic$|^.*-modules-4\.18\.0\-16\-generic$|^.*-kernel-4\.18\.0\-16\-generic$|^linux-backports-modules-.*-4\.18\.0\-16\-generic$|^linux-modules-.*-4\.18\.0\-16\-generic$|^linux-tools-4\.18\.0\-16\-generic$|^linux-cloud-tools-4\.18\.0\-16\-generic$) regexp to find running kernel packages Checking: locales ([]) adjusting candidate version: locales=2.23-0ubuntu10 pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] No packages found that can be upgraded unattended and no pending auto-removals root@x-uu-upgrade:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==--=== ii unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all automatic installation of security upgrades ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1775307 Title: Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1 version Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] * Unattended-upgrades fails to install updates when adjusting candidates is needed. [Test Case] Note that only 1.2ubuntu1 is affected. Earlier releases either did not crash or did not adjust candidates due to LP: #1775292. To reproduce the crash Cosmic's u-u 1.2ubuntu1 needs to be installed. * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug * Observe no line with "adjusting candidate version: " or a crash with buggy u-u versions ... adjusting candidate version: zfs-initramfs=0.7.5-1ubuntu15 adjusting candidate version: zfs-test=0.7.5-1ubuntu15 adjusting candidate version: zfs-zed=0.7.5-1ubuntu15 adjusting candidate version: zfsutils-linux=0.7.5-1ubuntu15 Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1928, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1554, in main allowed_origins=allowed_origins) File "/usr/bin/unattended-upgrade", line 122, in __init__ apt.Cache.__init__(self, rootdir=rootdir) File "/usr/lib/python3/dist-packages/apt/cache.py", line 130, in __init__ self.open(progress) File "/usr/bin/unattended-upgrade", line 152, in open self.adjust_candidates() File "/usr/bin/unattended-upgrade", line 161, in adjust_candidates for pkgname, candidate in self._get_candidates_to_adjust(): ValueError: too many values to unpack (expected 2) * Install fixed u-u version * Run sudo unattended-upgrade --dry-run --verbose --debug * Observe lines "adjusting candidate version: " and no crash [Regression Potential] * Unattended-upgrade may crash when adjusting candidates preventing upgrades to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1775307/+subscriptions --
[Touch-packages] [Bug 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)
This version fixes a subtle bug added by me when de-conflicting the diff. ** Patch removed: "Full debdiff for xenial systemd SRU (with correct changelog)" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5245818/+files/systemd_229-4ubuntu21.18.debdiff ** Patch added: "debdiff with a port of the fix in PR#8803 to trusty (test ppa upload)" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5245851/+files/systemd_229-4ubuntu21.18~ppa2.debdiff -- 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/1819728 Title: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18) Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Bug description: [Impact] On Ubuntu Core we recently hit the a race in daemon-reload and systemctl twice. This race is fixed in systemd upstream: "fix race between daemon-reload and other commands #8803". [TEST CASE] To reproduce its enough to run: for i in $(seq 50); do systemctl daemon-reload & systemctl start ssh & done This will result in "systemctl start ssh" hanging in ppoll. With the patch applied the hangs go away. [REGRESSION POTENTIAL] Low, this change is already in the systemd upstream and in use cosmic and later. The upstream fix is https://github.com/systemd/systemd/pull/8803 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+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 1819625] Re: Package resolvconf=1.79ubuntu10.18.04.1 broken
No vpn - DNS resolver broken by update (on production server) bug@test:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search ~~cut~~.intern lxd options edns0 ### -- bug@test:~$ systemd-resolve --status Global DNS Servers: 10.176.0.1 10.176.0.2 10.168.127.126 DNS Domain: ~~cut~~.intern DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa ~~ cut ~~ Link 3 (lxdbr0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.145.28.1 DNS Domain: lxd ### -- bug@test:~$ lxc launch ubuntu:18.04 ub18-1 Creating ub18-1 Starting ub18-1 ### -- bug@test:~$ dig ub18-1.lxd ;; ANSWER SECTION: ub18-1.lxd. 600 IN A 10.145.28.214 ;; SERVER: 127.0.0.53#53(127.0.0.53) ### -- bug@test:~$ sudo apt-get upgrade The following packages will be upgraded: resolvconf 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Preparing to unpack .../resolvconf_1.79ubuntu10.18.04.1_all.deb ... Processing triggers for resolvconf (1.79ubuntu10.18.04.1) ... ### -- bug@test:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 10.176.0.1 nameserver 10.176.0.2 nameserver 10.168.127.126 search ~~cut~~.intern lxd ### -- bug@test:~$ dig ub18-1.lxd ;; QUESTION SECTION: ;ub18-1.lxd.IN A ;; SERVER: 10.176.0.1#53(10.176.0.1) ### -- # temporary fix: bug@test:~$ wget http://de.archive.ubuntu.com/ubuntu/pool/universe/r/resolvconf/resolvconf_1.79ubuntu10_all.deb bug@test:~$ sudo dpkg --install resolvconf_1.79ubuntu10_all.deb bug@test:~$ dig ub18-1.lxd ;; ANSWER SECTION: ub18-1.lxd. 600 IN A 10.145.28.214 ;; Query time: 1 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1819625 Title: Package resolvconf=1.79ubuntu10.18.04.1 broken Status in resolvconf package in Ubuntu: Confirmed Bug description: The package resolveconf version 1.79ubuntu10.18.04.1 is broken. Installing the package breaks DNS resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.1 Uname: Linux 4.15.0-46-generic x86_64 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1819625/+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 1818516] Re: FFe: Mesa 19.0.x for disco
The upstream release tracker probably helps showing that there's only one identified bug on the list, which is triggered by Intel's CI. AMD has something similar but not as comprehensive AIUI. I've tested this on an Intel gen9 (coffee lake) gpu so far, AMD Ryzen/Vega Mobile is soon done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1818516 Title: FFe: Mesa 19.0.x for disco Status in mesa package in Ubuntu: New Bug description: Mesa 19.0.0 will be soon released, and we should get that for disco, and then follow point-releases until the last one is released (roughly next July, will need an SRU). We'll also migrate it to use LLVM 8. New features according to upstream release notes: GL_AMD_texture_texture4 on all GL 4.0 drivers. GL_EXT_shader_implicit_conversions on all drivers (ES extension). GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension). GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension). GL_EXT_render_snorm on gallium drivers (ES extension). GL_EXT_texture_view on drivers supporting texture views (ES extension). GL_OES_texture_view on drivers supporting texture views (ES extension). GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only). Shader-based software implementations of GL_ARB_gpu_shader_fp64, GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot on i965. VK_ANDROID_external_memory_android_hardware_buffer on Intel Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV VK_EXT_scalar_block_layout on Intel and RADV VK_KHR_depth_stencil_resolve on Intel VK_KHR_draw_indirect_count on Intel VK_EXT_conditional_rendering on Intel VK_EXT_memory_budget on RADV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
bionic was already fixed earlier by 18.2.2-0ubuntu1~18.04.2 in time for 18.04.2 release cosmic got the exact same oneliner in 18.2.8-0ubuntu0~blah, and then that was backported to bionic which reopened this bug. Requiring Alkis to test this on cosmic is too much IMO, as it would involve first to set up a school to use cosmic, then test remotely or ask folks over there to report back... all for a oneliner. Alkis, please correct me if I'm wrong.. ** Description changed: - Several schools reported black screens after normally updating their - Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. + [Impact] + Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: - * systemctl --failed says "gpu-manager" and "lightdm" have failed - * Xorg.log is clean: https://termbin.com/6l2b - * dmesg too: https://termbin.com/ip4e - * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. - * If one runs `xinit` from ssh, it fails with: + * systemctl --failed says "gpu-manager" and "lightdm" have failed + * Xorg.log is clean: https://termbin.com/6l2b + * dmesg too: https://termbin.com/ip4e + * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. + * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument + + This is caused by mesa assuming that soft-pinning on GEN8+ is working + since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a + proper fix would be to backport commits from 4.19.3/4.20 to fix GTT + sizes/pin flags, but that's left for future. + + [Test case] + install fixed mesa or kernel, check that the regression is fixed + + [Regression potential] + mesa: shouldn't be any, it just reverts the change to always soft-pin + (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1789924] Re: Missing Intel GPU pci-id's
** Description changed: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] - Check that the user session uses the proper driver on these systems. + Check that the user session uses the proper driver on these systems, if possible. Adding new pci-id's is a trivial change which can't regress existing hw. [Regression potential] none, these just add pci-id's and platform definitions -- 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems, if possible. Adding new pci-id's is a trivial change which can't regress existing hw. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1789924] Re: Missing Intel GPU pci-id's
This was already fixed in bionic by 18.2.2-0ubuntu1~18.04.1, now the same is included upstream in 18.2.8 which was upload to cosmic too as well as to bionic via a new backport. Again, I don't have the hardware (AML, WHL is broken atm), adding pci- id's just allow the X driver to load the DRI driver, there is no regression potential on other hw etc etc. So in a way this bug should've been marked 'invalid' for cosmic and just let it be part of 18.2.8 upstream version which is handled separately in bug 1811225.. My bad for including it in the changelog. -- 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems, if possible. Adding new pci-id's is a trivial change which can't regress existing hw. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1800836] Re: systemd-networkd doesn't process IPv6 RA properly
I can confirm the same issues with `systemd-networkd` in Xenial (and Debian Stretch). Do you know if there is a patch from a modern `systemd` that can be used to backport a fix to older versions? When not using `systemd-networkd` (like older dists or "vanilla" Xenial) it is possible to see when an default route expires, but that data seems to be lost with `systemd-networkd`. Trusty without `systemd-networkd`: ``` $ ip -6 r [...] default via fe80::209:fff:fe09:5 dev eth0 proto kernel metric 1024 expires 1566sec ``` Xenial without `systemd-networkd`: ``` $ ip -6 r [...] default via fe80::209:fff:fe09:5 dev ens192 proto ra metric 1024 expires 1545sec pref medium ``` Xenial WITH `systemd-networkd`: ``` $ ip -6 r [...] default via fe80::209:fff:fe09:5 dev ens192 proto ra metric 1024 pref medium ``` -- 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/1800836 Title: systemd-networkd doesn't process IPv6 RA properly Status in systemd package in Ubuntu: Confirmed Bug description: The gateways/firewalls in our DC are highly available and when there is a failover their IPv6 VIP (fe80::1) moves from the master to the backup one. We found that only our Bionic VMs behind those gateways had issues after a failover. Those Bionic VMs were all running systemd-networkd (from netplan) and before the failover they had: $ ip -6 route ... default via fe80::1 dev eth0 proto ra metric 1024 pref medium But after a failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 And after another failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 nexthop via fe80::210:18ff:fe77:b558 dev eth0 weight 1 This is problematic as those then use fe80::210:18ff:fe77:b558%$IFACE as their default gateway even when this gateway is unavailable: $ ip -6 route get :: :: from :: via fe80::210:18ff:fe77:b558 dev eth0 proto ra src fe80::a800:ff:fe51:8c37 metric 1024 pref medium We concluded it was a systemd-networkd bug after checking that the following combinations were NOT affected: 1) Xenial+4.4 kernel 2) Xenial+4.15 kernel 3) Bionic+ifupdown Additional information: $ apt-cache policy systemd systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 31 08:47:28 2018 Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=43b7ee2e-2ab1-4505-8e0b-d9fe0563a034 ro console=ttyS0 net.ifnames=0 vsyscall=none kaslr nmi_watchdog=0 possible_cpus=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800836/+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 1819909] [NEW] Problem with windows
Public bug reported: No border around windows, no resizing buttons (max, min, close). Windows cannot be moved or resized. Alt+tab and Alt+F4 have no effect, but some other keyboard shortcuts, e.g. ctrl+alt+T and ctrl+Q, seem to work ok. Only closing a window changes focus; even clicking with mouse doesn't. For instance, I can use ctrl+alt+t to open a terminal, and click in it all I want, but even though it is on top, whatever I type just goes into this window. When I close the browser, however, it will gain focus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Wed Mar 13 08:30:21 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [17aa:3809] InstallationDate: Installed on 2018-09-10 (184 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:a745 IMC Networks Bus 001 Device 003: ID 0cf3:e360 Atheros Communications, Inc. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80T7 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/28/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 1GCN12WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: 00RD15IPG076 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15IBR dmi.modalias: dmi:bvnLENOVO:bvr1GCN12WW:bd02/28/2016:svnLENOVO:pn80T7:pvrLenovoideapad110-15IBR:rvnLENOVO:rn00RD15IPG076:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15IBR: dmi.product.family: IDEAPAD dmi.product.name: 80T7 dmi.product.version: Lenovo ideapad 110-15IBR dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 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/1819909 Title: Problem with windows Status in xorg package in Ubuntu: New Bug description: No border around windows, no resizing buttons (max, min, close). Windows cannot be moved or resized. Alt+tab and Alt+F4 have no effect, but some other keyboard shortcuts, e.g. ctrl+alt+T and ctrl+Q, seem to work ok. Only closing a window changes focus; even clicking with mouse doesn't. For instance, I can use ctrl+alt+t to open a terminal, and click in it all I want, but even though it is on top, whatever I type just goes into this window. When I close the browser, however, it will gain focus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Wed Mar 13 08:30:21 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-46-generic,
[Touch-packages] [Bug 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)
The xenial version of this is NOT ready yet, a second run produced a CRASH at startup on UC16 with the updated systemd. ** Patch removed: "debdiff with a port of the fix in PR#8803 for xenial" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5245665/+files/fix-systemctl-race-8803.debdiff -- 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/1819728 Title: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18) Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Bug description: [Impact] On Ubuntu Core we recently hit the a race in daemon-reload and systemctl twice. This race is fixed in systemd upstream: "fix race between daemon-reload and other commands #8803". [TEST CASE] To reproduce its enough to run: for i in $(seq 50); do systemctl daemon-reload & systemctl start ssh & done This will result in "systemctl start ssh" hanging in ppoll. With the patch applied the hangs go away. [REGRESSION POTENTIAL] Low, this change is already in the systemd upstream and in use cosmic and later. The upstream fix is https://github.com/systemd/systemd/pull/8803 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+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 1789924] Re: Missing Intel GPU pci-id's
What testing did you perform? ** Tags removed: verification-done verification-done-cosmic ** Tags added: verification-needed verification-needed-cosmic -- 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1789924] Re: Missing Intel GPU pci-id's
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. -- 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)
The xenial build of the updated systemd was tested using a full spread run with no regressions and a new test was added in https://github.com/snapcore/snapd/pull/6595 to test that the regression is fixed This test shows that core/edge is fixed but core/beta which does not yet has the fix is hanging (as expected). -- 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/1819728 Title: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18) Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Bug description: [Impact] On Ubuntu Core we recently hit the a race in daemon-reload and systemctl twice. This race is fixed in systemd upstream: "fix race between daemon-reload and other commands #8803". [TEST CASE] To reproduce its enough to run: for i in $(seq 50); do systemctl daemon-reload & systemctl start ssh & done This will result in "systemctl start ssh" hanging in ppoll. With the patch applied the hangs go away. [REGRESSION POTENTIAL] Low, this change is already in the systemd upstream and in use cosmic and later. The upstream fix is https://github.com/systemd/systemd/pull/8803 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+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 1800836] Re: systemd-networkd doesn't process IPv6 RA properly
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/1800836 Title: systemd-networkd doesn't process IPv6 RA properly Status in systemd package in Ubuntu: Confirmed Bug description: The gateways/firewalls in our DC are highly available and when there is a failover their IPv6 VIP (fe80::1) moves from the master to the backup one. We found that only our Bionic VMs behind those gateways had issues after a failover. Those Bionic VMs were all running systemd-networkd (from netplan) and before the failover they had: $ ip -6 route ... default via fe80::1 dev eth0 proto ra metric 1024 pref medium But after a failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 And after another failover: $ ip -6 route ... default proto ra metric 1024 nexthop via fe80::1 dev eth0 weight 1 nexthop via fe80::210:18ff:febe:6750 dev eth0 weight 1 nexthop via fe80::210:18ff:fe77:b558 dev eth0 weight 1 This is problematic as those then use fe80::210:18ff:fe77:b558%$IFACE as their default gateway even when this gateway is unavailable: $ ip -6 route get :: :: from :: via fe80::210:18ff:fe77:b558 dev eth0 proto ra src fe80::a800:ff:fe51:8c37 metric 1024 pref medium We concluded it was a systemd-networkd bug after checking that the following combinations were NOT affected: 1) Xenial+4.4 kernel 2) Xenial+4.15 kernel 3) Bionic+ifupdown Additional information: $ apt-cache policy systemd systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 31 08:47:28 2018 Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=43b7ee2e-2ab1-4505-8e0b-d9fe0563a034 ro console=ttyS0 net.ifnames=0 vsyscall=none kaslr nmi_watchdog=0 possible_cpus=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800836/+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 1742714] Re: MIR: mesa-vulkan-drivers FFE: install by default
moving back to the metapackage ** Package changed: xorg-server (Ubuntu) => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1742714 Title: MIR: mesa-vulkan-drivers FFE: install by default Status in mesa package in Ubuntu: New Status in vulkan-loader package in Ubuntu: Invalid Status in xorg package in Ubuntu: New Bug description: MIR mesa-vulkan-drivers: - is from mesa, which is already in main - maintained just as mesa is, by ubuntu-x-swat MIR vulkan-loader: https://bugs.launchpad.net/ubuntu/+source/vulkan-loader/+bug/1742711 FFE: - new packages in the default install (mesa-vulkan-drivers, libvulkan1) -> no chance of regressing anything -- A Vulkan related bug was filed at https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in a related note, having mesa-vulkan-drivers moved from Universe to Main and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten mature and since the OpenGL drivers are installed, it will very complimentary. Having this available will aid game developers and users who load up a Vulkan application and get errors. They may not know to enable Universe in their Software Manager and to manually install mesa- vulkan-drivers for their video card. They may just load up that Vulkan application, find out it doesn't work, and then give up on it. We cannot have that for future adoption of the API. Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV are implementing experimental support for Vulkan. For Ubuntu being a leader for the desktop and a base for GNU/Linux gaming, shouldn't it be painless for Ubuntu 18.04? Especially since it is a long term release for 5 years. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1742714/+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 1742714] Re: MIR: mesa-vulkan-drivers FFE: install by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1742714 Title: MIR: mesa-vulkan-drivers FFE: install by default Status in mesa package in Ubuntu: New Status in vulkan-loader package in Ubuntu: Invalid Status in xorg package in Ubuntu: New Bug description: MIR mesa-vulkan-drivers: - is from mesa, which is already in main - maintained just as mesa is, by ubuntu-x-swat MIR vulkan-loader: https://bugs.launchpad.net/ubuntu/+source/vulkan-loader/+bug/1742711 FFE: - new packages in the default install (mesa-vulkan-drivers, libvulkan1) -> no chance of regressing anything -- A Vulkan related bug was filed at https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in a related note, having mesa-vulkan-drivers moved from Universe to Main and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten mature and since the OpenGL drivers are installed, it will very complimentary. Having this available will aid game developers and users who load up a Vulkan application and get errors. They may not know to enable Universe in their Software Manager and to manually install mesa- vulkan-drivers for their video card. They may just load up that Vulkan application, find out it doesn't work, and then give up on it. We cannot have that for future adoption of the API. Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV are implementing experimental support for Vulkan. For Ubuntu being a leader for the desktop and a base for GNU/Linux gaming, shouldn't it be painless for Ubuntu 18.04? Especially since it is a long term release for 5 years. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1742714/+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 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)
** Description changed: [Impact] On Ubuntu Core we recently hit the a race in daemon-reload and systemctl twice. This race is fixed in systemd upstream: "fix race between daemon-reload and other commands #8803". [TEST CASE] To reproduce its enough to run: for i in $(seq 50); do systemctl daemon-reload & systemctl start ssh & done This will result in "systemctl start ssh" hanging in ppoll. With the patch applied the hangs go away. [REGRESSION POTENTIAL] Low, this change is already in the systemd upstream and in use cosmic and later. + + The upstream fix is https://github.com/systemd/systemd/pull/8803 -- 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/1819728 Title: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18) Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Bug description: [Impact] On Ubuntu Core we recently hit the a race in daemon-reload and systemctl twice. This race is fixed in systemd upstream: "fix race between daemon-reload and other commands #8803". [TEST CASE] To reproduce its enough to run: for i in $(seq 50); do systemctl daemon-reload & systemctl start ssh & done This will result in "systemctl start ssh" hanging in ppoll. With the patch applied the hangs go away. [REGRESSION POTENTIAL] Low, this change is already in the systemd upstream and in use cosmic and later. The upstream fix is https://github.com/systemd/systemd/pull/8803 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+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 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly
** Changed in: systemd (Debian) 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/1818282 Title: systemd-networkd - RoutingPolicyRule does not apply correctly Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Status in systemd package in Debian: New Bug description: [Impact] When attaching multiple IPs on secondary interface the routing policy rules do not apply for all IPs. The rules that are applied after restarting networkd are random. The issue has been reported and addressed upstream. [Test Case] Attach multiple IPs to secondary interface, config file: $ cat /etc/systemd/network/ens8.network [Match] Name=ens8 [Network] Address=172.31.28.195/20 Address=172.31.24.151/20 Address=172.31.24.152/20 Address=172.31.24.153/20 [Route] Destination=0.0.0.0/0 Gateway=172.31.16.1 Table=1000 [Route] Destination=172.31.24.153 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.28.195 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.24.151 Gateway=0.0.0.0 Scope=link Table=1000 [Route] Destination=172.31.24.152 Gateway=0.0.0.0 Scope=link Table=1000 [RoutingPolicyRule] From=172.31.24.153 Table=1000 [RoutingPolicyRule] From=172.31.28.195 Table=1000 [RoutingPolicyRule] From=172.31.24.152 Table=1000 [RoutingPolicyRule] From=172.31.24.151 Table=1000 $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 32766:from all lookup main 32767:from all lookup default - restart networkd $ sudo systemctl restart systemd-networkd $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 0:from 172.31.24.153 lookup 1000 0:from 172.31.28.195 lookup 1000 32766:from all lookup main 32767:from all lookup default - restart again $ sudo systemctl restart systemd-networkd $ ip rule show 0:from all lookup local 0:from 172.31.24.151 lookup 1000 0:from 172.31.24.152 lookup 1000 32766:from all lookup main 32767:from all lookup default The behaviour is random [Regression Potential] May impact the systemd-networkd service functionality. [Other] Affects Disco Bionic and Cosmic. Upstream bug : https://github.com/systemd/systemd/issues/11280 Upstream fix : https://github.com/systemd/systemd/pull/11795/commits $ lsb_release -rd Description: Ubuntu Disco Dingo (development branch) Release: 19.04 Systemd version : systemd: Installed: 240-6ubuntu1 Candidate: 240-6ubuntu1 Version table: *** 240-6ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818282/+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
