This appears to still be a problem in version 5.7.2(2221). I have modified my PPD as described and that does fix the issue. However I have reports of users on 10.15.7 getting intermittent freezing occasionally when they are in the print dialog box. (We do use the Accounting system and have it pop-up asking for the account code). Is anyone else having this issue? Could it be related to modifying the PPD? I see there is some sort of checksum line in there somewhere but I'm not an expert on the ins and outs.
And, um, do we think Xerox is going to fix this in their driver? How do we help inspire and hasten that change?
Oh, I should probably add I'm using the Xerox C70 PPD which had this same problem with the tray selection.
Hi,
This was really frustrating with my MBP, OSX 10.15.6 (now), and my ColorQube 8580DN, because I was trying to fix this with multiple variations of deleting and then reinstalling the printer driver.
However, after reading MRCAnalyst's workaround post in this thread, I located the gzipped PPD file in /Library/Printers/PPDs/Contents/Resources for my printer, filename "Xerox ColorQube 8580DN.gz", and then double clicked it, which unzipped it to my Downloads folder. Opening it with TextEdit, I then located the line with;
*DefaultInputSlot:
(line 813), and then edited it to read;
*DefaultInputSlot: automatic
I also edited the following line;
(Line 13) *NickName: "Xerox ColorQube 8580DN-2, 5.6.0"
adding the -2 to the description name so I can find it in the Printer list. Then I saved it with the filename of "Xerox ColorQube 8580DN-2", and moved the file to the /Library/Printers/PPDs/Contents/Resources folder.
Then I just added a new printer to my system, selected the entry for Xerox ColorQube 8580DN-2, and after installing, it will now finally, print from the installed tray correctly.
printereasy routermanuals techtipseasy
Thanks again all.
Great news Andrew! Thanks for testing!
Tim
YES! it looks like this issues is finally resolved. I put it on 6 Catalina and 1 Mojave MACs today and all them worked flawlessly. I tested it by putting 11X17 paper in tray 1 and each MAC by printing on to letter size paper multiple times. Each print job came out without asking for the paper to be put in to tray 1. So we can call this one closed!
Andrew
I just noticed version 5.7.2(2221) came out today. Unfortunately we are not allowed in the office (covid). So if anyone is able to test this version for the issue mentioned above and give their results that would be great!
I con't see a changelog or list of bugfixes of the driver version, or am I looking in the wrong place?
https://www.support.xerox.com/en-us/product/workcentre-7800-series/content/149515
Thanks in advance!
Tim
Hi Andrew,
I have not had any issues to date utilizing the workaround that I provided. I have mostly moved on from this issue after making my voice heard as much as possible within Xerox, but I still assist coworkers from time to time remotely with this. Are you trying to install the printer through System Preferences with a custom .ppd file? That used to work in macOS but no longer does. If you want to use a .ppd format file for a custom install then you have to do it through CUPS. Otherwise we need to put the edited .ppd back into a .gz file, copy it to the library, and then we can install the printer through System Preferences. That's the method that I exhibted in my video that I shared in one of my earlier responses to this forum topic.
Have you had any success editing the ppd? I tried it two weeks ago and I got a message like "illegal ppd" when I tried to use the edited ppd. I am not sure what level the MACos was at though.
Andrew
We're having the same issues, but with a Xerox 8580 Color Qube. Changing the paper tray selections in the print dialogue doxes does nothing, as the driver sets the selection back to Tray 1 (MPT) immediately after you click "print". We're running the V5.6.0 driver.
Editing the ppd file for the printer did not solve the problem.
I'm hoping for a better long-term fix from Xerox soon as editing .ppd files manually isn't a long term fix.
Does anyone know if this problem is fixed in latest update of macOS Catalina 10.15.7 ?