Hello.

Thank you for your reply.

The python on my system is whatever it is that comes as stock on Devuan 4, which was freshly installed as a full disk encrypted system installation. I do not use python and so am unable to know if my installation is complete or missing anything.

I assume you are actually running protonvpm-cli on your system. I am curious if you have tried to install protonvpn according to the version 2 installation instructions on the protonvpn site for debian. The protonvpn  versions at the site are for both the gui and cli versions and are available  in both stable and beta form .

Both the gui and cli versions installed and failed to run on my system.

If I am missing any files on my system that would allow the git version 2 community protonvpn-cli to run on my system I would be only to happy to make whatever changes need to be made so when I build the git version of protonvpn-cli it will run cleanly.

When you have a moment, please reply to this message and build and install the community version of protonvpn-cli again. In your reply, please list the step by step commands you have used to build and install it.

If you have updated the version of python on your system or installed additional modules that you think have contributed to your successful installation, please list them so I can update my system as required; and what version of Devuan are you running.

Please, when you have the time,  try and install and run protonvpn, gui and cli versions, both beta and stable, on your system following the instructions on the protonvpn site. If they install and run cleanly and you are not using version 4 of devuan, then this is a problem that needs to be reported and fixed on version 4.

In my original post, when protonvpn, the gui version, failed to start, the runtime error message issued  ended with the following statement:

You have said that has nothing to do with systemd.

What does that statement refer to.

Best,

Colby

PS: You are quite correct, the bash script version is well past end of life. I first used it when it first came out for Linux and that was some years ago. For the moment however it has the virtue of being the only version that works, on my system.

@golinux

Hi.

For the THIRD time I am going to post to this thread the sources.list of the repositories I have used which produced a working mate 1.20 desktop COMPLETE with a working Mate power-manager and Mate network manager on Devuan 2.0 installed via netinst.

My Devuan 2.0-Release installation did not include the default Devuan desktop. It did include the Mate desktop component of Devuan 2.0-Release.

Here are some details so you have a complete picture of where I started from and the steps I took to get mate 1.20 with working mate-power-manager and network-manager (nm-applet) on my system.

After that installation I proceeded to reconfigure the desktop to have a single panel and a new desktop background. I compiled and installed a new theme - Vimix, available at the GIT. I added two sets of icons I have used since the release of the gtk2-version of the desktop. I tested to see if Caja would use some of these icons correctly to represent files and directories. It did not, as is usual since the switch to GTK3. These icons rendered correctly on Devuan1. I installed a freetype.sh and libreoffice.sh file in /etc/profile.d to ensure font rendering that I prefer and altered the /etc/fonts.d by removing various hints scripts to ensure Firefox rendered text as I prefer. I used dconf-editor to make various additional changes.

At the end of this I had a desktop that was similar to the desktop I used when gtk1 was the desktop toolkit and almost exactly like the desktop configuration I had when the desktop used the gtk2 toolkit. The theme I used then was entirely different and I miss it enough to from time to time consider returning to devuan-1.

The default mate desktop version included with Devuan-2 has various annoying cosmetic bugs which only seem to be completely fixed in mate 1.20.2. This has also been true on the mate release on  Manjaro and Ubuntu. This is not specific to the Devuan-2 release but to the Mate-desktop.

These bugs are greatly reduced in mate 1.20 on Manjaro, Ubuntu and Devuan-2.

I decided to try to upgrade mate to version 1.20 again. Unlike my prior attempts to upgrade to mate 1.20 using the Devuan-2 release candidate, this time, using Devuan-2-Release, the upgrade was completely uneventful.

This is what my sources.list contained before I upgraded to mate 1.20. It has not been changed since that upgrade.

# deb cdrom:[devuan_ascii_2.0.0_amd64_netinst]/ ascii main non-free

# deb cdrom:[devuan_ascii_2.0.0_amd64_netinst]/ ascii main non-free

deb http://pkgmaster.devuan.org/merged/ ascii main non-free contrib
deb-src http://pkgmaster.devuan.org/merged/ ascii main non-free contrib

deb http://pkgmaster.devuan.org/merged/ ascii-security main non-free contrib
deb-src http://pkgmaster.devuan.org/merged/ ascii-security main non-free contrib

deb http://pkgmaster.devuan.org/merged/ ascii-updates main non-free contrib
deb-src http://pkgmaster.devuan.org/merged/ ascii-updates main non-free contrib

deb http://pkgmaster.devuan.org/merged/ ascii-backports main non-free contrib

deb http://www.hezeh.org/packages/ ascii main contrib non-free
deb-src http://www.hezeh.org/packages/ ascii main contrib non-free

You have stated that I should not use debian packages because ...

If there are any debian repositories in my sources.list please point them out to me so I can remove them.

After the upgrade to mate 1.20, I removed wicd and xfce-power-manager from my system and replaced them with the following packages which all have origins in DEVUAN and HEZEH repositories.

gnome-power-manager                     3.22.2-2
mate-power-manager                        1.20.0-1+hezeh1
mate-power-manager-common         1.20.0-1+hezeh1

network-manager                              1.6.2-3+devuan1.1
network-manager-gnome                  1.4.4-1

Here are the origins for all of the packages listed above.

apt-cache policy gnome-power-manager
gnome-power-manager:
  Installed: 3.22.2-2
  Candidate: 3.22.2-2
  Version table:
*** 3.22.2-2 500
        500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
        100 /var/lib/dpkg/status

