• Re-Enable LightDM on Gnome3


    Hi,
    I installed antergos with gnome yesterday. So far, everything works fine, except lightdm :/
    For testing/playing around, I removed lightdm and installed gdm yesterday. However, I felt that gdm slowed down my overall system, especially the gnome shell (??). Thus, I deleted gdm and reinstalled lightdm. Everything works as expected (e.g. I can log-in), except the lock-screen:

    • Automatic lock / screensaver does not work. I am not sure, if this worked before my install/reinstall of lightdm. I disabled all gnome related power settings in “power”, but the settings changed in light-locker are not saved (same as: https://forum.antergos.com/topic/5473/gnome-not-locking-screen-automatically/15)
    • Activating the lock screen using the gnome hotkeys, e.g. “super+l” does not work. This worked before.

    I found the following thread https://forum.antergos.com/topic/5465/buttons-go-missing-from-the-system-menu-in-gnome-3 leading me to https://github.com/the-cavalry/light-locker/issues/54 which both deal with the problem, but do not give a definitive answer. However, antergos + gnome ships with lightdm as default, so I assume that there is a way to get it working? Any ideas whats going on here?

    Here is some additional info:

    dm-tool lock #works, I get the standard lock-screen and can login with a problem
    
    light-locker-command -l #not working, nothing happens. No output
    
    light-locker --debug # some infos
    [gs_debug_init] gs-debug.c:106 (09:39:23):	 Debugging enabled
    [main] light-locker.c:126 (09:39:23):	 initializing light-locker 1.6.0
    [main] light-locker.c:128 (09:39:23):	 lock after screensaver 5
    [main] light-locker.c:129 (09:39:23):	 late locking 0
    [main] light-locker.c:130 (09:39:23):	 lock on suspend 1
    [query_session_id] gs-listener-dbus.c:1790 (09:39:23):	 org.freedesktop.login1.NoSessionForPID raised:
     PID 21835 does not belong to any known session
    
    
    [init_session_id] gs-listener-dbus.c:1882 (09:39:23):	 Got session-id: (null)
    [query_sd_session_id] gs-listener-dbus.c:1866 (09:39:23):	 Couldn't determine our own sd session id: No such device or address
    [init_session_id] gs-listener-dbus.c:1887 (09:39:23):	 Got sd-session-id: (null)
    [init_seat_path] gs-listener-dbus.c:1964 (09:39:23):	 Got seat: /org/freedesktop/DisplayManager/Seat0
    
    ** (light-locker:21835): WARNING **: screensaver already running in this session
    
    
  • @pille.buschjaeger said in Re-Enable LightDM on Gnome3:

    gdm slowed down my overall system

    yes true GDM is a monster…

    But lightdm is almost not working good together with Gnome and light-locker…
    I start using lightm-gtk-greeter and lightdm-gtk-greeter-settings this kind of working better with gnome…

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    http://kamprad.net/howto-installing-antergos/
    how to add system logs

  • I just installed lightdm-gtk-greeter and it works. However, I still need to use

    dm-tool lock
    

    to lock my screen. The standard gnome shortcuts still do not work, so I’ll probably end up defining a custom one. Did not check automatic lock / fade-to-blackscreen yet. lightdm-gtk-greeter-settings seems to have a bug in which “timeout until the screen blanks” is not updated if the slider below it is used. I hope the slider still works and my screen gets blank in like 5 minutes.
    So in that regard, lightdm-gtk-greeter is not really an improvement so far and I am asking myself, if there is a working solution to this at all :o

  • I do research yesterday, but no way to get this working with lightdm + light-locker + Gnome…

    I can see also that try to autostart:

    $ xset dpms 600 900 1200
    

    xset dpms <Standby> <Suspend> <Off> (in seconds)

    will not be working with this combi, i can not find how but this settings will be reset…

    I read also that if GDM is not present Gnome give the Monitor powermanagement to gnome-screensaver… but i do not know how…

    https://github.com/the-cavalry/light-locker/issues/82
    https://github.com/the-cavalry/light-locker/issues/54

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    http://kamprad.net/howto-installing-antergos/
    how to add system logs

  • @joekamprad said in Re-Enable LightDM on Gnome3:

    I do research yesterday, but no way to get this working with lightdm + light-locker + Gnome…

    I can see also that try to autostart:

    $ xset dpms 600 900 1200
    

    xset dpms <Standby> <Suspend> <Off> (in seconds)

    will not be working with this combi, i can not find how but this settings will be reset…

    I read also that if GDM is not present Gnome give the Monitor powermanagement to gnome-screensaver… but i do not know how…

    https://github.com/the-cavalry/light-locker/issues/82
    https://github.com/the-cavalry/light-locker/issues/54

    Seems support for lock-screen is complete forced to gdm under gnome:
    https://unix.stackexchange.com/questions/86221/how-can-i-lock-my-screen-in-gnome-3-8-without-gdm/178496:

    As you can read there for gnome3 they also erase support for gnome-screensaver complete, so no way to get this handled by other then gdm.

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    http://kamprad.net/howto-installing-antergos/
    how to add system logs

  • To make things a little more worse, it seems like GDM suffers from memory leaks + starts two instances on TTY1 and 2 for the login, eating up additional ~200 MB for a process which does nothing most of the time. See: https://bugzilla.gnome.org/show_bug.cgi?id=747339

    Not sure if this is fixed by now for single user systems, since the last comment on this war in February this year, but the bug report is still open.

  • I do see this now at the memory side:

    ps_mem | grep gdm
    
    Private +  Shared   =  RAM used  Program
    1.5 MiB + 182.5 KiB =   1.6 MiB	gdm
    1.5 MiB + 252.0 KiB =   1.7 MiB	gdm-x-session (2)
    3.8 MiB +   1.1 MiB =   4.9 MiB	gdm-session-worker (2)
    

    Does not look like what i remember from like one month ago ;)

    All Ram usage:

    ps_mem | curl -F c=@- https://ptpb.pw/
    

    https://ptpb.pw/Oe5I

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    http://kamprad.net/howto-installing-antergos/
    how to add system logs

  • @pille.buschjaeger said

    To make things a little more worse, it seems like GDM suffers from memory leaks + starts two instances on TTY1 and 2

    Ah, this is not a bug. It simply is the way Gnome devs work! It was reported some 2-3 yeass ago. The answer was that it intentionally provides 2 instances, the one used as a fast way to swap users.
    There was no way to contact the dev responsible for this, at that time, because he was in Australia. I guess he must still be there!

    1.Antergos Linux KDE plasma / Gnome 2.Ubuntu 17.10 64bit Unity
    Intel Core2 Duo CPU P8400 2.26GHz‖ RAM 3908 MiB ‖ Dell Inc. 0F328M - Dell Inc. Latitude E6500
    Intel Mobile 4 Series Chipset Integrated Graphics [8086:2a42] {i915

  • @anarch your bold text corrections i was able to see live like a movie …but sadly i was not able to do a screencast…:(

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    http://kamprad.net/howto-installing-antergos/
    how to add system logs

  • @joekamprad , poor, old eyes. The platform unfortunatelly doesn t help when zoomed. It becomes ureadable. So, I can only check what I posted after I submmit it… sorry about this… -:(

    1.Antergos Linux KDE plasma / Gnome 2.Ubuntu 17.10 64bit Unity
    Intel Core2 Duo CPU P8400 2.26GHz‖ RAM 3908 MiB ‖ Dell Inc. 0F328M - Dell Inc. Latitude E6500
    Intel Mobile 4 Series Chipset Integrated Graphics [8086:2a42] {i915

  • My eys too 44 y.o. but i have big screen you mean this? https://i.imgur.com/9IiaTKz.png

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    http://kamprad.net/howto-installing-antergos/
    how to add system logs

light-locker3 lightdm89 login-manager3 Posts 11Views 491
Log in to reply