Hi,
Entrance installed correctly on my laptop.
But I got an error when running apug. It uninstalled what I believe is some wireless card driver to replace it with a newer version, that did not compile properly.
Nonetheless, my wireless connection still works normally.
yes, I have the same and think it's a dkms issue but if I do: "sudo dkms status"
I get, among others:
broadcom-sta, 6.30.223.271: added
Broadcom is a proprietary binary module that is in fact in the non-free sector.
I wrote somewhen earlier about broadcom, no (?)
Sure, but I didn't see your post at first.
I'm sorry I contributed to make this forum a bit more messy.
As a solution I just uninstalled the broken package (not needed on my computer).
maybe is an issue in entrance, so maybe doesn't include integrations like lightdm does for add this functionality 
, I assume it requires a bigger research
could be good if we are able to use back entrance, which could mean entrance themes in a login manager like in Gem 
theming should be not an issue, but first we need to make sure that is a realiable / working / usable login manager 
mmmh, i don't think in any reason of why this can be possible, but if you switched the WM the feel can be entirely different!
BTW e23 should consume the same as e16 (no more) , in fact cairo-dock is an extra memory consumption thing
can you report it?
We did, 
It was going to be looked into.
I've been using it lately and it was working super fine (except for the icon of the users randomly turning in 1€ coins lol). Also rememeber each user's last session
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
That's because they built-in a mind reader ....... 
Good, so that indeed has been seen to.
Umm, not very clear who "you" is here.
IMO @stoppy98 coined (pun intended) the issue here so would be the obvious. 
Hi guys,
I am really excited of your effort to bring back entrance to elive.
Going to give a try...
thanks
Why do you use ap* commands in user mode instead of apt?
They're aliases to simplify commands like "apt-cache search" into "apse" and also never forgetting the "sudo" .
Do "alias |grep apt" to see them all.
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
Should Entrance: development issues (boot process, login privileges, etc) be merged into this thread?
mentions: @triantares, @thanatermesis
[quote="TheTechRobo, post:33, topic:1783"]
merged into this thread?
definitely. 
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"
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.
Ok so there's 2 things to consider:
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.
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)
