My experience has been that it's better to start those applications before you start your window manager. Also, I've had problems when the window manager isn't "exec"'ed.
Try: swisswatch & xload & xbiff & exec enlightenment I've been running gnome-session (which usually remembers the applications you had open when you log out). So my .xsession file looks like: #!/bin/sh . $HOME/.bash_profile xrdb -merge $HOME/.Xdefaults esd -as 2 & #esd sound daemon that shares... exec gnome-session If you plan to use the gnome-session manager. First log in with enlightenment as usual. Then start the gnome-name-service, and other gnome apps like panel and gmc. Then edit your .xsession file with exec gnome-session last (it'll remember which window manager you last used). .xession should be executable (700). On 19 Jul, Cyrus Patel wrote: | | Hi guys, | | I recently made the switch from fvwm to enlightenment as my default window | manager. | | Currently, my .xsession file looks like this and works fine: | | enlightenment | | But when I tried to add other progs at startup using the new .xsession file: | | enlightenment & | swisswatch & | xload & | xbiff & | | it wouldn't work. My .xsession-errors file is as follows: | | Imlib Init | X connection to :0.0 broken (explicit kill or server shutdown). | Xlib: connection to ":0.0" refused by server | Xlib: Client is not authorized to connect to Server | Error: Can't open display: :0 | Xlib: connection to ":0.0" refused by server | Xlib: Client is not authorized to connect to Server | Error: Can't open display: :0 | | Am I going about this the wrong way, is there a better way to do it? | | Thanks alot in advance | -- Eric G. Miller Powered by the POTATO (http://www.debian.org)!
