[Touch-packages] [Bug 1808493] [NEW] Let's Encrypt CA Root Certificates missing
Public bug reported: Please add the Chain of trust for the Let's Encrypt CA to the ubuntu ca- certificates https://letsencrypt.org/certificates/ we have to add them always manually and i think it's time to accept, that let's encrypt is now one of the bigger CA. Missing in releases 16.04 LTS / 18.04 LTS ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1808493 Title: Let's Encrypt CA Root Certificates missing Status in ca-certificates package in Ubuntu: New Bug description: Please add the Chain of trust for the Let's Encrypt CA to the ubuntu ca-certificates https://letsencrypt.org/certificates/ we have to add them always manually and i think it's time to accept, that let's encrypt is now one of the bigger CA. Missing in releases 16.04 LTS / 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1808493/+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 1808428] Re: Ping of a link local address with -I as non-root produces "Invalid argument"
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1808428 Title: Ping of a link local address with -I as non-root produces "Invalid argument" Status in iputils package in Ubuntu: New Bug description: iputils-ping 3:20161105-1ubuntu2 amd64 18.04.1 LTS In the following, "c7" is a host with the link-local address fe80::5054:ff:fe45:1e87. The mapping is in "/etc/hosts". It is reachable via the "enp2s0" interface on the local machine. I have masked the local machine's MAC address. 1. As a regular (non-root) user, ping returns "Invalid argument": $ ping -I enp2s0 c7 PING c7(c7 (fe80::5054:ff:fe45:1e87)) from fe80:::xxff:fexx:%enp2s0 enp2s0: 56 data bytes ping: sendmsg: Invalid argument ping: sendmsg: Invalid argument ping: sendmsg: Invalid argument 2. As root, ping works: # ping -I enp2s0 c7 PING c7(c7 (fe80::5054:ff:fe45:1e87)) from fe80:::xxff:fexx:%enp2s0 enp2s0: 56 data bytes 64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=1 ttl=64 time=0.285 ms 64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=2 ttl=64 time=0.306 ms 64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=3 ttl=64 time=0.307 ms 3. Specifying the interface-qualified IPv6 address directly works: $ ping fe80::5054:ff:fe45:1e87%enp2s0 PING fe80::5054:ff:fe45:1e87%enp2s0(fe80::5054:ff:fe45:1e87%enp2s0) 56 data bytes 64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=1 ttl=64 time=0.476 ms 64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=2 ttl=64 time=0.408 ms 64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=3 ttl=64 time=0.395 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1808428/+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 1808491] [NEW] CUPS wrong orientation at custom size
Public bug reported: Hi, I am developing a GUI using Qt toolkit. I have a Zebra GC420t connected over USB. I am using a custom sized label. Printing was successful at 2.1.3-4, but after update got wrong orientation. Tried to downgrade current machine, but cannot get output. Tried to fix orientation with an edited PPD file, but can only print half of the label. This is the related question at Zebra forum : https://developer.zebra.com/thread/36319 1) The release of Ubuntu you are using, via 'lsb_release -rd' - $ lsb_release -rd Description:Ubuntu 16.04.5 LTS Release:16.04 2) The version of the package you are using --- $ LC_ALL=C apt-cache policy cups cups: Installed: 2.1.3-4ubuntu0.6 Candidate: 2.1.3-4ubuntu0.6 Version table: *** 2.1.3-4ubuntu0.6 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 2.1.3-4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen -- Print right orientation at custom size 4) What happened instead Wrong orientated printing at custom size ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Package changed: flashplugin-nonfree (Ubuntu) => cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1808491 Title: CUPS wrong orientation at custom size Status in cups package in Ubuntu: New Bug description: Hi, I am developing a GUI using Qt toolkit. I have a Zebra GC420t connected over USB. I am using a custom sized label. Printing was successful at 2.1.3-4, but after update got wrong orientation. Tried to downgrade current machine, but cannot get output. Tried to fix orientation with an edited PPD file, but can only print half of the label. This is the related question at Zebra forum : https://developer.zebra.com/thread/36319 1) The release of Ubuntu you are using, via 'lsb_release -rd' - $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 2) The version of the package you are using --- $ LC_ALL=C apt-cache policy cups cups: Installed: 2.1.3-4ubuntu0.6 Candidate: 2.1.3-4ubuntu0.6 Version table: *** 2.1.3-4ubuntu0.6 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 2.1.3-4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen -- Print right orientation at custom size 4) What happened instead Wrong orientated printing at custom size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1808491/+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 1808491] [NEW] CUPS wrong orientation at custom size
You have been subscribed to a public bug: Hi, I am developing a GUI using Qt toolkit. I have a Zebra GC420t connected over USB. I am using a custom sized label. Printing was successful at 2.1.3-4, but after update got wrong orientation. Tried to downgrade current machine, but cannot get output. Tried to fix orientation with an edited PPD file, but can only print half of the label. This is the related question at Zebra forum : https://developer.zebra.com/thread/36319 1) The release of Ubuntu you are using, via 'lsb_release -rd' - $ lsb_release -rd Description:Ubuntu 16.04.5 LTS Release:16.04 2) The version of the package you are using --- $ LC_ALL=C apt-cache policy cups cups: Installed: 2.1.3-4ubuntu0.6 Candidate: 2.1.3-4ubuntu0.6 Version table: *** 2.1.3-4ubuntu0.6 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 2.1.3-4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen -- Print right orientation at custom size 4) What happened instead Wrong orientated printing at custom size ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- CUPS wrong orientation at custom size https://bugs.launchpad.net/bugs/1808491 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups 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 1808476] [NEW] Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants
Public bug reported: $ python -c 'import ssl; print(ssl.OP_NO_TLSv1_3)' Prints 0, for python2.7 built against 1.1.0 headers, yet prints 536870912 when built against 1.1.1 irrespective of the runtime libssl1.1 library version. This may yield confusion, especially since ssl.OPENSSL_VERSION reports runtime libssl version, not the version of the libssl headers. Such that, e.g. it looks like ssl module is running against 1.1.1, has OP_NO_TLSv1_3 option, yet cannot actually use it to disable TLSv1.3. Also vice versa, python2.7 build against 1.1.1 can be installed with 1.1.0 runtime library, and thus OP_NO_TLSv1_3 might be set, which is not understood by the runtime library. In libpython2.7-stdlib, please bump libssl1.1 version dep to "libssl1.1 (>= 1.1.1)" when building against libssl-dev >= 1.1.1. python3.x are not affected, as they started to exploit 1.1.1-only symbols/features, and thus already have an automatic dep on >= 1.1.1. ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Description changed: $ python -c 'import ssl; print(ssl.OP_NO_TLSv1_3)' Prints 0, for python2.7 built against 1.1.0 headers, yet prints 536870912 when built against 1.1.1 irrespective of the runtime libssl1.1 library version. This may yield confusion, especially since ssl.OPENSSL_VERSION reports runtime libssl version, not the version of the libssl headers. Such that, e.g. it looks like ssl module is running against 1.1.1, has OP_NO_TLSv1_3 option, yet cannot actually use it to disable TLSv1.3. Also vice versa, python2.7 build against 1.1.1 can be installed with 1.1.0 runtime library, and thus OP_NO_TLSv1_3 might be set, which is not understood by the runtime library. In libpython2.7-stdlib, please bump libssl1.1 version dep to "libssl1.1 (>= 1.1.1)" when building against libssl-dev >= 1.1.1. + + python3.x are not affected, as they started to exploit 1.1.1-only + symbols/features, and thus already have an automatic dep on >= 1.1.1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1808476 Title: Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants Status in python2.7 package in Ubuntu: New Bug description: $ python -c 'import ssl; print(ssl.OP_NO_TLSv1_3)' Prints 0, for python2.7 built against 1.1.0 headers, yet prints 536870912 when built against 1.1.1 irrespective of the runtime libssl1.1 library version. This may yield confusion, especially since ssl.OPENSSL_VERSION reports runtime libssl version, not the version of the libssl headers. Such that, e.g. it looks like ssl module is running against 1.1.1, has OP_NO_TLSv1_3 option, yet cannot actually use it to disable TLSv1.3. Also vice versa, python2.7 build against 1.1.1 can be installed with 1.1.0 runtime library, and thus OP_NO_TLSv1_3 might be set, which is not understood by the runtime library. In libpython2.7-stdlib, please bump libssl1.1 version dep to "libssl1.1 (>= 1.1.1)" when building against libssl-dev >= 1.1.1. python3.x are not affected, as they started to exploit 1.1.1-only symbols/features, and thus already have an automatic dep on >= 1.1.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1808476/+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 1759836] Re: systemd-udevd consumes 100% of CPU
Can you try comment out this section helps:
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01",
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
and this section:
ATTR{bDeviceClass}=="e0", ATTR{bDeviceSubClass}=="01",
ATTR{bDeviceProtocol}=="01", ATTR{idVendor}=="413c", \
ENV{REMOVE_CMD}="/sbin/udevadm trigger --action=change --subsystem-match=usb
--property-match=HID2HCI_SWITCH=1"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1759836
Title:
systemd-udevd consumes 100% of CPU
Status in linux:
Confirmed
Status in The Ubuntu Power Consumption Project:
New
Status in bluez package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Confirmed
Bug description:
The systemd-udevd proccess consumes 100% of a thread everytime, but
i'm not noticing any difference in my computer.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 29 08:52:54 2018
InstallationDate: Installed on 2018-03-05 (23 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
MachineType: Dell Inc. Inspiron N5010
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service →
/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/user@.service →
/lib/systemd/system/user@.service.d/timeout.conf
2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 08R0GW
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias:
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Inspiron N5010
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1759836/+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 1802591] Re: Skip enslaved devices during boot
Hello Marcelo, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.6 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: initramfs-tools (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: initramfs-tools (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1802591 Title: Skip enslaved devices during boot Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Cosmic: New Bug description: In order to support live migration in OCI, we need to filter enslaved devices during boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1802591/+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 1802591] Please test proposed package
Hello Marcelo, or anyone else affected, Accepted initramfs-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.122ubuntu8.14 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1802591 Title: Skip enslaved devices during boot Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Cosmic: New Bug description: In order to support live migration in OCI, we need to filter enslaved devices during boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1802591/+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 1802591] Re: Skip enslaved devices during boot
Can we have this fix applied in development asap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1802591 Title: Skip enslaved devices during boot Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Cosmic: New Bug description: In order to support live migration in OCI, we need to filter enslaved devices during boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1802591/+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 1802591] Re: Skip enslaved devices during boot
Or indicate here it is not required for other reasons. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1802591 Title: Skip enslaved devices during boot Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Cosmic: New Bug description: In order to support live migration in OCI, we need to filter enslaved devices during boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1802591/+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 1808337] Re: Codename is n/a
OK. Thanks, @juliank. I just found the Debian source repo. https://salsa.debian.org/apt-team/python-apt/merge_requests/13 -- 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/1808337 Title: Codename is n/a Status in python-apt package in Ubuntu: Invalid Bug description: Codename is `n/a` which is not right. I noticed that codename is come from `_lsb_release()` in `aptsources/distro.py`. However `lsb_release -a` may give a wrong result. Maybe we could try `cat /etc/debian_version`. All Debian derives should have this file. ```bash # lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.6 (n/a) Release: 9.6 Codename: n/a # cat /etc/debian_version buster/sid # cut -f1 -d'/' /etc/debian_version buster # cat /etc/issue Debian GNU/Linux buster/sid \n \l # cat /etc/os-release PRETTY_NAME="Debian GNU/Linux buster/sid" NAME="Debian GNU/Linux" ID=debian HOME_URL="https://www.debian.org/"; SUPPORT_URL="https://www.debian.org/support"; BUG_REPORT_URL="https://bugs.debian.org/"; ``` ```python Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 95, in sp = SoftwareProperties(options=options) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 109, in __init__ self.reload_sourceslist() File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 599, in reload_sourceslist self.distro.get_sources(self.sourceslist) File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in get_sources (self.id, self.codename)) aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Debian/n/a ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1808337/+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 1808193] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1808193 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in upower package in Ubuntu: New Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808193/+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 1808203] Re: ddfs
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1808203 Title: ddfs Status in Ubuntu: Incomplete Bug description: sdfsf ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Dec 12 21:07:13 2018 DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad] InstallationDate: Installed on 2016-04-24 (962 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Sony Corporation SVE1112M1EW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-12 (0 days ago) dmi.bios.date: 08/22/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0120D8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE1112M1EW dmi.product.version: C60B8BEP dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Dec 12 18:07:04 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808203/+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 1808419] Re: Screen Brightness problem
Firstly, please keep each bug report about a single issue. This bug should be about the screen brightness only. Next, please look in: Settings > Power and turn off automatic dimming in case that is contributing to the problem. If the problem still isn't fixed, can you tell us if the brightness slider in the top-right menu works for you? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Tags added: backlight nvidia -- 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/1808419 Title: Screen Brightness problem Status in xorg-server package in Ubuntu: Incomplete Bug description: When i switch on my laptop with Ubuntu. It starts with lowest brightness. Even it set to normal. When i set it again it returning to normal. But when after screen dimming it does not return again. So it doesnt recognize to my mouse or keyboard. Sorry for my English. I hope I could explain my problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 14 02:43:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed nvidia, 390.48, 4.15.0-34-generic, x86_64: installed nvidia, 390.48, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04ca] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04ca] InstallationDate: Installed on 2018-09-30 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron N5110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4a66061d-c599-4959-97d9-eee379ba8b99 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0HVRTT dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0HVRTT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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/xorg-server/+bug/1808419/+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 1808193] Re: Battery indicator shows false reading
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Battery indicator shows false reading + Battery percentage changes suddenly depending on whether AC is plugged in ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808193/+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 1647368] Re: [16.04.1 LTS] debconf-get-selections --installer, produces no output
That still worked fine in 14.04 (allowing to create a custom preseed script easily), not working in 16.04 or 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1647368 Title: [16.04.1 LTS] debconf-get-selections --installer, produces no output Status in debconf package in Ubuntu: Confirmed Bug description: On Ubuntu release: Ubuntu 16.04.1 LTS Package: debconf-utils Version: 1.5.58ubuntu1 Arch: amd64 When running (as root): "debconf-get-selections --installer" No output is produced. Typically needed to produce a preseed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1647368/+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 1808275] Re: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped
Sound hardware sometimes remembers its state even if you switch between operating systems. So please also try turning the machine off for a few seconds and then on again. -- 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/1808275 Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped Status in pulseaudio package in Ubuntu: Incomplete Bug description: The green headphone out was working and I changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped and changing it back to Analog Output didn't restore the sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 12 23:10:39 2018 InstallationDate: Installed on 2018-12-06 (7 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97510J.86A.1487.2007.0902.1724 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX dmi.board.vendor: Intel Corporation dmi.board.version: AAD27094-305 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-305:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1808275/+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 1808323] Re: gfg
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1808323 Title: gfg Status in Ubuntu: Incomplete Bug description: gfg ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Dec 13 14:09:43 2018 DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad] InstallationDate: Installed on 2016-04-24 (963 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Sony Corporation SVE1112M1EW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-12 (0 days ago) dmi.bios.date: 08/22/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0120D8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE1112M1EW dmi.product.version: C60B8BEP dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Dec 12 18:07:04 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808323/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
It appears the gnome-shell!278 fix is only in future version 3.31.3 at the moment. I've had the same issue with other laptops and would be surprised if this was the only bug report. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in linux package in Ubuntu: In Progress Status in upower package in Ubuntu: Confirmed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
This issue also affects Asus Vivobook 15 X510UR. -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in upower package in Ubuntu: Confirmed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in upower package in Ubuntu: Confirmed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upower (Ubuntu) Status: New => Confirmed -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in upower package in Ubuntu: Confirmed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in upower package in Ubuntu: Confirmed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1804755] Re: SRU of LXC 3.0.3 (upstream bugfix release)
This bug was fixed in the package lxc - 3.0.3-0ubuntu1~18.04.1
---
lxc (3.0.3-0ubuntu1~18.04.1) bionic; urgency=medium
* New upstream bugfix release (LP: #1804755):
- CONTRIBUTING: Update reference to kernel coding style
- CONTRIBUTING: Link to latest online kernel docs
- CONTRIBUTING: Direct readers to CODING_STYLE.md
- CODING_STYLE: Mention kernel style in introduction
- CONTRIBUTING: Add 'be' to fix grammar
- CODING_STLYE: Simplify explanation for use of 'extern'
- CODING_STLYE: Remove sections implied by 'kernel style'
- CODING_STYLE: Fix non-uniform heading level
- CODING_STYLE: Update section header format
- cmd: Use parenthesis around complex macro
- cmd: Use 'void' instead of empty parameter list
- cmd: Do not use braces for single statement block
- cmd: Fix whitespace issues
- cmd: Use 'const' for static string constant.
- cmd: Remove unnecessary whitespace in string
- cmd: Put trailing */ on a separate line
- cmd: Remove typo'd semicolon
- cmd: Do not use comparison to NULL
- lxc_init: s/SYSDEBUG()/SYSERROR()/g in remove_self
- tools: lxc-attach: add default log priority & cleanups
- tools: lxc-cgroup: add default log priority & cleanups
- tools: lxc-checkpoint: add default log priority & cleanups
- tools: lxc-console: add default log priority & cleanups
- tools: lxc-create: add default log priority & cleanups
- tools: lxc-destroy: add default log priority & cleanups
- tools: lxc-device: add default log priority & cleanups
- tools: lxc-execute: add default log priority & cleanups
- tools: lxc-start: add default log priority & cleanups
- tools: lxc-stop: add default log priority & cleanups
- tools: lxc-freeze: add default log priority & cleanups
- tools: lxc-unfreeze: add default log priority & cleanups
- storage_utils: move duplicated function from tools
- tools: fix lxc-execute command parsing
- lseek - integer overflow
- cmd: lxc-user-nic: change log macro & cleanups
- cmd: lxc-usernsexec reorder includes
- cmd: move declarations to macro.h
- cmd: use utils.{c,h} helpers in lxc-usernsexec
- cmd: simplify lxc-usernsexec
- cmd: use safe number parsers in lxc-usernsexec
- macro: add missing headers
- macro: add macvlan properties
- tools: Indicate container startup failure
- storage: exit() => _exit(). when exec is failed
- tools: lxc-wait: add default log priority & cleanups
- conf: fix path/lxcpath mixups in tty setup
- cmd: use goto for cleanup in lxc-usernsexec
- cmd: Do not reassign variable before it is used
- cmd: Reduce scope of 'count' variable
- cmd: Fix format issues found by clang-format
- list: fix indent
- utils: split into {file,string}_utils.{c,h}
- pam_cgfs: build from the same sources as liblxc
- conf: fix devpts mounting when fully unprivileged
- macro: s/rexit()/_exit()/g
- attach: move struct declaration to top
- macro: move macros from attach.c
- Makefile: don't allow undefined symbols
- autotools: check if compiler is new enough
- log: handle strerror_r() versions
- autotools: add --{disable,enable}-thread-safety
- log: fail build on ENFORCE_THREAD_SAFETY error
- {file,string}_utils: remove NO_LOG
- initutils: remove useless comment
- string_utils: remove unnecessary include
- string_utils: remove unused headers
- string_utils: add remove_trailing_slashes()
- Makefile: remove last pam_cgfs special-casing
- conf: add missing headers
- Fix typo
- ifaddrs: add safe implementation of getifaddrs()
- Makefile: conditionalize ifaddrs.h inclusion
- execute: skip lxc-init logging when unprivileged
- execute: pass /proc/self/fd/
- tests: cleanup get_item.c
- build: fix musl
- configure: reorder header checks
- compiler: add compiler.h header
- commands: return -1 on lxc_cmd_get_init_pid() err
- tests: add basic.c
- tests: cleanup Makefile
- commands: ensure -1 is sent on EPIPE for init pid
- macro: add LXC_AUDS_ADDR_LEN
- macro: move LXC_CMD_DATA_MAX from commands.h
- macro: add PTR_TO_INT() and INT_TO_PTR()
- macro: add INTTYPE_TO_STRLEN()
- caps: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- cgfsng: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- confile: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- log: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- lsm: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- macro: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- lxccontainer: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- monitor: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- network: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- string_utils: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- utils: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- tools: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- conf: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- tests:
[Touch-packages] [Bug 1804755] Re: SRU of LXC 3.0.3 (upstream bugfix release)
This bug was fixed in the package lxc - 3.0.3-0ubuntu1~18.10.1
---
lxc (3.0.3-0ubuntu1~18.10.1) cosmic; urgency=medium
* New upstream bugfix release (LP: #1804755):
- CONTRIBUTING: Update reference to kernel coding style
- CONTRIBUTING: Link to latest online kernel docs
- CONTRIBUTING: Direct readers to CODING_STYLE.md
- CODING_STYLE: Mention kernel style in introduction
- CONTRIBUTING: Add 'be' to fix grammar
- CODING_STLYE: Simplify explanation for use of 'extern'
- CODING_STLYE: Remove sections implied by 'kernel style'
- CODING_STYLE: Fix non-uniform heading level
- CODING_STYLE: Update section header format
- cmd: Use parenthesis around complex macro
- cmd: Use 'void' instead of empty parameter list
- cmd: Do not use braces for single statement block
- cmd: Fix whitespace issues
- cmd: Use 'const' for static string constant.
- cmd: Remove unnecessary whitespace in string
- cmd: Put trailing */ on a separate line
- cmd: Remove typo'd semicolon
- cmd: Do not use comparison to NULL
- lxc_init: s/SYSDEBUG()/SYSERROR()/g in remove_self
- tools: lxc-attach: add default log priority & cleanups
- tools: lxc-cgroup: add default log priority & cleanups
- tools: lxc-checkpoint: add default log priority & cleanups
- tools: lxc-console: add default log priority & cleanups
- tools: lxc-create: add default log priority & cleanups
- tools: lxc-destroy: add default log priority & cleanups
- tools: lxc-device: add default log priority & cleanups
- tools: lxc-execute: add default log priority & cleanups
- tools: lxc-start: add default log priority & cleanups
- tools: lxc-stop: add default log priority & cleanups
- tools: lxc-freeze: add default log priority & cleanups
- tools: lxc-unfreeze: add default log priority & cleanups
- storage_utils: move duplicated function from tools
- tools: fix lxc-execute command parsing
- lseek - integer overflow
- cmd: lxc-user-nic: change log macro & cleanups
- cmd: lxc-usernsexec reorder includes
- cmd: move declarations to macro.h
- cmd: use utils.{c,h} helpers in lxc-usernsexec
- cmd: simplify lxc-usernsexec
- cmd: use safe number parsers in lxc-usernsexec
- macro: add missing headers
- macro: add macvlan properties
- tools: Indicate container startup failure
- storage: exit() => _exit(). when exec is failed
- tools: lxc-wait: add default log priority & cleanups
- conf: fix path/lxcpath mixups in tty setup
- cmd: use goto for cleanup in lxc-usernsexec
- cmd: Do not reassign variable before it is used
- cmd: Reduce scope of 'count' variable
- cmd: Fix format issues found by clang-format
- list: fix indent
- utils: split into {file,string}_utils.{c,h}
- pam_cgfs: build from the same sources as liblxc
- conf: fix devpts mounting when fully unprivileged
- macro: s/rexit()/_exit()/g
- attach: move struct declaration to top
- macro: move macros from attach.c
- Makefile: don't allow undefined symbols
- autotools: check if compiler is new enough
- log: handle strerror_r() versions
- autotools: add --{disable,enable}-thread-safety
- log: fail build on ENFORCE_THREAD_SAFETY error
- {file,string}_utils: remove NO_LOG
- initutils: remove useless comment
- string_utils: remove unnecessary include
- string_utils: remove unused headers
- string_utils: add remove_trailing_slashes()
- Makefile: remove last pam_cgfs special-casing
- conf: add missing headers
- Fix typo
- ifaddrs: add safe implementation of getifaddrs()
- Makefile: conditionalize ifaddrs.h inclusion
- execute: skip lxc-init logging when unprivileged
- execute: pass /proc/self/fd/
- tests: cleanup get_item.c
- build: fix musl
- configure: reorder header checks
- compiler: add compiler.h header
- commands: return -1 on lxc_cmd_get_init_pid() err
- tests: add basic.c
- tests: cleanup Makefile
- commands: ensure -1 is sent on EPIPE for init pid
- macro: add LXC_AUDS_ADDR_LEN
- macro: move LXC_CMD_DATA_MAX from commands.h
- macro: add PTR_TO_INT() and INT_TO_PTR()
- macro: add INTTYPE_TO_STRLEN()
- caps: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- cgfsng: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- confile: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- log: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- lsm: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- macro: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- lxccontainer: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- monitor: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- network: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- string_utils: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- utils: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- tools: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- conf: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- tests:
[Touch-packages] [Bug 1804755] Update Released
The verification of the Stable Release Update for lxc has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1804755
Title:
SRU of LXC 3.0.3 (upstream bugfix release)
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Xenial:
Triaged
Status in lxc source package in Bionic:
Fix Released
Status in lxc source package in Cosmic:
Fix Released
Status in lxc source package in Disco:
Fix Released
Bug description:
LXC upstream released LXC 3.0.3 as a bugfix release with following
changelog:
- CONTRIBUTING: Update reference to kernel coding style
- CONTRIBUTING: Link to latest online kernel docs
- CONTRIBUTING: Direct readers to CODING_STYLE.md
- CODING_STYLE: Mention kernel style in introduction
- CONTRIBUTING: Add 'be' to fix grammar
- CODING_STLYE: Simplify explanation for use of 'extern'
- CODING_STLYE: Remove sections implied by 'kernel style'
- CODING_STYLE: Fix non-uniform heading level
- CODING_STYLE: Update section header format
- cmd: Use parenthesis around complex macro
- cmd: Use 'void' instead of empty parameter list
- cmd: Do not use braces for single statement block
- cmd: Fix whitespace issues
- cmd: Use 'const' for static string constant.
- cmd: Remove unnecessary whitespace in string
- cmd: Put trailing */ on a separate line
- cmd: Remove typo'd semicolon
- cmd: Do not use comparison to NULL
- lxc_init: s/SYSDEBUG()/SYSERROR()/g in remove_self
- tools: lxc-attach: add default log priority & cleanups
- tools: lxc-cgroup: add default log priority & cleanups
- tools: lxc-checkpoint: add default log priority & cleanups
- tools: lxc-console: add default log priority & cleanups
- tools: lxc-create: add default log priority & cleanups
- tools: lxc-destroy: add default log priority & cleanups
- tools: lxc-device: add default log priority & cleanups
- tools: lxc-execute: add default log priority & cleanups
- tools: lxc-start: add default log priority & cleanups
- tools: lxc-stop: add default log priority & cleanups
- tools: lxc-freeze: add default log priority & cleanups
- tools: lxc-unfreeze: add default log priority & cleanups
- storage_utils: move duplicated function from tools
- tools: fix lxc-execute command parsing
- lseek - integer overflow
- cmd: lxc-user-nic: change log macro & cleanups
- cmd: lxc-usernsexec reorder includes
- cmd: move declarations to macro.h
- cmd: use utils.{c,h} helpers in lxc-usernsexec
- cmd: simplify lxc-usernsexec
- cmd: use safe number parsers in lxc-usernsexec
- macro: add missing headers
- macro: add macvlan properties
- tools: Indicate container startup failure
- storage: exit() => _exit(). when exec is failed, child process needs to
use _exit()
- tools: lxc-wait: add default log priority & cleanups
- conf: fix path/lxcpath mixups in tty setup
- cmd: use goto for cleanup in lxc-usernsexec
- cmd: Do not reassign variable before it is used
- cmd: Reduce scope of 'count' variable
- cmd: Fix format issues found by clang-format
- list: fix indent
- utils: split into {file,string}_utils.{c,h}
- pam_cgfs: build from the same sources as liblxc
- conf: fix devpts mounting when fully unprivileged
- macro: s/rexit()/_exit()/g
- attach: move struct declaration to top
- macro: move macros from attach.c
- Makefile: don't allow undefined symbols
- autotools: check if compiler is new enough
- log: handle strerror_r() versions
- autotools: add --{disable,enable}-thread-safety
- log: fail build on ENFORCE_THREAD_SAFETY error
- {file,string}_utils: remove NO_LOG
- initutils: remove useless comment
- string_utils: remove unnecessary include
- string_utils: remove unused headers
- string_utils: add remove_trailing_slashes()
- Makefile: remove last pam_cgfs special-casing
- conf: add missing headers
- Fix typo
- ifaddrs: add safe implementation of getifaddrs()
- Makefile: conditionalize ifaddrs.h inclusion
- execute: skip lxc-init logging when unprivileged
- execute: pass /proc/self/fd/
- tests: cleanup get_item.c
- build: fix musl
- configure: reorder header checks
- compiler: add compiler.h header
- commands: return -1 on lxc_cmd_get_init_pid() err
- tests: add basic.c
- tests: cleanup Makefile
- commands: ensure -1 is sent on EPIPE for init pid
- macro: add LXC_AUDS_ADDR_LEN
- macro: mo
[Touch-packages] [Bug 1804755] Re: SRU of LXC 3.0.3 (upstream bugfix release)
Updated a bionic and cosmic system, containers kept working fine, newly
started ones are good too.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic
verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1804755
Title:
SRU of LXC 3.0.3 (upstream bugfix release)
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Xenial:
Triaged
Status in lxc source package in Bionic:
Fix Released
Status in lxc source package in Cosmic:
Fix Released
Status in lxc source package in Disco:
Fix Released
Bug description:
LXC upstream released LXC 3.0.3 as a bugfix release with following
changelog:
- CONTRIBUTING: Update reference to kernel coding style
- CONTRIBUTING: Link to latest online kernel docs
- CONTRIBUTING: Direct readers to CODING_STYLE.md
- CODING_STYLE: Mention kernel style in introduction
- CONTRIBUTING: Add 'be' to fix grammar
- CODING_STLYE: Simplify explanation for use of 'extern'
- CODING_STLYE: Remove sections implied by 'kernel style'
- CODING_STYLE: Fix non-uniform heading level
- CODING_STYLE: Update section header format
- cmd: Use parenthesis around complex macro
- cmd: Use 'void' instead of empty parameter list
- cmd: Do not use braces for single statement block
- cmd: Fix whitespace issues
- cmd: Use 'const' for static string constant.
- cmd: Remove unnecessary whitespace in string
- cmd: Put trailing */ on a separate line
- cmd: Remove typo'd semicolon
- cmd: Do not use comparison to NULL
- lxc_init: s/SYSDEBUG()/SYSERROR()/g in remove_self
- tools: lxc-attach: add default log priority & cleanups
- tools: lxc-cgroup: add default log priority & cleanups
- tools: lxc-checkpoint: add default log priority & cleanups
- tools: lxc-console: add default log priority & cleanups
- tools: lxc-create: add default log priority & cleanups
- tools: lxc-destroy: add default log priority & cleanups
- tools: lxc-device: add default log priority & cleanups
- tools: lxc-execute: add default log priority & cleanups
- tools: lxc-start: add default log priority & cleanups
- tools: lxc-stop: add default log priority & cleanups
- tools: lxc-freeze: add default log priority & cleanups
- tools: lxc-unfreeze: add default log priority & cleanups
- storage_utils: move duplicated function from tools
- tools: fix lxc-execute command parsing
- lseek - integer overflow
- cmd: lxc-user-nic: change log macro & cleanups
- cmd: lxc-usernsexec reorder includes
- cmd: move declarations to macro.h
- cmd: use utils.{c,h} helpers in lxc-usernsexec
- cmd: simplify lxc-usernsexec
- cmd: use safe number parsers in lxc-usernsexec
- macro: add missing headers
- macro: add macvlan properties
- tools: Indicate container startup failure
- storage: exit() => _exit(). when exec is failed, child process needs to
use _exit()
- tools: lxc-wait: add default log priority & cleanups
- conf: fix path/lxcpath mixups in tty setup
- cmd: use goto for cleanup in lxc-usernsexec
- cmd: Do not reassign variable before it is used
- cmd: Reduce scope of 'count' variable
- cmd: Fix format issues found by clang-format
- list: fix indent
- utils: split into {file,string}_utils.{c,h}
- pam_cgfs: build from the same sources as liblxc
- conf: fix devpts mounting when fully unprivileged
- macro: s/rexit()/_exit()/g
- attach: move struct declaration to top
- macro: move macros from attach.c
- Makefile: don't allow undefined symbols
- autotools: check if compiler is new enough
- log: handle strerror_r() versions
- autotools: add --{disable,enable}-thread-safety
- log: fail build on ENFORCE_THREAD_SAFETY error
- {file,string}_utils: remove NO_LOG
- initutils: remove useless comment
- string_utils: remove unnecessary include
- string_utils: remove unused headers
- string_utils: add remove_trailing_slashes()
- Makefile: remove last pam_cgfs special-casing
- conf: add missing headers
- Fix typo
- ifaddrs: add safe implementation of getifaddrs()
- Makefile: conditionalize ifaddrs.h inclusion
- execute: skip lxc-init logging when unprivileged
- execute: pass /proc/self/fd/
- tests: cleanup get_item.c
- build: fix musl
- configure: reorder header checks
- compiler: add compiler.h header
- commands: return -1 on lxc_cmd_get_init_pid() err
- tests: add basic.c
- tests: cleanup Makefile
- commands: ensure -1 is sent on EPIPE for init pid
- macro: add LXC_AUDS_ADDR_LEN
- macro: move LXC_CMD_DATA_MAX from commands.h
- macro: add PTR_TO_INT() and INT_TO_PTR()
- macro: add INTTYPE_TO_STRLEN()
- caps: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- cgfsng: s/
[Touch-packages] [Bug 1808432] [NEW] systemctl template units not enabled per docs
Public bug reported: Report is for Description:Ubuntu 16.04.4 LTS Release:16.04 Package data is Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Multi-Arch: foreign No log file is applicable The problem is that systemctl enable does not perform according to documentation in enabling template unit files. If a template unit file exists /full_path_to/tmpl@.service and you try to enable it with systemctl per the docs sudo systemctl enable /full_path_to/tmpl@instance.service or systemctl --user enable /full_path_to/tmpl@instance.service you get the error Failed to execute operation: No such file or directory What should happen is that systemctl fails to find /full_path_to/tmpl@instance.service so it then tries the template name /full_path_to/tmpl@.service, finds it, and creates a symlink to that template file. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1808432 Title: systemctl template units not enabled per docs Status in systemd package in Ubuntu: New Bug description: Report is for Description: Ubuntu 16.04.4 LTS Release: 16.04 Package data is Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Multi-Arch: foreign No log file is applicable The problem is that systemctl enable does not perform according to documentation in enabling template unit files. If a template unit file exists /full_path_to/tmpl@.service and you try to enable it with systemctl per the docs sudo systemctl enable /full_path_to/tmpl@instance.service or systemctl --user enable /full_path_to/tmpl@instance.service you get the error Failed to execute operation: No such file or directory What should happen is that systemctl fails to find /full_path_to/tmpl@instance.service so it then tries the template name /full_path_to/tmpl@.service, finds it, and creates a symlink to that template file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808432/+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 1808428] [NEW] Ping of a link local address with -I as non-root produces "Invalid argument"
Public bug reported: iputils-ping 3:20161105-1ubuntu2 amd64 18.04.1 LTS In the following, "c7" is a host with the link-local address fe80::5054:ff:fe45:1e87. The mapping is in "/etc/hosts". It is reachable via the "enp2s0" interface on the local machine. I have masked the local machine's MAC address. 1. As a regular (non-root) user, ping returns "Invalid argument": $ ping -I enp2s0 c7 PING c7(c7 (fe80::5054:ff:fe45:1e87)) from fe80:::xxff:fexx:%enp2s0 enp2s0: 56 data bytes ping: sendmsg: Invalid argument ping: sendmsg: Invalid argument ping: sendmsg: Invalid argument 2. As root, ping works: # ping -I enp2s0 c7 PING c7(c7 (fe80::5054:ff:fe45:1e87)) from fe80:::xxff:fexx:%enp2s0 enp2s0: 56 data bytes 64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=1 ttl=64 time=0.285 ms 64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=2 ttl=64 time=0.306 ms 64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=3 ttl=64 time=0.307 ms 3. Specifying the interface-qualified IPv6 address directly works: $ ping fe80::5054:ff:fe45:1e87%enp2s0 PING fe80::5054:ff:fe45:1e87%enp2s0(fe80::5054:ff:fe45:1e87%enp2s0) 56 data bytes 64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=1 ttl=64 time=0.476 ms 64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=2 ttl=64 time=0.408 ms 64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=3 ttl=64 time=0.395 ms ** Affects: iputils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1808428 Title: Ping of a link local address with -I as non-root produces "Invalid argument" Status in iputils package in Ubuntu: New Bug description: iputils-ping 3:20161105-1ubuntu2 amd64 18.04.1 LTS In the following, "c7" is a host with the link-local address fe80::5054:ff:fe45:1e87. The mapping is in "/etc/hosts". It is reachable via the "enp2s0" interface on the local machine. I have masked the local machine's MAC address. 1. As a regular (non-root) user, ping returns "Invalid argument": $ ping -I enp2s0 c7 PING c7(c7 (fe80::5054:ff:fe45:1e87)) from fe80:::xxff:fexx:%enp2s0 enp2s0: 56 data bytes ping: sendmsg: Invalid argument ping: sendmsg: Invalid argument ping: sendmsg: Invalid argument 2. As root, ping works: # ping -I enp2s0 c7 PING c7(c7 (fe80::5054:ff:fe45:1e87)) from fe80:::xxff:fexx:%enp2s0 enp2s0: 56 data bytes 64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=1 ttl=64 time=0.285 ms 64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=2 ttl=64 time=0.306 ms 64 bytes from c7 (fe80::5054:ff:fe45:1e87%enp2s0): icmp_seq=3 ttl=64 time=0.307 ms 3. Specifying the interface-qualified IPv6 address directly works: $ ping fe80::5054:ff:fe45:1e87%enp2s0 PING fe80::5054:ff:fe45:1e87%enp2s0(fe80::5054:ff:fe45:1e87%enp2s0) 56 data bytes 64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=1 ttl=64 time=0.476 ms 64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=2 ttl=64 time=0.408 ms 64 bytes from fe80::5054:ff:fe45:1e87%enp2s0: icmp_seq=3 ttl=64 time=0.395 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1808428/+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 972077] Re: apt repository disk format has race conditions
If this is about not matching hashes from a apt-get-repository ppa, then I am affected by this. -- 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/972077 Title: apt repository disk format has race conditions Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+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 1808419] [NEW] Screen Brightness problem
Public bug reported: When i switch on my laptop with Ubuntu. It starts with lowest brightness. Even it set to normal. When i set it again it returning to normal. But when after screen dimming it does not return again. So it doesnt recognize to my mouse or keyboard. Sorry for my English. I hope I could explain my problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 14 02:43:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed nvidia, 390.48, 4.15.0-34-generic, x86_64: installed nvidia, 390.48, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04ca] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04ca] InstallationDate: Installed on 2018-09-30 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron N5110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4a66061d-c599-4959-97d9-eee379ba8b99 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0HVRTT dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0HVRTT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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/1808419 Title: Screen Brightness problem Status in xorg package in Ubuntu: New Bug description: When i switch on my laptop with Ubuntu. It starts with lowest brightness. Even it set to normal. When i set it again it returning to normal. But when after screen dimming it does not return again. So it doesnt recognize to my mouse or keyboard. Sorry for my English. I hope I could explain my problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 14 02:43:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed
[Touch-packages] [Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications
** Changed in: gtk+3.0 (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1798861 Title: Tooltips flicker constantly in GTK3 applications Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 package in Debian: Fix Released Bug description: Tooltips are flicker constantly (i.e. repeatedly shown and the hidden again) in GTK3 applications under XFCE. It is a regression in the recent GTK 3.24. This is the upstream report and fix: https://gitlab.gnome.org/GNOME/gtk/issues/1371 https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2 A workaround for XFCE is as follows: Open Settings Editor. Set xsettings -> Gtk -> CursorThemeSize to 16. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgtk-3-0 3.24.1-1ubuntu2 Uname: Linux 4.19.0-041900rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 12:23:53 2018 InstallationDate: Installed on 2017-02-01 (624 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+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 1795651] Re: ICU data package is grossly outdated
** Changed in: icu (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1795651 Title: ICU data package is grossly outdated Status in icu package in Ubuntu: New Status in icu package in Debian: New Bug description: The data package compiled into supplied ICU libs is extremely out of date. I.e. the timezone information in libicu52 (Ubuntu 14) is as old as 2013g. The "newest" shipped tzdata in Bionic is 2017c, which is about as "new" as the one in Trusty. Means, pretty much rotten by now. It wouldn't be so hard to override it with env. vars, if not for applications, which intentionally clear environments at startup. F.e. PHP FPM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1795651/+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 1808203] Re: ddfs
** Information type changed from Private Security to Public -- 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/1808203 Title: ddfs Status in xorg package in Ubuntu: New Bug description: sdfsf ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Dec 12 21:07:13 2018 DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad] InstallationDate: Installed on 2016-04-24 (962 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Sony Corporation SVE1112M1EW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-12 (0 days ago) dmi.bios.date: 08/22/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0120D8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE1112M1EW dmi.product.version: C60B8BEP dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Dec 12 18:07:04 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1808203/+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 1167053] Re: untrusted packages silently added to blacklist
This bug was fixed in the package unattended-upgrades - 1.9
---
unattended-upgrades (1.9) unstable; urgency=medium
[ Julian Andres Klode ]
* test_dev_release: Fix and enable test.
* Depend on python3-distro-info.
This is needed to make sure DEVEL_UNTIL_RELEASE actually works. We need
to fix up travis in addition to control, as it only knows about trusty
build dependencies.
* Import distro_info globally, and fix calculation of days.
The check was off by one: If you were 21 days away from the release,
it would not switch on, but tell you that it would not upgrade before
today.
* test_dev_release: Test Unattended-Upgrade::DevRelease=auto.
[ David Lang and Balint Reczey]
* Allow installing untrusted packages when APT::Get::AllowUnauthenticated
is set (Closes: #775469) (LP: #1167053)
[ Hans van Kranenburg and Balint Reczey]
* Clarify highly misleading Package-Blacklist option documentation
(Closes: #753892)
[ Balint Reczey ]
* test/test_dev_release.py: Fix missing mock attributes
* Leave the cache clean when returning from calculate_upgradable_pkgs()
When collecting upgradable packages the upgradable ones stayed in the
cache and they were upgraded together even when unattended-upgrades
was configured to perform upgrades in minimal steps.
Thanks to Paul Wise
* debian/tests/upgrade-all-security: Check if all security-updates are
applied and if old-autoremovable packages are kept
* Clear cache only when needed when checking black- and whitelists
* Add --no-minimal-upgrade-steps option
* Stop using untrusted package names as blacklists (LP: #1805447)
* Update copyright info
* Load modules lazily loaded by datetime.datetime.strptime() when u-u starts
When Python is upgraded to a new major version the the version running
unattended-upgrades can be removed as being newly unused causing a crash.
* Start service after systemd-logind.service to be able to take inhibition
lock
and handle gracefully when logind is down (LP: #1806487)
* List packages making reboot required in /var/run/reboot-required.pkgs
-- Balint Reczey Wed, 12 Dec 2018 13:41:49 +0100
** Changed in: unattended-upgrades (Ubuntu)
Status: Confirmed => Fix Released
--
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/1167053
Title:
untrusted packages silently added to blacklist
Status in unattended-upgrades package in Ubuntu:
Fix Released
Bug description:
Packages that are not trusted are added to the blacklist but no reason
is ever printed out while running in debug mode causing confusion as
to why a package would be blacklisted until you dig into the source.
Release: All versions
Package: All versions
Expected behavior: Print out debug message that informs user package was
blacklisted due to not being trusted
Actual behavior: Message saying package is blacklisted without reason
Still trying to figure out how to properly upload a patch to this, but
basically just adding
logging.debug("%s blacklisted because it's not trusted" %
pkgname_from_deb(item.destfile))
to line 946 would suffice
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1167053/+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 1806487] Re: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet)
This bug was fixed in the package unattended-upgrades - 1.9 --- unattended-upgrades (1.9) unstable; urgency=medium [ Julian Andres Klode ] * test_dev_release: Fix and enable test. * Depend on python3-distro-info. This is needed to make sure DEVEL_UNTIL_RELEASE actually works. We need to fix up travis in addition to control, as it only knows about trusty build dependencies. * Import distro_info globally, and fix calculation of days. The check was off by one: If you were 21 days away from the release, it would not switch on, but tell you that it would not upgrade before today. * test_dev_release: Test Unattended-Upgrade::DevRelease=auto. [ David Lang and Balint Reczey] * Allow installing untrusted packages when APT::Get::AllowUnauthenticated is set (Closes: #775469) (LP: #1167053) [ Hans van Kranenburg and Balint Reczey] * Clarify highly misleading Package-Blacklist option documentation (Closes: #753892) [ Balint Reczey ] * test/test_dev_release.py: Fix missing mock attributes * Leave the cache clean when returning from calculate_upgradable_pkgs() When collecting upgradable packages the upgradable ones stayed in the cache and they were upgraded together even when unattended-upgrades was configured to perform upgrades in minimal steps. Thanks to Paul Wise * debian/tests/upgrade-all-security: Check if all security-updates are applied and if old-autoremovable packages are kept * Clear cache only when needed when checking black- and whitelists * Add --no-minimal-upgrade-steps option * Stop using untrusted package names as blacklists (LP: #1805447) * Update copyright info * Load modules lazily loaded by datetime.datetime.strptime() when u-u starts When Python is upgraded to a new major version the the version running unattended-upgrades can be removed as being newly unused causing a crash. * Start service after systemd-logind.service to be able to take inhibition lock and handle gracefully when logind is down (LP: #1806487) * List packages making reboot required in /var/run/reboot-required.pkgs -- Balint Reczey Wed, 12 Dec 2018 13:41:49 +0100 ** Changed in: unattended-upgrades (Ubuntu) Status: New => Fix Released -- 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/1806487 Title: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) 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 Committed Bug description: [Impact] * Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start. * Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process. * The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence. [Test Case] * Stop systemd-logind and make it unable to start for example by masking it: root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload root@bb-logind:~# service systemd-logind stop root@bb-logind:~# service systemd-logind status ● systemd-logind.service Loaded: masked (/dev/null; bad) Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago Main PID: 1938 (code=killed, signal=TERM) Status: "Processing requests..." ... * Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start: root@bb-logind:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log ... 2018-12-13 14:30:17,600 WARNING - Could not get delay inhibitor lock 2018-12-13 14:30:17,601 DEBUG - Skip waiting for signals, starting operation now 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken * Restore logind's ability to start root@bb-logind:~# rm /etc/systemd/system/systemd-logind.service root@bb-logind:~#
[Touch-packages] [Bug 1805447] Re: Untrusted package names are mishandled as blacklist regexps
This bug was fixed in the package unattended-upgrades - 1.9 --- unattended-upgrades (1.9) unstable; urgency=medium [ Julian Andres Klode ] * test_dev_release: Fix and enable test. * Depend on python3-distro-info. This is needed to make sure DEVEL_UNTIL_RELEASE actually works. We need to fix up travis in addition to control, as it only knows about trusty build dependencies. * Import distro_info globally, and fix calculation of days. The check was off by one: If you were 21 days away from the release, it would not switch on, but tell you that it would not upgrade before today. * test_dev_release: Test Unattended-Upgrade::DevRelease=auto. [ David Lang and Balint Reczey] * Allow installing untrusted packages when APT::Get::AllowUnauthenticated is set (Closes: #775469) (LP: #1167053) [ Hans van Kranenburg and Balint Reczey] * Clarify highly misleading Package-Blacklist option documentation (Closes: #753892) [ Balint Reczey ] * test/test_dev_release.py: Fix missing mock attributes * Leave the cache clean when returning from calculate_upgradable_pkgs() When collecting upgradable packages the upgradable ones stayed in the cache and they were upgraded together even when unattended-upgrades was configured to perform upgrades in minimal steps. Thanks to Paul Wise * debian/tests/upgrade-all-security: Check if all security-updates are applied and if old-autoremovable packages are kept * Clear cache only when needed when checking black- and whitelists * Add --no-minimal-upgrade-steps option * Stop using untrusted package names as blacklists (LP: #1805447) * Update copyright info * Load modules lazily loaded by datetime.datetime.strptime() when u-u starts When Python is upgraded to a new major version the the version running unattended-upgrades can be removed as being newly unused causing a crash. * Start service after systemd-logind.service to be able to take inhibition lock and handle gracefully when logind is down (LP: #1806487) * List packages making reboot required in /var/run/reboot-required.pkgs -- Balint Reczey Wed, 12 Dec 2018 13:41:49 +0100 ** Changed in: unattended-upgrades (Ubuntu) Status: New => Fix Released -- 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/1805447 Title: Untrusted package names are mishandled as blacklist regexps Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: ... if not item.is_trusted: blacklisted_pkgs.append(pkgname_from_deb(item.destfile)) ... check_changes_for_sanity(..., blacklisted_pkgs, ...) ... is_pkg_change_allowed(pkg, blacklist, whitelist) ... if is_pkgname_in_blacklist(pkg.name, blacklist): ... for blacklist_regexp in blacklist: if re.match(blacklist_regexp, pkgname): To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1805447/+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 1808360] Re: AppArmor fails after MySQL installation using 18.04.1 LTS
Didn't meant to have the tags ( and ) -- 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/1808360 Title: AppArmor fails after MySQL installation using 18.04.1 LTS Status in apparmor package in Ubuntu: New Bug description: This is run and returned under root. 08:12 ~: aa-complain /etc/apparmor.d ERROR: Include file /etc/apparmor.d/abstractions/mysql not found 08:18 ~: apt-cache policy apparmor.d libapparmor-dev: Installed: (none) Candidate: 2.12-4ubuntu5.1 Version table: 2.12-4ubuntu5.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.12-4ubuntu5 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1808360/+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 1808360] Re: AppArmor fails after MySQL installation using 18.04.1 LTS
I created a file /etc/apparmor.d/abstractions/mysql and inserted the
folowing:
# --
#
#Copyright (C) 2002-2006 Novell/SUSE
#Copyright (C) 2013 Christian Boltz
#
#This program is free software; you can redistribute it and/or
#modify it under the terms of version 2 of the GNU General Public
#License published by the Free Software Foundation.
#
# --
/var/lib/mysql{,d}/mysql{,d}.sock rw,
/{var/,}run/mysql{,d}/mysql{,d}.sock rw,
/usr/share/{mysql,mysql-community-server,mariadb}/charsets/ r,
/usr/share/{mysql,mysql-community-server,mariadb}/charsets/*.xml r,
--
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/1808360
Title:
AppArmor fails after MySQL installation using 18.04.1 LTS
Status in apparmor package in Ubuntu:
New
Bug description:
This is run and returned under root.
08:12 ~: aa-complain /etc/apparmor.d
ERROR: Include file /etc/apparmor.d/abstractions/mysql not found
08:18 ~: apt-cache policy apparmor.d
libapparmor-dev:
Installed: (none)
Candidate: 2.12-4ubuntu5.1
Version table:
2.12-4ubuntu5.1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
2.12-4ubuntu5 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1808360/+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 1806660]
I really do not know. In Windows 10 it works well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806660 Title: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids Status in Linux: Confirmed Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hello, The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids. In the upper part of gnome-shell it appears that they are with the headphones, and it is not like that. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2784 F pulseaudio /dev/snd/pcmC0D0p: caravena 2784 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 07:59:27 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806660/+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 1806660]
!! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Wed Dec 12 18:48:09 UTC 2018 http://www.alsa- project.org/db/?f=697ac07e0a3265eb4d04b32bc0114e1eaf1119ee -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806660 Title: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids Status in Linux: Confirmed Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hello, The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids. In the upper part of gnome-shell it appears that they are with the headphones, and it is not like that. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2784 F pulseaudio /dev/snd/pcmC0D0p: caravena 2784 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 07:59:27 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806660/+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 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Hi, same issue here in bionic 18.04 LTS on btrs subvolumes with the following systemd releases: *** 237-3ubuntu10.10 100 -10 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.9 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages How can we apply the patch also in bionic? Regards Luca -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+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 1726856] Re: ufw does not start automatically at boot
For those experiencing this issue, can you adjust /lib/ufw/ufw-init to use this: #!/bin/sh -x on its first line instead of: #!/bin/sh Then reboot and until you see the issue. When you do, please use `journalctl --no-pager --unit=ufw` and attach the results. Thanks! ** Changed in: ufw Status: Triaged => Incomplete ** Changed in: ufw Assignee: Jamie Strandboge (jdstrand) => (unassigned) ** Changed in: ufw (Ubuntu) Assignee: Jamie Strandboge (jdstrand) => (unassigned) ** Changed in: ufw (Ubuntu Xenial) Assignee: Jamie Strandboge (jdstrand) => (unassigned) ** Changed in: ufw (Ubuntu Artful) Assignee: Jamie Strandboge (jdstrand) => (unassigned) ** Changed in: ufw (Ubuntu Bionic) Assignee: Jamie Strandboge (jdstrand) => (unassigned) ** Changed in: ufw (Ubuntu Cosmic) Assignee: Jamie Strandboge (jdstrand) => (unassigned) ** No longer affects: ufw (Ubuntu Artful) ** Changed in: ufw (Ubuntu) Status: Triaged => Incomplete ** Changed in: ufw (Ubuntu Xenial) Status: Triaged => Incomplete ** Changed in: ufw (Ubuntu Bionic) Status: Triaged => Incomplete ** Changed in: ufw (Ubuntu Cosmic) Status: Triaged => New ** Changed in: ufw (Ubuntu Bionic) Status: Incomplete => New ** Changed in: ufw (Ubuntu Xenial) Status: Incomplete => New ** Changed in: ufw (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot Status in ufw: Incomplete Status in ufw package in Ubuntu: New Status in ufw source package in Xenial: New Status in ufw source package in Bionic: New Status in ufw source package in Cosmic: New Bug description: Whenever I boot into 17.10 ufw is always inactive, even though /etc/ufw/ufw.conf has this: # Set to yes to start on boot. If setting this remotely, be sure to add a rule # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp' ENABLED=yes ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ufw 0.35-5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 13:56:40 2017 InstallationDate: Installed on 2015-04-01 (936 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170 To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+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 1368411] Re: Cannot insert IPV6 rule before IPV4 rules
** Changed in: ufw (Ubuntu) Status: Confirmed => Triaged ** Changed in: ufw (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Also affects: ufw (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ufw (Ubuntu Disco) Importance: Medium Assignee: Jamie Strandboge (jdstrand) Status: Triaged ** Also affects: ufw (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ufw (Ubuntu Bionic) Status: New => Triaged ** Changed in: ufw (Ubuntu Cosmic) Status: New => Triaged ** Changed in: ufw (Ubuntu Cosmic) Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Changed in: ufw (Ubuntu Bionic) Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Changed in: ufw (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: ufw (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1368411 Title: Cannot insert IPV6 rule before IPV4 rules Status in ufw: Fix Committed Status in ufw package in Ubuntu: Triaged Status in ufw source package in Bionic: Triaged Status in ufw source package in Cosmic: Triaged Status in ufw source package in Disco: Triaged Status in ufw package in Debian: New Bug description: I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered 6 to 10, the following command: [code] ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] errors with "ERROR: Invalid position '1'". However, the command [code] ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] succeeds. In my case, this poses a problem, since I am trying to insert rules from a script against brute force attacks. The script needs to insert blocking rules before a number of other rules that open up some ports (since the order of rules is important in ufw). However since the number of IPV4 rules will be changing all the time, the position of the first available number for an IPV6 address is hard to determine. Proposed solution: either allow IPV6 rules to precede IPV4 rules, or implement a keyword defining the first available position; e.g. "ufw insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1". BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu 12.04.5 LTS, To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+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 1808393] Re: libedit 3.1-20181209-1 causes php7.3 to FTBFS
This might be fixed by patching php7.3 of course. We're still looking into it. ** Changed in: libedit (Ubuntu) Status: New => In Progress ** Changed in: libedit (Ubuntu) Assignee: (unassigned) => Karl Stenerud (kstenerud) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. https://bugs.launchpad.net/bugs/1808393 Title: libedit 3.1-20181209-1 causes php7.3 to FTBFS Status in libedit package in Ubuntu: In Progress Bug description: php7.3 7.3.0-1 did previously build in Launchpad, but doesn't rebuild unless I manually drop the Build-Depends for libedit-dev to force 3.1-20180525-1 from the release pocket to be used. Since we noticed this before proposed migration I'm adding a block since it causes a known regression in the release pocket. If this is the wrong thing to do, let's discuss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1808393/+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 1808393] [NEW] libedit 3.1-20181209-1 causes php7.3 to FTBFS
Public bug reported: php7.3 7.3.0-1 did previously build in Launchpad, but doesn't rebuild unless I manually drop the Build-Depends for libedit-dev to force 3.1-20180525-1 from the release pocket to be used. Since we noticed this before proposed migration I'm adding a block since it causes a known regression in the release pocket. If this is the wrong thing to do, let's discuss. ** Affects: libedit (Ubuntu) Importance: Undecided Assignee: Karl Stenerud (kstenerud) Status: In Progress ** Tags: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. https://bugs.launchpad.net/bugs/1808393 Title: libedit 3.1-20181209-1 causes php7.3 to FTBFS Status in libedit package in Ubuntu: In Progress Bug description: php7.3 7.3.0-1 did previously build in Launchpad, but doesn't rebuild unless I manually drop the Build-Depends for libedit-dev to force 3.1-20180525-1 from the release pocket to be used. Since we noticed this before proposed migration I'm adding a block since it causes a known regression in the release pocket. If this is the wrong thing to do, let's discuss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1808393/+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 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo
** Description changed: [Impact] kubernetes loaded inactive dead transient mount points grows https://github.com/kubernetes/kubernetes/issues/57345 [Test Case] # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test Expected outcome (w/ the fix) : # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test [Regression Potential] This is a adapted version of 2 upstream fixes as the original upstream commit has been made on top on 2 functions mount_setup_new_unit() & mount_setup_existing_unit() that not yet exist systemd 229. It is easily adaptable because the current function mount_setup_unit() is dealing with both of at the moment instead of being individually separate in two distinct function. It is an adaptation of commits : [65d36b495] core: Fix edge case when processing /proc/self/mountinfo [03b8cfede] core: make sure to init mount params before calling mount_is_extrinsic() This patch changes mount_setup_unit() to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialised properly. Additionally, the patch got the blessing of 'xnox' who looked at it and mention it looks fine to him. [Pending SRU] * Regression in autopkgtest for nplan (s390x): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz modprobe: FATAL: Module cfg80211 not found in directory /lib/modules/4.4.0-138-generic This above seems to be a recurrent failure since a couple of release already. This wasn't introduce by this particular SRU. + I don't think having wifi module is relevant in s390x anyway, so most + likely the module is not there on purpose for s390x architecture. + * Regression in autopkgtest for systemd (s390x): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/s/systemd/20181213_162040_4f06f@/log.gz FileNotFoundError: [Errno 2] No such file or directory: '/boot/grub/grub.cfg' This above seems to be a recurrent failure since a couple of release already. This wasn't introduce by this particular SRU. * Regression in autopkgtest for umockdev (i386): test log * * * * [Other Info] One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 systemd v237 has this fix, but we'd like to have it fixed in 16.04. It only affect systemd for Xenial, later release already has the fix: $ git describe --contains 65d36b495 v237~140 ==> systemd | 229-4ubuntu21.4 | xenial-updates systemd | 237-3ubuntu10.3 | bionic-updates systemd | 239-7ubuntu9 | cosmic [Original Description] From the PR: Currently, if there are two /proc/self/mountinfo entries with the same mount point path, the mount setup flags computed for the second of these two entries will overwrite the mount setup flags computed for the first of these two entries. This is the root cause of issue #7798. This patch changes mount_setup_existing_unit to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialized properly. One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 ** Description changed: [Impact] kubernetes loaded inactive dead transient mount points grows https://github.com/kubernetes/kubernetes/issues/57345 [Test Case] # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test Expected outcome (w/ the fix) : # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep
[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo
** Description changed: [Impact] kubernetes loaded inactive dead transient mount points grows https://github.com/kubernetes/kubernetes/issues/57345 [Test Case] # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test Expected outcome (w/ the fix) : # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test [Regression Potential] This is a adapted version of 2 upstream fixes as the original upstream commit has been made on top on 2 functions mount_setup_new_unit() & mount_setup_existing_unit() that not yet exist systemd 229. It is easily adaptable because the current function mount_setup_unit() is dealing with both of at the moment instead of being individually separate in two distinct function. It is an adaptation of commits : [65d36b495] core: Fix edge case when processing /proc/self/mountinfo [03b8cfede] core: make sure to init mount params before calling mount_is_extrinsic() This patch changes mount_setup_unit() to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialised properly. Additionally, the patch got the blessing of 'xnox' who looked at it and mention it looks fine to him. [Pending SRU] * Regression in autopkgtest for nplan (s390x): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz modprobe: FATAL: Module cfg80211 not found in directory /lib/modules/4.4.0-138-generic This above seems to be a recurrent failure since a couple of release already. This wasn't introduce by this particular SRU. + * Regression in autopkgtest for systemd (s390x): test log + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/s/systemd/20181213_162040_4f06f@/log.gz + + FileNotFoundError: [Errno 2] No such file or directory: + '/boot/grub/grub.cfg' + + This above seems to be a recurrent failure since a couple of release + already. This wasn't introduce by this particular SRU. * Regression in autopkgtest for umockdev (i386): test log - * * * * - [Other Info] One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 systemd v237 has this fix, but we'd like to have it fixed in 16.04. It only affect systemd for Xenial, later release already has the fix: $ git describe --contains 65d36b495 v237~140 ==> systemd | 229-4ubuntu21.4 | xenial-updates systemd | 237-3ubuntu10.3 | bionic-updates systemd | 239-7ubuntu9 | cosmic [Original Description] From the PR: Currently, if there are two /proc/self/mountinfo entries with the same mount point path, the mount setup flags computed for the second of these two entries will overwrite the mount setup flags computed for the first of these two entries. This is the root cause of issue #7798. This patch changes mount_setup_existing_unit to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialized properly. One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 -- 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/1795764 Title: systemd: core: Fix edge case when processing /proc/self/mountinfo Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] kubernetes loaded inactive dead transient mount points grows https://github.com/kubernetes/kubernetes/issues/57345 [Test Case] # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
yes, i also got `command not found` when running `fakeroot` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo
** Description changed: [Impact] kubernetes loaded inactive dead transient mount points grows https://github.com/kubernetes/kubernetes/issues/57345 [Test Case] # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test Expected outcome (w/ the fix) : # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test [Regression Potential] This is a adapted version of 2 upstream fixes as the original upstream commit has been made on top on 2 functions mount_setup_new_unit() & mount_setup_existing_unit() that not yet exist systemd 229. It is easily adaptable because the current function mount_setup_unit() is dealing with both of at the moment instead of being individually separate in two distinct function. It is an adaptation of commits : [65d36b495] core: Fix edge case when processing /proc/self/mountinfo [03b8cfede] core: make sure to init mount params before calling mount_is_extrinsic() This patch changes mount_setup_unit() to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialised properly. Additionally, the patch got the blessing of 'xnox' who looked at it and mention it looks fine to him. + [Pending SRU] + + * Regression in autopkgtest for nplan (s390x): test log + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz + + modprobe: FATAL: Module cfg80211 not found in directory /lib/modules/4.4.0-138-generic + modprobe: FATAL: Module cfg80211 not found in directory /lib/modules/4.4.0-138-generic + ERROR + ERROR + + This above seems to be a recurrent failure since a couple of release + already. This wasn't introduce by this particular SRU. + [Other Info] One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 systemd v237 has this fix, but we'd like to have it fixed in 16.04. It only affect systemd for Xenial, later release already has the fix: $ git describe --contains 65d36b495 v237~140 ==> systemd | 229-4ubuntu21.4 | xenial-updates systemd | 237-3ubuntu10.3 | bionic-updates systemd | 239-7ubuntu9 | cosmic [Original Description] From the PR: Currently, if there are two /proc/self/mountinfo entries with the same mount point path, the mount setup flags computed for the second of these two entries will overwrite the mount setup flags computed for the first of these two entries. This is the root cause of issue #7798. This patch changes mount_setup_existing_unit to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialized properly. One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 ** Description changed: [Impact] kubernetes loaded inactive dead transient mount points grows https://github.com/kubernetes/kubernetes/issues/57345 [Test Case] # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test Expected outcome (w/ the fix) : # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test [Regression Potential] This is a adapted version of 2 upstream fixes as the original upstream commit has been made on top on 2 functions mount_setup_new_unit() & mount_setup_existing_unit() that not yet exist systemd 229. It is easily adaptable because the current function mount_setup_unit() is dealing with both of at the moment instead of being individually separate in two distinct function. It is an adaptation of commits : [65d36b495] core: Fix edge case
[Touch-packages] [Bug 1807373] Re: /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed
** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1807373 Title: /usr/bin/software-properties- gtk:AttributeError:on_driver_selection_changed Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: New Status in software-properties source package in Cosmic: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 1.92.36bodhi1, the problem page at https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650 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/software-properties/+bug/1807373/+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] Please test proposed package
Hello Ernst, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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 1602536] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.
--
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 1260041] Please test proposed package
Hello avius, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1260041 Title: Unattended-Upgrades crashes with a dpkg error 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 upgrading packages in the middle of a dpkg/apt call due to a parallel process acquiring apt or dpkg lock while u-u is running, but u-u running apt/dpkg anyway without successfully re-acquiring the lock. * The fix is stopping processing updates when the lock is detected to be lost. [Test Case] * Set up a system with packages (> 30) to be upgraded: $ lxc launch ubuntu:b36ec647e374 uu-lock-bail * 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 installing the updates run the following command in shell "B": $ while sleep 0.1; do python3 -c 'import apt, apt_pkg, time; print(apt_pkg.pkgsystem_lock()); time.sleep(2)' ; done * With not fixed u-u observe the following exception repeated in shell "B", then True being printed when the lock is successfully stolen from u-u: ... 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 ... Buggy u-u continues operation even after the lock is stolen. Fixed u-u stops operation with a printout similar to the following when it detects the lock to be stolen: ... Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log /usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure /var/cache/apt/archives/distro-info-data_0.37ubuntu0.1_all.deb /usr/bin/dpkg --status-fd 9 --configure --pending Exception happened during upgrade. Traceback (most recent call last): File "./unattended-upgrade", line 539, in cache_commit res = cache.commit(install_progress=iprogress) File "./unattended-upgrade", line 360, in __exit__ apt_pkg.pkgsystem_lock() 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? Exception happened during upgrade. NoneType: None Installing the upgrades failed! error message: 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? dpkg returned a error! See /var/log/unattended-upgrades/unattended-upgrades-dpkg.log for details ... [Regression Potential] * As a consequence of the fix unattended-upgrade stops installing security-updates when an other dpkg frontend's parallel activity is detected.
[Touch-packages] [Bug 1446552] Please test proposed package
Hello Sjoerd, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1446552 Title: Unattended upgrades handles new dependencies inconsistently Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: [Impact] When an installed package adds a dependency that is not yet installed on the system, this sometimes causes the package to not be installed, depending on the origin containing the original candidate version. I believe that the problem is in /usr/bin/unattended-upgrade, line 102. Here a check is performed to prevent downgrades. However, as a side effect it also prevents adjusting the candidate version for packages that have not yet been installed (because pkg.is_upgradable is False for packages that have not been installed). This makes updating private packages using unattended-upgrades troublesome, especially when new dependencies have been added. Currently it requires repackaging the dependencies with a slightly higher version number than what is in the main repository, and then hosting them on the private repository, which is time consuming and error-prone. With the included patch, it is sufficient to just host the same version on the private repository. [Test Case] - Create a testing package (doesn't have to really contain anything) that just installs 1 file into /usr/share/testpackage/, and have it depend on some packages. - Put that package on a private repository (which is also configured for APT and unattended-upgrades) - Install the package using `apt-get install testingpackage` - Update the package as follows: 1. Add a dependency which is not yet installed on your machine (and is also not in the security-repository). Up the version number, and add it to the private repository. - Run `unattended-upgrade --debug --apt-debug 2>&1 | tee output.txt`. - Verify the package was not updated (missing dependency). - Host the dependency on your private APT server as well (1-1 copy). - Run `unattended-upgrade --debug --apt-debug 2>&1 | tee output.txt`. - Verify the package was not updated (missing dependency). - Re-build the dependency with a higher version number, and add it to your private APT repository. - Run `unattended-upgrade --debug --apt-debug 2>&1 | tee output.txt`. - Verify the package was now upgraded. With the proposed patch, the upgrade would already succeed after hosting the exact copy on the private APT repository. [Regression Potential] The changed code logic now allows adjusting candidates of packages which are not upgradable and not installed. Since the changed check was there to avoid downgrades the possible regression would be somehow enabling downgrades accidentally. Adjusting _not_ installed packages in itself would not cause downgrading installed packages thus the change seems to be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1446552/+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] Please test proposed package
Hello Jarno, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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 apt package in Ubuntu: Confirmed Status in gnome-software package in Ubuntu: Invalid 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 apt source package in Artful: Confirmed Status in gnome-software source package in Artful: Invalid 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 b
[Touch-packages] [Bug 1615381] Please test proposed package
Hello Jarno, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/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 1230246] Please test proposed package
Hello Lee, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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 1577215] Please test proposed package
Hello Mark, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.
--
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 1455097] Please test proposed package
Hello Alex, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1455097
Title:
/etc/pm/sleep.d/ is no more processed
Status in aiccu package in Ubuntu:
Invalid
Status in ceph package in Ubuntu:
Fix Released
Status in grub2 package in Ubuntu:
New
Status in ifplugd package in Ubuntu:
New
Status in lizardfs package in Ubuntu:
New
Status in oss4 package in Ubuntu:
New
Status in pm-utils package in Ubuntu:
Won't Fix
Status in toshset package in Ubuntu:
New
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Bug description:
[Impact (unattended-upgrades)]
* Unattended-upgrades does not gracefully stop installing updates
when the system goes to hibernation potentially letting the system to
hibernate in a state where the system can't resume from.
[Test Case (unattended-upgrades)]
* Configure the system to have several 20+ packages upgradable by
unattended-upgrades. One easy way of setting this up is starting with
a system where packages from -security are installed but packages from
-updates are not and enabling -updates in u-u:
# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' > /etc/apt/apt.conf.d
/51unattended-upgrades-updates-too
* Pre-download upgrades
# unattended-upgraded --download-only
* Trigger unattended-upgrades run:
# service apt-daily-upgrade start
* Hibernate, then resume the system and watch unattended-upgrades
being gracefully stopped, checking /var/log/unattended-upgrades
/unattended-upgrades.log. There should be packages left to be
upgraded.
[Regression Potential (unattended-upgrades)]
* The added hook for unattended-upgrades may block the system from
hibernation for 25 minutes if unattended-upgrades (or most likely a
package upgrades) hangs. There is a better solution proposed based on
systemd's inhibitor interface at https://github.com/mvo5/unattended-
upgrades/issues/162 .
[Original Bug Text]
I added a new script in /etc/pm/sleep.d/ that worked fine before the
upgrade to vivid. I was wondering why it doesn't work and I find out
that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last
logs from pm-suspend were on Apr 28, when I upgraded from utopic to
vivid.
The laptop suspends and wakes fine, it just seems that no pm scripts
are run after suspend/powersave.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: pm-utils 1.4.1-15
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 14 15:36:26 2015
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-precise-amd64-20120703-2
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-03-12 (792 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary
20120703-15:08
PackageArchitecture: all
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1455097/+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] Please test proposed package
Hello Daniel, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed 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 Committed Status in linux source package in Artful: Won't Fix 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.boa
[Touch-packages] [Bug 1654070] Please test proposed package
Hello Brian, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1654070 Title: sanity check can fail for packages missing dependencies Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: I've been getting mail for days about pulseaudio-module-gconf and -module-zeroconf being upgraded, come to find out its not really happening. bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose Initial blacklisted packages: nvidia-304 Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] Checking: pulseaudio-module-gconf ([]) Checking: pulseaudio-module-zeroconf ([]) pkgs that look like they should be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: ['nvidia-304'] whitelist: [] Checking the black and whitelist: pulseaudio-module-gconf Checking the black and whitelist: pulseaudio-module-zeroconf Packages that will be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' All upgrades installed InstCount=0 DelCount=0 BrokenCount=0 Extracting content from '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 12:27:12' Sending mail to 'bdmurray@bizarro.watchtower.local' mail returned: 0 bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf pulseaudio-module-gconf: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3.1 Version table: 1:8.0-0ubuntu3.1 500 500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages *** 1:8.0-0ubuntu3 500 500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+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 1773033] Please test proposed package
Hello Anthony, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.
--
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/1773033
Title:
unattended upgrade no longer actions on shutdown
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 does not install upgrades when it is configured
to install updates on shutdown and when it the system is started on
battery, but installs updates on battery in other cases.
* This behaviour is unintended and confuses users, moreover
installing updates on battery risks the system to be shut down in the
middle of an upgrade due to depleting the battery.
* This upload changes u-u to skip updates or gracefully stop when the
system is switching to batter-powered state by default minimizing the
risk of breaking the system.
[Test Case]
* Run "unattended-upgrade --dry-run --verbose" on battery and on AC
power
* With default configuration u-u should stop with the following message on
battery:
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
System is on battery power, stopping
* On AC power it should continue:
$ sudo ./unattended-upgrade --dry-run --verbose
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
No packages found that can be upgraded unattended and no pending auto-removals
* Add the following configuration file and check u-u continuing even on
battery:
$ cat /etc/apt/apt.conf.d/51unattended-upgrades-on-battery
Unattended-Upgrade::OnlyOnACPower "false";
rbalint@yogi:~/projects/deb/unattended-upgrades$ sudo ./unattended-upgrade
--dry-run --verbose
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
No packages found that can be upgraded unattended and no pending auto-removals
[Regression Potential]
* Unattended-upgrades may fail to install updates even on AC power,
but this is unlikely to happen due to the code changed being fairly
simple. on_ac_power may return 255 (false) Power status could not be
determined, but this is mapped to being on AC power and installing the
updates, only subprocess.call("on_ac_power") == 1 makes u-u skip
updates.
[Original Bug Text]
Ubuntu 17.10 and 18.04 do not install updates with InstallOnShutdown
flag set.
post-install script on 14.04 and 16.04 would set options in
/etc/apt/apt.conf.d/50unattended-upgrades and
/etc/apt/apt.conf.d/10periodic to install updates on shutdown of
ubuntu desktop. This worked on 17.10 also, until an update before the
release of 18.04. After a fresh install of 18.04, ran the post install
script. Below is the contents of the two files, updates do not run,
even if performing an apt update and leaving the machine up for a few
hours to download packages in the back ground. Both the unattended-
upgrades and unattended-upgrades-shutdown log files are empty.
Description: Ubuntu 18.04 LTS
Release: 18.04
ii unattended-upgrades1.1ubuntu1
all automatic installation of security upgrades
--/etc/apt/apt.conf.d/50unattended-upgra
[Touch-packages] [Bug 1737637] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1737637 Title: Replacing configuration file directory with file breaks unattended- upgrades 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 a package update changes a config dir to a config file. * U-u stops installing security updates when it crashes. [Test Case] (Xenial) * Install an older version of the git package than the one available from xenial-security: # apt install git=1:2.7.4-0ubuntu1 * Change a configuration file to a directory and observe not fixed u-u crashing and fixed u-u installing the update. # mv /etc/bash_completion.d/git-prompt /etc/bash_completion.d/git-prompt.bak # mkdir /etc/bash_completion.d/git-prompt # unattended-upgrade --verbose --dry-run 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'] Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1485, in main(options) File "/usr/bin/unattended-upgrade", line 1275, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 671, in conffile_prompt with open(prefix + conf_file, 'rb') as fb: IsADirectoryError: [Errno 21] Is a directory: '/etc/bash_completion.d/git-prompt' # fixed u-u: # unattended-upgrade --verbose --dry-run ... Unpacking git (1:2.17.1-1ubuntu0.4) over (1:2.17.1-1ubuntu0.3) ... dpkg: warning: git: conffile '/etc/bash_completion.d/git-prompt' is not a plain file or symlink (= '/etc/bash_completion.d/git-prompt') Setting up git (1:2.17.1-1ubuntu0.4) ... dpkg: warning: git: conffile '/etc/bash_completion.d/git-prompt' is not a plain file or symlink (= '/etc/bash_completion.d/git-prompt') ... [Regression Potential] * As a known and demonstrated regression configuration files replaced with directories by the local administrator are overwritten and this is dpkg's default behavior. The same thing would happen when applying the security update using apt, and this is still better than skipping the security update. [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/ed79dbb4e6eba8c7b89fcd7e0cbf60b0db4920ce 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 1556, in main(options) File "/usr/bin/unattended-upgrade", line 1348, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 725, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/fonts/conf.avail/65-0-fonts-guru-extra.conf' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1737637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~t
[Touch-packages] [Bug 1775307] Please test proposed package
Hello Balint, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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 -- 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 1741579] Please test proposed package
Hello ITEAS, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.
--
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/1741579
Title:
Wrong/confuse text on shutdown at unattended-upgrades
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Bug description:
[Impact]
* The confusing text on shutdown is, well, can confuse users.
* This fix itself is minor and would not warrant a backport but it is
backported as part of fully backporting Bionic's u-u version to Xenial.
[Test Case]
* Check that the status text is less confusing than it was previously
either by configuring unattended-upgrades to run at shutdown and
waiting for the text to appear or check that the text is changed in
unattended-upgrades-shutdown:
$ grep -B1 please /usr/share/unattended-upgrades/unattended-upgrade-shutdown
msg = _("Unattended-upgrade in progress during shutdown, "
"please don't turn off the computer")
* The former way or the verification may not be easy since with the fix for
LP: #1803137 the shutdown screen does not show up when u-u-shutdown starts
running, see the bug for the details.
* Also checking unatttended-upgrades-shutdown for the changed text does not
ensure that the translation is ready, too.
[Regression Potential]
* The updated text should not cause major issues, but until it is
translated to each language it is shown in English, possibly confusing
users in a different way.
[Original Bug Text]
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades-0.90ubuntu0.9
Uname: 4.4.0-104-generic #127-Ubuntu SMP
Architecture: amd64
I've german systems, so when updates will be installed at shutdown
this text will be displayed at the screen.
German:
"unattended upgrade läuft während des herunterfahrens weiter, es wird fünf
Sekunden lange gewartet"
English:
"unattended upgrade runs during the shutdown, it waits for five seconds"
This sentence make absolutly no sence for me. Maybe it is an
translationproblem? Don't know text on the english ubuntuversion.
The problem is that some customer turned of some computers, because the
updates need more time then 5 seconds ;)
A better message will that was Windows10 displays at shutdown ...don't
turn off the computer, updates will be installed...
Thanks and best Reagards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1741579/+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] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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 start 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@x2:~# echo extra-junk >> /etc/apt/apt.conf.d/50unattended-upgrades root@x2:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown Traceback (most recent call last): File "/usr/share/unattended-upgrades/unattended-upgrade-shutdown", line 119, in apt_pkg.init_config() SystemError: E:Syntax error /etc/apt/apt.conf.d/50unattended-upgrades:67: Extra junk at end of file root@x2:~# * Fixed version: # /usr/share/unattended-upgrades/unattended-upgrade-shutdown ; echo $? 1 root@bb-lp-1806076:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-11-30 18:05:56,515 ERROR - Apt returned an error, exiting 2018-11-30 18:05:56,515 ERROR - error message: 'E:Syntax error /etc/apt/apt.conf.d/50unattended-upgrades:93: Extra junk at end of file' [Regression Potential] * U-u-s used to exit crashing, now it exits with an error code, just logging the error. There is little chance for regressing here, but users may have harder time to figure out why u-u-s exited, they need to check the log file. * There is also an enhancement request tracked to start u-u-s with a default config when parsing the config fails to be able to act on shutdown: https://github.com/mvo5/unattended-upgrades/issues/161 [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/b1c4cd0c858e1c3c6c86f938397e8d5d4208242b 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/share/unattended-upgrades/unattended-upgrade-shutdown", line 136, in apt_pkg.init_config() apt_pkg.Error: E:Syntax error /etc/apt/apt.conf:2: Extra junk at end of file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1737717/+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 1680599] Please test proposed package
Hello Dan, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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 1779157] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1779157 Title: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended- upgrade@1927:main:do_install 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 can be crashing when packages are marked for removal after collecting upgradable packages. * The fix clear the cache when it may be in an invalid state to lose markings. [Test Case] * Observe https://errors.ubuntu.com/problem/66b5fef8d6dd83a7db6c494c807cfc067626c0c2 not occurring in fixed versions. [Regression Potential] * The extra cache.clear() can take extra CPU time when invoked needlessly or can cause skipping updates when invoked at the wrong time. However the fix received extensive testing in newer releases making unnoticed regressions unlikely to surface. [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 1.1ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 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 Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1927, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1782, in main logfile_dpkg) File "/usr/bin/unattended-upgrade", line 1057, in do_install "removal:%s" % "".join([pkg.name for pkg in marked_delete])) AssertionError: Internal error. The following packages are marked for removal:linux-headers-4.15.0-20-generic Also seen as: https://errors.ubuntu.com/problem/733d2e7865692e215f406231edd3692a6a1810c5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1779157/+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] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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 1737635] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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 1654600] Please test proposed package
Hello Erik, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.
--
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/1654600
Title:
unattended-upgrade-shutdown hangs when /var is a separate filesystem
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 Yakkety:
Fix Released
Status in unattended-upgrades source package in Zesty:
Fix Released
Status in unattended-upgrades package in Debian:
Fix Released
Bug description:
[SRU justification]
This fix is needed to make sure that the system does not hang on shutdown
when /var is a speparate file system
[Impact]
System can hang up to 10 minutes if not fixed.
[Fix]
Change the systemd unit's ExecStart to an ExecStop so the unit is correctly
sequenced.
Change WantedBy to multi-user.target. This requires working around Debian Bug
#797108 which causes the new unit not to be enabled.
Remove the unneeded override_dh_isntallinit
Add Default-Start levels to the SysV initscript
Improve DEP8 testing
[Test Case]
In a VM with /var separated from the / file system, shutdown the VM. It will
hang for 10 minutes
[Regression]
Upgrade has been tested on Xenial, Yakkety, Zesty. do-release-upgrade has
been tested from Trusty to Xenial. All behave as expected.
A change of behavior may occur now that the systemd unit is correctly
enabled, which would make functionalities like InstallOnShutdown to
work as expected whereas it could have been broken previously. This
cannot be considered as a regression as it is expected behavior.
Shutdown may be slowed down as it now correctly depends on /var and
/boot to be available so the unit will run earlier than previously.
[Original description of the problem]
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all
filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in /var/run) exists, and if it does, there is an unattended-upgrade in
progress
and the service will wait until it finishes (and therefore automatically wait
at
shutdown).
However, if /var is a separate filesystem, it will get unmounted even though
/var/run
is a tmpfs that's still mounted on top of the /var/run directory in the /var
filesystem.
The unattended-upgrade script will fail to find lockfile, sleeps for 5
seconds, and
tries to check the lockfile again. After 10 minutes (the default timeout), it
will finally
exit and the system will continue shutdown.
The problem is the error handling in
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
where it tries to lock itself:
while True:
res = apt_pkg.get_lock(options.lock_file)
logging.debug("get_lock returned %i" % res)
# exit here if there is no lock
if res > 0:
logging.debug("lock not taken")
break
lock_was_taken = True
The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an
error.
File descriptors are just C file descriptors, so they are always positive
integers.
The code should check the result to be negative, not positive. I have
attached a patch
to reverse the logic.
Additional information:
1)
Description: Ubuntu 16.04.1 LTS
Release: 16.04
2)
unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
*** 0.90ubuntu0.3 500
500 http://nl.archive.ubuntu.c
[Touch-packages] [Bug 1778219] Please test proposed package
Hello Cs-gon, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.
--
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/1778219
Title:
unattended-upgrades hangs on shutdown, leaves system in a broken state
Status in apt package in Ubuntu:
Invalid
Status in init-system-helpers package in Ubuntu:
Invalid
Status in snapd package in Ubuntu:
Confirmed
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Confirmed
Status in init-system-helpers source package in Xenial:
Confirmed
Status in snapd source package in Xenial:
Confirmed
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in apt source package in Bionic:
Confirmed
Status in init-system-helpers source package in Bionic:
Confirmed
Status in snapd source package in Bionic:
Confirmed
Status in unattended-upgrades source package in Bionic:
Fix Released
Status in unattended-upgrades source package in Cosmic:
Fix Released
Bug description:
[Impact]
* Unattended-upgrades hangs and gets killed when installing upgrades
that stat/stop services on shutdown, leaving the system in a broken
state
[Test Case]
* Install an updated bionic system:
$ lxc launch ubuntu:18.04 uu-shutdown-test
# apt update
...
* When testing the fixed version, install upgrade u-u at this point checking
that u-u.service is set up before and is wanted by shutdown.target:
# systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" [color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
Color legend: black = Requires
dark blue = Requisite
dark grey = Wants
red = Conflicts
green = After
* Configure u-u to run on shutdown and install -updates:
# echo 'Unattended-Upgrade::InstallOnShutdown "true";' >
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too
* Downgrade snapd:
# apt install snapd=2.32.5+18.04
* Dowload packages for u-u:
# unattended-upgrade --download-only
* Reboot using logind to let inhibitors hold up shutdown:
# dbus-send --system --print-reply --dest=org.freedesktop.login1
/org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false
* With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
`-{unattended-upgr}
* With fixed u-u observe snapd update taking place and system
rebooting after a few seconds with all updates installed
* Since this fix is partially reverting the fix for LP: #1654600
please test LP: #1654600 as well to avoid regressions.
[Regression Potential]
* As part of the fix manual changes were made to postinst to properly
transition from coupling u-u.service with multi-user.target to coupling it with
shutdown.target again which can make u-u started during
[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually
I have a Sony MDR-XB950N1 and I'm seeing the same thing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1690980] Please test proposed package
Hello ethan.hsieh, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.
--
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/1690980
Title:
unattended-upgrades does not block shutdown of system, as it is
designed to
Status in OEM Priority Project:
Triaged
Status in OEM Priority Project xenial series:
Triaged
Status in apt package in Ubuntu:
Fix Released
Status in unattended-upgrades package in Ubuntu:
Fix Released
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 Zesty:
Won't Fix
Status in unattended-upgrades source package in Zesty:
Won't Fix
Bug description:
Title: No pop-up window to warn users that system should not reboot or
shutdown while installing security updates
Summary:
No pop-up window to warn users that system should not reboot or shutdown
while installing security updates
Steps:
1. trigger unattended-upgrades
2. reboot or shutdown system while installing packages
Expected results: There is a pop-up window to warn users that system
should not reboot or shutdown
Actual results: There is no pop-up window to warn users
Additional information:
$ apt-cache policy unattended-upgrades
unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
* APT SRU *
[Impact]
Stopping apt-daily-upgrade.service terminates dpkg and friends by sending the
signals to all processes in the cgroup, and will send KILL quickly after.
[Test case]
Start apt-daily-upgrade.service and stop it while unattended-upgrades is
running.
The upgrade should run to completion or a safe exit point as long as
it takes less than about 900s (which is the timeout for sending kill).
[Regression potential]
Leftover processes might remain in the apt-daily-upgrade cgroup if the
postinst scripts or some apt hooks do something funny.
Shutdown might take longer due to the 900 second timeout.
* unattended-upgrades SRU
[Impact]
* Undattended-upgrades does not stop quickly gracefully when shutdown/reboot
is initiated by the user.
* The fix is performing the updates in minimal package sets and allow
gracefully stopping between those steps when unattended-upgrades.service sends
a TERM signal to running u-u. The signal is sent on receiving
PrepareForShutdown() from logind
(https://www.freedesktop.org/wiki/Software/systemd/inhibit/) to stop
unattended-upgrades a bit earlier than the shutdown process starts (LP:
#1803137).
[Test Case]
* Configure the system to have several 20+ packages upgradable by
unattended-upgrades. One easy way of setting this up is starting with
a system where packages from -security are installed but packages from
-updates are not and enabling -updates in u-u:
# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' > /etc/apt/apt.conf.d
/51unattended-upgrades-updates-too
* Pre-download upgrades
# unattended-upgraded --download-only
* Trigger unattended-upgrades run:
# service apt-daily-upgrade start
* Shutdown the system from a graphical user session or by executing
# dbus-send --system --print-reply --dest=org.freedesktop.login1
/org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false
* Observe the system unattended-upgrades being gracefully stopped,
checking /var/log/unattended-upgrades/unattended-upgrades.log. There
should be packages left to be upgraded.
[Regression Potential]
On Xenial (with Unity) starting shutdown from the graphical session
does not log the user out nor sho
[Touch-packages] [Bug 1781183] Please test proposed package
Hello Balint, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1781183 Title: Skip updates on metered connections 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 Status in unattended-upgrades package in Debian: Fix Released Bug description: [Impact] * Systems running unattended-upgrades may download updates over metered connections causing excessive data usage possibly making users being charged for the downloads. * Avoiding users being unexpectedly charged due to unattended- upgrades' activity warrants an SRU, IMO. * The fix uses NetworkMonitor.get_network_metered(NetworkMonitor.get_default()) for deciding if the connection is metered and skips or gracefully stops updates. [Test Case] * Run "unattended-upgrades --dry-run --verbose" on metered connection - The unfixed versions should provide the following output with default configuration: $ sudo unattended-upgrade --dry-run --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic No packages found that can be upgraded unattended and no pending auto-removals - The fixed versions should provide the following output with default configuration: Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic System is on metered connection, stopping - You can check if the default route is on metered connection by running: nmcli -t -f GENERAL.DEVICE,GENERAL.METERED dev show `ip route list 0/0 | sed -r 's/.*dev (\S*).*/\1/g'` - Also run fixed u-u on not metered connection to check if it still works. U-u in lxc for example does not detect the connection to be metered. - Check if the following configuration can enable updates even on metered connections: $ cat /etc/apt/apt.conf.d/51unattended-upgrades-metered Unattended-Upgrade::Skip-Updates-On-Metered-Connections "false"; [Regression Potential] * Unattended-upgrades may skip updates even on not metered connections or crash, but those are not likely. * U-u also adds two new dependencies with the fix which can be seen as a regression, but those packages exist on most Ubuntu installations already. (The packages are: gir1.2-glib-2.0 and python3-gi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1781183/+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 1781176] Please test proposed package
Hello Balint, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.
--
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/1781176
Title:
Blacklisted packages are included in the "upgradable origin", while
they should not
Status in unattended-upgrades:
Fix Released
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]
* Reports from u-u incorrectly list packages from non-upgradable
origins as "Packages with upgradable origin but kept back"
* Listing the packages incorrectly is a result of
is_pkgname_in_blacklist() having a side effect and removing the side
effect is part of fixing LP: #1396787 which fix is also being SRU-d.
* The fix is removing the side effect of is_pkgname_in_blacklist()
[Test Case]
* There is a build-time test in test/test_blacklisted_wrong_origin.py
* To reproduce the original problem set up a system where all security
updates are installed but ebtables (from bionic-updates) is not updated:
$ sudo unattended-upgrade --verbose
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
No packages found that can be upgraded unattended and no pending auto-removals
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
apt apt-utils ebtables initramfs-tools initramfs-tools-bin
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io
networkd-dispatcher nplan
python-apt-common python3 python3-apt python3-minimal
python3-update-manager snapd squashfs-tools
unattended-upgrades update-manager-core update-notifier-common
27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 24.1 MB of archives.
After this operation, 1454 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
* blacklist ebtables, set up emails from u-u, then run u-u again:
$ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' >
/etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables
$ sudo echo 'Unattended-Upgrade::Mail "root";' >
/etc/apt/apt.conf.d/51unattended-upgrades-mail
$ sudo unattended-upgrade --verbose
Initial blacklisted packages: ebtables
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
Packages that will be upgraded:
* Observe ebtables listed as being kept back and having upgradable origin
with buggy u-u:
$ sudo cat /var/mail/mail
...
Packages with upgradable origin but kept back:
ebtables=20
...
* Upgrade u-u to a fixed version and run it, observing ebtables to be
not listed as having upgradable origin
[Regression Potential]
* Regressions may make packages incorrectly missing from u-u's
report, but the autopkgtests also cover that to some extent.
[Other Info]
* Original report: https://github.com/mvo5/unattended-
upgrades/issues/116
To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1781176/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : http
[Touch-packages] [Bug 1775292] Please test proposed package
Hello Balint, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1775292 Title: Unattended-upgrades stopped adjusting candidates in 1.1 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 may fail to install an update when the highest version of a package to be updated exists in an origin u-u is not allowed to pull packages from. [Test Case] * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug * Observe no line with "adjusting candidate version: " with buggy u-u version * Install fixed u-u version * Run sudo unattended-upgrade --dry-run --verbose --debug * Observe lines "adjusting candidate version: " [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/1775292/+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 1778800] Please test proposed package
Hello Joshua, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1778800 Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post- installation script subprocess returned error exit status 1 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] * Upgrading unattended-upgrades during shutdown fails due to postinst trying to start the unattended-upgrades service. This can break installation of other security-fixes, too. * Unattended-upgrades is regularly SRU-d and this bug can break installing other important updates. * The fix is not starting/stopping the init.d script in postinst which is not useful during package installation anyway. [Test Case] * Check prerm that invoke-rc.d is not called: --- prerm.old 2018-06-07 01:30:55.0 +0200 +++ /var/lib/dpkg/info/unattended-upgrades.prerm 2018-07-12 14:04:12.294677476 +0200 @@ -40,11 +40,6 @@ # dh_installdeb will replace this with shell code automatically # generated by other debhelper scripts. -# Automatically added by dh_installinit/11.1.6ubuntu2 -if [ -x "/etc/init.d/unattended-upgrades" ] && [ "$1" = remove ]; then - invoke-rc.d unattended-upgrades stop || exit 1 -fi -# End automatically added section exit 0 * Check postinst that invoke-rc.d is not called: --- postinst.old 2018-06-07 01:30:55.0 +0200 +++ /var/lib/dpkg/info/unattended-upgrades.postinst 2018-07-12 14:04:12.242676369 +0200 @@ -108,8 +108,7 @@ # Automatically added by dh_installinit/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then if [ -x "/etc/init.d/unattended-upgrades" ]; then - update-rc.d unattended-upgrades defaults >/dev/null - invoke-rc.d unattended-upgrades start || exit 1 + update-rc.d unattended-upgrades defaults >/dev/null || exit 1 fi fi # End automatically added section [Regression Potential] * Unattended-upgrades.service may fail to start upon first installation. This is not an issue in default configuration since apt starts u-u based on timers and stops it gracefully upon shutdown. [Original Bug Text] update did not install. a similar thing has happened with several apps have tried to download and the OS wont install them for some reason. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 26 22:26:14 2018 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-06-08 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unatten
[Touch-packages] [Bug 1675079] Please test proposed package
Hello Bryce, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1675079 Title: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist 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) 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] On a 16.04LTS system, the /boot partition will eventually fill with Kernel images, until the point where "apt-get autoremove" can't complete. This issue has previously been reported as fixed, but it is not fixed: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093 Generally what I see is the final kernel image that fills the drive is incompletely installed (the header package does not make it). "apt- get autoremove" tries to work, but fails. I must manually remove kernel images to free enough space. I see this on a machine used by my elderly parents, where 'Download and install updates automatically' is set. And on my home machines, where the setting is elsewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : ht
[Touch-packages] [Bug 1702793] Please test proposed package
Hello Matt, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1702793 Title: Full backport SRU for unattended-upgrades Status in unattended-upgrades package in Ubuntu: In Progress Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: [Impact] * I would like to propose a one-off full backport of unattended-upgrades 1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because selectively backporting fixes for crashes and for issues that made u-u unreliable would be more risky thanks to the huge number of fixes and the inter-dependencies between them. [Test Case] * Since this backport involves fixing several bugs and this bug itself covers the full backport this is an overview of all LP bugs the upload fixes: - most important bugs (feel free to add more) + LP: #1615381 : apt-get autoremove may remove current kernel All LP bugs fixed by the backport, comments are welcome: + LP: #1230246 could use SRU template but seems straightforward + LP: #1260041 SRU template ok + LP: #1396787 SRU template ok + LP: #1446552 SRU template ok + LP: #1455097 SRU template ok + LP: #1458204 could use SRU template but seems straightforward + LP: #1577215 could use SRU template but seems straightforward + LP: #1602536 SRU template ok + LP: #1615381 could use SRU template but seems straightforward + LP: #1624644 SRU template ok + LP: #1649709 not affecting xenial + LP: #1654070 could use SRU template but seems straightforward + LP: #1654600 SRU template ok + LP: #1675079 SRU template ok + LP: #1680599 could use SRU template but seems straightforward + LP: #1686470 SRU template ok + LP: #1690980 SRU template ok + LP: #1698159 SRU template ok + LP: #1702793 this bug + LP: #1714019 just a merge request + LP: #1718419 just a merge request + LP: #1719630 SRU template ok + LP: #1722426 just a merge request + LP: #1737442 SRU template ok + LP: #1737635 SRU template ok + LP: #1737637 SRU template ok + LP: #1737717 SRU template ok + LP: #1741579 SRU template ok + LP: #1764797 just a merge request + LP: #1773033 SRU template ok + LP: #1775292 SRU template ok + LP: #1775307 SRU template ok + LP: #1778219 SRU template ok + LP: #1778800 SRU template ok + LP: #1779157 SRU template ok + LP: #1781176 SRU template ok + LP: #1781183 SRU template ok + LP: #1781446 SRU template ok + LP: #1781586 SRU template ok + LP: #1785093 SRU template ok + LP: #1789637 SRU template ok + LP: #1803749 SRU template ok [Regression Potential] * Due to this update covering the full backport unattended-upgrades can regress in any imaginable way including failing to install, upgrade, run, or removing essential packages from the system. Those are unlikely.* There are open bugs about u-u being slower than in the past, thus this may be a likely regression but IMO the pending speed optimizations should not be blocking the backport because the reliability issues are more important to fix and speed optimizations can be cherry-picked later. [Other Info] I asked for an exception for the package in following the SRU process: https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html I'm preparing the backport in ppa:rbalint/scratch and also run autopkgtests on it in addition to testing it manually in VMs. [Original Bug Text] Changes to support day-of-week patching and logging to syslog were added t
[Touch-packages] [Bug 1698159] Please test proposed package
Hello Ian, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/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 in APT::NeverAutoRemove, for example, on cosmic: "^linux-cloud-tools-4\.17\.0-9-generic$"; "^linux-cloud-tools-4\.18\.0-7-generic$"; Those are in 01autoremove-kernels [Test case (unattended-upgrades)] * Check the running kernel and install relevant cloud-tools packages: # uname -a Linux x-uu-lp-1737637 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@x-uu-lp-1737637:~# apt-cache search 4.15.0-39-generic linux-cloud-tools-4.15.0-39-generic - Linux kernel version specific cloud tools for version 4.15.0-39 linux-headers-4.15.0-39-generic - Linux kernel headers for version 4.15.0 on 64 bit x86 SMP linux-image-4.15.0-39-generic - Signed kernel image generic linux-image-unsigned-4.15.0-39-generic - Linux kernel image for version 4.15.0 on 64 bit x86 SMP linux-modules-4.15.0-39-generic - Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP linux-modules-extra-4.15.0-39-generic - Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP # apt install linux-cloud-tools-4.15.0-39-generic Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39 The following NEW packages will be installed: linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39 0 upgraded, 3 newly installed, 0 to remove and 17 not upgraded. Need to get 119 kB of archives. After this operation, 854 kB of additional disk space will be used. Do you want to continue? [Y/n] ... * Mark them autoremovable and configure u-u to autoremove unused packages: # apt-mark auto linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-4.15.0-39-generic set to automatically installed. ### set Unattended-Upgrade::Remove-Unused-Dependencies "true"; # vi /etc/apt/apt.conf.d/50unattended-upgrades * The not fixed version of u-u removes the
[Touch-packages] [Bug 1719630] Please test proposed package
Hello Jean-Baptiste, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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 1785093] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1785093 Title: RecursionError error in call_adjusted() 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 may crash and stop installing security updates on users' system due to entering infinite loop. * The fix ensures terminating the recursive calls. [Test Case] * TODO / observe the crash not being reported for fixed releases on errors.ubuntu.com. [Regression Potential] * Unattended-upgrades now adjusts package candidates only to lower versions than the one originally offered by apt's resolver. This is a change in behavior which aligns well with the default configuration, i.e. installing packages from -security but not from -updates, since -updates almost always have higher version numbers. This change may cause using different upgrade paths when PPAs are involved and all packages can't be upgraded to the highest versions found in allowed origins, because of Conflicts: for example. * Unexpected regressions can cause candidate adjustments not taking place, but please note that autopkgtest now includes applying all outstanding security updates for the release thus the new code is covered, too. [Original Bug report] 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.18.04.5, the problem page at https://errors.ubuntu.com/problem/fa706afe2f0e04b661fe54da0a59b9fc3da50734 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 1991, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1647, in main cache, options, allowed_origins, blacklisted_pkgs, whitelisted_pkgs) File "/usr/bin/unattended-upgrade", line 1349, in calculate_upgradable_pkgs whitelisted_pkgs) File "/usr/bin/unattended-upgrade", line 1288, in try_to_upgrade cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed) File "/usr/bin/unattended-upgrade", line 212, in mark_upgrade_adjusted self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs) File "/usr/bin/unattended-upgrade", line 206, in call_adjusted self.call_adjusted(function, pkg, **kwargs) File "/usr/bin/unattended-upgrade", line 206, in call_adjusted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1785093/+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 1781586] Please test proposed package
Hello Balint, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1781586 Title: Skip rebuilding python-apt in upgrade autopkgtests 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] * Python-apt has a new build dependency making the rebuilding as is failing and the reference handling issue is worked around in unattended-upgrades already. * Table updates of python-apt may make u-u autopkgtest fail without the u-u package having any problem when it is installed. [Test Case] * Check upgrade-all-security autopkgtest output, it should not rebuild the python-apt package. [Regression Potential] * Autopkgtest may fail due running it with not rebuilt python-apt. This problem can be caught easily when testing the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1781586/+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 1781446] Please test proposed package
Hello Balint, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1781446 Title: Autopkgtest upgrade-all-security is failing due to apt printing to stderr in Bionic 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] * The following error can be seen in autopkgtest, holding back u-u from migration: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/unattended-upgrades/20180712_151033_c44d8@/log.gz : ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.11-2) ... W: APT had planned for dpkg to do more than it reported back (2370 vs 2372). Affected packages: fuse:amd64 Reading package lists... ... autopkgtest [14:17:33]: test upgrade-all-security: - - - - - - - - - - results - - - - - - - - - - upgrade-all-security FAIL stderr: W: APT had planned for dpkg to do more than it reported back (2370 vs 2372). autopkgtest [14:17:34]: test upgrade-all-security: - - - - - - - - - - stderr - - - - - - - - - - W: APT had planned for dpkg to do more than it reported back (2370 vs 2372). Affected packages: fuse:amd64 autopkgtest [14:17:34]: test upgrade-between-snapshots: preparing testbed ... [Test Case] * upgrade-all-security autopkgtest [Regression Potential] * Valid errors manifesting themselves only as output from stderr may not fail the autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1781446/+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 1803749] Please test proposed package
Hello Balint, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.
--
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/1803749
Title:
apt.Cache.clear() may set apt.Package.is_auto_removable to False
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
Status in unattended-upgrades source package in Cosmic:
Fix Released
Bug description:
[Impact]
* Originally autoremovable packages can be removed as newly autoremovable
ones by unattended-upgrades
* This can surprise users potentially removing packages which are needed for
the system's operation.
[Test Case]
* The buggy u-u version will remove the previously autoremovable zsh
at the end, the fixed one does not.
$ sudo debootstrap bionic uu-test-bionic-1803749
...
$ sudo chroot uu-test-bionic-1803749
# apt install unattended-upgrades zsh
# apt-mark auto zsh
...
# echo "Unattended-Upgrade::Package-Blacklist {"libs";}" >
/etc/apt/apt.conf.d/51unattended-upgrades
# echo "deb http://archive.ubuntu.com/ubuntu bionic-security main" >>
/etc/apt/sources.list
# echo "deb http://archive.ubuntu.com/ubuntu bionic-updates main" >>
/etc/apt/sources.list
# apt update -qq
# unattended-upgrades --dry-run --verbose --debug
...
All upgrades installed
marking zsh for removal
marking zsh-common for removal
Packages that were successfully auto-removed:
Packages that are kept back:
InstCount=0 DelCount=0 BrokenCount=0
#
[Regression Potential]
* Unattended-upgrades may use more CPU-time for operation but I did not
observe a significant increase. Autopkgtest measures u-u's performance thus if
this regression occurs, we can observe it easily.
* Due to the code changes u-u may still remove already autoremovable
packages or fail to remove newly autoremovable ones in default configuration,
but since the code became simpler with the change by eliminating an
optimization this regression is unlikely to take place.
[Original Bug Text]
While triaging LP: #1803587 I found that originally autoremovable
packages were handled as newly autoremovable ones by unattended-
upgrades due to not finding all of them at the beginning of u-u's run.
The root cause seems to be cache.clear() resetting
pkg.is_auto_removable to False under some circumstances I haven't
fully narrowed down.
Set up a Bionic (or later) system with autoremovable packages,
packages upgradable from -security and blacklist at least one
upgradable package and apply the following patch to u-u:
root@bb-1803587:~# diff -Naur /usr/bin/unattended-upgrade.orig
/usr/bin/unattended-upgrade
--- /usr/bin/unattended-upgrade.orig 2018-11-16 16:17:58.522583254 +
+++ /usr/bin/unattended-upgrade 2018-11-16 16:36:12.226675870 +
@@ -948,7 +948,9 @@
def rewind_cache(cache, pkgs_to_upgrade):
# type: (apt.Cache, List[apt.Package]) -> None
""" set the cache back to the state with packages_to_upgrade """
+print([pkg.name for pkg in cache if pkg.is_auto_removable])
cache.clear()
+print([pkg.name for pkg in cache if pkg.is_auto_removable])
for pkg2 in pkgs_to_upgrade:
pkg2.mark_install(from_user=not pkg2.is_auto_installed)
if cache.broken_count > 0:
Run u-u to observe cache.clear() resetting the list of autoremovable
packages:
~# /usr/bin/unattended-upgrade --dry-run --verbose --debug
Initial blacklisted packages: systemd
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu
[Touch-packages] [Bug 1806487] Re: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet)
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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: unattended-upgrades (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-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/1806487 Title: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) Status in unattended-upgrades package in Ubuntu: New 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 Committed Bug description: [Impact] * Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start. * Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process. * The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence. [Test Case] * Stop systemd-logind and make it unable to start for example by masking it: root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload root@bb-logind:~# service systemd-logind stop root@bb-logind:~# service systemd-logind status ● systemd-logind.service Loaded: masked (/dev/null; bad) Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago Main PID: 1938 (code=killed, signal=TERM) Status: "Processing requests..." ... * Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start: root@bb-logind:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log ... 2018-12-13 14:30:17,600 WARNING - Could not get delay inhibitor lock 2018-12-13 14:30:17,601 DEBUG - Skip waiting for signals, starting operation now 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken * Restore logind's ability to start root@bb-logind:~# rm /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload * Restart unattended-upgrades.service root@bb-logind:~# service unattended-upgrades restart root@bb-logind:~# 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 Thu 2018-12-13 14:31:43 UTC; 3s ago Docs: man:unattended-upgrade(8) Main PID: 4129 (unattended-upgr) Tasks: 2 (limit: 4915) CGroup: /system.slice/unattended-upgrades.service └─4129 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal Dec 13 14:31:43 bb-logind systemd[1]: Started Unattended Upgrades Shutdown. root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-13 14:30:17,601 DEBUG - Sta
[Touch-packages] [Bug 1789637] Please test proposed package
Hello Balint, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1789637 Title: Proper support for frontend lock 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] Apt and dpkg implemented the Frontend Locking API and unattended- upgrades needs to adopt it to not leave the packaging system unlocked while passing control to python-apt and dpkg to perform package installations and removals. Leaving the packaging system unlocked caused many crashes of u-u when other tools took the lock and in the worse case let other package management tools operate on dpkg's database breaking systems. The change takes advantage of python-apt's new API and keeps the frontend lock during the run of u-u and unlocks only the inner locks for committing changes. [Test case] Run strace unattended-upgrades to upgrade several packages and check that lock-frontend is acquired at the beginning and not released until the end (not reacquired repeatedly). Unfixed u-u's output is like this: # strace unattended-upgrade --verbose --dry-run 2>&1 | grep lock openat(AT_FDCWD, "/var/run/unattended-upgrades.lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4 openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5 openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6 openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5 openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6 openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 93 openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6 openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5 openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6 openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5 openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6 ... Fixed u-u's output is like that: # strace unattended-upgrade --dry-run --verbose 2>&1 | grep lock openat(AT_FDCWD, "/var/run/unattended-upgrades.lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4 openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 8 openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10 openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 57 openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10 openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 69 openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10 openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 70 openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10 ... [Regression potential] Incorrect lock API usage can make unattended-upgrades to crash, but it is unlikely to hang since the lock handling operations are non- blocking. Failing to reserve the locks can also cause problems by allowing other package management tools to install packages in parallel, but this problem existed in the past, too. [Additional Info] This is part of a wider series of changes for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended
[Touch-packages] [Bug 1808060] Re: libmirclient causes multiarch SDL2 headers to conflict with each other
On reflection, there are several factors contributing to the problem. Addressing any one of them would resolve the problem reported. 1. none of the Mir -dev packages are co-installable 2. libsdl2-dev should not depend on libmirclient-dev 3. SDL2 is being built with mirclient support on 18.10 1 & 2 have been the case since well before 16.04 and this issue has gone undetected. If there's a reason for /2/, it's a bad one. Regardless, we ought to address /1/. 3 is pointless and likely an oversight. I'm under the impression that SDL2 dropped mirclient support upstream, but I guess that hasn't filtered through yet. In any case mirclient lost GL support in 18.04 and will not support Nvidia eglstream drivers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1808060 Title: libmirclient causes multiarch SDL2 headers to conflict with each other Status in mir package in Ubuntu: Triaged Bug description: libmirclient-dev makes impossible to install both libsdl2-dev and libsdl2-dev:i386 which is essential for anyone building game related software. Seeing mir not being used at all in any of the official Ubuntu flavors, I find it strange that it was considered an acceptable solution to break a common and important workflow in favor of an experimental display server. It's probably a minor packaging bug anyway, multi-arch development headers usually don't conflict with each other. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libmirclient-dev 0.32.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 14:25:50 2018 SourcePackage: mir UpgradeStatus: Upgraded to cosmic on 2018-11-02 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1808060/+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 1806487] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.8 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. -- 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/1806487 Title: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) Status in unattended-upgrades package in Ubuntu: New Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start. * Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process. * The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence. [Test Case] * Stop systemd-logind and make it unable to start for example by masking it: root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload root@bb-logind:~# service systemd-logind stop root@bb-logind:~# service systemd-logind status ● systemd-logind.service Loaded: masked (/dev/null; bad) Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago Main PID: 1938 (code=killed, signal=TERM) Status: "Processing requests..." ... * Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start: root@bb-logind:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log ... 2018-12-13 14:30:17,600 WARNING - Could not get delay inhibitor lock 2018-12-13 14:30:17,601 DEBUG - Skip waiting for signals, starting operation now 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken * Restore logind's ability to start root@bb-logind:~# rm /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload * Restart unattended-upgrades.service root@bb-logind:~# service unattended-upgrades restart root@bb-logind:~# 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 Thu 2018-12-13 14:31:43 UTC; 3s ago Docs: man:unattended-upgrade(8) Main PID: 4129 (unattended-upgr) Tasks: 2 (limit: 4915) CGroup: /system.slice/unattended-upgrades.service └─4129 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal Dec 13 14:31:43 bb-logind systemd[1]: Started Unattended Upgrades Shutdown. root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken 2018-
[Touch-packages] [Bug 1806487] Re: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet)
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.5ubuntu3.18.10.1 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: unattended-upgrades (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: unattended-upgrades (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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1806487 Title: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) Status in unattended-upgrades package in Ubuntu: New Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start. * Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process. * The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence. [Test Case] * Stop systemd-logind and make it unable to start for example by masking it: root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload root@bb-logind:~# service systemd-logind stop root@bb-logind:~# service systemd-logind status ● systemd-logind.service Loaded: masked (/dev/null; bad) Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago Main PID: 1938 (code=killed, signal=TERM) Status: "Processing requests..." ... * Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start: root@bb-logind:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log ... 2018-12-13 14:30:17,600 WARNING - Could not get delay inhibitor lock 2018-12-13 14:30:17,601 DEBUG - Skip waiting for signals, starting operation now 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken * Restore logind's ability to start root@bb-logind:~# rm /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload * Restart unattended-upgrades.service root@bb-logind:~# service unattended-upgrades restart root@bb-logind:~# 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 Thu 2018-12-13 14:31:43 UTC; 3s ago Docs: man:unattended-upgrade(8) Main PID: 4129 (unattended-upgr) Tasks: 2 (limit: 4915) CGroup: /system.slice/unattended-upgrades.service └─4129 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal Dec 13 14:31:43 bb-logind systemd[1]: Started Unattended Upgrades Shutdown. root@bb-logind:~# tail /var/log/unattended-upgrades/
[Touch-packages] [Bug 1808360] [NEW] AppArmor fails after MySQL installation using 18.04.1 LTS
Public bug reported: This is run and returned under root. 08:12 ~: aa-complain /etc/apparmor.d ERROR: Include file /etc/apparmor.d/abstractions/mysql not found 08:18 ~: apt-cache policy apparmor.d libapparmor-dev: Installed: (none) Candidate: 2.12-4ubuntu5.1 Version table: 2.12-4ubuntu5.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.12-4ubuntu5 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: 18.04 apparmor lts mysql -- 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/1808360 Title: AppArmor fails after MySQL installation using 18.04.1 LTS Status in apparmor package in Ubuntu: New Bug description: This is run and returned under root. 08:12 ~: aa-complain /etc/apparmor.d ERROR: Include file /etc/apparmor.d/abstractions/mysql not found 08:18 ~: apt-cache policy apparmor.d libapparmor-dev: Installed: (none) Candidate: 2.12-4ubuntu5.1 Version table: 2.12-4ubuntu5.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.12-4ubuntu5 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1808360/+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 1702088] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1473:main:do_auto_remove:cache_commit:commit:_fetch_archives
*** This bug is a duplicate of bug 1789637 *** https://bugs.launchpad.net/bugs/1789637 ** This bug has been marked a duplicate of bug 1789637 Proper support for frontend lock -- 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/1702088 Title: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin /unattended- upgrade@1473: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 0.92ubuntu1.2, the problem page at https://errors.ubuntu.com/problem/37066ff20a4421af7c675c8b0c0737c18eb719d0 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 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/1702088/+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 1806487] Re: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet)
** Summary changed: - /usr/share/unattended-upgrades/unattended-upgrade-shutdown:dbus.exceptions.DBusException(org.freedesktop.DBus.Error.TimedOut):activate_name_owner:get_name_owner:call_blocking:/usr/share/unattended-upgrades/unattended-upgrade-shutdown@373:main:__init__:get_logind_proxy:get_object:__init__:activate_name_owner:start_service_by_name:call_blocking + [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) ** Tags added: regression-update -- 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/1806487 Title: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) Status in unattended-upgrades package in Ubuntu: New Bug description: [Impact] * Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start. * Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process. * The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence. [Test Case] * Stop systemd-logind and make it unable to start for example by masking it: root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload root@bb-logind:~# service systemd-logind stop root@bb-logind:~# service systemd-logind status ● systemd-logind.service Loaded: masked (/dev/null; bad) Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago Main PID: 1938 (code=killed, signal=TERM) Status: "Processing requests..." ... * Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start: root@bb-logind:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log ... 2018-12-13 14:30:17,600 WARNING - Could not get delay inhibitor lock 2018-12-13 14:30:17,601 DEBUG - Skip waiting for signals, starting operation now 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken * Restore logind's ability to start root@bb-logind:~# rm /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload * Restart unattended-upgrades.service root@bb-logind:~# service unattended-upgrades restart root@bb-logind:~# 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 Thu 2018-12-13 14:31:43 UTC; 3s ago Docs: man:unattended-upgrade(8) Main PID: 4129 (unattended-upgr) Tasks: 2 (limit: 4915) CGroup: /system.slice/unattended-upgrades.service └─4129 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal Dec 13 14:31:43 bb-logind systemd[1]: Started Unattended Upgrades Shutdown. root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken 2018-12-13 14:31:43,595 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2018-12-13 14:31:43,688 WARNING - Could not get delay inhibitor lock 2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead. 2018-12-13 14:31:43,691 WARNING - Maybe systemd-logind service is not running. 2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead. 2018-12-13 14:31:43,691 WARNING - To enable monitoring the PrepareForShutdown() signal instead of polling please install the python3-gi package root@bb-logind:~# systemd-analyze dot | grep unattended ... "unattended-upgrades.service"->"systemd-logind.service" [color="green"]; ... [Regression Potential] * The change to service ordering is unlikely to cause any issue, but the graceful handling of missing logind
[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
** Description changed:
[Impact]
* Unattended-upgrades hangs and gets killed when installing upgrades
that stat/stop services on shutdown, leaving the system in a broken
state
[Test Case]
* Install an updated bionic system:
$ lxc launch ubuntu:18.04 uu-shutdown-test
# apt update
...
* When testing the fixed version, install upgrade u-u at this point checking
that u-u.service is set up before and is wanted by shutdown.target:
# systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" [color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
Color legend: black = Requires
dark blue = Requisite
dark grey = Wants
red = Conflicts
green = After
* Configure u-u to run on shutdown and install -updates:
# echo 'Unattended-Upgrade::InstallOnShutdown "true";' >
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too
* Downgrade snapd:
# apt install snapd=2.32.5+18.04
- * Dowload packages for u-u:
-# unattended-upgrade --download-only
- * Reboot using logind to let inhibitors hold up shutdown:
+ * Dowload packages for u-u:
+ # unattended-upgrade --download-only
+ * Reboot using logind to let inhibitors hold up shutdown:
# dbus-send --system --print-reply --dest=org.freedesktop.login1
/org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false
* With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
`-{unattended-upgr}
* With fixed u-u observe snapd update taking place and system rebooting
after a few seconds with all updates installed
* Since this fix is partially reverting the fix for LP: #1654600 please
test LP: #1654600 as well to avoid regressions.
[Regression Potential]
* As part of the fix manual changes were made to postinst to properly
transition from coupling u-u.service with multi-user.target to coupling it with
shutdown.target again which can make u-u started during normal boot when there
is a bug in the implementation.
on-testing the SRU.
* Due to relationship changes between u-u.service, other services and
targets u-u may fail to run on shutdown in case of an unexpected regression.
+ * There is a rarely occurring new crash caused by the (second) fix tracked in
LP: #1806487.
[Original Bug Text]
When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
package installation on various packages hangs until the systemd
ShutdownTimeout (30min) is expired and systemd kills all processes and
powers off/reboots the system.
This leaves packages in an unconfigured, broken state. At least
sometimes this cannot be fixed with a "dpkg --configure -a", but instead
requires the user to manually reinstall the package that caused the
hang.
This appears to be a deadlock, because the hanging commands are always
"systemctl stop ..." or "systemctl restart ...", etc.. If I understand
this correctly, those systemctl commands block because systemd tries to
shutdown the system and tries to satisfy all dependencies for the
shutdown targets before those systemctl commands could get executed,
which creates a deadlock.
Steps to reproduce:
- Install 18.04
- activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
- disable bionic-updates in /etc/apt/sources.list (more on that later)
- execute "unattended-upgrade --download-only"
- reboot the system
-> The upgrade on shutdown hangs when configuring the apport package.
The hanging command is "systemctl stop apport-forward.socket". The
system hangs until the systemd ShutdownTimeout expires and systemd
forcefully reboots the system.
After the system is rebooted the apport package is in "iUR" state, and
needs to be reinstalled to fix this.
I disabled the bionic-updates pocket in sources.list, because in the
default configuration unattended-updates does not use bionic-updates,
and seems to have skipped installation of apport from bionic-security
(supposedly because an already newer version of apport was
[Touch-packages] [Bug 1803137] Re: Unattended-upgrades may keep running after unmounting local filesystems in InstallOnShutdown mode
** Description changed: [Impact] * Unattended-upgrades may keep running during shutdown even beyond unmounting local filesystems potentially leaving a broken installation behind. * The fix reverts the original fix of LP: #1778219 and applies a different one starting unattended-upgrades-shutdown _before_ the shutdown transaction starts/ [Test Case] * Run unattended-upgrades in InstallOnShutdown mode and observe it being finished installing a few packages _before_ the shutdown transaction starts: $ lxc launch ubuntu:18.10 cc-uu-onshutdown Creating cc-uu-onshutdown Starting cc-uu-onshutdown $ lxc shell cc-uu-onshutdown mesg: ttyname failed: No such device root@cc-uu-onshutdown:~# apt update -qq 33 packages can be upgraded. Run 'apt list --upgradable' to see them. root@cc-uu-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@cc-uu-onshutdown:~# dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false method return time=1542112922.046290 sender=:1.4 -> destination=:1.13 serial=27 reply_serial=2 Session terminated, terminating shell...$ $ lxc shell cc-uu-onshutdown mesg: ttyname failed: No such device root@cc-uu-onshutdown:~# journalctl -l ... Nov 13 12:50:10 cc-uu-shutdown systemd[1]: Started Unattended Upgrades Shutdown. Nov 13 12:51:17 cc-uu-shutdown systemd-logind[228]: System is rebooting. ... root@cc-uu-shutdown:~# cat /var/log/unattended-upgrades/unattended-upgrades-shutdown.log ... 2018-11-13 12:51:13,835 WARNING - Running unattended-upgrades in shutdown mode 2018-11-13 12:51:13,852 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer 2018-11-13 12:51:15,482 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer 2018-11-13 12:51:17,151 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer 2018-11-13 12:51:17,166 INFO - All upgrades installed [Regression Potential] * The change reverts the behavior of unattended-upgrades-shutdown to be close to the behavior observed in Ubuntu 18.04, blocking the shutdown process reliably until is unattended-upgrades finished, but it starts _before_ shutdown triggered by the PrepareForShutdown() signal. Due to the shutdown not fully starting yet users may not get visual notification of unattended-upgrades running. In my testing on Bionic when a logged-in user shuts down the system when InstallOnShutdown is configured the user is dropped out to the login manager and nothing shows that u-u is running behind the screens for 30s, when the inhibition timer expires and u-u is starting to gracefully stop and the usual text appears after the login manager exits and plymouth shutdown screen is shown. The fix would be the login manager also monitoring PrepareForShutdown() and exiting (LP: #1803581). On Xenial (with Unity) starting shutdown from the graphical session does not log the user out nor show any progress on the shutdown until the inhibition timer expires which is confusing. Users should be logged out on PrepareForShutdown() (LP: #1803581). * The reversion of unattended-upgrades.service was not complete in u-u 1.7 and needed a further fix in 1.7ubuntu1 (which fix is already included in 1.5ubuntu4). This part may be source of potential regressions. * The fix itself rewrites big part of unattended-upgrades-shutdown and this rewrite could cause regressions in running unattended-upgrades in InstallOnShutdown mode, but also this mode was extensively tested. * The fix includes increasing logind's InhibitDelayMaxSec to 30s to give u-u enough time to gracefully stop in normal mode and install packages in InstallOnShutdown mode. The delay is global, thus any other program holding the lock can delay shutdown or sleep by 30s instead of the original 5s default. This regression is hard to avoid and the 30s was chosen to minimize the regression potential while still giving more than 5s to u-u to finish actions. Bugs reporting increased delay to sleep or shutdown should be monitored to catch other programs misbehaving with this new default. + * There is a rarely occurring new crash caused by this fix tracked in + LP: #1806487. + [Other Info] This is a regression of introduced in LP: #1778219 and can be observed in a cosmic lxd container easily: $ lxc launch ubuntu:18.10 cc-uu-onshutdown Creating cc-uu-onshutdown Starting cc-uu-onshutdown $ lxc shell cc-uu-onshutdown mesg: ttyname failed: No such device root@cc-uu-onshutdown:~# apt update -qq 33 packages can be upgraded. Run 'apt list --upgradable' to see them. root@cc-uu-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt
[Touch-packages] [Bug 1808275] Re: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped
I have tried rebooting multiple times after all the suggestions that I could find on this issue on the net. It still doesn't seem to work. -- 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/1808275 Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped Status in pulseaudio package in Ubuntu: Incomplete Bug description: The green headphone out was working and I changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped and changing it back to Analog Output didn't restore the sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 12 23:10:39 2018 InstallationDate: Installed on 2018-12-06 (7 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97510J.86A.1487.2007.0902.1724 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX dmi.board.vendor: Intel Corporation dmi.board.version: AAD27094-305 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-305:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1808275/+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 1806487] Re: /usr/share/unattended-upgrades/unattended-upgrade-shutdown:dbus.exceptions.DBusException(org.freedesktop.DBus.Error.TimedOut):activate_name_owner:get_name_owner:call
** Description changed: [Impact] * Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start. * Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process. * The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence. [Test Case] * Stop systemd-logind and make it unable to start for example by masking it: root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service - root@bb-logind:~# rm /etc/systemd/system/systemd-logind root@bb-logind:~# systemctl daemon-reload root@bb-logind:~# service systemd-logind stop root@bb-logind:~# service systemd-logind status ● systemd-logind.service Loaded: masked (/dev/null; bad) Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago Main PID: 1938 (code=killed, signal=TERM) Status: "Processing requests..." ... * Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock - at its start. + at its start: + + root@bb-logind:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug + root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log + ... + 2018-12-13 14:30:17,600 WARNING - Could not get delay inhibitor lock + 2018-12-13 14:30:17,601 DEBUG - Skip waiting for signals, starting operation now + 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes + 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration + 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 + 2018-12-13 14:30:17,602 DEBUG - lock not taken + * Restore logind's ability to start + + root@bb-logind:~# rm /etc/systemd/system/systemd-logind.service + root@bb-logind:~# systemctl daemon-reload + * Restart unattended-upgrades.service - root@bb-logind:~# systemctl daemon-reload root@bb-logind:~# service unattended-upgrades restart - root@bb-logind:~# service unattended-upgrades status + root@bb-logind:~# 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 Thu 2018-12-13 13:08:13 UTC; 16s ago - Docs: man:unattended-upgrade(8) - Main PID: 2079 (unattended-upgr) - Tasks: 2 (limit: 4915) - CGroup: /system.slice/unattended-upgrades.service - └─2079 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal +Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) +Active: active (running) since Thu 2018-12-13 14:31:43 UTC; 3s ago + Docs: man:unattended-upgrade(8) + Main PID: 4129 (unattended-upgr) + Tasks: 2 (limit: 4915) +CGroup: /system.slice/unattended-upgrades.service +└─4129 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal - Dec 13 13:08:13 bb-logind systemd[1]: Started Unattended Upgrades Shutdown. + Dec 13 14:31:43 bb-logind systemd[1]: Started Unattended Upgrades Shutdown. + root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log + 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes + 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration + 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 + 2018-12-13 14:30:17,602 DEBUG - lock not taken + 2018-12-13 14:31:43,595 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running + 2018-12-13 14:31:43,688 WARNING - Could not get delay inhibitor lock + 2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead. + 2018-12-13 14:31:43,691 WARNING - Maybe systemd-logind service is not running. + 2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead. + 2018-12-13 14:31:43,691 WARNING - To enable monitoring the PrepareForShutdown() signal instead of polling please install the python3-gi package + root@bb-logind:~# systemd-analyze dot | grep unattended ... "unattended-upgrades.service"->"systemd-logind.service" [color="green"]; ... [Regression Potential] * The change to service ordering is unlikely to cause any issue, but the graceful handling of missing logind involved a small-scale refactoring of u-u-s's code. Extensive testing did not reveal regressions in that area
[Touch-packages] [Bug 1807023] Please test proposed package
Hello Mauricio, or anyone else affected, Accepted ca-certificates into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ca- certificates/20170717~14.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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1807023 Title: installer stock images fail to validate any HTTPS certificates (ca- certificates missing) Status in debian-installer: Fix Released Status in ca-certificates package in Ubuntu: Invalid Status in debian-installer package in Ubuntu: Fix Released Status in ca-certificates source package in Trusty: Fix Committed Status in debian-installer source package in Trusty: Fix Committed Status in ca-certificates source package in Xenial: Fix Committed Status in debian-installer source package in Xenial: Fix Committed Status in ca-certificates source package in Bionic: Invalid Status in debian-installer source package in Bionic: Fix Committed Status in ca-certificates source package in Cosmic: Invalid Status in debian-installer source package in Cosmic: Fix Committed Status in ca-certificates source package in Disco: Invalid Status in debian-installer source package in Disco: Fix Released Status in debian-installer package in Debian: Fix Released Bug description: [Impact] * The installer stock images fail to validate any HTTPS certificates because ca-certificates is not available in the installer environment. * This causes wget/download errors for preseed files on HTTPS servers (or HTTP servers that redirect to HTTPS, which are increasingly common nowadays - e.g., GitHub) and theoretically any other files that are downloaded with d-i-utils/fetch-url/wget. * The fix is to ship ca-certificates-udeb in installer stock images. * Debian already ships ca-certificate-udeb in the stock installer images; the fix is applied since Jan 2017. (reference: Debian Bug #842040 / d-i commit 2f00c51a [1]) [Test Case] * In the installer shell: ~ # wget http://github.com # or https://github.com - FAIL if ca-certificates-udeb is missing: "ERROR: cannot verify github.com's certificate, <...>' - PASS if ca-certificates-udeb is available "Saving to: 'index.html'" * Test steps with virt-install and netboot images are provided in the comments, for each release. [Regression Potential] * Low. This just adds the ca-certificates files in /etc/ssl/certs and symlink in /usr/lib/ssl/certs, so only tools looking for that would be affected. * Apparently only wget checks for/uses those files, and the difference in behavior is download errors no longer occur. [Notes] * The ca-certificates-udeb is not currently present in the Ubuntu 'main' component, but in 'universe', despite the normal deb being in 'main'. However, when rebuilding in a PPA it goes into 'main' accordingly, and can be used by default by debian-installer (otherwise, UDEB_COMPONENTS has to be modified to include universe/d-i). * So this fix includes a no-change-rebuild for the ca-certificates package, in order to publish the udeb in the archive (at least in PPA for testing). Hopefully that can be sorted out for this fix to work out. * The ca-certificates and debian-installer builds have been done in a PPA using all architectures, and testing has been done with the amd64 images. * This fix is requested for Bionic, Cosmic, Disco at least. * The fix for Trusty and Xenial needed a little bit more work to build/ship the (new) udeb. (reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2]) It would be good to have them too if at all possible. [1] https://salsa.debian.org/installer-team/debian-installer/comm
