| 1 |
On 2020-07-22, Walter Dnes <waltdnes@××××××××.org> wrote: |
| 2 |
> On Tue, Jul 21, 2020 at 04:00:21PM -0000, Grant Edwards wrote |
| 3 |
>> |
| 4 |
>> Before I can try that, I apparently have to enable the elogind USE |
| 5 |
>> flag because of somthing else that changed since I sync'ed yesterday. |
| 6 |
>> |
| 7 |
>> That only requires 6 new packages (two of them are |
| 8 |
>> acct-{user,group}/polkitd, so it's only 4 new "real" packages. Of |
| 9 |
>> course every self-respecting package needs to install at least one new |
| 10 |
>> programming language -- this time it's dev-lang/spidermonkey. :/ |
| 11 |
>> |
| 12 |
>> Sheesh. |
| 13 |
> |
| 14 |
> According to news item https://www.gentoo.org/support/news-items/2020-06-24-xorg-server-dropping-default-suid.html |
| 15 |
> |
| 16 |
> * xorg-server will no longer be "suid" *BY DEFAULT* |
| 17 |
> * that means *THE DEFAULT* is to require a logind server like systemd |
| 18 |
> or elogind |
| 19 |
> |
| 20 |
> The news item also says... |
| 21 |
> |
| 22 |
>> Users who do not wish to use logind interface or have rare hardware |
| 23 |
>> that does not use KMS and because of that, require root privileges |
| 24 |
>> to operate, can manually re-enable 'suid' and disable 'elogind' USE |
| 25 |
>> flags in order to preserve the previous behavior. |
| 26 |
|
| 27 |
Yes, that's what I did months ago, and everything worked fine with |
| 28 |
Xorg using the "suid" flag and without consolekit or elogind -- until |
| 29 |
this morning, when pam refused to upgrade unless I set the elogind USE |
| 30 |
flag. |
| 31 |
|
| 32 |
-- |
| 33 |
Grant |
Archives