Can I cinnamon-screensaver lock on live system?
Hello everyone.
Can I cinnamon-screensaver lock on live system?
My debian live USB can not lock by cinnamon-screensaver on debian10 buster.
I can lock on debian9 stretch.
result of gsettings get following.
user@LIVE:~$ gsettings get org.cinnamon.desktop.session idle-delay
uint32 900
user@LIVE:~$ gsettings get org.cinnamon.desktop.screensaver idle-activation-enabled
true
user@LIVE:~$ gsettings get org.cinnamon.desktop.screensaver lock-enabled
true
No effect following.
live-config.nocomponents=cinnamon-screensaver
Debug info following.
How to start helper process?
user@LIVE:~$ cinnamon-screensaver-command -e
user@LIVE:~$ cinnamon-screensaver --debug &
[1] 1716
user@LIVE:~$ Debug mode active
/usr/share/cinnamon-screensaver/cinnamon-screensaver-main.py:61: DeprecationWarning:
Gtk.icon_size_register is deprecated
Gtk.icon_size_register("audio-button", 20, 20)
/usr/share/cinnamon-screensaver/cinnamon-screensaver-main.py:86: Warning: g_base64_en
code_step: assertion 'in != NULL' failed
css = provider.to_string()
Cinnamon Screensaver support not found in current theme - adding some...
Trying to connect to logind...
org.gnome.ScreenSaver is gone from the session bus
org.mate.ScreenSaver is gone from the session bus
Starting screensaver...
Not running under the session scope, trying XDG_SESSION_ID
found session: 1
Successfully using logind
user@LIVE:~$ cinnamon-screensaver-command -l
Found 1 Xinerama screens on display :0
Monitor 0 is 0,0 1024 x 768
Cinnamon Screensaver compiled without Solaris Xinerama support
Scale factor of 1 applied. Monitor 0 is 0,0 1024 x 768
Stage.update_geometry - new backdrop position: 0, 0 new size: 1024 x 768
monitorView: updating view state
monitorView: show wallpaper
user@LIVE:~$ manager: user activity, waking
manager: not locked, queueing idle deactivation
authClient: cancel requested, but no helper process
CsScreen dispose
CsScreen finalize
Can I cinnamon-screensaver lock on live system on debian10 buster?
Thanks.
--
yellowhouse@yellowhouse.jp
Reply to: