• Michael Catanzaro's avatar
    Don't use dbus-broker if not running under systemd · 260a4414
    Michael Catanzaro authored
    Since gdm@febeb9a9, gdm no longer runs a systemd user session, because
    gdm supports multiseat but systemd only allows one graphical session per
    user. Since gdm currently runs as the gdm user, that means we cannot use
    systemd there. Benjamin Berg says we could fix that by changing gdm to
    use temporary users for each seat, but that would be a lot of work.
    Meanwhile, dbus-broker relies on systemd to autostart D-Bus services. So
    if we are not running a systemd user session, nothing gets autostarted
    in response to D-Bus calls. That means orca never gets any response to
    its method calls to org.a11y.atspi.Registry, and we wind up with no
    accessibility on the gnome-shell login screen.
    Fix this by implementing Benjamin's suggested check to see if we are
    running under systemd before using dbus-broker. So now we will use
    dbus-daemon on the login screen, but we will still use dbus-broker for
    the user session (except in distros that still prefer dbus-daemon...
    which is actually the default configuration). libsystemd is added as a
    build dependency whenever built with dbus-broker support, which should
    be uncontroversial because it won't work without systemd.
    I expect dbus-daemon is going to live alongside dbus-broker for a long
    time, because it seems very hard for us to migrate fully.
    Big thanks to Benjamin Berg for discovering the problem and suggesting
    this solution.
    Fixes #25