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

Bug#461354: Package: cupsys-driver-gutenprint Version: 5.0.0-3 error when unpacking with aptitude install



Package: cupsys-driver-gutenprint
Version: 5.0.0-3

Dear All,

I recently upgraded my computer from sarge to etch. In doing so I also
upgraded my version of CUPS from ver. 1.2.3 (manually installed from
sourcecode) to ver. 1.2.7 (the current debian-etch package). To use my
printer, an Epson Stylus CX-4200, I need the driver supplied by
gutenprint. Thus I attempted to install the cupsys-driver-gutenprint
package via aptitude install cupsys-driver-gutenprintThe package did not
install properly. The following error message was displayed on-screen:

cups-genppd.5.0: symbol lookup error: cups-genppd.5.0: undefined symbol:
stp_get_maximum_imageable_area
can't close cups-genppd pipe: at /usr/sbin/cups-genppdconfig.5.0 line 418.
dpkg: error processing cupsys-driver-gutenprint (--install): subprocess
post-installation script returned error exit status 127
Errors were encountered while processing: cupsys-driver-gutenprint

Is the cupsys-driver-gutenprint package currently (17. January 2008,
~3:15 am Eastern Time, ~20:15 UTC) available broken, or am I doing
something wrong in the installation?
Based on the above error message I think that the package contains errors
that prevent a proper installation.

Some information about my OS that might be useful:
Debian Etch ver. 4.0 rev. 2
kernel: 2.6.18-5-686
libc: libc-2.3.6.so
libc6: libc6 version 2.3.6.ds1-13etch4
aptitude: aptitude version 0.4.4-4
dpkg: dpkg version 1.13.25
cupsys: cupsys 1.2.7-4etch2

I would greatly appreciate your assistance in resolving this matter.
Please do not hesitate to e-mail me at ajurgensen@mail.src.wisc.edu , if
you have any further questions.

Best Regards,

Astrid Jurgensen

P.S.: Your bug report website claims that the Package name and Version
number should be in the first and second line of the message body,
respectively. I have this message twice before already with the Package
name and Version listed as instructed on your website. Both times the 
message was filed as junk. In this third attempt I am sending the 
message as plain text. Hopefully this will go through.
If the bug report message needs to be sent in plain text format, it might
be useful to include this in the instructions on your website. 
For webmail, sending a message as plain text is usually not the 
default.

Reply to: