Terminator not working after update

ykonstant · 2020-12-21 16:10:03

Dear all,

after my last update with

sudo pacman -Syu

my main terminal emulator Terminator stopped working with the error:

Traceback (most recent call last):
  File "/usr/bin/terminator", line 48, in <module>
    import terminatorlib.optionparse
  File "/usr/lib/python3.9/site-packages/terminatorlib/optionparse.py", line 24, in <module>
    from . import config
  File "/usr/lib/python3.9/site-packages/terminatorlib/config.py", line 76, in <module>
    from validate import Validator
ModuleNotFoundError: No module named 'validate'

Pacman informs me that my terminator version is terminator 1.92-3 and my python version is python 3.9.1-1. Any ideas as to what has gone wrong?

ewaller · 2020-12-21 16:29:43

Are you using terminator from community? Or did you install it from the AUR?
My guess is that python has been migrated from 3.8.x to 3.9.x, and that the module 'validate' has not yet been installed for python 3.9

ykonstant · 2020-12-21 16:43:20

It is from community. Is there any way to tell terminator to use python 3.8 ? Currently, too much of my workflow depends on launching terminator in various settings, and it's all in shambles.

ewaller · 2020-12-21 16:54:08

I just installed it, tested it, and removed it from my system. No issues.

I suggest you uninstall it using pacman -Rs terminator and reinstalling it with pacman -Syu terminator
Let's see what happens.

restore · 2020-12-21 17:08:56

Same error here. I even tried to deinstall it with

sudo pacman -Rns terminator

but I got the same error as ykonstant described above. Also using Terminator version 1.92-3.

restore · 2020-12-21 17:12:09

May it be related to todays update of the package python-configobj?

ykonstant · 2020-12-21 17:13:42

restore wrote:

May it be related to todays update of the package python-configobj?

I am pretty sure the update that killed my terminator included a package that had configobj in its name. I don't remember exactly, though.

EDIT:

[2020-12-21T16:51:04+0100] [ALPM] upgraded python-configobj (5.0.6-9 -> 5.0.6-10)

appears in pacman.log.

Last edited by ykonstant (2020-12-21 17:15:15)

restore · 2020-12-21 17:17:37

Indeed it was this! After running

sudo pacman -U /var/cache/pacman/pkg/python-configobj-5.0.6-9-any.pkg.tar.zst

– provided you did not clean the cache – let terminator start again

ykonstant · 2020-12-21 17:19:41

restore wrote:

Indeed it was this! After running
sudo pacman -U /var/cache/pacman/pkg/python-configobj-5.0.6-9-any.pkg.tar.zst
– provided you did not clean the cache – let terminator start again

Is that a safe operation to do? I have a very rigid update process only via -Syu, and I am not sure if this is something like a partial upgrade that could create trouble.

restore · 2020-12-21 17:21:03

restore wrote:

Indeed it was this! After running
sudo pacman -U /var/cache/pacman/pkg/python-configobj-5.0.6-9-any.pkg.tar.zst
– provided you did not clean the cache – let terminator start again

To whoever reads this at a later time – this downgrades the package as you can read here and is only a temporary solution!!!

restore · 2020-12-21 17:25:43

ykonstant wrote:

[…] Is that a safe operation to do? I have a very rigid update process only via -Syu, and I am not sure if this is something like a partial upgrade that could create trouble.

As I wrote above, this is downgrading, not upgrading. As far as I understand the pacman process, this is regarding your “strict update process” – which I follow myself by the way – perfectly safe. As soon as one of both packages (python-configobj or terminator) has a new version, it will be updated. I expect we should both wait with further updates of those particular packages until a bugfix is provided.

ykonstant · 2020-12-21 17:31:05

restore wrote:

ykonstant wrote:
[…] Is that a safe operation to do? I have a very rigid update process only via -Syu, and I am not sure if this is something like a partial upgrade that could create trouble.
As I wrote above, this is downgrading, not upgrading. As far as I understand the pacman process, this is regarding your “strict update process” – which I follow myself by the way – perfectly safe. As soon as one of both packages (python-configobj or terminator) has a new version, it will be updated. I expect we should both wait with further updates of those particular packages until a bugfix is provided.

