MX Linux Forum

Posted: **Mon Dec 18, 2023 4:21 pm**

Hi,

I made a fatal mistake of screwing up my MX-Linux 23.1 KDE install by attempting to install systemctl and forgot that this is a systemd command!
Why was I trying to do this? I was attempting to stop autodiscovery of printer(s) as what happens with most if not all GNU/Linux distributions these days is that the Linux kernel recognises what printer is attached and in the driver description, names it as a 'driverless printer' - this means it is not going to print without the Linux driver for any given brand of printer, from the manufacturer's support pages. I found an old thread about how to disable autodiscovery, starting off by editing avahi.conf but then it goes on to state about systemctrl which is a systemd element. So how do I stop this in MX-Linux 23.1 KDE which uses SysVinit?

Posted: **Mon Dec 18, 2023 5:58 pm**

swarfendor437 wrote: Mon Dec 18, 2023 4:21 pm Hi,

I made a fatal mistake of screwing up my MX-Linux 23.1 KDE install by attempting to install systemctl and forgot that this is a systemd command!
Why was I trying to do this? I was attempting to stop autodiscovery of printer(s) as what happens with most if not all GNU/Linux distributions these days is that the Linux kernel recognises what printer is attached and in the driver description, names it as a 'driverless printer' - this means it is not going to print without the Linux driver for any given brand of printer, from the manufacturer's support pages. I found an old thread about how to disable autodiscovery, starting off by editing avahi.conf but then it goes on to state about systemctrl which is a systemd element. So how do I stop this in MX-Linux 23.1 KDE which uses SysVinit?

On sysvinit one would stop the auto-discovery service like this:

Code: Select all

sudo service avahi-daemon stop

and disable like this:

Code: Select all

sudo update-rc.d  avahi-daemon remove

It may help to discourage cups to query the avaihi-disovered printer about their potential capabilities and not create a cups-printer entry for those discovered printer in cups.

Posted: **Mon Dec 18, 2023 8:37 pm**

Use the new MX service manager to first stop the ahavi daemon then to disable it.

I usually set up my network connected printers using the IPP (first choice) or DNSSD protocol.
As a FYI, digging deeper into the Windows stack, their default method for connecting to networked connected printers is IPP.

Posted: **Tue Dec 19, 2023 7:28 am**

In cat /etc/cups/cups-browsed.conf

# All configuration options described here can also be supplied on the
# command line of cups-browsed via the "-o" option. In case of
# contradicting settings the setting defined in the configuration file
# will get used.

# Unknown directives are ignored, also unknown values.
:
# Which protocols will we use to discover printers on the network?
# Can use DNSSD and/or CUPS and/or LDAP, or 'none' for neither.

# BrowseRemoteProtocols dnssd cups
BrowseRemoteProtocols none
:

or: pkill / disable 'cups-browsed' service overall ?

HTH l0dr3

MX Linux Forum

How to remove autodiscovery of printers in KDE 23.1?

How to remove autodiscovery of printers in KDE 23.1?

Re: How to remove autodiscovery of printers in KDE 23.1?

Re: How to remove autodiscovery of printers in KDE 23.1?

Re: How to remove autodiscovery of printers in KDE 23.1?