Tomasz Torcz <tomek@xxxxxxxxxxxxxx> a écrit:
>> I am running this rawhide box using init 3
>> (/lib/systemd/system/multi-user.target) as the default init level, and I
>> am running the desktop by doing:
>>
>> xinit /dev/gnome-session
>>
>> So somewhere something is failing to make my user be properly acl'd
>> onto the /dev/dri/card0 device, and I have no idea what I should do to
>> have it fixed. Anyone has got an idea?
>
> Devices needing ACLs are marked by "uaccess" TAG in udev rules. For
> /dev/dri/*, the rule is in /usr/lib/udev/rules.d/70-uaccess.rules:
>
> SUBSYSTEM=="drm", KERNEL=="card*", TAG+="uaccess"
>
> You should verify this with "udevadm info --name=/dev/dri/card0 --query=property".
I think the uaccess tag has been properly attached to the device:
$ udevadm info --name=/dev/dri/card0 --query=property
DEVNAME=/dev/dri/card0
DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
DEVTYPE=drm_minor
ID_FOR_SEAT=drm-pci-0000_01_00_0
ID_PATH=pci-0000:01:00.0
ID_PATH_TAG=pci-0000_01_00_0
MAJOR=226
MINOR=0
SUBSYSTEM=drm
TAGS=:seat:uaccess:
USEC_INITIALIZED=549569
$
> Yet, the way you start graphical desktop is suspicious at least.
Why? Running rawhide can be a bumpy ride. So I like to be able to
launch my gnome session myself, so that when something goes awry in the
graphical realm, I still can easily log onto the box w/o the graphical
stack and send emails to devel@xxxxxxxxxxxxxxxxxxxxxxx and ask for help.
:-)
So I think launching the graphical environment like this (or in a
similar way) should work. And it has worked until recently.
> I'm not entirely sure if logind registers new graphical session and if
> ACL are set.
What's the mechanism that sets the ACL for a given user, for
/dev/dri/card0 exactly?
> This, in turn, you can verify by "loginctl" with various commands - list-sessions,
> session-status etc.
I tried, but haven't found anything relevant to ACLs in there.
--
Dodji
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