apt-cache policy mate-power-manager
mate-power-manager:
  Installed: 1.20.0-1+hezeh1
  Candidate: 1.20.0-1+hezeh1
  Version table:
*** 1.20.0-1+hezeh1 500
        500 http://www.hezeh.org/packages ascii/main amd64 Packages
        100 /var/lib/dpkg/status

mate-power-manager-common:
  Installed: 1.20.0-1+hezeh1
  Candidate: 1.20.0-1+hezeh1
  Version table:
*** 1.20.0-1+hezeh1 500
        500 http://www.hezeh.org/packages ascii/main amd64 Packages
        100 /var/lib/dpkg/status
     1.16.2-1+deb9u1 500
        500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages

apt-cache policy network-manager
network-manager:
  Installed: 1.6.2-3+devuan1.1
  Candidate: 1.6.2-3+devuan1.1
  Version table:
*** 1.6.2-3+devuan1.1 500
        500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
        100 /var/lib/dpkg/status

apt-cache policy network-manager-gnome
network-manager-gnome:
  Installed: 1.4.4-1
  Candidate: 1.4.4-1
  Version table:
*** 1.4.4-1 500
        500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
        100 /var/lib/dpkg/status

Please show me the DEBIAN repository in the above list. I will be happy to remove the package.

Of course maybe that's not the problem. So to continue.

MSI asked/stated:

So, mate-power-manager here is a third-party package that has apparently been rebuilt so it won't depend on systemd and network-manager is a genuine Devuan package that has been forked from Debian in order to eliminate the systemd dependency.

My response to that was:

I have not looked at the source code or queried the maintainers for these packages, therefore I can not give you an authoritative answer to your question.

Though I have been programming since 1966, I have found that does not give me supernatural insight into other peoples code. Also, not everybody who uses a system like Devuan is a programmer.

The question is appropriate, asking for a clarification I can not give because I do not and have not worked with the code. If MSI is a programmer then all he need do is look at the code, or the change log for the package, but if he is not, or if the code base is large, then what.

He could send the same question to the package MAINTAINER and see if he gets an answer.

In particular.

dpkg-query -W -f='${Maintainer}' gnome-power-manager
Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>

dpkg-query -W -f='${Maintainer}' mate-power-manager
Antonio Volpicelli <nioanto@live.it>

dpkg-query -W -f='${Maintainer}' power-manager-common
dpkg-query: no packages found matching power-manager-common

dpkg-query -W -f='${Maintainer}' network-manager
Vincenzo (KatolaZ) Nicosia <katolaz@freaknet.org>

dpkg-query -W -f='${Maintainer}' network-manager-gnome
Utopia Maintenance Team <pkg-utopia-maintainers@lists.alioth.debian.org>

This is a start in contacting people familiar with the code who can give MSI an authoritative answer to his question.

That's the best I could do in trying to answer his question.

You do understand that the packages these people maintain are all in DEVUAN or HEZEH repositories - right?

So getting back to those DEBIAN packages and repositories..

How bout you educating me about where those DEBIAN repositories are in my sources.list and what are the packages I'm using that are from DEBIAN.

Hi

Both power manager and network manger run on devuan Mate-1.20. I installed them from devuan repositories and hezeh, as listed in my source.list file which follows.

I removed wicd and xfce-power-manager.

I'm not going to argue the merits of these applications, that's not really the issue. I customize my desktop and system as I choose. That's what was attractive about linux when it first came out; at least to me.

As to systemd, my only interest in it is whether it's running or not.

These are the packages I have installed and running on my system:

gnome-power-manager                       3.22.2-2
mate-power-manager                          1.20.0-1+hezeh1
mate-power-manager-common           1.20.0-1+hezeh1

network-manager                                1.6.2-3+devuan1.1
network-manager-gnome                    1.4.4-1

They can be found in:

======my repositories

# deb cdrom:[devuan_ascii_2.0.0_amd64_netinst]/ ascii main non-free

# deb cdrom:[devuan_ascii_2.0.0_amd64_netinst]/ ascii main non-free

deb http://pkgmaster.devuan.org/merged/ ascii main non-free contrib
deb-src http://pkgmaster.devuan.org/merged/ ascii main non-free contrib

deb http://pkgmaster.devuan.org/merged/ ascii-security main non-free contrib
deb-src http://pkgmaster.devuan.org/merged/ ascii-security main non-free contrib

deb http://pkgmaster.devuan.org/merged/ ascii-updates main non-free contrib
deb-src http://pkgmaster.devuan.org/merged/ ascii-updates main non-free contrib

deb http://pkgmaster.devuan.org/merged/ ascii-backports contrib non-free main 

deb http://www.hezeh.org/packages/ ascii main contrib non-free
deb-src http://www.hezeh.org/packages/ ascii main contrib non-free

Hi,

I've read that both mate-power-manager and mate-network-manager are dependent upon systemd. This is a recent dependency for both applications as they were working for the Gnome2 desktop, from which mate was derived,  and if memory serves me both were present in the gnome 1 desktop based on gtk1. This was a very different animal under the hood and used Orbit, to provide the Gnu Network Object Model Environment,  as an object request broker, which was a GNU development, adopted by the Gnome project. The Gnome desktop was started and run by Miguel de Icaza and Federico Mena and many many volunteers, not the current crew at gnome.

Systemd is not running on my system. There is an /etc/systemd directory with a few entries none of which concern mate-power-manager. There is some networking window dressing, but how these files are used without systemd is unclear to me . Systemd became a Gnome project dependency in 2011. All I know about systemd is I don't want to run on a system that is dependent on it.