* Ibukun Olumuyiwa ([EMAIL PROTECTED]) wrote:
> Is your .xinitrc executable? This is off the top of my head, but I think
> elogin doesn't use the shell to execute sessions. Will have to go back and
> look at the code though.
>
It was not, so it was part of the problem.
> Kill elogind. (e.g. killall elogind). It will automatically kill its child
> processes (including the X server) before shutting down. This IIRC is the
> same behavior exhibited by kdm (not sure about gdm).
It does, I was just not waiting long enough.
I now have a very strange behavior:
- I can launch e17 with startx
- if I try to launch it with elogin, it works a little: e get started,
but all my .xinitrc stuff does not happen (I think it is a path
problem, need to check that). I attach my .xinitrc and my mysetting
files, so that you can have an idea of what is going on
- if I lauch "mysetting" manually, e17 suddenly quits and I'm back to
elogin screen
- I cannot lauch e again (either through elogin or startx) until I
- mv .e away
- restart e
- get my desktop subfolder back into .e to have my default iconbar and
bg
I'm a bit confused at what is happening. I could try rebuilding e to the
latest version, but I do not remember much changing recently (and the
problem comes only when I launch e through elogin).
Thanks,
Alan
--
The hacker: someone who figured things out and made something cool happen.
#xmodmap -e "keysym Alt_R = Multi_key Alt_R"
#xmodmap -e "keysym Alt_L = Multi_key Alt_L"
xset s off
xset -dpms
xset -b
xmodmap -e "keysym Super_L = Multi_key"
xmodmap -e "keysym Menu = Multi_key"
xmodmap -e "clear lock"
#xmodmap -e "keycode 66 = Escape"
xmodmap -e "keycode 66 = Control_L"
xmodmap -e "add control = Control_L"
#exec /usr/X11R6/bin/sawfish
mysetting
exec /usr/local/bin/enlightenment
#export GDK_USE_XFT=1
#exec gnome-session
#exec xterm
#!/bin/sh
mylogs
Eterm -g 82x24+68+0 -e /home/schmitta/perso/mysu/suroot su - &
gkrellm &
xpad &
