From my non-expert point of view and as far as I understand
https://bugzilla.novell.com/show_bug.cgi?id=688614
https://bugzilla.novell.com/show_bug.cgi?id=688614#c28
--- Comment #28 from Johannes Meixner 2011-04-29 13:44:37 UTC ---
FYI:
prnt/hpijs/hpijs.cpp in the HPLIP sources (long lines wrapped here)
----------------------------------------------------------------------------
pSS->pPC = new PrintContext (pSS, 0, 0);
/* Ignore JOB_CANCELED. This a bi-di hack that allows
the job to continue even if bi-di communication failed. */
if (pSS->pPC->constructor_error > 0
&& pSS->DisplayStatus != DISPLAY_PRINTING_CANCELED)
{
BUG("unable to open PrintContext object err=%d\n",
pSS->pPC->constructor_error);
goto BUGOUT;
}
----------------------------------------------------------------------------
it seems it is an issue with bidirectional communication.
Compare
https://bugzilla.novell.com/show_bug.cgi?id=462048#c23
If it is really an issue with bidirectional communication
it is a bug in HPLIP because HPIJS should not abort but
fall back to unidirectional communication if bidirectional
communication is not possible and if the printer also
works with unidirectional communication (some printers
do not work with unidirectional communication but then
the "socket" backend would also not work), see
http://hplipopensource.com/node/128
The generic CUPS backend "socket" does basically
unidirectional communication (i.e. it only sends
the data to port 9100 at the network printer)
similar as the "backend for a network printer" at
http://en.opensuse.org/SDB:Using_Your_Own_Backends_to_Print_with_CUPS
From my corrent point of view it seems HPLIP/HPIJS is still
not sufficiently robust if bidirectional communication fails.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.