Yes it is in Debian as expected and it is intended for use in containers running on systemd hosts.

I see, that explains why it got confused running on a Devuan system!

~# apt-cache show systemctl

Yes it is in Debian as expected and it is intended for use in containers running on systemd hosts.

But systemctl is in the repositories

Interesting, I wasn't aware of that. It only needs Python, so I went ahead and installed it. Let's see what it does...

$ systemctl status ssh
/usr/bin/systemctl:1541: SyntaxWarning: invalid escape sequence '\w'
  expanded = re.sub("[$](\w+)", lambda m: get_env1(m), cmd.replace("\\\n",""))
/usr/bin/systemctl:1543: SyntaxWarning: invalid escape sequence '\w'
  new_text = re.sub("[$][{](\w+)[}]", lambda m: get_env2(m), expanded)
/usr/bin/systemctl:1628: SyntaxWarning: invalid escape sequence '\w'
  cmd3 = re.sub("[$](\w+)", lambda m: get_env1(m), cmd2)
/usr/bin/systemctl:1631: SyntaxWarning: invalid escape sequence '\w'
  newcmd += [ re.sub("[$][{](\w+)[}]", lambda m: get_env2(m), part) ]
ssh.service - OpenBSD Secure Shell server
    Loaded: loaded (/usr/lib/systemd/system/ssh.service, enabled)
    Active: inactive (dead)

Well, something happened! That part at the end appears similar to authentic systemctl output, but it's not correct. sshd was active, and the system had live clients connected when I ran this. Something also clearly went very wrong with those regexes.

Yes, it is a systemd tool sanitised by our devs/packagers to work, like it says, without systemd.

But as Devuan does not use systemd, the tool used to manage* services is service.
* ie: start, stop, status, restart and others.

It a native and time proven, easy to use Linux tool.
Knowing how to use it is important.

See here for a hint.

Best,

A.

But systemctl is in the repositories and is described as "daemonless "systemctl" command to manage services without systemd".
I must admit I don't know much about how daemons work.

sudo apt remove ipp-usb

this one has been helped a lot of times;
but it magically comes back to interrupt printing locally on my epson ecotank.

https://epson.com/Support/wa00821?utm_s … s-linux-us

systemctl restart cups-browsed

I'm not currently running cups on any of my systems, but keep in mind Devuan doesn't have systemd, and therefore doesn't use systemctl. You're probably going to want something more like this:

service cups-browsed restart

Maybe you can uninstall cups-browsed if your printer is directly attached to your PC, which is perhaps why some people have solved it by simply uninstalling it, but that didn't work for me on a network. Some have said you can uninstall cups-browsed as long as you arrange Cups to use the printer's fixed network address, by editing the Cups config files, but I've never tried that.

What works for me is restarting cups-browsed  :

systemctl restart cups-browsed

In Cups, on the admin page for an unprinted job I get this message:
"No destination host name supplied by cups-browsed for printer "EPSON_WF_5190_Series", is cups-browsed running?"

Possible solutions:

For lack of a better reply, I'd say that what you have is a very specific CUPS issue.

Unfortunately, Apple Corp. has blocked all acess to the huge source of data/information that were the CUPS archives.

That said, there is are new lists set up by the chap who wrote CUPS:

See here for general instructions:
https://subspace.kernel.org/subscribing.html

See here for specific CUPS lists instructions:
https://subspace.kernel.org/lists.linux.dev.html

For printing-architecture
subscribe       printing-architecture+subscribe@lists.linux.dev   
unsubscribe   printing-architecture+unsubscribe@lists.linux.dev
posting          printing-architecture@lists.linux.dev
archive          https://lore.kernel.org/printing-architecture/

For printing-users
subscribe      printing-users+subscribe@lists.linux.dev
unsubscribe  printing-users+unsubscribe@lists.linux.dev
posting          printing-users@lists.linux.dev
archive          https://lore.kernel.org/printing-users/

The background to all this hassle, more specifically, the archives at https://lists.cups.org/pipermail/cups/:

Up to (at least) May last year, the archive was accessible to anyone, suscribed or not.
Those suscribed to the list could post to all list members by sending mail to cups@cups.org
Just like most standard issue mailing lists ...

Some time ago I needed to look up something and found that attempting to access the archives
returned a *403 Forbidden* page.

A mail to cups-owner@cups org got me this reply:
---
More recent cups related stuff can be found at openprinting.org.
When apple bought cups, those lists went to their servers.
Mike quietly left apple years ago, and it appears that apple has removed the lists.
They own "cups". So Mike had to make a new name.
---
'Mike' obviously refers to Michael Sweet who left Apple in December 2019.

Unfortunately, a further email asking for more information went unanswered.
Bad vibes ...

It seems that I can still post to the list (ie: email does not bounce) and I receive other people's
posts containing replies so the list works, but the thread is not accessible.

I then posted to the OpenPrinting GitHub page asking about this and right away received a
reply from M.R. Sweet himself:

https://github.com/OpenPrinting/cups/discussions/1237

---
Unfortunately, lists.cups.org is an Apple-managed site and we have no control over its
contents or configuration...
The printing-users and printing-architecture lists on kernel.org are the current place for
discussing printing-related issues.
---

The thing is that all this went down without *any* notice sent to the list and the wealth of information that made up the archives are, thanks to the assholes at Apple Corp., lost to any and everyone who ever posted anything there.

The first example of such shitty behaviour came from yet another well known corporation (Oracle): after taking over Sun Microsystems, they blocked all access (mailing lists and downlaods) to anyone without a $ervice contract.

Best,

A.

There are others in the logs, but lots of duplicate messages

Any suggestions to track down and fix this?
It may be I have been bitten by the cups updates?