https://bugzilla.novell.com/show_bug.cgi?id=688614
https://bugzilla.novell.com/show_bug.cgi?id=688614#c19
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
InfoProvider| |ralf@kruedewagen.de
Summary|hplip: the "hp" backend for |hpijs fails with "unable to
|a HP network printer lets |open PrintContext object
|it print "Unable to open |err=2" for the "hp" backend
|initial device, quitting" |for a HP network printer
|(it works with the |(it works with the "socket"
|"socket" backend) |backend)
--- Comment #19 from Johannes Meixner 2011-04-29 08:37:46 UTC ---
Ralf Krüdewagen,
very many thanks for your complete and exact logs!
Without logs of such quality there would be nothing
what I could do here but now there can be progress:
Both attachment #427211
(cups error log when printing test page with HPLIP tool)
and attachment #427212
(cups error log when printing from kwrite)
and your comment #15
show the actual piece of software which fails via:
prnt/hpijs/hpijs.cpp 638: unable to open PrintContext object err=2
It is the hpijs driver which fails
and as a consequence Ghostscript which had called
the hpijs driver also fails and Ghostscript outputs
on stderr: Can't start ijs server "hpijs"
and on stdout: Unable to open the initial device, quitting.
Currently I have no idea what the root cause could be
which lets the hpijs driver fail in this case.
I searched in Google for
"unable to open PrintContext object err=2"
and got an old bug report from Jan 2008
https://bugs.launchpad.net/hplip/+bug/182658
(start to read at "#4" therein)
which ends with "Fixed in hplip 2.8.2."
and
a newer user question
https://answers.launchpad.net/hplip/+question/99661
which shows an interesting possible reason
because therein I found (near the end):
-------------------------------------------------------------
kovach said on 2010-04-27:
YES, still having a problem to run the HP P1006 on RHE 5.0.
-------------------------------------------------------------
Naga Samrat Chowdary, Narla said on 2010-05-14:
Please try by setting following settings.
System -> SELinux Management
Set "System Default Enforcing Mode" and
"Current Enforcing Mode" to Permissive.
and try printing.
-------------------------------------------------------------
kovach said on 2010-05-14:
That did the trick!
-------------------------------------------------------------
Ralf Krüdewagen,
do you have any kind of special security software active
like AppArmor, SELinux, Firewall, whatever else?
E.g. see
Bug #539401 (AppArmor lets cupsd fail to start)
Bug #474403 (AppArmor makes CUPS irresponsive)
Have in mind that the filters and the CUPS backend
are run by default as the user "lp" so that this
user must have sufficient permissions e.g. to run
subsequent filter programs and/or to communicate
with the printer device via USB or network.
FYI, some background information:
All stderr output of all filters is redirected to the cupsd
which writes it into /var/log/cups/error_log if
"LogLevel debug" is set in /etc/cups/cupsd.conf
so that both the hpijs stderr output
prnt/hpijs/hpijs.cpp 638: unable to open PrintContext object err=2
and the Ghostscript stderr output
Can't start ijs server "hpijs"
appear in /var/log/cups/error_log
Now it depends on how exactly Ghostscript was called
by which kind of foomatic-rip filter (either foomatic-rip
or foomatic-rip-hplip) whether or not Ghostscript's stdout output
Unable to open the initial device, quitting.
is discarded or sent as if it was usual filter output
to the CUPS backend which sends it to the printer device.
--
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.