Sigil on Linux

[DiapDealer]

For the record ... when I do a fresh install of Sigil from the repo on Xenial (I set up a VM), and install the test plugin, the error I get when first trying to run the plugin is: "Error: Interpreter Python3.4 has no path set". Which is sort of what I figured.

After using the Plugin Manager to set the Python 3.x path (the 'Auto' button set the path to /usr/bin/python3 for me) the plugin then passed all tests with flying colors! Yay! Full Sigil ... plugin support (with all the recommended extra python modules) ... no compiling, no pipping.

On a completely unrelated note ... I'd forgotten how badly I hate Ubuntu's Unity interface.

[st_albert]

Originally Posted by DiapDealer

For the record ... when I do a fresh install of Sigil from the repo on Xenial (I set up a VM), and install the test plugin, the error I get when first trying to run the plugin is: "Error: Interpreter Python3.4 has no path set". Which is sort of what I figured.

After using the Plugin Manager to set the Python 3.x path (the 'Auto' button set the path to /usr/bin/python3 for me) the plugin then passed all tests with flying colors! Yay! Full Sigil ... plugin support (with all the recommended extra python modules) ... no compiling, no pipping.

On a completely unrelated note ... I'd forgotten how badly I hate Ubuntu's Unity interface.

That's definitely not the error message I got. FWIW I have both python2.7 and python3.5 installed, and Sigil did have paths showing in the plugin manager panel (I didn't look to see if they were the correct paths, however, though I have no reason to suspect they weren't).

All of the plugins I tried, including Flight Crew 0.9.1, epubcheck 0.3.6, AddIDs 0.3, kindleimport 0.80.5, and the testplugin 0.1.2 failed in the same way with the same message.

So it's still possible that there is something uniquely FUBAR about my system, and the error(s) that DiapDealer and signum are getting are not the same as what I'm seeing.

Now I'm tempted to remove the Sigil I built from source, and re-install the repo version so I can take a closer look.

Somebody stop me!

Albert

ETA: Too late. I did it. Hopefully there are 2 screenshots attached, showing (1) the PI manager window (with correct paths for Py-2.7 and Py-3.5 as automatically found by sigil, as well as the installed plugins that "don't exist" and (2) the error message itself. Not what Diap described.

$ which python2
/usr/bin/python2

$ which python3
/usr/bin/python3

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
UBUNTU_CODENAME=xenial

$ apt-cache policy sigil
sigil:
  Installed: 0.9.5+dfsg-0ubuntu1
  Candidate: 0.9.5+dfsg-0ubuntu1
  Version table:
 *** 0.9.5+dfsg-0ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
        100 /var/lib/dpkg/status

And that's all I got.

[DiapDealer]

Keep in mind my Xenial install was fresh out of the box. No prior Sigil installation. In addition to the preferences directory, keep in mind that there will be portions of Sigil left in the /usr/local prefix. The repo version will be installed in /usr.

It definitely sounds like you might be mixing and matching installation preferences a bit. Neither python interpreter path boxes should be pre-configured on a fresh repo install.

[st_albert]

Originally Posted by DiapDealer

It definitely sounds like you might be mixing and matching installation preferences a bit. Neither python interpreter path boxes should be pre-configured on a fresh repo install.

Yes, you're right. I thought about that after I posted. Before installing from the repo I renamed the following file and directories

/usr/local/bin/sigil
/usr/local/lib/sigil
/usr/local/share/sigil

but I forgot to delete sigil's preferences directory, ~/.local/share/sigil-ebook. So that's why the plugins and paths were already filled in.

Just now I uninstalled (apt-get purge sigil), deleted the preferences directory, and re-installed (apt-get install sigil). Then, I did have to click "auto" to fill in the python paths, and install the plugin again (testplugin). When I tried to run it, however, I got the same result as before. Maybe I missed some other sigil files / directories somewhere?

Oh well. I've run out of time for today.

[DiapDealer]

Originally Posted by st_albert

When I tried to run it, however, I got the same result as before. Maybe I missed some other sigil files / directories somewhere

Only the sigil desktop file (in /usr/local/applications) and the icon (in /usr/local/pixmaps).

This really is odd. I didn't have to jump through any hoops to get it to work

[anavin]

I have the same problem on my OpenSUSE 42.1; my Sigil 0.9.5 is compiled using this repo's srpm (0.9.4, with source code change to 0.9.5), but I remember that I installed the binary rpms before 0.9.5 from it and got the same result.

I use FlightCrew 0.9.1 and ePub3-itizer 0.3.6. I've used the test plugin too.

1. if I run the plugin from menu->plugins, the "A plugin with that name not exist" message appears.
2. if I set the plugin to the shortcut button then run the plugin from the button, the plugin works.
3. the problem only appears when I'm in KDE5. If I'm in IceWM (preinstalled by OpenSUSE), there's no problems.

[DiapDealer]

Interesting, thanks! That seems to suggest a KDE connection. I think this issue should definitely be reported to the appropriate repo maintainers since the problem doesn't occur when building from Sigil's official source package (KDE or otherwise). At least there seems to be a temporary work-around (running plugins from a shortcut button).

[signum]

Hoping to leverage @anavin's comment #2, I made a keyboard shortcut (Alt+P) to execute plugin #1, making sure #1 was filled in and all. The first time I tried to use the shortcut, I got an error message:
---------
Ambiguous shortcut detected

The key sequence "Alt+P" is ambiguous. Use "Configure
Shortcuts" from the 'Settings' menu to solve the
ambiguity.
No action will be triggered.
-------------
Immediately tried alt-p again, got a different error result. All it did was to display the plugin dropdown menu. When I selected with plugin I wanted, it came up with:
--------------
Error: A plugin by that name does not exist.
--------------

Sigil then alternated between these two popups every time I pressed alt+p

Two observations about the new error message:
1) "Ambiguous" probably means defined more than once. I couldn't find any other definition of alt-p, at least inside Sigil.
2) There is no 'Settings' menu and the 'configure shortcuts' menu doesn't exist under that name. The
functionality *is* available under the 'Preferences' menu, which is what I used.

[DiapDealer]

But did the plugin work if you clicked the assigned shortcut button?

[signum]

Forgot there was a *button* along with a shortcut keystroke. Tried that, and got this error:

-------------------------
p, li { white-space: pre-wrap; } ImportError: No module named _tkinter, please install the python-tk package
Error: No module named _tkinter, please install the python-tk package


--------------------------
(a few minutes later)
Installed python-tk and python3-tk. Tried the button in Sigil and it worked!


The two error messages will still happen (different on alternate trys) if I use the keyboard shortcut or enter through the plugins dropdown.