i3lock | improved screen locker

by i3 C Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(8)Vulnerabilities Install Support

kandi X-RAY | i3lock Summary

i3lock is a C library. i3lock has no bugs, it has no vulnerabilities and it has low support. However i3lock has a Non-SPDX License. You can download it from GitHub.

Simply invoke the i3lock command. To get out of it, enter your password and press enter. On OpenBSD the i3lock binary needs to be setgid auth to call the authentication helpers, e.g. /usr/libexec/auth/login_passwd.

Support

Quality

Security

License

Reuse

Support

i3lock has a low active ecosystem.

It has 659 star(s) with 364 fork(s). There are 31 watchers for this library.

It had no major release in the last 6 months.

There are 18 open issues and 152 have been closed. On average issues are closed in 89 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of i3lock is current.

Quality

i3lock has no bugs reported.

Security

i3lock has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

i3lock has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

i3lock releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of i3lock

Get all kandi verified functions for this library.

i3lock Key Features

No Key Features are available at this moment for i3lock.

i3lock Examples and Code Snippets

No Code Snippets are available at this moment for i3lock.

Community Discussions

Trending Discussions on i3lock

Xmonad Layout Follow up

How can I use both Super and Super+L as different keyboard shortcuts in Arch Linux?

Bash script works in terminal emulator, but not as i3 keybind

When waking up from i3lock some interaction is allowed before the password is requested

Prevent xautolock/i3lock when watching video

Ubuntu + i3lock lock on lid close

Using qemu Raspbian: installing libc6:i386 fails

Java GUI Xmonad not working

QUESTION

Xmonad Layout Follow up

Asked 2021-Feb-02 at 11:06

This is a follow up to a question that I had before. I know about the DoRectFloat/RationalRect modules and such, but, I've tried to write proper Haskell and it either doesn't compile, or it compiles and doesn't do what I want.

(These are floating windows that I want) What I want is a layout like

How would I go about writing this?

My current Xmonad Config:

...

ANSWER

Answered 2021-Jan-28 at 15:37

When starting the three windows, use xterm's -class option to modify the WM_CLASS property it attaches to its window, choosing a different and unique class for each of the three. Then you can select for that class in your manage hook to only match the right window.

Source https://stackoverflow.com/questions/65939554

QUESTION

How can I use both Super and Super+L as different keyboard shortcuts in Arch Linux?

Asked 2020-Feb-05 at 08:18

Using xfce4-keyboard-settings, I have SuperL keybound to start rofi using rofi -show drun, but this prevents me from using SuperL in combination with any other key combinations, such as Super + L to lock the screen. rofi is hijacking the show immediately.

I've tried prepending a sleep to rofi, ie. sh -c "sleep 1 && rofi -show drun", which correctly sleeps and even lets me use Super + L to lock the screen, but then rofi loads over the top and starts to interact weirdly (read: undesirably) with the lock screen.

Is there a way that I can have both keyboard shortcuts work as desired without interfering with eachother?

BTW, the lock screen I'm using is i3lock-fancy.

...

ANSWER

Answered 2018-Jun-08 at 04:16

I solved this following AndreLDM's advice.

I installed xcape, and added xcape -e 'Super_L=Control_L|Escape' to ~/.config/openbox/autostart and bound the keyboard shortcut Ctrl+Esc to run rofi. I was then able to keybind Super+L to i3lock-fancy and have both keyboard shortcuts work as I intended. Pressing Super by itself presents my rofi drun menu, and Super+L locks the screen.

Source https://stackoverflow.com/questions/50642713

QUESTION

Bash script works in terminal emulator, but not as i3 keybind

Asked 2020-Feb-05 at 08:17

I have a lock screen script (via i3lock) that runs correctly in a terminal window, but not when used as a keybind in i3 config.

The script is pretty straightforward:

...

ANSWER

Answered 2018-Jun-21 at 12:35

I remember something similar... try specifying the absolute path like this, might be that exec doesn't honor the $PATH environment variable:

Source https://stackoverflow.com/questions/50968451

QUESTION

When waking up from i3lock some interaction is allowed before the password is requested

Asked 2019-Nov-26 at 11:04

I have the following three lines in my .config/i3/config file:

