On 05/05/2023 20:04, zithro wrote:
journalctl after GUI LOGOFF
I do not see obvious problems. What might be inspected more closely:
May 05 14:09:14 debzit systemd[711]: Stopping D-Bus User Message Bus...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If it is the bus shared with ssh connection than it may be an issue,
however it is for systemd unit, real process may be running independently.
Perhaps there is a specific command, but at leas you may compare
env | grep -i bus
from ssh and from GUI sessions. Output may be like
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
May 05 14:09:14 debzit gvfsd[14302]: A connection to the bus can't be made
May 05 14:09:14 debzit systemd[711]: xdg-permission-store.service: Main
process exited, code=exited, status=1/FAILURE
...
May 05 14:09:14 debzit systemd[711]: Stopped D-Bus User Message Bus.
May 05 14:09:14 debzit systemd[711]: Started D-Bus User Message Bus.
Why it started again from the same systemd user session if it is logout?
I would compare with logout messages when there are no ssh connections.
May 05 14:09:14 debzit sshd[14246]: Received disconnect from IP.IP.IP.IP
port 38524:11: disconnected by user
May 05 14:09:14 debzit sshd[14246]: Disconnected from user zithro
IP.IP.IP.IP port 38524
ssh client kicked off immediately after d-bus restart. Higher time
resolution may be requested by
journalctl -o short-iso-precise
May 05 14:09:14 debzit sshd[14239]: pam_unix(sshd:session): session
closed for user zithro
May 05 14:09:14 debzit systemd[711]: at-spi-dbus-bus.service: Succeeded.
May 05 14:09:14 debzit lightdm[23289]: pam_unix(lightdm:session):
session closed for user zithro
Likely it is completion of closing PAM lightdm session. I do not
remember if it is possible to increase PAM verbosity to get a log entry
when PAM close session are called. However systemd may perform actions
in parallel, so attributions of log entries to specific actions may be
ambiguous.