On Sat, 17 Jun 2017 14:23:37 +0200 michael bouchaud <michael.bouch...@gmail.com> said:
hey yoz! how far are you along with this entrance re-do? my thoughts are as follows: just re-use enlightenment itself as a login manager. why? it will have all the multi-screen, dimming/dpms, input calibration, power management (shut down, suspend, suspend on lid close etc.) stuff that you'd want a login screen to be able to do... what it needs added is some work to lock it down security-wise a bit (no main menu, no bindings to do anything not needed/allowed by the login manager), the actual "login screen/widget" and associated code that might list users and get their "avatar" images, list available sessions etc., the actual session spawning code, and a "login profile" that has all of this configured. it sounds a bit heavy but in the end i suspect it's the best way to re-use a lot of the above stuff that you'd have a fully done login manager that also can do all your other necessary power managing and so on stuff while you are not logged in yet. on login this e would cleanly shut down and then have the user session start (take over the display). even better (imho) is it could self-configure the same way e does with all the same infra. you just need to "auth as root" first - we do this for desklock already (auth as yourself) so... we can recycle a lot. if you do this it brings up a settings dialog to configure stuff and maybe "unlocks" gadgets pre-configured on the screen allowing you to add, remove or drag them around etc... (until you hit ok then it locks up again). if you want to add a battery display/meter to entrance you'd have to code all the battery back-end stuff again, the system controls (suspend/shut down etc.). for wayland -> same for dpms/blank/dim code, input setup code (kbd layouts, on screen keyboard etc.). a login manager that is really nice to use for users needs a lot of these elements that e already has. > Hi, > > That's sound go to me ear entrance is alive. If you need my help don't > think about it twice ! > Entrance is in this shape today because I'm working on a new version of > entrance where I go far beyond the goal of this actual version. I need to > rework about everything and today I don't have what I expected to share, > So... Good to know you try to provide this one whithout bug. > To clear things about where I go, my main goal is to provide a bootsplash > and a login manager where we secure the userland. It's just about replace > all piece of software your distrib and systemd provide with user > interaction at boot time. > My main goal is security, X11 is a joke about it. Wayland is a cleaner way > for multi-user desktop use. > About the current code, the gui is almost good but done in a new way where > all object is defined by theme not by the app (as enlightenment, > terminology does...). This enhance theming possibilities. I think I will > keep it in this way, just to let you know. > > > Regards > > 2017-06-17 4:10 GMT+02:00 William L. Thomson Jr. <wlt...@o-sinc.com>: > > > For good or bad entrance is alive again. It actually only had 2 major > > issues, but a fair amount of other issues. Which likely still has more. > > I will continue to work on entrance, and address any issues, etc. > > > > Main issues: > > > > 1. Socket file was created as root via daemon, but client is run as > > nobody. Thus client failed to connect to server due to socket file > > permission issues. > > > > 2. Pam /etc/pam.d file needed updating. > > > > That was basically the main show stoppers. Still much to be fixed, > > improved, etc. Not to mention ability to log into Wayland, or start a > > Wayland session without requiring X/Ecore X. Which presently entrance > > is bound to X/Ecore X. Though it should be able to start Wayland > > sessions in theory. > > > > Still a few more things to address and I will do a tag/version release. > > Not sure if I will do binaries, deb/rpm/tgz. Likely just do source > > release. For now it is usable for me at least, no more sddm :) > > > > For anyone interested > > https://github.com/Obsidian-StudiosInc/entrance > > > > Running > > > > 11948 ? Ss 0:00 /usr/sbin//entrance > > 12094 ? S 0:00 /bin/bash --login -c > > /usr/lib64/entrance/entrance_ck_launch /usr/bin/enlightenment_start > > > /home/wlt/.entrance_session.log 2>&1 > > 12097 ? S 0:00 /usr/lib64/entrance/entrance_ck_launch > > /usr/bin/enlightenment_start > > > > -- > > William L. Thomson Jr. > > > > ------------------------------------------------------------ > > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > > -- > Michaƫl Bouchaud > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel