I wasn't sure that the HP1020 LaserJet 1020 was supported by the foo2zjs driver, but it is listed as supported as shown here. So, it's probably worth a shot.

Here's an Ubuntu guide, which offers clear instructions with installing the foo2zjs driver precisely for this model.

A Mint guide using essentially the same commands. (Make sure to load the firmware for you model though.)

Once the driver is installed, you can configure using system-config-printer, or a browser (CUPS web interface).

http://foo2zjs.rkkda.com/cups/hp1020.html

I've had problems with trying to use HPLIP for HP 1020, but this http://foo2zjs.rkkda.com/ has always worked on Centos v5 & v6.

Thanks, but what is (or are) Centos v5 and v6?

I've already provided the link to the foo2zj driver. (Refer first URL of post #31).

Follow the instructions in the Ubuntu guide and you won't go wrong. CentOS is another Linux distro (and based on the source code of Red Hat Enterprise Linux).

I was about to sent a euphoric message - the routine in the Ubuntu guide went perfectly smoothly, all the way down to the last message testing the installation - this was the output -

tail /var/log/syslog
Apr 13 10:47:19 alok-desktop foo2zjs-wrapper: foo2zjs-wrapper -z1 -P -L0 -r1200x600 -p9 -T3 -m1 -s7 -n1
Apr 13 10:47:20 alok-desktop foo2zjs-wrapper: gs -sPAPERSIZE=a4 -g9920x7016 -r1200x600 -sDEVICE=pbmraw -dCOLORSCREEN -dMaxBitmap=500000000
Apr 13 10:47:20 alok-desktop foo2zjs-wrapper: foo2zjs -r1200x600 -g9920x7016 -p9 -m1 -n1 -d1 -s7 -z1 -u 192x96 -l 192x96 -L 0 -T3 -P
Apr 13 10:47:43 alok-desktop dbus[510]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' (using servicehelper)
Apr 13 10:47:43 alok-desktop dbus[510]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism'
Apr 13 10:48:16 alok-desktop foo2zjs-wrapper: foo2zjs-wrapper -z1 -P -L0 -r1200x600 -p9 -T3 -m1 -s7 -n1
Apr 13 10:48:17 alok-desktop foo2zjs-wrapper: gs -sPAPERSIZE=a4 -g9920x7016 -r1200x600 -sDEVICE=pbmraw -dCOLORSCREEN -dMaxBitmap=500000000
Apr 13 10:48:17 alok-desktop foo2zjs-wrapper: foo2zjs -r1200x600 -g9920x7016 -p9 -m1 -n1 -d1 -s7 -z1 -u 192x96 -l 192x96 -L 0 -T3 -P
Apr 13 10:48:48 alok-desktop dbus[510]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' (using servicehelper)
Apr 13 10:48:48 alok-desktop dbus[510]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism'

All of which looked fine, and even managed to print a test page successfully. After that, I power-cycled the PC and the printer, but when I tried printing again, it was back to the old "Processing" - the printer that didn't go beyond processing.

Am feeling quite disheartened now. Any ideas?

And thank you all for being so patient.

Still persisting. Ran the var/log/syslog command again, and identified something different this time. Here is the output -

tail /var/log/syslog
Apr 13 10:47:20 alok-desktop foo2zjs-wrapper: gs -sPAPERSIZE=a4 -g9920x7016 -r1200x600 -sDEVICE=pbmraw -dCOLORSCREEN -dMaxBitmap=500000000
Apr 13 10:47:20 alok-desktop foo2zjs-wrapper: foo2zjs -r1200x600 -g9920x7016 -p9 -m1 -n1 -d1 -s7 -z1 -u 192x96 -l 192x96 -L 0 -T3 -P
Apr 13 10:47:43 alok-desktop dbus[510]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' (using servicehelper)
Apr 13 10:47:43 alok-desktop dbus[510]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism'
Apr 13 10:48:16 alok-desktop foo2zjs-wrapper: foo2zjs-wrapper -z1 -P -L0 -r1200x600 -p9 -T3 -m1 -s7 -n1
Apr 13 10:48:17 alok-desktop foo2zjs-wrapper: gs -sPAPERSIZE=a4 -g9920x7016 -r1200x600 -sDEVICE=pbmraw -dCOLORSCREEN -dMaxBitmap=500000000
Apr 13 10:48:17 alok-desktop foo2zjs-wrapper: foo2zjs -r1200x600 -g9920x7016 -p9 -m1 -n1 -d1 -s7 -z1 -u 192x96 -l 192x96 -L 0 -T3 -P
Apr 13 10:48:48 alok-desktop dbus[510]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' (using servicehelper)
Apr 13 10:48:48 alok-desktop dbus[510]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism'
Apr 13 10:51:22 alok-desktop kernel: [ 465.625480] perf interrupt took too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 50000

*

The last line is missing from the previous output. Significant?

That last line is not related to CUPS processing. That's one of the problems with examining syslog output. Use CUPS page_log and error_log instead.

You managed to print a test page successfully, so that's good. Now, we need to know where the processing fails, and that can be complicated. This DebuggingPrintingProblems guide is your friend here. Learning and patience is required to locate the cause of the problem.

But first, what kind of file were you trying to print? Application? That may be impacting here.

Meanwhile, I power-cycled some more, and switched the USB slot, and the lsusb managed to detect a printer, and I managed to print a test successfully. So, I'm delighted - but still confused! And afraid that the printer might decide to go whimsical on me again.

However, what could be the significance of that last line?

Also, if I wanted to run CUPS page_log and error_log - what would the command in Terminal look like?

I printed just a few letters - ;lihf;asd - that sort of thing - from LibreOffice Writer.

Truth to tell, I am also rather enjoying having shed the passivity of the Windows world, and actually becoming involved in what the computer is doing - takes me back to the earlier DOS, pre-Windows days when I got my first PC - which probably tells you that I am rather more ancient than the usual Linux user. Certainly, the few people I can call on for advice here are a little surprised that someone like me should be trying to get the hang of this kind of thing! (Pls forgive the autobiographical aside, but I thought you might be interested to know a little more about this chap who is seeking your help so persistently!)

I will certainly give the DebuggingPrintingProblems guide a shot. Thanks.

Okay, so to cancel all pending/failed jobs do
then print a PDF with the lpr command using something like
eg I might do this to print a file /home/dean/example.pdf
You'd be surprised about the age range of members here. (I'm a moderator at openSUSE forums, and there are a number of senior members there who are retired users, some with work histories using computers since mainframe days!)

Yes, it's worth the investment. Essentially looking under the hood...like taking an engine apart. If you get stuck, I'll do my best to help.

Thanks a ton!

Just managed to print a PDF successfully!

Problem solved,I think!

I'm glad that you managed to print a PDF successfully, but don't be too quick to say its solved. CUPS uses (and now expects) the incoming file to be in PDF format as part of the workflow.

https://lwn.net/Articles/485617/

Hopefully, it is just LO that has the printing issue, but it will take further investigation on your part.

Successfully printed more nonsense off LibreOffice!

O the sense of triumph!

Just to answer one of your questions I missed before (in case it helps others)
You could open the error_log file with an editor eg using nano
or to watch the tail of the file live, open a terminal window and do
then proceed to print while observing the output.