Comment 2 for bug 1469700

HOOAA, this package is crazy lightweight and does the job :D

I did read this though:
http://z-issue.com/wp/screen-lockers-xtrlock-and-slock/

And that article is correct about:

"Both applications also have a similar “flaw,” which likely won’t have much of an impact, but is worth mentioning. When the screen is locked using either application, one can switch to a different virtual terminal (by using the CTRL-ALT-F# combination for the desired virtual terminal) without entering the password of the user that started the locking application. Now, that user can log in to the system, but cannot kill xtrlock or slock unless they can become root. However, it does pose a bit of a security concern in some use cases that don’t really apply to my situation. If you can think of some other possibilities, feel free to leave a comment here, and I’ll further investigate."

Anyway, I don't mind that as long as we are going to mention this - if we all agree to use it - in the release notes.

The only thing I need to figure now is how to use that feature without typing:

"xtrlock"

On the "Run" window.

I was hoping to see that as an entry on the menu but it seems that package has no entry and one needs to do it manually but let's see, hopefully there is a way if we are going to use that super lightweight package :)