Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1038701: lightdm logs "lightdm[1166]: gkr-pam: unable to locate daemon control file" error on boot
435 views
Skip to first unread message
Yura
Jun 20, 2023, 5:50:05 AM6/20/23
to
Package: lightdm
Version: 1.26.0-8
Severity: minor
X-Debbugs-Cc: splashed_o...@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.
Nevertheless, the booting process succeeds.
The expectation is that such error shouldn't occur.
-- System Information:
Debian Release: 12.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
DE: Xfce
Versions of packages lightdm depends on:
ii adduser 3.134
ii dbus 1.14.6-1
ii debconf [debconf-2.0] 1.5.82
ii libaudit1 1:3.0.9-1
ii libc6 2.36-9
ii libgcrypt20 1.10.1-3
ii libglib2.0-0 2.74.6-2
ii libpam-systemd [logind] 252.6-1
ii libpam0g 1.5.2-6
ii libxcb1 1.15-1
ii libxdmcp6 1:1.1.2-3
ii lightdm-gtk-greeter [lightdm-greeter] 2.0.8-2+b1
ii lsb-base 11.6
ii sysvinit-utils [lsb-base] 3.06-4
Versions of packages lightdm recommends:
ii xserver-xorg 1:7.7+23
Versions of packages lightdm suggests:
ii accountsservice 22.08.8-6
ii upower 0.99.20-2
pn xserver-xephyr <none>
-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
[Seat:*]
greeter-hide-users=false
[XDMCPServer]
[VNCServer]
-- debconf information:
lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm
Version: 1.26.0-8
Severity: minor
X-Debbugs-Cc: splashed_o...@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.
Nevertheless, the booting process succeeds.
The expectation is that such error shouldn't occur.
-- System Information:
Debian Release: 12.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
DE: Xfce
Versions of packages lightdm depends on:
ii adduser 3.134
ii dbus 1.14.6-1
ii debconf [debconf-2.0] 1.5.82
ii libaudit1 1:3.0.9-1
ii libc6 2.36-9
ii libgcrypt20 1.10.1-3
ii libglib2.0-0 2.74.6-2
ii libpam-systemd [logind] 252.6-1
ii libpam0g 1.5.2-6
ii libxcb1 1.15-1
ii libxdmcp6 1:1.1.2-3
ii lightdm-gtk-greeter [lightdm-greeter] 2.0.8-2+b1
ii lsb-base 11.6
ii sysvinit-utils [lsb-base] 3.06-4
Versions of packages lightdm recommends:
ii xserver-xorg 1:7.7+23
Versions of packages lightdm suggests:
ii accountsservice 22.08.8-6
ii upower 0.99.20-2
pn xserver-xephyr <none>
-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
[Seat:*]
greeter-hide-users=false
[XDMCPServer]
[VNCServer]
-- debconf information:
lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm
Yves-Alexis Perez
Jun 20, 2023, 5:30:05 PM6/20/23
to
-----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" error message from lightdm, which indicates that
> there is some issue.
>
> Nevertheless, the booting process succeeds.
>
> The expectation is that such error shouldn't occur.
Hey,
this looks to be https://github.com/canonical/lightdm/issues/70 but there's
not definite conclusion in that issue. It looks like gnome-keyring is launched
for the lightdm user but lacks space to write some files. I don't think we
really need gnome-keyring as part of the lightdm session anyway so I don't
think it's really problematic, mostly cosmetic at that point.
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSGOMACgkQ3rYcyPpX
RFu2mwgAtSXk2CbNNaPObACSEhVIbL3uZYFPMDyHucZQ2vXYYp/occiOlAaf1rNF
efANrjxSFNngBuGrGvWyki5uGyw14GHKudSb4KJgg6qMbW4meCES4cvf/m6VP+p8
Is2Vbj6Dk4c3c0+JEZyWJD6Me9h6nMhu1g4RAyrxPo3K6kzbmcsWx2ZzAr3Yo686
NyrEy0jdBuea/C/eBh4q+fFNVB6BnXkwLBDYd0vHes/V3lfxAxG9Wv08L47B5elP
ixr2pfX0Bx6h4thaloj8C88PR2sDNgGM95CJHktxKxX7By8tEp8yIKQg7x/NnR6D
IoN3d/HUQFqbJYz+A8iiYKsgK9EsNw==
=6fHb
-----END PGP SIGNATURE-----
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" error message from lightdm, which indicates that
> there is some issue.
>
> Nevertheless, the booting process succeeds.
>
> The expectation is that such error shouldn't occur.
this looks to be https://github.com/canonical/lightdm/issues/70 but there's
not definite conclusion in that issue. It looks like gnome-keyring is launched
for the lightdm user but lacks space to write some files. I don't think we
really need gnome-keyring as part of the lightdm session anyway so I don't
think it's really problematic, mostly cosmetic at that point.
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSGOMACgkQ3rYcyPpX
RFu2mwgAtSXk2CbNNaPObACSEhVIbL3uZYFPMDyHucZQ2vXYYp/occiOlAaf1rNF
efANrjxSFNngBuGrGvWyki5uGyw14GHKudSb4KJgg6qMbW4meCES4cvf/m6VP+p8
Is2Vbj6Dk4c3c0+JEZyWJD6Me9h6nMhu1g4RAyrxPo3K6kzbmcsWx2ZzAr3Yo686
NyrEy0jdBuea/C/eBh4q+fFNVB6BnXkwLBDYd0vHes/V3lfxAxG9Wv08L47B5elP
ixr2pfX0Bx6h4thaloj8C88PR2sDNgGM95CJHktxKxX7By8tEp8yIKQg7x/NnR6D
IoN3d/HUQFqbJYz+A8iiYKsgK9EsNw==
=6fHb
-----END PGP SIGNATURE-----
splashed_o...@simplelogin.com
Jun 21, 2023, 3:40:04 AM6/21/23
to
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 managers will be developed, but for now we have to live with it. GDM is better suited for GNOME, SDDM for KDE and all more or less supported that is currently available for Xfce is Lightdm.
Best Regards,
Yura
------- Original Message -------
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 managers will be developed, but for now we have to live with it. GDM is better suited for GNOME, SDDM for KDE and all more or less supported that is currently available for Xfce is Lightdm.
Best Regards,
Yura
------- Original Message -------
On Wednesday, June 21st, 2023 at 00:23, Yves-Alexis Perez - corsac at debian.org <corsac_at_deb...@simplelogin.co> wrote:
> Hey,
>
> this looks to be https://github.com/canonical/lightdm/issues/70 but there's
> not definite conclusion in that issue. It looks like gnome-keyring is launched
> for the lightdm user but lacks space to write some files. I don't think we
> really need gnome-keyring as part of the lightdm session anyway so I don't
> think it's really problematic, mostly cosmetic at that point.
>
> Regards,
> --
> Yves-Alexis
> Hey,
>
> this looks to be https://github.com/canonical/lightdm/issues/70 but there's
> not definite conclusion in that issue. It looks like gnome-keyring is launched
> for the lightdm user but lacks space to write some files. I don't think we
> really need gnome-keyring as part of the lightdm session anyway so I don't
> think it's really problematic, mostly cosmetic at that point.
>
> Regards,
> --
0 new messages