From 28f18359527d7cb4dbbcf593e6d6b9d9cbe0011a Mon Sep 17 00:00:00 2001 From: Konrad Bucheli Date: Thu, 18 Jul 2024 11:42:53 +0200 Subject: [PATCH] login errors --- admin-guide/troubleshooting/login.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/admin-guide/troubleshooting/login.md b/admin-guide/troubleshooting/login.md index 41fb8c25..29200752 100644 --- a/admin-guide/troubleshooting/login.md +++ b/admin-guide/troubleshooting/login.md @@ -18,12 +18,37 @@ because the PSI firewall only allows connections from a certain gateway, eg ## Known Errors +### Problematic `.bashrc`/`.bash_profile` +Some people load a pmodule or a conda environment when bash is started. This can easily break the Gnome Startup as this can bring in incompatible tools and libraries. Suspicous is also setting the `LD_LIBRARY_PATH` environment variable. Once even `PATH` was the culprit because an incompatible `kinit` was used after. + + ### pam_sss System Error ``` pam_sss(sshd:account): Access denied for user xxxxxx_y: 4 (System error) ``` Here the AD join might be broken. The machine can be rejoined by deleting/moving away `/etc/krb5.keytab` and then running Puppet (`puppet agent -t`). +### KioskWithKeyboard Error +``` +gnome-session[31143]: gnome-session-binary[31143]: dconf-WARNING: unable to open named profile (redhatkiosk): using the null configuration. +gnome-session-binary[31143]: dconf-WARNING: unable to open named profile (redhatkiosk): using the null configuration. +gnome-session[31143]: gnome-session-binary[31143]: WARNING: Unable to find required component 'com.redhat.KioskWithKeyboard.WindowManager' +gnome-session-binary[31143]: WARNING: Unable to find required component 'com.redhat.KioskWithKeyboard.WindowManager' +gnome-session[31143]: gnome-session-binary[31143]: WARNING: Unable to find required component 'com.redhat.Kiosk.Script' +gnome-session-binary[31143]: WARNING: Unable to find required component 'com.redhat.Kiosk.Script' +gnome-session-binary[31143]: Entering running state +gnome-session[31214]: Unable to init server: Could not connect: Connection refused +gnome-session-f[31214]: Cannot open display: +``` +For some reason the user got the first instead of the default desktop session. This can be fixed with + +``` +USER_WITH_BROKEN_LOGIN=... +systemctl stop accounts-daemon.service +rm /var/lib/AccountsService/users/$USER_WITH_BROKEN_LOGIN +systemctl start accounts-daemon.service +``` + ## Notes For normal users there will be a [`pam_access(8)`](https://linux.die.net/man/8/pam_access) error even for