Merge lp:~ballogy/indicator-session/systemd-support into lp:indicator-session/13.04
Proposed by
Balló György
Status: | Rejected |
---|---|
Rejected by: | Ted Gould |
Proposed branch: | lp:~ballogy/indicator-session/systemd-support |
Merge into: | lp:indicator-session/13.04 |
Diff against target: |
84 lines (+66/-1) 1 file modified
src/gtk-logout-helper.c (+66/-1) |
To merge this branch: | bzr merge lp:~ballogy/indicator-session/systemd-support |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Mathieu Trudel-Lapierre | Abstain | ||
Review via email: mp+141656@code.launchpad.net |
Description of the change
This change adds systemd support for gtk-logout-helper.
Since shutdown/reboot with gnome-session works only with a patch that rejected by upstream[1], and consolekit is no longer available on systemd systems (e.g. Arch Linux), systemd-logind[2] is the only way to do this.
[1] https:/
[2] http://
To post a comment you must log in.
Unmerged revisions
- 381. By Balló György
-
Add support for systemd
Removing the consolekit_fallback looks wrong at first glance; but there's not enough context to see what's up. Seems to me like doing things this way would break those systems that should still fallback using consolekit.
It *is* a call to consolekit_fallback from within call_consolkit though, so maybe doing things this way isn't so crazy, but it seems to me like the initial assumption was to try again if the call to consolekit somehow failed; so that the failure can be recovered from.
Shouldn't it be possible to decide which backend to use at compile time?