SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,074
Rep:
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).
Tue Apr 16 18:50:13 UTC 2024
a/elogind-255.4_r2-x86_64-1.txz: Upgraded.
Prefer SuspendMode=deep. Thanks to LuckyCyborg.
Make 10-elogind.conf .new (but it will still be forced in this time).
Fix reading login.conf. Thanks to af7567.
This branch is feeling a bit alpha to me, but we'll stick with it for now.
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.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,074
Rep:
@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?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.