[cups.bugs] cups 220.127.116.11 crash
stefano.sabatini-lala at poste.it
Sat Sep 6 02:31:58 PDT 2008
On date Thursday 2008-09-04 21:56:36 +0200, Stefano Sabatini wrote:
> On date Thursday 2008-09-04 09:48:42 -0700, Michael R Sweet wrote:
> > Stefano Sabatini wrote:
> > > ...
> > > So they are:
> > > cups-common + cups-utils 18.104.22.168
> > OK, so for starters there is no CUPS 22.214.171.124. What you have is not
> > a standard CUPS distribution, so you'll need to report this problem
> > to your Linux distributor.
> Well OK, the version was indeed 1.3.8-1 (the last -1 was added by
> Debian, yes I know it means it is a patched/adapted version).
> > > foomatic-db-engine 3.0.2
> > > foomatic-db-gutenprint 5.0.2-4
> > Gutenprint does not require foomatic, which is an entirely unnecessary
> > piece of software for 99.9% of all printers that are supported through
> > CUPS today.
> Good to know.
> > > cups-driver-gutenprint 5.0.2-4
> > > gimp-gutenprint 5.0.2-4
> > Gutenprint is only needed for inkjet printers.
> So I suppose I need it.
> > > ...
> > > lpstat -t is crashing the server. So now I wonder, there is some way
> > > to debug this? Is it a known problem?
> > It is not a known problem, but as I said above you are not using a
> > standard CUPS release.
> > The /var/log/cups/error_log file may provide some hints as to the
> > cause of the crash, and your Linux distributor will probably want a
> > copy of it when they try to determine the cause of the problem.
> No unfortunately that file is completely missing.
> > > BTW, where should I ask general usage question, even if not related to
> > > some bugs?
> > The cups.general forum is the place to ask general usage questions.
> OK, thank you for your time.
Purging and reinstalling everything (libcups2 included) it started to
work again, so it wasn't obviously cups fault (I think it depended on
a .so versioning issue).
Linux user number 337176 (see http://counter.li.org)
More information about the cups-devel