some installed rpms: cndrvcups-common-1.90-1.i386 cndrvcups-ufr2-uk-1.90-1.i386 cups-1.4.6-6.1.i586 cups-client-1.4.6-6.1.i586 cups-libs-1.4.6-6.1.i586 kde4-printer-applet-4.6.0-3.4.i586 python-cups-1.9.52-4.1.i586 python-cupshelpers-1.2.5-4.1.i586 yast2-printer-2.20.8-2.1.i586 In /etc/papersize and everwhere else I can find I have letter selected as default papersize, and have no other size paper I can use. I have a Canon MF4370dn IP attached printer that works OK usually with my 11.2 using the Canon supplied PPD driver RPM from Canon's UK web site. At the time I bought it a year ago it was the only MF printer I could find that claimed Linux support on the box, but it turned out Canon will not provide support or drivers to owners of this model who live in North America. Today I tried to set it up on an 11.4 system. On first try, YaST2 failed to find any printers, so I tried again and decided I had 2 the same. I deleted them and started over, ending up with only one. YaST2 can print a test page just fine. Trying to print with Konq or Firefox or Gwenview results in the printer reporting unspecified data errors and printing nothing, and a printer queue that resists attempts to delete the botched jobs from it. The document print status applet reports each such job's status as "processing". After cancelling a job the cancelled job seems to want to display in the applet in perpetuity. What I log out of KDE and back in, the previous botched job shows as processing in the printer applet unless I've cancelled it. Is there a way to ensure jobs in process at log out time, done in an attempt to escape from a deranged printer, are not revived when logging back in? Cycling the printer's power, with 5 minutes or more of off time, after clearing the botched jobs, doesn't seem to help either. Attempts to clear bad jobs using the CUPS web page in Konq don't do any better, and require a password to admin the printer even though there are no ordinary users configured on the system. I have to goto /var/cache/cups and delete job.cache before the printer will ever light up again, but this doesn't always work, since /var/spool/cups/* causes job.cache magically reappear whenever it feels like it unless I rccups stop and/or delete /var/spool/cups/*. Rebooting also causes the printer to beep and report data error, and the /var/cache/cups/job.cache file I deleted to be restored, every time I reboot, unless I delete the printer in YaST2 first, or /var/spool/cups/*. O_O Repeating the whole process, deleting the printer, rebooting, configuring a new printer, always produces the same results. Deleting /var/spool/cups/* helps. Apparently selecting to cancel a job in the KDE printer applet doesn't delete anything from /var/spool/cups/. Knowing that is still no help to figure out why YaST2 can print a test page but nothing else I try can print anything. I've had similar trouble getting 11.2 to print in the past, but have no recollection how I got past it. :-( Cups logs: http://fm.no-ip.com/Tmp/Linux/cups114-access_log-big31.txt http://fm.no-ip.com/Tmp/Linux/cups114-error_log-big31.txt Nothing I see /var/log seems related. Can anyone help? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org