| Summary: | Fix installing xinit script | ||
|---|---|---|---|
| Product: | systemd | Reporter: | tingping |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
| Severity: | normal | ||
| Priority: | medium | CC: | dh.herrmann, leho |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | Fix not installing xinit script | ||
|
Description
tingping
2015-05-28 03:21:53 UTC
I'm not a big fan of making this official systemd ABI. To clarify, this script is currently used to make kdbus work with .busname units for .desktop files. It is a hack we use while testing and developing kdbus. However, it's nothing we want to ship on real systems (at least not without downstream discussion). Background story here is that Xorg might run multiple times per user. However, `systemd --user` can only run once per user. Therefore, a systemd user unit cannot know to which Xorg server to connect. Our xinit-hack always pushes the address of the last-started Xorg server into systemd as environment, thus enabling units to access Xorg. However, this should not be the job of systemd (systemd should not have any X11 specific code at all). Last but not least, `systemd --user` hasn't been finished nor integrated into any existing distributions. So this needs discussion with downstream to decide how the per-user systemd units get access to per-session data. Given that sessions map n:1 to users, it will always be a hack to make any session-data accessible to per-user units. The real fix would be to make Xorg run only once per user (preferably as unit). In this case, it can place its socket in /run/user/$uid/ and all units get implicit access to it. Closing, as the kdbus thing is gone anyway from makefile.am |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.