yvbbrjdr / i3lock-fancy-rapid Goto Github PK

Whenever I lock my laptop with i3lock-fancy-rapid 7 1 command I have to lock the telegram-desktop client as well, otherwise notifications are still visible and not blurred.

I cloned and compiled the newest commit 80467db of master of i3lock-fancy-rapid. There are some warnings. And the execution of ./i3lock-fancy-rapid 5 3 does not work but gets stuck (must use Ctrl+C to terminate).

$ cd i3lock-fancy-rapid
$ git log --oneline
80467db (HEAD -> master, origin/master, origin/dev, origin/HEAD) Merge pull request #6 from piluke/dev
...
...
$ make      
gcc -c -O3 -fopenmp -DLODEPNG_NO_COMPILE_DECODER -DLODEPNG_NO_COMPILE_DISK -DLODEPNG_NO_COMPILE_ANCILLARY_CHUNKS -DLODEPNG_NO_COMPILE_ERROR_TEXT -Wall -Wextra i3lock-fancy-rapid.c -o i3lock-fancy-rapid.o
i3lock-fancy-rapid.c: In function ‘main’:
i3lock-fancy-rapid.c:188:5: warning: ignoring return value of ‘pipe’, declared with attribute warn_unused_result [-Wunused-result]
     pipe(fds);
     ^~~~~~~~~
i3lock-fancy-rapid.c:190:9: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
         write(fds[1], postblur, height * width * 3);
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
gcc -c -O3 -fopenmp -DLODEPNG_NO_COMPILE_DECODER -DLODEPNG_NO_COMPILE_DISK -DLODEPNG_NO_COMPILE_ANCILLARY_CHUNKS -DLODEPNG_NO_COMPILE_ERROR_TEXT -Wall -Wextra -x c lodepng/lodepng.cpp -o lodepng.o
gcc i3lock-fancy-rapid.o lodepng.o -lX11 -fopenmp -o i3lock-fancy-rapid

$ ./i3lock-fancy-rapid 5 3
i3lock: unrecognized option '--raw'
i3lock: Syntax: i3lock [-v] [-n] [-b] [-d] [-c color] [-u] [-p win|default] [-i image.png] [-t] [-e] [-I timeout] [-f]
^C

System: Ubuntu 19.04/disco on Lenovo Thinkpad T440p.

$ uname -a
Linux ubuntu 5.0.0-25-generic #26-Ubuntu SMP Thu Aug 1 12:04:58 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 19.04
Release:	19.04
Codename:	disco

When running i3lock-fancier-rapid 5 3 in terminal, I am seeing i3lock error, that the --indicator option is not recognized. Any suggestions?

There is no problem with i3lock-fancy-rapid in Ubuntu 18 LTS but in 20.04 LTS, got this error after unlocking the screen.

$ i3lock-fancy-rapid 5 3
...
~/build/i3lock-fancy-rapid master
=================================================================
==42054==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 4864 byte(s) in 19 object(s) allocated from:
    #0 0x7f4fd4be2bc8 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)
    #1 0x7f4fd3e572f4  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x212f4)

Indirect leak of 1184 byte(s) in 37 object(s) allocated from:
    #0 0x7f4fd4be2dc6 in calloc (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x10ddc6)
    #1 0x7f4fd3e5793c  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x2193c)

Indirect leak of 341 byte(s) in 34 object(s) allocated from:
    #0 0x7f4fd4b6b3dd in strdup (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x963dd)
    #1 0x7f4fd3e56b64 in FcValueSave (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x20b64)

SUMMARY: AddressSanitizer: 6389 byte(s) leaked in 90 allocation(s).

I built i3lock-fancy-rapid from source pulled from Github master.

Edited: Before i3lock-fancy-rapid worked with i3 normally but it's no longer working after upgrading to Ubuntu 20.04. Executed i3lock-fancy-rapid from command line like above, I got the error.

Hi, there. Nice wok!

I help package it on GURU, which is an official repository of Gentoo Linux. The package is called x11-misc/i3lock-fancy-rapid.

The steps to install it are as follows:

# install a repository management tool
sudo emerge --ask --verbose app-eselect/eselect-repository
# refresh the repository list
sudo eselect repository list
# enable guru
sudo eselect repository enable guru
# sync guru
sudo emerge --sync guru
# install betterlockscreen_rapid
sudo emerge --ask --verbose x11-misc/i3lock-fancy-rapid

This will benefit Gentoo users. It would be very appreciated if you add this information to the readme file.

Feel free to close this issue.

There is no feature for adding images to compose with the screenshot. Also lacks other features from original i3lock-fancy.

Is it possible to do pixelation rather then blurring?

I got linked this reddit thread about a 'new' i3lock modifier: corruptor.

It looks very fancy (see screenshot), but it's way too slow for me, when using regular i3lock. Would it be possible to get a corrupted screenshot as lock screen, but fast?

Corruptor repo

Summary

Hey yvbbrjdr,
I3lock-fancy-rapid does not validate arguments. If you set an negative radius or time strange things happen.

Steps to reproduce

./i3lock-fancy-rapid -x -y where x,y >0

Solution

Check if radius or time are >=0.

Regards,

deltaxflux

Even after following the README, its not working!

I'm currently surveying the different blurring lockers for performance. This one takes about 330ms on my machine, whereas https://github.com/karulont/i3lock-blur (which uses a fragment shader) takes less than 200ms.

Here's the output:
gcc -lX11 -fopenmp i3lock-fancy-rapid.o lodepng.o -o i3lock-fancy-rapid
i3lock-fancy-rapid.o: In function 'main':
i3lock-fancy-rapid.c:(.text.startup+0x5f): undefined reference to 'XOpenDisplay'
i3lock-fancy-rapid.c:(.text.startup+0x71): undefined reference to 'XDefaultRootWindow'
i3lock-fancy-rapid.c:(.text.startup+0x8d): undefined reference to 'XGetWindowAttributes'
i3lock-fancy-rapid.c:(.text.startup+0xdd): undefined reference to 'XGetImage'
i3lock-fancy-rapid.c:(.text.startup+0x194): undefined reference to 'XDestroyWindow'
i3lock-fancy-rapid.c:(.text.startup+0x19c): undefined reference to 'XCloseDisplay'
collect2: error: ld returned 1 exit status
Makefile:7: recipe for target 'i3lock-fancy-rapid' failed
make: *** [i3lock-fancy-rapid] Error 1

I'm on Ubuntu 17.10. libx11-dev is installed.