| 1 |
On 28/10/19 2:23 pm, Arve Barsnes wrote: |
| 2 |
> On Mon, 28 Oct 2019 at 04:38, Dale <rdalek1967@×××××.com> wrote: |
| 3 |
>> Also, are there any other options to elogind? Is that the only option |
| 4 |
>> when using KDE? |
| 5 |
> I think the answer here is yes. |
| 6 |
> |
| 7 |
> I run openbox, so no requirement to have this at all, but I have |
| 8 |
> previously done the migration to elogind, and that went without a |
| 9 |
> hitch. With no experience to back me up, I think the thing that might |
| 10 |
> break upon migration is the shutdown/reboot scripts, so you might have |
| 11 |
> to reboot from the commandline. Otherwise I don't expect much trouble. |
| 12 |
> |
| 13 |
> Regards, |
| 14 |
> Arve |
| 15 |
> |
| 16 |
It works for me - but its annoying in that its inherited some parts of |
| 17 |
the systemd "stuff you - I dont care, I am going to take it over anyway" |
| 18 |
attitude. For me its laptop suspend/hibernate - its never worked as |
| 19 |
well as previous scripts and it seems it cant be undone. Its also quite |
| 20 |
chatty in the logs - also annoying. |
| 21 |
|
| 22 |
I know the author is responsive and has done a good job in just being |
| 23 |
able to get it to work, but he has started with crapware and it shows. |
| 24 |
(sorry, but suspend/hibernate is a sore point for me) |
| 25 |
|
| 26 |
BillK |
Archives