You are not logged in.

Pages: 1

#1 2020-08-18 13:54:27

phuturism
Member
From: Melbourne
Registered: 2016-07-15
Posts: 179

Lithium logout - delay displaying login fields again

1. On selecting "logout" through the exit dialogue, bl session is logged out (Lithium)
2. the usual lightdm wallpaper displays, but no login fields are visible
3.  No keystrokes I have tried display the fields
4. After around 90 seconds the screen blanks briefly (<1s) with cursor top left, then the lightdm login fields and wallpaper are displayed
5. can login normally at this point

Bug or feature?

Last edited by phuturism (2020-08-18 14:19:25)

Offline

#2 2020-08-18 16:25:33

JCN-9000
Member
From: Turin, Italy
Registered: 2016-04-22
Posts: 17

Re: Lithium logout - delay displaying login fields again

phuturism wrote:

Bug or feature?

Dunno but I checked and by me it's the same.

Switching to a VT I see a bunch of user processes still running, mostly children of this process: 

systemd --user

they remain active for 90 sec., then lightdm kiks in with its own systemd --user set of processes.
Shortly after my processes go away.

Not found a reason for this.

Offline

#3 2020-08-18 17:12:16

damo
....moderator....
Registered: 2015-08-20
Posts: 6,628

Re: Lithium logout - delay displaying login fields again

You can probably see what the holdup is with

sudo journalctl -b

EDIT: look for something like

A stop job is running for......(1min29sec)

Last edited by damo (2020-08-18 23:09:23)

Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#4 2020-08-19 05:18:33

ohnonot
...again
Registered: 2015-09-29
Posts: 5,487

Re: Lithium logout - delay displaying login fields again

JCN-9000 wrote:

I checked and by me it's the same.

Switching to a VT I see a bunch of user processes still running, mostly children of this process: 

systemd --user

they remain active for 90 sec., then lightdm kiks in with its own systemd --user set of processes.
Shortly after my processes go away.

Could you try this again please, only this time use

journalctl -f

It's like 'dmesg -w', it shows new entries as they happen (plus a few initial lines).

Give to COVAX! Here or here. (explanation)

Offline

#5 2020-08-19 05:19:24

phuturism
Member
From: Melbourne
Registered: 2016-07-15
Posts: 179

Re: Lithium logout - delay displaying login fields again

damo wrote:

You can probably see what the holdup is with

sudo journalctl -b

EDIT: look for something like

A stop job is running for......(1min29sec)

Dumb question, if I logout how can I view the journalctl processes?

Offline

#6 2020-08-19 06:11:26

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,051

Re: Lithium logout - delay displaying login fields again

phuturism wrote:

Dumb question, if I logout how can I view the journalctl processes?

To go to VT2 (Virtual terminal or tty), press and hold Ctrl and press F2.
There you can log in. Swtch back to graphical session with Ctrl + F7

// Regards rbh

Online

#7 2020-08-19 07:27:39

damo
....moderator....
Registered: 2015-08-20
Posts: 6,628

Re: Lithium logout - delay displaying login fields again

phuturism wrote:

Dumb question, if I logout how can I view the journalctl processes?

If you can log in again, the journal shows the activity from the current boot session.

Or if you have journal persistence enabled you can see the journals of previous boots.

Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#8 2020-08-20 04:24:25

phuturism
Member
From: Melbourne
Registered: 2016-07-15
Posts: 179

Re: Lithium logout - delay displaying login fields again

Here's the output of a logout/login event using journalctl -r so in reverse chronological order:

