Summary: | x11-base/xorg-server-1.20.10: startx stopped working, permissions problems | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrey Grozin <grozin> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrey Grozin
2021-01-13 03:14:42 UTC
BTW, I don't use systemd Have you read the news item from June? eselect news read 2020-06-24-xorg-server-dropping-default-suid (In reply to Matt Turner from comment #2) > Have you read the news item from June? > > eselect news read 2020-06-24-xorg-server-dropping-default-suid Yes, I have read it. I use a desktop profile (namely, plasma), and have elogind installed. The USE flag elogind is globally enabled. Without USE=suid X did not work for a long time (I mean when I use startx, not a display manager). But with USE=suid it worked fine until very recently. Follow the troubleshooting part of https://wiki.gentoo.org/wiki/Non_root_Xorg (In reply to Piotr Karbowski from comment #4) > Follow the troubleshooting part of https://wiki.gentoo.org/wiki/Non_root_Xorg OK thanks. Adding elogind to the boot runlevel has helped. But an interesting question remains: whas has been broken quite recently in Xorg with USE=suid? Why it worked for so long and suddenly stopped working? Sounds a bit similar to https://bugs.gentoo.org/764557 But we lack information and steps to reproduce it, if you can join it and confirm/deny, it would be great. |