OK. Here is something that is really strange.
On a wild guess I ran sigil inside of gdb.
Code:
gdb /usr/local/bin/sigil
It wouldn't run, and it said that the file was not an executable file. That's when I found out that it is a startup script at that location. I didn't know that. So I ran the executable at /usr/local/lib64/sigil/sigil
Code:
[poobah@BSKMageia ~]$ gdb /usr/local/lib64/sigil/sigil
It runs.
It does not crash when run inside of gdb bypassing the startup script.
That is very interesting.
I took a look at the script /usr/local/bin/sigil.
It sets QTLIB_DIR="/usr/lib64"
So I listed all of /usr/lib64 with anything that has 'qt' in it (a very long listing) and at the very bottom I found
Code:
--- snip lots of stuff ---
libQtXml.so.4.8.7*
libsignon-qt5.so.1@
libsignon-qt5.so.1.0@
libsignon-qt5.so.1.0.0*
libtelepathy-logger-qt.so.0.9.80.0*
libtelepathy-logger-qt.so.5@
libtelepathy-qt5-service.so.0@
libtelepathy-qt5-service.so.0.0.9.7*
libtelepathy-qt5.so.0@
libtelepathy-qt5.so.0.0.9.7*
qca-qt5/
qt3/
qt4/
qt5/
qtcreator/
The different Qt versions are in subfolders on this system.
So I edited /usr/local/bin/sigil and changed to
Code:
QTLIB_DIR="/usr/lib64/qt5"
And it runs.
The same trick worked on the old version of sigil as well.
So, the answer is that this Mageia system does not comply with a clean installlation of Qt. It does indeed have qt3, qt4, and qt5 installed in subfolders of /usr/lib64. Sigil was not able to find Qt at all, hence the error.
Now I can go put PageEdit in and see how I can use that for editing books.
Thanks for all the help you guys gave me on this one. It made my noggin hurt for a while, but glad to have my sigil back.
Banjo