Can you report as a feature request to support the user icons just like lightdm does? seems like to be a standard, the elive tool to create users already does that, and as a bonus, uses your gravatar image if you have one!
~ ❯❯❯ grep icon /usr/sbin/user-manager
# add a lightdm icon reference for the username for its login
echo -e "[User]\nIcon=/usr/share/icons/gnome/256x256/apps/logo-elive.png" > "/var/lib/AccountsService/users/$username"
so basically that /var/lib/AccountsService/users/youruser contains a text info about the location of the icon, entrance should use this image then
Hopefully with an option for the Lucax or default theme??
That's one of my favourites too. If I figure out how to make a theme, I'll probably do a WinXP theme. Would make old computers feel like home lol
Entrance seems to work extremely stable now, like I'm using it instead of lightdm. I'm fine with the randomized icons - in fact, I'd prefer it to be randomized lol
First boot....and the subsequent ones, which were first boots too as it never finished.
Reverting to lightdm solved it ..... haven't retried yet with "entrance"
Edit
Restarted with "entrance" and no problem whatsoever so DANG !! not reproduceable.
Hopefully a fluke and won't happen again.
Just reproduced the situation.
I set /etc/entrance/entrance.conf to the user me (antares), with choice Enlightenment and enable autologin.
Everything works fine and boots into E23, albeit that now the shutdown, reboot suspend, hibernate options are greyed out. only "lock" and "logout" are allowed.
If I then disable autologin (as it was before boolean = 0) the hung situation on boot occurs. There are no errors on F12 though.
I need to change the .conf file again I suspect but it beats me why this happens as the settings are back to what they were before.
Editing the conf file and setting the bool for "ask password" to 0 allows a normal startup through entrance.
I notice on that "plymouthd" keeps running on the machine that boots with "entrance" taking up to 60% CPU.
When using "entrance", "plymouth" doesn't quit and lies at the base of the boot problem.
I've seen the same 2 messages again in F12 at that moment. "A start job is running for Hold until boot process finishes up (32s,/no limit)"
Switching to lightdm makes it go away on boot as it should.
entrance is not considered "stable" so we should make sure that the issue happens with lightdm to say that there's an issue with Elive
in any case sounds like we have a bug in entrance, which is good to know / report it in order to have it fixed
So i have checked the code and in the systemd service file for entrance, which is a copy of the lightdm one for compatibility reasons, i found this piece of code:
# replaces plymouth-quit since lightdm quits plymouth on its own
Conflicts=plymouth-quit.service
After=plymouth-quit.service
looking at the comment, seems like lightdm makes sure to stop plymouth, but should be not the case of entrance so sounds like this code is not needed and may confict (in other words, it may be the cause of the issue)
if you want to test:
apr --purge entrance
apir entrance
it is not tested, but maybe you don't have the issue with plymouth anymore (or maybe we have another now )
Without removing/purging but simply not using entrance through "dpkg-reconfigure entrance" and enabling lightdm solves the issue i.e lightdm turning off plymouth is not overridden.
The trouble is that this plymouth issue does not happen all the time. Looks like it only happens when entrance has a new/changed configuration.
Which would also be the case on a first boot if it was already there after an upgrade.
So: For now it's not advisable to keep "entrance" installed when upgrading i.e use it on first boot until the issue is fixed.
Topic
It seems to be going off topic but is actually a side step. I ran into this whilst looking into the "unable to reboot/shutdown" issue i.e setting Entrance to auto-login and back again.
So: IMO that shutdown/reboot issue is related to "autologin" being used in the live/install/upgrade session.
since systemd is a paralel booting system, processes may run in different times, which makes the issue happens "sometimes", that's why the .service file needs to include the correct specific "dependencies" (before run X, after to run X, better if run X before, etc...). On this case, I removed an entry about plymouth which should conflict (unless we add the code in entrance to close plymouth, which is not hard), but as said, I have not tested it and probably more improvements needs to be made on the .service file of entrance
it is not (unless you specifically added it in the packages-list-to-maintain)
UPDATE: Entrance issues are not directly related (ATM) with the Elive system itself, but is good to keep it updated and fixed for the future, so i moved the last posts of the other thread to this one specifically for entrance issues
@triantares confirmed, autologin in entrance makes those "system" options to be grayed out, this means that the autologin is starting in a different mode than the normal mode and it lacks some privileges / options, for compatibility they shoudl use the same login system... can you report the issue with autologin to entrance ?
Will do, although this opens the question whether it's an entrance or enlightenment issue.
...... there's more. like setting a "user" as remembered not working and not getting .edj files to work as a personalized background (.png works but OTH .jpg does not)
I had another issue in entrance tests: it makes entrance to always restart (like every minute or a similar time), same if you are logged in E, the cause is entrance receiving signal 15 (something like a restart requested, aparently by systemd), im trying to improve the .service file and seems like it is not restarting now... updated packages are now available
seems like to be a standard, the elive tool to create users already does that, and as a bonus, uses your gravatar image if you have one! 
only "lock" and "logout" are allowed.
