[Group.of.nepali.translators] [Bug 1822270] Re: Debconf readline frontend does not show options
** Changed in: debconf (Ubuntu Eoan) 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/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Fix Released Status in debconf source package in Xenial: Confirmed Status in debconf source package in Bionic: Confirmed Status in debconf source package in Cosmic: Confirmed Status in debconf source package in Disco: Confirmed Status in debconf source package in Eoan: Fix Released Status in debconf package in Debian: Fix Committed Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. Upstream commit: https://salsa.debian.org/pkg- debconf/debconf/commit/48c5ce38cfd5 [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: 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.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+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 1817518] Re: Bluetooth not working (Intel CyclonePeak)
** Also affects: oem-priority 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/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+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 1826357] Re: linux-hwe: 4.15.0-49.52~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1826356 (linux-hwe-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Testing phase-changed: Monday, 29. April 2019 18:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing 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/1826357 Title: linux-hwe: 4.15.0-49.52~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1826356 (linux-hwe-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Testing phase-changed: Monday, 29. April 2019 18:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826357/+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 1826354] Re: linux-azure: 4.15.0-1044.48 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826352 (trusty/linux-azure) derivatives: bug 1826351 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Testing phase-changed: Monday, 06. May 2019 15:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): - arch=amd64:channel=latest/beta' - snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): - arch=amd64:channel=latest/edge' + snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected channel(s): + arch=amd64:channel=latest/candidate:rev=55' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing 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/1826354 Title: linux-azure: 4.15.0-1044.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826352 (trusty/linux-azure) derivatives: bug 1826351 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Testing phase-changed: Monday, 06. May 2019 15:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected channel(s): arch=amd64:channel=latest/candidate:rev=55' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826354/+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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system
This bug was fixed in the package apt - 1.8.1+19.10
---
apt (1.8.1+19.10) eoan; urgency=medium
* Upload to eoan
apt (1.8.1) unstable; urgency=medium
* Add test case for local-only packages pinned to never
* Prevent shutdown while running dpkg (LP: #1820886)
* Add linux-{buildinfo,image-unsigned,source} versioned kernel pkgs
(LP: #1821640)
-- Julian Andres Klode Mon, 06 May 2019 11:26:17
+0200
** Changed in: apt (Ubuntu Eoan)
Status: Triaged => 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/1821640
Title:
Missing pattern for linux-image-unsigned keeps autoremovable kernels
on the system
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
New
Status in apt source package in Bionic:
New
Status in apt source package in Cosmic:
New
Status in apt source package in Disco:
Fix Committed
Status in apt source package in Eoan:
Fix Released
Bug description:
[Impact]
Unattended-upgrades keeps versioned kernel packages because they don't match
known kernel package patterns:
...
Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it
would also remove the following packages which should be kept in this step:
linux-image-unsigned-4.18.0-14-generic
...
For reproduction see LP: #1795696, but running u-u with --verbose.
And APT does not apply proper kernel-version based protection to it.
[Test case]
linux-image-unsigned should popup in the same list in 01autoremove-kernels as
linux-signed-image, and should be autoremovable iff it's signed counterpart is
autoremovable.
[Regression potential]
Not really any, it's just an additional string in the entry. The only
difference really possible therefore is that the set of autoremovable packages
changes and unattended-upgrades and friends might autoremove different sets of
them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress
This bug was fixed in the package apt - 1.8.1+19.10
---
apt (1.8.1+19.10) eoan; urgency=medium
* Upload to eoan
apt (1.8.1) unstable; urgency=medium
* Add test case for local-only packages pinned to never
* Prevent shutdown while running dpkg (LP: #1820886)
* Add linux-{buildinfo,image-unsigned,source} versioned kernel pkgs
(LP: #1821640)
-- Julian Andres Klode Mon, 06 May 2019 11:26:17
+0200
** Changed in: apt (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/1820886
Title:
Potential inconsistency due to system halt/reboot being allowed when
package installation in progress
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
New
Status in apt source package in Bionic:
New
Status in apt source package in Cosmic:
New
Status in apt source package in Disco:
Fix Committed
Bug description:
[System]
Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic,
Cosmic).
[Impact]
Package installation turns into an inconsistent state if system is rebooted
in the middle of an apt install/upgrade.
[Test Case]
1. User1 at Ubuntu box issues "sudo apt-get upgrade";
2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
3. System reboots and potentially turns into an inconsistent state.
[Remarks]
APT should automatically inhibit system halts/reboots while packages being
installed/removed. A similar behavior to what is shown by unattended-upgrades.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1826354] Re: linux-azure: 4.15.0-1044.48 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826352 (trusty/linux-azure) derivatives: bug 1826351 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 - phase: Promote to Proposed - phase-changed: Monday, 06. May 2019 10:40 UTC + phase: Testing + phase-changed: Monday, 06. May 2019 15:11 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): + arch=amd64:channel=latest/beta' + snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): + arch=amd64:channel=latest/edge' + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing 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/1826354 Title: linux-azure: 4.15.0-1044.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826352 (trusty/linux-azure) derivatives: bug 1826351 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Testing phase-changed: Monday, 06. May 2019 15:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): arch=amd64:channel=latest/beta' snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): arch=amd64:channel=latest/edge' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826354/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to :
[Group.of.nepali.translators] [Bug 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826036 - phase: Packaging - phase-changed: Monday, 06. May 2019 13:34 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 06. May 2019 14:34 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Holding -- builds not complete in ppa -- 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/1826032 Title: linux-fips: 4.4.0-1009.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826036 phase: Holding before Promote to Proposed phase-changed: Monday, 06. May 2019 14:34 UTC reason: promote-to-proposed: Holding -- builds not complete in ppa To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826032/+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 1826351] Re: linux-azure-edge: 4.15.0-1044.48 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826354 - phase: Promote to Proposed - phase-changed: Monday, 06. May 2019 11:42 UTC + phase: Ready for Testing + phase-changed: Monday, 06. May 2019 13:44 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + regression-testing: Ongoing -- testing in progress + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing 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/1826351 Title: linux-azure-edge: 4.15.0-1044.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-azure-edge source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826354 phase: Ready for Testing phase-changed: Monday, 06. May 2019 13:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826351/+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 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826036 - phase: Ready for Packaging - phase-changed: Wednesday, 24. April 2019 09:06 UTC + phase: Packaging + phase-changed: Monday, 06. May 2019 13:34 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- 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/1826032 Title: linux-fips: 4.4.0-1009.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1826036 phase: Packaging phase-changed: Monday, 06. May 2019 13:34 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826032/+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 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value
Can we get an SRU template for this bug? At least a viable test-case could be enough, with bonus points for everything else. ** Also affects: libreoffice (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: openjdk-lts (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Disco) 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/1822839 Title: LibreOffice doesn't detect JVM because of unexpected java.vendor property value Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in openjdk-lts package in Ubuntu: New Status in libreoffice source package in Xenial: Triaged Status in libreoffice source package in Bionic: Triaged Status in libreoffice source package in Disco: Incomplete Status in openjdk-lts source package in Disco: New Status in libreoffice package in Debian: New Bug description: libreoffice autopkgtests are failing on disco with openjdk 11.0.3+4-2ubuntu1. The likely culprit is that change: +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium + + * Sync packages with 11.0.3+4-2: +[ Matthias Klose ] +- Configure with vendor flags. Indeed with version 11.0.3+4-1ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Oracle Corporation And with version 11.0.3+4-2ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Private Build Looking at the code in Libreoffice that looks for a JVM, it validates the vendor against a hardcoded list of known vendors: https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33 Not sure what the purpose of that upstream code is, but this means the new openjdk-11 build in Ubuntu breaks it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:06:25 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (1003 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: openjdk-lts UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1822839/+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 1827866] Re: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X-KVM
vmx_apicv_test timeouted on B-KVM: FAIL vmx_apicv_test (timeout; duration=10) ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: - vmx_apicv_test from ubuntu_kvm_unit_tests failed on X-KVM, the test was - terminated with return code 124: + vmx_apicv_test from ubuntu_kvm_unit_tests failed on X-KVM: + FAIL vmx_apicv_test (timeout; duration=10) + + the test was terminated with return code 124: # TESTNAME=vmx_apicv_test TIMEOUT=10 ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "apic_reg_virt_test virt_x2apic_mode_test" timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,+vmx -append apic_reg_virt_test virt_x2apic_mode_test # -initrd /tmp/tmp.K6b7rjmgp8 enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: apic_reg_virt_test --- Virtualize APIC accesses test --- PASS: xapic - reading 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - writing 0x12345678 to 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - reading 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - writing 0x12345678 to 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - reading 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - writing 0x12345678 to 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - reading 0x030: got APIC access exit @ page offset 0x030, want 0x030 PASS: xapic - writing 0x12345678 to 0x380: non-virtualized write; val is 0x12345678, want 0x12345678 PASS: xapic - reading 0x390: read 0x12345678, expected 0x12345678. PASS: xapic - writing 0x12345678 to 0x390: non-virtualized writqemu-system-x86_64: terminating on signal 15 from pid 1327 # echo $? 124 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1044-kvm 4.4.0-1044.50 ProcVersionSignature: Ubuntu 4.4.0-1044.50-kvm 4.4.177 Uname: Linux 4.4.0-1044-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon May 6 10:47:17 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1827866 Title: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Bionic: New Bug description: vmx_apicv_test from ubuntu_kvm_unit_tests failed on X-KVM: FAIL vmx_apicv_test (timeout; duration=10) the test was terminated with return code 124: # TESTNAME=vmx_apicv_test TIMEOUT=10 ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "apic_reg_virt_test virt_x2apic_mode_test" timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,+vmx -append apic_reg_virt_test virt_x2apic_mode_test # -initrd /tmp/tmp.K6b7rjmgp8 enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: apic_reg_virt_test --- Virtualize APIC accesses test --- PASS: xapic - reading 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - writing 0x12345678 to 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - reading 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - writing 0x12345678 to 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - reading 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - writing 0x12345678 to 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - reading 0x030: got APIC access exit @ page offset 0x030, want 0x030 PASS: xapic - writing 0x12345678 to 0x380: non-virtualized write; val is 0x12345678, want 0x12345678 PASS: xapic - reading 0x390: read 0x12345678, expected 0x12345678. PASS: xapic - writing 0x12345678 to 0x390: non-virtualized writqemu-system-x86_64: terminating on signal 15 from pid 1327 # echo $? 124 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1044-kvm 4.4.0-1044.50 ProcVersionSignature: Ubuntu 4.4.0-1044.50-kvm 4.4.177 Uname: Linux 4.4.0-1044-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture:
[Group.of.nepali.translators] [Bug 1826028] Re: linux-kvm: 4.4.0-1045.51 -proposed tracker
4.4.0-1045.51 - kvm Regression test CMPL, RTB. Issue to note in amd64: ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel (bug 1763323) ubuntu_kernel_selftests - psock_tpacket in net failed (bug 1812176) test_bpf in net (bug 1812189) test_user_copy return code in user (bug 1812352) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) port80 (bug 1748105) vmx (bug 1821394) vmx_hlt_with_rvi_test (bug 1822308) vmx_apicv_test (bug 1827866) vmx_apic_passthrough_thread (bug 1822309) debug (bug 1821906) ubuntu_ltp_syscalls - tested failed for nfs-kernel-server issue (bug 1821275) ubuntu_lxc - python3 API failed (bug 1764618) ubuntu_qrt_kernel_security - SCHED_STACK_END_CHECK should be enabled (bug 1812159) ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1826028 Title: linux-kvm: 4.4.0-1045.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826036 phase: Signoff phase-changed: Saturday, 27. April 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826028/+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 1812159] Re: SCHED_STACK_END_CHECK should be enabled in B-kvm
Found on X-KVM as well.
** Tags added: cosmic xenial
** Also affects: linux-kvm (Ubuntu Xenial)
Importance: Undecided
Status: New
** Summary changed:
- SCHED_STACK_END_CHECK should be enabled in B-kvm
+ q-r-t security test says SCHED_STACK_END_CHECK should be enabled in B-kvm
** Summary changed:
- q-r-t security test says SCHED_STACK_END_CHECK should be enabled in B-kvm
+ q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels
--
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/1812159
Title:
q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM
kernels
Status in ubuntu-kernel-tests:
New
Status in linux-kvm package in Ubuntu:
New
Status in linux-kvm source package in Xenial:
New
Status in linux-kvm source package in Bionic:
New
Status in linux-kvm source package in Cosmic:
New
Bug description:
The test_380_config_sched_stack_end_check test failed on the Bionic
KVM kernel
FAIL: test_380_config_sched_stack_end_check
(__main__.KernelSecurityConfigTest)
Ensure SCHED_STACK_END_CHECK is set
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2628, in
test_380_config_sched_stack_end_check
self.assertKernelConfig('SCHED_STACK_END_CHECK', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: SCHED_STACK_END_CHECK option was expected to be set in
the kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 06:44:41 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812159/+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 1827391] Re: Japanese era Reiwa SRU
** Changed in: icu (Debian) 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/1827391 Title: Japanese era Reiwa SRU Status in icu package in Ubuntu: New Status in icu source package in Precise: New Status in icu source package in Trusty: New Status in icu source package in Xenial: New Status in icu source package in Bionic: New Status in icu source package in Cosmic: New Status in icu source package in Disco: New Status in icu source package in Eoan: New Status in icu package in Debian: Fix Released Bug description: Japanese era Reiwa SRU $ rmadison icu 4.8.1.1-3ubuntu0.7 | precise-updates 52.1-3ubuntu0.8| trusty-updates 55.1-7ubuntu0.4| xenial-updates 60.2-3ubuntu3 | bionic 60.2-6ubuntu1 | cosmic 63.1-6 | disco 63.1-6 | eoan Note reported abi break / crash of chromium at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1827391/+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 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Cosmic) 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/1820886 Title: Potential inconsistency due to system halt/reboot being allowed when package installation in progress Status in apt package in Ubuntu: In Progress Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: New Bug description: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] 1. User1 at Ubuntu box issues "sudo apt-get upgrade"; 2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI; 3. System reboots and potentially turns into an inconsistent state. [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade
Debugging per [1], did not show anything new.
There just is no activity on the actual access of /home all I see is the
trigger for /home registering at startup.
Startup:
ubuntu@xenial-autofs-client:/$ sudo automount -f -v --debug
Starting automounter version 5.1.1, master map /etc/auto.master
using kernel protocol version 5.02
lookup_nss_read_master: reading master file /etc/auto.master
parse_init: parse(sun): init gathered global options: (null)
lookup_read_master: lookup(file): read entry +dir:/etc/auto.master.d
lookup_nss_read_master: reading master dir /etc/auto.master.d
lookup_read_master: lookup(dir): scandir: /etc/auto.master.d
lookup_read_master: lookup(file): read entry /-
master_do_mount: mounting /-
automount_path_to_fifo: fifo name /var/run/autofs.fifo--
lookup_nss_read_map: reading map file /etc/auto.nfs
parse_init: parse(sun): init gathered global options:
nosymlink,fstype=nfs,nfsvers=3,rw,hard,intr,rsize=8192,wsize=8192
mounted direct on /home with timeouts disabled
do_mount_autofs_direct: mounted trigger /home
st_ready: st_ready(): state = 0 path /-
It is the open syscall itself that fails:
0.29 open("/home", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ELOOP
(Too many levels of symbolic links) <0.12>
So we must have set up the kernel/trigger to be broken - no userspace component
active at the time (although it might have set it up wrong before).
But since I haven't found fixes in autofs maybe it is fixed in the kernel then?
Yes, here I found a fix.
Installing linux-virtual-hwe-16.04 (since I was in a VM to test) resolved the
issue.
With the same setup I can now mount /home just fine again on Xenial.
On a bare metal system you likely want linux-generic-hwe-16.04 instead.
I'm adding a kernel task to potentially identify and backport the fix to the
4.4 kernel, but since after so much time it isn't in the stable releases
chances are that it is hard to backport.
Until then you can get this issue resolved with the -hwe kernels.
[1]:
https://help.ubuntu.com/community/Autofs#Debugging_Auto_Mount_Problems
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: autofs5 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: autofs5 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: autofs5 (Ubuntu Bionic)
Status: New => Invalid
** Changed in: autofs5 (Ubuntu Xenial)
Status: New => Invalid
** Changed in: autofs5 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
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/1827286
Title:
autofs - "Too many levels of symbolic links" after apt upgrade
Status in autofs5 package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in autofs5 source package in Xenial:
Invalid
Status in linux source package in Xenial:
Confirmed
Status in autofs5 source package in Bionic:
Invalid
Status in linux source package in Bionic:
Fix Released
Bug description:
Description:Ubuntu 16.04.6 LTS
Release:16.04
I moved to autofs this week as a workaround for Bug #1577575 failing
to mount NFS entries at boot. This worked file until I ran 'apt
upgrade' today.
Now trying to access /vol/home mount results in the following error:
root@chi:~# ls -la /vol/home/
ls: cannot access '/vol/home/': Too many levels of symbolic links
root@chi:~#
Oddly enough, the other two autofs entries work fine (output trimmed):
root@chi:~# ls -la /vol/media
total 4
...
root@chi:~#
root@chi:~# ls -al /vol/temp/
total 24
...
root@chi:~#
I have a scratch VM I can break tonight by performing upgrades individually
and testing after each. Will provide that detail when available.
Here is /var/log/apt/history.log
Start-Date: 2019-05-01 17:37:00
Commandline: apt upgrade
Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12,
1:9.10.3.dfsg.P4-8ubuntu1.14), libisccfg140:amd64
(1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), ureadahead:amd64
(0.100.0-19, 0.100.0-19.1), libldap-2.4-2:amd64 (2.4.42+dfsg-2ubuntu3.4,
2.4.42+dfsg-2ubuntu3.5), libirs141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12,
1:9.10.3.dfsg.P4-8ubuntu1.14), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12,
1:9.10.3.dfsg.P4-8ubuntu1.14), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12,
1:9.10.3.dfsg.P4-8ubuntu1.14), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12,
[Group.of.nepali.translators] [Bug 1826453] Re: Grub2 Booting in blind mode due to "invalid video mode specification `text'"
This bug was fixed in the package grub2-signed - 1.66.22 --- grub2-signed (1.66.22) xenial; urgency=medium * Rebuild against grub2 2.02~beta2-36ubuntu3.22. (LP: #1826453) -- Mathieu Trudel-Lapierre Tue, 30 Apr 2019 11:16:33 -0400 ** Changed in: grub2-signed (Ubuntu Xenial) 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/1826453 Title: Grub2 Booting in blind mode due to "invalid video mode specification `text'" Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in grub2 source package in Trusty: New Status in grub2-signed source package in Trusty: New Status in grub2 source package in Xenial: Fix Released Status in grub2-signed source package in Xenial: Fix Released Bug description: [Impact] UEFI users booting VMs on Hyper-V [Test case] 1) Install Ubuntu 16.04 in a Gen2 VM on Hyper-V (Windows) 2) After install; edit /etc/default/grub to add: GRUB_GFXPAYLOAD_LINUX="text" 3) Run 'sudo update-grub' 4) Reboot Verify whether the system writes an error/warning on console during boot (this shows up and disappears quickly, one must watch the console attentively): error: invalid video mode specification `text'. Booting in blind mode [Regression potential] There is minimal risk of regression; this is a patch that has been succesfully used in other releases to address the same issue (see bug 1711452). It only affects graphical payload selection in grub to avoid a value that is clearly invalid, thus skipping the error value and falling back to the default text-mode. Care should be taking while testing to identify any possible issues with displaying the grub menu or outputting information from the kernel at console as the system boots (if applicable). --- In a Ubuntu 16.04.6 VM, which runs as a Gen2 VM on Hyper-V, I add GRUB_GFXPAYLOAD_LINUX="text" into /etc/default/grub and run update- grub; next, grub2 prints the below error: error: invalid video mode specification `text'. Booting in blind mode This means grub2 passes a zero value for the "lfb_base" to Linux kernel, which then fails to reserve the framebuffer MMIO range in drivers/hv/vmbus_drv.c: vmbus_reserve_fb(); as a result, when we pass through a PCIe device to the VM, the PCIe device may get a PCI MMIO BAR in the FB MMIO range, causing a conflict, and the PCIe device can not work in the VM. The issue can not reproduce with Ubuntu 18.04. It turns out the grub2 in Ubuntu 18.04 has the below fix: video: skip 'text' gfxpayload if not supported, to fallback to default (https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/commit/?id=38d9e2f862a96a039ae8ca8b87b8615d154ceda4). I'm asking the patch author (Mathieu Trudel-Lapierre) to submit the patch to the upstream grub and this is the upstream bug link: https://savannah.gnu.org/bugs/?56217 . Here this launchpad bug is for Ubuntu 16.04 and 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1826453/+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 1825968] Re: dep8/lxd: test fails due to unrelated message to stderr
This bug was fixed in the package ubuntu-fan - 0.12.8~16.04.3 --- ubuntu-fan (0.12.8~16.04.3) xenial; urgency=medium * dep8: Allow output on stderr without failing (LP: #1825968) -- Stefan Bader Tue, 23 Apr 2019 12:37:17 +0200 ** Changed in: ubuntu-fan (Ubuntu Xenial) 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/1825968 Title: dep8/lxd: test fails due to unrelated message to stderr Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: Fix Released Status in ubuntu-fan source package in Bionic: Triaged Bug description: [SRU Justification] == Impact == The LXD DEP8 test fails because of an unrelated message to stderr during containser setup (sd_bus_open_system: No such file or directory Exit request sent.). The test itself successfully runs to completion. == Fix == Change the test control to ignore messages on stderr sicne the test itself should exit with a non-zero return code if some test error happens. == Testcase == ADT testing == Risk of Regression == None, no code change, only DEP8 testing modified To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1825968/+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 1826453] Re: Grub2 Booting in blind mode due to "invalid video mode specification `text'"
This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.22 --- grub2 (2.02~beta2-36ubuntu3.22) xenial; urgency=medium * debian/patches/skip_text_gfxpayload_where_not_supported.patch: Skip the 'text' payload if it's not supported but present in gfxpayload, such as on EFI systems. (LP: #1826453) -- Mathieu Trudel-Lapierre Mon, 29 Apr 2019 10:04:24 -0400 ** Changed in: grub2 (Ubuntu Xenial) 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/1826453 Title: Grub2 Booting in blind mode due to "invalid video mode specification `text'" Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in grub2 source package in Trusty: New Status in grub2-signed source package in Trusty: New Status in grub2 source package in Xenial: Fix Released Status in grub2-signed source package in Xenial: Fix Released Bug description: [Impact] UEFI users booting VMs on Hyper-V [Test case] 1) Install Ubuntu 16.04 in a Gen2 VM on Hyper-V (Windows) 2) After install; edit /etc/default/grub to add: GRUB_GFXPAYLOAD_LINUX="text" 3) Run 'sudo update-grub' 4) Reboot Verify whether the system writes an error/warning on console during boot (this shows up and disappears quickly, one must watch the console attentively): error: invalid video mode specification `text'. Booting in blind mode [Regression potential] There is minimal risk of regression; this is a patch that has been succesfully used in other releases to address the same issue (see bug 1711452). It only affects graphical payload selection in grub to avoid a value that is clearly invalid, thus skipping the error value and falling back to the default text-mode. Care should be taking while testing to identify any possible issues with displaying the grub menu or outputting information from the kernel at console as the system boots (if applicable). --- In a Ubuntu 16.04.6 VM, which runs as a Gen2 VM on Hyper-V, I add GRUB_GFXPAYLOAD_LINUX="text" into /etc/default/grub and run update- grub; next, grub2 prints the below error: error: invalid video mode specification `text'. Booting in blind mode This means grub2 passes a zero value for the "lfb_base" to Linux kernel, which then fails to reserve the framebuffer MMIO range in drivers/hv/vmbus_drv.c: vmbus_reserve_fb(); as a result, when we pass through a PCIe device to the VM, the PCIe device may get a PCI MMIO BAR in the FB MMIO range, causing a conflict, and the PCIe device can not work in the VM. The issue can not reproduce with Ubuntu 18.04. It turns out the grub2 in Ubuntu 18.04 has the below fix: video: skip 'text' gfxpayload if not supported, to fallback to default (https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/commit/?id=38d9e2f862a96a039ae8ca8b87b8615d154ceda4). I'm asking the patch author (Mathieu Trudel-Lapierre) to submit the patch to the upstream grub and this is the upstream bug link: https://savannah.gnu.org/bugs/?56217 . Here this launchpad bug is for Ubuntu 16.04 and 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1826453/+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 1799614] Re: Use new media API
This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.10 --- gnome-software (3.28.1-0ubuntu4.18.04.10) bionic; urgency=medium * debian/control: * debian/patches/0027-snap-Use-new-media-API.patch: - Use new snapd media API (LP: #1799614) * debian/patches/0030-odrs-Only-show-reviews-from-the-same-distribution.patch: - Show only Ubuntu reviews (LP: #1825064) -- Robert Ancell Wed, 17 Apr 2019 12:48:34 +1200 ** Changed in: gnome-software (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/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Released Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Status in snapd-glib source package in Cosmic: Fix Released Bug description: [Impact] snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. [Test Case] Run gnome-software with updated snapd-glib and confirm that screenshots and promoted snap banners continue to work. [Regression Potential] Possibility of new errors being introduced in updated code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1799614] Re: Use new media API
This bug was fixed in the package gnome-software - 3.30.2-0ubuntu11 --- gnome-software (3.30.2-0ubuntu11) cosmic; urgency=medium * debian/patches/0025-snap-Use-new-media-API.patch: * debian/control: - Use new snapd media API (LP: #1799614) * debian/patches/0026-odrs-Only-show-reviews-from-the-same-distribution.patch: - Show only Ubuntu reviews (LP: #1825064) -- Robert Ancell Wed, 17 Apr 2019 14:48:48 +1200 ** Changed in: gnome-software (Ubuntu Cosmic) 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/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Status in snapd-glib source package in Cosmic: Fix Released Bug description: [Impact] snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. [Test Case] Run gnome-software with updated snapd-glib and confirm that screenshots and promoted snap banners continue to work. [Regression Potential] Possibility of new errors being introduced in updated code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+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 1825994] Re: Add Ubuntu Eoan as a known release
This bug was fixed in the package debootstrap - 1.0.112ubuntu1.1 --- debootstrap (1.0.112ubuntu1.1) disco; urgency=low * Add (Ubuntu) eoan as a symlink to gutsy. (LP: #1825994) -- Andy Whitcroft Tue, 23 Apr 2019 14:43:36 +0100 ** Changed in: debootstrap (Ubuntu Disco) 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/1825994 Title: Add Ubuntu Eoan as a known release Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Trusty: Invalid Status in debootstrap source package in Xenial: Fix Committed Status in debootstrap source package in Bionic: Fix Committed Status in debootstrap source package in Cosmic: Fix Committed Status in debootstrap source package in Disco: Fix Released Status in debootstrap source package in Eoan: Fix Released Bug description: [Impact] Without this update users cannot generate eoan chroots for development. [Test Case] Attempt to debootstrap eoan. [Regression Potential] Very low, this simply introduces a suite specific script which is not used unless you attempt to create and Ubuntu Eoan chroot. === Add Eoan Eanimal as a known release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1825994/+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
