(FWIW, I don't yet understand the implications of that change, just
wondering if anyone has confirmed the hunch.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2077538
Titl
Okay, well has this been tested? Trying this would be trivial:
$ cat > /etc/udev/rules.d/90-test.rules << EOF
ACTION!="add", GOTO="default_end"
SUBSYSTEM=="drm", KERNEL=="renderD*", GROUP="render", MODE="0666"
LABEL="default_end"
EOF
$ reboot
--
You received this bug notification because you
One thing I noticed is that Debian used 0600 instead of 0666 here:
https://salsa.debian.org/systemd-team/systemd/-/commit/8ca0c4921b
Using 0666 may be enough to fix this issue and it could be why distros
other than Debian or Ubuntu didn't seem to have a problem here.
--
You received this bug no
Can you please distill what the request is for systemd to do exactly? I
would engage on the bug, but I don't have an account there, and it seems
like you are in a position to share the tl;dr.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification b
I'm adding a systemd task since there are multiple points on
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/224 about
how this issue needs to be handled by systemd.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification b
5 matches
Mail list logo