Opened 8 years ago

Closed 7 years ago

#297 closed defect (duplicate)

last night's poppler update seems to have damaged the pdf plugin

Reported by: gerry Owned by:
Priority: major Milestone:
Component: Backend Version: 1.3.6
Keywords: Cc:

Description

up to first thing this morning I was able to print .pdf files with 136rc1, but since applying YUM updates, which I am sure included one to poppler, the pdf plugin is no longer listed. same result for rc2a.

Change History (5)

comment:1 Changed 8 years ago by Gregg Young

You have to have poppler 0.42.0 install for 1.3.6rc1 to work (needs popple59.dll). You now have popple63.dll (poppler 0.47.0) installed. We are looking at a solution to this issue. For now you can either revert to poppler 0.42.0, use an old version (1.3.5 or earlier) or if you can email (ygk at qwest dot net no spaces) me privately. I can send a test version I built against poppler 0.47.0

Last edited 8 years ago by Gregg Young (previous) (diff)

comment:2 Changed 8 years ago by Lewis Rosenthal

Gerry, what I would do is this:

  1. If using ANPM, use the Get specific release feature to roll back to poppler 0.42.0-1.
  2. Copy the installed %UNIXROOT%\usr\lib\popple59.dll to %UNIXROOT%\usr\local\lib (create local and lib under that, if you don't have these already).
  3. Upgrade poppler to 0.47.0.

This will give you poppler 0.42.0 for Lucide 1.3.6 RC2a, and poppler 0.47.0 for, say, qPDFView.

Ultimately, you won't have to go through this dance every time a new poppler lands. Growing pains!

comment:3 Changed 8 years ago by gerry

Unfortunately, ANPM will not let me downlevel poppler on its own - probably need to do all three packages in the right order. However, 1.3.5 still works as well as it ever did so I can put up with that for now .... but I am always happy to try test versions

comment:4 Changed 8 years ago by Lewis Rosenthal

Related: #295

comment:5 Changed 7 years ago by Gregg Young

Resolution: duplicate
Status: newclosed

I am marking this as a duplicated of #322 which deals with all the dependency issues

Note: See TracTickets for help on using tickets.