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

Bug#757077: marked as done (Fwd: printer-driver-gutenprint: Updating ppd in printer queues during package updates)

Your message dated Fri, 22 Jun 2018 20:38:47 +0100
with message-id <22062018104354.cfa0c81b10cb@desktop.copernicus.org.uk>
and subject line Re: Bug#757077: Fwd: printer-driver-gutenprint: Updating ppd in printer queues during package updates
has caused the Debian Bug report #757077,
regarding Fwd: printer-driver-gutenprint: Updating ppd in printer queues during package updates
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.)


-- 
757077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757077
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: printer-driver-gutenprint
Version: 5.2.10-3
Severity: wishlist
Tags: d-i

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I updated printer-driver-gutenprint and my printer stopped working, the
error in printing job said "The PPD version (5.2.9) is not compatible with
Gutenprint 5.2.10.".

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

I deleted the printer and I reinstalled because it was impossible to change the printer
ppd. I selected a new one using the web interface, saved,  but when I looked
again at the prenter's settings it was back to the original outdated ppd.

   * What was the outcome of this action?

That did the trick and the printer is working again, but then looking at the logs
I noticed a message saying that running cups-genppdupdate.5.2 would have fixed
the problem.

   * What outcome did you expect instead?

I was wondering if it would be possible to run cups-genppdupdate.5.2 after
the package update, either automatically or interactively (i.e. asking the
user if he/she wants to run the ppd updater).

Also, I was wondering why it wasn't possible to change the ppd using the web
interface.

Here are the relevant logs.

Thank you and have a nice day,

Paolo

==================== LOGS START

==== I think here is when I attempted to change ppd to the queue using the
==== web interface

E [04/Aug/2014:20:17:32 +0800] [Client 15] Request for non-absolute resource
"".
E [04/Aug/2014:20:17:32 +0800] [Client 15] Request for non-absolute resource
"".
W [04/Aug/2014:20:17:32 +0800] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
'Canon_iP2700_series-Gray..' already exists
W [04/Aug/2014:20:17:32 +0800] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
'Canon_iP2700_series-RGB..' already exists


==== Here is the error saying the ppd is not compatible
E [04/Aug/2014:20:17:47 +0800] [Job 507] The PPD version (5.2.9) is not
compatible with Gutenprint 5.2.10.
E [04/Aug/2014:20:17:47 +0800] [Job 507] Job stopped due to filter errors;
please consult the error_log file for details.

[...]

D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint:
============================================================
D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint:
VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint: 5.2.10 Starting
D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint: command line:
Canon_iP2700_series '507' 'paolo' 'KennethBirthCert.jpg' '1' <args>
D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint: using PPD file
/etc/cups/ppd/Canon_iP2700_series.ppd
D [04/Aug/2014:20:17:47 +0800] [Job 507] Start rendering...
D [04/Aug/2014:20:17:47 +0800] [Job 507] Set job-printer-state-message to
"Start rendering...", current level=INFO
D [04/Aug/2014:20:17:47 +0800] [Job 507] Processing page 1...
D [04/Aug/2014:20:17:47 +0800] [Job 507] Set job-printer-state-message to
"Processing page 1...", current level=INFO
D [04/Aug/2014:20:17:47 +0800] [Job 507] Set job-printer-state-message to
"The PPD version (5.2.9) is not compatible with Gutenprint 5.2.10.", current
level=ERROR
D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint: If you have upgraded
your version of Gutenprint
D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint: recently, you must
reinstall all printer queues.
D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint: If the previous
installed version of Gutenprint
D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint: was 5.0.0 or higher,
you can use the `cups-genppdupdate.5.2'
D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint: program to do this; if
the previous installed version
D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint: was older, you can use
the Modify Printer command via
D [04/Aug/2014:20:17:47 +0800] [Job 507] Gutenprint: the CUPS web interface:
http://localhost:631/printers.
D [04/Aug/2014:20:17:47 +0800] [Job 507] PID 23570
(/usr/lib/cups/filter/rastertogutenprint.5.2) stopped with status 1.
D [04/Aug/2014:20:17:47 +0800] [Job 507] Hint: Try setting the LogLevel to
"debug" to find out more.
D [04/Aug/2014:20:17:47 +0800] [Job 507] Sent 0 bytes...

==================== LOGS END

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-rc6-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages printer-driver-gutenprint depends on:
ii  cups                             1.7.4-1
ii  cups-client                      1.7.4-1
ii  cups-filters [ghostscript-cups]  1.0.55-1
ii  libc6                            2.19-7
ii  libcups2                         1.7.4-1
ii  libcupsimage2                    1.7.4-1
ii  libgutenprint2                   5.2.10-3
ii  libusb-1.0-0                     2:1.0.19-1

printer-driver-gutenprint recommends no packages.

Versions of packages printer-driver-gutenprint suggests:
pn  gutenprint-doc      <none>
ii  gutenprint-locales  5.2.10-3

-- no debconf information


--- End Message ---
--- Begin Message --- 
tags 757077 - moreinfo
thanks.



On Tue 05 Aug 2014 at 14:23:33 +0800, Paolo Scarabelli wrote:

> Package: printer-driver-gutenprint
> Version: 5.2.10-3
> Severity: wishlist
> Tags: d-i
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate
> ***
> 
>    * What led up to the situation?
> 
> I updated printer-driver-gutenprint and my printer stopped working, the
> error in printing job said "The PPD version (5.2.9) is not compatible with
> Gutenprint 5.2.10.".
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> 
> I deleted the printer and I reinstalled because it was impossible to change
> the printer
> ppd. I selected a new one using the web interface, saved,  but when I looked
> again at the prenter's settings it was back to the original outdated ppd.
> 
>    * What was the outcome of this action?
> 
> That did the trick and the printer is working again, but then looking at
> the logs
> I noticed a message saying that running cups-genppdupdate.5.2 would have
> fixed
> the problem.
> 
>    * What outcome did you expect instead?
> 
> I was wondering if it would be possible to run cups-genppdupdate.5.2 after
> the package update, either automatically or interactively (i.e. asking the
> user if he/she wants to run the ppd updater).
> 
> Also, I was wondering why it wasn't possible to change the ppd using the web
> interface.
> 
> Here are the relevant logs.
> 
> ==================== LOGS START

[...]

I am going to assume that Didier 'OdyX' Raboud's assessment is along
along the right lines and close this report. In the intervening period
one would hope the issue has resolved itself.

One way to re-run updating the PPDs is:

1. touch /usr/share/cups/ppd-updaters/*

2. apt --reinstall install cups

Regards,

Brian.

--- End Message ---
Reply to: