Page error msg on opening Sigil

[DiapDealer]

Whoops! Spoke too soon. It's definitely the PCLOS lib64xml2_2 (v2.9.7-1) package that's causing the issue. Hopefully they'll fix it soon. Arch's latest libxml2-2.9.7 doesn't suffer from it.

I may give the standalone installer a try. Would it need upgrading at all though?

Yes. It doesn't use many system libraries, so anytime a new version of Sigil was released, you'd have to manually update it.

Another easier fix that I've verified will work is using the installer I created that only places a compatible version of libxml2 into your regular Sigil installation directory. I created it because there have been lot's of buggy versions of libxml2 that caused problems for Sigil (and other programs using webkit). There's a sticky thread on it too.

It should get you by until they update their libxml2 package.

This bug report looks relevant.

[DiapDealer]

Originally Posted by C-novice

Looking back at this,
libxml2 on PCLOS (2.7.1-1)? you found this version in Synaptic? I don't see it. These I see are installed among others

lib64xml2_2 ver 2.9.7-1
libxml2-python ver 2.9.7-1
lib64xml++2.6_2 ver 2.40.1-2

Typo. Sorry. lib64xml2_2 v2.9.7-1 is what I meant. Those other packages aren't used by Sigil.

[C-novice]

Originally Posted by DiapDealer

Whoops! Spoke too soon. It's definitely the PCLOS lib64xml2_2 (v2.9.7-1) package that's causing the issue. Hopefully they'll fix it soon. Arch's latest libxml2-2.9.7 doesn't suffer from it.


Yes. It doesn't use many system libraries, so anytime a new version of Sigil was released, you'd have to manually update it.

Another easier fix that I've verified will work is using the installer I created that only places a compatible version of libxml2 into your regular Sigil installation directory. I created it because there have been lot's of buggy versions of libxml2 that caused problems for Sigil (and other programs using webkit). There's a sticky thread on it too.

It should get you by until they update their libxml2 package.

This bug report looks relevant.

I'm glad you were able to see it; I was wondering if something may indeed be wrong with my computer.

Thanks for taking the time to figure this out and thanks for the alternative options. .