Issue with shutdown antiX 26 s6-rc

[olsztynMember]

I am experiencing an issue with shutting down antiX 26 when using s6-rc init.
On shutting down processes it displaying “nm-dispatcher: Caught signal 15…”, where it stays.
Probably something is missing in my shutdown process of network manager s6 service.
Any ideas will be appreciated…

$ inxi -xFz
System:
  Kernel: 6.19.14-2-liquorix-amd64 arch: x86_64 bits: 64
    compiler: gcc v: 14.2.0
  Desktop: LXQt v: 2.1.4 Distro: antiX-26_x64-full Stephen
    Kapos 28 January 2026 base: Debian GNU/Linux 13 (trixie)
Machine:
  Type: Laptop System: LENOVO product: 4173L8U
    v: ThinkPad T420s serial: <superuser required>
  Mobo: LENOVO model: 4173L8U serial: <superuser required>
    UEFI-[Legacy]: LENOVO v: 8CET51WW (1.31 ) date: 11/29/2011
Battery:
  ID-1: BAT0 charge: 1.8 Wh (6.1%)
    condition: 30.2/39 Wh (77.4%) volts: 10.61 min: 11.1
    model: SANYO 42T4845 status: discharging
CPU:
  Info: dual core model: Intel Core i5-2520M bits: 64
    type: MT MCP arch: Sandy Bridge rev: 7 cache: L1: 128 KiB
    L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 797 min/max: 800/2501 boost: enabled
    cores: 1: 797 2: 797 3: 797 4: 797 bogomips: 19936
  Flags-basic: avx ht lm nx pae sse sse2 sse3 sse4_1
    sse4_2 ssse3
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family
    Integrated Graphics vendor: Lenovo driver: i915 v: kernel
    arch: Gen-6 bus-ID: 00:02.0
  Device-2: Chicony integrated camera driver: uvcvideo
    type: USB bus-ID: 4-1.6:5
  Display: x11 server: X.org with: Xwayland v: 24.1.6
    driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: crocus gpu: i915 resolution: 1600x900~60Hz
  API: EGL v: 1.5 drivers: crocus,swrast platforms:
    active: gbm,x11,surfaceless,device inactive: wayland
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: intel mesa
    v: 26.0.1-2~mx25ahs glx-v: 1.4 direct-render: yes
    renderer: Mesa Intel HD Graphics 3000 (SNB GT2)
  Info: Tools: api: eglinfo,glxinfo de: kscreen-doctor
    x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 6 Series/C200 Series Family High
    Definition Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0
  API: ALSA v: k6.19.14-2-liquorix-amd64 status: kernel-api
  Server-1: PipeWire v: 1.4.2 status: active
Network:
  Device-1: Intel 82579LM Gigabit Network
    vendor: Lenovo ThinkPad T520 driver: e1000e v: kernel
    port: 4080 bus-ID: 00:19.0
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak]
    driver: iwlwifi v: kernel bus-ID: 03:00.0
  IF: wlan0 state: up mac: <filter>
Drives:
  Local Storage: total: 111.79 GiB used: 21.12 GiB (18.9%)
  ID-1: /dev/sda vendor: SanDisk model: SDSSDA120G
    size: 111.79 GiB
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 47.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 4031
Info:
  Memory: total: N/A available: 5.67 GiB
    used: 1.03 GiB (18.2%)
  Processes: 250 Uptime: 7m Init: s6
  Packages: 2315 Compilers: gcc: 14.2.0 Shell: Bash
    v: 5.2.37 inxi: 3.3.39
demo@antix1:~
$ 

Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[c0pAMember]

I have also experienced shutdown issues with this init, as described here: https://www.antixforum.com/forums/topic/which-init-are-you-using-mostly-and-why/#post-201845 by @larrys4227

[olsztynMember]

c0pA wrote:

I have also experienced shutdown issues with this init, as described here: https://www.antixforum.com/forums/topic/which-init-are-you-using-mostly-and-why/#post-201845 by @larrys4227

Appears the same symptom.
I found desktop-session-exit does work though… I need to study this issue in more depth…

• This reply was modified 4 months, 1 week ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[ProwlerGrMember]

@anticapitalista

If this is a common issue, maybe we could reconsider reintroducing the busybox fallback for our reboot & poweroff functions?
The reason we had it removed was because it interrupted the automatic persist-save, however I’m thinking if this can be detected the reboot/poweroff script could be reconfigured to exit without executing the busybox functions

sync && /usr/lib/s6-rc/reboot $@ && sync && sleep 3 && [ ! -e /detected/persist-save ] && /usr/bin/busybox reboot -f; exit 0

(The [ ! -e /detected/persist-save ] is obviously just for context – if a proper detection method exists it could be used)

• This reply was modified 4 months, 1 week ago by ProwlerGr.

[olsztynMember]

@ProwlerGr:
As I mentioned earlier in this thread, desktop-session-exit does seem to work properly. Considering @anticapitalista provided a new desktop-exit-antix, which I am trying to test, perhaps this new exit would solve this issue, if it is common?

Edit:
Based on additional info from @anticapitalista desktop-exit-antix may not be the solution after all.

• This reply was modified 4 months, 1 week ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Brian MasinickModerator]

I dug into this today, and I’ve got them all working well once again, and basically I just used the /lib/init-diversity scripts, reboot.sh and poweroff.sh. I see no reason to change them. To me, I believe the problems some people are experiencing is that they are attempting to either use a different shutdown/reboot approach OR they’ve been messing with other login manager alternatives.

I thought I saw an issue recently with s6-66, but today I made sure to boot, reboot and poweroff properly and it worked. Same with s6-rc; with the right scripts it worked.

