[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#908147: restarting cups-browsed deleted print jobs



Package: cups-browsed
Version: 1.21.1-1
Severity: grave

I had an two jobs of online receipts set to print to a cups-browsed
remote print queue (a PDF printer on a remote machine), and a bit after
printing noticed that print handn't completed. I checked the local CUPS
status page and saw a message that cups-pdf hadn't provided a host name,
confirm it is running (compare bug #887495).

I checked (via systemctl status), it was running:

root@Zia:~# systemctl status cups-browsed.service 
● cups-browsed.service - Make remote CUPS printers available locally
   Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2018-09-06 00:00:04 EDT; 13h ago
 Main PID: 31796 (cups-browsed)
    Tasks: 3 (limit: 4915)
   Memory: 5.0M
   CGroup: /system.slice/cups-browsed.service
           └─31796 /usr/sbin/cups-browsed

Sep 06 00:00:04 Zia systemd[1]: Started Make remote CUPS printers available locally.

... since it wasn't working, I did the obvious thing: systemctl restart cups-browsed.service

After doing so, the queue in the browser refreshed and showed empty. But
I checked — the PDFs were not created. Showing completed jobs shows
nothing. Looking in /var/spool/cups (on both the local machine and the
remote machine) shows no sign of the two jobs.

So it appears restarting cups-browsed deletes all pending print jobs.
Unfortunately, they're just gone ... hope I don't need those receipts.

A test page now works, so at least it fixed the queue. Testing
restarting it again, the job history is indeed gone, so that confirms
its deleting the data.

Unexpectedly and without warning discarding user data (pending print
jobs) really isn't OK, especially when CUPS itself is suggesting the
action that led to it.

Also, it looks like it was automatically restarted yesterday & this morning at
midnight; that makes this worse.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (200, 'unstable'), (150, 'stable'), (100, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en_GB (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups-browsed depends on:
ii  cups-daemon       2.2.8-5
ii  libavahi-client3  0.7-4
ii  libavahi-common3  0.7-4
ii  libavahi-glib1    0.7-4
ii  libc6             2.27-5
ii  libcups2          2.2.8-5
ii  libcupsfilters1   1.21.1-1
ii  libglib2.0-0      2.56.1-2
ii  libldap-2.4-2     2.4.46+dfsg-5
ii  lsb-base          9.20170808

Versions of packages cups-browsed recommends:
ii  avahi-daemon  0.7-4

cups-browsed suggests no packages.

-- Configuration Files:
/etc/cups/cups-browsed.conf changed:
BrowseRemoteProtocols dnssd cups
BrowsePoll watt.home


-- no debconf information

Reply to: