Unknown device: ijs after natty dist-upgrade

Bug #704157 reported by Marc Deslauriers
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ghostscript (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: cups

After doing a dist-upgrade in natty, I can no longer print. Attempting to print a test page on my printer results in a page being printed with the following information on it:
Unknown device: ijs
Unrecoverable error: undefined in .uninstallpagedevice

etc.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: cups 1.4.5-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Jan 17 16:17:48 2011
Lpstat:
 device for HP-Officejet-j4680: hp:/net/Officejet_J4680_series?ip=192.168.66.8
 device for HPColorLaserJet: hp:/net/HP_Color_LaserJet_CP2025dn?zc=NPI8209DF
MachineType: LENOVO 6459CTO
Papersize: letter
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
PpdFiles:
 HPColorLaserJet: HP Color LaserJet cp2025dn hpijs pcl3, 3.10.9
 HP-Officejet-j4680: HP Officejet j4680 Series, hpcups 3.10.9
ProcEnviron:
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
 LC_MESSAGES=en_CA.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.37-12-generic root=/dev/mapper/defaultvg-root ro vt.handoff=7 quiet splash
SourcePackage: cups
dmi.bios.date: 11/14/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC5WW (2.25 )
dmi.board.name: 6459CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7LETC5WW(2.25):bd11/14/2008:svnLENOVO:pn6459CTO:pvrThinkPadT61:rvnLENOVO:rn6459CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 6459CTO
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO

Related branches

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Here's the log file from the troubleshooter after a different attempt.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Debian has changed the packaging scheme of Ghostscript vastly and I have overtaken the new scheme working towards having identical Ghostscript source packages in both Debian and Ubuntu (we have this already with cups, hplip, foomatic-*). This change made the "ijs" output device in Ghostscript getting lost. Fix is on the way.

Changed in cups (Ubuntu):
status: New → In Progress
affects: cups (Ubuntu) → ghostscript (Ubuntu)
Changed in ghostscript (Ubuntu):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ghostscript - 9.01~dfsg~svn12047-0ubuntu1

---------------
ghostscript (9.01~dfsg~svn12047-0ubuntu1) natty; urgency=low

  * New upstream release
     o SVN snapshot rev. 12047
    Taken back the ijs subdirectory into the repackaged source tarball as
    Ghostscript's build system does not support using an external, shared
    libijs (LP: #704913, LP: #704157).
    Removed the newly added ./cups/libs/ directory in the repackaging as
    we use the CUPS libraries of the cups package.
  * debian/rules: Removed ijs subdirectory from upstream source repackaging
    check and added cups/libs/ subdirectory.
  * debian/rules: Override a bug that if dynamically loadable X11 drivers are
    uses ("./configure --enable-dynamic") that in the core Ghostscript library
    the X11 drivers are also built in. This bug got most probably introduced
    with SVN rev. 12025.
  * debian/symbols.common: Updated for new upstream source. Applied patch
    which dpkg-gensymbols generated for debian/libgs9.symbols to this file.
 -- Till Kamppeter <email address hidden> Sat, 22 Jan 2011 11:25:36 +0100

Changed in ghostscript (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.