MXLinux 21.3 SysVinit and kernel issues resolved

[hopeless-attempt]

---

Running MXLinux 21.3 KDE 5.20.5 Debian 11.7

I've found Windscribe has issues with SysVinit and as MXLinux has the dual boot options of SysVinit or systemd have made this cumbersome workaround to successfully install Windscribe.

When booted with SysVinit install Windscribe using MX Package installer. This throws an error message and does not install correctly. But it does place an init script windscribe-helper in /etc/init.d/. Save this file somewhere. Copy below.

Reboot with systemd. Re-Install Windscribe via MX Package Installer or Windscribe's deb file. This does install correctly and Windscribe works under systemd. This re-install has removed the /etc/init.d/windscribe-helper file though.

Reboot with SysVinit. Copy saved windscibe-helper file to /etc/init.d/. Ownership to root.
I tried to enable windscribe-helper with the standard "sudo update-rc.d windscribe-helper defaults" but it didn't work.
Fortunately I have two SysVinit utility program installed - rcconf & sysv-rc-conf.
Enabled windscribe-helper with "sudo rcconf". Checked run levels with "sudo sysv-rc-conf". All O.K. windscribe-helper enabled but not yet started. It does start on a SysVinit reboot.

Now Windscribe works on both SysVinit & systemd.

HOWEVER, my latest install on MXLinux KDE had the Debian 6.1.25-1~mx21ahs+1 kernel and athough Windscribe would run it would NOT connect via wireguard and I had to use openvpn.
FIXED this by installing the default debian kernel Debian 5.10.179-1.

Finally Windscribe works perfectly using SysVinit or systemd and does connect via wireguard.

---

This is the windscribe-helper init script

#!/bin/sh

Generated by sysd2v v0.3 -- http://www.trek.eu.org/devel/sysd2v

kFreeBSD do not accept scripts as interpreters, using #!/bin/sh and sourcing.

if [ true != "$INIT_D_SCRIPT_SOURCED" ] ; then
set "$0" "$@"; INIT_D_SCRIPT_SOURCED=true . /lib/init/init-d-script
fi

BEGIN INIT INFO

Provides: windscribe-helper

Required-Start: $remote_fs

Required-Stop: $remote_fs

Should-Start: $local_fs

Should-Stop: $local_fs

Default-Start: 2 3 4 5

Default-Stop: 0 1 6

Description: Windscribe helper service

END INIT INFO

DESC="windscribe-helper"
DAEMON=/opt/windscribe/helper
PIDFILE=/var/run/windscribe-helper.pid
START_ARGS="--background --make-pidfile"

[kurtbahartr]

If someone came across this issue for whatever reason and got flabbergasted about the SysVinit script pasted here because of Markdown problems, here's a properly-formatted version;

#!/bin/sh

# Generated by sysd2v v0.3 -- http://www.trek.eu.org/devel/sysd2v

# kFreeBSD do not accept scripts as interpreters, using #!/bin/sh and sourcing.

if [ true != \"$INIT_D_SCRIPT_SOURCED\" ] ; then
 set \"$0\" \"$@\"; INIT_D_SCRIPT_SOURCED=true . /lib/init/init-d-script
fi

### BEGIN INIT INFO

# Provides: windscribe-helper
# Required-Start: $remote_fs
# Required-Stop: $remote_fs
# Should-Start: $local_fs
# Should-Stop: $local_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Description: Windscribe helper service

### END INIT INFO

DESC=\"windscribe-helper\"
DAEMON=/opt/windscribe/helper
PIDFILE=/var/run/windscribe-helper.pid
START_ARGS=\"--background --make-pidfile\"

I used GitHub APIs to get raw text of the issue body and echo -e to work around the JS/HTML formatting: echo -e $(curl -L https://api.github.com/repos/Windscribe/Desktop-App/issues/91 | jq '.body')

[hopeless-attempt]

Thanks kurtbahartr.

That looks a lot neater.

I have no experience with markdown.

All the best.

[kurtbahartr]

Thanks kurtbahartr.

That looks a lot neater.

You're welcome!

I have no experience with markdown.

Quick tip in the case of code: You can wrap texts with `a single backtick` for inline code and with
```
triple backticks
```
for

code blocks.

Here's a quick documentation should you need more in-depth info about GitHub's version of Markdown: https://github.com/lifeparticle/Markdown-Cheatsheet

All the best.

Same for you!