Norbert Melzer 64b347a30a betterlockscreen: make dunst optional ... When dunst is detected *and* awesomeWM is used (its internal notification system to be exact) then betterlockscreen waits for dunst to reply on the DBus. Due to dunstctl being in PATH through the wrapper, dunst will always be tried to reach. None of the workarounds mentioned in the awesome and betterlockscreen repos do not work with this version, as dunstctl is always called and has to time out first. In the current master of BLS there is a change that makes BLS check and env-var first, and would ignore any dunstctl in PATH. Once the new release happened this could still be used to reduce the closure size.		2023-05-13 20:28:52 +02:00
..
alock	treewide: fix typos	2022-12-17 19:39:44 -05:00
betterlockscreen	betterlockscreen: make dunst optional	2023-05-13 20:28:52 +02:00
electricsheep	treewide: make ffmpeg_4-dependant packages depend on ffmpeg_4	2023-03-13 16:42:22 -06:00
i3lock-pixeled
light-locker	treewide: remove attrPath from nix-update-script calls	2022-12-26 12:39:21 -05:00
multilockscreen
physlock
pipes
pipes-rs	pipes-rs: update license	2023-04-17 22:24:26 -04:00
rss-glx	treewide: move NIX_CFLAGS_COMPILE to the env attrset	2023-02-22 21:23:04 +02:00
slock	slock: 1.4 → 1.5	2022-11-12 20:03:37 +03:00
vlock
xautolock	xautolock: use xorg.* packages directly instead of xlibsWrapper indirection	2022-10-30 11:35:20 +01:00
xlockmore
xscreensaver	xscreensaver: 6.04 -> 6.06	2023-04-22 23:11:17 -03:00
xss-lock
xssproxy	xssproxy: 1.0.1 -> 1.1.0	2022-08-28 13:05:00 +02:00
xtrlock-pam	xtrlock-pam: use xorg.* packages directly instead of xlibsWrapper indirection	2022-10-29 12:12:32 +02:00