On 8/25/2019 7:41 AM, Pierre Labastie via blfs-dev wrote:
On 25/08/2019 04:56, DJ Lucas via blfs-dev wrote:
On 8/24/2019 9:53 PM, Ken Moffat via blfs-dev wrote:
Not sure how any of this fits with Pierre's earlier observation
about multiple users on the same machine, and frankly that part is
not my problem. Now I really WILL step away from the machine.
Goodnight, thanks for the assistance.
Goodnight. Thanks for the assistance. I think ultimately we go back to setuid
Xorg for now. We'll see what happens from there.
Well, I won't oppose that, although I do not like it: on this system, apart
from the keyboard issue with gdm, I have all DE's working (not tested
thoroughly, though), with a non suid Xorg and mountcgroupfs disabled.
For the permissions: as soon a logind is started it adds some ACL's to
/dev/dri/card0 for the logged in user (even if logged in on the console, I
think): for example:
$ getfacl /dev/dri/card0
# file: dev/dri/card0
# owner: root
# group: video
user::rw-
user:pierre:rw-
group::rw-
mask::rw-
other::---
So no need to belong to the video group.
Note that the ACL is not changed if you do 'su - new-user'.
OTOH, for the /dev/input/* files, their permissions do not seem to be changed.
But I can tell you that I have functional keyboard and mouse, without
belonging to the input group.
Yes, the input devices get associated with the seat. I'm in the same
boat. It has and does work perfectly for a regular user with only
primary group membership. I am unable to figure out why the polkit
mechanism is not working for some. My point is that we've always had
Xorg suid in the SysV book. While I am reluctant to do so, we haven't
been successful in finding whatever it is that I've missed in elogind's
introduction to the book, and I just don't think this issue should put
any more strain on the release, as it is not a regression.
There is a less desirable method for handling suid bit for the Xorg bin.
We could add a note with instructions for the suid bit in the event that
there is a problem on your particular build. For the book, I lean
towards just putting back the suid bit as it was, as I place a higher
value on the consistency between different builds, but that is strictly
my opinion. While I don't particularly like either suggestion, I suppose
all are worth consideration.
OTOH, dropping the elogind and mountcgroupfs bootscripts absolutely
should happen before release. The PAM configuration works just fine in
both user sessions and DM sessions (regardless of the seat association);
the scripts just add needless complexity.
--DJ
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
