Eu atualizei uma máquina para o Kubuntu 18.04 por uma reinstalação completa. Ainda temos gerenciamento de usuários usando o NFS / NIS. Pacotes são instalados, os usuários podem efetuar login. Eu tenho um usuário local dhlocal (userid: 1000) com o diretório home /localhome/dhlocal e usuários como dh (userid: 5000) com o diretório home /home/dh .
Eu posso logar em dhlocal para a sessão X / KDE e trabalhar lá sem nenhum problema - se apenas esse usuário estiver logado.
Se eu fizer login em dh , o sistema entrará em pausa por cerca de 20 segundos (independentemente de o login estar no console ou no X). Então, o KDE aparece. Após cerca de dois minutos, o sistema trava de repente. .xsession-errors no final é assim:
The session is not registered: "PID 11214 does not belong to any known session"
QObject::connect: No such signal
QDBusAbstractInterface::PrepareForSleep(bool)
powerdevil: Backend is ready, KDE Power Management system initialized
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-dh'
klauncher: Exiting on signal 15
ICE default IO error handler doing an exit(), pid = 11236, errno = 32
The X11 connection broke: I/O error (code 1)
XIO: fatal IO error 4 (Unterbrechung während des Betriebssystemaufrufs) on X server ":0"
after 37 requests (37 known processed) with 0 events remaining.
O mais estranho é: Se eu logar em dh em um console (ex. Ctrl-Alt-F2 e login) enquanto tiver dhlocal logado em X / KDE, a dhlocal session também falha após cerca de dois minutos. Isso acontece mesmo se eu fizer login novamente dhlocal no KDE, contanto que dh esteja logado em qualquer console. Mensagens em .xsession-errors de dhlocal :
The X11 connection broke (error 1). Did the X11 server die?
kdeinit5: sending SIGTERM to children.
kdeinit5: Exit.
klauncher: Exiting on signal 15
The X11 connection broke (error 1). Did the X11 server die?
The X11 connection broke: I/O error (code 1)
XIO: fatal IO error 2 (Datei oder Verzeichnis nicht gefunden) on X server ":0"
after 3523 requests (3523 known processed) with 0 events remaining.
klauncher: Exiting on signal 1
The X11 connection broke: I/O error (code 1)
XIO: fatal IO error 2 (Datei oder Verzeichnis nicht gefunden) on X server ":0"
after 1122 requests (1122 known processed) with 0 events remaining.
QProcess: Destroyed while process ("kwin_x11") is still running.
The X11 connection broke (error 1). Did the X11 server die?
Unexpected response from KInit (response = 0).
The X11 connection broke (error 1). Did the X11 server die?
startkde: Could not start ksmserver. Check your installation.
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
Error: Can't open display: :0
Could not connect to D-Bus server:
org.freedesktop.DBus.Error.NoServer:
Failed to connect to socket /tmp/dbus-V6z3BsURMt: Verbindungsaufbau
abgelehnt
startkde: Shutting down...
kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: :
No such file or directory
Error: Can not contact kdeinit5!
xprop: unable to open display ':0'
xprop: unable to open display ':0'
startkde: Done.
Eu removi o ambiente completo de dh e substituí a versão .profile / .bashrc pela dhlocal . Eu observo duas coisas com dh :
O login tem esse atraso de mais de 20 segundos, o que acontece mesmo antes de qualquer arquivo de inicialização do bash em $HOME ou /etc ser executado. Eu não sei de onde isso vem.
Por algum motivo, XDG_RUNTIME_DIR não está definido para dh . Outras variáveis de ambiente, no entanto, são. Mais uma vez .xsession-errors para dh :
Xsession: X session started for dh at Mo 30. Apr 17:06:17 CEST 2018
localuser:dh being added to access control list
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting LANG=de_DE.UTF-8
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting PAM_KWALLET5_LOGIN=/tmp/kwallet5_dh.socket
dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/plasma.mandatory.path
dbus-update-activation-environment: setting USER=dh
dbus-update-activation-environment: setting DESKTOP_SESSION=plasma
dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/plasma.default.path
dbus-update-activation-environment: setting PWD=/home/dh
dbus-update-activation-environment: setting HOME=/home/dh
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=KDE
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=KDE
dbus-update-activation-environment: setting GPG_AGENT_INFO=/home/dh/.gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting SHLVL=1
dbus-update-activation-environment: setting LOGNAME=dh
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-rMq6WSod2U,guid=9e31faa7d68efa98592ebb2b5ae730ea
dbus-update-activation-environment: setting PAM_KWALLET_LOGIN=/tmp/kwallet_dh.socket
dbus-update-activation-environment: setting XAUTHORITY=/home/dh/.Xauthority
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session3
dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment
O que está acontecendo aqui? Como posso consertar isso? Alguma informação adicional é necessária?