Requests for current-next (15.0-->15.1)

marav · 04-15-2024, 06:57 AM

Quote:

Originally Posted by ZhaoLin1457

Let's remember that elogind is maintained by programmers affiliated with Gentoo and Devuan. And these programmers do not necessarily use SysV init like Slackware, on the contrary, they can very well use OpenRC or S6.

If we continue to use an old version of elogind, I think we run the risk of elogind becoming incompatible with Slackware and its SysV init.

And then what? Will we follow Devuan and adopt S6 or Gentoo and its OpenRC? I don't think that staying in an old version of elogind is an option, in my humble opinion.

Actually, those versions are the ones tag as "stable" by gentoo

https://packages.gentoo.org/packages/sys-auth/polkit
https://packages.gentoo.org/packages/sys-auth/elogind

Site note: elogind version > 252.9 is not even in their unstable branch

I know, I know, we are not Gentoo, but I like when my laptop wakes up from suspend with everything works as it did before

LuckyCyborg · 04-15-2024, 07:09 AM

Quote:

Originally Posted by marav

I know, I know, we are not Gentoo, but I like when my laptop wakes up from suspend with everything works as it did before

Then let's fix these builds of latest packages for elogind and polkit.

If everybody will stuck their tails between legs and ran on older versions, who will fix them?

Petri Kaukasoina · 04-15-2024, 07:10 AM

Quote:

Originally Posted by LuckyCyborg

Nope. Unfortunately, looks like the elogind 255.4 prefers s2idle because seems to use this configuration option for its preferences:

Code:

SuspendMode=s2idle deep

I haven't edited 10-elogind.conf. It uses deep here.

Code:

# cat /sys/power/mem_sleep 
s2idle [deep]
# echo s2idle > /sys/power/mem_sleep
# cat /sys/power/mem_sleep 
[s2idle] deep

(I changed to s2idle above.)

LuckyCyborg · 04-15-2024, 07:18 AM

Quote:

Originally Posted by Petri Kaukasoina

I haven't edited 10-elogind.conf. It uses deep here.

Code:

# cat /sys/power/mem_sleep 
s2idle [deep]
# echo s2idle > /sys/power/mem_sleep
# cat /sys/power/mem_sleep 
[s2idle] deep

(I changed to s2idle above.)

Apparently, even the elogind's developer Yamakuzure agrees with what I have observed, that latest elogind defaults to s2idle for system sleeping.

https://github.com/elogind/elogind/i...ent-2056460129

Again, this is a different thing than the kernel defaults - even the kernel prefers "deep" , the elogind still will prefer "s2idle" because reasons, unless instructed otherwise.

BTW, please note what configuration options he uses.

Petri Kaukasoina · 04-15-2024, 07:46 AM

Quote:

Originally Posted by LuckyCyborg

Again, this is a different thing than the kernel defaults - even the kernel prefers "deep" , the elogind still will prefer "s2idle" because reasons, unless instructed otherwise.

Yes, I understand now what you say. You are right. I just put it to sleep with 'echo mem>/sys/power/state' which used the kernel default 'deep'. But 'loginctl suspend' uses the elogind default 's2idle', and afterwards there is s2idle written in /sys/power/mem_sleep, too. So, elogind-daemon writes s2idle to /sys/power/mem_sleep just before it suspends the system.

marav · 04-15-2024, 07:47 AM

Quote:

Originally Posted by LuckyCyborg

Then let's fix these builds of latest packages for elogind and polkit.

If everybody will stuck their tails between legs and ran on older versions, who will fix them?

Sometimes, I do
Reverting to make my laptop working again doesn't mean I won't try to fix or to help with the issue
But you already know that ;-)

kgha · 04-15-2024, 09:20 AM

Can confirm that uncommenting the line SuspendMode=s2idle deep in /etc/elogind/sleep.conf.d/10-elogind.conf and change it to
SuspendMode=deep s2idle
gives the "proper" suspend behaviour. In my case I can also suspend/resume by closing/opening the laptop lid.
But the network issue remains...

Reverting to previous elogind and polkit versions is probably the best temporary measure. However, what also works (at least for me) if one wants to keep the latest versions, is to make appropriate adjustments in the abovemetioned .conf file and rebuild NetworkManager, editing line 136 in the slackware buildscript from

Code:

  --with-suspend-resume=elogind \

to

Code:

  --with-suspend-resume=upower \

If the LEDs on my laptop can be trusted, wifi goes down during suspend (as do bluetooth), but both are immediately alive after resume.

EDIT: I have to revoke this suggestion. It seems first to work fine, but I get issues with connections - if Thunderbird is running when resuming, connection with mail servers are broken and requires restarting Thunderbird.

marav · 04-15-2024, 09:56 AM

NetworkManager

It seems

Code:

  --with-session-tracking=elogind \
  --with-suspend-resume=elogind \

no longer builds session tracking with the desired value

Code:

Platform:
  session tracking: consolekit
  suspend/resume: elogind

With a meson version of the Slackbuild

Code:

  -Dsession_tracking=elogind \
  -Dsuspend_resume=elogind \

Code:

    session_tracking    : elogind
    suspend_resume      : elogind

My setup

Code:

--- NetworkManager.SlackBuild   2024-02-23 02:49:52.589076742 +0100
+++ NetworkManager.SlackBuild.1 2024-04-15 17:31:17.070756579 +0200
@@ -98,11 +98,6 @@
   zcat $dfile | patch -p1 --verbose || exit 1
 done
 
