@LuckyCyborg:

Version 252.23 is a stable release and AFAIK there has been no reports here about any issues, so no need to go back to 252.9.

No, we shouldn't tuck our tails between our legs and just wait for fair weather. Which is why a lot of users here have been fiddling with elogind-255.4: reporting issues, spotting errors in the buildscript, reporting to the devs (who are investigating).

But I for one am not happy with a version that breaks functionality (suspend/resume) on my everyday system. OK, I could upgrade to latest, refrain from suspending (switch the laptop lid function to just sending screen to sleep). If it doesn't bother you, well and good - you're free to upgrade (or not) as you wish. It's Slackware.

EDIT: And there is some interaction between elogind and polkit. With elogind-252.23 and polkit-124 installed, power management (including screen brightness) no longer works and the shutdown menu disappears (on mate and xfce desktops). And not just for me, others have experienced the same.

2 members found this post helpful.

Another discovery regarding the elogind/polkit issue: If polkit-124 is rebuilt with elogind-252.23 installed, power management works properly (thanks to ill323 for the suggestion). The polkit-124 package in the -current repo was built after the elogind-255 release.

3 members found this post helpful.

It's a well know issue the one proposing me to comment out the last line of 10-elogind.conf simply don't read what people writes.

Anyway, that line is already commented out or the system dies on sleep. Even so /etc/rc.d/rc.networkmanager restart is still required in /lib64/elogind/system-sleep/whatever.sh, otherwise network is dead after resume. So, elogind-255.4_r2 didnt fix anything here and caused an entirely new and more annoying issue. That file is not part of the package so it will also be preserved between upgrades.

To downgrade elogind or not is not a decision that concerns me. What concerns me is my system at an usable state don't matter what is being thrown at it, including any workarounds people on -current should be prepared to do at anytime.

It seems that "s2idle" works correctly only for a number of modern laptops. For everyone else it seems that "deep" is the one that works correctly.

Commenting out a line in a configuration file is an annoying issue?

1 members found this post helpful.

Not at all. A system dying on sleep is way more annoying than no network on resume.

I believe I said all that matters on the subject already, so I'm leaving this discussion here.

But 10-elogind.conf is a configuration file that you have to modify only once, because starting with the last elogind-255.4_r2 package, this file will not be overwritten.

If "s2idle" works better for you, there's nothing stopping you from configuring it this way.

1 members found this post helpful.

Since xfce4-notifyd-0.9.4-x86_64-1 now there are a couple of dbus service file included.
These cause xfce4-notifyd to start even in a KDE session, overriding KDE's notifier.
Please rebuild xfce4-notifyd with the "--disable-dbus-start-daemon" configure parameter to avoid the installation of these dbus service files.

1 members found this post helpful.

Latest bluez package contains duplicates of some config files:
Looks like the ones without .new extension are installed by Makefile and the .new ones by SlackBuild.

Really ?

You dont know some packages have configs as NEW , to no overwrite your preferences?

You can inspectioning the NEW to see changes ..

or if you no want NEW files can put as defaults one..

But some people install only XFCE ... that affect this people?

It's not even an issue, since the line is commented out as per default after upgrading. See the changelog:
"Prefer SuspendMode=deep. Thanks to LuckyCyborg."

If "deep" isn't the right choice for your hardware, you must of course do something about it.

Could any mod move all the elogin discussion to an elogin dedicated topic? This has been the only talk on this thread for the past few pages/days, and surely shouldn't had happened at this thread.

1 members found this post helpful.

Try changing any of the files from my post, then reinstall bluez and see if your changes are still there.

Development-related?

in elogind.SlackBuild (and probably others using meson) to "dismiss"

(Verified.)