[Linux] FlightCrew Plugin don't works with 0.9.0

[Camelot]

Hi, today i update Sigil from my Debian/sid repo to 0.9.0.

I notice, Sigil has nothing validator
Now i install FlightCrew as plugin, but not working.

When click on start:

Traceback (most recent call last):
  File "/usr/share/sigil/plugin_launchers/python/launcher.py", line 301, in <module>

    sys.exit(main())
  File "/usr/share/sigil/plugin_launchers/python/launcher.py", line 262, in main
    bc = ValidationContainer(rk)
  File "/usr/share/sigil/plugin_launchers/python/validationcontainer.py", line 42, in __init__
    super(ValidationContainer, self).__init__(wrapper, debug)
  File "/usr/share/sigil/plugin_launchers/python/outputcontainer.py", line 45, in __init__
    self.hspell=HunspellChecker(wrapper.get_hunspell_path())
  File "/usr/share/sigil/plugin_launchers/python/pluginhunspell.py", line 41, in __init__
    self.hunspell.Hunspell_create.restype = POINTER(c_int)
  File "/usr/lib/python2.7/ctypes/__init__.py", line 378, in __getattr__
    func = self.__getitem__(name)
  File "/usr/lib/python2.7/ctypes/__init__.py", line 383, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /usr/bin/python2: undefined symbol: Hunspell_create

With Sigil 0.8.7 from Debian/testing no Problem/no error with the FlightCrew Plugin.

python2.7: 2.7.10-5
python3.4: 3.4.3-7
libtcl8.6: 8.6.4

Please help.

[Turtle91]

Make sure you check "use Bundled Python" in Preferences/Plugins...that's what did it for me.

[DiapDealer]

I have no idea what what your repo maintainer changed when packaging v0.9.0 for Debian/sid, but I do know that the current Flightcrew plugin works fine when Sigil v0.9.0 is built from source (with either Python2.7 or Python3.4).

And building from source is currently the only "officially" supported method of installing Sigil on Linux. As much as we might like to, we can't really work on bugs that someone else may have introduced. You'll probably need to report this to the Debian/sid repo maintainers.

[DiapDealer]

Originally Posted by Turtle91

Make sure you check "use Bundled Python" in Preferences/Plugins...that's what did it for me.

That's not an option on Linux.

[Camelot]

Originally Posted by DiapDealer

As much as we might like to, we can't really work on bugs that someone else may have introduced. You'll probably need to report this to the Debian/sid repo maintainers.

Thanks, i report this bug to Maintainer.

[DiapDealer]

Judging by the error message, unfortunately, I'm guessing that no plugins are going to run for you.

Looks like maybe they've forgotten to enforce the libhunspell dependency. You could try installing libhunspell-1.3-0 to see if that helps, but that's just a wild guess.

[eschwartz]

Runs fine for me on ArchLinux, using sigil-git 0.9.0.r2.g6a465dd-1 compiled from the AUR.
Just plain old Sigil, with SYSTEM_LIBS_REQUIRED and a dependency on hunspell and minizip.

So I agree it is probably the debian packaging at fault, though I don't know what.
I don't know how debian determines dependencies (are linked libraries automatically pulled in) but the *.deb lists libhunspell...

[DiapDealer]

I'm not sure what they've done either, to be honest. I just know that that particular error means that the python plugin framework can't find (or can't load with ctypes.cdll) the libhunspell shared library. Which means the ctypes hunspell interface can't be inialized.

The framework first tries to locate hunspell in the same directory as the Sigil executable (where it's put when the bundled hunspell is built). If that fails, it attempts to locate a system hunspell using ctypes.util.find_library.

[eschwartz]

Vanilla python 3.5.0-2 here also.

*Maybe* debian did something amusing with python instead?

...

Considering it is debian which requested for system libhunspell to be an option with the plugin launcher, it is interesting that their package is the one that won't run a plugin properly.

[KevinH]

Hi eschwartz,

Good point but that might be partially my fault. Many packagers may not be users of Sigil and therefore do not have an easy way to test plugin use. I think we shoudl include an official testwithme.zip plugin in the docs and have it exercise the plugin interface and include a sample of what the output should look like so that they can more easily test their build works with plugins.

We have a testme3 plugin that could easily be modified to do that. I will add this to my to-do list.

KevinH

[DiapDealer]

That's not a bad idea.

In addition, I have a change I'd like to make to the pluginhunspell.py file so that in the event that the libhunspell shared flibrary can't be found and/or loaded at runtime, it will only affect plugins that actually attempt to USE libhunspell. Other plugins would still be functional.

Does that make sense? Or would it only make plugin troubleshooting more complicated?

[Doitsu]

Originally Posted by eschwartz

*Maybe* debian did something amusing with python instead?

Actually, the official debian Sigil 0.9.0 packages (sigil & sigil_data) are only available for the unstable Debian version, "sid." They can't be installed on Debian 8 "jessie" machines. However, if you build Sigil on a Debian 8 machine, it works just fine.

@Camelot: Have a look at DiapDealer's very detailed Linux build instructions and try to build Sigil 0.9.0 from source. (It requires only moderate technical skills.)

[eschwartz]

Originally Posted by KevinH

Hi eschwartz,

Good point but that might be partially my fault. Many packagers may not be users of Sigil and therefore do not have an easy way to test plugin use. I think we shoudl include an official testwithme.zip plugin in the docs and have it exercise the plugin interface and include a sample of what the output should look like so that they can more easily test their build works with plugins.

We have a testme3 plugin that could easily be modified to do that. I will add this to my to-do list.

KevinH

That sounds like an excellent idea.

[eschwartz]

Originally Posted by Doitsu

Actually, the official debian Sigil 0.9.0 packages (sigil & sigil_data) are only available for the unstable Debian version, "sid." They can't be installed on Debian 8 "jessie" machines. However, if you build Sigil on a Debian 8 machine, it works just fine.

So you're saying it might have something to do with sid.
Whatever it is that debian packagers may or may not be doing.

[Camelot]

Thanks for your replies, i reported the bug and downgrade to Sigil 0.8.7.