On 01/04/2021 07.58, Simon Becherer wrote:
Sending the log files to the list would make this much shorter and save you a lot of time.
Absolutely. Instead of going in a wild chase reinstalling things that doesn't solve anything, wastes time and causes distress, the log tells precisely what is wrong.
Am 01.04.21 um 04:49 schrieb Doug McGarrett:
D [31/Mar/2021:19:53:44 -0400] [Job 370] pdftops: error while loading shared libraries: libpoppler.so.106: cannot open shared object file: No such file or directory D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5805 (pdftops) stopped with status 127! D [31/Mar/2021:19:53:44 -0400] [Job 370] The print file is empty. D [31/Mar/2021:19:53:44 -0400] [Job 370] PID 5806 (pstops) stopped with status 1!
this is your (ore one of your problems)
"the print file is empty" -> you send data to the printer, BUT the data file is empty.
check where you lost the libpoppler.so.106 file install it. (open yast, search for poppler and maybe force installation of the already installed package, first check if the file is somewhere inside) - sorry i do not know the commandline rpm or zypper command for this -
No, that is not that easy, they can only tell that information if the package is already installed. Unfortunate. BUT, we can look it up for him in our systems. first, "locate libpoppler.so", which on leap says /usr/lib64/libpoppler.so.89 and other hits. Then the command rpm -qf /usr/lib64/libpoppler.so.89 tells the rpm: cer@Telcontar:~> wrpm /usr/lib64/libpoppler.so.89 libpoppler89-0.79.0-lp152.2.3.1.x86_64 cer@Telcontar:~> So in this case you can search in yast for "libpoppler" and it will find it. So will zypper. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)