-# For git-patched builds
-autoreconf -vif
-automake
-./autogen.sh
-
 # Configuring --enable-json-validation --enable-ovs requires the Jansson
 # json-c library. If there's any interest or usefulness with that, let me
 # know. The library is fairly small, but in order to actually use team
@@ -111,34 +106,41 @@
 # Update September 2018: Added those options since we needed Jansson
 # already for HTTP/2 support.
 
-CFLAGS="$SLKCFLAGS" \
-CXXFLAGS="$SLKCFLAGS" \
-./configure \
+export CFLAGS="$SLKCFLAGS" 
+export CXXFLAGS="$SLKCFLAGS" 
+mkdir meson-build
+cd meson-build
+meson setup \
   --prefix=/usr \
   --libdir=/usr/lib${LIBDIRSUFFIX} \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --mandir=/usr/man \
-  --docdir=/usr/doc/$PKGNAM-$VERSION \
-  --with-udev-dir=/lib/udev \
-  --with-pppd-plugin-dir=/usr/lib${LIBDIRSUFFIX}/pppd/$PPPD \
-  --with-crypto=nss \
-  --enable-more-warnings=no \
-  --without-resolvconf \
-  --with-dhcpcd=/sbin/dhcpcd \
-  --with-dhclient=yes \
-  --with-modem-manager-1=yes \
-  --with-nmtui=yes \
-  --enable-json-validation \
-  --enable-ovs \
-  --with-consolekit=no \
-  --with-session-tracking=elogind \
-  --with-suspend-resume=elogind \
-  --with-hostname-persist=slackware \
-  --build=$TARGET || exit 1
-
-make $NUMJOBS || exit 1
-make install DESTDIR=$PKG || exit 1
+  -Dudev_dir=/lib/udev \
+  -Dpppd_plugin_dir=/usr/lib${LIBDIRSUFFIX}/pppd/$PPPD \
+  -Dsession_tracking=elogind \
+  -Dsuspend_resume=elogind \
+  -Dnmtui=true \
+  -Dovs=true \
+  -Dresolvconf='' \
+  -Ddhcpcd=/sbin/dhcpcd \
+  -Dconfig_dhcp_default=dhcpcd \
+  -Dcrypto=nss \
+  -Dsystemd_journal=false \
+  -Ddbus_conf_dir=/usr/share/dbus-1/system.d \
+  -Ddhclient=/sbin/dhclient \
+  -Dmodem_manager=true \
+  -Dmore_logging=false \
+  -Dhostname_persist=slackware \
+  -Dsystemd_journal=false \
+  -Dsystemdsystemunitdir=no \
+  -Dselinux=false \
+  -Dlibaudit=no \
+  -Dqt=false \
+  .. || exit 1
+  "${NINJA:=ninja}" $NUMJOBS || exit 1
+  DESTDIR=$PKG $NINJA install || exit 1
+cd ..
 
 # Don't ship .la files:
 rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la
@@ -190,6 +192,9 @@
 cp -a \
   AUTHORS CONTRIBUTING COPYING ChangeLog INSTALL NEWS README TODO \
   $PKG/usr/doc/$PKGNAM-$VERSION
+cp -a \
+  $PKG/usr/share/doc/NetworkManager/* $PKG/usr/doc/$PKGNAM-$VERSION
+  rm -rf $PKG/usr/share/doc/NetworkManager
 
 # If there's a ChangeLog, installing at least part of the recent history
 # is useful, but don't let it get totally out of control:

opty · 04-15-2024, 10:09 AM

elogind.SlackBuild changed without package rebuild? o_O

bormant · 04-15-2024, 10:12 AM

Quote:

Originally Posted by marav

Code:

@@ -113,32 +108,39 @@
 
 CFLAGS="$SLKCFLAGS" \
 CXXFLAGS="$SLKCFLAGS" \
-./configure \
+mkdir meson-build
+cd meson-build
+meson setup \

Code:

 CFLAGS="$SLKCFLAGS" \
 CXXFLAGS="$SLKCFLAGS" \

are unusable for mkdir ..., after patch:

Code:

CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
cd meson-build

Do they need for meson setup \ so moved down just before it

Code:

mkdir meson-build
cd meson-build
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
meson setup \

or else removed?

marav · 04-15-2024, 10:28 AM

Quote:

Originally Posted by bormant

Code:

 CFLAGS="$SLKCFLAGS" \
 CXXFLAGS="$SLKCFLAGS" \

are unusable for mkdir ...

My C/C failed. I cut the "export"

Code:

export CFLAGS="$SLKCFLAGS"
export CXXFLAGS="$SLKCFLAGS"
+mkdir meson-build
+cd meson-build
+meson setup \

marav · 04-15-2024, 10:43 AM

Quote:

Originally Posted by opty

elogind.SlackBuild changed without package rebuild? o_O

it didn't change the way the program works (or doesn't work, depending on your POV

)

opty · 04-15-2024, 10:58 AM

Even

Code:

  -Dmode=release \

?

opty · 04-15-2024, 11:04 AM

Populate /etc/gshadow to e.g. make grpck happy?

teoberi · 04-15-2024, 11:57 AM

Quote:

Originally Posted by opty

Populate /etc/gshadow to e.g. make grpck happy?

+1