On 02/04/2021 01.04, Doug McGarrett wrote:
On 4/1/21 7:34 PM, Carlos E. R. wrote:
On 02/04/2021 00.06, DennisG wrote:
On 4/1/21 1:40 PM, Doug McGarrett wrote:
On 4/1/21 2:39 PM, Carlos E. R. wrote:
On 01/04/2021 19.20, Doug McGarrett wrote:
On 4/1/21 5:15 AM, Carlos E.R. wrote: > > rpm -qf /usr/lib64/libpoppler.so.89
doug@linux1:~> rpm -qf /usr/lib64/libpoppler.so.89 error: file /usr/lib64/libpoppler.so.89: No such file or directory doug@linux1:~>
Obviously. It works on my machine, we know it will not work on yours.
linux1:~ # zypper install libpoppler.so.89
And you know this is the wrong command.
Sigh...
Man... just do "zypper install libpoppler"
just that.
doug@linux1:~> su - Password: linux1:~ # zypper install libpoppler Loading repository data... Reading installed packages... 'libpoppler' not found in package names. Trying capabilities. No provider of 'libpoppler' found. Resolving package dependencies... Nothing to do.
libpoppler108 is the current TW version:
Unfortunately, libpoppler doesn't follow the name-version.minor.release naming convention. Instead apparently it uses nameversion-minor.release, which made the command to fail.
And probably some dependency is broken, because it should have been installed automatically before that, not requiring a manual installation. Went to the 'net and reinstalled the file via their automatic install function. Still doesn't print.
WHY? WHY on EARTH are you reinstalling things! :-/// DON'T EVER GO TO NET! Oh god... :-/ JUST POST THE LOG! Ok, here is the log. This is the ONLY thing you had to do. We asked you to post the log, nothing else. Just post the log, and wait. Now we have to figure out what else you have broken by "going to the net" :-/ Let's look at the log.
logfile (portion) D [01/Apr/2021:18:51:36 -0400] [Job 373] Started filter pdftops (PID 23229) D [01/Apr/2021:18:51:36 -0400] [Job 373] Started filter pstops (PID 23230) D [01/Apr/2021:18:51:36 -0400] [Job 373] pdftops: error while loading shared libraries: libpoppler.so.106: cannot open shared object file: No such file or directory
You still have not installed or you have removed libpoppler. It is apparently expecting version 106, and you installed 108 earlier today.
D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23229 (pdftops) stopped with status 127! D [01/Apr/2021:18:51:36 -0400] [Job 373] STATE: -connecting-to-device D [01/Apr/2021:18:51:36 -0400] [Job 373] STATE: -media-empty-error,media-jam-error,hplip.plugin-error,cover-open-error,toner-empty-error,other
Your printer is apparently jammed or something, too.
D [01/Apr/2021:18:51:36 -0400] [Job 373] The print file is empty. D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23230 (pstops) stopped with status 1! D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23226 (/usr/lib/cups/filter/pdftops) stopped with status 1. D [01/Apr/2021:18:51:36 -0400] [Job 373] Hint: Try setting the LogLevel to "debug" to find out more. *see below* D [01/Apr/2021:18:51:36 -0400] [Job 373] HP PS filter ENDS D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23227 (/usr/lib/cups/filter/hpps) exited with no errors. D [01/Apr/2021:18:51:36 -0400] [Job 373] ready to print D [01/Apr/2021:18:51:36 -0400] [Job 373] PID 23228 (/usr/lib/cups/backend/hp) exited with no errors. D [01/Apr/2021:18:51:36 -0400] [Job 373] End of messages D [01/Apr/2021:18:51:36 -0400] [Job 373] printer-state=3(idle) D [01/Apr/2021:18:51:36 -0400] [Job 373] printer-state-message="ready to print" D [01/Apr/2021:18:51:36 -0400] [Job 373] printer-state-reasons=none
doug@linux1:/var/log/cups> LogLevel debug If 'LogLevel' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf LogLevel
What on earth do you expect that to do? It is not a command to type. It is something you can write in some config file, and we have not told you to do that, nor how. This is exasperating. Ok, do this, and only this: run: rpm -qa | grep libpopler copy the result in an email. run: zypper dup let it run to completion, don't post it. then run: rpm -qa | grep libpopler and copy the result to the same email. then reboot Then try to print one page and post everything new that appears on the log file /var/log/cups/error_log. just look at the timestamp when you tried to print and post everything after that timestamp. Don't try to do anything else. DON'T go to the NET. Don't try to repair it. You just post here and wait. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)