02-12-2019, 04:38 AM | #31 |
null operator (he/him)
Posts: 20,553
Karma: 26954694
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
|
02-12-2019, 05:48 AM | #32 | |
Groupie
Posts: 164
Karma: 31650
Join Date: May 2011
Location: Asuncion (Paraguay)
Device: Several Kindle 3 KB's
|
Quote:
|
|
Advert | |
|
02-12-2019, 05:56 AM | #33 |
Grand Sorcerer
Posts: 27,546
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Note that there is a plugin index thread in the plugin subforum.
https://www.mobileread.com/forums/sh...d.php?t=247431 Makes it a little easier to see what's available. |
02-12-2019, 06:32 AM | #34 | |
Groupie
Posts: 164
Karma: 31650
Join Date: May 2011
Location: Asuncion (Paraguay)
Device: Several Kindle 3 KB's
|
Quote:
|
|
02-12-2019, 08:11 AM | #35 |
Grand Sorcerer
Posts: 27,546
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
No problem. Still no joy with the test plugin passing the hunspell check?
|
Advert | |
|
02-12-2019, 09:00 AM | #36 | |
Groupie
Posts: 164
Karma: 31650
Join Date: May 2011
Location: Asuncion (Paraguay)
Device: Several Kindle 3 KB's
|
Quote:
The error messsages are: Code:
ron@localhost:~ $ sigil Warning: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-ron' Warning: Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed Warning: libpng warning: iCCP: known incorrect sRGB profile Warning: libpng warning: iCCP: known incorrect sRGB profile ^CPlease close browser and run mozplugger-update Code:
Traceback (most recent call last): File "/usr/share/share/sigil/python3lib/xmlprocessor.py", line 182, in repairXML def repairXML(data, mtype="", indent_chars=" "): KeyboardInterrupt Code:
Traceback (most recent call last): File "/usr/share/share/sigil/python3lib/xmlprocessor.py", line 182, in repairXML def repairXML(data, mtype="", indent_chars=" "): KeyboardInterrupt |
|
02-12-2019, 09:56 AM | #37 |
Grand Sorcerer
Posts: 27,546
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
As far as running from the commandline goes; you are starting Sigil by using the /usr/bin/sigil script and not by directly running the /usr/lib/sigil/sigil binary, correct?
|
02-12-2019, 01:09 PM | #38 | |
Groupie
Posts: 164
Karma: 31650
Join Date: May 2011
Location: Asuncion (Paraguay)
Device: Several Kindle 3 KB's
|
Quote:
So I tried /usr/bin/sigil and got this: Code:
ron@localhost:~ $ /usr/lib/sigil/sigil /usr/lib/sigil/sigil: error while loading shared libraries: libsigilgumbo.so: cannot open shared object file: No such file or directory |
|
02-12-2019, 01:20 PM | #39 |
Guru
Posts: 653
Karma: 4568205
Join Date: Jan 2010
Location: Sweden
Device: Kobo Forma
|
Try "which sigil".
|
02-12-2019, 01:23 PM | #40 |
Grand Sorcerer
Posts: 27,546
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
That's what I would expect if you bypassed the launch script. It helps to know you're not doing that, but it doesn't help me understand why it won't launch normally from the menu or the command line (when it does for me when installed from the same repos).
Are you running one of the official PCLinuxOS versions or did you happen to download one of the community-created versions? The official downloads typically allow you to choose between KDE and Mate for Desktop Environments. I'd like to try and set up a virtual machine of the exact same system/DE you're using if I can. |
02-12-2019, 03:01 PM | #41 |
Grand Sorcerer
Posts: 27,546
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Also make certain you have the lib64python3.6 package installed. It should match the version of python3 you have installed if there's any question.
|
02-12-2019, 03:26 PM | #42 | |
Groupie
Posts: 164
Karma: 31650
Join Date: May 2011
Location: Asuncion (Paraguay)
Device: Several Kindle 3 KB's
|
Code:
ron@localhost:~ $ which sigil /usr/bin/sigil Quote:
lib64python3.6 is installed, and both it and python3 are version 3.6.5-3 |
|
02-12-2019, 03:35 PM | #43 | |
Grand Sorcerer
Posts: 27,546
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
I figured, but I had to be certain. |
|
02-12-2019, 06:53 PM | #44 |
Grand Sorcerer
Posts: 27,546
Karma: 193191846
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. |
02-13-2019, 04:03 AM | #45 |
Groupie
Posts: 164
Karma: 31650
Join Date: May 2011
Location: Asuncion (Paraguay)
Device: Several Kindle 3 KB's
|
Works perfectly now, thanks again for your help.
I have copied the gist of that information on the PCLinuxOS forum, for their edification. https://www.pclinuxos.com/forum/inde...48065.new.html |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Sigil-0.8.4 not launching on Windows 7 Professional 32-bit | jwlewis | Sigil | 28 | 06-11-2015 10:13 PM |
Sigil Problem??? | crutledge | Sigil | 8 | 10-20-2013 04:30 PM |
Sigil not launching in Win XP on VMWare | sachinwalia | Sigil | 19 | 01-27-2010 03:19 AM |
Problem launching Calibre in OS X - depends on which USER | Nigel Brooks | Calibre | 10 | 11-13-2009 02:37 AM |
iLiad Problem Launching ipdf from other app | joana.estafanell | iRex Developer's Corner | 7 | 12-27-2008 05:41 AM |