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.
Most likely elogind works perfectly in Gentoo and Devuan, operating systems under which it is developed and for which it is developed. It seems that the elogind developer does not even have problems with the communication between elogind and NetworkManager.
Personally, I would say that there are compatibility issues between the latest versions of elogind and Slackware. Which problems will surely get worse if Slackers stay in old versions of elogind.
I hope we don't find out that elogind is no longer compatible with Slackware, while we wait for the Devuan developers to fix it for us.
@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.
By fortune, the stock package of NetworkManager is built with "session-traking=consolekit" (which is not ConsoleKit2, but that old abandoned ConsoleKit) and if you add/change to "suspend-resume=upower", then NetworkManager is completely disconnected from elogind.
If it still doesn't work, it means that there are another problems in Slackware-current, beyond this elogind 255.4 vs. NetworkManager 1.46.0
In another way, can you explain to me why a NetworkManager that is completely disconnected from elogind does not work correctly?
Last edited by ZhaoLin1457; 04-17-2024 at 04:42 AM.
I haven't dug further into this so I don't know why this happens.
I'm not contradicting you. What I want to say is that your statement is a clear proof that there are other compatibility problems in Slackware-current, beyond this elogind.
Which compatibility problems, they probably have have reached a critical mass lately and we have come to notice them widely and pay more attention to them.
I'm on Slackware-current, and have that power issue. Elogind-255.4-r2 is on github at least, but I can't build it because it wants auditd . What's that?
EDIT: I read somewhere (Github issues or comments?) that some issue with elogind-255.4 was leading to orphaned processes and 255.4-r1 was supposed to fix that.
If Memory serves, I didn't have the power-off issue on Current of 2024-03-24. A large amount of stuff has changed, so that's not diagnostically useful. But if this issue gets narrowed down to a dozen packages or so, I can still downgrade them, as I still have the 2024-03-24 iso on disk.
Last edited by business_kid; 04-17-2024 at 05:49 AM.
I'm on Slackware-current, and have that power issue. Elogind-255.4-r2 is on github at least, but I can't build it because it wants auditd . What's that?
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,074
Rep:
If "power issue" is about broken power management and the disappearing shutdown menu (mate, xfce, maybe KDE too) there are three possible solutions:
- use the latest elogind-255.4_r2 and polkit-124 from the -current repo (but then network breaks after suspend/resume)
- downgrade elogind to v252.23 and polkit to v123
- downgrade elogind to v252.23 and then rebuild polkit-124
someone
networkmanager listens to elogind signals on dbus to handle sleep/resume.
elogind sends the "sleep" message correctly, but not the "resume" message.
So, after resume networkmanager doesn't bring up the network again, and needs to be restarted.
The same problems applies to other networkmanager-enabled applications, eg. Firefox and Thunderbird.
the problem in elogind is caused by a patch introduced to fix another problem. 252.23 is good, any new version is broken (252.23-r1, 255.4-*)
someone
networkmanager listens to elogind signals on dbus to handle sleep/resume.
elogind sends the "sleep" message correctly, but not the "resume" message.
So, after resume networkmanager doesn't bring up the network again, and needs to be restarted.
The same problems applies to other networkmanager-enabled applications, eg. Firefox and Thunderbird.
the problem in elogind is caused by a patch introduced to fix another problem. 252.23 is good, any new version is broken (252.23-r1, 255.4-*)
And how you explain the issues with the initial release of 255.4 (without ulterior patches) ?
I for one I believe that an explanation could be that this issue introduced by that patch is in fact the second one (but having a similar misbehavior) , as speculated by Zhao Lin there:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.