I understand that how much blurring looks good in extremely subjective, however, with the current defaults blurred text is easily readable (partially defeating the idea of locking my screen).

I had to push radius and sigma up to 15 for text to become unreadable (but you can still tell it's text). Maybe I overdid it a bit, but I'd like to proposed to bump the defaults a bit so that i3lock -f makes text unreadable by out-of-the-box.

This would give it a wider audience and make it easier to install on any available system. I love this lock, and wish it were available in more places.

When I run "i3lock -f" with applications running the result is what I expect. However, if I have no applications opened and can only see my background (produced by feh in i3), I see a blurred back background (with my i3bar at the bottom) when running "i3lock -f".

I'm running arch with 2 screens using Nvidia-304xx as a driver.
Adding the -f flag will throw the following error:

X Error of failed request: BadValue (integer parameter our of range for operation)
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 16 (X_GLXVendorPrivate)
Value in failed request: 0x20de
Serial number of failed request: 0
Current serial number in output stream: 649

I think this might be similar to the issues regarding the catalyst drivers, but I'm not sure.

I get a white background and as far as there is no man page with your program I can't really see what the new options mean. If I run i3lock without any other arguments I get just a white background like on the regular i3lock which is not what I want, I dont run composite manager on i3 so that is not a problem. It wouldn't hurt to update a manpage and install it during a make install wouldn't it?
Thanks for your work but this program does not work for me now.

I was playing around with this after trying i3lock-wrapper but finding it too slow. The blurring functionality works great and is much quicker. However, after I type my password I get some pretty crazy screen corruption (The pattern does not appear at once, but instead snakes across the screen a block at a time until the whole display is covered). Switching to a vtty and back to Xorg will clear it up and reveal my desktop. This does not happen if I remove the '-f' option.

I am using the proprietary nvidia drivers (v358.16-3 from the arch linux repositories).

Got something....

Just letting you know that this doesn't work for me at all. It locks the screen with a messed up image over my 3 monitors. I am running Arch with catalyst drivers.

Maybe someday will look into it, when I get my hands on a machine with ati/amd graphics.

I would like to be able to configure i3lock-blur to darken the image when the screen is locked. A brightness adjustment parameter with a range of 0-100 or something similar would be nice. Thanks.

I have a hybrid intel/amd laptop, which means I also have Intel and AMD GPUs.
When using intel, i3lock -f works as expected.
However when on AMD (using proprietary fglrx) it does not work. It blurs for a moment and then it probably crashes or something, as my screen is not locked and unblurred.
I don't know how to debug this, so any suggestion is appreciated.

It takes me 3~4 secs to lock the screen, and 6~9secs to unlock it.

Arch linux
i3-gaps-next-git 4.14.30
i3lock-blur 2.9-1
Running i3lock -f -r 12 -s 12 -u && echo mem > /sys/power/state
i3lock -f -r 12 -s 12 -u -n is also very slow.

I cannot find any related log, not sure how to fix this issue. Do you have any idea ?

I was wondering. Ther's no installation guide, i'am not a c freak, but i know there must be some kind og configure or Makefile. But they're named different, so i'cant execute any of -./configure or make...

Upstream now has a option to show number of failed login attempts. In upstream it is enabled with a cmdline switch '-f'. In i3lock-blur '-f' is used to enable blurring background.

Should I use another switch to enable blurring, or just use another switch to show failed login attempts.

Whenever I use i3lock -f my monitors blur for about 1 second, then unblur, and then it seems like it's frozen for a while. I cannot use my mouse, I cannot enter my password to unlock it, nothing seems to be giving any feedback. After a while it "unfreezes" and throws the following error:

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 4920 requests (4920 known processed) with 0 events remaining.

The amount of requests (4920) differs sometimes. Note that using i3lock by itself works just fine.

Some information about my machine:

• Arch Linux 4.11.9-1
• GPU: Nvidia GTX 1070
• GPU driver: Nvidia proprietary driver 318.22.
• 2 monitors, 1 in landscape, 1 in portrait, both 1440p.

If there's anything else you'd like to know, I can provide that.

This was tested on the master branch and on the version that's on AUR as of writing this issue which is 2.9-1.

First off big thanx for a great locker!
I would like to use the fuzzy option when locking the screen, then suspend to ram, but can't get it to work using either what's suggested in the man page: i3lock -f && echo mem > /sys/power/state nor i3lock -f && systemctl suspend.
I think the reason is that call to fork() isn't issued when the fuzzy flag is applied - I guess for a good reason, but would like to check with you anyway? Or is there some other way of doing it?
Cheers!

Observed in LXQT, but probably similar with LXDE and other:
The option i3lock -f makes the screenshot (and blur it) of all screen elements except of the Panel. In the place of panel there is just blurred background.

I received a "bug report".

The blurring cuts in and out when I use this; one moment it's blurred, then the next it's clear, then it's blurred again, seeming to update in time with the clock on my statusbar.

• Celti

When I do "i3lock -f" it will show a blurred screenshot as expected. However it seems to stop workin after that. It will just show the screenshot and not any lock symbol. And when I try to type my password to unlock the screen nothing happens. Neither any indication on the lockscreen that it registered me typing nor unlocking the screen. I have to go to another tty to kill the process. When I run "i3lock -f --debug" I get these errors:
scaling factor = 7.680000 radius = 3 sigma = 3.840000 X11 Error received! sequence 0x11c, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x11d, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x11e, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x11f, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x120, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x121, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x123, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x124, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x126, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x128, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x12a, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x12b, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x12d, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2e5, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2e6, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2e7, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2e8, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2e9, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2ea, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2ec, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2ed, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2ef, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2f1, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2f3, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2f4, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x2f6, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x371, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x372, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x373, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x374, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x375, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x376, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x378, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x379, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x37b, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x37d, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x37f, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x380, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x382, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x3fd, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x3fe, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x3ff, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x400, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x401, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x402, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x404, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x405, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x407, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x409, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x40b, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x40c, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x40e, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x489, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x48a, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x48b, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x48c, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x48d, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x48e, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x490, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x491, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x493, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x495, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x497, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x498, error_code = 8, major = 0x3e, minor = 0x0 X11 Error received! sequence 0x49a, error_code = 8, major = 0x3e, minor = 0x0 [i3lock-debug] device = 3 [i3lock-debug] found Xinerama screen: 1366 x 768 at 0 x 0 [i3lock-debug] device = 3 [i3lock-debug] redraw_screen(unlock_state = 0, pam_state = 0) [i3lock-debug] redraw_screen(unlock_state = 0, pam_state = 0) [i3lock-debug] redraw_screen(unlock_state = 0, pam_state = 0) [i3lock-debug] redraw_screen(unlock_state = 0, pam_state = 0)
I have not been able to figure out what the X11 errors mean. I am running Arch Linux with an Intel CPU and ATI Radeon graphics card. When I use it without the -f option it works fine.