2018-03-21 8:24 GMT+01:00 Simon Lees <sfl...@suse.de>: > Be aware that this release has issues with the lock screen not > unlocking, we are working on a fix and 0.22.3 will be out in the coming > days fixing this issue. >
Until then, the only way to recover your session right now, as posted in archlinux issue tracking the upstream one, is to go to a console (CTRL+F2) and "kill -SIGSEGV enlightenment" , at which point the "white screen of death" will appear and after resuming from it, the screenlock will be gone. Which makes me think, is this a desired behaviour too? After killing enlightenment and resuming the session, shouldn't it return automatically to the screenlock if it was in that state? Looks like a security issue for me. Imagine I have a terminal emulator with "su root" inside enlightenment, and I also have a terminal opened in CTRL+F2 with my unprivileged user. If I leave my PC unattened, somebody could access my user through CTRL+F2, and then basically escalate privileges to root by killing -SIGSEGV enlightenment and accessing the terminal which was under lockscreen before but which is now unlocked. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
