New printer added after each kernel upgrade

Hi,
my environment:

System Details Report


Report details

  • Date generated: 2026-08-11 15:31:05

Hardware Information:

  • Hardware Model: TUXEDO TUXEDO Polaris 17 Intel Gen1
  • Memory: 16.0 GiB
  • Processor: Intel® Core™ i7-10750H × 12
  • Graphics: Intel® UHD Graphics (CML GT2)
  • Graphics 1: NVIDIA GeForce GTX 1650 Ti
  • Disk Capacity: 750.2 GB

Software Information:

  • Firmware Version: N.1.05
  • OS Name: Fedora Linux 44 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 50
  • Windowing System: Wayland
  • Kernel Version: Linux 7.1.7-200.fc44.x86_64

I have only one printer attached as Officejet_Pro_8600 . After each kernel upgrade an additional printer is added as Officejet_Pro_8600_35C3A4 . I often remove this additional printer using the ‘System setting’, but it is always added again after having upgraded. CUPS only knows Officejet_Pro_8600 .
How can I prevent that as Officejet_Pro_8600_35C3A4 is added again and again?

Thank you in advance,
Jochen

Ignore the one that is automatically created and only print to the one that you have defined and is known to work. Set the one that works as the default so it does not try to use the other one. I have had similar actions with my HP printer queues for a long time and grew tired of removing the one that is automatically defined by the system.

The difference seems to be that you probably added the printer that works using hplip and the other one is system defined and does not use the hp driver. After all the Officejet Pro 8600 is almost 15 years old (from its first release) and may not even be properly supported by ipp (which is the driver used for the system generated print queue.)

Have you enabled cups-browsed?

this should happen at every boot, or restart of cups-browsed, unless the system is restarted only after kernel upgrades.

network printer?

/etc/cups/cups-browsed.conf

# Which protocols will we use to discover printers on the network?
# Can use DNSSD or 'none'.

BrowseRemoteProtocols none

for an usb printer you probably need to disable cups-browsed, which is the default setting.

$ systemctl  status cups-browsed
○ cups-browsed.service - Make remote CUPS printers available locally
     Loaded: loaded (/usr/lib/systemd/system/cups-browsed.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

You pretty much don’t want to run it at all these days. Most of its functionality was removed after the latest security incident with cups-browsed.

cups-browsed is disabled.

My default printer is a network printer : hp:/net/Officejet_Pro_8600?ip=192.168.178.10

Sure, I could ignore the added printer. But whenever my wife uses our notebook and wants to print she asks me which printer she should use…:roll_eyes: . So for me the best solution would be that there is only one printer visible in our environment.

Please share output of lpstat -s showing both queues and output of avahi-browse -at ( only the relevant printer related lines)

How is the printer connected to the network, LAN and/or WIFI?
Not sure but does the printer have BT or WIFI_direct enabled?

How is the printer attached? Your model supports Airprint, which should work with Linux IPP (until Apple changes Airprint!). There have been issues with USB connections, but those appear to have been resolved (Airprint was originally for iPhones, so targeted WiFi) in https://github.com/OpenPrinting/ipp-usb, but the work to make a USB printer appear like a network device is not trivial. The problem facing users in the current environment is the possibility of bugs affecting security and vendors who would rather sell new printers than support out-of-warranty models. I would verify that both printer configurations work in case problems appear with one.

AirPrint is very similar to Mopria and to IPP-Everywhere. The Printer Working Group is a group of major printer manufacturer and defines the PWG standards. Microsoft is changing its printer support to Mopria instead of the printer provided drivers. Android devices also uses the Mopria standard.

If apple changes AirPrint then the result would be that you can’t printer from Apple devices, and that would be bad for Apple.

Dear all,

‘kernel update’ is not the reason for adding the printer. Your remarks above led me to another assumption that I could verify right now:
the printer is attached via ethernet LAN. After having checked using the printer’s ‘Embedded Web Server (Integrierter Web-Server)’ and looking at all the options I detected the option IPP Internet Printing Protocol. Obviously it was activated all the time. I activated/de-activated IPP several times now with the result, that the activated IPP caused the printer to be added.
I now deactivated permantently…

Thank you,
Jochen