Hi, Being compulsively hopefull I just burned another 2+ hours on this trying different variations and even trying to install the cups and lpr drivers from the Brother-USA web site. Here's a description of situation as best I can tell. There are TWO separate problems.
#1 is related to BR-Script3 driver. That is the ERROR NAME / COMMAND / OPERAND STACK type error I originally reported on 09Dec2008 and confirmed existed still in 9.10 on 14Feb2010. Specifically, fails to print correct output on first attempt with this ERROR NAME / COMMAND / OPERAND STACK error on the printed page, followed by success on next print job. Blow a lot of extra paper if a user is doing only a couple prints per session. #2 is related to the CUPS driver in the Laser1 package. When set to print on US letter size paper, it shifts the printed image down and to the right by at least 5/8 inch down and 1/4 right. It not only looks messed up printing but if one is printing with small margins, content is lost off the edge of the page (like the Ubuntu print test image looses much of the border rings on the bottom and right side). Today I selected A4 as the output paper and the margins appeared to be correct on the top and left sides. Of course, being in the USA, using A4 paper isn't a real solution since everything is setup for US letter size paper. So I tried Mr Lui's idea again and find that the CUPS driver for the MFC-8840D still has messed up output placement on the printed page (as seen with 8.10 on 04Jan2009). After allowing Update Manager to update the CUPS-related files from the initial install, I have also lost the ability to print using the Foomatic/Postscript driver. Now it throws ERROR NAME / COMMAND / OPERAND STACK errors on all print attempts instead of successfully printing every time as it does from live CD or did from the initial install before Update Manager 'updated it'. This is a show stopper for my use of the OS. -- Brother MFC8840D errors on 1st print job https://bugs.launchpad.net/bugs/306401 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
