You are not logged in.
My Arch install with Plasma with display manager gdm wont start the KDE lock screen correctly when I open the lid from suspend. Is there any fix to this? This really does concern me.
Offline
What does "won't lock right" mean? How does this show itself, post your journal after such a locking situation. FWIW GDM is a lock screen and KDE has a lock screen, I don't know if there's an option to disable GDM from trying to be a lock screen, but if there isn't you might be better off using another display manager that doesn't try to be a lockscreen itself.
Edit: try something like
sudo -u gdm dbus-run-session gsettings set org.gnome.desktop.lockdown disable-lock-screen 'true'Also is this a wayland session and if so did you try xorg?
Mod note: Moving to NC
Last edited by V1del (2019-06-14 14:47:11)
Offline
Not a wayland session. What I mean is that When I open the lid of my laptop, the session doesn’t show the lock screen and goes straight to the desktop. Which is a huge security risk. Also would like to add that this is mostly happening on battery instead of ac
Offline
Also heres a Log that may help
Offline
Jun 14 10:17:50 blackndoob ksmserver[1031]: lock called
Jun 14 10:17:50 blackndoob ksmserver[1031]: Could not establish screen lockDid you try what I mentioned wrt GDM? What's your output for
systemd-inhibit --listalso please edit and append to posts if no one has answered in-between
Offline
Heres my output (edit for completeness)
WHO UID USER PID COMM WHAT >
NetworkManager 0 root 523 NetworkManager sleep >
UPower 0 root 804 upowerd sleep >
PowerDevil 1000 daniel 1526 org_kde_powerde handle-power-key:handle-suspend-key:han>
Screen Locker 1000 daniel 1306 ksmserver sleep >
Telepathy 1000 daniel 1312 mission-control shutdown:sleep >
5 inhibitors listed.
...skipping...
WHO UID USER PID COMM WHAT >
NetworkManager 0 root 523 NetworkManager sleep >
UPower 0 root 804 upowerd sleep >
PowerDevil 1000 daniel 1526 org_kde_powerde handle-power-key:handle-suspend-key:han>
Screen Locker 1000 daniel 1306 ksmserver sleep >
Telepathy 1000 daniel 1312 mission-control shutdown:sleep >
5 inhibitors listed.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
Edit: also would like to add that i did input that command and it didn't do anything but output this
dbus-daemon[7103]: [session uid=120 pid=7103] Activating service name='ca.desrt.dconf' requested by ':1.0' (uid=120 pid=7104 comm="gsettings set org.gnome.desktop.lockdown disable-l")
dbus-daemon[7103]: [session uid=120 pid=7103] Successfully activated service 'ca.desrt.dconf'
Last edited by Dunked0n (2019-06-14 16:01:07)
Offline
Are there any potential fixes or workarounds?
Offline
Wrap output in [ code ][ /code] tags (without the spaces) and don't bump your post
Did you reboot after executing that command? If it still fails even after reboot, get GDM out of the picture, and use normal a configured startx, or if it has to be a DM use sddm.
Last edited by V1del (2019-06-15 11:04:50)
Offline