What I’m going to do next is to turn on another system and see if I have it properly configured; the one I’ve been using today IS properly configured, so that’ll give me more information to see if the problems I have on the other systems are the same or similar problems that others are experiencing; if that is the case, AGAIN I recommend SPECIFICALLY using the /lib/init-diversity directory to explicitly run reboot.sh, shutdown.sh or poweroff.sh, and also run them as root, that is, either su root or prepend /lib/init-diversity/reboot.sh or one of the other scripts with sudo.

I’ll report back later today with my findings from other systems that may not have all of my “conveniences” that ensure that I’m running these scripts PROPERLY!

--
Brian Masinick
Alternate "Search B":
This search page

[olsztynMember]

Brian Masinick wrote:

I dug into this today, and I’ve got them all working well once again, and basically I just used the /lib/init-diversity scripts, reboot.sh and poweroff.sh. I see no reason to change them. To me, I believe the problems some people are experiencing is that they are attempting to either use a different shutdown/reboot approach OR they’ve been messing with other login manager alternatives.

Thanks @Brian!
Looks like this issue has been therefore taken care of… I am good with what you reminded about.

I am also looking at other options, such as developed by @valera to route these as init commands through dbus to power off/reboot.
He implemented these in his latest version of his dinit antiX MXD respin. In that implementation after hitting shutdown/reboot button a dialog with timer appears just in case you want to cancel, if your hit those buttons unintentionally.
Thanks again.

Live antiX Boot Options (Previously posted by Xecure):
http://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Brian MasinickModerator]

I’m on a different system now so I’m about to exercise it. Started with dinit and so far it’s doing well, so I’ll shift to one of the s6 varieties and see what happens there. But first I’m going to double-check my alias commands to ensure that I’m calling the correct reboot and shutdown tools so my experiments are proper – on antiX 26 we should use the shell scripts in the /lib/init-diversity directory to handle shutdowns and reboots and they should be run from su or sudo.

--
Brian Masinick
Alternate "Search B":
This search page

[c0pAMember]

Brian Masinick wrote:

But first I’m going to double-check my alias commands to ensure that I’m calling the correct reboot and shutdown tools so my experiments are proper – on antiX 26 we should use the shell scripts in the /lib/init-diversity directory to handle shutdowns and reboots and they should be run from su or sudo.

How does one check that?!

[Brian MasinickModerator]

Here: forget about my scripts.

Open either a terminal or a root file manager.
Visit the directory /lib/init-diversity (antiX 26).

/lib/init-diversity
[antix26]/lib/init-diversity: > ls
poweroff.sh  rcS.sh	runlevel.sh  user-session.sh
rc.sh	     reboot.sh	shutdown.sh

These are the scripts you should use to poweroff = poweroff.sh
shutdown = shutdown.sh
reboot = reboot.sh.

In case it is still not clear, here’s an example of how to reboot antiX 26:

sudo /lib/init-diversity/reboot.sh

Is that sufficiently clear?

--
Brian Masinick
Alternate "Search B":
This search page

[c0pAMember]

Brian Masinick wrote:

Is that sufficiently clear?

Yes! But…

Is there a way to make that the default behavior when using the Menu > Logout button? From your previous posts, I understand that the problem occurs because these menus don’t properly call those scripts.

I might have misinterpreted that, though.

[Brian MasinickModerator]

c0pA wrote:

Brian Masinick wrote:

Is that sufficiently clear?

Yes! But…

Is there a way to make that the default behavior when using the Menu > Logout button? From your previous posts, I understand that the problem occurs because these menus don’t properly call those scripts.

I might have misinterpreted that, though.

I will check; chances are the menus call the correct code.
I’ll be back to verify this; in any case the procedures in /lib/init-diversity DO work.

--
Brian Masinick
Alternate "Search B":
This search page

[Brian MasinickModerator]

c0pA wrote:

Brian Masinick wrote:

Is that sufficiently clear?

Yes! But:

Is there a way to make that the default behavior when using the Menu > Logout button? From your previous posts, I understand that the problem occurs because these menus don’t properly call those scripts.

I might have misinterpreted that, though.

I will check; chances are the menus call the correct code.
I’ll be back to verify this; in any case the procedures in /lib/init-diversity DO work.

YES! The menus DO call the correct code!

I apologize for giving you the wrong impression. I wasn’t talking about the menus. I was talking about the convenience scripts and alias commands that I typically use so I haven’t used the logout/reboot menus on antiX very often; in fact they work GREAT! Now that I double checked my stuff, on some systems I had my tools properly configured; on the system I just visited not all of my tools were accurate; they are now, but for the readers like you, I apologize for the confusion I created. The problems are MINE, not the fault of antiX, but I’ve cleared them up anyway.

I recommend for most people to simply use the provided tools because they WORK!
Geeks like me can experiment; I can fix my mistakes and also ADMIT when I’ve made a mistake; though I’m experienced, I make plenty of mistakes and it’s great practice to keep my diagnostic skills sharp!

Anyway let me repeat it: the standard mechanisms in this release and other releases of antiX work just fine; nothing wrong here. In fact, most of us that are finding little problems here and there are due either to our respins, a typo or incompatibilities in the pieces we cobble together – NOT the fault of the antiX release!

• This reply was modified 4 months ago by Brian Masinick.

--
Brian Masinick
Alternate "Search B":
This search page

[c0pAMember]

Brian, you don’t have to apologize! I just thought the problem might be related to the logout menus. We all appreciate your efforts.

I’ll experiment with those scripts to see if s6-rc shuts down properly.

[Brian MasinickModerator]

s6-rc DOES shut down properly in my tests. See if the same is true for you.

--
Brian Masinick
Alternate "Search B":
This search page

[Author]

Posts