| 1 |
On Thursday, 27 June 2019 10:55:16 BST Mick wrote: |
| 2 |
|
| 3 |
> The next thing to try: |
| 4 |
> |
| 5 |
> I don't have elogind starting up as a boot level rc service, because it is |
| 6 |
> launched when needed by dbus or pam. Perhaps if elogind is running as a |
| 7 |
> background service sddm will (re)launch differently? |
| 8 |
|
| 9 |
I just tried it and it works. :-) |
| 10 |
|
| 11 |
With elogind running as a boot service, sddm launches with the Shutdown/Reboot |
| 12 |
buttons shown and they work as expected. However, as I do not have a /usr/ |
| 13 |
bin/loginctl, all I can assume is irrespective of the HaltCommand path |
| 14 |
specified in the default sddm config, when launched sddm searches all paths |
| 15 |
and eventually finds /bin/loginctl, which it runs when a button is pressed. |
| 16 |
|
| 17 |
As we've established with no -elogind +consolekit the commands specified in |
| 18 |
the default sddm config file are different. Also, with consolekit being a |
| 19 |
default rc service, it is running at the time sddm is launched. |
| 20 |
|
| 21 |
Thank you all for your responses. |
| 22 |
-- |
| 23 |
Regards, |
| 24 |
|
| 25 |
Mick |
Archives