Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot print via (all-in-one) printserver #2185

Closed
michaelrsweet opened this issue Jan 9, 2007 · 3 comments
Closed

cannot print via (all-in-one) printserver #2185

michaelrsweet opened this issue Jan 9, 2007 · 3 comments
Labels
priority-low wontfix This will not be worked on
Milestone

Comments

@michaelrsweet
Copy link
Collaborator

michaelrsweet commented Jan 9, 2007

Version: 1.2.7
CUPS.org User: macias

CUPS 1.1.x version can print via printserver without any problems, however 1.2.x version simply refuses to do anything.

The problem was originally reported on OpenSUSE bugzilla:
https://bugzilla.novell.com/show_bug.cgi?id=217215

Printer: Lexmark E120,
Printserver: USRobotics 9108A
Connection: http://192.168.1.1:1631/printers/My_Printer

@michaelrsweet
Copy link
Collaborator Author

michaelrsweet commented Jan 9, 2007

CUPS.org User: mike

Unless you (or USR) can send us one of these print servers, there is little we can do to help you. The Novell folks that told you about the device error were correct - the print server is returning an error for a valid IPP request, and IPP is not always a well-supported protocol in network gear... The fact that USR is running it on a non-standard port points to USR not wanting to support IPP yet...

@michaelrsweet
Copy link
Collaborator Author

michaelrsweet commented Jan 9, 2007

CUPS.org User: macias

Unless you (or USR) can send us one of these print servers, there is
little we can do to help you.

CUPS 1.1.x works. So I can help by testing patches while fixing 1.2.x series. Something was changed in CUPS so partly the problem lies in cups sources.

The fact that USR is running it on a non-standard port points to USR
not wanting to support IPP yet...

They support it. From the user point of view, printserver works 100% correctly (windows, cups 1.1.x). I know, that in fact maybe USR has implemented IPP not properly, but since it is possible to talk to this printserver I (and many other users) would like to use it.

There is no point of improving CUPS if it would support less hardware than previous versions, isn't it?

The bug report I quoted mentioned only two people (including me) so it is hard to tell if it is only this model problem.

Anyway, I would like to help, but I cannot send you my router :-)

@michaelrsweet
Copy link
Collaborator Author

michaelrsweet commented Jan 9, 2007

CUPS.org User: mike

Regarding the 1.1.x -> 1.2 changes, CUPS 1.1.x did not conforming to the HTTP 1.1 spec 100%, while 1.2 does. That conformance is probably tweaking a bug in the USR implementation, and we will not break CUPS to work around a vendor bug!

We can't even begin working on diagnosing the problem without a device to test in-house, sorry...

@michaelrsweet michaelrsweet added priority-low wontfix This will not be worked on labels Mar 17, 2016
@michaelrsweet michaelrsweet added this to the Stable milestone Mar 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-low wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant