The current Edgy should not suffer this problem (or perhaps for some Toshiba printers). Do (copy and paste the commands with your mouse):
cd /usr/share/foomatic for f in db/source/*/*.xml; do cat $f | perl -e '$a = join("", <>); ($a =~ /\r/ ? exit 0 : exit 1)' && echo $f; done I get only db/source/printer/Toshiba-e-Studio_520.xml db/source/printer/Toshiba-e-Studio_600.xml db/source/printer/Toshiba-e-Studio_720.xml db/source/printer/Toshiba-e-Studio_850.xml Older versions of Foomatic had a lot more ^m characters. Especially the XML file for your printer (Epson Stylus Photo 750) is fixed in current Edgy, perhaps even in the final Dapper. In addition, in Edgy this printer is supported by Gutenprint via a ready-made PPD, so Foomatic will not need to generate a PPD. So for everyone who has not one of the 4 Toshiba printers listed above this bug is fixed. And as for these Toshiba models Edgy included the ready-made PostScript PPDs provided by Toshibe, the printer setup tools will most probably not break on these. Every program parsing XML should not break on these Toshiba XML files, as xmllint --noout /usr/share/foomatic/db/source/printer/Toshiba*.xml does not show any error. ** Changed in: foomatic-db (Ubuntu) Status: Needs Info => Fix Released -- xml foomatic files containing ^M https://launchpad.net/bugs/40224 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs