Dev1 Galaxy Forum / takes 23 seconds to login or "su" [recent change]

Re: takes 23 seconds to login or "su" [recent change]

dummy@example.com (jacksprat) — Sun, 06 Oct 2024 19:11:52 +0000

Thanks @stopAI, good to know. Dbus always seems to get dragged in by Firefox, and I suspect bits will fail if I try to get rid of it.

Re: takes 23 seconds to login or "su" [recent change]

dummy@example.com (stopAI) — Tue, 01 Oct 2024 13:43:45 +0000

Hello.

Please check Devuan 5 release notes

Here is an excerpt that I think will be important to you:

xserver-xorg-core now uses libseat1 to control rootless startx and access to
input and video devices. This has several advantages, the most significant being
that it removes the dbus dependency from xserver-xorg-core.
libseat1 can use either seatd or elogind as a
backend. If you need to override the default choice (autodiscovery), use the
LIBSEAT_BACKEND environment variable.
If you are using seatd as the backend, ensure the user is a member of the video group.
This is only relevant to running startx as a user, xorg run as root by a display
manager is unaffected.

Re: takes 23 seconds to login or "su" [recent change]

dummy@example.com (jacksprat) — Sun, 29 Sep 2024 13:15:38 +0000

@sg1: thanks, but same happened for a new user.

added: I had previously removed elogind [by moving links in /etc/runit], and forgot. That solves 23s waits, but if I try to remove the elogind packages, it wants to replace it with consolekit. Why do I need that?

Re: takes 23 seconds to login or "su" [recent change]

dummy@example.com (stargate-sg1-cheyenne-mtn) — Sun, 29 Sep 2024 10:20:33 +0000

perhaps adding a new user and checking for the delays there might yield insight?

takes 23 seconds to login or "su" [recent change]

dummy@example.com (jacksprat) — Sun, 29 Sep 2024 09:06:24 +0000

Recently, my Devuan laptop started to take a LONG time to login from console, and "su" took a similar time [23 seconds]. To investigate, I removed my .bashrc and the equivalent in /etc, but no good. Does anyone know what can cause this behaviour or hint at further tests I can perform find out what is happening? Thanks.