[Bug 1903367] Re: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Quote: "it may be related to a kernel issue in this case or even hardware." I think this is a strong possibility. The system is hosted on an old Xen hypervisor (although, I've never had this problem before, updating other VMs from 18.04 to 20.04). Maybe it was a transient quirk. I still was able to finish the update successfully, nevertheless. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903367 Title: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1903367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903367] [NEW] package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Public bug reported: A simple 'do-release-upgrade' from 18.04 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lxd (not installed) ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Nov 7 00:36:31 2020 ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-22 (654 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: lxd Title: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-11-06 (0 days ago) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903367 Title: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1903367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687898] Re: unable to create drive c
** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687898 Title: unable to create drive c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1687898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687898] Re: unable to create drive c
WTF is this ?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687898 Title: unable to create drive c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1687898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention
In Debian 9 Stretch, works as it should. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628591 Title: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1305232] Re: Postfix fails to start, "failure to copy certificates"
Still hasn't made it in Xenial after 4 months... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1305232 Title: Postfix fails to start, "failure to copy certificates" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1305232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664390] Re: Trusty version (2:2.8.4-2) has not been bumped to address security vulnerabilities
The most convenient fix is to update the package to upstream v2.8.24. I've subscribed the MOTU Team. Please help us ! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664390 Title: Trusty version (2:2.8.4-2) has not been bumped to address security vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1664390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643063] Re: unable to ifup vlan based interface with systemd persistent naming
*** This bug is a duplicate of bug 1628591 *** https://bugs.launchpad.net/bugs/1628591 Check out my alternative workaround from duplicate bug #1628591. In my opinion, it's cleaner. I haven't heard of vconfig to be deprecated. Anyway... it's funny how we must do workarounds for basic functionality, such as networking. In Debian 9 Stretch, you don't have to do any of this. It works out-of- the-box with both "eth" and "enp" naming conventions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643063 Title: unable to ifup vlan based interface with systemd persistent naming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1643063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643063] Re: unable to ifup vlan based interface with systemd persistent naming
*** This bug is a duplicate of bug 1628591 *** https://bugs.launchpad.net/bugs/1628591 ** This bug has been marked a duplicate of bug 1628591 ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643063 Title: unable to ifup vlan based interface with systemd persistent naming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1643063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention
As a workaround, you could add "vlan-raw-device", like this: auto enp0s8 iface enp0s8 inet manual auto enp0s8.7 iface enp0s8.7 inet static vlan-raw-device enp0s8 address x.x.x.x/y It's a pity that such a project doesn't pay more attention to basic features... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628591 Title: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention
** Summary changed: - ifup and ifdown dont work for vlan devices when raw ethernet device name does not meet regular conventions + ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628591 Title: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664390] Re: Trusty version (2:2.8.4-2) has not been bumped to address security vulnerabilities
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664390 Title: Trusty version (2:2.8.4-2) has not been bumped to address security vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1664390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684298] Re: Security issues (solved in Debian) - affecting icu52 in trusty
Thank you, Janitor ! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684298 Title: Security issues (solved in Debian) - affecting icu52 in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445549] Re: systemctl start mysql.service starts mariadb but reports failure
This bug report is no longer valid, is it ? Can we close it ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445549 Title: systemctl start mysql.service starts mariadb but reports failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1445549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686160] Re: Security issues (solved in Debian) - affecting mysql-5.5.54 in Precise and Trusty
Thank you ! ** Changed in: mysql-5.5 (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/1686160 Title: Security issues (solved in Debian) - affecting mysql-5.5.54 in Precise and Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1686160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686160] [NEW] Security issues (solved in Debian) - affecting mysql-5.5.54 in Precise and Trusty
*** This bug is a security vulnerability *** Public security bug reported: Package: mysql-5.5 CVE ID : CVE-2017-3302 CVE-2017-3305 CVE-2017-3308 CVE-2017-3309 CVE-2017-3329 CVE-2017-3453 CVE-2017-3456 CVE-2017-3461 CVE-2017-3462 CVE-2017-3463 CVE-2017-3464 CVE-2017-3600 Debian Bug : 854713 860544 Several issues have been discovered in the MySQL database server. The vulnerabilities are addressed by upgrading MySQL to the new upstream version 5.5.55, which includes additional changes, such as performance improvements, bug fixes, new features, and possibly incompatible changes. Please see the MySQL 5.5 Release Notes and Oracle's Critical Patch Update advisory for further details: https://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-55.html http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html For the stable distribution (jessie), these problems have been fixed in version 5.5.55-0+deb8u1. ** Affects: mysql-5.5 (Ubuntu) Importance: Undecided Status: New ** Tags: mysql-5.5 precise security trusty ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3302 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3305 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3308 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3309 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3329 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3453 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3456 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3461 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3462 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3463 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3464 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3600 ** Information type changed from Public to Public Security ** Tags added: mysql-5.5 precise security trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686160 Title: Security issues (solved in Debian) - affecting mysql-5.5.54 in Precise and Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1686160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684274] Re: Security issues (solved in Debian) - affecting mariadb-server in xenial and yakkety
Thank you for your time and commitment on both projects (Debian and Ubuntu). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684274 Title: Security issues (solved in Debian) - affecting mariadb-server in xenial and yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1684274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684274] Re: Security issues (solved in Debian) - affecting mariadb-server in xenial and yakkety
** Summary changed: - Security issues -> new upstream release (incl. Debian) + Security issues (solved in Debian) - affecting mariadb-server in xenial and yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684274 Title: Security issues (solved in Debian) - affecting mariadb-server in xenial and yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1684274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684298] Re: Security issues (solved in Debian) - affecting icu52 in trusty
** Summary changed: - Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty + Security issues (solved in Debian) - affecting icu52 in trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684298 Title: Security issues (solved in Debian) - affecting icu52 in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684298] [NEW] Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty
*** This bug is a security vulnerability *** Public security bug reported: Date Reported: 19 Apr 2017 Security database references: In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International Components for Unicode library, did not correctly validate its input. An attacker could use this problem to trigger an out-of-bound write through a heap-based buffer overflow, thus causing a denial of service via application crash, or potential execution of arbitrary code. For the stable distribution (jessie), these problems have been fixed in version 52.1-8+deb8u5. ** Affects: icu (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Public Security ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-7867 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-7868 ** Description changed: Date Reported: 19 Apr 2017 Security database references: - In the Debian bugtracking system: Bug 860314. + In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International Components for Unicode library, did not correctly validate its input. An attacker could use this problem to trigger an out-of-bound write through a heap-based buffer overflow, thus causing a denial of service via application crash, or potential execution of arbitrary code. For the stable distribution (jessie), these problems have been fixed in version 52.1-8+deb8u5. ** Summary changed: - Security issues (solved in Debian) + Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684298 Title: Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684274] Re: Security issues -> new upstream release (incl. Debian)
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684274 Title: Security issues -> new upstream release (incl. Debian) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1684274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684274] [NEW] Security issues -> new upstream release (incl. Debian)
Public bug reported: Security database references: In Mitre's CVE dictionary: CVE-2017-3302, CVE-2017-3313. The vulnerabilities are addressed by upgrading MariaDB to the new upstream version 10.0.30. Please see the MariaDB 10.0 Release Notes for further details: https://mariadb.com/kb/en/mariadb/mariadb-10030-release-notes/ For the stable distribution (jessie), these problems have been fixed in version 10.0.30-0+deb8u1. ** Affects: mariadb-10.0 (Ubuntu) Importance: Undecided Status: New ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3302 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-3313 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684274 Title: Security issues -> new upstream release (incl. Debian) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1684274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612647] Re: myisam_ftdump is shipped by both mysql-client-5.7 and mariadb-server-10.0 which do not conflict, causing a dpkg error
** Changed in: mysql-5.7 (Ubuntu) Status: Triaged => In Progress ** Changed in: mysql-5.7 (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612647 Title: myisam_ftdump is shipped by both mysql-client-5.7 and mariadb- server-10.0 which do not conflict, causing a dpkg error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1612647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
