cups-browsed problem

Gallerilt

New Member
Joined
Sep 6, 2023
Messages
29
Reaction score
1
Credits
271
After installing Debian 12 I have a problem with my printer. After boot I have to do
systemctl start cups-browsed to get it to work.
I have
cups-browsed.service enabled enabled
My cups-browsed is version 1.28.17-3+deb12u1
How to get the printer to work after boot without this manual systemctl command?
 


What is the printer [full make and model]

what dependencies did you install with cups?
 
After installing Debian 12 I have a problem with my printer. After boot I have to do
systemctl start cups-browsed to get it to work.
I have
cups-browsed.service enabled enabled
My cups-browsed is version 1.28.17-3+deb12u1
How to get the printer to work after boot without this manual systemctl command?
Normally if one has the systemd cups.service enabled, then it will start automatically at boot, for example, as root one would run:
Code:
systemctl enable cups.service
That command would enable the service and be sufficient to start the service to run the printer. The cups service brings in other dependencies. That's apparent from the unit file:
Code:
$ systemctl cat cups.service
# /usr/lib/systemd/system/cups.service
[Unit]
Description=CUPS Scheduler
Documentation=man:cupsd(8)
After=network.target nss-user-lookup.target nslcd.service
Requires=cups.socket

[Service]
ExecStart=/usr/sbin/cupsd -l
Type=notify
Restart=on-failure


[Install]
Also=cups.socket cups.path
WantedBy=printer.target multi-user.target

Once the cups service is enabled, all the relevant cups programs are loaded and running, as shown here:
Code:
$ systemctl -a | grep cups
  cups.path            loaded    active   running   CUPS Scheduler
  cups-browsed.service loaded    active   running   Make remote CUPS printers available locally
  cups.service         loaded    active   running   CUPS Scheduler
  cups.socket          loaded    active   running   CUPS Scheduler

If none of this is happening as expected on your system, the problem may be elsewhere.
 
Last edited:
All of this is happening as expected on my system, so what could be the problem?
 
All of this is happening as expected on my system, so what could be the problem?
I suggest to consult the logs soon after boot.

Install lnav which will enable you to read multiple logs in color:
Bash:
sudo apt install lnav

Then after boot run:
Bash:
sudo lnav /var/log

This will not recurse into sub-directories because bookworm's lnav is out of date. (you can but it takes a lot of time due to a bug)
To recurse use:
Bash:
sudo lnav -r /var/log

You can explicitly run it against specific directory within /log/ directory, if such directory is related to cups.
If you find anything suspicious share it here.
 
All of this is happening as expected on my system, so what could be the problem?
If the configs are set properly, and the system started in the normal way with systemctl, but the problem persists, then it's a troubleshooting situation. Perhaps if you could supply the details mentioned in post #2 by @Brickwizard it may help readers.

It's unclear as to why one would need to restart cups-browsed.service if it is already running, as indicated by the output of the command in post #3 which I'm assuming is the same or similar to the output on your machine.

A look at the journals may be a useful first step . For example, commands such as the following may output some relevant information:
Code:
journalctl -b | grep -i cups
journalctl -u cups.service -e
grep -i cups /var/log/syslog
less /var/log/cups/error_log

If you don't have any of the syslog packages installed, that's okay since the journal should cover it.

In particular look for any issues to do with cups-browsed.service, for example, output such as:
Code:
Started cups-browsed.service - Make remote CUPS printers available locally.
That output normally indicates proper set up if it's found after other output showing starting and stopping.

There may be some matter internal to the cups printer software that is interfering. One such element is unfinished jobs that may be left in the queue, unbeknown to the user. To check that, visit the URL: http://localhost:631 in a web browser, select Administration from the menu bar, login as root and from there go to Manage Printers -> <select_printer> -> Maintenance -> Cancel All Jobs. Then power cycle the printer.

The above are the first investigative steps I'd take.
 
Can I do without cups-browsed? It is a small LAN with one shared printer, shared with a Windows PC. .
 