OK, thank you for the information!

restore · 2020-12-21 17:43:58

ykonstant wrote:

[...] OK, thank you for the information!

You are very welcome! This is actually the first time ever I could help anybody here – happy times!

I also added a bug report, let’s see what happens.

loqs · 2020-12-21 17:46:15

python-configobj 5.0.6-10 moved to git master and picked up https://github.com/DiffSK/configobj/com … 65190cbc62
Unfortunately https://github.com/DiffSK/configobj/blo … alidate.py compat shim is not being installed.
Edit:
Please try rebuilding python-configobj with the changes below

git diff
diff --git a/trunk/PKGBUILD b/trunk/PKGBUILD
index 443c14b..db1045c 100644
--- a/trunk/PKGBUILD
+++ b/trunk/PKGBUILD
@@ -16,7 +16,9 @@ source=("git+$url#commit=3e2f4cca81b60171e6b3e23619f6f4929a13322e") # latest mas
 sha256sums=(SKIP)
 
 package() {
+  export PYTHONPATH="$PYTHONPATH:$PWD"
   cd configobj
   python setup.py install --root="$pkgdir" --optimize=1
+  python setup_validate.py install --root="$pkgdir" --optimize=1
   install -Dm644 LICENSE "$pkgdir/usr/share/licenses/$pkgname/LICENSE"
 }

Last edited by loqs (2020-12-21 18:02:02)

restore · 2020-12-21 18:52:00

loqs wrote:

Please try rebuilding python-configobj with the changes below
…

I tried with the following steps:

$ mkdir /tmp/python-configobj
$ cd !$
$ wget https://github.com/archlinux/svntogit-community/raw/packages/python-configobj/trunk/PKGBUILD
$ # add the two lines of your patch with an editor to PKGBUILD
$ makepkg

This gave me the following error:

Copying src/configobj.egg-info to /tmp/python-configobj/pkg/python-configobj/usr/lib/python3.9/site-packages/configobj-5.1.0.dev0-py3.9.egg-info
running install_scripts
Traceback (most recent call last):
  File "/tmp/python-configobj/src/configobj/setup_validate.py", line 17, in <module>
    from validate import __version__ as VERSION
  File "/tmp/python-configobj/src/configobj/validate.py", line 32, in <module>
    from configobj.validate import *
ModuleNotFoundError: No module named 'configobj.validate'; 'configobj' is not a package
==> FEHLER: Ein Fehler geschah in package().
    Breche ab...

loqs · 2020-12-21 19:27:20

Did you have python-configobj installed when you ran makepkg?
Change PYTHONPATH so $PWD is searched first, does that work?

git diff
diff --git a/trunk/PKGBUILD b/trunk/PKGBUILD
index 443c14b..0b452e5 100644
--- a/trunk/PKGBUILD
+++ b/trunk/PKGBUILD
@@ -16,7 +16,9 @@ source=("git+$url#commit=3e2f4cca81b60171e6b3e23619f6f4929a13322e") # latest mas
 sha256sums=(SKIP)
 
 package() {
+  export PYTHONPATH="$PWD:$PYTHONPATH"
   cd configobj
   python setup.py install --root="$pkgdir" --optimize=1
+  python setup_validate.py install --root="$pkgdir" --optimize=1
   install -Dm644 LICENSE "$pkgdir/usr/share/licenses/$pkgname/LICENSE"
 }

RubyCasey · 2020-12-21 22:39:58

I ran a system upgrade today and ended up having the same problem. I don't know a lot about python, but "ModuleNotFound" sounded like a missing dependency to me. I ran "pip install validate" to see if that might fix the issue, but that returned (what I think is) a syntax error within the validate module.

Full pip output:

Defaulting to user installation because normal site-packages is not writeable
Collecting validate
  Using cached validate-1.0.1.tar.gz (32 kB)
    ERROR: Command errored out with exit status 1:
     command: /usr/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-4l701nhu/validate/setup.py'"'"'; __file__='"'"'/tmp/pip-install-4l701nhu/validate/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-5drp7feu
         cwd: /tmp/pip-install-4l701nhu/validate/
    Complete output (8 lines):
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-4l701nhu/validate/setup.py", line 13, in <module>
        from configobj import __version__ as VERSION
      File "/tmp/pip-install-4l701nhu/validate/configobj.py", line 1632
        except Exception, e:
                        ^
    SyntaxError: invalid syntax
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

