Phaser 8560DN reports "Ink/toner empty," "Ink/toner waste bin full" erroneou

[Detlef]

We haven't seen a case where this doesnt fix the issue. In that case, I'd recommend running the 10.6.8 Combo Updater from apple.com to ensure everything is properly re-written.

Done that again

The driver I installed the last time was:

File Download: Driver Installer Package for Mac 10.6
Filename Phaser8560_EN.dmg
Date Aug 28, 2009
Size 11.6 MB
Apple Installer Package for the Phaser 8560 supporting Mac 10.6.

Now I used:

File Download: Print Driver Installer for Mac 10-5 - 10.7

    Filename Xerox_Mac10.7_Print_Drivers_2.0.9.dmg
    Version 2.0.9
    Date Aug 19, 2011
    Size 109.4 MB

Apple Installer Package supporting 10.5, 10.6 and 10.7. Includes Xerox printer discovery and print queue creation for quick setup and use.

(By the way, the download pages don't work for me in Firefox 8, they work fine in Safary)

Now, this worked! :smileyhappy:

I think, the older 10.6 driver should be removed, in order to avoid this mix-up

[MicahS-Xerox · Accepted solution]

We haven't seen a case where this doesnt fix the issue. In that case, I'd recommend running the 10.6.8 Combo Updater from apple.com to ensure everything is properly re-written. 

To date, 100% of the callers we've had in our centre have had the issue fixed by re-running the Patch found here so this would be the first I've seen of this.

If that specific patch does not work, We'd need more information from your specific Mac to see what we could do.

[Detlef]

A recommended solution would be to roll your cups packages back to a 1.4.6 or earlier state. The Mac OS Package we recommend on xerox.com does this,

Ok, so I went to Xerox.com, downloaded the reccommended Driver Setup for 8560 and 10.6, reinstalled - and...... No change! :smileylol:

[tobyfoote]

I've been anxiously awaiting this fix. It's bothersome having the yellow exclamation mark jump up and down in the Mac Dock when printing. I've installed the version 2.0.9 Mac drivers (as well as the version 2.0.8 drivers prior) and this is still an issue.

[MicahS-Xerox]

I hope to shed some light on this.

The root problem happened when Apple took over the CUPS project several years back. So while you might be running a Linux based OS, we can still have "an Apple Problem." The problem exists with CUPS interpretation of MIB values that machines send back to indicate things such as toner levels and paper tray status. The new versions of CUPS 1.4.7 and 1.5 have these issues.

A recommended solution would be to roll your cups packages back to a 1.4.6 or earlier state. The Mac OS Package we recommend on xerox.com does this, and you can find the binaries on cups.org under "Older Versions"

Please let me know if you have further issues.

[chelmite]

I now have the following rpms installed and am still getting the erroneous error messages:

bluez-cups-4.96-3.fc16.x86_64
cups-1.5.0-22.fc16.x86_64
cups-libs-1.5.0-22.fc16.i686
cups-libs-1.5.0-22.fc16.x86_64
cups-pk-helper-0.1.3-3.fc16.x86_64
ghostscript-cups-9.04-7.fc16.x86_64
gutenprint-cups-5.2.7-7.fc16.x86_64
python-cups-1.9.60-1.fc16.x86_64

[c-x]

By the way, nothing changed on my end from when it happily printed to when it started complaining. I haven't upgraded during that time and there have been very few OS updates.

[c-x]

I'm on Fedora 14, and getting the same problem for the last couple months.  The first few times it would still let me print, but now it's stopped letting me print at all.

[chelmite]

I'm seeing the problem in Fedora 15, so an update to Apple OS won't fix the problem. I have the following rpms installed:

bluez-cups-4.87-7.fc15.x86_64
cups-1.4.8-5.fc15.x86_64
cups-libs-1.4.8-5.fc15.i686
cups-libs-1.4.8-5.fc15.x86_64
cups-pk-helper-0.1.3-2.fc15.x86_64
ghostscript-cups-9.04-3.fc15.x86_64
gutenprint-cups-5.2.7-3.fc15.x86_64
libgnomecups-0.2.3-9.fc15.x86_64
python-cups-1.9.57-1.fc15.x86_64

[TimD-USX13774-xrx]

Hi Fabio,

Sorry for the delay in response.  There is no SPAR for this as it is not a Xerox issue.  The Apple Bug ID# for this is 7265420.  Our engineers are working with Apple to get the issue resolved but the fix will have to come from Apple.  

Thank you,

Tim