Sigil on Linux

[signum]

Last weekend, I installed Kubuntu Linux 16.04 (Xenial) on my home computer. I was delighted to find Sigil 0.9.5 available to install from the normal, usual repositories.

Installed it and copied the entire Sigil directory structure from my old system to the new one. It works great!

Whoever is responsible for making this happen - Thank you v v much!

Nice to be running with the big dogs again. :-)

[eschwartz]

Is Xenial either the latest release, or the currently-active development version of Ubuntu?

Because Sigil was finally added to Debian unstable, and Ubuntu presumably cloned it from there.

...

Just remember that Ubuntu being Ubuntu, they will not update it until the next major Ubuntu release.

[DiapDealer]

Looks like Mattia Rizzolo is responsible. Only available on Xenial and Yakkety, but good news nonetheless!

Might have to make a suggestion on his description, though. He's still crediting HTML Tidy for the auto-formatting/code correction instead of Gumbo.

Still ... I'm excited to see it! Thanks for letting us know.

Xenial's the latest LTS version, btw. Just released last week, I think. Yakkety will be 16.10

[eschwartz]

I figured as much, but I don't follow Ubuntu anymore so I can't really remember offhand which are the current crop of releases.

[st_albert]

Hmm, I just installed 0.9.5 from the Kubuntu 16.04 repos (64-bit), and it runs, but when I installed the testplugin 0.1.12 and tried to run it, the error message says "this plugin does not exist" or words to that effect. I blew away the Sigil preferences directory, re-installed the plugin, and got the same result. Even though the plugin was definitely there. Ditto for any of the plugins I regularly use.

However, building 0.9.5 from source worked fine.




Albert

[DiapDealer]

I think there's two packages for sigil in the repos, if I remember correctly. The second is the sigil-data package, I believe. I've no idea what the sigil-data package contributes, though.

I'd be sure to mention any issues with the repo version of Sigil to its maintainer, if possible.

[eschwartz]

sigil-data is probably the non-architecture-dependent files. Debian separates them because it is to have more packages.
I doubt that is the problem -- it should be a dependency of the main package.

[st_albert]

Originally Posted by eschwartz

sigil-data is probably the non-architecture-dependent files. Debian separates them because it is to have more packages.
I doubt that is the problem -- it should be a dependency of the main package.

You're correct. sigil-data was installed as well.

@signum: If you're still following this thread, do plugins work for you? It is remotely possible that it is PEBCAK on my part.

Albert

[signum]

I get the same error as you. I am not a big user of plugins, only once in a while. Checked a bit further and the one I just tried (it's very old; one of the first) is registered to use Python 2. Not sure that even exists on my system just yet. It's very simple so it might just work if I tell Sigil to use Python 3 instead. I'll try that later.

Just in case, can Python 2 and Python 3 co-exist simultaneously? How? Do I just install Python 2 with Muon? What new problems would I likely encounter?

Edit: Just re-read your post for anything I missed. It looks like you are using a new-ish plugin that is known to work with the default Python 3. Looks like a bug to me. No idea who to report it to or how.

[DiapDealer]

You must have Python 3.4+. Sigil 0.9.5 simply wouldn't work without it. I'm guessing the newer systems are coming with Python3 installed/configured as the default Python (with Python2 available in the repo upon request), but Sigil is defaulting to only having the Python 2 interpreter configured in the Plugin Manager.

I'd try making sure you have a Python3-ready plugin installed and then configure the Plugin Manager with the location of the Python3 interpreter. I'm betting that would do it.

[eschwartz]

Yes, python 2 & 3 coexist perfectly. Just install it from the repos.

The only issue is deciding which one should get the default symlink for the "python" command.
Which on Debian is python2.

[Doitsu]

Originally Posted by signum

Just in case, can Python 2 and Python 3 co-exist simultaneously?

You can install both, but AFAIK, pretty much all of the plugins work with Python 2 and Python 3.
I.e. you shouldn't have to install Python 2.

For testing purposes you can also install the flightcrew plugin.

If you can run this plugin, you should be able to run other plugins. Also remember not to rename or to unpack plugin zip files and to make sure that the Python interpreter path(s) defined in the Preferences dialog box are valid.

[DiapDealer]

Yep. The more I think about this, the more I'm convinced that it's a simple case of "No Python 2 Installed on the System," plus "No Python 3 Interpreter Configured in Sigil's Plugin Manager." Which adds up to "No Python Interpreter Available to Run a Plugin."

[eschwartz]

Then perhaps a clearer error message is in order.

[DiapDealer]

Originally Posted by eschwartz

Then perhaps a clearer error message is in order.

I'm pretty sure the actual error message might be a little more helpful. We've only had the "or words to that effect" version so far.

What should probably be in order is changing Sigil's code in the repo version to not have Python 2 be the only interpreter configured on systems where Python 2 isn't installed by default.