On Wed, May 26, 2010 at 09:39, David C. Rankin
<drankina...@suddenlinkmail.com> wrote:
> Guys,
>
>        I ran into this problem the last time I worked with e17 ~ 9 months or 
> so ago.
> The problem is when the screensaver activates and the e17 lock is activated,
> there is no way to unlock the session without killing X. There is no 
> individual
> lck/lock process to kill. The only workaround is to use 'xlock' as the lock
> process which makes me miss out on the great looking e17 unlock screen.
>
>        I can't recall where we left the issue last, but has there been any 
> progress on
> this issue? My setup is E17-svn-r48925 on opensuse 11.0 using dmitry's rpms. 
> Any
> thoughts, tests, workarounds, etc.. would really be appreciated.

Sounds like a PAM problem for me. E17 normally uses PAM for the
password, so you should check your PAM settings in you distro, or if
the packages of E you're using are properly built with PAM support.

------------------------------------------------------------------------------

_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to