[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
** Description changed: - https://gitlab.gnome.org/GNOME/gdm/issues/408 + [Impact] + Sessions in specific circumstances when switching to TTY while plymouth is being activated or deactivated. + + [Test cases] + Steps to reproduce: + 1) Log-in using X11 login via GDM. + 2) Use the desktop for a while. (For some reason I cannot reproduce if I login and then restart after a short while). + 3) In Gnome click System menu -> Power Button -> Restart + 4) Quickly press CTRL-ALT-F1 + + Validate whether your login password is visible on the TTY. + + [Regression Potential] + Possible regressions may include difficulty showing text-mode splash or boot messages given that this changes the state of tty based on plymouth's own activation state. --- - I don't which package this applies to, but I believe the best bet is - GDM. + https://gitlab.gnome.org/GNOME/gdm/issues/408 + + + I don't which package this applies to, but I believe the best bet is GDM. Steps to reproduce: 1) Log-in using X11 login via GDM. 2) Use the desktop for a while. (For some reason I cannot reproduce if I login and then restart after a short while). 3) In Gnome click System menu -> Power Button -> Restart 4) Quickly press CTRL-ALT-F1 5) I see my login password in plain text in the console. Once I saw the login password repeated twice. See attached photo with the login password blanked out. Below the password is the console cursor. ## lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ## apt-cache policy gdm3 gdm3: Installed: 3.28.0-0ubuntu1 Candidate: 3.28.0-0ubuntu1 Version table: *** 3.28.0-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-18.19-generic 4.15.17 Uname: Linux 4.15.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:54:07 2018 InstallationDate: Installed on 2018-04-13 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: plymouth (Ubuntu) Assignee: Canonical Foundations Team (canonical-foundations) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767918 Title: Login password from GDM is shown in plain text on the VT1 console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790709] Re: Backport gnu-efi 3.0.8 to all supported releases for SHIM
Rebuilds in PPA have all passed -- the failures for efitools are exactly the same as they previously were and due to EFI not being available (or sbsigntool, efivar, etc.) on those architectures: https://launchpad.net/~cyphermox/+archive/ubuntu/rebuild-tests/+packages In any case, amd64 (the only arch that built for efitools) has not regressed. syslinux for bionic needs a patch, which in currently waiting in the bionic unapproved queue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790709 Title: Backport gnu-efi 3.0.8 to all supported releases for SHIM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnu-efi/+bug/1790709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790724] Re: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases
Verification-done for shim, shim-signed on bionic: shim 15+1533136590.3beb971-0ubuntu1 shim-signed 1.37~18.04.1+15+1533136590.3beb971-0ubuntu1 System is booting as expected with the new shim, and mokutil allows for importing a certificate and enabling validation at the same time (or any multiple actions in MokManager). ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790724 Title: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1790724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708245] Re: shim can't enable validation and enroll keys in one sitting
This confirms the system boots and is in Secure Boot mode. Do you have time to run through the other test cases using mokutil? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708245 Title: shim can't enable validation and enroll keys in one sitting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1708245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /
Verification-done on bionic with initramfs-tools 0.130ubuntu3.3: Verified that with the SRU applied, the initramfs configured to use MODULES=dep can still determine that the root is over ZFS, and accordingly add the files needed in the initramfs. ** Description changed: [Impact] - Ubuntu users who have installed on ZFS devices. + Ubuntu users who have installed on ZFS devices, and using MODULES=dep in initramfs.conf. [Test case] -- upgrade -- 1) install 16.04 using ZFS as rootfs. 2) upgrade to 18.04 -- initramfs update -- 1) install Ubuntu, using ZFS as a rootfs. - 2) run "sudo update-initramfs -u" + 2) change 'MODULES=most' to 'MODULES=dep' in /etc/initramfs-tools/initramfs.conf + 3) run "sudo update-initramfs -u" Without the patch, you should see a warning from mkinitramfs: mkinitramfs: failed to determine device for / mkinitramfs: workaround is MODULES=most, check: grep -r MODULES /etc/initramfs-tools/ With initramfs-tools patched, you should not see the warning, and instead have additional kernel modules added to the initramfs that are required to support the block devices that host the ZFS pools. [Regression Potential] This change is limited to behavior for ZFS filesystems. Likely regressions might include loading a kernel module that conflicts with another that is required at boot but not blacklisted, causing unexpected behavior on the system, or failure to find the necessary kernel modules or ZFS pools, possibly leading to an initramfs that does not contain the necessary modules yet has not shown a warning on screen to indicate that might be the issue. --- When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with root on ZFS I get this error: Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic mkinitramfs: failed to determine device for / mkinitramfs: workaround is MODULES=most, check: grep -r MODULES /etc/initramfs-tools/ Error please report bug on initramfs-tools Include the output of 'mount' and 'cat /proc/mounts' update-initramfs: failed for with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052. dpkg: error processing package linux-image-4.4.0-59-generic (--configure): subprocess installed post-installation script returned error exit status 2 version of initramfs-tools is 0.122ubuntu8.8 Output of mount is: sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755) rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) mqueue on
[Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'
Verification-done for bionic with initramfs-tools 0.130ubuntu3.3: Verified that at boot the system does get the additional config for netplan in /run/netplan and that it forces systemd-networkd not to release the IP lease. ** Tags removed: verification-needed verification-needed-artful verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769682 Title: NFS-based remote root hangs when running 'netplan apply' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401532] Re: GRUB's Secure Boot implementation loads unsigned kernel without warning
This probably should not have been closed as Fix Released quite yet. A gsbx64.efi binary was being built, which allowed enforcement. Now, the proper fix to never allow unsigned / invalidly signed kernels has landed in Cosmic; so proceeding with the SRUs. ** No longer affects: grub2 (Ubuntu Zesty) ** No longer affects: grub2 (Ubuntu Yakkety) ** No longer affects: grub2-signed (Ubuntu Yakkety) ** No longer affects: grub2-signed (Ubuntu Zesty) ** Also affects: grub2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: grub2-signed (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu Bionic) Status: New => In Progress ** Changed in: grub2-signed (Ubuntu Bionic) Status: New => In Progress ** Changed in: grub2-signed (Ubuntu Bionic) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: grub2 (Ubuntu Bionic) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: grub2 (Ubuntu Xenial) Status: Confirmed => Triaged ** Changed in: grub2 (Ubuntu Trusty) Status: Confirmed => Triaged ** Changed in: grub2-signed (Ubuntu Trusty) Status: Confirmed => Triaged ** Changed in: grub2-signed (Ubuntu) Status: Triaged => Fix Released ** Changed in: grub2-signed (Ubuntu Xenial) Status: Confirmed => Triaged ** Changed in: grub2-signed (Ubuntu Bionic) Importance: Undecided => High ** Changed in: grub2-signed (Ubuntu Xenial) Importance: Undecided => High ** Changed in: grub2-signed (Ubuntu Trusty) Importance: Undecided => High ** Changed in: grub2 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: grub2 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: grub2 (Ubuntu Trusty) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401532 Title: GRUB's Secure Boot implementation loads unsigned kernel without warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1401532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747455] Re: netplan does not support defining route with scope 'link'
** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan Status: New => Fix Committed ** Changed in: netplan.io (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747455 Title: netplan does not support defining route with scope 'link' To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1747455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736965] Re: "netplan apply" does not set file mode, umask 077 causes systemd-networkd to be unable to start
** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736965 Title: "netplan apply" does not set file mode, umask 077 causes systemd- networkd to be unable to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1736965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785033] Re: GRUB needs to support 64-bit efi linear frame buffer address
** Also affects: grub2-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1785033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790724] Re: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases
shim and shim-signed 15 / 1.37 are already in Cosmic. ** Also affects: shim (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: shim (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: shim (Ubuntu Cosmic) Status: New => Fix Released ** Also affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: shim-signed (Ubuntu Cosmic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790724 Title: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1790724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790709] Re: Backport gnu-efi 3.0.8 to all supported releases for SHIM
** Description changed: [Impact] All users on UEFI systems. Gnu-efi needs to be backported everywhere to support new shim releases. This applies to bionic, xenial, and trusty. This is to properly build the new shim releases on these releases of Ubuntu. - [Test cases] -- build tests -- Validate that the following reverse-dependencies build correctly: + + Reverse-Build-Depends-Indep + === + * syslinux + + Reverse-Build-Depends + = + * dell-recovery + * efitools + * fwupd + * fwupdate + * kexec-tools + * refind + * sbsigntool + * shim + * systemd + + Rebuild tests will happen in + https://launchpad.net/~cyphermox/+archive/ubuntu/rebuild-tests == Functionality tests == Run the following tests after the packages have been rebuilt against the new gnu-efi. === mokutil === Validate that mokutil can process: - Certificate import: mokutil --import - List enrolled certificates: mokutil --list-enrolled - Set verbosity: mokutil --set-verbosity true Reboot, and validate that MokManager processes the requested changes. - === efibootmgr === - Validate that efibootmgr can read the BootEntries normally: - - sudo efibootmgr -v - - [Regression potential] gnu-efi is a library that supports applications in handling EFI variables in and outside of the runtime environment, along with supporting standard library features for EFI applications. As such, any application that makes uses of EFI variables on a running system or as their own EFI application should be validated against possible corruption of the contents of the variables, as well as doing smoketesting of the EFI applications themselves for incorrect behavior, crashes, and other runtime issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790709 Title: Backport gnu-efi 3.0.8 to all supported releases for SHIM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnu-efi/+bug/1790709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790724] [NEW] Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases
Public bug reported: [Impact] All UEFI users. [Test case] == shim == 1) Enable Secure Boot in firmware. 2) Update to new shim and shim-signed packages (shim 15+, shim-signed 1.37~) 3) Validate that the system still boots and validates the shim image as well as the grub binary. == MokManager == 0) Generate a new self-signed certificate. You can use "sudo update-secureboot-policy --new-mok" for that purpose, the DER file will be in /var/lib/shim-signed/mok. 1) Run 'sudo mokutil --enable-validation' 2) Follow prompts on screen to enable validation if applicable. 3) Run 'sudo mokutil --import ' 4) Follow the prompts on screen to import a new certificate. 5) Reboot 6) Follow prompts to import the new certificate and enable validation. 7) Validate that the system boots all the way to userland. 8) Verify that the certificate has been correctly imported, it should be listed in the output of 'sudo mokutil --list-enrolled'. == mokutil == 1) Run 'sudo mokutil --timeout 14' (or any other arbitrary value). 2) follow the steps for MokManager tests above. 3) Validate that the MokManager prompt happens and shows a timeout appropriate for the timeout value set using the mokutil command. Also validate 'mokutil --timeout 0' works correctly, where the MokManager never times out. [Regression potential] Possible regressions might include failure to load shim or MokManager, or failure to validate an EFI binary (which usually translates in a Security Violation message. Any such issues should be investigated as possible regressions caused by this update. --- Backport shim to all supported releases of Ubuntu. Include mokutil changes to support new timeout feature. ** Affects: shim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790724 Title: Backport shim 15+1533136590.3beb971-0ubuntu1 to all supported releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1790724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790709] Re: Backport gnu-efi 3.0.8 to all supported releases for SHIM
syslinux in bionic and newer need a small fix to avoid FTBFS now that gnu-efi provides memset() and memcpy(). ** Description changed: + [Impact] + All users on UEFI systems. + Gnu-efi needs to be backported everywhere to support new shim releases. This applies to bionic, xenial, and trusty. + + This is to properly build the new shim releases on these releases of + Ubuntu. + + + [Test cases] + -- build tests -- + Validate that the following reverse-dependencies build correctly: + + + == Functionality tests == + + Run the following tests after the packages have been rebuilt against the + new gnu-efi. + + === mokutil === + Validate that mokutil can process: + - Certificate import: mokutil --import + - List enrolled certificates: mokutil --list-enrolled + - Set verbosity: mokutil --set-verbosity true + + Reboot, and validate that MokManager processes the requested changes. + + + === efibootmgr === + Validate that efibootmgr can read the BootEntries normally: + + sudo efibootmgr -v + + + [Regression potential] + gnu-efi is a library that supports applications in handling EFI variables in and outside of the runtime environment, along with supporting standard library features for EFI applications. As such, any application that makes uses of EFI variables on a running system or as their own EFI application should be validated against possible corruption of the contents of the variables, as well as doing smoketesting of the EFI applications themselves for incorrect behavior, crashes, and other runtime issues. ** Also affects: syslinux (Ubuntu) Importance: Undecided Status: New ** Changed in: gnu-efi (Ubuntu) Status: New => Fix Released ** Also affects: gnu-efi (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: syslinux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: syslinux (Ubuntu) Status: New => In Progress ** Changed in: syslinux (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: syslinux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790709 Title: Backport gnu-efi 3.0.8 to all supported releases for SHIM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnu-efi/+bug/1790709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790709] [NEW] Backport gnu-efi 3.0.8 to all supported releases for SHIM
Public bug reported: [Impact] All users on UEFI systems. Gnu-efi needs to be backported everywhere to support new shim releases. This applies to bionic, xenial, and trusty. This is to properly build the new shim releases on these releases of Ubuntu. [Test cases] -- build tests -- Validate that the following reverse-dependencies build correctly: == Functionality tests == Run the following tests after the packages have been rebuilt against the new gnu-efi. === mokutil === Validate that mokutil can process: - Certificate import: mokutil --import - List enrolled certificates: mokutil --list-enrolled - Set verbosity: mokutil --set-verbosity true Reboot, and validate that MokManager processes the requested changes. === efibootmgr === Validate that efibootmgr can read the BootEntries normally: sudo efibootmgr -v [Regression potential] gnu-efi is a library that supports applications in handling EFI variables in and outside of the runtime environment, along with supporting standard library features for EFI applications. As such, any application that makes uses of EFI variables on a running system or as their own EFI application should be validated against possible corruption of the contents of the variables, as well as doing smoketesting of the EFI applications themselves for incorrect behavior, crashes, and other runtime issues. ** Affects: gnu-efi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790709 Title: Backport gnu-efi 3.0.8 to all supported releases for SHIM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnu-efi/+bug/1790709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790664] Re: routing policy not always applied on systemd-networkd restar
Please include the *.network, *.netdev, *.link files from /etc/systemd/network or /run/systemd/network as well for the configuration, after making sure you sanitized them if there are any information (IPs?) that you don't want public. Thanks! ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790664 Title: routing policy not always applied on systemd-networkd restar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782977] Re: [MIR] intel-processor-trace: new dependency of gdb
MIR approved. ** Changed in: intel-processor-trace (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782977 Title: [MIR] intel-processor-trace: new dependency of gdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-processor-trace/+bug/1782977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789743] Re: 1.37 manual testing
** Changed in: shim-signed (Ubuntu) Status: New => Fix Released ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789743 Title: 1.37 manual testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1789743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789743] [NEW] 1.37 manual testing
Public bug reported: 15+1533136590.3beb971-0ubuntu1 ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789743 Title: 1.37 manual testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1789743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789670] [NEW] qemu-system-* Recommends qemu-system-gui
Public bug reported: On cosmic as of 2018-08-29: qemu-system-$arch packages appear to Recommend qemu-system-gui. In turn, this means qemu-system-gui pulls in libgtk-3-0, which will pull in icon themes and all kinds of other things that probably shouldn't have to be on a server: mtrudel@kuebiko:~$ sudo apt install libvirt-bin libvirt-daemon libvirt0 Reading package lists... Done Building dependency tree Reading state information... Done libvirt0 is already the newest version (4.6.0-2ubuntu2). The following additional packages will be installed: adwaita-icon-theme at-spi2-core bridge-utils cpu-checker dconf-gsettings-backend dconf-service fontconfig glib-networking glib-networking-common glib-networking-services gsettings-desktop-schemas gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-x gtk-update-icon-cache hicolor-icon-theme humanity-icon-theme ibverbs-providers ipxe-qemu ipxe-qemu-256k-compat-efi-roms libaa1 libaio1 libasound2 libasound2-data libasyncns0 libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0 libavc1394-0 libbluetooth3 libbrlapi0.6 libcaca0 libcacard0 libcairo-gobject2 libcairo2 libcdparanoia0 libcolord2 libcroco3 libcups2 libdatrie1 libdconf1 libdv4 libepoxy0 libfdt1 libflac8 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common libgraphite2-3 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libgtk-3-0 libgtk-3-bin libgtk-3-common libgudev-1.0-0 libharfbuzz0b libibverbs1 libiec61883-0 libiscsi7 libjack-jackd2-0 libjson-glib-1.0-0 libjson-glib-1.0-common libmp3lame0 libmpg123-0 libncursesw5 libnl-route-3-200 libnspr4 libnss3 libogg0 libopus0 liborc-0.4-0 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpciaccess0 libpcsclite1 libpixman-1-0 libproxy1v5 libpulse0 librados2 libraw1394-11 librbd1 librdmacm1 librest-0.7-0 librsvg2-2 librsvg2-common libsamplerate0 libshout3 libsndfile1 libsoup-gnome2.4-1 libsoup2.4-1 libspeex1 libspice-server1 libtag1v5 libtag1v5-vanilla libthai-data libthai0 libtheora0 libtinfo5 libtwolame0 libusbredirparser1 libv4l-0 libv4lconvert0 libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvisual-0.4-0 libvorbis0a libvorbisenc2 libvpx5 libvte-2.91-0 libvte-2.91-common libwavpack1 libwayland-client0 libwayland-cursor0 libwayland-egl1 libxcb-render0 libxcb-shm0 libxcomposite1 libxcursor1 libxdamage1 libxen-4.9 libxenstore3.0 libxfixes3 libxi6 libxinerama1 libxkbcommon0 libxml2-utils libxrandr2 libxrender1 libxtst6 libxv1 msr-tools qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils seabios sharutils ubuntu-mono x11-common Suggested packages: ifupdown gvfs libasound2-plugins alsa-utils colord cups-common libdv-bin oss-compat libvisual-0.4-plugins gstreamer1.0-tools jackd2 opus-tools pcscd pulseaudio libraw1394-doc librsvg2-bin speex libvirt-daemon-driver-storage-gluster libvirt-daemon-driver-storage-sheepdog libvirt-daemon-driver-storage-zfs numad auditd nfs-common pm-utils radvd systemtap zfsutils samba vde2 sgabios ovmf debootstrap sharutils-doc bsd-mailx | mailx The following NEW packages will be installed: adwaita-icon-theme at-spi2-core bridge-utils cpu-checker dconf-gsettings-backend dconf-service fontconfig glib-networking glib-networking-common glib-networking-services gsettings-desktop-schemas gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-x gtk-update-icon-cache hicolor-icon-theme humanity-icon-theme ibverbs-providers ipxe-qemu ipxe-qemu-256k-compat-efi-roms libaa1 libaio1 libasound2 libasound2-data libasyncns0 libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatspi2.0-0 libavc1394-0 libbluetooth3 libbrlapi0.6 libcaca0 libcacard0 libcairo-gobject2 libcairo2 libcdparanoia0 libcolord2 libcroco3 libcups2 libdatrie1 libdconf1 libdv4 libepoxy0 libfdt1 libflac8 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common libgraphite2-3 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libgtk-3-0 libgtk-3-bin libgtk-3-common libgudev-1.0-0 libharfbuzz0b libibverbs1 libiec61883-0 libiscsi7 libjack-jackd2-0 libjson-glib-1.0-0 libjson-glib-1.0-common libmp3lame0 libmpg123-0 libncursesw5 libnl-route-3-200 libnspr4 libnss3 libogg0 libopus0 liborc-0.4-0 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpciaccess0 libpcsclite1 libpixman-1-0 libproxy1v5 libpulse0 librados2 libraw1394-11 librbd1 librdmacm1 librest-0.7-0 librsvg2-2 librsvg2-common libsamplerate0 libshout3 libsndfile1 libsoup-gnome2.4-1 libsoup2.4-1 libspeex1 libspice-server1 libtag1v5 libtag1v5-vanilla libthai-data libthai0 libtheora0 libtinfo5 libtwolame0 libusbredirparser1 libv4l-0 libv4lconvert0 libvirt-bin libvirt-daemon libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvisual-0.4-0 libvorbis0a libvorbisenc2 libvpx5 libvte-2.91-0 libvte-2.91-common libwavpack1 libwayland-client0 libwayland-cursor0
[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI
If anything, TBH it's unlikely to be shim /or/ grub; seeing as netbooting on hardware just works; but we should have a good look at shim and grub anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789319 Title: Unable to load shimx64.efi using iPXE over UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI
I can reproduce. This looks to be something in grub that shim doesn't appear to like. ** No longer affects: ipxe (Ubuntu) ** Package changed: shim-signed (Ubuntu) => grub2 (Ubuntu) ** Changed in: grub2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789319 Title: Unable to load shimx64.efi using iPXE over UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789319] Re: Unable to load shimx64.efi using iPXE over UEFI
So, what is the failure mode here? Just not finding the binaries? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789319 Title: Unable to load shimx64.efi using iPXE over UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1789319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789119] Re: conversion from netplan to ifupdown broken
At the end of the install you still have a file in /etc/netplan. Did you also remove that? That could definitely explain the delay, as the installer wrote config for you (with how you configured the interface in the installer), and that config will be attempted at boot. ** Changed in: netplan.io (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789119 Title: conversion from netplan to ifupdown broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1789119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789130] Re: netplan apply doesn't activate NetworkManager
** Changed in: netplan.io (Ubuntu) Status: New => Triaged ** Changed in: netplan.io (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789130 Title: netplan apply doesn't activate NetworkManager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1789130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788775] Re: updating grub can end up with loopback devices in grub.cfg
Well, we do use loop devices and do expect them to be listed for building the images. I'm not sure if there'll be a way to differentiate between the image build case and normal case to be able to pass some parameter (--skip-loopback, whatever) as appropriate. Let's look into that. ** Changed in: grub2 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788775 Title: updating grub can end up with loopback devices in grub.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466150] Re: grub-install breaks when ESP is on raid
All that patch would do is show a pretty error message earlier, not actually make sure the problem is fixed -- upgrades would still fail; installs would still fail on RAID. This has to do with grub not grokking the metadata format on disk, which is avoidable by using metadata 0.90. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466150 Title: grub-install breaks when ESP is on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1466150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /
@John, I've uploaded initramfs-tools with your patch to both cosmic and 18.04. Now, for the process of stable release updates [1]; we do need test cases and what is likely to break in case of a regression. I've added this to the best of my knowledge, but I don't have any systems with ZFS -- given that you have run into this issue, could you check and make sure at least my test cases correctly capture how to test that this fix works? Thanks. [1] https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Description changed: + [Impact] + Ubuntu users who have installed on ZFS devices. + + [Test case] + -- upgrade -- + 1) install 16.04 using ZFS as rootfs. + 2) upgrade to 18.04 + + -- initramfs update -- + 1) install Ubuntu, using ZFS as a rootfs. + 2) run "sudo update-initramfs -u" + + Without the patch, you should see a warning from mkinitramfs: + + mkinitramfs: failed to determine device for / + mkinitramfs: workaround is MODULES=most, check: + grep -r MODULES /etc/initramfs-tools/ + + With initramfs-tools patched, you should not see the warning, and + instead have additional kernel modules added to the initramfs that are + required to support the block devices that host the ZFS pools. + + --- + When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with root on ZFS I get this error: Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic mkinitramfs: failed to determine device for / mkinitramfs: workaround is MODULES=most, check: grep -r MODULES /etc/initramfs-tools/ Error please report bug on initramfs-tools Include the output of 'mount' and 'cat /proc/mounts' update-initramfs: failed for with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052. dpkg: error processing package linux-image-4.4.0-59-generic (--configure): - subprocess installed post-installation script returned error exit status 2 + subprocess installed post-installation script returned error exit status 2 version of initramfs-tools is 0.122ubuntu8.8 - Output of mount is: sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755) rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) debugfs on /sys/kernel/debug type debugfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) rpool/home on /home
[Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /
** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661629 Title: upgrade of kernel fails with mkinitramfs: failed to determine device for / To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1661629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664844] Re: No distinction between link-up and link-down interfaces
Repurposing this bug now to track the feature work for a specific activation mode option in netplan to keep interfaces administratively down (or manually configured) ** Changed in: nplan (Ubuntu) Status: Confirmed => In Progress ** Changed in: nplan (Ubuntu Xenial) Status: Fix Released => Fix Committed ** Changed in: nplan (Ubuntu Xenial) Status: Fix Committed => In Progress ** Changed in: nplan (Ubuntu Zesty) Status: Fix Released => In Progress ** Changed in: nplan (Ubuntu Artful) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664844 Title: No distinction between link-up and link-down interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781529] Re: [MIR] mecab
Let's get a code review for mecab by the security team. It parses data to re-encode... ** Changed in: mecab (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781529 Title: [MIR] mecab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mecab/+bug/1781529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781529] Re: [MIR] mecab
mecab-ipadic reviewed; it's basically only data in EUC-JP format, with an additional package that builds from that into UTF-8 format at install time. While that seems to be suboptimal to me, there's no particular objection. MIR approved for mecab-ipadic. ** Changed in: mecab-ipadic (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781529 Title: [MIR] mecab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mecab/+bug/1781529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781529] Re: [MIR] mecab
These packages appear to be missing a subscribing team, as is required for MIRs. Have you discussed including these packages in main with the server team? I've subscribed them to this bug to have their opinion on whether they are okay with the added effort of looking after mecab, mecab- ipadic, considering it could reduce the work on mysql packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781529 Title: [MIR] mecab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mecab/+bug/1781529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783707] Re: [MIR] sortedcontainers
This package is straightforward, appears to be well-maintained in Debian, and unlikely to require a significant maintenance effort in Ubuntu. Extensive tests are part of the build, and the code looks good. MIR approved. ** Changed in: sortedcontainers (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783707 Title: [MIR] sortedcontainers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sortedcontainers/+bug/1783707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783706] Re: [MIR] oath-toolkit
** Changed in: oath-toolkit (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team (ubuntu-security) ** Changed in: oath-toolkit (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783706 Title: [MIR] oath-toolkit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oath-toolkit/+bug/1783706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783706] Re: [MIR] oath-toolkit
This package does show some signs of age, and would probably really benefit (maintainability-wise) from having some cleanup/modernizing of the packaging, for instance to update debhelper usage, replace cdbs, etc. Assigning to the Security team since this includes a PAM module and is generally security-sensitive auth software. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783706 Title: [MIR] oath-toolkit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oath-toolkit/+bug/1783706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783706] Re: [MIR] oath-toolkit
** Changed in: oath-toolkit (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: oath-toolkit (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783706 Title: [MIR] oath-toolkit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oath-toolkit/+bug/1783706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783707] Re: [MIR] sortedcontainers
** Changed in: sortedcontainers (Ubuntu) Status: New => In Progress ** Changed in: sortedcontainers (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783707 Title: [MIR] sortedcontainers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sortedcontainers/+bug/1783707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'
We need to clarify whether the other bug really is a verification- failed. I don't think it actually fails, it's just an incomplete fix given that there's existing config that we can't easily change post- install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769682 Title: NFS-based remote root hangs when running 'netplan apply' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782578] Re: grub2 2.02-2ubuntu13 manual testing required
Manual testing done, both UEFI and legacy work. ** Changed in: grub2 (Ubuntu) Status: New => Fix Released ** Changed in: grub2-signed (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782578 Title: grub2 2.02-2ubuntu13 manual testing required To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1782578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716999] Re: installer creates rather small /boot partition
Already covered in ubiquity since artful. ubiquity upload in progress to address this on xenial. ** Changed in: ubiquity (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716999 Title: installer creates rather small /boot partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1716999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782578] [NEW] grub2 2.02-2ubuntu13 manual testing required
Public bug reported: cyphermox tested that grub2_2.02-2ubuntu13's reloc patch to grub-mkimage do generate a bootable image on UEFI. Needs a smoke-test to make sure we also have working legacy boot (grub- pc) images generated from grub-mkimage. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed ** Tags added: block-proposed ** Also affects: grub2-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782578 Title: grub2 2.02-2ubuntu13 manual testing required To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1782578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258597] Re: [Patch] Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
** Description changed: [Impact] All Ubuntu users. [Test case] Run 'sudo update-grub'. The message is shown at the beginning. [Regression potential] - Changes to the default config options may adversely impact boot behavior for the systems. Systems could start to always show the grub menu, or it may become hard to reach the menu when it was otherwise reachable due to the changes in timeout behavior. Any changes to the behavior of the boot menu timeout / default grub options should be looked at with suspicion. + There is a low risk of regression given that this change is essentially a no-op; changing two environment variables that are deprecated (and have been for a long while, pre-xenial), with a single, less confusing equivalent. That said, changes to the default config options may adversely impact boot behavior for systems. Systems could start to always show the grub menu, or it may become hard to reach the menu when it was otherwise reachable due to the changes in timeout behavior. Any changes to the behavior of the boot menu timeout / default grub options should be looked at with suspicion. --- When running update-grub I am getting the following message: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. $ sudo update-grub Generowanie grub.cfg... Uwaga: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Znaleziono obraz Linuksa: /boot/vmlinuz-3.12.0-6-generic Znaleziono obraz initrd: /boot/initrd.img-3.12.0-6-generic Found memtest86+ image: /boot/memtest86+.elf gotowe ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 3.12.0-6.14-generic 3.12.3 Uname: Linux 3.12.0-6-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 6 18:49:28 2013 InstallationDate: Installed on 2013-10-15 (51 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: grub2 UpgradeStatus: Upgraded to trusty on 2013-11-05 (31 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258597 Title: [Patch] Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1258597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258597] Re: [Patch] Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
** Description changed: + [Impact] + All Ubuntu users. + + [Test case] + Run 'sudo update-grub'. The message is shown at the beginning. + + [Regression potential] + Changes to the default config options may adversely impact boot behavior for the systems. Systems could start to always show the grub menu, or it may become hard to reach the menu when it was otherwise reachable due to the changes in timeout behavior. Any changes to the behavior of the boot menu timeout / default grub options should be looked at with suspicion. + + --- + When running update-grub I am getting the following message: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. $ sudo update-grub Generowanie grub.cfg... Uwaga: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. Znaleziono obraz Linuksa: /boot/vmlinuz-3.12.0-6-generic Znaleziono obraz initrd: /boot/initrd.img-3.12.0-6-generic Found memtest86+ image: /boot/memtest86+.elf gotowe ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 3.12.0-6.14-generic 3.12.3 Uname: Linux 3.12.0-6-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 6 18:49:28 2013 InstallationDate: Installed on 2013-10-15 (51 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pl_PL.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pl_PL.UTF-8 + SHELL=/bin/bash SourcePackage: grub2 UpgradeStatus: Upgraded to trusty on 2013-11-05 (31 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258597 Title: [Patch] Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1258597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781001] Re: DKMS seems to hang after installing a module.
** Description changed: + [Impact] + All users of third-party modules on Ubuntu. + + [Test cases] + 1) Install Ubuntu on an UEFI system + 2) Clear any files in /var/lib/shim-signed/mok: "sudo rm -rf /var/lib/shim-signed/mok/*" + 3) Install virtualbox-dkms: "sudo apt install virtualbox-dkms" + 4) Verify that you are prompted for a password to enroll a new MOK, and that you are asked that password at reboot. + + Without the patch, no prompt will appear at install of virtualbox-dkms. + + [Regression Potential] + + + (while gathering info for this bugreport, my knowledge about this issue has been growing. So the top part was written with not everything known yet) In my case I installed tp_smapi, but on the internet I've found others that have installed other modules. When configuring the tp-smapi-dkms package it says it will uninstall the module first and the it reports: Building initial module for 4.15.0-23-generic After that it hangs, or so it seems. It turns out that somewhere in there a script is being called with output redirected to /dev/null. But under certain circumstances, in my case "the computer is configured for secure boot", whiptail is being called asking for a password. Whiptail outputs curses codes to write stuff to the screen but that is redirected to /dev/null. It then waits for input from the user. I've debugged this to the point that it is saying this: whiptail --backtitle Package configuration --title Configuring Secure Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot enabled. UEFI Secure Boot requires additional configuration to work with third-party drivers. The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system's firmware. To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the "Enroll MOK" and "Change Secure Boot state" menus that will be presented to you when this system reboots. If you proceed but do not confirm the password upon reboot, Ubuntu will still be able to boot on your system but any hardware that requires third-party drivers to work correctly may not be usable. --scrolltext 20 77 but, as I said the output is redirected to /dev/null. The call-tree is as follows: -dpkg(18879)---tp-smapi-dkms.p(18880)---common.postinst(18881)---dkms(19146)---dkms(19161)---frontend(20224)-+-update-securebo(20238) | | `-whiptail(20253) (with the update-secureboot and whiptail both being children from "frontend". ). The tp-smapi-dkms.postinst program is still being called with stdout connected to my controlling terminal. The common.postinst has stdout connected ot /dev/null, so I'd first look in /var/lib/dpkg/info/tp-smapi-dkms.postinst I have looked there, and I don't see a reason why it would redirect the output of a subprocess to /dev/null. (the word does not occur in the short script.) Alternatively I'd think that maybe the subprocess /usr/lib/dkms/common.postinst would redirect its own stdout to /dev/null. On the other hand I found dkms build -m $NAME -v $VERSION -k $KERNEL $ARCH > /dev/null which explains the dkms subprocess running with output redirected to devnull, but not why the common.postinst runs with output redirected to devnull. Anyway. DKMS kernel module install postponed, apt inoperable until I can physically access the machine Should have been automatically added, but here goes: 1: Description:Ubuntu 18.04 LTS Release:18.04 2: dkms: 2.3-3ubuntu9.1 3: People (not just me) expect a simple apt-get install to not hang wihtout explaining why. 4: it hung without any explanation. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dpkg 1.19.0.5ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 10 16:54:20 2018 ExecutablePath: /usr/bin/dpkg InstallationDate: Installed on 2018-06-28 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: dpkg UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: [Impact] All users of third-party modules on Ubuntu. [Test cases] 1) Install Ubuntu on an UEFI system 2) Clear any files in /var/lib/shim-signed/mok: "sudo rm -rf /var/lib/shim-signed/mok/*" 3) Install virtualbox-dkms: "sudo apt install
[Bug 1771845] Re: grub-installer raid handling code missing nvme from sed filter
@Hans, Could you help verifying that this fix is working? I don't have access to any NVMe hardware. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771845 Title: grub-installer raid handling code missing nvme from sed filter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771704] Re: support for ipv4 link-local addressing
** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771704 Title: support for ipv4 link-local addressing To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1771704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716999] Re: installer creates rather small /boot partition
Verification done on xenial with partman-auto/134ubuntu1.3: Installed on a 320G disk with LVM (so that a boot partition gets created at all); /boot is generated with a size of 766MB. Obviously, exact size of the /boot partition will depend on the overall disk size, since the recipe depends on the proportions of the other partitions. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716999 Title: installer creates rather small /boot partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1716999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I've tested this on a system while testing the other SRU that goes with this upload (bug 1769682). I don't have any delays with the SRU installed, and see no lvmetad warnings. I do have an /etc/initramfs- tools/conf.d/resume file that points to my swap partition, but that doesn't seem to adversely affect the behavior at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716999] Re: installer creates rather small /boot partition
** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716999 Title: installer creates rather small /boot partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1716999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775097] Re: autopkgtests are still flaky
Verification-done on xenial: nplan/0.32~16.04.6: http://autopkgtest.ubuntu.com/packages/nplan lists the autopkgtest results on xenial. The tests that were flaky are now passing at first run (so no longer flaky), and are reproducible on the command-line. arm64, s390x are permanent failures for an entirely different reason: test bed failures, due to missing wireless tools/drivers (s390x doesn't have cfg80211, armhf doesn't have iw installed, armhf waiting for tests to complete). I feel this qualifies as validation passing. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775097 Title: autopkgtests are still flaky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1775097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780996] Re: Convert triggers to noawait
** Changed in: fusiondirectory (Ubuntu Xenial) Status: New => In Progress ** Changed in: fusiondirectory (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: fusiondirectory (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'
Verification-done for xenial with initramfs-tools/0.122ubuntu8.12: critical: true is correctly written into /run/netplan/$interface.yaml; which makes networkd not bring down the interface when restarting, which avoids crashing the system. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769682 Title: NFS-based remote root hangs when running 'netplan apply' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777474] Re: Netinstall ISO offers usage of HTTPS mirrors but lacks ca-certificates
Assigning to debian-installer for now -- this might be an issue where ca-certificates is missing (since it needs to be there before you go get it from an https mirror, hopefully). That said, is this issue reproducible using the standard iso image; the one available on http://cdimage.ubuntu.com/releases/bionic/release/ubuntu-18.04-server- amd64.iso ? ** Package changed: ubuntu => debian-installer (Ubuntu) ** Changed in: debian-installer (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777474 Title: Netinstall ISO offers usage of HTTPS mirrors but lacks ca-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1777474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258597] Re: [Patch] Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
** Changed in: grub2 (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258597 Title: [Patch] Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1258597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780996] Re: Convert triggers to noawait
** Changed in: fusiondirectory (Ubuntu) Status: New => In Progress ** Changed in: fusiondirectory (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780996] Re: Convert triggers to noawait
dovecot for cosmic and bionic already changed to noawait triggers by Debian maintainer. ** Changed in: dovecot (Ubuntu) Status: In Progress => Fix Released ** Changed in: dovecot (Ubuntu Bionic) Status: New => Fix Released ** Changed in: dovecot (Ubuntu Xenial) Status: New => In Progress ** Changed in: dovecot (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780996] Re: Convert triggers to noawait
** Changed in: dovecot (Ubuntu) Status: New => In Progress ** Changed in: dovecot (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780606] Re: NetworkManager not able to manage WWAN devices in 18.04 server
** Changed in: network-manager (Ubuntu) Status: New => Triaged ** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780606 Title: NetworkManager not able to manage WWAN devices in 18.04 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1780606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
I'd be a bit surprised if there really was a regression due to the change, we're more likely seeing something going down due to the DHCP server being slow to respond, possibly because it already responded before? What does the 'networkctl' command show immediately after boot? Let's continue debugging this on your own bug (1768827). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on boot To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716999] Re: installer creates rather small /boot partition
** Description changed: - The installer (in 16.04 and 17.10) creates a separate /boot partition, - when required, of only 487M. This ends up being rather small when you - using the following equation to estimate a minimal size allowing for - reasonable room for further growth. + [Impact] + All new installs of 16.04. + + [Test case] + 1) Install Ubuntu 16.04 on a system + 2) Validate that the size of the /boot partition is greater than or equal to 512MB; should be somewhere between 512MB and 1GB, close to 768MB. + + [Regression potential] + This may adversely affect installs on tiny disks, by taking up more space for the /boot partition than was previously taken, at the cost of / or /home. As such, failures to install due to insufficient space on a partition, or failure to partition a disk that was previously working should be investigated as possible regressions. + + --- + + + The installer (in 16.04 and 17.10) creates a separate /boot partition, when required, of only 487M. This ends up being rather small when you using the following equation to estimate a minimal size allowing for reasonable room for further growth. (2*(3*kernel + 4*plymouth-carrying initrd + bootloader)) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716999 Title: installer creates rather small /boot partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1716999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771845] Re: grub-installer raid handling code missing nvme from sed filter
** Description changed: + [Impact] + Installs on NVMe hardware, on RAID deployments (RAID made of NVMe devices). + + [Test case] + - Install Ubuntu on NVMe drives, configure the drives in RAID. + + [Regression potential] + Attention should be taken to the behavior of installs, especially on RAID arrays: given the changes to the device matching, failure to recognize some devices that should be part of the RAID array, or to see devices outside of the RAID array when they were not added to the array, should be investigated as potential regressions coming from this change. + + -- + It appears that Ubuntu patched grub-installer to handle raid arrays, duplicating some sed filters from earlier parts of the code. Debian probably added nvme to the earlier parts but the duplicate in the Ubuntu specific raid code did not get the same update. It needs the same update, and probably the whole raid handling part needs upstreamed to Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771845 Title: grub-installer raid handling code missing nvme from sed filter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716999] Re: installer creates rather small /boot partition
Why is this targetted to 18.04 too? It was fixed in artful, do we still need to further increase /boot size? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716999 Title: installer creates rather small /boot partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1716999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
** Description changed:
+ [Impact]
+ Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
+
+ [Test case]
+ - Write a new netplan YAML (adjusting for current system as necessary):
+ network:
+ version: 2
+ ethernets:
+ ens3:
+ dhcp4: true
+ match:
+ macaddress: 52:54:00:de:bd:f6
+ set-name: myif0
+
+ - Run 'netplan apply'
+ - Verify that the device is correctly renamed to 'myif0'.
+ - Reboot.
+ - Make sure the device is correctly renamed to 'myif0'.
+
+ [Regression potential]
+ Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
+
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed to
myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it also
works if I unbind the device and rebind it as netplan apply does. No
setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the device
will be called myiface3 and brought up fine with dhcp. However, instead
I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
The name has not been changed, and the device has not been brought up.
If I run netplan apply however, I see the following:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: myiface3: mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
valid_lft 3575sec preferred_lft 3575sec
inet6 fe80::5054:ff:fede:bdf6/64 scope link
valid_lft forever preferred_lft forever
So names are successfully changed with netplan apply.
This seems to be some udev-related timing or priority issue that I'm
still trying to hunt down.
This breaks some forms of migration in certain cloud environments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Title:
systemd-networkd not renaming devices on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775097] Re: autopkgtests are still flaky
** Description changed: + [Impact] + autopkgtests gating the netplan releases in the Ubuntu archive. + + [Test case] + Validate that the tests are passing; specifically test_eth_* and test_bond_resend_igmp. + + [Regression potential] + Given that this is limited to the test suite, there is only very limited chance of regression from this SRU. Specifically, this is meant to fix the test mentioned in test cases. New test failures should be investigated as potentially caused by this SRU. + + --- + Autopkgtests for netplan.io / nplan are still flaky, and tend to fail to run succesfully due to bad configuration rather than actually failing tests. Fix this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775097 Title: autopkgtests are still flaky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1775097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637180] Re: "The computer needs to restart" dialog constantly eats CPU
Verification-done on artful, using update-manager 1:17.10.15: Verified that the application does not take 100% CPU while waiting for input at the "computer needs restart" dialog; and the expected code changes are applied on the python modules on disk. Applying updates completed without issues. ** Tags removed: verification-needed verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637180 Title: "The computer needs to restart" dialog constantly eats CPU To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1637180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763830] Re: [MIR] gce-compute-image-packages
MIR approved. Please make sure to move the packaging source to someplace other than ~rbalint's own tree; it probably should be modifiable by others. ** Changed in: gce-compute-image-packages (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763830 Title: [MIR] gce-compute-image-packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1763830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575236] Re: adjust the s390x parts of the 16.04 install guide
** Changed in: installation-guide (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => (unassigned) ** Summary changed: - adjust the s390x parts of the 16.04 install guide + adjust the s390x parts of the install guide -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575236 Title: adjust the s390x parts of the install guide To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/installation-guide/+bug/1575236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
** Also affects: nplan (Ubuntu) Importance: Undecided Status: New ** Changed in: nplan (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on boot To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770579] Re: Failure to quote variable containing secureboot password (errors out with whitespace) package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package
Verification-done on bionic with shim-signed/1.34.9.1: update-secureboot-policy now properly accepts passwords with spaces, and passes them cleanly to mokutil. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770579 Title: Failure to quote variable containing secureboot password (errors out with whitespace) package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1770579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767091] Re: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 30
Verification-done on bionic with shim-signed/1.34.9.1: I checked that you can no longer backtrack in the GNOME debconf frontend from the "enable secure boot" question to cause the dialog to fail. Backtracking is no longer accepted, only allowed as part of the password handling steps. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767091 Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1767091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'
** Tags removed: verification-done-artful verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769682 Title: NFS-based remote root hangs when running 'netplan apply' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774131] Re: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed'
Verification-done with update-manager/1:18.04.11.2 on bionic: I verified that the restart CPU does not show 100% CPU usage, and it does show without crashing update-manager. AFAICT this is fixed correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774131 Title: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1774131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637180] Re: "The computer needs to restart" dialog constantly eats CPU
Verification-done with update-manager/1:18.04.11.2 on bionic: Verified that the restart CPU does not show 100% CPU usage, and it does show without crashing update-manager. AFAICT this is fixed correctly. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637180 Title: "The computer needs to restart" dialog constantly eats CPU To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1637180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776271] Re: Could not prepare Boot variable: No space left on device (package shim-signed 1.34.9+13-0ubuntu2 [origin: Ubuntu] failed to install/upgrade: Unterprozess installed shim-signed packag
Hi, Could you please run the following commands and report their full output? sudo efibootmgr -v sudo efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi (the backslashes there matter, we are building a path in EFI mode) Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776271 Title: Could not prepare Boot variable: No space left on device (package shim-signed 1.34.9+13-0ubuntu2 [origin: Ubuntu] failed to install/upgrade: Unterprozess installed shim-signed package post- installation script gab den Fehler-Ausgangsstatus 1 zurück) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1776271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776425] Re: could not install updates
Hi, Could you please run the following commands and report their full output? sudo efibootmgr -v sudo efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi (the backslashes there matter, we are building a path in EFI mode) Thanks! ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776425 Title: could not install updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1776425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774131] Re: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed'
Marking verification-done since it was verified as fixed in comments #10, #11. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774131 Title: update-manager crashed with AttributeError in resize_to_standard_width(): 'UpdateManager' object has no attribute 'signal_changed' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1774131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759056] Re: [Ubuntu18.04][Witherspoon DD2.2] netplan fails to configure network bridge interface (tg3/BCM5719)
ubuntu@AcerAspire:~$ sudo ethtool -i enp2s0 driver: tg3 version: 3.137 firmware-version: sb expansion-rom-version: bus-info: :02:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no I am unable to reproduce this with tg3 either. Could you please share the exact contents of the netplan YAML intended to configure the bridge, along with the contents of /run/systemd/networkd? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759056 Title: [Ubuntu18.04][Witherspoon DD2.2] netplan fails to configure network bridge interface (tg3/BCM5719) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1759056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775743] Re: [regression] Cosmic daily images 20180606-8 install but then never boot (stuck in grub).
What daily image are we talking about? How does "stuck in grub" present? Do you get thrown into a grub prompt, or do you just see nothing after the grub menu disappears? ** Changed in: grub2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775743 Title: [regression] Cosmic daily images 20180606-8 install but then never boot (stuck in grub). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1775743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759056] Re: [Ubuntu18.04][Witherspoon DD2.2] netplan fails to configure network bridge interface (tg3/BCM5719)
This issue was reported prior to 18.04 GA, using an older version of netplan.io. Have you tested the same with a newer version of netplan? It seems to work just fine here -- with two network interfaces connected to the system, I connect using ens6; then modify the netplan configuration to move the IP to a newly created bridge (added to the config -- not separately created from the command-line), then run 'sudo netplan apply'. The bridge interface is created and the IP is moved to it, and I do not lose connectivity. On reboot, the system comes up normally, and I have connectivity over br0. I see no reason for this to behave any differently on tg3, but I've managed to get access to a system with such an interface, so I'll test that as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759056 Title: [Ubuntu18.04][Witherspoon DD2.2] netplan fails to configure network bridge interface (tg3/BCM5719) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1759056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775710] Re: snap preseeding in xenial not working
Setting verification-done -- validation of the livecd-rootfs changes was done with 2.408.33 as per the previous comment. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775710 Title: snap preseeding in xenial not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1775710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767091] Re: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 30
** Description changed: + [Impact] + Any user of Secure Boot with DKMS modules having the GNOME debconf frontend enabled or other debconf frontends that are not Dialog or readline. + + [Test case] + 1) Delete /var/lib/shim-signed/mok/MOK.* if exists. + 2) Run 'sudo update-secureboot-policy --new-key' + 3) Run 'sudo update-secureboot-policy --enroll-key' + 4) When prompted to "enable Secure Boot", hit the Back button. + + With no patch applied, the dialog will fall into an invalid state and + error out, with the characteristic "return code 30" error as seen in the + bug report. + + With the patch applied, no Back button will be present -- the user + should not be allowed to back up out of the enrolment dialog except by + making the conscious decision to enable SecureBoot / enroll a MOK or + continue with no changes, as are the two options presented. + + [Regression Potential] + Issues to watch out for are any related to password handling (failure to get the password and continue out of the debconf prompts without error), failure to enroll keys, or being unable to use dkms modules after reboot and successful enrolment of the key. Any erroring out of the debconf prompts at install should be investigated as possible regressions from this SRU. + + --- + during partial update from 17.10 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shim-signed 1.34.9+13-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Apr 26 11:31:05 2018 DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-xenial-amd64-20160624-2 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 30 InstallationDate: Installed on 2018-03-26 (30 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MokSBStateRT: 6 0 0 0 1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: - dpkg 1.19.0.5ubuntu2 - apt 1.6.1 + dpkg 1.19.0.5ubuntu2 + apt 1.6.1 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 30 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767091 Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1767091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770579] Re: Failure to quote variable containing secureboot password (errors out with whitespace) package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package
** Description changed: - This happens when I tried to setup boot key during 18.04 upgrade. + [Impact] + Any user of third-party (dkms) modules with Secure Boot enabled, who uses a space in the mok password. + + [Test case] + 1) Delete /var/lib/shim-signed/mok/MOK.* if exists. + 2) Run 'sudo update-secureboot-policy --new-key' + 3) Run 'sudo update-secureboot-policy --enroll-key' + 4) When prompted, enter a password containing the space character. + + [Regression potential] + Issues to watch out for are any related to password handling (failure to get the password and continue out of the debconf prompts without error), failure to enroll keys, or being unable to use dkms modules after reboot and successful enrolment of the key. + + -- + + This happens when I tried to setup boot key during 18.04 upgrade. Exits with Error code 2 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shim-signed 1.34.9+13-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 9 20:01:47 2018 EFITables: - May 11 23:30:27 dheepan-tower kernel: efi: EFI v2.40 by American Megatrends - May 11 23:30:27 dheepan-tower kernel: efi: ESRT=0xbfed1d98 ACPI=0xbe576000 ACPI 2.0=0xbe576000 SMBIOS=0xbfed SMBIOS 3.0=0xbfecf000 MPS=0xfc9e0 - May 11 23:30:27 dheepan-tower kernel: secureboot: Secure boot disabled - May 11 23:30:27 dheepan-tower kernel: esrt: Reserving ESRT space from 0xbfed1d98 to 0xbfed1dd0. + May 11 23:30:27 dheepan-tower kernel: efi: EFI v2.40 by American Megatrends + May 11 23:30:27 dheepan-tower kernel: efi: ESRT=0xbfed1d98 ACPI=0xbe576000 ACPI 2.0=0xbe576000 SMBIOS=0xbfed SMBIOS 3.0=0xbfecf000 MPS=0xfc9e0 + May 11 23:30:27 dheepan-tower kernel: secureboot: Secure boot disabled + May 11 23:30:27 dheepan-tower kernel: esrt: Reserving ESRT space from 0xbfed1d98 to 0xbfed1dd0. ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2017-11-18 (173 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MokSBStateRT: 6 0 0 0 1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: - dpkg 1.19.0.5ubuntu2 - apt 1.6.1 + dpkg 1.19.0.5ubuntu2 + apt 1.6.1 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-05-09 (1 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770579 Title: Failure to quote variable containing secureboot password (errors out with whitespace) package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1770579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775768] Re: [MIR] dwz - new dependency of debhelper
MIR approved, please add the bug subscriber. ** Changed in: dwz (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775768 Title: [MIR] dwz - new dependency of debhelper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwz/+bug/1775768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770874] Re: [MIR] libgsf
- AIUI usually desktop-bugs should be subscribed -- has the team situation for which teams you guys are looking at the bugs for been clarified? - tests exists, and are "run" but all are skipped: please fix this to actually run the tests properly, or explain why they can only be skipped. As mentioned, libgsf was previous in main, so I see no other blockers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770874 Title: [MIR] libgsf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgsf/+bug/1770874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770146] Re: [MIR] libayatana-appindicator
Why does this require a MIR? It doesn't seem like there are any packages depending on it, in any flavour. Whether libappindicator FTBFS or not has no bearing on this. ** Changed in: libayatana-appindicator (Ubuntu) Status: New => Incomplete ** Changed in: libayatana-appindicator (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770146 Title: [MIR] libayatana-appindicator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libayatana-appindicator/+bug/1770146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750576] Re: [MIR] heat-dashboard
This is a complex javascript package, and there seems to be a heavy history of XSS issues with openstack dashboards. I'd be more confident if this was reviewed by the Security Team. They can optionally decide that I'm just being too paranoid ;) ** Changed in: heat-dashboard (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) ** Changed in: heat-dashboard (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750576 Title: [MIR] heat-dashboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heat-dashboard/+bug/1750576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660550] Re: [MIR] snapd in trusty
Setting this to Fix Committed. There has been feedback from the Security team, feedback was addressed, and it seems that in any case bundling of Go dependencies in trusty is more or less "unavoidable". MIR team ACK on promoting snapd to main in trusty. ** Changed in: snapd (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660550 Title: [MIR] snapd in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1660550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695899] Re: [MIR] python-scrypt, python-bcrypt
James, This hasn't been addressed yet (fixing BINDNOW and tests as per Tyler's comment in comment #4). Please fix ASAP. ** Changed in: python-scrypt (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695899 Title: [MIR] python-scrypt, python-bcrypt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-bcrypt/+bug/1695899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628289] Re: snapd should depend on squashfuse (for use in containers)
This MIR has been completed, but squashfuse is still not in main (and apparently not Depend-ed on by snapd). None of the referenced bugs mentions squashfuse, what is the status of this? ** Changed in: snapd (Ubuntu) Status: Confirmed => Incomplete ** Changed in: snappy Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628289 Title: snapd should depend on squashfuse (for use in containers) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1628289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621216] Re: [MIR] geoclue-2.0
Unsubscribing ~ubuntu-mir: the MIR for geoclue-2.0 and iio-sensor-prxoy are done, geoclue needs looking at (it's assigned, as per Steve's comment). The MIR team does not need any additional visibility on this since geoclue has already been demoted to universe. -- You received this bug notification because you are a member of Ubuntu Desktop, which is a bug assignee. https://bugs.launchpad.net/bugs/1621216 Title: [MIR] geoclue-2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue/+bug/1621216/+subscriptions -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
[Bug 1621216] Re: [MIR] geoclue-2.0
Unsubscribing ~ubuntu-mir: the MIR for geoclue-2.0 and iio-sensor-prxoy are done, geoclue needs looking at (it's assigned, as per Steve's comment). The MIR team does not need any additional visibility on this since geoclue has already been demoted to universe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621216 Title: [MIR] geoclue-2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue/+bug/1621216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572539] Re: [MIR] ubuntu-core-libs
This one is just pending promotion based on something "pulling it" in main -- probably should be in some "supported" seed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572539 Title: [MIR] ubuntu-core-libs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-core-meta/+bug/1572539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546953] Re: [MIR] py3dns (dependency of python-formencode)
Dependency on py3dns was dropped from python-formencode; as such, this MIR appears to no longer be needed. Closing as Invalid; please reopen or open a new MIR if py3dns should be in main for another reason. Thanks! ** Changed in: py3dns (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546953 Title: [MIR] py3dns (dependency of python-formencode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/py3dns/+bug/1546953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543754] Re: [MIR] barbican, python-pykmip
James, is there still interest in python-pykmip in main? This package had some issues identified that should be fixed prior to promotion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543754 Title: [MIR] barbican, python-pykmip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/barbican/+bug/1543754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488425] Re: [MIR] ubuntu-download-manager
Unsubscribing ~ubuntu-mir; this package was promoted, and later removed from the archive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488425 Title: [MIR] ubuntu-download-manager To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482765] Re: [MIR] neutron-vpnaas
This already has been reviewed and was in main in artful; if you need it back in main (and to stay there), you will also need to have something Depends on it, or have it listed in a seed. Setting back to Fix Committed -- no further review necessary. ** Changed in: neutron-vpnaas (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482765 Title: [MIR] neutron-vpnaas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron-vpnaas/+bug/1482765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518237] Re: [MIR] gmenuharness
Closing as Invalid, there appears to be nothing depending on it, and the request was made for build-dependencies (testing) of unity components. Please don't hesitate to reopen if this turns out to be needed by something else. ** Changed in: gmenuharness (Ubuntu) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518237 Title: [MIR] gmenuharness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gmenuharness/+bug/1518237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418999] Re: [MIR] libxml-xpath-perl
Closing as Invalid as this was open as a MIR for build-dependencies when such a process was still needed. If it turns out that libxml-xpath-perl becomes needed for a binary dep in main, please reopen (or file a new MIR) ** Changed in: libxml-xpath-perl (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418999 Title: [MIR] libxml-xpath-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml-xpath-perl/+bug/1418999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415160] Re: [MIR] angular.js
Closing as Fix Released, angular.js is already in main but the bug wasn't closed... ** Changed in: angular.js (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415160 Title: [MIR] angular.js To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/angular.js/+bug/1415160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
