-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: tag -1 help
control: retitle lightdm user needs access to DRI render nodes on some
platforms
On Sat, 2025-02-15 at 11:54 +0100, Heiko Stübner wrote:
> > I got that the first time, but I think that should be exactly the same
> > thing.
> > U
Am Samstag, 15. Februar 2025, 11:09:27 MEZ schrieb Yves-Alexis Perez:
> On Sat, 2025-02-15 at 10:22 +0100, Heiko Stübner wrote:
> > The problem is not the logged in user, but the user lightdm itself runs at.
> > I.e. user "lightdm".
>
> Hey Heiko,
>
> I got that the first time, but I think that s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2025-02-15 at 10:22 +0100, Heiko Stübner wrote:
> The problem is not the logged in user, but the user lightdm itself runs at.
> I.e. user "lightdm".
Hey Heiko,
I got that the first time, but I think that should be exactly the same thing.
Un
Hi,
Am Samstag, 15. Februar 2025, 10:09:17 MEZ schrieb Yves-Alexis Perez:
> On Fri, 2025-02-14 at 23:59 +0100, Heiko Stübner wrote:
> >
> > Adding the lightdm-user to group render, solves this issue and allows
> > lightdm to start.
>
> Hi, it looks to me that this should be dynamically granted th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2025-02-14 at 23:59 +0100, Heiko Stübner wrote:
>
> Adding the lightdm-user to group render, solves this issue and allows
> lightdm to start.
Hi, it looks to me that this should be dynamically granted through ACL with
udev, not statically u
Package: lightdm
Version: 1.32.0-6+b1
Severity: normal
On a number of systems with separate render-only gpu, for example
everything with a Mali GPU, the graphics output will be the regular
/dev/dri node, but for accelerated loads via mesa will render on the
separate render-node - /dev/dri/renderD1
6 matches
Mail list logo
