Gnome takes too long to present unlock screen once its locked [Solved]

Discussion in general that pertains to Sabayon Linux - Must Pertain to Sabayon Linux

Moderator: Moderators

Post Reply
mhzuchini
Simple Hen
Posts: 73
Joined: Mon Aug 20, 2007 18:46
Location: Campinas, Brazil

Gnome takes too long to present unlock screen once its locked [Solved]

Post by mhzuchini » Wed Jun 26, 2019 13:05

Hello, All.

I apologize if the case I'll describe is not a problem at all, but is seems odd to me.

I did a full update a week ago on my notebook. Before that, everything works fine, particularly locking an open Gnome session, put it to sleep by closing it and everything else works fine.

Since then, however, closing the lid no longer put the notebook into sleep and, what is more annoying, after I lock an open session and try to login again (i.e., unlock the session), it takes 13 to 15 seconds to give me back the login screen.

How to repeat:
1) Start notebook normally and login also normally. Noticeably, if one tries to open Gnome "Settings", it'll take up to 10 seconds to show the settings window. Everything else appears to work normally;
2) Lock the session (by pressing (WIN + L) or (ALT - clicking shutdown button)). It locks immediately;
3) In order to unlock, one have to click anywhere with the mouse, click any key or touchscreen. Then, the machine becomes unresponsive and takes 13 to 15 in order to present the login/unlock screen.

I did some research but found nothing directly relevant. Searching the logs, however, I've found a lot of messages like these:

Code: Select all

[email protected] ~ $ journalctl -b | grep "systemd-logind: got pause for"
...
Jun 25 18:44:45 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: got pause for 13:69
Jun 25 18:44:46 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: got pause for 226:1
Jun 25 18:44:46 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: got pause for 13:78
Jun 25 18:44:46 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: got pause for 13:67
Jun 25 18:44:46 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: got pause for 13:82
Jun 25 18:44:46 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: got pause for 13:66
Jun 25 18:44:46 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: got pause for 13:81
Jun 25 18:44:46 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: got pause for 226:0
Jun 25 18:44:46 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: got pause for 13:65
...
In fact, if I search for "systemd-logind" messages, I found these, which are closely related to my last trying:
1) I tried to put it to sleep by closing the lid. It fails to go to sleep;
2) I pressed power key. It has slept as expected (Jun 25);
3) Then, I opened the lid and tried to login... it took almost 15 seconds to give me the login screen...

Code: Select all

[email protected] ~ $ journalctl -b | grep "systemd-logind"

Jun 25 22:34:49 calvin systemd-logind[1106]: Lid opened.
Jun 25 22:35:00 calvin systemd-logind[1106]: Lid closed.
Jun 25 22:35:22 calvin systemd-logind[1106]: Lid opened.
Jun 25 22:35:25 calvin systemd-logind[1106]: Power key pressed.
Jun 26 08:33:44 calvin systemd-logind[1106]: Operation 'sleep' finished.
Jun 26 08:34:03 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: got fd for /dev/input/event18 13:82 fd 30 paused 1
Jun 26 08:34:03 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: releasing fd for 13:82
Jun 26 08:34:03 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: got fd for /dev/input/event19 13:83 fd 30 paused 1
Jun 26 08:34:03 calvin /usr/libexec/gdm-x-session[1283]: (II) systemd-logind: releasing fd for 13:83
Jun 26 08:34:03 calvin /usr/libexec/gdm-x-session[1788]: (II) systemd-logind: got fd for /dev/input/event19 13:83 fd 75 paused 0
Jun 26 08:34:03 calvin /usr/libexec/gdm-x-session[1788]: (II) systemd-logind: returning pre-existing fd for /dev/input/event19 13:83
Jun 26 08:34:03 calvin systemd-logind[1106]: Watching system buttons on /dev/input/event19 (Logitech K270)
Jun 26 08:34:03 calvin /usr/libexec/gdm-x-session[1788]: (II) systemd-logind: got fd for /dev/input/event18 13:82 fd 78 paused 0
Jun 26 08:40:01 calvin systemd-logind[1106]: New session c3 of user man.
Jun 26 08:40:09 calvin systemd-logind[1106]: Session c3 logged out. Waiting for processes to exit.
Jun 26 08:40:09 calvin systemd-logind[1106]: Removed session c3.
[email protected] ~ $ 

I'm using a Dell Linux 4.20.0-sabayon #1 SMP Tue May 14 19:41:00 UTC 2019 x86_64 Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz GenuineIntel GNU/Linux Gnome Version 3.30.2
Processor: Intel® Core™ i7-4510U CPU @ 2.00GHz × 4
Graphics: Intel® Haswell Mobile
OS: Sabayon/Linux 64-bit

Any hints to solve this issue?

Thanks in advance!
Last edited by mhzuchini on Mon Jul 01, 2019 17:58, edited 1 time in total.
______
Dell Inspiron 15 5547 - Gnome
Linux sabayonx86-64 4.2.0-sabayon

User avatar
Alexander88207
Simple Hen
Posts: 46
Joined: Tue Dec 11, 2018 19:10
Location: Germany

Re: Gnome takes too long to present unlock screen once its locked

Post by Alexander88207 » Wed Jun 26, 2019 16:37

Hello mhzuchini,

I noticed this, too, since the forum is no place to report such things, I will open a bug.

https://bugs.sabayon.org/show_bug.cgi?id=5803
How to create a sabayon uefi usb device: https://github.com/linuxerus/sabayon-st ... -device.md

mhzuchini
Simple Hen
Posts: 73
Joined: Mon Aug 20, 2007 18:46
Location: Campinas, Brazil

Re: Gnome takes too long to present unlock screen once its locked

Post by mhzuchini » Wed Jun 26, 2019 19:11

Thanks in advance, Alexander88207 !

As I was not sure if this behavior was expected due to some wrong configuration by my side, I chose to report here before.
I will follow the bug report for news, thank you again!
______
Dell Inspiron 15 5547 - Gnome
Linux sabayonx86-64 4.2.0-sabayon

mhzuchini
Simple Hen
Posts: 73
Joined: Mon Aug 20, 2007 18:46
Location: Campinas, Brazil

Re: Gnome takes too long to present unlock screen once its locked

Post by mhzuchini » Mon Jul 01, 2019 17:58

I can confirm, after a normal RIGO update (gnome-base/gdm-3.30.3-r3 was one of the packages) that the problem was fixed.
I cannot, however, point out a specific package to blame for the problem, since many others were updated as well.

Anyway, I thanks Alexander88207 for opening a bug that was solved.
______
Dell Inspiron 15 5547 - Gnome
Linux sabayonx86-64 4.2.0-sabayon

Post Reply