loqs · 2020-12-21 22:59:01

@RubyCasey please try the following:

pacman -S devtools git #install devtools used to build in a clean chroot and git needed to obtain source
git clone git://git.archlinux.org/svntogit/community.git --single-branch --branch "packages/python-configobj" #clone package source
cd community/trunk
curl -o PKGBUILD.diff http://ix.io/2J4c #download patch
git apply PKGBUILD.diff
extra-x86_64-build #build package in a clean chroot
pacman -U python-configobj-5.0.6-10-any.pkg.tar.zst #install built package

Edit:
See also https://github.com/gnome-terminator/terminator/pull/325

Last edited by loqs (2020-12-21 23:07:01)

RubyCasey · 2020-12-21 23:11:34

loqs wrote:

@RubyCasey please try the following:

pacman -S devtools git #install devtools used to build in a clean chroot and git needed to obtain source
git clone git://git.archlinux.org/svntogit/community.git --single-branch --branch "packages/python-configobj" #clone package source
cd community/trunk
curl -o PKGBUILD.diff http://ix.io/2J4c #download patch
git apply PKGBUILD.diff
extra-x86_64-build #build package in a clean chroot
pacman -U python-configobj-5.0.6-10-any.pkg.tar.zst #install built package

Edit:
See also https://github.com/gnome-terminator/terminator/pull/325

That fixed it, thanks!

Campaigner444 · 2020-12-22 14:45:02

RubyCasey wrote:

loqs wrote:

@RubyCasey please try the following:

pacman -S devtools git #install devtools used to build in a clean chroot and git needed to obtain source
git clone git://git.archlinux.org/svntogit/community.git --single-branch --branch "packages/python-configobj" #clone package source
cd community/trunk
curl -o PKGBUILD.diff http://ix.io/2J4c #download patch
git apply PKGBUILD.diff
extra-x86_64-build #build package in a clean chroot
pacman -U python-configobj-5.0.6-10-any.pkg.tar.zst #install built package

Edit:
See also https://github.com/gnome-terminator/terminator/pull/325

That fixed it, thanks!

Thank you. This worked for me too.

restore · 2020-12-26 17:12:43

loqs wrote:

[…] Edit:
See also https://github.com/gnome-terminator/terminator/pull/325

Wasn't at my PC for a few days, thank you! With today's update and version community/python-configobj 5.0.6.r110.g3e2f4cc-1, terminator also works for me

Arch Linux

#1 2020-12-21 16:10:03

Terminator not working after update

#2 2020-12-21 16:29:43

Re: Terminator not working after update

#3 2020-12-21 16:43:20

Re: Terminator not working after update

#4 2020-12-21 16:54:08

Re: Terminator not working after update

#5 2020-12-21 17:08:56

Re: Terminator not working after update

#6 2020-12-21 17:12:09

Re: Terminator not working after update

#7 2020-12-21 17:13:42

Re: Terminator not working after update

#8 2020-12-21 17:17:37

Re: Terminator not working after update

#9 2020-12-21 17:19:41

Re: Terminator not working after update

#10 2020-12-21 17:21:03

Re: Terminator not working after update

#11 2020-12-21 17:25:43

Re: Terminator not working after update

#12 2020-12-21 17:31:05

Re: Terminator not working after update

#13 2020-12-21 17:43:58

Re: Terminator not working after update

#14 2020-12-21 17:46:15

Re: Terminator not working after update

#15 2020-12-21 18:52:00

Re: Terminator not working after update

#16 2020-12-21 19:27:20

Re: Terminator not working after update

#17 2020-12-21 22:39:58

Re: Terminator not working after update

#18 2020-12-21 22:59:01

Re: Terminator not working after update

#19 2020-12-21 23:11:34

Re: Terminator not working after update

#20 2020-12-22 14:45:02

Re: Terminator not working after update

#21 2020-12-26 17:12:43

Re: Terminator not working after update

Board footer