After Update to Mac OS 10.13 High Sierra - Printer M553dn undefinedresult xshow message

[AndreasOxen]

For me with a M553, HP AirPrint works all of the time. 

USB-printing works erratically with USB (driver v19.13), but fails most of the times (xshow error).

USB-printing works always with a small Canon printer.

I doubt this is a font issue. I suspect instead APFS, as some other apps like TextWrangler sometimes seems to be confused with their temporary files when saving.

[rstooth]

Can't wait for this to get fixed...my HP M553X is basically unusable half the time due to this issue.

[dmolony]

Same here, latest printer drivers, latest OS, reset printers and reinstalled.

It happens with some excel spreadsheets (but not all), and it happens when printing a bank statement in Safari.

So not exclusively Microsoft.

[Greg_Reid]

Did the 10.13.3 update, released this week, help with any of the printing issues? 

I have to order printers for my company and if this latest release doesn't fix it, I'll need to look brands other than HP. I have too many unhappy Mac users right now who can't print a simple spreadsheet.

It's unbelivable that HP and Apple can't manage to fix what they broke.

Thanks!

[IgorA]

The 10.13.3 update has made no difference.

[--Hotti--]

10.3.3 did not help

[Greg_Reid]

Thank you for that. I'll have to find another printer brand to purchase for our new printers, I guess.

I'd call HP but that sounds like a fruitless endeavour based on others' comments in this forum; I did call Apple and created a formal help desk case back in October, soon after 10.13 was released, about the issue, but they haven't done anything, either.

I guess the net/net is that HP laser jet printers are no longer Mac compatible.

Good luck everyone.

[IronBadger]

A little update for everyone:

[Content Removed]

New firmware is still on track for the end of January for FutureSmart 4 and February for FutureSmart 3 so that printers handle the error more gracefully.

Edited for legal reasons.  Ugh.

[steve_maser]

I can't legally say that I'm testing the 10.13.4 beta, so I can't say I still have a document showing this problem when I try printing it to an M605 and/or M603.

So maybe 10.13.4 is not the answer here?

(To clarify the double negatives -- 10.13.4 is NOT fixing this on files we have that show this issue...)

[luz42]

[Content Removed]

Almost sounds too good to be true - but I really hope it is!

Because even if the problem can also be fixed or worked around in firmware, I doubt if there would have been such a fix for my stone age HP LJ 1320.

Fixing the root cause really sounds like a solution, and not an ugly workaround 😉