There are certainly better ways to resolve this, so if you want to toss in your two cents feel free to reply with more efficient solutions which do the same exact thing. Test by locking the screen - You will know success is achieved once the display turns itself off. In x-terminal-emulator: mate-panel -replace If pathExists("mate-screensaver-command"):īnnect( "clicked", self.ButtonClicked, "mate_dpmslock.sh" )īnnect( "clicked", self.ButtonClicked, "xdg_dpmslock.sh" )Īfter, either place the MATE Menu applet from panel preferences wherever for testing, or if you have it already perform the following: In an elevated editor of preference, for system_management.py: if ( self.showLockScreen = True ):īutton5 = easyButton( "system-lock-screen", self.iconsize,, -1, -1 ) Then open with elevation system_management.py to make the following changes: In x-temrinal-emulator: cd /usr/lib/python3/dist-packages/mate_menu/plugins Once saved and made executable, you can then make the following changes to MATE Menu, by first: In x-terminal-emulator sudo chmod +x /usr/bin/mate_dpmslock.sh Perform the following in a terminal to make them executable: Save both as mate_dpmslock.sh and xdg_dpmslock.sh respectively, for what will be done next. ![]() ![]() In an elevated editor of preference, for what will become /usr/bin/xdg_dpmslock.sh: #!/bin/bash In an elevated editor of preference, for what will become /usr/bin/mate_dpmslock.sh: #!/bin/bash You can name these files whatever you want, but know those names have to be used for MATE Menu - else it won't work! Names used are for the functional example presented below. In this example, two scripts will be present, and they will be stored in /usr/bin where they can be executed by filename alone. After much trial and error I figured out a way to do this in what some may argue is the worst way possible, but it doesn't involve any fancy scripting, and what basic scripting is shown, any individual regardless of skill could do without reading this guide. For some people, this behaviour is desired. Screen lock behaviour at the moment no longer blanks out (really: turns off) the display on lock. This also isn't the best solution, but it is a way that works without complicated scripting. There is a complex locking scheme available for power users thatĪllows locking policy to change for the lid, suspend and hibernateĪctions.These are not official instructions, and regardless whatever you do with your machine is at your own risk. Gnome-screensaver when the lid is closed, or the system performs a Means that the screen will lock if set to Lock screen in ![]() In Gnome screen locking guide it says: 6.2. Screen Lockingīy default, GNOME Power Manager supports a simple locking scheme. To reverse the setting back use: gsettings set lock-enabled true If true you can turn off screen saver locking with: gsettings set lock-enabled false To check screen saver lock status use: $ gsettings get lock-enabled ![]() Some people may want the screen saver to come on but not have it locked when waking up the screen. The screen saver requires input to get your desktop back. There was some confusion where people think disabling the Lock screen also disables the screen saver which is invoked after a certain period of inactivity. If you are unhappy with the new setting you can reverse it using: gsettings set disable-lock-screen 'false' Now set it to true using this command: gsettings set disable-lock-screen 'true' You can disable the lock screen permanently when waking from suspend.įirst use this command to discover current settings: $ gsettings get disable-lock-screen
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |