http://bugzilla.novell.com/show_bug.cgi?id=529489
User jsmeix@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=529489#c5
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #5 from Johannes Meixner 2009-08-12 03:38:49 MDT ---
The CUPS error_log in attachment #312032
looks perfectly o.k., in particular the processing
filters and the backend worked without errors:
-----------------------------------------------------------------------------
Started filter /usr/lib64/cups/filter/pstops (PID 28183)
Started filter /usr/lib64/cups/filter/brlpdwrapperHL5370DW (PID 28184)
Started backend /usr/lib64/cups/backend/usb (PID 28187)
..
PID 28183 (/usr/lib64/cups/filter/pstops) exited with no errors.
..
PID 28184 (/usr/lib64/cups/filter/brlpdwrapperHL5370DW) exited with no errors.
PID 28187 (/usr/lib64/cups/backend/usb) exited with no errors.
..
Completed successfully.
------------------------------------------------------------------------------
I.e. from the printing system's point of view
the job was processed correctly.
Therefore I cannot find out why it is not printed by your
particular printer (we do not have printers like yours
so that we cannot reproduce it).
Furthermore I don't know how to debug the third-party driver
/usr/lib64/cups/filter/brlpdwrapperHL5370DW
from Brother (I have no idea what this program actually does)
so that I cannot help you to find out why exactly it fails.
I can only guess that something in brlpdwrapperHL5370DW
or in whatever sub-process which is launched by it fails
but I don't know how to get debug messages from
brlpdwrapperHL5370DW.
But if something related to brlpdwrapperHL5370DW fails,
it should not exit with no errors and at least report
via stderr an appropriate error message which appears
in the CUPS error_log so that one has a chance for further
debugging. If something in Brother's driver fails but it
does not report an error, then at least this is a bug
in their driver because it makes it impossible for others
to find out why their driver fails - but it seems Brother
may be not interested that others find out what their driver
actually does...
Therefore all you can do is to contact Brother
for further help and debugging.
I can only close the bug as "wontfix" which means in this
case "cantfix".
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
