cups-browsed crashes when printing test page to remote printer

Bug #1904744 reported by Allan Dyer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cups-filters (Ubuntu)
New
Undecided
Unassigned

Bug Description

1)
lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
2)
apt-cache policy cups-filters
cups-filters:
  Installed: 1.27.4-1
  Candidate: 1.27.4-1
  Version table:
 *** 1.27.4-1 500
        500 http://hk.archive.ubuntu.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status
3)
I have several Ubuntu 20.04 LTS desktops configured to print to a CUPS print server with 4 printers. 3 of the printers work OK, the other one I can print a test page locally,
I would expect sending a test page from one of the desktops would result in the test page printing.

4) but sending a test page from one of the desktops results in the client CUPS showing:
Paused - "No destination host name supplied by cups-browsed for printer "Grassjewel", is cups-browsed running?"
When I check on the desktop system:
systemctl status cups-browsed
 cups-browsed.service - Make remote CUPS printers available locally
     Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled)
     Active: failed (Result: core-dump) since Wed 2020-11-18 21:31:48 HKT; 23min ago
    Process: 22293 ExecStart=/usr/sbin/cups-browsed (code=dumped, signal=SEGV)
   Main PID: 22293 (code=dumped, signal=SEGV)

Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV
Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Failed with result 'core-dump'.

Additional information: The 3 working printers are different manufacturer laser printers, on the network. The problem printer is an Epson dot-matrix printer connected to the CUPS server via a USB/Parallel converter.
Log files and core dump attached.

Revision history for this message
Allan Dyer (adyer) wrote :
Revision history for this message
Allan Dyer (adyer) wrote :
Revision history for this message
Allan Dyer (adyer) wrote :
Revision history for this message
Allan Dyer (adyer) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.