MobileRead Forums - View Single Post

Banjo · 04-10-2020, 10:45 AM

I booted my Mageia computer and confirmed that Sigil still crashes when using the original script. OK fine.

I renamed the superfluous Qt folders in /usr/lib64, qt3 and qt4, to remove them from any search in /usr/lib64. That had no effect, and Sigil crashed anyway. So I put them back.

Then, I edited the /usr/bin/sigil startup script and commented out the QTLIB_DIR environment variable

Code:

#QTLIB_DIR="/usr/lib64"

After that, Sigill runs fine. I presume that without the QTLIB_DIR variable, Sigil defaults somehow to a system default for Qt. How does a program find a system default? Is there a prescribed search sequence?

Anyway, another workaround for this problem is to simply remove the environment variable from the script.

I found /etc/alternatives and listed anything with qt

Code:

[root@BSKMageia alternatives]# ll | grep qt
lrwxrwxrwx 1 root root 36 Jul 22  2019 bssh-askpass -> /usr/libexec/openssh/qt5-ssh-askpass*
lrwxrwxrwx 1 root root 24 Feb 17 07:53 qmake -> /usr/lib64/qt5/bin/qmake*
lrwxrwxrwx 1 root root 25 Apr 18  2019 qtconfig -> /usr/lib/qt3/bin/qtconfig*
lrwxrwxrwx 1 root root 36 Jul 22  2019 ssh-askpass -> /usr/libexec/openssh/qt5-ssh-askpass*

It is interesting to note that qtconfig is pointing to qt3/qtconfig. That doesn't sound right.

But there is no qtconfig in qt5, so maybe qtconfig is something that is not used anymore.

Continuing to look for what is going on here.

04-10-2020, 10:45 AM	#41
Banjo Zealot Posts: 120 Karma: 5276 Join Date: Feb 2013 Device: Asus Zen Pad	I booted my Mageia computer and confirmed that Sigil still crashes when using the original script. OK fine. I renamed the superfluous Qt folders in /usr/lib64, qt3 and qt4, to remove them from any search in /usr/lib64. That had no effect, and Sigil crashed anyway. So I put them back. Then, I edited the /usr/bin/sigil startup script and commented out the QTLIB_DIR environment variable Code: #QTLIB_DIR="/usr/lib64" After that, Sigill runs fine. I presume that without the QTLIB_DIR variable, Sigil defaults somehow to a system default for Qt. How does a program find a system default? Is there a prescribed search sequence? Anyway, another workaround for this problem is to simply remove the environment variable from the script. I found /etc/alternatives and listed anything with qt Code: [root@BSKMageia alternatives]# ll \| grep qt lrwxrwxrwx 1 root root 36 Jul 22 2019 bssh-askpass -> /usr/libexec/openssh/qt5-ssh-askpass* lrwxrwxrwx 1 root root 24 Feb 17 07:53 qmake -> /usr/lib64/qt5/bin/qmake* lrwxrwxrwx 1 root root 25 Apr 18 2019 qtconfig -> /usr/lib/qt3/bin/qtconfig* lrwxrwxrwx 1 root root 36 Jul 22 2019 ssh-askpass -> /usr/libexec/openssh/qt5-ssh-askpass* It is interesting to note that qtconfig is pointing to qt3/qtconfig. That doesn't sound right. But there is no qtconfig in qt5, so maybe qtconfig is something that is not used anymore. Continuing to look for what is going on here.