[Bug 1917748] [NEW] datehook functions missing in Secure Boot mode
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 Package: grub-efi-amd64-signed 1.142.11+2.04-1ubuntu26.9 datehook.mod provides variables such as $HOUR, $DAY - we use these to control the boot options on a large number of classroom PCs. This module is not included in the signed grub binary, so when Secure Boot is enabled on the PC, our custom grub config no longer works. Can you include datehook.mod in future releases please? ** Affects: grub2 (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/1917748 Title: datehook functions missing in Secure Boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1917748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741934] Re: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix)
Tested 4.4.0-108.131~lp1741934 in a Ubuntu Xenial install on the following: Asus CS-B - booted OK Asus Q170M-C - booted OK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741934 Title: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741934] Re: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix)
Tested 4.4.0-108.131~lp1741934 in a Ubuntu Xenial install on the following: Intel DQ77MK - booted OK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741934 Title: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741934] Re: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix)
Tested 4.4.0-108.131 on PCs with the following motherboards: Asus CS-B - failed to boot Intel DQ77MK - failed to boot Asus Q170M-C - booted OK I'll retry with the kernel from #24 now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741934 Title: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
Follow-up to #34, on a system where unattended-upgrades happens to be running when shutdown is called, the shutdown does not wait, therefore any running dpkg is killed and the package left in an inconsistent state. - Xenial with single partition, InstallOnShutdown not defined. This may be a separate issue, but I'll investigate further before raising it as such. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
The Unit file in #33 works for me, ie stops the 10 minute hang, when unattended-upgrades is not running. - Xenial with /var as a separate FS, InstallOnShutdown="false" I will try to create a test case where unattended-upgrades is running when shutdown is called. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620358] [NEW] System-wide monitors.xml is ignored
Public bug reported: Using gnome-settings-daemon 3.18.2-0ubuntu3.1 on Ubuntu 16.04.1 LTS Logging in with a new user account, my two monitors are the wrong way round. I can fix for this user by right-click; run "Display Settings" and manually reconfiguring. This creates ~/.config/monitors.xml I now copy that file to /etc/gnome-settings-daemon/xrandr/monitors.xml - I expect this to apply to all other users on this PC: $ gsettings get org.gnome.settings-daemon.plugins.xrandr default-configuration-file '/etc/gnome-settings-daemon/xrandr/monitors.xml' When other users log in, they still get the incorrect display setup. It looks like /etc/gnome-settings-daemon/xrandr/monitors.xml is having no effect. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Attachment added: "monitors.xml" https://bugs.launchpad.net/bugs/1620358/+attachment/4734979/+files/monitors.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620358 Title: System-wide monitors.xml is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1620358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554848] Re: Please randomise automatic updates over a longer period
My apologies - this delay is already configurable using APT::Periodic::RandomSleep ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554848 Title: Please randomise automatic updates over a longer period To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554848] Re: Please randomise automatic updates over a longer period
It would be good to have the delay length as a configuration option, I would like to reduce the random delay for some of my PCs which are not turned on very often. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554848 Title: Please randomise automatic updates over a longer period To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
