Still hitting this bug on Trusty. chromium-browser
53.0.2785.143-0ubuntu0.14.04.1.1145.
Is there any way to temporarily disable CT for _all_ sites via corporate policy?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Yes, it seems like I just had a stale Chromium process running.
Everything is indeed fixed now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641380
Title:
chromium-browser: ERR_CERTIFICATE_TRANSPA
Happened to me too, and too after upgrade from 15.10 to 16.04. Since
we're using crypttab with the keyscript= option, we can't yet use
systemd, and it seems like the system affected can boot once in ~5 times
fine, suggesting there is indeed a race condition somewhere inside
upstart (?)
Despite was
Public bug reported:
Our company is using Ubuntu as our main OS now. Before we decided to switch to
16.04 (with systemd) we used keyscript= crypttab option to manage some of our
encrypted volumes.
Now with Systemd that's no longer possible and we're forced to use upstart,
which in itself contai
wrong package chosen
** Package changed: upstart (Ubuntu) => cryptsetup (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642955
Title:
cryptsetup does not support the 'keyscript' crypttab op
I have noticed that if the machine has been shut down uncleanly, then
the success rate of it getting to boot normally is nearly 100%. Must
have to do something with fsck delaying the startup sequence enough for
this bug not to trigger?
--
You received this bug notification because you are a membe
