On Monday 11 August 2008 20:42:01 Nathan Spaeth wrote:
> Get enlightenment's pid and run:
> gdb -p "e17sPID" #Where e17sPID is e17s pid
> then use the command: call e_desklock_hide()
> Finally, either use continue (to let the process continue), or quit,
> to get out of gdb (and let the proces
On Monday 11 August 2008 17:19:36 Leandro Santiago wrote:
>>only returns with
>> Ctrl+Alt+Backspace :-)
On Mon, Aug 11, 2008 at 11:49 AM, Alan McKinnon wrote:
>When the desktop won't
> unlock, Ctrl-Alt-F1 to a console and log in as that user. Get the PID of the
> process called enlightenment and s
> It seems PATH_MAX isn't defined on your platform or you didn't include
> the correct headers for any reasons. Try to search /usr/include for
> PATH_MAX. For local testing you could just include that header file
> where it's defined or define this to get it compiling (as workaround):
>
> /* # cha
On Monday 11 August 2008 17:19:36 Leandro Santiago wrote:
> Hello to all.
> I'm having problems with the system of locking the e17 desktop.
> I compiled enlightenment and the entrance to support the pam.
> But whenever I try to unlock the desktop user - but on a root session
> works - is returned a
= uid=7778 euid=7778 tty= ruser=
rhost=localhost user=remoto
The funny is that the entrance normally works.
I'm using enlightenment compiled by me yesterday evening (20080811) in
slackware 12.1, installed by the script easy_e17.
Is there any way to use the desklock without using the PAM,
