You are not logged in.
Hi! I would like to disable lightdm and use manual startx for run X window. There are not problem on this.
The problem is in the locker. I want use physlock as a locker.
I have modified the script bl-lock to call physlock and works fine. But when I suspend the system and the system is resumed the locker doesnt works.
Maybe the problem is relationated with the file /etc/systemd/system/display-manager.service but I dont know how to create a new adapted file por physlock
Any suggestion is welcome!
Thanks
Last edited by pepemopap (2016-04-29 23:52:06)
Offline
Welcome to BunsenLabs!
I have modified the script bl-lock to call physlock and works fine. But when I suspend the system and the system is resumed the locker doesnt works
What modifications have you made?
What exactly do you mean by "doesn't work"?
Also, how did you disable LightDM?
Offline
Welcome to BunsenLabs!
pepemopap wrote:I have modified the script bl-lock to call physlock and works fine. But when I suspend the system and the system is resumed the locker doesnt works
What modifications have you made?
What exactly do you mean by "doesn't work"?
Also, how did you disable LightDM?
Hi! Thanks for your welcome. This is my first intervention, but I follow the forum for a long time.
I have uninstlled lightdm and light-locker.
First i modified bl-block only replacling light-locker-command for physlock. But now i have restart the content of this script and i have created a script in /usr/bin/light-locker-command that only call physlock. I prefer not modify system files to prevent errors in future package update.
bl-lock command works fine with this.
When i suspend the system it restart directly without lock screen. No errors or messages are showed.
I would need configure the system for calling physlock after resume.
Thanks a lot.
Offline
Would this be because you uninstalled lightdm? Perhaps physlock needs a DM for it to be called?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
Would this be because you uninstalled lightdm? Perhaps physlock needs a DM for it to be called?
Really physlock works fine only calling the command physlock. I need config the system for calling it at resuming. I beleave physlock dont do it by itself, is very simple software.
Offline
Horizon_Brave wrote:Would this be because you uninstalled lightdm? Perhaps physlock needs a DM for it to be called?
Really physlock works fine only calling the command physlock. I need config the system for calling it at resuming. I beleave physlock dont do it by itself, is very simple software.
with light-locker, it gives you different switches to allow you to set how long and what happens when you resume...are you sure this physlock application doesn't have such a features? Also...I can't actually find any documentation about this. Are you spelling the name correctly?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
I have tried this solution and seems to work: https://wiki.debian.org/ScreenLockingOnSleep
Yes, physlock is the name. The github page is https://github.com/muennich/physlock
But if someone knows a better solution for lock in text mode i would like to know. The vlock command is popular, but the package in debian doesnt have the plugin for -n option, needed for lock in X mode.
Offline
if someone knows a better solution for lock in text mode i would like to know
I don't know about better, but:
Only sflock, physlock, Cinnamon Screensaver, MATE Screensaver and GNOME Screensaver are able to block tty access.
https://github.com/benruijl/sflock
Please add [SOLVED] to the thread title to help others with this problem
Offline