...

ANSWER

Answered 2019-Nov-26 at 11:04

I use slock.

I also use it in a small script to lock my machine what is has been suspended. It locks the machine after waking up.

Source https://stackoverflow.com/questions/58787527

QUESTION

Prevent xautolock/i3lock when watching video

Asked 2019-May-07 at 22:07

I use i3 window manager and have

...

ANSWER

Answered 2019-May-07 at 22:07

One possible way to do this, without needing to implement all of xautolock's options in myscript would be to write your $Locker as a script or program to determine if the conditions are met to prevent locking. Otherwise, call the screen locker:

Source https://stackoverflow.com/questions/53177614

QUESTION

Ubuntu + i3lock lock on lid close

Asked 2018-Mar-12 at 06:22

I looking to lock my laptop when i close the lid and can't get this working in Ubuntu 16.04.

I've tried this https://github.com/ruudud/i3wm-scripts

seems that this is the solution most commonly suggested on the internet, but it does not work.

The github repo suggests creating a service called i3lock.service that runs (as far as i can tell) before "sleep.target". Please note that i have no clue what that is, and would appreciate some more info about that.

I'm not sure if i'm supposed to just create the file and it should work or it requires some special privileges for that file or what? More detail on that would be needed.

If this solution is incorrect is it possible to be pointed to a better solution to this problem?

Thank you in advance :)

...

ANSWER

Answered 2017-May-08 at 18:03

In the meen time I switched to Manjaro (much nicer), but this solution should work on both:

Creating a service called lock@.service in /etc/systemd/system with this content:

Source https://stackoverflow.com/questions/41909770

QUESTION

Using qemu Raspbian: installing libc6:i386 fails

Asked 2017-Dec-04 at 11:52

this is my first post on this forum.

I am trying to get qemu running on my Raspberry Pi 3 with Raspbian stretch installed. My brothers DCP-350C scanner driver is only available precompiled on x86. I have added i386 arch with sudo dpkg --add-architecture i386 and installed qemu-user binfmt-support. No problems there.

But every time I try to install libc6:i386 I get an install error:

...

ANSWER

Answered 2017-Dec-04 at 11:52

That kind of error ("libgcc1:i386 Breaks: libgcc1 (!= 1:6.3.0-18) but 1:6.3.0-18+rpi1 is to be installed" and "libgcc1 : Breaks: libgcc1:i386 (!= 1:6.3.0-18+rpi1) but 1:6.3.0-18 is to be installed") is because multiarch support on Debian and Debian derivatives requires that all versions of a package for each architecture that you have installed must have exactly matching versions. So you can have libgcc1:i386 1:6.3.0-18 and libgcc1:armhf 1:6.3.0-18 installed together because the versions match, but not libgcc1:i386 1:6.3.0-18 and libgcc1:armhf 1:6.3.0-18+rpi1 (because the versions don't exactly match).

The problem here is that raspbian rebuilds packages, which is why they have the +rpi1 tag on the end of their version. So what you would need is either

a repository where the raspbian versions of packages have been built for i386 -- this may well not exist
or run pure upstream Debian rather than Raspbian -- which you likely don't want to swap to at this point
or rebuild all the packages for i386 yourself -- which is likely painful and easy to get wrong if you don't know what you're doing.

If it's any consolation I would be somewhat uncertain about whether QEMU could usefully handle emulating a hardware-specific piece of code like a scanner driver (which is probably a plugin to CUPS or other system software) anyway.

A quick google of the scanner model name brought up this webpage: http://support.brother.com/g/b/downloadlist.aspx?c=us_ot&lang=en&prod=dcp350c_all&os=128 which includes a download for source code for the scanner driver and CUPS wrapper driver. If I were you I would try the approach of building that natively for arm.

Source https://stackoverflow.com/questions/47590880

QUESTION

Java GUI Xmonad not working

Asked 2017-Jan-24 at 21:44

Java GUI applications only give me a blank window, I tried:

...

ANSWER

Answered 2017-Jan-24 at 21:44

so finally I found out it is:

Source https://stackoverflow.com/questions/41832881

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install i3lock

See [the i3lock home page](https://i3wm.org/i3lock/).

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: