You are not logged in.
Alright here is what happened. I followed this guide to install Arch via netinstall (this is my first time successfully installing Arch by the way), and then installed e17 using the command
pacman -S e17-svn e17-extra-svn. I then installed Elsa (I was going to use GDM but pacman was going to install all of Gnome just for GDM and that isn't happening) and edited /etc/inittab as the wiki said to. I also installed connman and replaced network in DAEMONS in /etc/rc.conf with connmand. Now here is the problem. I can not open any applications. I only have eterm and mplayer but neither will open. I do not know if it is a glitch in e17 or if there is something with Elsa or an Arch specific bug or what. Also I can not find the ConnMan module to use it. I do not know if that is just a bug or if I am missing something simple or what. I can not open a terminal to revert the changes to /etc/inittab so that I can access CLI on boot and I can not think of another way to revert them. I would like to avoid reinstalling as it took me quite a while. Any help is appreciated and if I forgot any information that is needed please ask.
Last edited by DiscipleOfDante (2012-03-25 06:28:46)
Offline
Did you try ctrl+alt+f1?
Offline
Thank you I didn't think of that. I managed to get some programs install that run, so now I have a working terminal and web browser. Now I just need to get Connman working (namely find the Connman module in E17) and then I am good.
Last edited by DiscipleOfDante (2012-03-25 13:51:58)
Offline
I'm just trying out E17 myself as an alternative to lxde/openbox. Very interresting! By the way, wouldn't wicd be possible instead of connman?
Offline
It is but E17 is supposed to have a native module for Connman so I am trying to get that to run. E17 is definitely not perfect, but I prefer it to anything else, excluding KDE. I found the module is called connection manager, but I can not get it to work.
Last edited by DiscipleOfDante (2012-03-25 15:21:21)
Offline
I don't think Elsa is finished or 100% reliable. If it works for you, great, else, stick to the .xinitrc method ( exec enlightenment_start, or exec ck-launch-session dbus-launch --exit-with-session enlightenment_start, whatever you need).
Connman is recommended as said because of the native connman module. You can also use wicd, but then you need a system tray, right? You can use the systray module on a shelf, works fine.
Good luck.
Offline
None of the network managers (connman networkmanager wicd) are working for me. I do not know why (Elsa is working for me by the way).
Offline
Edit: Didn't see the above post
Last edited by Tux the penguin (2012-03-25 22:38:28)
I don't suffer from insanity. I enjoy every minute of it.
MSI CR600 / 3GB Memory / 320GB HDD / Intel Pentium Dual-Core CPU T4200 @ 2.00 GHz | Archlinux x86_64
Offline
None of the network managers (connman networkmanager wicd) are working for me. I do not know why (Elsa is working for me by the way).
Just to be sure, log in using startx and .xinitrc, then try the networking. E17 is a window manager and doesn't/shouldn't prevent stuff like networking to do what it does, but I've seen trouble with elsa and stuff like sudo not working.
Last edited by VCoolio (2012-03-26 16:13:15)
Offline
okay startx + xinitrc didn't make a lick of difference. Please use my other thread by the way. (I made another one for this specific issue in case someone is having the same issue and searching it you can find it here)
Last edited by DiscipleOfDante (2012-03-26 17:21:04)
Offline