Bug with elogind-255.4-r2
 

Resume from suspend and hibernate breaks network connectivity.
More details at https://www.linuxquestions.org/quest...-a-4175735969/

I was going to start a thread on this. Also, I notice that my laptop is not really suspending at all. I can still hear the fan running and the laptop light is not turning amber like it usually does in suspend.

Thanks for reporting. I guess that is what messes up my laptop after one of the latest updates to SW64 --current.

If I leave it idle for some time, it goes to sleep, naturally. However, when I want to wake it up, it is nearly impossible.

Pressing or holding the power button doesn't do a thing in such cases. When I finally manage to wake it up (still not sure how, pressing the same buttons sometimes work, sometimes not, and I'm sure the keyboard is ok) the network is broken and I need to restart the machine.

Same issue. I reverted to elogind-252.23-x86_64-2.

YMMV, but you may have to downgrade both elogind (to v252.23) and polkit (to v123) in order to get full functionality (e.g screen brightness, shutdown menu, power management).

This should fix the issue:

Nope

The problem is that we have absolutely nothing in the logs when resuming after hibernation that can help us to find what's wrong with NetworkManager

See:
https://github.com/elogind/elogind/issues/280

elogind-255.4_r2-x86_64-1.txz in fact makes it worse

Now resume from sleep doesn't work anymore. Anything power managemnt related is borked.

Pat, please ...

Just comment the last line from /etc/elogind/sleep.conf.d/10-elogind.conf - which contains SuspendMode= and restart the computer. It's a config file, so this change will be preserved when upgrading the elogind package.

That doesn't work - the network is still borked.

Confirmed : rollback to 252/123 is still needed not to break network after suspend.

Please downgrade the current repo :)

That SuspendMode= is not intended to fix the NetworkManager related issue, because this one is the second and separate issue.

Just compiled networkmanager 1.46.0 with this:

test$ diff -u NetworkManager.SlackBuild.orig NetworkManager.SlackBuild
--- NetworkManager.SlackBuild.orig 2024-04-17 15:15:21.718644490 +0800
+++ NetworkManager.SlackBuild 2024-04-17 15:15:43.731519025 +0800
@@ -133,7 +133,7 @@
--enable-ovs \
--with-consolekit=no \
--with-session-tracking=elogind \
- --with-suspend-resume=elogind \
+ --with-suspend-resume=upower \
--with-hostname-persist=slackware \
--build=$TARGET || exit 1

And resuming works again.

I think new elogind do not send 'resume' signal to networkmanager.

@ill233:
tried this workaround, but unfortunately it doesn't work properly. If you have a mailclient (e.g. thunderbird) running at suspend, it somehow loses connection and needs to be restarted after resuming, see https://www.linuxquestions.org/quest...ml#post6495940. Might be seen as a minor snag, but since there seems to be no drawbacks in downgrading elogind and polkit, that's probably the best option right now.

Ok, just saw that thread.
It seems that elogind is broken.
And polkit depends on elogind, maybe polkit-124 compiled with old working elogind has no problem?