No I was wrong.
In my case this only happens with the certificate with a strange Issuer name
like
"x00d\x00b\x00_\x00M\x00a\x00n\x00u\x00f\x00a\x00c\x00t\x00u\x00r\x00e\x002\x000\x001\x005\x000\x006\x001\x007".
Only this certificate fails to load.
--
You received this bug notification because
Hi Andreas,
I'm not using autofs, frankly, I chimed in here just to add that sssd package
had been explicitly pulled and installed during the update to groovy. And that
it failed to start for reasons unknown, too.
I didn't feel like tinkering with the problem, and given that I don't need sssd
in
Hi, I had no intention to use sssd, it was pulled and installed during the
update. I am sure I had no sssd installed on focal as I am browsing now through
the image of my root partition created before the update was started.
Yes, I still have update logs.
--
You received this bug notification b
This bug "affects" me too. In a way that sssd fails to start. Also any attempt
to run something like "systemctl enable foo.service" is now being rejected
after entering correct password in pkexec popup window, so I have to use "sudo
systemctl enable foo.service". Log show sssd.service and its "s
I'm here to just confirm the bug and that your workaround is working.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889416
Title:
pulseaudio.service: Start request repeated too quickly.
To
This happens when `mokutil --use-db` setting is applied. With `--ignore-
db` this doesn't happen. I suppose this is only applicable for
situaltions where Secure Boot's db / KEK / PK are modified by the user.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
>> status: Confirmed → Fix Released
Any hint where can I find relevant patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798363
Title:
i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete
** Summary changed:
- iThe installer ignores deliberately selected /boot/efi partition
+ The installer ignores deliberately selected /boot/efi partition
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Description changed:
I've noticed that Ubuntu installer ignores explicitly selected /boot/efi
partition. I have 2 ssd drives: the first one is nvme (/dev/nvme0n1) the second
one is sata (/dev/sda), both have their EFI partitions for multiboot purposes.
During the installation process the i
Public bug reported:
I've noticed that Ubuntu installer ignores explicitly selected /boot/efi
partition. I have 2 ssd drives: the first one is nvme (/dev/nvme0n1) the second
one is sata (/dev/sda), both have their EFI partitions for multiboot purposes.
During the installation process the instal
This bug hasn't been fixed yet?! I was very surprised to face it during
testing one of Saucy's dailies a week ago. It is ridiculous to recompile
kernel each time one receives update because of one incorrect value.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
11 matches
Mail list logo
