Jorge Almeida wrote: > On Tue, Apr 14, 2020 at 7:29 PM tastytea <tastytea+gen...@tastytea.de> wrote: >> On 2020-04-14T19:16+0100 >> Jorge Almeida <jjalme...@gmail.com> wrote: >> >>> "Use elogind to get control over framebuffer when running as regular >>> user" >>> >>> Could someone explain what this entails? What happened before this USE >>> variable was created? What will I miss if I disable it? >> ConsoleKit2 is unmaintained, elogind is the replacement. If you don't >> use systemd, read `eselect news read new` or >> <https://www.gentoo.org/support/news-items/2020-04-14-elogind-default.html>. >> > OK, I get it. I don't use ConsoleKit2, and I have "-consolekit" in > make.conf, so it's just a matter of adding "-elogind" to make.conf. I > understand why suddenly updating world wanted to pull PAM. > What I still would like to understand is what are the consequences of > [not] enabling this stuff regarding xorg-server. What kind of control > over the framebuffer is meant by the USE description quoted above? > > Thanks > > Jorge > >
I'm not sure I can answer all your questions but I'll try to provide some info. Since it seems you are not using consolekit, PAM or friends, you must do everything manually when it comes to permissions. Whether it is consolekit or elogind, it basically allows users to do certain things that normally only root can do. Example, mount USB sticks etc. It seems, to me at least, that it also allows graphical environments to use elogind to manage the session when logged in as well. I started a thread about this a while back that should be archived somewhere. I'll also add this for those who use elogind already, OP, this may interest you as well. I did my usual Sunday upgrade last night. When you logout of whatever GUI you use, restart elogind before logging back in. I don't recall seeing elogind in the list, it was a long list, but it seems something upgraded that needs elogind restarted to work right. Here is what I noticed that wasn't right. I could not mount anything external, USB sticks or my external backup drive. It would give me a error about permissions. Logging into Konsole took minutes instead of seconds to accept my password. Logging into the GUI took a long time to, much longer than usual. Any program that asks for a password, it to took forever to start if it started at all. Some just died off and went to /dev/null. As soon as I could, I logged out, went to the boot runlevel, restarted elogind since it is in the boot runlevel and everything went back to normal. OP, this may give you some idea what all elogind does or has a effect on. If you have consolekit, PAM, elogind and such disabled, I'm not sure what if anything will change. I'd think by disabling elogind, you would be back to like you was before it *attempted* to add it. In other words, nothing changes. That's my thinking. Dale :-) :-)
