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

Bug#1033625: marked as done (cups constantly without timeout connects to network printer, does not print)



Your message dated Thu, 30 Mar 2023 13:10:53 +0100
with message-id <30032023130619.b367fe2cda3e@desktop.copernicus.org.uk>
and subject line Re: Bug#1033625:
has caused the Debian Bug report #1033625,
regarding cups constantly without timeout connects to network printer, does not print
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1033625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033625
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cups
Version: 2.4.2-2
Severity: important
X-Debbugs-Cc: johan.kroeckel@gmail.com

I am using a Kyocera Ecosys m5526cdw over the network. Printing stopped working (worked with this version before).

Now when I try to start a print job cups ends with a message "Der Druckauftrag wurde nicht angenommen.". BUT:

Now cups connects to the printer (LED on printer lights up as long as the pc is on) but nothing is printed. When I reboot, the LED stops to blink as long as the system is not completely booted, then the connection starts again.

After running cupsctl --debug-logging, error_log grows by around 30 megabytes per hour.

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups depends on:
ii  cups-client            2.4.2-2
ii  cups-common            2.4.2-2
ii  cups-core-drivers      2.4.2-2
ii  cups-daemon            2.4.2-2
ii  cups-filters           1.28.17-2
ii  cups-ppdc              2.4.2-2
ii  cups-server-common     2.4.2-2
ii  debconf [debconf-2.0]  1.5.82
ii  ghostscript            10.0.0~dfsg-9+b1
ii  libavahi-client3       0.8-9
ii  libavahi-common3       0.8-9
ii  libc6                  2.36-8
ii  libcups2               2.4.2-2
ii  libgcc-s1              12.2.0-14
ii  libstdc++6             12.2.0-14
ii  libusb-1.0-0           2:1.0.26-1
ii  poppler-utils          22.12.0-2+b1
ii  procps                 2:4.0.2-3

Versions of packages cups recommends:
ii  avahi-daemon  0.8-9
ii  colord        1.4.6-2.2

Versions of packages cups suggests:
pn  cups-bsd                                   <none>
pn  cups-pdf                                   <none>
pn  foomatic-db-compressed-ppds | foomatic-db  <none>
pn  smbclient                                  <none>
ii  udev                                       252.6-1

-- debconf information:
  cupsys/backend: lpd, socket, usb, snmp, dnssd
  cupsys/raw-print: true

--- End Message ---
--- Begin Message ---
On Thu 30 Mar 2023 at 09:55:24 +0200, Johan Kröckel wrote:

> Am Mi., 29. März 2023 um 13:23 Uhr schrieb Brian Potkin <
> claremont102@gmail.com>:

[...[
 
> > A print queue can also be manually set up by
> >
> >   lpadmin -p M5526cdw -v
> > "ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/" -E -m everywhere
> >
> > Test printing with
> >
> >   lp -d M5526cdw /etc/nsswitch.conf
> >
> 
> This worked. This works with a job pending in Kyocera_ECOSYS_M5526cdw as
> well.
> 
> Printing from a different device works as well
> while Kyocera_ECOSYS_M5526cdw has a pending job and keeps an open
> connection to the printer.
> 
> Cheers,
> >
> > Brian.
> >
> 
> Brian, thank you. Debugging such a problem is fun as long as someone guides
> you/me.

You appear happy with the outcome, John, so I am closing the report.

Cheers,

Brian.

--- End Message ---

Reply to: