After exiting awesome and logging back in using udm, xss-lock -- slock process takes 100% of one core,
Issue #9
new
I'm using awesome wm on Arch. My DM is udm. If I exit awesome and log back in, "xss-lock -- slock" process starts taking 100% of one core. I have to kill it and restart awesome (It's started by awesome configuration file).
I really like xss-slock, it's a good way of locking my screen using slock after waking up. Nice work!
I was also having this problem; looks to be fixed in commit 1e158fb. Try using xss-lock-git from AUR instead of xss-lock: https://bbs.archlinux.org/viewtopic.php?id=187480
On that note: @raymonad any chance of a 0.4.0 tag/release so the maintainer can update xss-lock?