[Bug 1903920] Re: Warning message about cryptsetup during boot
The correct way to disable the warning seems to be to add RESUME=none to /etc/initramfs-tools/conf.d/resume if your swap has a /dev/urandom key. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903920 Title: Warning message about cryptsetup during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582318] Re: amavis virus check fails when nvidia CUDA is on the same system
Hi Christian, I actually agree. Mostly because of the points you raised, but maybe even on a 4th point. Most users use (and should use) a virtualized or container-ized environment, where in this case this bug also does not apply. I realized this a bit after I wrote the original comment. I still think, any "stable" distribution should be kinda... stable :) but I will agree, that pretty much nobody should have an amavisd + cuda drivers on one station (VM or bare-metal). Maybe a few private servers, but nothing serious. As for the new distribution; well sure it is fixed, but my question was for xenial. I do retract my opinion of a "high gain". I still consider it low risk, but without a warrant, it is probably not worth the risk. Thanks for your reply and opinion! Helge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582318 Title: amavis virus check fails when nvidia CUDA is on the same system To manage notifications about this bug go to: https://bugs.launchpad.net/amavisd-new/+bug/1582318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582318] Re: amavis virus check fails when nvidia CUDA is on the same system
Just encountered this bug on a xenial lts server. Isn't it supposed to be fixed there? If it's not should we open a SRU? It seems low risk and potentially high gain. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582318 Title: amavis virus check fails when nvidia CUDA is on the same system To manage notifications about this bug go to: https://bugs.launchpad.net/amavisd-new/+bug/1582318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634584] Re: package mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Description changed: - Probably relates to #1612517 + Probably relates to + https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1612517 Looks like mysql is not able to upgrade from 5.5 to 5.7 (trusty to xenial). I'm not sure from which version the config originates. After the option to send this report, I also saw this message in the terminal: - Setting up mysql-server-5.7 (5.7.15-0ubuntu0.16.04.1) ... Renaming removed key_buffer and myisam-recover options (if present) ERROR: Unable to start MySQL server: 2016-10-18T16:07:35.642062Z 0 [ERROR] unknown variable 'table_cache=256' 2016-10-18T16:07:35.648308Z 0 [ERROR] Aborting After removing the opposing statement from /etc/mysql/my.cnf (and starting apt-get -f install) the upgrade continued successfully (DB and tables upgraded and DB started) and the server restarted OK. JFYI ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 18 15:54:05 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 Logs.var.log.daemon.log: - - Logs.var.log.mysql.error.log: + + Logs.var.log.mysql.error.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf: - [mysqld_safe] - syslog + [mysqld_safe] + syslog MySQLConf.etc.mysql.conf.d.mysqldump.cnf: - [mysqldump] - quick - quote-names - max_allowed_packet = 16M + [mysqldump] + quick + quote-names + max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: - [mysqld_safe] - syslog + [mysqld_safe] + syslog MySQLVarLibDirListing: ['ibdata1', 'backup', 'mysql', 'ib_logfile0', 'phpmyadmin', 'mysql_upgrade_info', 'piwik', 'performance_schema', 'ib_logfile1', 'debian-5.5.flag', 'zabbix'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic root=UUID=4debcc35-8617-4fdb-a912-19421d092134 ro text RelatedPackageVersions: - dpkg 1.18.4ubuntu1.1 - apt 1.2.12~ubuntu16.04.1 + dpkg 1.18.4ubuntu1.1 + apt 1.2.12~ubuntu16.04.1 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-10-18 (0 days ago) ** Description changed: - Probably relates to - https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1612517 + Probably relates to LP: #1612517 Looks like mysql is not able to upgrade from 5.5 to 5.7 (trusty to xenial). I'm not sure from which version the config originates. After the option to send this report, I also saw this message in the terminal: Setting up mysql-server-5.7 (5.7.15-0ubuntu0.16.04.1) ... Renaming removed key_buffer and myisam-recover options (if present) ERROR: Unable to start MySQL server: 2016-10-18T16:07:35.642062Z 0 [ERROR] unknown variable 'table_cache=256' 2016-10-18T16:07:35.648308Z 0 [ERROR] Aborting After removing the opposing statement from /etc/mysql/my.cnf (and starting apt-get -f install) the upgrade continued successfully (DB and tables upgraded and DB started) and the server restarted OK. JFYI ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 18 15:54:05 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 Logs.var.log.daemon.log: Logs.var.log.mysql.error.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['ibdata1', 'backup', 'mysql', 'ib_logfile0', 'phpmyadmin', 'mysql_upgrade_info', 'piwik', 'performance_schema', 'ib_logfile1', 'debian-5.5.flag', 'zabbix'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic root=UUID=4debcc35-8617-4fdb-a912-19421d092134 ro text RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-10-18 (0 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/1634584 Title: package mysql-server-5.7
[Bug 1634584] [NEW] package mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Probably relates to #1612517 Looks like mysql is not able to upgrade from 5.5 to 5.7 (trusty to xenial). I'm not sure from which version the config originates. After the option to send this report, I also saw this message in the terminal: Setting up mysql-server-5.7 (5.7.15-0ubuntu0.16.04.1) ... Renaming removed key_buffer and myisam-recover options (if present) ERROR: Unable to start MySQL server: 2016-10-18T16:07:35.642062Z 0 [ERROR] unknown variable 'table_cache=256' 2016-10-18T16:07:35.648308Z 0 [ERROR] Aborting After removing the opposing statement from /etc/mysql/my.cnf (and starting apt-get -f install) the upgrade continued successfully (DB and tables upgraded and DB started) and the server restarted OK. JFYI ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 18 15:54:05 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 Logs.var.log.daemon.log: Logs.var.log.mysql.error.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['ibdata1', 'backup', 'mysql', 'ib_logfile0', 'phpmyadmin', 'mysql_upgrade_info', 'piwik', 'performance_schema', 'ib_logfile1', 'debian-5.5.flag', 'zabbix'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic root=UUID=4debcc35-8617-4fdb-a912-19421d092134 ro text RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-10-18 (0 days ago) ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634584 Title: package mysql-server-5.7 5.7.15-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1634584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505963] Re: extfs/uzip does not parse new 'unzip -v' format correctly
Package mc_4.7.0-1ubuntu1 from Lucid does not have this bug. It uses the new date format already. -- extfs/uzip does not parse new 'unzip -v' format correctly https://bugs.launchpad.net/bugs/505963 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
