From: bigon@debian.org
Le 28/12/25 à 11:50, Cyril Brulebois a écrit :
> Hi Kristjan,
>
> And thanks for the report.
>
> Kristjan (2025-12-28):
>> After a fresh Debian Testing installation (installer build 20250803+deb13u1)
>> with GNOME desktop (task-gnome-desktop), the created user was not added to
>> the 'render' group, although the group exists in the system.
>>
>> What led up to the situation?
>> * Standard Debian Testing netinstall with GNOME desktop task selected
>> * User created during installation process
>>
>> What was the outcome?
>> * User is member of: cdrom floppy audio dip video plugdev users netdev
>> scanner bluetooth lpadmin input
>> * The 'render' group exists (GID 992) but is completely empty
>> * Vulkan applications fail with errors like:
>> "Gdk-WARNING: Vulkan: Could not open device /dev/dri/renderD128:
>> Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)"
This is quite weird as with a default installation (using systemd and
logind) a local user should have all the necessary rights and everything
should work out-of-the-box.
>>
>> What outcome did you expect?
>> * Desktop users should be automatically added to the 'render' group during
>> installation, similar to how they are added to the 'video' group
>> * The 'render' group is required for GPU computing and Vulkan applications
>> to access /dev/dri/renderD* devices
>> [...]
Did you check that your user is properly opening a logind session (with
loginctl)?
> Over the past few years, the trend has been to shrink the number of
> groups set up via the installer, because other components can do that
> automatically (and not just for the first user).
>
> I'm cc-ing Laurent, who contributed such changes.
Yes I still think we have to many default groups already
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
