I'm having the same problem. Super+L and clicking on "Lock" don't do anything.

Locking via shell works however with:

dm-tool lock

but not with:

gnome-screensaver-command --lock

    Exactly the same comportment than seagle describe with my normal account (sudoer).

      @ All user affected: What desktop environment are you running?

      Works fine for me. Latest Solus Budgie.

        It's interesting. All users here have an updated Budgie.
        2 users have a lock that works.
        The rest do not.
        If we were all running WIN I would easily guess "software conflict", when apps regularly over-rode the settings of another app.
        Does such a thing as software conflict exist in solus/linux I wonder?

        a month later
        10 days later

        By running gnome-screensaver in debug mode like this:

        pkill -f gnome-screensaver
/usr/bin/gnome-screensaver --no-daemon --debug &

        I noticed this output in the shell when trying to lock

        [listener_lock_cb] gs-monitor.c:209 (10:02:48):	 Locking disabled by the administrator

        Which got me to check org.gnome.desktop.lockdown via gsettings

        $ gsettings get org.gnome.desktop.lockdown disable-lock-screen
true

        This nees to be set to false

        sudo gsettings set org.gnome.desktop.lockdown disable-lock-screen 'false'

        Now locking the computer is working normally again for me.

          6 months later

          seagle Late reply, but you cracked the case Seagle! Although I had to solve the problem using a slightly different gsetting command - thought I'd post here in case anyone else encountered this foible.

          By running the following command I confirmed that the value for Gnome's desktop lockdown setting was 'true' when it should be 'false'.
          sudo gsettings set org.gnome.desktop.lockdown disable-lock-screen 'false'

          I tried to set it to 'false' using the set command but no dice for some reason, so I used the reset command which did the trick.
          gsettings reset org.gnome.desktop.lockdown disable-lock-screen

          The GUI lock function now works! Though the behaviour of Solus's locking system does seem slightly weird - I wonder why after locking and switching users, getting back into your account requires logging in on the home screen, and then typing the same password into the still active lock screen... seems a bit redundant to me as you've already proved you have the right credentials on the home screen.

              trenchanter the "reset" probably makes more sense anyway than manually setting it to "false".

                7 months later

                Thanks a lot, rest it works !
                gsettings reset org.gnome.desktop.lockdown disable-lock-screen

                a month later

                Sorry for the late reply, but I was having the exact same issue after last Friday's software update. trenchanter your solution did the trick to solve the lock issue. Thanks!

                  4 months later

                  I am getting this behavior after the upgrade of gnome-settings-daemon from 3.36.1-47-1-x86_64 to 3.38.1-48-1-x86_64.

                  I have not disabled this:

                  $ gsettings get org.gnome.desktop.lockdown disable-lock-screen
false

                  Despite this, my screen never locks. I ran gnome-screen-saver from command line with debugging enabled, as you can see below, it detects me "toggling" screen locking on/off:

                  /usr/bin/gnome-screensaver --no-daemon --debug
[key_changed_cb] gs-prefs.c:325 (18:25:18):	 lock-enabled=0
[gs_manager_set_lock_enabled] gs-manager.c:162 (18:25:18):	 GSManager: lock-enabled=0
[key_changed_cb] gs-prefs.c:325 (18:25:20):	 lock-enabled=1
[gs_manager_set_lock_enabled] gs-manager.c:162 (18:25:20):	 GSManager: lock-enabled=1

                  When I set the screen lock to 5 minutes I get this logged, which seems to indicate that the inactivity was identified, but nothing happens (my screen does not lock):

                  [watcher_idle_notice_cb] gs-monitor.c:126 (18:41:03):	 Idle notice signal detected: 1
[_gs_watcher_set_session_idle_notice] gs-watcher-x11.c:207 (18:41:03):	 Idle notice signal not handled: 1

(gnome-screensaver:51636): GLib-CRITICAL **: 18:41:03.501: Source ID 36 was not found when attempting to remove it
[listener_dbus_handle_system_message] gs-listener-dbus.c:851 (18:41:03):	 obj_path=/org/freedesktop/login1/session/c1 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:851 (18:41:03):	 obj_path=/org/freedesktop/login1/seat/seat0 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:851 (18:41:03):	 obj_path=/org/freedesktop/login1/user/_1000 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:851 (18:41:03):	 obj_path=/org/freedesktop/login1 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)

                  When I move the mouse after seeing this message (because my screen stays on) I see this logged indicating it has understood that there is activity:

                  [listener_dbus_handle_system_message] gs-listener-dbus.c:851 (18:41:34):	 obj_path=/org/freedesktop/login1/session/c1 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:851 (18:41:34):	 obj_path=/org/freedesktop/login1/seat/seat0 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:851 (18:41:34):	 obj_path=/org/freedesktop/login1/user/_1000 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)
