[Bug 1868024] [NEW] Auto-size doesn't render correctly
Public bug reported: When running the following: $ dialog --infobox "Hello" 0 0 The resulting dialog does not render correctly - the outside borders don't match with the text. This worked in Ubuntu 16.04. Please note that this is tested inside Docker, but I believe it should still work correctly. ** Affects: dialog (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/1868024 Title: Auto-size doesn't render correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1868024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779760] Re: Aptly 1.2.0 tries to use incompatible GPG2
1.3.0 is available in Cosmic, but Bionic still has 1.2.0. Therefore, the bug is still not fixed in Bionic (which is a long-term support release.) What is the solution for people who use Bionic and would rather stick with LTS? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779760 Title: Aptly 1.2.0 tries to use incompatible GPG2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptly/+bug/1779760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779760] [NEW] Aptly 1.2.0 tries to use incompatible GPG2
Public bug reported: Because Ubuntu Bionic ships with GPG2 as "gpg", Aptly tries to use this instead of "gpg1". However, the command line options for GPG2 are different from GPG1, and Aptly hasn't yet been fully ported to GPG2. The only version they currently officially support is GPG1. In addition, Aptly's "internal" PGP implementation doesn't seem to properly support subkeys (which we are using), so that won't work for us as a workaround. This was fixed as of upstream pull request #734. It makes sure "gpg" is the correct version, and if not, it falls back to "gpg1". The simplest fix for this issue would be to backport these commits. ** Affects: aptly (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/1779760 Title: Aptly 1.2.0 tries to use incompatible GPG2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptly/+bug/1779760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox
Currently running 5.1.34-dfsg-0ubuntu1.16.04.2. This appears to have solved the host crash for me. I did have to manually update virtualbox- dkms too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736116 Title: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbuild/+bug/1736116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
