[Group.of.nepali.translators] [Bug 1894849] Re: autopkgtest failing
autopkgtest is still broken in Xenial and Bionic. ** Also affects: snapcraft (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: snapcraft (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1894849 Title: autopkgtest failing Status in snapcraft package in Ubuntu: Fix Released Status in snapcraft source package in Xenial: New Status in snapcraft source package in Bionic: New Status in snapcraft source package in Focal: Fix Released Status in snapcraft source package in Groovy: Fix Released Bug description: The autopkgtest runs the following code: snapcraft version | grep "snapcraft, version 3.*" But this is no longer true, snapcraft is now at version 4. * SRU [Impact] * Breaks autopkgtests, e.g. for snapd [Test Case] * run autopkgtest, observe failure [Regression Potential] * very low, autopkgtest tests are currently broken, worst case is that they are still broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1894849/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1755310] Re: MIR libzstd
** Also affects: libzstd (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1755310 Title: MIR libzstd Status in libzstd package in Ubuntu: Fix Released Status in libzstd source package in Xenial: New Bug description: [Availability] * In Universe, on all supported arches, since xenial [Rationale] * In use by btrfs-progs[-udeb] in main * To be used by apt & dpkg * Already in use by the kernel for initramfs compression, however that is using in-kernel implementation [Security] * https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=zstd -> none * Hardenening flags is available * There are some compiler warnings [Quality assurance] * Maintained in debian med team * xnox has upload rights, and fixed up for it to be Multi-arch sane * testsuite is enabled and passing * lacks autopkgtests, could be added to run the test-suite [Dependencies] * Currently has only glibc as depedency * Command line tool can be compiled with gzip (already eanbled), xz/lzma/lz4 (not enabled), thus making the zstd util to cover all cases of compress/decompress/cat/less for any of these algos. [Standards compliance] * Complies with debian packaging guidelines * Currently does not build reproducibly [Maintenance] * Med, D-I teams in Debian, and foundations in Ubuntu [Background information] * A new compression algorithm from facebook, which is comparable to gzip, yet faster / less resource intensive than xz. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzstd/+bug/1755310/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1764220] Re: [SRU] dpkg zstd support
** Summary changed: - [FFe] dpkg zstd support + [SRU] dpkg zstd support ** Also affects: dpkg (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1764220 Title: [SRU] dpkg zstd support Status in dpkg: Incomplete Status in dpkg package in Ubuntu: Fix Released Status in dpkg source package in Xenial: New Bug description: As discussed previously, we want to have zstd support in 18.04 to evaluate and potentially enable it in later releases. The zstd support adds a dependency on libzstd1 to dpkg. This should not have any effect on live images, since libzstd1 is part of the various live tasks, as btrfs-progs need it. For installed systems, this might be a new dependency (if they do not use btrfs, tor, or some other tools), so an increase of ~520 KB, as that's the size of the library and the library only depends on libc6. The change is isolated, it adds the compressor and decompressor to dpkg, please see the attached patch for the details. The change is being discussed here: https://lists.ubuntu.com/archives/ubuntu-devel/2018-March/040211.html https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664 To manage notifications about this bug go to: https://bugs.launchpad.net/dpkg/+bug/1764220/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Bug watch added: Debian Bug tracker #984573 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984573 ** Also affects: docker.io (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984573 Importance: Unknown Status: Unknown ** No longer affects: docker.io (Debian) ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984573 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Committed Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Committed Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Unknown Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg
[Group.of.nepali.translators] [Bug 1404003] Re: glibc vulnerability CVE-2014-9402
** Also affects: glibc (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: eglibc (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: eglibc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: eglibc (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu Xenial) Status: New => Fix Released ** Changed in: glibc (Ubuntu Bionic) Status: New => Fix Released ** Changed in: glibc (Ubuntu Focal) Status: New => Fix Released ** Changed in: glibc (Ubuntu) Status: Triaged => Fix Released ** Changed in: eglibc (Ubuntu Xenial) Status: New => Invalid ** Changed in: eglibc (Ubuntu Bionic) Status: New => Invalid ** Changed in: eglibc (Ubuntu Focal) Status: New => Invalid ** Changed in: eglibc (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1404003 Title: glibc vulnerability CVE-2014-9402 Status in eglibc package in Ubuntu: Invalid Status in glibc package in Ubuntu: Fix Released Status in eglibc source package in Xenial: Invalid Status in glibc source package in Xenial: Fix Released Status in eglibc source package in Bionic: Invalid Status in glibc source package in Bionic: Fix Released Status in eglibc source package in Focal: Invalid Status in glibc source package in Focal: Fix Released Bug description: https://sourceware.org/bugzilla/show_bug.cgi?id=17630 https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=11e3417af6e354f1942c68a271ae51e892b2814d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1404003/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1605635] Re: [SRU] Please backport pollen
This is unlikely to happen since Xenial is entering ESM period soon. ** Changed in: pollen (Ubuntu Trusty) Status: Fix Committed => Won't Fix ** Changed in: pollen (Ubuntu Xenial) Status: Fix Committed => Won't Fix ** Changed in: pollen (Ubuntu) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1605635 Title: [SRU] Please backport pollen Status in pollen package in Ubuntu: Won't Fix Status in pollen source package in Trusty: Won't Fix Status in pollen source package in Xenial: Won't Fix Bug description: Please backport pollen version >=4.21 to Trusty and Xenial. [Impact] We need a newer version of pollen running on entropy.ubuntu.com. Canonical IS requires that the package be updated in trusty-updates in order for this to happen. We need a couple of things fixed: improved error logging and entropy available monitoring, [Test Case] Start a new Ubuntu instance (trusty, xenial). sudo apt install pollen pollinate. Then, try running pollinate against localhost: 'sudo pollinate -r -s http://localhost:80'. Also, check that an appropriate message is logged in /var/log/syslog. grep pollen /var/log/syslog. [Regression Potential] The regression potential is mostly around the upstart/systemd jobs. We should just be sure that the service starts/stops/restarts cleanly, and comes up automatically at boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1605635/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Committed Status in systemd source package in Bionic: New Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Committed Status in systemd source package in Focal: New Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Committed Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The
[Group.of.nepali.translators] [Bug 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii
** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806076 Title: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in apt source package in Xenial: New Status in unattended-upgrades source package in Xenial: Won't Fix Status in apt source package in Bionic: Triaged Status in unattended-upgrades source package in Bionic: Won't Fix Bug description: [Test Case] rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076 Creating bb-lp-1806076 Starting bb-lp-1806076 rbalint@yogi:~$ lxc shell bb-lp-1806076 mesg: ttyname failed: No such device root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base 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: language-pack-ru The following NEW packages will be installed: language-pack-ru language-pack-ru-base 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. Need to get 2310 kB of archives. After this operation, 11.8 MB of additional disk space will be used. Selecting previously unselected package language-pack-ru-base. (Reading database ... 28536 files and directories currently installed.) Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru-base (1:18.04+20180712) ... Selecting previously unselected package language-pack-ru. Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru-base (1:18.04+20180712) ... Generating locales (this might take a while)... ru_RU.UTF-8... done ru_UA.UTF-8... done Generation complete. root@bb-lp-1806076:~# env LANG=ru_RU unattended-upgrade --help | cat Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1983, in (options, args) = parser.parse_args() # type: ignore File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args stop = self._process_args(largs, rargs, values) File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args self._process_long_opt(rargs, values) File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt option.process(opt, value, values, self) File "/usr/lib/python3.6/optparse.py", line 785, in process self.action, self.dest, opt, value, values, parser) File "/usr/lib/python3.6/optparse.py", line 807, in take_action parser.print_help() File "/usr/lib/python3.6/optparse.py", line 1647, in print_help file.write(self.format_help()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 126-133: ordinal not in range(128) root@bb-lp-1806076:~# env LANG=ru_RU.UTF-8 unattended-upgrade --help | cat Usage: unattended-upgrade [options] Options: -h, --helpshow this help message and exit -d, --debug print debug messages --apt-debug make apt/libapt print verbose debug messages -v, --verbose print info messages --dry-run Simulation, download but do not install --download-only Only download, do not even try to install. --minimal-upgrade-steps Upgrade in minimal steps (and allow interrupting with SIGTERM [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.6, the problem page at https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 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/. Also seen in: * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1806076/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Changed in: glibc (Ubuntu Xenial) Status: New => Invalid ** Changed in: glibc (Ubuntu Bionic) Status: New => Invalid ** Changed in: glibc (Ubuntu Focal) Status: New => Invalid ** Changed in: glibc (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in glibc source package in Xenial: Invalid Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in glibc source package in Bionic: Invalid Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: New Status in systemd source package in Bionic: New Status in docker.io source package in Focal: New Status in glibc source package in Focal: Invalid Status in libseccomp source package in Focal: New Status in runc source package in Focal: New Status in systemd source package in Focal: New Status in docker.io source package in Groovy: New Status in glibc source package in Groovy: Invalid Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: New Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Status in systemd source package in Hirsute: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2
[Group.of.nepali.translators] [Bug 1916485] Re: test -x fails inside shell scripts in containers
Running "test -x ..." also fails in systemd-nspawn for systemd < 247, I think only the following patch needs to be SRU-d to earlier systemd versions: https://github.com/systemd/systemd/commit/bcf08acbffdee0d6360d3c31d268e73d0623e5dc ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Hirsute) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in glibc source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in glibc source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: New Status in systemd source package in Bionic: New Status in docker.io source package in Focal: New Status in glibc source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: New Status in systemd source package in Focal: New Status in docker.io source package in Groovy: New Status in glibc source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: New Status in systemd source package in Groovy: New Status in docker.io source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Status in systemd source package in Hirsute: Fix Released Bug description: glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl https://syncthing.net/release-key.txt | apt-key add - Breaking it down it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container. So adding keys in unpriviledged container or possibly kubernetes will not work anymore. Flo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to :
[Group.of.nepali.translators] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Changed in: docker.io (Ubuntu Hirsute) Importance: Undecided => Critical ** Changed in: glibc (Ubuntu Hirsute) Status: Triaged => Opinion -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in docker.io source package in Xenial: New Status in glibc source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in docker.io source package in Bionic: New Status in glibc source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: New Status in docker.io source package in Focal: New Status in glibc source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: New Status in docker.io source package in Groovy: New Status in glibc source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: New Status in docker.io source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Bug description: glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl https://syncthing.net/release-key.txt | apt-key add - Breaking it down it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container. So adding keys in unpriviledged container or possibly kubernetes will not work anymore. Flo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1915547] Re: sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial
Fixed in 2.8.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1915547
Title:
sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to
1.1ubuntu1.18.04.7~16.04.7 ) Xenial
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Triaged
Bug description:
== Begin SRU Template ==
[Impact]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08
19:21:39
+++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644
2020-02-17 18:03:38
@@ -1,11 +1,13 @@
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
The reason we are presented with this diff is that the xenial package
does not contain a md5sum history file that informs ucf about all the
supported configs for 50unattended-upgrades. To fix that upgrade
problem, we are prosing the following changes on the xenial package of
unattended-upgrades:
- Add 50unattended-upgrades.md5sum file into the xenial package
- Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
- Modify ucf command in postinst to be aware of the md5sum history file
See the changelog entry below for a full list of changes and bugs.
[Test Case]
We have performed a manual test with a modified version of the xenial package:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
Using that package, we were able to verify that the config change
prompt no longer happens from trusty to xenial.
[Regression Potential]
Since we are modifying are features on unattended-upgrades, just adding a new
file to package, we don't believe there is any regression potential
[Discussion]
== End SRU Template ==
== Changelog ==
* data: add md5sum history file on the data folder
- This file contains md5sum of several supported 50unattended-upgrades
config files
* data: add xenial md5sum of 50unattented-upgrades into md5sum file
* debian/postint: make ucf command reference the md5sum history file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1915547/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1896638] Re: Path to swapfile doesn't use a static device path
Hibagent is affected as well. https://github.com/aws/ec2-hibernate-linux-agent/issues/8 ** Also affects: hibagent (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/aws/ec2-hibernate-linux-agent/issues #8 https://github.com/aws/ec2-hibernate-linux-agent/issues/8 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1896638 Title: Path to swapfile doesn't use a static device path Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in hibagent package in Ubuntu: New Status in ec2-hibinit-agent source package in Xenial: Fix Released Status in hibagent source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in hibagent source package in Bionic: New Status in ec2-hibinit-agent source package in Focal: Fix Released Status in hibagent source package in Focal: New Status in ec2-hibinit-agent source package in Groovy: Fix Released Status in hibagent source package in Groovy: New Bug description: [Impact] * Using the device name on the kernel cmdline in the resume= option leads to failure to resume from hibernation when the device name is not stable, which can be the case for nvme drives. [Test Case] * Set up an EC2 instance to allow hibernation * Wait for hibinit-agent.service fully started * /etc/default/grub.d/99-set-swap.cfg should refer to the resume= partition by PARTUUID [Regression Potential] * Failure to discover PARTUUID makes the system unable to resume. A potential crash would cause the system unable to set up hibernation or unable to resume. (On Focal PARTUUID is already in use, even without this fix.) [Original Bug Text] When the agent inserts the resume device path and offset into the kernel cmdline, it uses device names such as the following: `resume_offset=223232 resume=/dev/nvme1n1p1` The issue is that `/dev/nvme1n1p1` is not static. On the reboot, the block device may appear at `/dev/nvme0n1p1` resulting in failure to find the swapfile used to suspend. The solution should be to use a persistent block device naming scheme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1896638/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1911689] Re: Please update to upstream release 20210112.00
Release for Xenial is blocked on https://github.com/GoogleCloudPlatform/osconfig/issues/279 . ** Also affects: google-osconfig-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Bug watch added: github.com/GoogleCloudPlatform/osconfig/issues #279 https://github.com/GoogleCloudPlatform/osconfig/issues/279 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1911689 Title: Please update to upstream release 20210112.00 Status in google-osconfig-agent package in Ubuntu: Fix Committed Status in google-osconfig-agent source package in Xenial: New Status in google-osconfig-agent source package in Bionic: Fix Committed Status in google-osconfig-agent source package in Focal: Fix Committed Status in google-osconfig-agent source package in Groovy: Fix Committed Bug description: [Impact] This package is provided by Google for installation within guests that run on Google Compute Engine. It is part of a collection of tools and daemons, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating this package to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of this package is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/1911689/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1911911] [NEW] Make dh-golang work with golang-1.13 in Xenial and Bionic
Public bug reported:
[Impact]
The following environment variables need to be properly in packages'
debian/rules to use golang-1.13 in Bionic and earlier releases:
export GOCACHE := ${CURDIR}/_build/go-build
export GO111MODULE = off
This is redundant and a growing number of packages need golang-1.13 to
build.
** Affects: dh-golang (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: dh-golang (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: dh-golang (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: dh-golang (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: dh-golang (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: dh-golang (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1911911
Title:
Make dh-golang work with golang-1.13 in Xenial and Bionic
Status in dh-golang package in Ubuntu:
Fix Released
Status in dh-golang source package in Xenial:
New
Status in dh-golang source package in Bionic:
New
Bug description:
[Impact]
The following environment variables need to be properly in packages'
debian/rules to use golang-1.13 in Bionic and earlier releases:
export GOCACHE := ${CURDIR}/_build/go-build
export GO111MODULE = off
This is redundant and a growing number of packages need golang-1.13 to
build.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-golang/+bug/1911911/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1908136] Re: no_proxy=::1 is not honored in Bionic and earlier versions
Upstream bug: https://github.com/curl/curl/issues/2353 ** Also affects: auto-package-testing Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1908136 Title: no_proxy=::1 is not honored in Bionic and earlier versions Status in Auto Package Testing: New Status in curl package in Ubuntu: Fix Released Status in curl source package in Xenial: New Status in curl source package in Bionic: New Status in curl source package in Focal: Fix Released Bug description: Bionic: env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Could not resolve proxy: foo * Closing connection 0 curl: (5) Could not resolve proxy: foo Focal: $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Uses proxy env variable no_proxy == '::1' * Trying ::1:80... * TCP_NODELAY set * Immediate connect fail for ::1: Network is unreachable * Closing connection 0 curl: (7) Couldn't connect to server To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1908136] [NEW] no_proxy=::1 is not honored in Bionic and earlier versions
Public bug reported: Bionic: env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Could not resolve proxy: foo * Closing connection 0 curl: (5) Could not resolve proxy: foo Focal: $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Uses proxy env variable no_proxy == '::1' * Trying ::1:80... * TCP_NODELAY set * Immediate connect fail for ::1: Network is unreachable * Closing connection 0 curl: (7) Couldn't connect to server ** Affects: auto-package-testing Importance: Undecided Status: New ** Affects: curl (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: curl (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: curl (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: curl (Ubuntu Focal) Importance: Undecided Status: Fix Released ** Also affects: curl (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: curl (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: curl (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: curl (Ubuntu Focal) Status: New => Fix Released ** Changed in: curl (Ubuntu) Status: New => Fix Released ** Bug watch added: github.com/curl/curl/issues #2353 https://github.com/curl/curl/issues/2353 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1908136 Title: no_proxy=::1 is not honored in Bionic and earlier versions Status in Auto Package Testing: New Status in curl package in Ubuntu: Fix Released Status in curl source package in Xenial: New Status in curl source package in Bionic: New Status in curl source package in Focal: Fix Released Bug description: Bionic: env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Could not resolve proxy: foo * Closing connection 0 curl: (5) Could not resolve proxy: foo Focal: $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Uses proxy env variable no_proxy == '::1' * Trying ::1:80... * TCP_NODELAY set * Immediate connect fail for ::1: Network is unreachable * Closing connection 0 curl: (7) Couldn't connect to server To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1899629] Re: [SRU] Please update to upstream release 20200925.00
** Changed in: gce-compute-image-packages (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1899629 Title: [SRU] Please update to upstream release 20200925.00 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in google-compute-engine-oslogin package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in google-compute-engine-oslogin source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Bionic: Fix Released Status in google-compute-engine-oslogin source package in Bionic: Fix Released Status in gce-compute-image-packages source package in Focal: Fix Released Status in google-compute-engine-oslogin source package in Focal: Fix Released Bug description: [Impact] Google-compute-engine-oslogin is provided by Google for installation within guests that run on Google Compute Engine. It part of the collection of tools and daemons originally packaged as gce-compute- image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating google-compute-engine-oslogin to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of google-compute-engine-oslogin is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] Since google-compute-engine-oslogin is split off from gce-compute- image-packages, gce-compute-image-packages should also be updated to not build the OS Login package. This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1899629/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1898087] Re: Please disable suspend when the package is installed
Thanks, marking Bionic and Xenial as won't fix. Please reopen the bug against those releases if the SRU becomes needed. ** Changed in: ec2-hibinit-agent (Ubuntu Xenial) Status: Incomplete => Won't Fix ** Changed in: ec2-hibinit-agent (Ubuntu Bionic) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1898087 Title: Please disable suspend when the package is installed Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in ec2-hibinit-agent source package in Xenial: Won't Fix Status in ec2-hibinit-agent source package in Bionic: Won't Fix Status in ec2-hibinit-agent source package in Focal: Fix Committed Bug description: [Impact] Enabling CONFIG_SUSPEND in the kernel exposes a potential deadlock on Xen instance types on AWS during hibernation, so it has been disabled in the linux-aws kernel as an extra safety measure to prevent this problem from happening. [Test Case] Try to suspend the system as a regular user: $ /lib/systemd/systemd-sleep suspend Sleep mode "suspend" is disabled by configuration, refusing. On a system where this change is not present permission error appears: $ /lib/systemd/systemd-sleep suspend Failed to open /sys/power/state: Permission denied [Regression Potential] The fix is placing a configuration file drop-in to prevent the system from suspending. On EC2 instances this is unlikely to cause unwanted side effects, since suspended instances can't be woken up. Outside of EC2 there is no use of the package itself, but this change disable suspend when the package is installed. [Original Bug Text] From LP: #1892728 We also need to set "AllowSuspend=no" in /etc/systemd/sleep.conf (or a .d file) as CONFIG_SUSPEND has been disabled in the kernel to improve the robustness of hibernation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1898087/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1756209] Re: i386 implementation of memmove broken since glibc 2.21
** Changed in: glibc (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1756209 Title: i386 implementation of memmove broken since glibc 2.21 Status in glibc package in Ubuntu: Fix Released Status in glibc source package in Xenial: New Status in glibc source package in Bionic: Fix Released Bug description: [Impact] * i386 memmove breaks when crossing the 2GB threshold. [Test Case] * Compile and run the reproducer as described at https://github.com/fingolfin/memmove-bug or observe string/test- memmove test passing during the build/autopkgtest on i386. [Regression Potential] * Can break memmove, but this is unlikely since memmove is the very function fixed by fixing signedness handling. [Original Bug Text] In glibc 2.21 they optimized i386 memcpy: https://sourceware.org/ml/libc-alpha/2015-02/msg00119.html The implementation contained a bug which causes memmove to break when crossing the 2GB threshold. This has been filed with glibc here (filed by someone else, but I have requested an update from them as well): https://sourceware.org/bugzilla/show_bug.cgi?id=22644 Unfortunately they have not yet taken action on this bug, however I want to bring it to your attention in the hope that it can be patched into all current Ubuntu releases as soon as possible. I hope this is not improper procedure. Both myself and another (see comment 1 in the glibc bug report) have tested the patch provided in the above glibc bug report and it does appear to fix the problem, however I don't know what the procedure is for getting it properly confirmed/tested and merged into Ubuntu. As requested in the guidelines: 1) We are using: Description:Ubuntu 16.04.4 LTS Release:16.04 2) libc6:i386: Installed: 2.23-0ubuntu10 However as stated above this has been present since libc6:i386 2.21 and affects Ubuntu 15.04 onward. (I have actually tested this as well. 15.04 conveniently used both glibc 2.19 and 2.21 so it was a good test platform when I was initially attempting to track down the problem.) 3) What we expected to happen: memmove should move data within the entire valid address space without segfaulting or corrupting memory. 4) What happened instead: When memmove attempts to move data crossing the 2GB threshold it either segfaults or causes memory corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1756209/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
** Changed in: ec2-hibinit-agent (Ubuntu Xenial) Status: Incomplete => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Xenial: Invalid Status in linux-aws source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: Fix Released Status in linux-aws source package in Eoan: Won't Fix Status in ec2-hibinit-agent source package in Focal: Fix Released Status in linux-aws source package in Focal: New Bug description: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. [Regression Potential] The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel module before restarting systemd-networkd. If the kernel module is removed (for example when hitting LP: #1615381) the module reloading fails and the instance can not restore network connections. This is expected to a be very rare situation and the module reload is the best workaround the Kernel Team found to mitigate the original issue. The workaround also adds a 2 second delay before reloading the modules to let things settle a bit after resuming. The 2 seconds is very short compared to the overall time needed resuming an instance. [Original Bug Text] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1863242] Re: [SRU] OOM errors with new kernels on resuming
@fginther Xenial does not need the backport, right? ** Also affects: ec2-hibinit-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ec2-hibinit-agent (Ubuntu Xenial) Status: New => Incomplete -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1863242 Title: [SRU] OOM errors with new kernels on resuming Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in ec2-hibinit-agent source package in Xenial: Incomplete Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in ec2-hibinit-agent source package in Eoan: Fix Released Bug description: [Impact] * During resuming EC2 instances from hibernation sometimes processes are killed OOM manager. [Test Case] * Set up an EC2 instance to allow hibernation as the stop instance action. * Start the attached Python script in a screen session to reserve 85% of the memory: python3 mem-waster-pct.py -p 85 * Log out, hibernate, then resume the instance. * Observe the Python script still running after resuming [Regression Potential] * The fix is setting memory overcommit policy to 'always overcommit' while removing the swap file. This helps dealing with the shrinking swap space during the swap removal. There is no expected side effect, since processes trying to allocate excessive amount of memory would fail with stricter policies, too. The fix introduces a potential race condition with processes detecting the overcommit policy: The policy used when the hibernation took place is saved shortly after resuming and it is restored after the swap file is removed. In this time window other processes detect the policy as 'always overcommit', despite it may not have been set as such before hibernation and may be restored to a different policy after removing the swap file. Hitting this race condition seems to be unlikely and there seem to be no good way of avoiding it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1863242/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
@fginther Xenial does not need the backport, right? ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ec2-hibinit-agent (Ubuntu Xenial) Status: New => Incomplete -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Xenial: Incomplete Status in linux-aws source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: Fix Released Status in linux-aws source package in Eoan: Won't Fix Status in ec2-hibinit-agent source package in Focal: Fix Released Status in linux-aws source package in Focal: New Bug description: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. [Regression Potential] The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel module before restarting systemd-networkd. If the kernel module is removed (for example when hitting LP: #1615381) the module reloading fails and the instance can not restore network connections. This is expected to a be very rare situation and the module reload is the best workaround the Kernel Team found to mitigate the original issue. The workaround also adds a 2 second delay before reloading the modules to let things settle a bit after resuming. The 2 seconds is very short compared to the overall time needed resuming an instance. [Original Bug Text] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions ___
[Group.of.nepali.translators] [Bug 1896638] Re: Path to swapfile doesn't use a static device path
** Changed in: ec2-hibinit-agent (Ubuntu Focal) Status: New => Invalid ** Changed in: ec2-hibinit-agent (Ubuntu Groovy) Status: New => Invalid ** Changed in: ec2-hibinit-agent (Ubuntu Bionic) Status: New => Confirmed ** Changed in: ec2-hibinit-agent (Ubuntu Focal) Status: Invalid => Confirmed ** Changed in: ec2-hibinit-agent (Ubuntu Groovy) Status: Invalid => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1896638 Title: Path to swapfile doesn't use a static device path Status in ec2-hibinit-agent package in Ubuntu: Confirmed Status in ec2-hibinit-agent source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Confirmed Status in ec2-hibinit-agent source package in Focal: Confirmed Status in ec2-hibinit-agent source package in Groovy: Confirmed Bug description: When the agent inserts the resume device path and offset into the kernel cmdline, it uses device names such as the following: `resume_offset=223232 resume=/dev/nvme1n1p1` The issue is that `/dev/nvme1n1p1` is not static. On the reboot, the block device may appear at `/dev/nvme0n1p1` resulting in failure to find the swapfile used to suspend. The solution should be to use a persistent block device naming scheme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1896638/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1898087] Re: Please disable suspend when the package is installed
Should this be back-ported to Bionic and Xenial, too? ** Also affects: ec2-hibinit-agent (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ec2-hibinit-agent (Ubuntu Xenial) Status: New => Incomplete ** Changed in: ec2-hibinit-agent (Ubuntu Bionic) Status: New => Incomplete ** Changed in: ec2-hibinit-agent (Ubuntu Focal) Status: New => In Progress ** Changed in: ec2-hibinit-agent (Ubuntu) Status: Confirmed => In Progress ** Changed in: ec2-hibinit-agent (Ubuntu Focal) Status: In Progress => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1898087 Title: Please disable suspend when the package is installed Status in ec2-hibinit-agent package in Ubuntu: In Progress Status in ec2-hibinit-agent source package in Xenial: Incomplete Status in ec2-hibinit-agent source package in Bionic: Incomplete Status in ec2-hibinit-agent source package in Focal: Confirmed Bug description: From LP: #1892728 We also need to set "AllowSuspend=no" in /etc/systemd/sleep.conf (or a .d file) as CONFIG_SUSPEND has been disabled in the kernel to improve the robustness of hibernation. [Test Case] Try to suspend the system as a regular user: $ /lib/systemd/systemd-sleep suspend Sleep mode "suspend" is disabled by configuration, refusing. On a system where this change is not present permission error appears: $ /lib/systemd/systemd-sleep suspend Failed to open /sys/power/state: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1898087/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 182629] Re: gksu crashed with SIGSEGV in gdk_window_set_opacity()
The last release where gksu was present is Xenial. ** Also affects: gksu (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: gksu (Ubuntu Xenial) Status: New => Triaged ** Changed in: gksu (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/182629 Title: gksu crashed with SIGSEGV in gdk_window_set_opacity() Status in GKSu: New Status in gksu package in Ubuntu: Invalid Status in gksu source package in Xenial: Triaged Status in gksu package in Debian: New Bug description: can't add new users ProblemType: Crash Architecture: i386 Date: Sun Jan 13 18:34:36 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/gksu Package: gksu 2.0.0-5ubuntu1 PackageArchitecture: i386 ProcCmdline: /usr/bin/gksu --desktop /usr/share/applications/synaptic.desktop -- /usr/sbin/synaptic --hide-main-window --non-interactive -o Synaptic::closeZvt=true --parent-window-id 23068675 --set-selections-file /tmp/tmpeHSTcC ProcCwd: /home/yaya ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: gksu Stacktrace: #0 0xb7afd24c in gdk_window_set_opacity () from /usr/lib/libgdk-x11-2.0.so.0 #1 0xb7f5a96c in ?? () from /usr/lib/libgksu2.so.0 #2 0x61706573 in ?? () #3 0x in ?? () StacktraceTop: gdk_window_set_opacity () from /usr/lib/libgdk-x11-2.0.so.0 ?? () from /usr/lib/libgksu2.so.0 ?? () ?? () Title: gksu crashed with SIGSEGV in gdk_window_set_opacity() Uname: Linux juju-laptop 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev scanner video SegvAnalysis: Segfault happened at: 0xb7afd24c :mov (%edi),%edx PC (0xb7afd24c) ok source "(%edi)" (0x61706573) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA To manage notifications about this bug go to: https://bugs.launchpad.net/gksu/+bug/182629/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1698388] Re: Assertion failure in journal-remote-parse.c
Fixed in Bionic and later. ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1698388 Title: Assertion failure in journal-remote-parse.c Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Bug description: I am observing the following assertion failure in systemd-journal- remote: Assertion 'source->filled <= source->size' failed at ../src/journal- remote/journal-remote-parse.c:95, function get_line(). Aborting. Systemd version: systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Ubuntu release: Description: Ubuntu 16.04.1 LTS Release: 16.04 Package version: systemd: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu17 It looks like this issue has been fixed upstream in v230, specifically in commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1. Could this particular commit be backported? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698388/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii
** Changed in: unattended-upgrades (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806076 Title: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in apt source package in Xenial: New Status in unattended-upgrades source package in Xenial: New Status in apt source package in Bionic: New Status in unattended-upgrades source package in Bionic: New Bug description: [Test Case] rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076 Creating bb-lp-1806076 Starting bb-lp-1806076 rbalint@yogi:~$ lxc shell bb-lp-1806076 mesg: ttyname failed: No such device root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base 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: language-pack-ru The following NEW packages will be installed: language-pack-ru language-pack-ru-base 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. Need to get 2310 kB of archives. After this operation, 11.8 MB of additional disk space will be used. Selecting previously unselected package language-pack-ru-base. (Reading database ... 28536 files and directories currently installed.) Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru-base (1:18.04+20180712) ... Selecting previously unselected package language-pack-ru. Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru-base (1:18.04+20180712) ... Generating locales (this might take a while)... ru_RU.UTF-8... done ru_UA.UTF-8... done Generation complete. root@bb-lp-1806076:~# env LANG=ru_RU unattended-upgrade --help | cat Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1983, in (options, args) = parser.parse_args() # type: ignore File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args stop = self._process_args(largs, rargs, values) File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args self._process_long_opt(rargs, values) File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt option.process(opt, value, values, self) File "/usr/lib/python3.6/optparse.py", line 785, in process self.action, self.dest, opt, value, values, parser) File "/usr/lib/python3.6/optparse.py", line 807, in take_action parser.print_help() File "/usr/lib/python3.6/optparse.py", line 1647, in print_help file.write(self.format_help()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 126-133: ordinal not in range(128) root@bb-lp-1806076:~# env LANG=ru_RU.UTF-8 unattended-upgrade --help | cat Usage: unattended-upgrade [options] Options: -h, --helpshow this help message and exit -d, --debug print debug messages --apt-debug make apt/libapt print verbose debug messages -v, --verbose print info messages --dry-run Simulation, download but do not install --download-only Only download, do not even try to install. --minimal-upgrade-steps Upgrade in minimal steps (and allow interrupting with SIGTERM [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.6, the problem page at https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 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/. Also seen in: * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1806076/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1860142] Re: Please update ec2-instance-connect to 1.1.12 release
** Description changed: [Impact] New upstream release of the package providing SSH access to instances; available to any AWS users. The most notable new feature is supporting Instance Metadata Service Version 2, but since the release included major rewrite which honored on Security Team's input the package is backported in full. [Test Cases] This is manually tested by Amazon: 0) Deploy an Amazon AWS instance with Instance Connect feature enabled 1) Install the ec2-instance-connect package 2) Verify that the sshd process has been restarted with the changed command-line, now including "AuthorizedKeysCommand*" options. 3) Attempt to connect to the instance using a SSH key that is known by the Instance Connect service. 4) Purge the ec2-instance-connect package 5) Configure the instance to use IMDSv2 6) Install the ec2-instance connect again and verify that is working again (steps 2 and 3) [Regression Potential] - Limited to SSH access on instances where the package gets installed. This is a brand new package for a new service provided to AWS customers. In the case of an issue, things to watch out for would be for some keys to not be usable to connect to the instance when they are expected to be, as the list of authorized keys is collated by the service to include both the usual authorized_keys contents, as well as keys provided by the Instance Connect service. + Limited to SSH access on instances where the package gets installed. This package will be installed by default for a new service called "Instance Connect" provided to AWS customers. In the case of an issue, things to watch out for would be for some keys to not be usable to connect to the instance when they are expected to be, as the list of authorized keys is collated by the service to include both the usual authorized_keys contents, as well as keys provided by the Instance Connect service. [Other Info] The source difference for the SRUs contain a lot of extra files because the source now contains almost the full upstream tarball, but the difference between the binary packages is still minimal and it maybe easier to reviewing that difference. Disco SRU is skipped because it goes EOL before the aging of the package would finish. ** Also affects: ec2-instance-connect (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: ec2-instance-connect (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ec2-instance-connect (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: ec2-instance-connect (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ec2-instance-connect (Ubuntu Disco) Status: New => Won't Fix ** Description changed: [Impact] New upstream release of the package providing SSH access to instances; available to any AWS users. The most notable new feature is supporting Instance Metadata Service Version 2, but since the release included major rewrite which honored on Security Team's input the package is backported in full. [Test Cases] This is manually tested by Amazon: 0) Deploy an Amazon AWS instance with Instance Connect feature enabled - 1) Install the ec2-instance-connect package + 1) Install the previous version of the ec2-instance-connect package 2) Verify that the sshd process has been restarted with the changed command-line, now including "AuthorizedKeysCommand*" options. 3) Attempt to connect to the instance using a SSH key that is known by the Instance Connect service. - 4) Purge the ec2-instance-connect package - 5) Configure the instance to use IMDSv2 - 6) Install the ec2-instance connect again and verify that is working again (steps 2 and 3) + 4) Upgrade to the new version of the package + 5) Attempt to connect to the instance using a SSH key that is known by the Instance Connect service. + 6) Purge the ec2-instance-connect package + 7) Configure the instance to use IMDSv2 + 8) Install the new ec2-instance-connect again and verify that is working again (steps 2 and 3) + [Regression Potential] Limited to SSH access on instances where the package gets installed. This package will be installed by default for a new service called "Instance Connect" provided to AWS customers. In the case of an issue, things to watch out for would be for some keys to not be usable to connect to the instance when they are expected to be, as the list of authorized keys is collated by the service to include both the usual authorized_keys contents, as well as keys provided by the Instance Connect service. + + The package upgrade is covered in the test case. [Other Info] The source difference for the SRUs contain a lot of extra files because the source now contains almost the full upstream tarball, but the difference between the binary packages is still minimal and it maybe easier to reviewing that difference. Disco SRU is
[Group.of.nepali.translators] [Bug 1840245] Re: Update gce-compute-image-packages to 20190801
** Also affects: gce-compute-image-packages (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: gce-compute-image-packages (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1840245 Title: Update gce-compute-image-packages to 20190801 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Committed Status in gce-compute-image-packages source package in Bionic: Fix Committed Status in gce-compute-image-packages source package in Disco: Fix Committed Status in gce-compute-image-packages source package in Eoan: Fix Released Bug description: [Impact] Compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates GCE requested updating the package to version 20191121 without releasing 20190801 to stable releases. Please consider this bug verified when LP: #1853846 is verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1840245/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1853861] Re: [SRU] Unattended-upgrades silently does not apply updates when MinimalSteps is disabled and there are autoremovable kernels
** Also affects: unattended-upgrades (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Fix Released ** Changed in: unattended-upgrades (Ubuntu Disco) Status: New => Fix Released ** Changed in: unattended-upgrades (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1853861 Title: [SRU] Unattended-upgrades silently does not apply updates when MinimalSteps is disabled and there are autoremovable kernels Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: New Status in unattended-upgrades source package in Bionic: New Status in unattended-upgrades source package in Disco: Fix Released Status in unattended-upgrades source package in Eoan: Fix Released Bug description: [Impact] * When autoremovable kernel packages are present on the system, there are updates to apply and Unattended-Upgrade::MinimalSteps is set to "false", the autoremovable kernel packages are not removed and the updates are not applied. * The root cause is u-u not cleaning the dirty cache between operations and also relying on having a cache with packages marked to be installed when applying updates in one shot. * The fix is clearing the cache between operations and marking packages before installing them in one shot. [Test Case] * Install kernel-related packages, mark them as automatically installed to make them auto-removable ones. * Downgrade a few packages to a version lower than what is present in the security pocket. * Set Unattended-Upgrade::MinimalSteps to "false": # echo 'Unattended-Upgrade::MinimalSteps "false";' > /etc/apt/apt.conf.d/51unattended-upgrades-oneshot * Run u-u: # unattended-upgrade --verbose --debug * Observe fixed versions removing the kernel packages properly and also upgrading packages. [Regression Potential] * The changes introduce marking packages to install/upgrade and clearing the cache more often. The added operations slow down u-u, but clearing the cache adds a few 100 milliseconds on typical hardware and marking upgradable packages is also in the same range. * Functional regressions are unlikely due to those changes since the fixes are present in 19.04 and later releases and the extensive autopkgtest also covers when upgrades are performed in minimal steps. [Other Info] * While this bug has a security impact by holding back installation of security updates I don't recommend releasing the fix via the security pocket because this bug occurs only when the local configuration file of u-u is changed and u-u does not hold back upgrades with UCF-managed config file conflicts. See: https://github.com/mvo5/unattended-upgrades/issues/168 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1853861/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
@frank-heimes, thank you for the testing and also for your additional comments. This fix was once accepted to bionic-proposed, while it does not have a test case in the bug description nor the description follows the SRU template: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template . Ensuring that is the job of the SRU uploader, and the first time is was skipped and I also missed that. Since the bug did not exist in 18.04 I'm marking it invalid instead of performing the SRU again. ** Changed in: systemd (Ubuntu Bionic) Status: Incomplete => Invalid ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in Ubuntu on IBM z Systems: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Invalid Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
Tested 229-4ubuntu21.22 on Xenial: ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo systemd-run /usr/bin/env [sudo] password for ubuntu: Running as unit run-r22d04a00a8304e2da719773bb14b6fb4.service. ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ journalctl -a | grep PATH Jul 02 14:31:04 ubuntu-Standard-PC-i440FX-PIIX-1996 env[2093]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l systemd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ii systemd 229-4ubuntu21.22 amd64system and service manager ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ dmesg | grep initr [0.243635] Unpacking initramfs... [0.891349] Freeing initrd memory: 54320K The fix for Xenial does not depend on snapd's environment generator, just hardcodes including /snap/bin in the PATH. ** Changed in: snapd (Ubuntu Xenial) Status: Confirmed => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Invalid Status in systemd source package in Xenial: Fix Committed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
@mvo /usr/lib/systemd/system-environment-generators/snapd-env-generator is working in Bosmic and up, but in Bionic it is not executable. Could this please be fixed? ** Changed in: snapd (Ubuntu Cosmic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot or run systemctl-daemon-reload, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1659534] Re: userdel doesn't supports extrausers
@mvo This fix raised bionic-update's shadow version above cosmic's. Do you plan fixing that or just wait for Cosmic's EOL? ** Also affects: shadow (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: shadow (Ubuntu Cosmic) Status: New => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1659534 Title: userdel doesn't supports extrausers Status in Snappy: In Progress Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Fix Released Status in shadow source package in Bionic: Fix Released Status in shadow source package in Cosmic: Confirmed Bug description: TEST CASE: - run userdel --extrausers foo on a ubuntu core system REGRESSION POTENTIAL: - low, this option will only take effect when "userdel --extrauser" is used. On an Ubuntu Core system is impossible to delete an user from the extrausers db: root@localhost:/# userdel --extrausers alice userdel: unrecognized option '--extrausers' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1824212] Re: Update gce-compute-image-packages to 20190315
*** This bug is a duplicate of bug 1831436 *** https://bugs.launchpad.net/bugs/1831436 ** This bug is no longer a duplicate of bug 1830194 Update gce-compute-image-packages to 20190521 ** This bug has been marked a duplicate of bug 1831436 Update gce-compute-image-packages to 20190522 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1824212 Title: Update gce-compute-image-packages to 20190315 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Committed Status in gce-compute-image-packages source package in Xenial: Fix Committed Status in gce-compute-image-packages source package in Bionic: Fix Committed Status in gce-compute-image-packages source package in Cosmic: Fix Committed Status in gce-compute-image-packages source package in Disco: Fix Committed Bug description: [Impact] compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. With this release we also add a new binary package to the suite - google-compute-engine-oslogin which is for a future feature of using OS Login on GCE VM instances. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1824212/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
Please add Breaks: unattended-upgrades (<< 1.1ubuntu1.18.04.11) to qemu- guest-agent for Bionic and similar breaks for other affected releases to prevent unfixed u-u from considering the upgrade the package. This allows installation of other security fixes. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory:
[Group.of.nepali.translators] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Xenial runs X on VT7 thus in default installations the postinst scripts don't break X. If this fix is scheduled for SRU, please also fix console-setup.postinst, not just keyboard-configuration.postinst. ** Also affects: kbd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: console-setup (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: console-setup (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: New Status in xorg-server source package in Xenial: New Status in console-setup source package in Bionic: Fix Committed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Committed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Committed Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: In Progress Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ On Xenial X runs on VT7 thus the graphical environment is not affected in the default configuration, but the keyboard-configuration postinst maintaner script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode to observe the change: $ sudo kbd_mode -s -C /dev/tty1 $ sudo kbd_mode -C /dev/tty1 The keyboard is in raw (scancode) mode * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same (on Xenial check VT1: sudo kbd_mode -C /dev/tty1): $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1599646] Re: E-mail report contains repeated "Reading database ... NN%" lines
This bug has been fixed in 1.1ubuntu1.18.04.9. ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1599646 Title: E-mail report contains repeated "Reading database ... NN%" lines Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in apt package in Debian: New Bug description: [Impact] * Unattended-upgrades sends the following repeating dpkg progress lines with almost no informational value in the email report: ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 60486 files and directories currently installed.) ... * This makes the report email too verbose and makes harder to spot real problems. [Test Case] * Run package autopkgtest and observe no such lines in the echoed email in upgrade-all-security and upgrade-between-snapshots tests. [Regression Potential] * The fix filters dpkg's output only and in the worst case other lines could be missing or u-u could crash. Since the applied hard- coded regex pattern is fairly simple and we observed no crashes in the tests those regressions are unlikey to occur. [Originial Bug Text] This concerns unattended-upgrades 0.90 in Xenial. Here is an excerpt from an e-mail report sent out by u-u after the upgrade process is completed: Package installation log: Log started: 2016-07-06 17:24:21 Preconfiguring packages ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 314949 files and directories currently installed.) Preparing to unpack .../tzdata_2016f-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2016f-0ubuntu0.16.04) over (2016d-0ubuntu0.16.04) ... Preparing to unpack .../libgimp2.0_2.8.16-1ubuntu1.1_i386.deb ... All but the last "Reading database ..." line should be elided from the message. As a matter of fact, those lines do not appear in messages mailed out from current Trusty systems (u-u version 0.82.1ubuntu2.4), so this appears to be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1599646/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1615381] Re: apt-get autoremove may remove current kernel
@mathew-hodson apt still does that. ** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Changed in: apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released 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/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1820888] Re: unattended-upgrades may hold back upgrades due to comparing package versions by their string representation
Tested with 1.5ubuntu3.18.10.3 on Cosmic: https://launchpadlibrarian.net/416582074/buildlog_ubuntu-cosmic-amd64.unattended-upgrades_1.5ubuntu3.18.10.3_BUILDING.txt.gz : ... OK Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 ... OK ... ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic ** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1820888 Title: unattended-upgrades may hold back upgrades due to comparing package versions by their string representation Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the fix u-u could not upgrade particular packages from -security. It could be observed in Cosmic with systemd security updates failing to install partly due to 239-7ubuntu10.10 being smaller than 239-7ubuntu10.8 when comparing them as strings: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: ... Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 ... With the unfixed version the test case fails here because u-u tries to upgrade test-package to version 12.0 because it does not find version 2.0 smaller. [Regression Potential] * The change is very small and isolated, but fixing it revealed the issue fixed in LP: #1821101. Since the found issue's fix introduces fallbacks when apt's resolver can't find a the solution it is unlikely that other failures are triggered by the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1820888/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1821101] Re: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade
Tested with 1.5ubuntu3.18.10.3 on Cosmic: https://launchpadlibrarian.net/416582074/buildlog_ubuntu-cosmic-amd64.unattended-upgrades_1.5ubuntu3.18.10.3_BUILDING.txt.gz : ... OK Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to marking test2-package, then adjusting changes DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:falling back to marking test3-package, then adjusting changes WARNING:root:package test3-package upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) DEBUG:root:falling back to adjusting all packages DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-old-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 WARNING:root:package z-package upgradable but fails to be marked for upgrade () . -- Ran 1 test in 0.025s OK ... ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic ** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => In Progress ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1821101 Title: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the introduced fallbacks u-u could not upgrade particular package sets from -security. It could be observed in Cosmic with systemd security updates failing to install in: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to marking test2-package, then adjusting changes DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:falling back to marking test3-package, then adjusting changes WARNING:root:package test3-package upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) DEBUG:root:falling back to adjusting all packages DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-old-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 WARNING:root:package z-package upgradable but fails to be marked for upgrade () . -- Ran 1 test in 0.039s OK [Regression Potential] * When failing to mark a package to upgrade/install from the allowed origin holding the highest version the first fallback resets all already adjusted candidates to the highest available version irrespective to the origin of this version being allowed or not. This itself is not a risky operation and sanity checks later ensure that no package would be installed from
[Group.of.nepali.translators] [Bug 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove
** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu Cosmic) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1795696 Title: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended- upgrade@1991:main:do_auto_remove Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: New Status in unattended-upgrades source package in Bionic: Confirmed Status in unattended-upgrades source package in Cosmic: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e 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/1795696/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1602536] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
*** This bug is a duplicate of bug 1260041 ***
https://bugs.launchpad.net/bugs/1260041
** This bug has been marked a duplicate of bug 1260041
Unattended-Upgrades crashes with a dpkg error
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1818150] Re: Hibinit-agent configures GRUB referring to root partition as resume=/dev/root
Tested on Cosmic, Bionic and Xenial with the latest version in -proposed: ubuntu@ip-172-31-11-18:~$ dpkg -l ec2-hibinit-agent | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-=-==--= ii ec2-hibinit-agent 1.0.0-0ubuntu4~18.10.0 all Amazon EC2 hibernation agent ubuntu@ip-172-31-11-18:~$ grep -m 1 root= /boot/grub/grub.cfg linux /boot/vmlinuz-4.18.0-1011-aws root=PARTUUID=71d081c0-01 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 no_console_suspend=1 resume_offset=245760 resume=PARTUUID=71d081c0-01 ubuntu@ip-172-31-7-41:~$ dpkg -l ec2-hibinit-agent | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-=-==--= ii ec2-hibinit-agent 1.0.0-0ubuntu4~18.04.0 all Amazon EC2 hibernation agent ubuntu@ip-172-31-7-41:~$ grep -m 1 root= /boot/grub/grub.cfg linux /boot/vmlinuz-4.15.0-1033-aws root=UUID=b5361850-7320-445b-b1c9-a8b294830484 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 no_console_suspend=1 resume_offset=235520 resume=/dev/xvda1 ubuntu@ip-172-31-12-48:~$ dpkg -l ec2-hibinit-agent | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-=-==--= ii ec2-hibinit-agent 1.0.0-0ubuntu4~16.04.0 all Amazon EC2 hibernation agent ubuntu@ip-172-31-12-48:~$ grep -m 1 root= /boot/grub/grub.cfg linux /boot/vmlinuz-4.4.0-1077-aws root=UUID=7d8f7a6c-6fdc-4cfe-a376-95b51a59f117 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 nvme_core.io_timeout=4294967295 no_console_suspend=1 resume_offset=346112 resume=/dev/xvda1 ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-xenial ** Changed in: ec2-hibinit-agent (Ubuntu Trusty) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1818150 Title: Hibinit-agent configures GRUB referring to root partition as resume=/dev/root Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in ec2-hibinit-agent source package in Trusty: Won't Fix Status in ec2-hibinit-agent source package in Xenial: Fix Committed Status in ec2-hibinit-agent source package in Bionic: Fix Committed Status in ec2-hibinit-agent source package in Cosmic: Fix Committed Bug description: [Impact] * The kernel can't find /dev/root when booting initramfsless thus can't resume from hibernation * The fix sets resume=... to the same identifier passed as root=... on the kernel command when the swap file is found to be on /dev/root. [Test Case] * (Install and) start hibinit-agent on an EC2 instance supporting hibernation, then when it started successfully verify the grub configuration: $ grep -m 1 root= /boot/grub/grub.cfg linux /boot/vmlinuz-4.18.0-1008-aws root=PARTUUID=6b4ea835-01 ro console=tty1 console=ttyS0 nvme.io_timeout=4294967295 no_console_suspend=1 resume_offset=438272 resume=PARTUUID=6b4ea835-01 resume=... must not refer to /dev/root with the default configuration, but to a block device known to the kernel without using initramfs. [Regression Potential] * Hibinit-agent may parse the grub configuration file incorrectly and set a wrong partition to resume from. Since the fix is quite small and the number of variants of grub configurations is also small this regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1818150/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1812166] Re: [SRU] Please accept ec2-hibinit-agent to supported releases
Trusty will not include the package. ** Changed in: ec2-hibinit-agent (Ubuntu Trusty) Status: Fix Committed => Won't Fix ** Tags removed: verification-needed-trusty ** Description changed: [Impact] The package is new to the releases and sets up EC2 on demand instances to hibernate on an ACPI sleep event. [Test Case] 1. Please perform piuparts-like tests with the package and make sure that ec2-hibinit-agent service is started. On EC2 on demand instances that were configured to allow hibernation the hibinit-agent service prepares the system for enabling hibernation. On non EC2 on demand instances and on EC2 on demand instances where hibernation is not configures when launching the instance the service starts without error but does not prepare the system for being able to hibernate. Note, that the resource on the URL enabling hibernation may be missing or may hold true or false: $ curl http://169.254.169.254/latest/meta-data/hibernation/configured http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;> + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;> http://www.w3.org/1999/xhtml; xml:lang="en" lang="en"> - - 404 - Not Found - - - 404 - Not Found - + + 404 - Not Found + + + 404 - Not Found + $ curl http://169.254.169.254/latest/meta-data/hibernation/configured false curl http://169.254.169.254/latest/meta-data/hibernation/configured true + Negative cases and proper start are tested in LP: #1817926. 2. Start a long running process on the instance, like top in screen. 3. Hibernate, then after it finished start the instance on EC2 console 4. Log in to the instance and observe top still running in screen. 5. Hibernate, then after it finished start the instance on EC2 console 6. Log in to the instance and observe top still running in screen. (This second cycle ensures that hibernation works more than once.) [Regression Potential] Since the package is new it may not cause regressions by being broken. The package sets up a swap file on / reserving the size of the memory from the root partition. There is check in the service to ensure that there is enough space but the space left may not be enough for the proper operation of the system later. Users a warned on EC2 console to allocate a big enough root partition for the instance when instance hibernation is enabled. For Trusty in my tests the generic default 3.x kernel could not resume from hibernation, but the latest 4.4.x-based linux-aws kernel could. -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1812166 Title: [SRU] Please accept ec2-hibinit-agent to supported releases Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in ec2-hibinit-agent source package in Trusty: Won't Fix Status in ec2-hibinit-agent source package in Xenial: Fix Committed Status in ec2-hibinit-agent source package in Bionic: Fix Committed Status in ec2-hibinit-agent source package in Cosmic: Fix Committed Bug description: [Impact] The package is new to the releases and sets up EC2 on demand instances to hibernate on an ACPI sleep event. [Test Case] 1. Please perform piuparts-like tests with the package and make sure that ec2-hibinit-agent service is started. On EC2 on demand instances that were configured to allow hibernation the hibinit-agent service prepares the system for enabling hibernation. On non EC2 on demand instances and on EC2 on demand instances where hibernation is not configures when launching the instance the service starts without error but does not prepare the system for being able to hibernate. Note, that the resource on the URL enabling hibernation may be missing or may hold true or false: $ curl http://169.254.169.254/latest/meta-data/hibernation/configured http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;> http://www.w3.org/1999/xhtml; xml:lang="en" lang="en"> 404 - Not Found 404 - Not Found $ curl http://169.254.169.254/latest/meta-data/hibernation/configured false curl http://169.254.169.254/latest/meta-data/hibernation/configured true Negative cases and proper start are tested in LP: #1817926. 2. Start a long running process on the instance, like top in screen. 3. Hibernate, then after it finished start the instance on EC2 console 4. Log in to the instance and observe top still running in screen. 5. Hibernate, then after it finished start the instance on EC2 console 6. Log in to the instance and observe top still running in screen. (This second cycle ensures that hibernation works more than once.) [Regression Potential] Since the package is new it may not cause regressions by being broken. The
[Group.of.nepali.translators] [Bug 1817926] Re: Hibinit-agent starts even when instance hibernation is disabled
Verified with 1.0.0-0ubuntu4~16.04.0 on Xenial: + sudo apt-get install -qq ec2-hibinit-agent debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, <> line 1.) debconf: falling back to frontend: Readline Selecting previously unselected package ec2-hibinit-agent. (Reading database ... 38529 files and directories currently installed.) Preparing to unpack .../ec2-hibinit-agent_1.0.0-0ubuntu4~16.04.0_all.deb ... Unpacking ec2-hibinit-agent (1.0.0-0ubuntu4~16.04.0) ... Setting up ec2-hibinit-agent (1.0.0-0ubuntu4~16.04.0) ... + sleep 3 + curl http://169.254.169.254/latest/meta-data/hibernation/configured http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;> http://www.w3.org/1999/xhtml; xml:lang="en" lang="en"> 404 - Not Found 404 - Not Found + service hibinit-agent status ● hibinit-agent.service - EC2 instance hibernation setup agent Loaded: loaded (/lib/systemd/system/hibinit-agent.service; enabled; vendor preset: enabled) Active: inactive (dead) since Tue 2019-03-12 11:53:46 UTC; 3s ago Docs: file:/usr/share/doc/ec2-hibinit-agent/README Mar 12 11:53:46 ip-172-31-0-169 systemd[1]: Starting EC2 instance hibernation setup agent... Mar 12 11:53:46 ip-172-31-0-169 /hibinit-agent[5933]: Instance Launch has not enabled Hibernation Configured Flag. h ibinit-agent exiting!! Mar 12 11:53:46 ip-172-31-0-169 hibinit-agent[5933]: Instance Launch has not enabled Hibernation Configured Flag. hi binit-agent exiting!! Mar 12 11:53:46 ip-172-31-0-169 systemd[1]: Started EC2 instance hibernation setup agent. + true + sudo apt-get install -qq screen + sudo apt-get install -qq ec2-hibinit-agent + sleep 3 + curl http://169.254.169.254/latest/meta-data/hibernation/configured http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;> http://www.w3.org/1999/xhtml; xml:lang="en" lang="en"> 404 - Not Found 404 - Not Found + service hibinit-agent status ● hibinit-agent.service - EC2 instance hibernation setup agent Loaded: loaded (/lib/systemd/system/hibinit-agent.service; enabled; vendor preset: enabled) Active: inactive (dead) since Tue 2019-03-12 11:39:16 UTC; 15min ago Docs: file:/usr/share/doc/ec2-hibinit-agent/README Mar 12 11:39:16 ip-172-31-11-52 systemd[1]: Starting EC2 instance hibernation setup agent... Mar 12 11:39:16 ip-172-31-11-52 /hibinit-agent[1730]: Instance Launch has not enabled Hibernation Configured Flag. h Mar 12 11:39:16 ip-172-31-11-52 hibinit-agent[1730]: Instance Launch has not enabled Hibernation Configured Flag. hi Mar 12 11:39:16 ip-172-31-11-52 systemd[1]: Started EC2 instance hibernation setup agent. + true + sudo apt-get install -qq screen + screen -d -m top ubuntu@ip-172-31-11-52:~$ dpkg -l ec2-hibinit-agent | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-=-==--= ii ec2-hibinit-agent 1.0.0-0ubuntu4~16.04.0 all Amazon EC2 hibernation agent + sudo apt-get install -qq ec2-hibinit-agent + sleep 3 + curl http://169.254.169.254/latest/meta-data/hibernation/configured true+ service hibinit-agent status ● hibinit-agent.service - EC2 instance hibernation setup agent Loaded: loaded (/lib/systemd/system/hibinit-agent.service; enabled; vendor preset: enabled) Active: inactive (dead) since Tue 2019-03-12 11:39:40 UTC; 15min ago Docs: file:/usr/share/doc/ec2-hibinit-agent/README Main PID: 1727 (code=exited, status=0/SUCCESS) Mar 12 11:39:40 ip-172-31-12-48 hibinit-agent[1723]: Allocating 4194304000 bytes in /swap-hibinit Mar 12 11:39:40 ip-172-31-12-48 hibinit-agent[1723]: Swap pre-heating is skipped, the swap blocks won't be touched Mar 12 11:39:40 ip-172-31-12-48 hibinit-agent[1723]: Running: mkswap /swap-hibinit Mar 12 11:39:40 ip-172-31-12-48 hibinit-agent[1723]: Running: swapon /swap-hibinit Mar 12 11:39:40 ip-172-31-12-48 hibinit-agent[1723]: Updating the kernel offset for the swapfile: /swap-hibinit Mar 12 11:39:40 ip-172-31-12-48 hibinit-agent[1723]: Updating GRUB to use the device /dev/xvda1 with offset 346112 Mar 12 11:39:40 ip-172-31-12-48 hibinit-agent[1723]: GRUB configuration is updated Mar 12 11:39:40 ip-172-31-12-48 hibinit-agent[1723]: Setting swap device to 51713 with offset 346112 Mar 12 11:39:40 ip-172-31-12-48 hibinit-agent[1723]: Done updating the swap offset. Turning swapoff Mar 12 11:39:40 ip-172-31-12-48 hibinit-agent[1723]: Running: swapoff /swap-hibinit + true + sudo apt-get install -qq screen + screen -d -m top ubuntu@ip-172-31-12-48:~$ dpkg -l ec2-hibinit-agent | cat Desired=Unknown/Install/Remove/Purge/Hold |
[Group.of.nepali.translators] [Bug 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not
The fix is incomplete in Xenail the same way as it is incomplete in Bionic.
Tested version: 1.1ubuntu1.18.04.7~16.04.1
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-failed verification-failed-xenial
** Changed in: unattended-upgrades (Ubuntu Bionic)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
Confirmed
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/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist
** Changed in: unattended-upgrades (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs 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: Confirmed 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/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1753943] Re: [SRU] Please accept rax-nova-agent to supported releases
** Changed in: rax-nova-agent (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: rax-nova-agent (Ubuntu Artful) Status: Fix Committed => Won't Fix ** Changed in: rax-nova-agent (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1753943 Title: [SRU] Please accept rax-nova-agent to supported releases Status in rax-nova-agent package in Ubuntu: Fix Released Status in rax-nova-agent source package in Xenial: Fix Released Status in rax-nova-agent source package in Artful: Won't Fix Bug description: [Impact] * Instances on Rackspace currently use an agent to configure the instance which is not in the Ubuntu archive. The rax-nova-agent to be included in stable releases is a replacement for the agent not included in the archive. [Test Case] * 1. Generate Ubuntu image including rax-nova-agent and boot it in Rackspace's network. 2. Perform tests on the image CPC Team find necessary. * 1. Boot an image containing the agent to be replaced in Rackspace's network. The agent to be replaced is packaged as rax-openstack-guest-agents. 2. Upgrade to rax-nova-agent. 3. Perform tests on the image CPC Team find necessary. [Regression Potential] * Instances containing rax-nova-agent may fail to operate properly in Rackspace's network including potentially failing to boot, apply user's configuration or mis-configuring the system. * The potential regressions may arise upon booting from an image containing rax-nova-agent pre-installed or on images upgrading from rax-openstack-guest-agents. [Other Info] * - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rax-nova-agent/+bug/1753943/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Bug description: Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] root@uu-systemd-onshutdown:~# reboot Session terminated, terminating shell...Terminated root@uu-systemd- rbalint@yogi:~$ rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# tail /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ... Setting up libsystemd0:amd64 (237-3ubuntu10.6) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up systemd (237-3ubuntu10.6) ... Failed to try-restart systemd-networkd.service: Transaction is destructive. See system logs and 'systemctl status systemd-networkd.service' for details. Failed to try-restart systemd-resolved.service: Transaction is destructive. See system logs and 'systemctl status systemd-resolved.service' for details. root@uu-systemd-onshutdown:~# ps -ef | cat UIDPID PPID C STIME TTY TIME CMD root 1 0 0 15:34 ?00:00:00 /lib/systemd/systemd --system --deserialize 22 root53 1 0 15:34 ?00:00:00 /lib/systemd/systemd-journald systemd+ 153 1 0 15:34 ?00:00:00
[Group.of.nepali.translators] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
*** This bug is a duplicate of bug 1778219 *** https://bugs.launchpad.net/bugs/1778219 Since this issue is marked as invalid for linux i'm setting it as a duplicate of the u-u bug where SRU-ing the fix is tracked. ** This bug has been marked a duplicate of bug 1778219 unattended-upgrades hangs on shutdown, leaves system in a broken state -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in unattended-upgrades source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in unattended-upgrades source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in unattended-upgrades source package in Cosmic: Fix Released Status in linux source package in Disco: Invalid Status in unattended-upgrades source package in Disco: Fix Released Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1615381] Re: apt-get autoremove may remove current kernel
** Changed in: unattended-upgrades (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs 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: Confirmed 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/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1771894] Re: /usr/bin/update-manager:TypeError::on_button_install_clicked:start_install:_start_pane:start:unwind_generator
Verified with 1:16.04.15 on Xenial. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial ** Changed in: update-manager (Ubuntu) Status: New => Fix Released ** Changed in: update-manager (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1771894 Title: /usr/bin/update- manager:TypeError::on_button_install_clicked:start_install:_start_pane:start:unwind_generator Status in update-manager package in Ubuntu: Invalid Status in update-manager source package in Xenial: Fix Committed Bug description: [Impact] The backend API change made update-manager crash when the updated incompatible backend was loaded to the not updated running update- manager process. The issue causes crashes upon update-manager updates harming the upgrade experience for users. The fix avoids lazy loading of the backend modules but still honors the backend selection options. [Test Case] 1. Start with a fully upgraded system and downgrade a few packages to let u-m upgrade them and also downgrade update-manager to 1:16.04.12 or earlier: $ sudo eatmydata apt install -y --allow-downgrades gnome-software=3.28.1-0ubuntu4 gnome-software-common=3.28.1-0ubuntu4 $ sudo apt install update-manager=1:16.04.12 update-manager-core=1:16.04.12 python3-update-manager=1:16.04.12 2. Start u-m with: $ update-manager --no-update 3. Upgrade update-manager to a still not fixed version to observe the crash: $ sudo apt install update-manager=1:16.04.14 update-manager-core=1:16.04.14 python3-update-manager=1:16.04.14 ... or to the fixed version to a see the crash not happening in step 4: $ sudo apt install update-manager=1:16.04.15 update-manager- core=1:16.04.15 python3-update-manager=1:16.04.15 4. Press "Install Now" on u-m GUI. The fixed u-m will successfully perform the installation, the unfixed one will fail with: TypeError: commit() missing 1 required positional argument: 'pkgs_remove' [Regression Potential] The change to the backend API could cause u-m not able to remove unused kernels, but in my testing this feature still worked. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/310b9890e139c17b61faeee8f50078909283794e 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/update-manager/+bug/1771894/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1798706] Re: Incomplete linking with boost_regex
Bionic and later releases don't need the boost regex library thus this bug does not affect the latest releases. ** Changed in: gce-compute-image-packages (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1798706 Title: Incomplete linking with boost_regex Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Bug description: SRU Justification = [Impact] oslogin fails on Xenial and Trusty. In auth.log we see: Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: cannot open shared object file: No such file or directory Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: pam_oslogin_login.so Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: cannot open shared object file: No such file or directory Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: pam_oslogin_admin.so The error message is a bit deceptive - PAM tries to load the module from the correct location, fails, and then tries the other location where it is missing. It then reports the missing error rather than the real error. symlink the module into both paths leads to a much more useful error message: Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: undefined symbol: _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE Oct 18 06:45:12 dja-202158 sshd[16554]: PAM adding faulty module: pam_oslogin_login.so Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: undefined symbol: _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE [Test case] - set up GCE VM - turn on oslogin - attempt to log in [Fix] debian/patches/0002-Set-LDFLAGS-at-the-end-of-the-c-command-line-right-b.patch re-orders the link flags to link boost_regex for oslogin. However, this didn't change the flags for PAM module linking. So fix that too. [Regression Potential] - fixes a regression - limited to oslogin, and how it is linked. [Other Notes] We still see a scary list of warnings when building, but they don't seem to have an impact on the common path: dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail13put_mem_blockEPv used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail14verify_optionsEjNS_15regex_constants12_match_flagsE used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZNK5boost9re_detail31cpp_regex_traits_implementationIcE17transform_primaryEPKcS4_ used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost13match_resultsIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISB_12maybe_assignERKSF_ used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost11basic_regexIcNS_12regex_traitsIcNS_16cpp_regex_traitsIcE9do_assignEPKcS7_j used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail19raise_runtime_errorERKSt13runtime_error used by
[Group.of.nepali.translators] [Bug 1693948] Re: useless diagnostics in dpkg.log from journalctl due to ellipses
Fixed in https://salsa.debian.org/debian/init-system- helpers/commit/5836b307724f8731b47d3d4d064ada1833182705 thus the package is fixed in version debian/1.49 and later. ** Also affects: init-system-helpers (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: init-system-helpers (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: init-system-helpers (Ubuntu Xenial) Status: New => Confirmed ** Changed in: init-system-helpers (Ubuntu) Status: Confirmed => Fix Released ** Changed in: init-system-helpers (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: init-system-helpers (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1693948 Title: useless diagnostics in dpkg.log from journalctl due to ellipses Status in init-system-helpers package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: Confirmed Status in init-system-helpers source package in Bionic: Fix Released Bug description: Many of the apport hooks try to include some information about why a service didn't start correctly. One recent report included the following: May 26 18:39:19 ux305ua-linux systemd[1]: Starting OpenBSD Secure Shell serv May 26 18:39:19 ux305ua-linux sshd[2500]: /etc/ssh/sshd_config line 64: miss May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Main process exited, ...a[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;31mFailed to start OpenBSD Secure She[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Unit entered failed s[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Failed with result 'e[0m Hint: Some lines were ellipsized, use -l to show in full. The actual error information is this: /etc/ssh/sshd_config line 64: miss and Failed with result 'e This is very nearly useless. We should include the -l parameter as suggested so that we stand a chance of seeing an error that doesn't occur in the first twenty characters of program output. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1693948/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1787508] Re: (non-syslog) log file entries are missing the newline when loglinelen is set to a non-positive number (sudo version 1.8.14 - 1.8.16)
Fixed in latest Ubuntu releases, let release managers decide if it can go into Xenial. Thanks for the offer BTW! :-) ** Also affects: sudo (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: sudo (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1787508 Title: (non-syslog) log file entries are missing the newline when loglinelen is set to a non-positive number (sudo version 1.8.14 - 1.8.16) Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: New Bug description: This is basically a request to have an upstream patch applied to the current Ubuntu Xenial package. Changes made in sudo 1.8.14 introduced this bug. It was fixed upstream in 1.8.17 https://www.sudo.ws/devel.html#1.8.17b1 https://bugzilla.sudo.ws/show_bug.cgi?id=742 Ubuntu release: Ubuntu 16.04.5 LTS Package version: sudo/xenial-updates,now 1.8.16-0ubuntu1.5 amd64 I am willing to help fix this (literally a one-liner in the patch), I just don't know the proper channels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1787508/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1753779] Re: [SRU] Please accept pyxs to supported releases
** Changed in: pyxs (Ubuntu Artful) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1753779 Title: [SRU] Please accept pyxs to supported releases Status in pyxs package in Ubuntu: Fix Released Status in pyxs source package in Xenial: Fix Committed Status in pyxs source package in Artful: Won't Fix Bug description: [Impact] * Pyxs needs to be back-ported since it is a dependency of rax-nova- agent that package needs to be backported, too. [Test Case] * Install the package. [Regression Potential] * This is a leaf package and have no relations to existing packages in the release. [Other Info] * - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyxs/+bug/1753779/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1774120] Re: ebtables cannot be upgraded from 2.0.10.4-3.5ubuntu2 to 2.0.10.4-3.5ubuntu2.18.04.1 on WSL
@ddstreet I uploaded a backported patch to Bionic to make it to the .1 point release. ** Changed in: ebtables (Ubuntu Trusty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1774120 Title: ebtables cannot be upgraded from 2.0.10.4-3.5ubuntu2 to 2.0.10.4-3.5ubuntu2.18.04.1 on WSL Status in ebtables package in Ubuntu: Fix Released Status in ebtables source package in Trusty: Won't Fix Status in ebtables source package in Xenial: In Progress Status in ebtables source package in Artful: In Progress Status in ebtables source package in Bionic: In Progress Status in ebtables source package in Cosmic: Fix Released Bug description: [impact] ebtables cannot be upgraded on Ubuntu 18.04 for WSL. [test case] on a WSL installation that already has ebtables installed (most installations do), try to upgrade the package with apt or dpkg; its prerm script will fail, and prevent the upgrade. [regression potential] the ebtables init script is changed to never return an error code when called as 'stop', so anything that depends on the script returning an error code when 'stop' fails will no longer work correctly. However, nothing appears to use the 'stop' return value, besides the package's prerm script, which is what is causing the upgrade failure. Additionally, the prerm script is updated to ignore 'failed-upgrade' failures, to allow upgrading over the previous version(s). Finally note that the rpm-specific ebtables.spec file that is included in the package specifically ignores the 'stop' return value, i.e.: /sbin/service ebtables stop &>/dev/null || : [other info] note that ebtables is effectively dead upstream, so it's extremely unlikely there will be many more package updates/srus, except to fix minor bugs such as this. [original description] ebtables cannot be upgraded on Ubuntu 18.04 for WSL. apt-get upgrade fails with the following error: Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages will be upgraded: ebtables 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/79.9 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 47381 files and directories currently installed.) Preparing to unpack .../ebtables_2.0.10.4-3.5ubuntu2.18.04.1_amd64.deb ... invoke-rc.d: could not determine current runlevel [31m*[39;49m Error: insufficient privileges to access the ebtables rulesets. invoke-rc.d: initscript ebtables, action "stop" failed. dpkg: warning: old ebtables package pre-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... invoke-rc.d: could not determine current runlevel [31m*[39;49m Error: insufficient privileges to access the ebtables rulesets. invoke-rc.d: initscript ebtables, action "stop" failed. dpkg: error processing archive /var/cache/apt/archives/ebtables_2.0.10.4-3.5ubuntu2.18.04.1_amd64.deb (--unpack): new ebtables package pre-removal script subprocess returned error exit status 1 update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults invoke-rc.d: could not determine current runlevel Errors were encountered while processing: /var/cache/apt/archives/ebtables_2.0.10.4-3.5ubuntu2.18.04.1_amd64.deb See https://github.com/Microsoft/WSL/issues/1761 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1774120/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value
@xnox markig procps as wontfix since the kernel fix seems to be sufficient. ** Changed in: procps (Ubuntu) Status: New => Won't Fix ** Changed in: procps (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: procps (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1717224 Title: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value Status in Ubuntu on IBM z Systems: Fix Released Status in kvm package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Status in procps package in Ubuntu: Won't Fix Status in linux source package in Xenial: Fix Released Status in procps source package in Xenial: Won't Fix Status in linux source package in Artful: Fix Released Status in procps source package in Artful: Won't Fix Bug description: Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with the following error: root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038 error: Failed to start domain zs93kag70038 error: internal error: process exited while connecting to monitor: 2017-07-26T01:48:26.352534Z qemu-kvm: -drive file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native: Could not open backing file: Could not set AIO state: Inappropriate ioctl for device The previous 17 guests started fine: root@zm93k8# virsh start zs93kag70020 Domain zs93kag70020 started root@zm93k8# virsh start zs93kag70021 Domain zs93kag70021 started . . root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036 Domain zs93kag70036 started We ended up fixing the issue by adding the following line to /etc/sysctl.conf : fs.aio-max-nr = 4194304 ... then, reload the sysctl config file: root@zm93k8:/etc# sysctl -p /etc/sysctl.conf fs.aio-max-nr = 4194304 Now, we're able to start more guests... root@zm93k8:/etc# virsh start zs93kag70036 Domain zs93kag70036 started The default value was originally set to 65535: root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr 65536 Note, we chose the 4194304 value, because this is what our KVM on System Z hypervisor ships as its default value. Eg. on our zKVM system: [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr 4194304 ubuntu@zm93k8:/etc$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial ubuntu@zm93k8:/etc$ ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version Version: 1:2.5+dfsg-5ubuntu10.8 Is something already documented for Ubuntu KVM users warning them about the low default value, and some guidance as to how to select an appropriate value? Also, would you consider increasing the default aio-max-nr value to something much higher, to accommodate significantly more virtual guests? Thanks! ---uname output--- ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux Machine Type = z14 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- See Problem Description. The problem was happening a week ago, so this may not reflect that activity. This file was collected on Aug 7, one week after we were hitting the problem. If I need to reproduce the problem and get fresh data, please let me know. /var/log/messages doesn't exist on this system, so I provided syslog output instead. All data have been collected too late after the problem was observed over a week ago. If you need me to reproduce the problem and get new data, please let me know. That's not a problem. Also, we would have to make special arrangements for login access to these systems. I'm happy to run traces and data collection for you as needed. If that's not sufficient, then we'll explore log in access for you. Thanks... - Scott G. I was able to successfully recreate the problem and captured / attached new debug docs. Recreate procedure: # Started out with no virtual guests running. ubuntu@zm93k8:/home/scottg$ virsh list IdName State # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in /etc/sysctl.conf ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf fs.aio-max-nr = 65536 ## sysctl -a shows: fs.aio-max-nr = 4194304 ## Reload sysctl. ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf fs.aio-max-nr = 65536 ubuntu@zm93k8:~$ ubuntu@zm93k8:~$ sudo sysctl -a |grep
[Group.of.nepali.translators] [Bug 1739418] Re: Please build minimized images in a 1GiB image
We discussed the change with Steve Langasek again and agreed that the initial image should not be changed and the size of the final images produced by livecd-rootfs should be monitored. The change already made in trunk will be reverted soon. ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: livecd-rootfs (Ubuntu) Status: Fix Released => Won't Fix ** Changed in: livecd-rootfs (Ubuntu Xenial) Assignee: Balint Reczey (rbalint) => (unassigned) ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1739418 Title: Please build minimized images in a 1GiB image Status in livecd-rootfs package in Ubuntu: Won't Fix Status in livecd-rootfs source package in Xenial: Won't Fix Bug description: [Impact] * Without the fix the initial size of the image is ~2.2GiB, even for minimized images. Changing it to 1GiB allows detecting an increase in packages' installed installed size in case they would exceed this smaller limit. * Minimized images are generated for Xenial, too, and having this limit in effect may help keeping images small. [Test Case] * Generate all minimized an non-minimized images to see that all the builds still succeed. [Regression Potential] * Since partitions images are expanded to pre-defined sizes at the end of image generation this change should not change the resulting image sizes where having free space is needed at run-time. * The change may break building images, hence the tests in the Test Cases section. * The change is tested extensively in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1739418/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1721261] Re: [SRU] Release minimized image related changes to Xenial
** Changed in: livecd-rootfs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1721261 Title: [SRU] Release minimized image related changes to Xenial Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Bug description: [Impact] * Ability to generate minimized images is a new feature of livecd-rootfs. Minimized images have smaller footprint on disk, may not use initramfs to boot and may have smaller RAM footprint as well. * Using minimal images can save bandwidth and system resources and we would like to make those improvements available for Xenial users. [Test Case] * A new autopkgtest (minimized) was added to test building minimized images. The test logs show the generated image sizes for ubuntu-cpc images with and without minimization and the minimized images have to be smaller. [Regression Potential] * The changes should not affect images which are not minimized but the minimized images may not boot on some systems. For example the Linux kernel does not boot in a Vagrant VM without initramfs, but the minimized Vagrant image does not include initramfs. * In case the effect of changes are not limited to the minimized image they may make packages missing from regular images and/or may make the regular images unbootable. [Other Info] * The current patch works around the 'minimized' autopkgtest failure on ppc64el which affects Artful and can be observed when the Linux kernel package does not depend on initramfs-tools (LP: #1700972) thus the minimized images don't include initramfs support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1721261/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1732681] Re: Switching to to xz -0 from pxz increases compressed raspi2 image size
Since the change passing -0 to xz never entered Xenial on its own this bug does not have to be tracked for Xenial. ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1732681 Title: Switching to to xz -0 from pxz increases compressed raspi2 image size Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Invalid Bug description: [Impact] * Switching from xz -0 to xz (-6) for compression raspi2 image. [Test Case] * To test the change install updated livecd-rootfs on armhf and create images setting the following environment variables: ARCH=armhf SUBARCH=raspi2 PROJECT=ubuntu-cpc. Notice that the xz-compressed rapi2 image is still created with xz's default (-6) compression. [Regression Potential] * In case of this change causes regression it would manifest itself as failing build for raspi2, failing build for ubuntu-cpc images or using other compression for raspi2 images than xz -6. [Original Bug Report Text] Switching from pxz to xz -0 in LP: #1701132 made the downloadable raspi2 image bigger, ~360MB which is a notable size increase from the original ~250MB while decreasing time the needed for compressing it. The bigger compressed image is currently downloadable for Artful: http://cdimage.ubuntu.com/ubuntu/releases/17.10/release/ Zesty's image is 232MB: http://cdimage.ubuntu.com/ubuntu/releases/17.04/release/ To find the proper trade-off I ran compression tests on Xenial (xz ignores -T4 there): https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1701132/comments/5 : ... rbalint@xenial-test:~/Downloads$ ls -al ubuntu-16.04.3-preinstalled-server-armhf+raspi2.img.p.xz -rw-rw-r-- 1 rbalint rbalint 254621780 Nov 16 00:03 ubuntu-16.04.3-preinstalled-server-armhf+raspi2.img.p.xz ... -0 -T4 81.56 73.64 1.46 4820 29.27 25.82 0.09 2252 329984 -1 -T4 103.68 95.14 1.67 10800 24.41 22.86 0.12 3180 298060 -2 -T4 134.05 126.22 1.76 18480 22.06 21.65 0.13 4232 286276 -3 -T4 170.57 162.72 1.72 33812 21.62 20.94 0.12 6188 275036 -4 -T4 322.15 317.83 2.10 50284 21.55 21.05 0.07 6136 258684 -5 -T4 407.15 399.93 1.92 97656 21.85 20.50 0.12 10412 247320 -6 -T4 478.64 473.32 1.95 97660 21.92 20.34 0.09 10348 245772 -7 -T4 493.97 485.52 1.99 191692 20.66 20.01 0.08 18548 240192 -8 -T4 512.28 506.08 2.20 380096 22.03 19.58 0.11 34888 229740 -9 -T4 652.71 559.20 4.78 691076 20.57 19.15 0.08 67700 224496 ... The tests on Bionic are still running. Generating the raspi2 image is not part of autopkgtests at the moment, but may be periodically tested internally often and I can't tell the number of downloads either thus I'm asking for help to pick the proper compression setting for xz. Looking at the Xenial numbers I believe -3 would result reasonably fast builds with a tolerable increase in size compared to xz -6's results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1732681/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1732681] Re: Switching to to xz -0 from pxz increases compressed raspi2 image size
** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Xenial) Assignee: (unassigned) => Balint Reczey (rbalint) ** Description changed: + [Impact] + + * Switching from xz -0 to xz (-6) for compression raspi2 image. + + [Test Case] + + * To test the change install updated livecd-rootfs on armhf and create images setting the following environment variables: ARCH=armhf SUBARCH=raspi2 PROJECT=ubuntu-cpc. +Notice that the xz-compressed rapi2 image is still created with xz's default (-6) compression. + + [Regression Potential] + + * In case of this change causes regression it would manifest itself as + failing build for raspi2, failing build for ubuntu-cpc images or using + other compression for raspi2 images than xz -6. + + [Original Bug Report Text] + Switching from pxz to xz -0 in LP: #1701132 made the downloadable raspi2 image bigger, ~360MB which is a notable size increase from the original ~250MB while decreasing time the needed for compressing it. The bigger compressed image is currently downloadable for Artful: http://cdimage.ubuntu.com/ubuntu/releases/17.10/release/ Zesty's image is 232MB: http://cdimage.ubuntu.com/ubuntu/releases/17.04/release/ To find the proper trade-off I ran compression tests on Xenial (xz ignores -T4 there): https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1701132/comments/5 : ... rbalint@xenial-test:~/Downloads$ ls -al ubuntu-16.04.3-preinstalled-server-armhf+raspi2.img.p.xz -rw-rw-r-- 1 rbalint rbalint 254621780 Nov 16 00:03 ubuntu-16.04.3-preinstalled-server-armhf+raspi2.img.p.xz ... -0 -T4 81.56 73.64 1.46 4820 29.27 25.82 0.09 2252 329984 -1 -T4 103.68 95.14 1.67 10800 24.41 22.86 0.12 3180 298060 -2 -T4 134.05 126.22 1.76 18480 22.06 21.65 0.13 4232 286276 -3 -T4 170.57 162.72 1.72 33812 21.62 20.94 0.12 6188 275036 -4 -T4 322.15 317.83 2.10 50284 21.55 21.05 0.07 6136 258684 -5 -T4 407.15 399.93 1.92 97656 21.85 20.50 0.12 10412 247320 -6 -T4 478.64 473.32 1.95 97660 21.92 20.34 0.09 10348 245772 -7 -T4 493.97 485.52 1.99 191692 20.66 20.01 0.08 18548 240192 -8 -T4 512.28 506.08 2.20 380096 22.03 19.58 0.11 34888 229740 -9 -T4 652.71 559.20 4.78 691076 20.57 19.15 0.08 67700 224496 ... The tests on Bionic are still running. Generating the raspi2 image is not part of autopkgtests at the moment, but may be periodically tested internally often and I can't tell the number of downloads either thus I'm asking for help to pick the proper compression setting for xz. Looking at the Xenial numbers I believe -3 would result reasonably fast builds with a tolerable increase in size compared to xz -6's results. ** Branch linked: lp:~rbalint/livecd-rootfs/deps-xenial -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1732681 Title: Switching to to xz -0 from pxz increases compressed raspi2 image size Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: In Progress Bug description: [Impact] * Switching from xz -0 to xz (-6) for compression raspi2 image. [Test Case] * To test the change install updated livecd-rootfs on armhf and create images setting the following environment variables: ARCH=armhf SUBARCH=raspi2 PROJECT=ubuntu-cpc. Notice that the xz-compressed rapi2 image is still created with xz's default (-6) compression. [Regression Potential] * In case of this change causes regression it would manifest itself as failing build for raspi2, failing build for ubuntu-cpc images or using other compression for raspi2 images than xz -6. [Original Bug Report Text] Switching from pxz to xz -0 in LP: #1701132 made the downloadable raspi2 image bigger, ~360MB which is a notable size increase from the original ~250MB while decreasing time the needed for compressing it. The bigger compressed image is currently downloadable for Artful: http://cdimage.ubuntu.com/ubuntu/releases/17.10/release/ Zesty's image is 232MB: http://cdimage.ubuntu.com/ubuntu/releases/17.04/release/ To find the proper trade-off I ran compression tests on Xenial (xz ignores -T4 there): https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1701132/comments/5 : ... rbalint@xenial-test:~/Downloads$ ls -al ubuntu-16.04.3-preinstalled-server-armhf+raspi2.img.p.xz -rw-rw-r-- 1 rbalint rbalint 254621780 Nov 16 00:03 ubuntu-16.04.3-preinstalled-server-armhf+raspi2.img.p.xz ... -0 -T4 81.56 73.64 1.46 4820 29.27 25.82 0.09 2252 329984 -1 -T4 103.68 95.14 1.67 10800 24.41 22.86 0.12 3180 298060 -2 -T4 134.05 126.22 1.76 18480 22.06 21.65 0.13 4232 286276 -3 -T4 170.57
[Group.of.nepali.translators] [Bug 1701132] Re: Please use xz instead of pxz
416368 -1 -T435.73 140.12 0.4573456 1.291.220.063136 414640 -2 -T438.15 149.36 0.54141044 1.301.210.084160 414624 -3 -T440.74 153.95 0.55276336 1.301.220.086216 414620 -4 -T440.02 152.20 0.63341980 1.381.230.116352 414588 -5 -T441.68 153.74 1.10676656 1.491.270.1010336 414564 -6 -T442.70 157.64 1.19677144 1.481.250.1310436 414564 -7 -T447.70 157.42 2.241330432 1.601.320.0818480 414560 -8 -T474.56 178.48 13.32 1676392 1.691.340.1035000 414560 Command terminated by signal 9 Command exited with non-zero status 1 0 -9 -T419.60 41.90 5.281656776 0.010.000.002076 416296 -0e -T430.23 117.70 0.5630596 1.291.220.062444 414584 -1e -T437.16 144.83 0.5190304 1.311.210.103272 414572 -2e -T438.73 151.84 0.50174124 1.321.240.084296 414568 -3e -T440.78 156.10 0.65342012 1.331.270.056432 414572 -4e -T442.03 161.22 0.62342108 1.331.240.096396 414564 -5e -T443.10 160.05 1.08676732 1.471.300.0710448 414568 -6e -T443.17 159.25 1.31676584 1.551.270.1210328 414564 -7e -T448.12 162.80 2.091330552 1.601.290.1218596 414568 -8e -T477.13 182.30 13.98 1673832 1.691.340.1034920 0 - Command terminated by signal 9 Command exited with non-zero status 1 + Command terminated by signal 9 Command exited with non-zero status 1 -9e -T418.92 44.75 4.781662540 0.020.000.002196 ** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Xenial) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1701132 Title: Please use xz instead of pxz Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: In Progress Bug description: [Impact] * Livecd-rootfs switches from using pxz to xz * Pxz is installed at run-time instead of being a package dependency and pxz is in universe despite livecd-rootfs being in main. Both of those are undesired and fixing them makes livecd-rootfs easier to maintain following best practice and policy in Ubuntu. [Test Case] * Livecd-rootfs in Xenial uses (p)xz only for compressing raspi2 images. To test the change install updated livecd-rootfs on armhf and create images setting the following environment variables: ARCH=armhf SUBARCH=raspi2 PROJECT=ubuntu-cpc. Notice that the xz-compressed rapi2 image is still created. [Regression Potential] * It is a known and accepted regression that raspi2 image generation takes more wall-clock time after switching to xz because while Xenial's xz version does accept the -T4 option it does not compress in a parallel manner. * The original change in Artful set -0 compression for xz which resulted in ~35% bigger compressed images. This regression is fixed in LP: #1732681 which is scheduled to be back-ported together with switching to xz. * In case of this change causes regression it would manifest itself as failing build for raspi2, failing build for ubuntu-cpc images or increased raspi2 image size. [Original bug report text] Livecd-rootfs (main) 2.447 uses "pxz -T4" for xz compression, while pxz is not in main. Xz 5.2 also supports multi-threaded compression thus xz could easily replace current pxz usage. A quick test on compressing livecd.ubuntu-cpc.img (created by ubuntu- image) shows that there is very little difference in compressed file size while xz's -T4 brings substantial speedup in wall clock time: $ cat test-xz #!/bin/sh TESTFILE=$1 echo "Compr.\tThreads\tWall.t\tUser.t\tSys.t\tRes.t" > times.txt echo "Wall.t\tUser.t\tSys.t\tRes.t" > decompression-times.txt echo "Size(kB)" > sizes.txt for threads in 1 4; do for compression in $(seq 0 9) $(seq -f '%0.fe' 0 9); do /usr/bin/time -a -o times.txt -f "-$compression\t -T$threads\t%e\t%U\t%S\t%M" -- xz -T$threads -$compression -k $TESTFILE /usr/bin/time -a -o decompression-times.txt -f "%e\t%U\t%S\t%M" -- xz -t $TESTFILE.xz ls -k -s $TESTFILE.xz | cut -d' ' -f1 >> sizes.txt rm $
[Group.of.nepali.translators] [Bug 1699105] Re: Update google compute-image-packages to 20170609
** Changed in: gce-compute-image-packages (Ubuntu Trusty) Status: New => Invalid ** Changed in: gce-compute-image-packages (Ubuntu Xenial) Status: New => Invalid ** Changed in: gce-compute-image-packages (Ubuntu Yakkety) Status: New => Invalid ** Changed in: gce-compute-image-packages (Ubuntu Zesty) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1699105 Title: Update google compute-image-packages to 20170609 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Invalid Status in gce-compute-image-packages source package in Xenial: Invalid Status in gce-compute-image-packages source package in Yakkety: Invalid Status in gce-compute-image-packages source package in Zesty: Invalid Bug description: [Impact] compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1699105/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