What is the printer [full make and model]

what dependencies did you install with cups?
It is av Canon IP7200.
apt-cache depends cups
cups
Avhenger av: cups-client
Avhenger av: cups-common
Avhenger av: cups-core-drivers
Avhenger av: cups-daemon
Avhenger av: cups-filters
Avhenger av: cups-ppdc
Avhenger av: cups-server-common
|Avhenger av: debconf
Avhenger av: <debconf-2.0>
cdebconf
debconf
Avhenger av: ghostscript
Avhenger av: libcups2
Avhenger av: poppler-utils
Avhenger av: procps
Avhenger av: libavahi-client3
Avhenger av: libavahi-common3
Avhenger av: libc6
Avhenger av: libgcc-s1
Avhenger av: libstdc++6
Avhenger av: libusb-1.0-0
Anbefaler: avahi-daemon
Anbefaler: colord
Foreslår: cups-bsd
Foreslår: <cups-pdf>
printer-driver-cups-pdf
|Foreslår: foomatic-db-compressed-ppds
Foreslår: foomatic-db
foomatic-db-compressed-ppds
Foreslår: smbclient
Foreslår: udev

"Avhenger" means depends.

apt-cache depends cups-browsed
cups-browsed
Forutsetter: init-system-helpers
Avhenger av: cups-daemon
Avhenger av: lsb-base
sysvinit-utils
Avhenger av: libavahi-client3
Avhenger av: libavahi-common3
Avhenger av: libavahi-glib1
Avhenger av: libc6
Avhenger av: libcups2
Avhenger av: libcupsfilters1
Avhenger av: libglib2.0-0
Avhenger av: libldap-2.5-0
Ødelegger: cups-filters
Anbefaler: avahi-daemon
Erstatter: cups-filters
Forbedrer: cups
 
Can I do without cups-browsed? It is a small LAN with one shared printer, shared with a Windows PC. .
Yes, you can do without cups-browsed if you are not using your printer in a network, but rather just as a single printer running configured properly on a single machine. But it seems your set up is networked, so it will be needed since the cups-daemon depends on it:
Code:
$ apt-cache rdepends cups-browsed 
cups-browsed
Reverse Depends:
  cups-daemon
  education-networked-common
 
cannon can be a pig to get working on Linux, you may consider the proprietary drivers for 64 bit linux

 
Never had problems with Canon printers :-) Don't think this is a Canon problem. I think I have to do some log reading - the problem comes an goes. After reboot this time I get, and all is working:
systemctl status cups-browsed
● cups-browsed.service - Make remote CUPS printers available locally
Loaded: loaded (/etc/systemd/system/cups-browsed.service; enabled; preset: enabled)
Active: active (running) since Wed 2025-03-12 11:18:55 CET; 7min ago
Main PID: 20195 (cups-browsed)
Tasks: 3 (limit: 9338)
Memory: 4.6M
CPU: 356ms
CGroup: /system.slice/cups-browsed.service
└─20195 /usr/sbin/cups-browsed

Sorry if you feel I am nagging.
 
check to see if cups-backend-bjnp is installed or not if not install it check it through the Synaptic Package Manager

This package provides a back-end for CUPS printing system to interface with Canon printers using the proprietary USB over IP BJNP protocol
 
No I don't. Is this solution for not needing to use cups-browsed?
Are you referring to the post above this one, ?....if not, which one ?
 
The post above. If I installed cups-backend-bjnp, is this an alternative to cups-browsed? My IP7200 is not a USB-only printer, but a network printer. Is cups-backend-bjnp supposed to support also network printers? I'm having trouble finding info about this by search. Are there any advantages to this? I think my problem is linked to some systemctl/systemd problems, not linked to my IP7200.
Hope this was clarifying.
 
Try finding and installing it via Synaptic Package Manager.

if it works, all to the good

If it does not work, you can simply uninstall it, also via synaptic

No harm, no foul
 



Top