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

Bug#658579: marked as done (cups: parallel device gets stuck at 100% CPU with Xerox Phaser 3121)

Your message dated Tue, 10 Dec 2013 15:23:49 +0100
with message-id <2453295.LGUtZKLF3q@gyllingar>
and subject line Re: parallel gets stuck at 100% CPU
has caused the Debian Bug report #658579,
regarding cups: parallel device gets stuck at 100% CPU with Xerox Phaser 3121
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.)


-- 
658579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658579
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cups
Version: 1.5.0-16
Severity: normal

Dear Maintainer,

First of all, I would like to apologize if this is not the right
package; I think it is, but I'm really not sure. Maybe something
in the kernel.

In the last 2-3 days, it seems every operation that tries to access
my Xerox Phaser 3121 printer, which is connected through the parallel
port, gets stuck and never completes; I get a process on the host
that looks like this in "ps axuww":


lp        9324 99.9  0.0   5732  1104 ?        R    07:57 268:48 parallel:/dev/lp0 1547 sigal Cooks 1 TonerDensity=3 Duplex=None number-up=2 number-up-layout=btlr PageSize=A4 Resolution=300dpi InputSlot=Auto EconoMode=0 noJamRecovery Altitude=LOW MediaType=OFF PowerSave=5 job-uuid=urn:uuid:d8331db0-edd9-3d65-72d5-81b8567a00e8 job-originating-host-name=localhost time-at-creation=1328334501 time-at-processing=1328335027

The only way I found to solve this is to "lprm" the print jobs, bring
down the cups service, and "sudo kill -9" the process. If I just bring
down cups, the process stays up (also does not respond to SIGTERM); if
I just kill the process, cups respawns it; if I just bring down cups
and the process (leaving jobs in the queue), cups restarts it as soon
as it is brought back up.

Some of the time -- can't be sure -- I've gotten error messages printed
by the printer, complaining about a timeout.

Until yesterday, I was using the older, Samsung ML-1710 driver from
Foomatic/gdi; I switched to Splix with the actual Xerox model, but
it made no difference.

Another printer, connected via USB, continues to function normally.

Thanks for all your good work,

Shai.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cups depends on:
ii  adduser                3.113+nmu1
ii  bc                     1.06.95-2
ii  cups-client            1.5.0-16
ii  cups-common            1.5.0-16
ii  cups-filters           1.0~b1-3
ii  cups-ppdc              1.5.0-16
ii  debconf [debconf-2.0]  1.5.41
ii  ghostscript            9.04~dfsg-3
ii  libavahi-client3       0.6.30-6
ii  libavahi-common3       0.6.30-6
ii  libc6                  2.13-26
ii  libcups2               1.5.0-16
ii  libcupscgi1            1.5.0-16
ii  libcupsimage2          1.5.0-16
ii  libcupsmime1           1.5.0-16
ii  libcupsppdc1           1.5.0-16
ii  libdbus-1-3            1.4.16-1
ii  libgcc1                1:4.6.2-12
ii  libgnutls26            2.12.16-1
ii  libgssapi-krb5-2       1.10+dfsg~beta1-2
ii  libkrb5-3              1.10+dfsg~beta1-2
ii  libldap-2.4-2          2.4.28-1.1
ii  libpam0g               1.1.3-7
ii  libpaper1              1.1.24+nmu1
ii  libslp1                1.2.1-8
ii  libstdc++6             4.6.2-12
ii  libusb-1.0-0           2:1.0.9~rc3-3
ii  lsb-base               3.2-28.1
ii  poppler-utils          0.16.7-2+b1
ii  procps                 1:3.3.2-3
ii  ssl-cert               1.0.28

Versions of packages cups recommends:
ii  avahi-daemon                                        0.6.30-6
ii  colord                                              0.1.16-2
ii  cups-driver-gutenprint                              5.2.7-4
ii  foomatic-filters                                    4.0.9-1
ii  ghostscript-cups                                    9.04~dfsg-3
ii  printer-driver-gutenprint [cups-driver-gutenprint]  5.2.7-4

Versions of packages cups suggests:
ii  cups-bsd     1.5.0-16
ii  cups-pdf     <none>
ii  foomatic-db  20111206-1
ii  hplip        3.11.12-2
ii  smbclient    2:3.6.3-1
ii  udev         175-3

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

--- End Message ---
--- Begin Message --- 
Version: 1.0.16-2

Le samedi, 5 mai 2012, 17.24:11 Zrin Žiborski a écrit :
> After upgrading to versions from unstable -
> cups and cups-client to 1.5.2-10 and
> cups-filters to 1.0.16-2
> printing works again as expected.

Hereby closing, thanks !

Cheers, OdyX

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: