Hi,
Thanks for the response! Yes, it seems so. If I'm not mistaken, the problem was
also present for the entirety of the Bullseye lifecycle. I guess the conclusion
is that it's an upstream issue and nothing could be done to address it on the
Debian side. Maybe in the future better display
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: forwarded -1 https://github.com/canonical/lightdm/issues/70
On Tue, 2023-06-20 at 12:44 +0300, Yura wrote:
> Dear Maintainer,
>
> I've noticed that on boot system logs the "lightdm[1166]: gkr-pam: unable to
> locate daemon control file"
Package: lightdm
Version: 1.26.0-8
Severity: minor
X-Debbugs-Cc: splashed_overbuilt...@simplelogin.com
Dear Maintainer,
I've noticed that on boot system logs the "lightdm[1166]: gkr-pam: unable to
locate daemon control file" error message from lightdm, which indicates that
there is some issue.
3 matches
Mail list logo