| 1 |
On 3/22/2019 4:32 PM, Piotr Karbowski wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I'd like to propose doing the following: |
| 5 |
> |
| 6 |
> - Keywording elogind on missing archs |
| 7 |
> - Making elogind a global USE flag |
| 8 |
> - Switching desktop profiles to elogind from consolekit while still |
| 9 |
> preserving -suid +elogind on xorg-server for those that does not use |
| 10 |
> desktop profiles (systemd profiles users not affected) |
| 11 |
> - Making pambase always install the configuration for pam_elogind.so, |
| 12 |
> the same way it does for pam_gnome_keyring.so at this very moment, |
| 13 |
> effectively removing elogind USE flag from it. |
| 14 |
> |
| 15 |
> What do you all think about? |
| 16 |
> |
| 17 |
> -- Piotr. |
| 18 |
> |
| 19 |
|
| 20 |
What are the implications, if any, of using DMs which are not aware of |
| 21 |
{,e}logind? Do they work without modification? |
| 22 |
|
| 23 |
Afaik, only sddm or, now, gdm even have an elogind USE flag. |
| 24 |
|
| 25 |
All other DMs have consolekit support but unknown elogind status. |
| 26 |
|
| 27 |
Brian |
Archives