Dev1 Galaxy Forum / Login hangs after upgrade to chimaera? Slim might be the cause!

Re: Login hangs after upgrade to chimaera? Slim might be the cause!

dummy@example.com (Geoff 42) — Thu, 21 Oct 2021 14:48:38 +0000

Reading the ps man page I discovered the command :-

ps -eo pid,user,start,args

which prints the start time for each process. I spotted that the 30s delay came between some power management daemons and the first user applications (Claws and Pale Moon). I went into :-

Preferences>LXQt settings>LXQt Configuration Centre
and selected the Session Settings.
In Basic settings I turned off Power Management and in
Autostart I turned off Power Manager.
On a reboot there was no delay.
I then turned these power management things back on and at a reboot there was still no delay.
I notice that I am running /usr/bin/xfce4-power-manager, which I don't remember being there before, as well as /usr/libexec/upowerd and /usr/bin/lxqt-powermanagement. I could not guaranty that the xfce one was not there before!

I will leave it as it is and see if the delay really has gone.

Re: Login hangs after upgrade to chimaera? Slim might be the cause!

dummy@example.com (Geoff 42) — Thu, 21 Oct 2021 08:05:36 +0000

I don't know that command! Anyway it reports :-

loginctl session-status
1 - user1 (1026)
           Since: Thu 2021-10-21 08:59:18 BST; 2min 0s ago
          Leader: 3182 (lxdm-session)
            Seat: seat0; vc7
             TTY: tty7
         Service: lxdm; type x11; class user
           State: active

I don't know if that is ok, but it looks sensible to me. (I have edited out my real username)

Geoff

Re: Login hangs after upgrade to chimaera? Slim might be the cause!

dummy@example.com (Head_on_a_Stick) — Wed, 20 Oct 2021 20:10:36 +0000

Is your login session okay?

loginctl session-status

Re: Login hangs after upgrade to chimaera? Slim might be the cause!

dummy@example.com (Geoff 42) — Wed, 20 Oct 2021 19:13:25 +0000

Thank you!

I have tried combinations of rngd and havged and neither.
I have also tried your suggestion with urandom :-

ls -alF /dev/*rand*
lrwxrwxrwx 1 root root    7 Oct 20 19:59 /dev/random -> urandom
crw-rw-rw- 1 root root 1, 9 Oct 20 19:59 /dev/urandom

None of which have any effect on my 30s delay. I may be experiencing a different problem from the OP as I should highlight that I am not using Slim but lxdm.

Re: Login hangs after upgrade to chimaera? Slim might be the cause!

dummy@example.com (Head_on_a_Stick) — Wed, 20 Oct 2021 18:39:42 +0000

Symlinking /dev/random to /dev/urandom is a better solution:

# /etc/udev/rules.d/00-random.rules
KERNEL=="urandom", PROGRAM+="/bin/rm -f /dev/random", SYMLINK+="random"

Reference: https://www.2uo.de/myths-about-urandom/

But the best solution is probably to switch from SLiM to a display manager that actually supports login sessions correctly.

Re: Login hangs after upgrade to chimaera? Slim might be the cause!

dummy@example.com (Geoff 42) — Wed, 20 Oct 2021 18:08:55 +0000

There is a thread on the mailing list :-

https://lists.dyne.org/lurker/message/2 … eb.en.html

where there is a report of a 30 second delay. This is thought to be related to the random number generator and that installing haveged can get rid of the delay.

Geoff

Re: Login hangs after upgrade to chimaera? Slim might be the cause!

dummy@example.com (Geoff 42) — Wed, 20 Oct 2021 08:40:59 +0000

I am also seeing a delay. However, I am running lxdm and XLQt.
The desktop seems to load ok, including lxqt-panel, but then it hangs for about 30 seconds.
If I look in ~/.xsession-errors, then I can see a gap in the time amongst the messages.

(redshift-gtk:5080): Gdk-CRITICAL **: 09:12:05.617: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

several other messages, including :-

Starting idlenesswatcher
"PowerButton" "" ""
"SuspendButton" "" ""
"HibenateButton" "" ""
[Notice] Started
[Notice] X11 error: type: 0, serial: 319, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 312
[Notice] X11 error: type: 0, serial: 321, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 312
[Notice] X11 error: type: 0, serial: 323, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 312
[Notice] X11 error: type: 0, serial: 325, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 312
[Warning] Cannot grab shortcut 'Alt+F2'
[Notice] X11 error: type: 0, serial: 683, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 312
[Notice] X11 error: type: 0, serial: 685, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 312
[Notice] X11 error: type: 0, serial: 687, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 312
[Notice] X11 error: type: 0, serial: 689, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 312
[Warning] Cannot grab shortcut 'Control+Alt+D'

and when I start Claws

(claws-mail:5166): GLib-GObject-CRITICAL **: 09:12:48.912: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

The part about idlenesswatcher caught my eye, but I have not yet been able to pin it down. The Cannot grab shortcut 'Control+Alt+D' was displaying before the upgrade, but did seem to come after a bit of a delay. I have not yet found where it is configured to set that as a shortcut.

Geoff

Login hangs after upgrade to chimaera? Slim might be the cause!

dummy@example.com (mstrohm) — Tue, 19 Oct 2021 19:01:48 +0000

Hello

After upgrading from Devuan GNU+Linux beowulf to chimaera, I had the problem that the login hang for 10 to 15 seconds before the desktop is being loaded. This also happened when I tried to login as another user from my X session using su in a shell.

This problem is somehow related to the Slim desktop manager and can be circumvented by using lightdm instead of Slim.
I'm writing this post just in case someone else has the same problem.

Regards
mstrohm