Hi Michael,

I found the time to do some more troubleshooting on my current machine.
I'm trying to explain my results here in detail, if there's anything you
don't understand please/ reproduce just ask me for more details ;-)

First of all, logging on @/dev/tty1 and starting e17 via 'startx' works
perfectly. I can do this at least 5 times in a row.

I wrote myself an init script for elsa. It is called 'enlightenment' and
you will find it attached to this email.
I also attached my current configuration file (called "elsa.conf").

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'
  
- When I go back to /dev/tty1 I can see a few user processes to be still
  running. These are
        gnome-pty-helper
        tilda
        gnome-keyring-daemon
        dbus-launch
- After killing all these processes (order doesn't matter), X is doing 
  something, and my /dev/tty1 switches back to X. However the screen 
  remains black. 
        You can find all elsa log messages until this point (including
        the previous messages) in the file called 
        'elsa.log__after_killing_remaining_user_processes'

Regards,
Mr. Olli

On Fri, 2011-01-28 at 23:50 +0100, michael bouchaud wrote:
> Still have problems with elsa, or ?
> surely it isn't perfect but ...
> 
> 2010/12/29 Mister Olli <[email protected]>
>         hi... 
>         
>         
>         >         While doing further testing I found two more
>         problems
>         >         regarding elsa,
>         >         and I'm unsure if they are related to my system or
>         elsa
>         >         itself:
>         >         1) When logging in with elsa --> exiting e17 -->
>         login with
>         >         elsa again
>         >           my screen remains blank. I see no entry in any
>         logfile that
>         >         points
>         >           me to what is just going wrong.
>         >
>         > I have break the loggout recently so X are still here login
>         screen are
>         > spawn but no auth are made.
>         > So it's a bug :D. But I prefer change some things before
>         correct this.
>         > be patient ^^
>         
>         
>         is it already fixed *CURIOUS* ;-)
>         I've recompiled elsa within the last hour, and now I'm unable
>         to exit an
>         enlightenment session. When hitting 'exit' the screen turns
>         blank, I can
>         see&move my mouse cursor. Elsa does not start up, neither can
>         I kill
>         xorg by strg+alt+del. 
>         
>         >
>         >
>         >         2) When logging in with elsa --> switching to tty0
>         -->
>         >         switching back
>         >           to X freezez my system with tty0 still on screen.
>         I have to
>         >         switch
>         >           off completly, no shutdown method works
>         >
>         > I don't think it is a problem with elsa. Don't you have the
>         same
>         > probem with xinit or others ?
>         
>         Seems to be somehow elsa related. When using xinit/startx I
>         can
>         start&exit enlightenment as oftern as I want. Even with logout
>         of the
>         user on the tty.
>         
>         Regards,
>         Mr. Olli
>         
>         
> 
> 
> 
> -- 
> Michaƫl Bouchaud
> 

#!/sbin/runscript
# Copyright 1999-2007 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2

depend() {
        need dbus acpid
}

start() {
        ebegin "Starting enlightenment"

        /usr/sbin/elsa

        eend $? "Failed to start enlightenment..."                      
}

stop() {
        ebegin "Currently not supported"
        # TODO
        eend $? "Failed to stop local"
}
group "Elsa_Config" struct {
    value "session_path" string: "./:/bin:/usr/bin:/usr/local/bin";

    /* X server path */
    value "xinit_path" string: "/usr/bin/X";
    /* X server args */
    value "xinit_args" string: "-nolisten tcp -br vt7";

    /* xauth path binary */
    value "xauth_path" string: "/usr/bin/xauth";
    /* xauth file for server */
    value "xauth_file" string: "/var/run/elsa.auth";


    /* Commands executed when starting a session */
    value "session_start" string: "/usr/bin/sessreg -a -l :0.0";
    /* Command executed when login. Warning xsession must be set to 0 */
    value "session_login" string: "exec /bin/bash -login 
/etc/X11/xinit/xinitrc";
    /* Commands executed when exiting a session */
    value "session_stop" string: "/usr/bin/sessreg -d -l :0.0";


    /* Commands executed to shutdown */
    value "shutdown" string: "/usr/bin/shutdown -h now";
    /* Command executed to reboot */
    value "reboot" string: "/usr/bin/shutdown -h now";
    /* Command executed to suspend */
    value "suspend" string: "/usr/bin/shutdown -h now";


   /** Start in daemon mode. This can be overriden by the command line
     *  1 = True, 0 = False */
    value "daemonize" uchar: 1;

    /* Enable numlock */
    value "numlock" uchar: 1;

    /** Bool to determine if elsa must login user with the session_login command
     *  or use xdg desktop and determine the command to use
     *  1 = desktop_file_cmd, 0 = session_login */
    value "xsessions" uchar: 0;

    /** Bool to determine if elsa must autologin user when X start
     *  1 = autologin enabled, 0 = autologin disabled */
    value "autologin" uchar: 0;

    /* The name of the user to use when autologin are enabled */
    value "userlogin" string: "myusername";


    /* Lock file */
    value "lockfile" string: "/var/run/elsa.pid";

    /* Log file */
    value "logfile" string: "/var/log/elsa.log";
}
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to