On Friday 05 May 2023 12:27:42 am Michele Calgaro via tde-users wrote: Hi Michele (&dep), It's not that easy to break, but trying to lock the screen in a desktop where Oracle VB is running will eventually do it. So, it's something with an app interfering with kdesktop_lock, not something wrong, per se, with kdesktop_lock. (imo) Playing with it, I've found just killing kdesktop_lock /usr/bin/pkill kdesktop_lock causes the screen to lock. No matter what state isBlanked is in. I can code with that, but is that normal? Thanks much for the pointer to kdesktop, this has been nagging me for the last 5 or 6 years. I’m also copying at end my new ‘goodnight’ script for anyone who cares or uses what I’ve posted in the past. Best Regards, Michael PS: michael@local [~/data/trash]# dcop kdesktop KScreensaverIface isEnabled true michael@local [~/data/trash]# dcop kdesktop KScreensaverIface isBlanked false Not a biggie, but I’m also somewhat curious why they are returning text values instead of 0 and 1? # # # # # # # # # # # # #!/bin/bash #### # Goodnight script to lock and blank the monitor. # Generally attached to a button in the taskbar / panel. #### isBlanked=`dcop kdesktop KScreensaverIface isBlanked` if [ "$isBlanked" = 'true' ] ; then /usr/bin/pkill kdesktop_lock else dcop kdesktop KScreensaverIface lock fi sleep 3 xset dpms force standby