MobileRead Forums - View Single Post

DiapDealer · 02-12-2019, 06:53 PM

OK, here's the scoop.

After setting up Community-PCLinuxOS-Xfce (which seems to have a few issues of its own). I ran "apt-get dist-upgrade" and when that was done I ran "apt-get install sigil". Once all the extra packages were finished installing, I was in the same boat you were: Sigil wouldn't launch from the menus, and I got the exact same errors you did trying to launch via the command-prompt. I can assure you that this was not the case with either of the official PCLOS releases.

Long story short ... I removed mozplugger (and one other multimedia thingimabob that depended upon it), and after that Sigil launched just fine--from both the menus and from the command prompt.

Next up: downloaded and installed the testplugin and ran it. Needless to say most tests failed. So I installed the sigil-plugin-framework package and ran the testplugin again. This time, everything except the 2 gui modules (PyQt5 and Tkinter), and the libhunspell test passed. I made the symbolic link to the linhunspell-1.6.so library in the /usr/lib/sigil/ directory that we talked about in this thread and that test then passed.

NOTE: those who rely on the PCLOS sigil-plugin-framework package to make Sigil plugin-ready will be disappointed the first time they try to use a Sigil plugin that has a gui interface (which to be fair is probably only most of them), since that package doesn't install tkinter or PyQt5. So I installed the tkinter3 package and the python3-qt5 (and python3-sip) packages. This fixed the tkinter test, but not the PyQt5 test. Suffice to say that PyQt5 is badly broken when installed via the python3-qt5/python3-sip packages. I couldn't even get PyQt5 to work outside of Sigil. So I removed those two packages.

I then installed python3-pip and used that to install PyQt5 and got it working via a python3 shell at least, but it never would work in the Sigil testplugin (even though the location pip installed it was in Python's sys.path). Go figure.

So, yeah.... It's a bit of mess. But still, you ought to have a fairly functional version of Sigil just by removing the mozplugger package. There's not many plugins that use a PyQt5 interface, so many will still be available to use.

02-12-2019, 06:53 PM	#44
DiapDealer Grand Sorcerer Posts: 28,774 Karma: 206758686 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	OK, here's the scoop. After setting up Community-PCLinuxOS-Xfce (which seems to have a few issues of its own). I ran "apt-get dist-upgrade" and when that was done I ran "apt-get install sigil". Once all the extra packages were finished installing, I was in the same boat you were: Sigil wouldn't launch from the menus, and I got the exact same errors you did trying to launch via the command-prompt. I can assure you that this was not the case with either of the official PCLOS releases. Long story short ... I removed mozplugger (and one other multimedia thingimabob that depended upon it), and after that Sigil launched just fine--from both the menus and from the command prompt. Next up: downloaded and installed the testplugin and ran it. Needless to say most tests failed. So I installed the sigil-plugin-framework package and ran the testplugin again. This time, everything except the 2 gui modules (PyQt5 and Tkinter), and the libhunspell test passed. I made the symbolic link to the linhunspell-1.6.so library in the /usr/lib/sigil/ directory that we talked about in this thread and that test then passed. NOTE: those who rely on the PCLOS sigil-plugin-framework package to make Sigil plugin-ready will be disappointed the first time they try to use a Sigil plugin that has a gui interface (which to be fair is probably only most of them), since that package doesn't install tkinter or PyQt5. So I installed the tkinter3 package and the python3-qt5 (and python3-sip) packages. This fixed the tkinter test, but not the PyQt5 test. Suffice to say that PyQt5 is badly broken when installed via the python3-qt5/python3-sip packages. I couldn't even get PyQt5 to work outside of Sigil. So I removed those two packages. I then installed python3-pip and used that to install PyQt5 and got it working via a python3 shell at least, but it never would work in the Sigil testplugin (even though the location pip installed it was in Python's sys.path). Go figure. So, yeah.... It's a bit of mess. But still, you ought to have a fairly functional version of Sigil just by removing the mozplugger package. There's not many plugins that use a PyQt5 interface, so many will still be available to use.