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

Bug#402538: kdeprint: escputil fails with usb printer



Package: kdeprint
Version: 4:3.5.5a.dfsg.1-2
Severity: normal



-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kdeprint depends on:
ii  enscript               1.6.4-11          Converts ASCII text to Postscript,
ii  kdelibs4c2a            4:3.5.5a.dfsg.1-5 core libraries and binaries for al
ii  libc6                  2.3.6.ds1-8       GNU C Library: Shared libraries
ii  libgcc1                1:4.1.1-19        GCC support library
ii  libqt3-mt              3:3.3.7-1         Qt GUI Library (Threaded runtime v
ii  libstdc++6             4.1.1-19          The GNU Standard C++ Library v3
ii  poster                 1:19990428-8      Create large posters out of PostSc
ii  psutils                1.17-24           A collection of PostScript documen

Versions of packages kdeprint recommends:
ii  evince [postscript-viewe 0.4.0-2+b2      Document (postscript, pdf) viewer
ii  gs-esp [postscript-viewe 8.15.3.dfsg.1-1 The Ghostscript PostScript interpr
ii  gv [postscript-viewer]   1:3.6.2-2       PostScript and PDF viewer for X

-- no debconf information
In the print manager you can select the printer tool - escputil and it fails to 
connect providing an error message instead. Changing the printer device uri 
to /dev/usr/lp0 lets it work but confuses other things.

CUPS doesn't use the actual USB port in the printer device URI, but a pseudo-URI 
based on information obtained by polling the USB port (manufacturer and model). 
This port<->device mapping is currently not supported by escputil or kdeprint. 
The only workaround is to use a device URI like usb:/dev/usb/lp0 instead of 
the URI proposed by the wizard (coming from CUPS) when creating the printer.



See http://bugs.kde.org/show_bug.cgi?id=97113



Reply to: