I'm experiencing this as well.

Rollback to elogind-252.23 and polkit-123 fixes most problems as far as I tested.

I spoke too soon. By using the upower workaround the internet still works fine, and firefox and thunderbird work initially after a resume. But after a few minutes they do go wrong and need restarting anyway. So it looks like NM aware apps are just going to go wrong whichever workaround is used, so downgrade is the only reliable fix at the moment.

I've raised the issue at github.com/elogind. Hopefully some explanation/help/solution will come out of it.

However, it seems as if Pat considers reverting to version 252.23, or maybe come down with an aternative solution: https://www.linuxquestions.org/quest...ml#post6495928

logind.conf is ignored by 255.4 at the moment (at least on Slackware), I opened an issue on github about that yesterday. So anything you tested changing in the logind.conf files won't have done anything.

edit: Oh sorry, I just saw you referenced my issue there so do know about the logind.conf thing :)

Yup. And as I wrote over there,I've tried recompiling elogind using the latest 255.4-r1 and your patch, but no difference.

LuckyCyborg has posted something regarding the elogind upgrade here: https://www.linuxquestions.org/quest...ml#post6496029
but I can't see how this relates to the network issue.

On my system resuming from s2idle results in my mouse not working for some reason, so it seems to break more devices than real sleep does. I have always had SuspendMode set to deep because of that, and s2idle also keeps the PC running so not really sleeping at all.

I have just seen that the elogind developer also mentions s2idle.
You can check what sleep method your system is using in /var/log/messages, and see if it is different when using 252 instead of 255
s2idle would explain why the LEDs stay on, but the network staying down problem happens whatever sleep mode is used.

Right now I'm provisionally running elogind-255.4 and polkit-124 with the following /etc/elogind/sleep.conf.d/10-elogind.conf:
(The last line is the important one, changed from default).

I also have the rebuilt NetworkManager, built with --with-suspend-resume=upower \ as mentioned in post #12 above.

Suspend/resume behaviour appears "normal" - the wifi LED goes off during suspend, wifi and bluetooth immediately active after resume. And suspend/resume by closing/opening laptop lid works. I have not encountered any problems with my browser (vivaldi) or mail client (thunderbird) that af7567 mentions in post #18

EDIT: Have to revoke the last lines - I do get issues with Thunderbird. So this is not a viable option. Sorry.

Just to know if is related: after rollbacking polkit and elogind, I'm experiencing the notify service of KDE failing and falling back to xfce4 one. Anyone else experience the same?

EDIT: tried upgrading to the current version of elogind and polkit with no result. I guess is not related. Rollbacked again and i'll open another thread about it

On a tangent kioslave5 is also crashing for me too, not sure if it's related (but it also started happening only after a recent upgrade)

-- ltlnx

Edit: on both fully upgraded and upgraded-then-downgraded -current

I just had a reboot after a couple of days and had the same thing happening.
I guess this is related, i'm investigating the changes:

yes is it. I solved it at https://www.linuxquestions.org/quest...le-4175736075/

The revert to elogind-252 did the trick. Marking this as solved. Thanks Pat and everyone involved!

-- ltlnx