There were a couple dozen bug reports for Monday 8th Feb. Most were
already in process, the ones listed below took some attention. Only
this first one is worth some discussion:
LP: #1914894 [mysql-8.0] "mysql-server failed to install/upgrade: can't create
lock file /var/run/mysqld/mysqlx.sock.lock"
- We've been getting a number of these with same error in logs. I
went through our open mysql bugs and duped all matching ones
together into one Christian had done some analysis on a while back.
- Not seeing reports of this issue beyond Ubuntu, and so suspect it
might be something apparmor related (esp. since there have been
similar issues in the past that were due to apparmor).
- Only thought is that in .etc.apparmor.d.usr.sbin.mysqld.txt we have
rules for mysqld.{pid,sock,sock.lock} but only for
mysqlx.{sock,sock.lock} and I wonder if we also need to add a rule
for mysqlx.pid?
- In any case, we really need to have a way to reproduce the bug
ourselves in order to make progress...
LP: #1914865 [tidy-html5] `tidy -utf` treated as `tidy -u -t -f` instead of as
`tidy -utf8`, with no error
- Reproduced issue, analyzed root cause
--> Forwarded bug upstream
LP: #1914883 [qemu] hart0: trap handler failed (error -2) (Needs cherry-pick
ab3d207f)
- Patch on a plate.
--> Tagged for server-next; Christian's on it
LP: #1914939 [libseccomp] faccessat2 syscall needed for Docker
- There's already a bug tracking backport, this is essentially a dupe
--> Incomplete
LP: #1914875 [sssd] installed libpam-sss:amd64 package post-installation script
subprocess returned error
- Bug in debconf code
--> retargetted to debconf
LP: #1902122 [sssd] Cannot install libnss-sss:amd64 2.2.3-3 due to
/etc/nsswitch.conf
- The code seems to check for /etc/nsswitch.conf properly before
trying to modify it, so is unclear why it fails. Could not
reproduce it. Posed some questions for the reporter.
--> Incomplete
--
ubuntu-server mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
