Re: KDE printer interface problem
Michael,
Thanks for this reply. I must have missed it in the normal deluge(*)
of e-mails from the kde-user list. In the meantime, a hard copy of the
document I needed to print turned up and then I got distracted
until now.
On Sat, 10 Jul 2004 03:25 pm, Silvan wrote:
<snip/>
> > How do I diagnose this problem?
>
> I'd start at CUPS and work back. http://localhost:631/printers
>
> Try printing a test page.
>
> You may need to purge old jobs left over from aborted attempts to get
> things going. I'm not sure if that will be necessary in your case or not.
> I've had a lot of trouble out of a POS USB winprinter, and when it (the
> proprietary, closed source, binaries only POS driver) dies, it will never
> pick up the old jobs in the queue after I restart everything, and it just
> sits there until I go in and clean up the queue by hand and start over.
<snip/>
Firstly, I think I have solved my problem. I remove files named
/var/spool/cups/c00001, .../c00002, ... .../c00005*. These
seemed to correlate with the records shown on the screen
http://localhost:631/jobs?which_jobs=completed :
ID Name User Size State Control
BJC-1000-1 sinnamon.doc sinnamon 402k aborted
BJC-1000-2 sinnamon sinnamon 402k aborted
BJC-1000-3 sinnamon.doc sinnamon 402k aborted
BJC-1000-4 file:/ sinnamon 148k aborted
BJC-1000-5 Test Page root 15k aborted
(I also deleted files in /var/spool/lpd/lp/ but that seemed to have
little bearing on the problem.)
I found I could print the test page, and a page of a MS Word
(ughhh!) document with Open Office.
I then found additional entries on
http://localhost:631/jobs?which_jobs=completed:
ID Name User Size State Control
...
BJC-1000-6 Test Page root 15k completed at Fri 16 Jul ...
BJC-1000-7 sinnamon.doc sinnamon 16k completed at Fri 16 Jul ...
... and two files in /var/spool/cups: c00006 and c00007.
Somehow, refreshing the screen does not cause the entries for
the previously aborted jobs (BJC-1000-1 ... BJC-1000-5) to go,
so it is a mystery to me as to where the displayed data
originates from.
Also the screen doesn't tell me why the job 'aborted' (should
trawl through /var/spool/cups/* I guess) or how to purge
the records for the aborted jobs.
Anyhow, it looks like my immediate problem is fixed, so
I guess I can get by without really understanding what is
going on.
Thanks again for the help.
regards,
James
(*) I am probably a contributor to this deluge so I
will try to show a little more restraint in future, myself.
--
James Sinnamon
frodo000@bigpond net au
+61 412 319669, +61 2 95692123
Reply to: