Opened 8 years ago
Closed 8 years ago
#133 closed defect (invalid)
fntcnf1 does not properly load from 2.12.1-2 pentium4
Reported by: | Lewis Rosenthal | Owned by: | |
---|---|---|---|
Priority: | Feedback pending | Milestone: | |
Component: | fontconfig | Version: | |
Severity: | high | Keywords: | |
Cc: |
Description
I had fontconfig 2.12.1-2 installed. I installed latest Lucide 1.4.0 RC4 (up from 1.3.5). All prerequisites met for poppler, however, Lucide exited immediately. POPUPLOG.OS2 contains two instances of:
12-18-2016 13:50:11 SYS2070 PID 1035 TID 0001 Slot 01b4 C:\PROGRAMS\LUCIDE\LUCIDE.EXE FNTCNF1->LIBCX0._read 127
(libcx0 is 0.4.1 pentium4)
Removing lupopplr.dll revealed that indeed, poppler could not start. Running fc-validate.exe from the command line resulted in a similar failure. In fact, PMDLL (latest) exits immediately upon attempting to load that fntcnf1.dll.
Downgraded to fontconfig 2.11.95-1 seems to resolve the issue for poppler not loading, and fc-validate also works.
I'm not sure what debug data I can provide (I have no TRP files generated from anything). I'll test on a few more systems. The only thing different about this machine is that it is running a special uconv.dll to address an Apache issue (Paul built it in 2013), but I have not seen any other issues with it, and as I say, the downlevel fontconfig seems to work just fine.
Change History (2)
comment:1 by , 8 years ago
Priority: | major → Feedack pending |
---|
comment:2 by , 8 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Ugh. I should have thought to check. Indeed, libcx was backleveled for some reason, and not in the manner in which I would have expected. I normally just place an alternative dll ahead in libpath for testing, but this one was:
9-25-16 16:35 17,207 0 libcx0.dll
which was clearly backleveled as not only did ANPM tell me that 0.4.1 was installed, but the docs matched 0.4.1.
I replaced the dll with the proper one, and can confirm that after upgrading fontconfig to 2.12.1-2 (again), everything works as expected.
Sorry for the waste of time!
I heavily doubt there is a fntcfg1.dll issue with libcx, as then a lot ppl would see it. I more suspect you use a old libcx somewhere. Or a old libcx was loaded when you updated libcx and you did not reboot.