Hi Kristjan, And thanks for the report.
Kristjan <[email protected]> (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)" > > 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 > > Workaround: > * sudo usermod -aG render $USER (or: sudo adduser $USER render) > * logout/login > > This likely affects desktop installations where the user was created > during the installation process, preventing users from using Vulkan or > GPU-accelerated applications without elevated privileges. 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. Cheers, -- Cyril Brulebois ([email protected]) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
