5.7.22 (in Ubuntu 16.04) still supports the empty port value, so I don't think
the issue is really related to this.
The "empty value specified" message is basically a deprecation warning in 5.7,
but changed to error in 8.0
--
You received this bug notification because you are a member of Ubunt
** Also affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: vaultlocker
Status: In Progress => 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/178
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780842
Title:
packa
** Changed in: blueman (Debian)
Status: Unknown => 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/1780878
Title:
postinst fails in chroot, dbus reload trigger should be removed
T
OK I hacked in a test of:
cmd = [
'udevadm', 'trigger',
'--subsystem-match=block', '--action=add'
]
before the settle, and the by-uuid device does appear. I'm still not
sure why that does not happen automatically but that is a definite fix
we can apply in vaultlocker.
--
701 - 705 of 705 matches
Mail list logo