You mustn't launch elsa_client. Elsa_client was used to catch some user
inforamtion (login, password, ...), so use less memory if you don't need it
(autologin). Don't make some scripts to launch elsa_client, it's elsa's job.
She cleans the things between logons, with restarting X. When X will be
ready, elsa_client is launched.
ps: I think your version isn't up to date.
2011/2/7 C Anthony Risinger <anthony@...>
> On Fri, Feb 4, 2011 at 11:33 AM, Mister Olli <mister.olli@...>
> > I currently experience the following behaviour.
> > - Starting & logging in via elsa works perfectly. My e17 is as stable
> > as starting X manually
> > - When I finish enlightenment all windows get closed, my screen remains
> > black and mouse curses is a little X
> > You can find all elsa log messages (from the log file) until
> > this point in the file called 'elsa.log__hanging_e17_exit'
> i don't know if this is the case for you, but i believe it could be.
> elsa's architecture seems to have changed a bit, it feels for the
> better, but it's wasn't apparent at first what needed to be done to
> get it running. it seems that `elsa` is now a daemon, that runs
> forever (in contrast to other login managers) as root. you then use
> `elsa_client` as your user to connect to the server and start a login
> session. when the system first boots, i think `elsa` does this for
> you, but not after you logout... it looks exactly as you've described.
> so, after you logout, try switching to another VT and running
> `elsa_client`; this works for me every time. the problem i'm having
> is trying to wire this whole process up to inittab... i can start
> `elsa`, but it's not easy to wire up `elsa_client`... im trying to
> work out some kind of wrapper script to handle this properly, possibly
> with cgroups; im also in the process of switching to systemd, and that
> might handle it better than traditional init.
> C Anthony