On Sun, Nov 06, 2016 at 08:22:25AM -0000, QkiZ wrote: > Additionally when this update is performed shim-signed is uninstalled > (dependency not met). After manual changing package version requirements > in shim-signed package to met shim package dependency and install > modified shim-signed package system still not boot in secureboot. That > means the problem is in one of new version of these packages:
No, all of those packages are correct. But you should not have been installing any of them; to install these, you must have had yakkety-proposed enabled, which is not a safe target for dist-upgrading to. On Sun, Nov 06, 2016 at 10:32:02AM -0000, QkiZ wrote: > new version of shim-signed was released 3h ago. It would be better to > release all changes related to same topic (secureboot for this example) > in same time. They *are* released at the same time. And none of these packages have been released yet: they are all still staged in yakkety-proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639546 Title: Problem with sigature verification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1639546/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