[listener_dbus_handle_system_message] gs-listener-dbus.c:851 (18:41:34):	 obj_path=/org/freedesktop/login1 interface=org.freedesktop.DBus.Properties method=PropertiesChanged destination=(null)

                  Both dm-tool lock and Super-L seem to work fine.

                    JoshStrobl First of all thanks for your time on this.

                    I was not aware the screen saver is forked, but in the meantime I've pursued another avenue. I installed a fresh VM with Solus, updated to Gnome 3.38, configured the screensaver there to 1 minute and waited: the VM locks the screen properly.

                    So now I'm wondering if the problem is that some configuration is broken in my system due to eopkg's failed rollback.

                    When I tried to rollback from 3.38 with eopkg history -t n, that failed due to a missing package (vino is removed from the repo). So eopkg aborted the rollback mid-way and I was forced to re-install all updates to go back to latest. (NOTE: I tried to roll back due to the resolution bug which I had just run into, and my first reaction was to revert).

                    I'm thinking that maybe some configuration was broken by eopkg when it interrupted its rollback?

                    One last thing I investigated was this:

                    I ran dbus-monitor in the VM and my desktop. I see in the VM these dbus messages when I go idle, the screen saver activates and when I move the mouse after:

                    # idle detected
signal time=1607120427.055833 sender=:1.34 -> destination=:1.7 serial=149 path=/org/gnome/Mutter/IdleMonitor/Core; interface=org.gnome.Mutter.IdleMonitor; member=WatchFired
method call time=1607120427.056460 sender=:1.7 -> destination=:1.34 serial=293 path=/org/gnome/Mutter/IdleMonitor/Core; interface=org.gnome.Mutter.IdleMonitor; member=AddUserActiveWatch

# screen saver activated
signal time=1607120437.280720 sender=:1.11 -> destination=(null destination) serial=17 path=/org/gnome/ScreenSaver; interface=org.gnome.ScreenSaver; member=ActiveChanged
method call time=1607120437.281013 sender=:1.24 -> destination=:1.34 serial=57 path=/org/gnome/Mutter/IdleMonitor/Core; interface=org.gnome.Mutter.IdleMonitor; member=AddIdleWatch

# moved mouse, idle stop
method call time=1607120437.281120 sender=:1.24 -> destination=:1.34 serial=58 path=/org/gnome/Mutter/IdleMonitor/Core; interface=org.gnome.Mutter.IdleMonitor; member=AddUserActiveWatch
signal time=1607120437.281972 sender=:1.34 -> destination=:1.24 serial=159 path=/org/gnome/Mutter/IdleMonitor/Core; interface=org.gnome.Mutter.IdleMonitor; member=WatchFired

                    On the host which has the issue I see no mention of org.gnome.ScreenSaver. It simply doesn't activate:

                    # idle detected
signal time=1607120702.020979 sender=:1.35 -> destination=:1.7 serial=367 path=/org/gnome/Mutter/IdleMonitor/Core; interface=org.gnome.Mutter.IdleMonitor; member=WatchFired
method call time=1607120702.021405 sender=:1.7 -> destination=:1.35 serial=364 path=/org/gnome/Mutter/IdleMonitor/Core; interface=org.gnome.Mutter.IdleMonitor; member=AddUserActiveWatch

# moved mouse, idle stop
signal time=1607120722.263449 sender=:1.35 -> destination=:1.7 serial=370 path=/org/gnome/Mutter/IdleMonitor/Core; interface=org.gnome.Mutter.IdleMonitor; member=WatchFired

                    However, in the window running gnome-screensaver --debug I do see it noticing the inactivity:

                    [watcher_idle_notice_cb] gs-monitor.c:126 (22:25:02):	 Idle notice signal detected: 1
[_gs_watcher_set_session_idle_notice] gs-watcher-x11.c:207 (22:25:02):	 Idle notice signal not handled: 1

                    I wonder who is supposed to handle this signal being emitted by gs-watcher. It is very likely that this failure to handle this signal is the culprit. Does something receive it and fail to process it? Does the thing supposed to receive it not run on my box anymore causing this? I don't know much about GNOME/dbus architecture unfortunately so I don't know what's supposed to happen there.