Mate screen lock issue

Issues related to applications and software problems
gostal
Posts: 30
Joined: 2019/09/23 15:26:45

Re: Mate screen lock issue

Post by gostal » 2019/11/27 19:50:39

I just noticed that Mate is starting the screensaver with the following command:

/usr/bin/mate-screensaver --no-daemon

and this is triggered by the file:

/usr/share/dbus-1/services/org.mate.ScreenSaver.service

If it's not running as a daemon then what is monitoring the state of idleness?

I have also googled this issue and apparently it has happened on Ubuntu:
https://ubuntu-mate.community/t/automat ... ating/5696
https://github.com/mate-desktop/mate-sc ... /issues/92
and I get the impression that it is sensitive to choice of window manager, number of monitors etc. I haven't found a direct solution, though. I also haven't found similar reports on systems using rpm.
Desktop Dell T5810 Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz, 72 GB RAM, Radeon Pro WX 7100
CentOS 7.7.1908

User avatar
TrevorH
Forum Moderator
Posts: 27138
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Mate screen lock issue

Post by TrevorH » 2019/11/27 20:39:46

--no-daemon just means that it doesn't put itself into the background to run. If part of the GUI is starting it up and controlling it then it wouldn't need to be a daemon. My config file looks like yours but my running copy is just

Code: Select all

$ ps fax | grep [s]creen
 7410 ?        Sl     4:17          \_ mate-screensaver
CentOS 6 will die in November 2020 - migrate sooner rather than later!
CentOS 5 has been EOL for nearly 3 years and should no longer be used for anything!
Full time Geek, part time moderator. Use the FAQ Luke

gostal
Posts: 30
Joined: 2019/09/23 15:26:45

Re: Mate screen lock issue

Post by gostal » 2019/11/27 21:44:27

Not so for me:

Code: Select all

ps fax|grep creen
...
5758 ?        Sl     0:00 /usr/bin/mate-screensaver --no-daemon
Desktop Dell T5810 Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz, 72 GB RAM, Radeon Pro WX 7100
CentOS 7.7.1908

User avatar
TrevorH
Forum Moderator
Posts: 27138
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Mate screen lock issue

Post by TrevorH » 2019/11/27 21:59:49

How are you starting MATE?
CentOS 6 will die in November 2020 - migrate sooner rather than later!
CentOS 5 has been EOL for nearly 3 years and should no longer be used for anything!
Full time Geek, part time moderator. Use the FAQ Luke

gostal
Posts: 30
Joined: 2019/09/23 15:26:45

Re: Mate screen lock issue

Post by gostal » 2019/11/27 23:21:27

TrevorH wrote:
2019/11/27 21:59:49
How are you starting MATE?
By selection at login screen during boot. Selection is needed only to switch desktop, of course. Essentially I followed this guide
https://www.rootusers.com/how-to-instal ... s-7-linux/
when I installed MATE except than Gnome was already installed.
Desktop Dell T5810 Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz, 72 GB RAM, Radeon Pro WX 7100
CentOS 7.7.1908

User avatar
TrevorH
Forum Moderator
Posts: 27138
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Mate screen lock issue

Post by TrevorH » 2019/11/28 11:12:55

So there is one difference I think - I am using lightdm and I think you are using gdm.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
CentOS 5 has been EOL for nearly 3 years and should no longer be used for anything!
Full time Geek, part time moderator. Use the FAQ Luke

gostal
Posts: 30
Joined: 2019/09/23 15:26:45

Re: Mate screen lock issue

Post by gostal » 2019/11/28 14:45:36

I believe you are right. Under /etc/systemd/system there is a symlink display-manager.service pointing to /usr/lib/systemd/system/gdm.service. There is also a /usr/lib/systemd/system/lightdm.service. Is switching as simple as redirecting the symlink and reboot? lightdm seems to be installed. I have the following packages:

lightdm-1.25.0-1.el7.x86_64
lightdm-gobject-1.25.0-1.el7.x86_64
lightdm-gtk-1.8.5-19.el7.x86_64
lightdm-gtk-common-1.8.5-19.el7.noarch

Are there any missing?

There is a tool system-switch-displaymanager.noarch in the repos. Perhaps this is the best way to go?
Desktop Dell T5810 Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz, 72 GB RAM, Radeon Pro WX 7100
CentOS 7.7.1908

User avatar
TrevorH
Forum Moderator
Posts: 27138
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Mate screen lock issue

Post by TrevorH » 2019/11/28 15:47:23

I don't even have gdm installed but display-manager points to lightdm.service here.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
CentOS 5 has been EOL for nearly 3 years and should no longer be used for anything!
Full time Geek, part time moderator. Use the FAQ Luke

gostal
Posts: 30
Joined: 2019/09/23 15:26:45

Re: Mate screen lock issue

Post by gostal » 2019/11/28 16:41:51

OK, I'll try redirecting the symlink and reboot then and see what happens.
Desktop Dell T5810 Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz, 72 GB RAM, Radeon Pro WX 7100
CentOS 7.7.1908

gostal
Posts: 30
Joined: 2019/09/23 15:26:45

Re: Mate screen lock issue

Post by gostal » 2019/11/29 10:47:11

It turns out that changing displaymanager is indeed as simple as redirecting the symlink /etc/systemd/system/display-manager.service and reboot. I didn't do it this way, however. Instead I followed the advice here:viewtopic.php?t=67166 and did (as root):

Code: Select all

systemctl disable gdm
systemctl enable lightdm.service
The first command gave the following response:
Removed symlink /etc/systemd/system/display-manager.service.

The second command gave the following:
Created symlink from /etc/systemd/system/display-manager.service to /usr/lib/systemd/system/lightdm.service.

i.e. the symlink got redirected!

No more gdm:

Code: Select all

systemctl status gdm
● gdm.service - GNOME Display Manager
   Loaded: loaded (/usr/lib/systemd/system/gdm.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
lightdm:

Code: Select all

systemctl status lightdm -l
● lightdm.service - Light Display Manager
   Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2019-11-29 11:16:02 CET; 16min ago
     Docs: man:lightdm(1)
 Main PID: 4603 (lightdm)
    Tasks: 25
   CGroup: /system.slice/lightdm.service
           ├─4603 /usr/sbin/lightdm
           ├─5068 /usr/bin/X -core -noreset :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch -background none
           └─5288 /usr/bin/gnome-keyring-daemon --daemonize --login

Nov 29 11:15:59 hostname systemd[1]: Starting Light Display Manager...
Nov 29 11:16:02 hostname systemd[1]: Started Light Display Manager.
Nov 29 11:16:02 hostname lightdm[5113]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Nov 29 11:16:16 hostname lightdm[5152]: pam_sss(lightdm:auth): authentication success; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=gostal
Nov 29 11:16:17 hostname gnome-keyring-daemon[5288]: failed to unlock login keyring on startup
Nov 29 11:16:19 hostname gnome-keyring-daemon[5288]: The Secret Service was already initialized
Nov 29 11:16:19 hostname gnome-keyring-daemon[5288]: The PKCS#11 component was already initialized
Nov 29 11:16:19 hostname gnome-keyring-daemon[5288]: The SSH agent was already initialized
Note: failed to unlock login keyring on startup. Is this serious and if so what do I do?

Changing to lightdm did not, however, fix the screensaver issue. It still does not start automatically when system has been idle long enough.

Is there anything else that I could try except switching to another screensaver?

Cheers,
gostal
Desktop Dell T5810 Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz, 72 GB RAM, Radeon Pro WX 7100
CentOS 7.7.1908

Post Reply

Return to “CentOS 7 - Software Support”