Recently, I switched from an HP to an Epson printer, as the former had died. Everything used to work fine with the HP printer and always did from the first attempt.
When I installed the Espon drivers initially, the printer would not output anything. So, I uninstalled the Epson drivers and the HP ones and reinstalled the Epson ones
again. The ‘Print Single Page Test’ worked when configuring the new printer and I have printed several documents since. Most came out fine, colors and all, until that
I discovered that Chromium prints tons of pages full of garbage even when printing a single-page document! Now, strangely, it prints to PDF file and those come out
looking good but anytime I print directly from Chromium, its just garbage. Pages after pages come out with light grey dots and some characters.
Went through the exercise again of uninstalling and reinstalling everything. Deleted the cups config and reinstalled that too and the same result is happening. Prints
come out good from the PDF viewer and Geeqie (the two apps tried) but Chromium still is not working. The only strange thing is that when printing from Chromium,
the printer appears twice, once with the model name and once with the series name but neither work.
OpenSUSE 15.1 on my machine was up to date just a week or two ago and Chromium is a very recent version too. There are no errors when printing but the output
is junk, so I don’t even know how to begin diagnosing this. Any suggestions how to drill down into the issue?
The Espon drivers were downloaded from the Epson site and are built purposefully for OpenSUSE 15.1 64-bit, just like my system.
Although you’ve posted this to the hardware forum, this is not hardware related, and very likely a chromium-specific issue (based on results shown from a quick online search). I’m not surprised to read that printing to PDF works, and subsequent printing also works. Try printing the same content from another browser.
Strange because there was no problem with the HP printer but the Espon is, so seemed like a driver issue to me which I thought hardware would be relevant.
Could it be that Chrome is selecting drivers differently than the OS?
Yes, I guess it could be. I don’t know much about Chromium and what happens under the hood. As I mentioned already, try comparing behaviour against another browser eg firefox.
Although this issue appears to be related to the application itself, you can investigate the CUPS printing workflow, and that might narrow down which filter is having an issue with the Chromium print job.
In general, CUPS logging verbosity can be increased with
sudo cupsctl --debug-logging
Any outstanding print jobs can be cancelled with
cancel -a
You can clear the existing log with
sudo rm -f /var/log/cups/error_log
and it will get recreated when CUPS next starts again.
After sending a print job (eg from Chromium) you can examine the error_log file. Its output can be lengthy, but something like the following might help drill down to understanding the printing workflow, and any errors occurring…
egrep -iA3 "error|filter" /var/log/cups/error_log
Hope that is enough to give an idea about how to proceed with diagnostics. It is likely that a bug report will be needed to help resolve this.
Looks like some really useful info. After reading through though, it seems like a long weekend project rather than a few mins of debugging! I will get back to this another day.
BTW, Firefox printing is working, so it’s most-likely Chromium specific. It’s going be tough because there are no errors in the logs now, just the output is wrong.
BTW, Firefox printing is working, so it’s most-likely Chromium specific.
As I suspected.
It’s going be tough because there are no errors in the logs now, just the output is wrong.
Cheers,
Itai
You could try running the filters by hand as the Fedora wiki page describes. That would help with capturing the print data at each step, and assist with determining where the issue lies. A bug report will be needed.
After a fresh install of LEAP 15.2, Chromium is printing correctly with the same printer.
There’s no free lunch though because the scanner of this all-in-one printer is no longer recognized!
EPSON provides drivers for 15.1 which I tried anyway on 15.2 but aren’t working at all, so there’s
one more thing to debug this weekend.
There’s also no listing for my scanner, the model numbers stop right before… is there a way to manually add the scan-data that’s missing?
Maybe some files/config could be copied from the 15.1 install? I haven’t wiped it yet but I plan to, so please let me know if there is some
files or data to recover from it that would help get things working on 15.2.
With the RPMs provided for 15.1 on 15.1, it shows my scanner on the list: Epson WF-7720 but with the packages from Packman for 15.2
it skips that model. Both WF-7620 and WF-8510/8590 are there but no WF-7720.
lsb-release -id && zypper se -si imagescan
Distributor ID: openSUSE
Description: openSUSE Leap 15.2
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
S | Name | Typ | Version | Arch | Repository
---+------------------------------+-------+----------------------------+--------+--------------
i | imagescan | Paket | 3.63.0-1epson4opensuse15.1 | x86_64 | Programme-rpm
i+ | imagescan-plugin-gt-s650 | Paket | 1.0.2-1epson4opensuse15.1 | x86_64 | Programme-rpm
i+ | imagescan-plugin-networkscan | Paket | 1.1.3-1epson4opensuse15.1 | x86_64 | Programme-rpm
I made a directory for downloaded rpms and insert this local directory as a repo in Yast/zypper.
So all downloaded rpm are copied to that directory and can be installed with
That’s exactly what didn’t work… that’s what I meant when saying that I tried the packages provided for 15.1
They do install and I see them in Yast but it keeps saying scanner not detected. I even tried selecting similar models but again, it never sees the scanner.
Launching imagescan immediately closes itself with an error saying there are no scanners.
This is only thing not working yet on my 15.2 install… so everything is working just right. Overall, that’s pretty good, specially the the scanner can also work standalone
directly to a memory key.
Has nothing to do with your problem (i think but who knows), but videolan and packman Repo at same tiime is mostly not a good choice.
So I would delete the videolan repo and set the packman repo to a higher priority as the others. After that I would dup to packman.
So scanner is working?
should work is supported by sane-backends:
WF-7620 Series USB 0x04b8/0x08b9 Complete network interface supported via DFSG non-free iscan-network-nt package
all-in-one
overseas version of the PX-M5041F epson2
(1.0.124 (unmaintained)) sane-epson2
