Dear Maintainer,

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
* 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.

Best regards
Kristjan

Hi Kristjan,

And thanks for the report.

Kristjan <kristjan.schmidt@googlemail.com> (2025-12-28):

(or: sudo adduser $USER render)

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,

Dear Maintainer,

please do not add the default user to yet another group by default.

This is the list of groups that a newly created user is added to:

```
# adduser newuser

# su - newuser

$ groups
newuser users
```

And everything works, if the system is using systemd/udev.

If someone needs to have their user be a member of the render group, due
to using 3rd party packages not packaged in debian, then they need to
configure their group membership accordinly, instead of pushing this
change onto all users of debian.

Le 28/12/25 à 11:50, Cyril Brulebois a écrit :
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.
Did you check that your user is properly opening a logind session (with
loginctl)?
Yes I still think we have to many default groups already