Aug 20 11:12:08 c7p40n0m1c0n systemd[5721]: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Aug 20 11:12:08 c7p40n0m1c0n systemd[1]: Starting User Manager for UID 108...
Aug 20 11:12:08 c7p40n0m1c0n systemd[1]: Started User Runtime Directory /run/user/108.
Aug 20 11:12:08 c7p40n0m1c0n systemd-logind[748]: New session c2 of user lightdm.
Aug 20 11:12:08 c7p40n0m1c0n systemd[1]: Starting User Runtime Directory /run/user/108...
Aug 20 11:12:08 c7p40n0m1c0n systemd[1]: Created slice User Slice of UID 108.
Aug 20 11:12:08 c7p40n0m1c0n lightdm[5717]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Aug 20 11:12:08 c7p40n0m1c0n lightdm[5717]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.Serv
Aug 20 11:12:07 c7p40n0m1c0n kernel: broken atomic modeset userspace detected, disabling atomic
Aug 20 11:12:07 c7p40n0m1c0n systemd-logind[748]: Removed session 2.
Aug 20 11:12:07 c7p40n0m1c0n systemd[1]: Stopped Session 2 of user anto.
Aug 20 11:12:07 c7p40n0m1c0n systemd[1]: session-2.scope: Failed with result 'timeout'.
Aug 20 11:12:07 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1181 (openbox) with signal SIGKILL.
Aug 20 11:12:07 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1138 (lightdm) with signal SIGKILL.
Aug 20 11:12:07 c7p40n0m1c0n systemd[1]: session-2.scope: Stopping timed out. Killing.
Aug 20 11:10:57 c7p40n0m1c0n systemd[1165]: pulseaudio.service: Succeeded.
Aug 20 11:10:57 c7p40n0m1c0n bluetoothd[1058]: Endpoint unregistered: sender=:1.60 path=/MediaEndpoint/A2DPSink
Aug 20 11:10:57 c7p40n0m1c0n bluetoothd[1058]: Endpoint unregistered: sender=:1.60 path=/MediaEndpoint/A2DPSource
Aug 20 11:10:37 c7p40n0m1c0n pkexec[5704]: anto: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/] [CO
Aug 20 11:10:37 c7p40n0m1c0n polkitd(authority=local)[796]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.33, objec
Aug 20 11:10:37 c7p40n0m1c0n systemd[1165]: run-user-1000-gvfs.mount: Succeeded.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: run-user-1000-gvfs.mount: Succeeded.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: Stopping Session 2 of user anto.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 5701 (loginctl) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 5700 (bash) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 5685 (jgmenu) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 5669 (pager) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 5668 (journalctl) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 5667 (sudo) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 5662 (bash) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 3195 (x-terminal-emul) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 3194 (sh) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1748 (gvfsd-trash) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1745 (gvfsd-metadata) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1739 (gvfs-afc-volume) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1734 (gvfs-mtp-volume) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1729 (gvfs-gphoto2-vo) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1724 (gvfs-goa-volume) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1719 (gvfs-udisks2-vo) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1611 (tint2) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n sudo[5667]: pam_unix(sudo:session): session closed for user root
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1606 (obexd) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1551 (xfce4-notifyd) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1547 (at-spi2-registr) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1541 (dconf-service) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1535 (xfce4-power-man) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1534 (dbus-daemon) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1518 (light-locker) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1515 (nm-applet) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1514 (agent) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1513 (blueman-applet) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1512 (at-spi-bus-laun) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1503 (xfconfd) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1501 (conky) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1489 (thunar) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1484 (clipit) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1483 (pnmixer) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1472 (ibus-engine-sim) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1470 (compton) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1465 (syndaemon) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1462 (xcape) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1460 (polkit-gnome-au) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1455 (xbindkeys) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1425 (ibus-portal) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1418 (ibus-x11) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1415 (ibus-extension-) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1412 (ibus-ui-gtk3) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1410 (ibus-dconf) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1408 (gvfsd-fuse) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1403 (gvfsd) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1395 (ibus-daemon) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1370 (ssh-agent) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1346 (dbus-daemon) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1339 (dbus-launch) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1181 (openbox) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1178 (gnome-keyring-d) with signal SIGTERM.
Aug 20 11:10:37 c7p40n0m1c0n obexd[1606]: Terminating
Aug 20 11:10:37 c7p40n0m1c0n systemd[1]: session-2.scope: Killing process 1138 (lightdm) with signal SIGTERM.
Aug 20 11:10:28 c7p40n0m1c0n sudo[5644]: pam_unix(sudo:session): session closed for user root
Aug 20 11:10:01 c7p40n0m1c0n CRON[5670]: pam_unix(cron:session): session closed for user anto

at 11:10:57 there is some stuff around bluetooth connections.

Then 11:12:07 SIGKILL around openbox/lightdm

Apart from this it's all Greek to me

Last edited by phuturism (2020-08-20 04:26:00)

Offline

#9 2020-08-20 07:49:27

damo
....moderator....
Registered: 2015-08-20
Posts: 6,628

Re: Lithium logout - delay displaying login fields again

Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.Serv

Do you have accountsservice package installed?

Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#10 2020-08-20 09:58:56

phuturism
Member
From: Melbourne
Registered: 2016-07-15
Posts: 179

Re: Lithium logout - delay displaying login fields again

damo wrote:
Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.Serv

Do you have accountsservice package installed?

No.  Installed, and that eliminated that error but 90 second delay on login fields becoming available persists.

Aug 20 16:54:36 c7p40n0m1c0n systemd-logind[763]: New session c4 of user lightdm.
Aug 20 16:54:36 c7p40n0m1c0n systemd[1]: Starting User Runtime Directory /run/user/108...
Aug 20 16:54:36 c7p40n0m1c0n systemd[1]: Created slice User Slice of UID 108.
Aug 20 16:54:36 c7p40n0m1c0n lightdm[3078]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Aug 20 16:54:35 c7p40n0m1c0n kernel: broken atomic modeset userspace detected, disabling atomic
Aug 20 16:54:35 c7p40n0m1c0n systemd-logind[763]: Removed session 9.
Aug 20 16:54:35 c7p40n0m1c0n systemd[1]: Stopped Session 9 of user anto.
Aug 20 16:54:35 c7p40n0m1c0n systemd[1]: session-9.scope: Failed with result 'timeout'.
Aug 20 16:54:35 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2094 (openbox) with signal SIGKILL.
Aug 20 16:54:35 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2085 (lightdm) with signal SIGKILL.
Aug 20 16:54:35 c7p40n0m1c0n systemd[1]: session-9.scope: Stopping timed out. Killing.
Aug 20 16:54:23 c7p40n0m1c0n ntpd[856]: 203.114.74.17 local addr 192.168.0.7 -> <null>
Aug 20 16:54:18 c7p40n0m1c0n ntpd[856]: 202.65.114.202 local addr 192.168.0.7 -> <null>
Aug 20 16:53:25 c7p40n0m1c0n systemd[1703]: pulseaudio.service: Succeeded.
Aug 20 16:53:25 c7p40n0m1c0n bluetoothd[1042]: Endpoint unregistered: sender=:1.151 path=/MediaEndpoint/A2DPSink
Aug 20 16:53:25 c7p40n0m1c0n bluetoothd[1042]: Endpoint unregistered: sender=:1.151 path=/MediaEndpoint/A2DPSource
Aug 20 16:53:05 c7p40n0m1c0n pkexec[3066]: anto: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/] [COMMAND=/usr/sbin/xfpm-power-backlight-helper --set-brigh
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: run-user-1000-gvfs.mount: Succeeded.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1703]: run-user-1000-gvfs.mount: Succeeded.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: Stopping Session 9 of user anto.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 3061 (loginctl) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 3060 (bash) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 3036 (tint2) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2852 (jgmenu) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2819 (gsimplecal) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2818 (sh) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2355 (obexd) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2323 (xfce4-notifyd) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2311 (at-spi2-registr) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2310 (xfce4-power-man) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2308 (dconf-service) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2298 (dbus-daemon) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2281 (light-locker) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2276 (nm-applet) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2275 (agent) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2274 (blueman-applet) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2273 (at-spi-bus-laun) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2272 (conky) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2269 (xfconfd) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2260 (thunar) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2253 (clipit) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2252 (pnmixer) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n polkitd(authority=local)[820]: Unregistered Authentication Agent for unix-session:9 (system bus name :1.125, object path /org/gnome/PolicyKit1/AuthenticationAgent, loca
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2241 (ibus-engine-sim) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2239 (compton) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2232 (xcape) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2231 (syndaemon) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2229 (polkit-gnome-au) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2223 (xbindkeys) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2200 (ibus-portal) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2197 (ibus-x11) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2193 (ibus-extension-) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2189 (ibus-ui-gtk3) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2185 (ibus-dconf) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2183 (gvfsd-fuse) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2176 (gvfsd) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2170 (ibus-daemon) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n obexd[2355]: Terminating
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2153 (ssh-agent) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2141 (dbus-daemon) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2140 (dbus-launch) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2094 (openbox) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2091 (gnome-keyring-d) with signal SIGTERM.
Aug 20 16:53:05 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2085 (lightdm) with signal SIGTERM.

Still seems to be the lightdm/openbox sessions that have to be SIGKILLed although I guess that's normal behaviour when the system decides it can't close whatever process is holding things up...

Aug 20 16:54:35 c7p40n0m1c0n systemd-logind[763]: Removed session 9.
Aug 20 16:54:35 c7p40n0m1c0n systemd[1]: Stopped Session 9 of user anto.
Aug 20 16:54:35 c7p40n0m1c0n systemd[1]: session-9.scope: Failed with result 'timeout'.
Aug 20 16:54:35 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2094 (openbox) with signal SIGKILL.
Aug 20 16:54:35 c7p40n0m1c0n systemd[1]: session-9.scope: Killing process 2085 (lightdm) with signal SIGKILL.
Aug 20 16:54:35 c7p40n0m1c0n systemd[1]: session-9.scope: Stopping timed out. Killing.

Last edited by phuturism (2020-08-20 10:05:15)

Offline

#11 2020-08-20 12:11:48

damo
....moderator....
Registered: 2015-08-20
Posts: 6,628

Re: Lithium logout - delay displaying login fields again

Look at the ntpd service just before the timeout. There are errors and a big delay there. You may have a problem with your network timeserver?

Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#12 2020-08-20 12:23:23

phuturism
Member
From: Melbourne
Registered: 2016-07-15
Posts: 179

Re: Lithium logout - delay displaying login fields again

OK, will go and find out about ntp service and why it's doing this...

Learning is fun


EDIT 

anto@c7p40n0m1c0n:~$ timedatectl
               Local time: Thu 2020-08-20 19:26:46 WIB
           Universal time: Thu 2020-08-20 12:26:46 UTC
                 RTC time: Thu 2020-08-20 12:26:46
                Time zone: Asia/Jakarta (WIB, +0700)
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: no

Have to go out but will explore this later

Last edited by phuturism (2020-08-20 12:26:21)

Offline

#13 2020-08-20 15:43:04

JCN-9000
Member
From: Turin, Italy
Registered: 2016-04-22
Posts: 17

Re: Lithium logout - delay displaying login fields again

Played with logout
Don't think is ntpd related.

Using

openbox --exit

logout is fast, no timeout, and login is readily available.
But some processes remain active and also the user session is listed as active.
Need some killing to cleanup

root@bl:~# loginctl list-sessions
SESSION UID USER    SEAT  TTY
    139   0 root    seat0 tty2
    146   0 root    seat0 tty3
    188 999 bladmin seat0          <------ user session 
    c15 108 lightdm seat0

4 sessions listed.
root@bl:~# ps -ef | grep bladmin
bladmin   239596       1  0 16:56 ?        00:00:00 /lib/systemd/systemd --user
bladmin   239598  239596  0 16:56 ?        00:00:00 (sd-pam)
bladmin   239634  239596  0 16:56 ?        00:00:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
bladmin   239705  239596  0 16:56 ?        00:00:00 /usr/libexec/gvfsd
bladmin   239728  239596  0 16:56 ?        00:00:00 /usr/libexec/at-spi-bus-launcher
bladmin   239733  239728  0 16:56 ?        00:00:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
bladmin   239801  239596  0 16:56 ?        00:00:00 /usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd
bladmin   239805       1  0 16:56 ?        00:00:00 clight
bladmin   239808       1  0 16:56 ?        00:00:00 /usr/bin/python3 /usr/share/system-config-printer/applet.py
bladmin   239840  239596  0 16:56 ?        00:00:00 /usr/libexec/dconf-service
bladmin   239871  239596  0 16:56 ?        00:00:00 /usr/lib/bluetooth/obexd
root      240003  234022  0 16:56 tty3     00:00:00 grep bladmin
root@bl:~# killall -u bladmin
root@bl:~# ps -ef | grep bladmin
bladmin   239596       1  0 16:56 ?        00:00:00 /lib/systemd/systemd --user
bladmin   239634  239596  0 16:56 ?        00:00:00 [dbus-daemon] <defunct>
bladmin   239705  239596  0 16:56 ?        00:00:00 [gvfsd] <defunct>
bladmin   239728  239596  0 16:56 ?        00:00:00 [at-spi-bus-laun] <defunct>
bladmin   239733  239596  0 16:56 ?        00:00:00 [dbus-daemon] <defunct>
bladmin   239801  239596  0 16:56 ?        00:00:00 [xfconfd] <defunct>
bladmin   239840  239596  0 16:56 ?        00:00:00 [dconf-service] <defunct>
bladmin   239871  239596  0 16:56 ?        00:00:00 [obexd] <defunct>
root      240032  234022  0 16:57 tty3     00:00:00 grep bladmin
root@bl:~# killall -s 9  -u bladmin
root@bl:~# ps -ef | grep bladmin
root      240037  234022  0 16:57 tty3     00:00:00 grep bladmin

This shows the Timeout setting for systemd:

# systemctl show --no-pager --property KillMode --property SendSIGKILL --property SendSIGHUP --property KillSignal --property TimeoutStopUSec test-base
TimeoutStopUSec=1min 30s
KillMode=control-group
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no

journalctl logs look quite like OP's

Last edited by JCN-9000 (2020-08-20 15:45:21)

Offline

#14 2020-08-21 05:30:56

phuturism
Member
From: Melbourne
Registered: 2016-07-15
Posts: 179

Re: Lithium logout - delay displaying login fields again

yes, openbox --exit gives me the login screen very quickly.

Offline

Pages: 1

Board footer

Powered by FluxBB