Hi, Johannes-
A couple of things come to mind as things to check:
1. Does SUSE require encryption to the server during IPP requests? (the
printer is added with a httpConnectEncrypt() call, but I am unsure if it is
working when encryption is required).
2. Does CUPS on SUSE 10.0-1 require that only root make the
httpConnectEncrypt() call?
3. Does CUPS on SUSE 10.0-1 try to parse the device URI that is being added?
I know that YaST has before rejected our hp: style URIs.
4. Is the PPD file for the added printer pre-existing on the disk, or are
they created by foomatic at runtime? (like Fedora does)
I will begin looking at this in more detail. Maybe you have some answers to
these questions?
Thanks,
Don
On 2/13/07, Johannes Meixner <[EMAIL PROTECTED]> wrote:
Hello,
On Feb 12 08:31 Aaron wrote (shortened):
> This is actually a known issue with Suse 10-10.1
Yes, I know that it is a known issue and that there is
no solution at the moment.
It even seems the reason is unknown at the moment.
I never had it before but now I can reproduce it
and I am interested to find out the actual reason.
> The workaround is to upgrade cups to 1.2.x.
This is not a possible workaround for the product which
I am talking about: Suse Linux Enterprise Desktop 10
(and also the Suse Linux Enterprise Server 10).
Both are based upon Suse Linux 10.1 which has CUPS 1.1.23.
Currently I am evaluating if an upgrade to the newest HPLIP
is possible for those products.
It is not possible in an enterprise environment to force our
customers to upgrade their whole printing system only because
of an upgrade of one printer driver package.
In business environment it is often not possible to upgrade
whatever software to whatever newer version because this may
invalidate existing certifications (third party software may be
certified to work o.k. e.g. with CUPS 1.1.23) or an upgrade
may invalidate existing support contracts (e.g. the support
department must be prepared to answer questions about a
particular software version running on a particular Linux
distribution running a particular hardware).
> We are looking at other solutions as well.
I would like to help you as good as I can to find the actual
reason and then try to find a solution so that an upgrade
to the newest HPLIP is possible for our business customers.
Is there a way to get even more detailed debug messages
what exactly hp-setup does (or tries to do) when it comes
to this error?
In particular because it works via CUPS command line tools
it indicates that CUPS should not be the actual reason.
I think it is something special what hp-setup does why it
doesn't work - I guess it does (or tries to do) something
which is not in full compliance to how CUPS works.
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
90409 Nuernberg, Germany WWW: http://www.novell.com/linux/
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
HPLIP-Help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hplip-help
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
HPLIP-Help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hplip-help
