[SOLVED] slackware-14.2 -> last slackware-current upgrade python VTE issue
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
slackware-14.2 -> last slackware-current upgrade python VTE issue
Hi there,
I use slackware-current (64bits - no multilib ) and update it every once in the while.
since the latest update, terminator terminal refuses to start due to this error: "you need to install python bindings for libvte"
Okay.. I first supposed that current is supposed to be the bleeding edge and my terminator version was a bit off ( 0.97 while 1.91 is out there)
After terminator update => still the same error.
So got curious about vte/libvte but not much help on the net.. except that python should be able to import vte module.
On a fresh 14.2 install with latest 14.2 updates vte is able to load fine
If I switch to slackware-current on that same fresh 14.2 install, which seems to updates python to the same version but for current it doen't work anymore:
ok i have tested your terminator version 0.97 need vte-0.28.2 because it contain a part of pygtk2 binding.
the vte-0.44.3 slackware-current doesn't contain this part.
terminator-1.91 need vte3 version and python2-gobject binding.
I had for sure gobject installed ( and was able to import it against python2.7 )
I've tried to install vte3 from slackbuilds on current with terminator1.0 and 1.91 , no success. (tested with vte3-ng instead of vte3 also - same error)
duno how I can give more "logs" or "trace" of the issue I'm facing
edit: seen your edit: checking if python2-gobject (pygobject3) and gtk+3 are installed...
Last edited by suprateam; 05-26-2017 at 07:10 AM.
Reason: adding infos
I've started from a fresh reinstall, and well the terminator 1.91 installation with its dependencies went okay.
- terminator 1.91 ( based on the slackbuild with just the version bump)
- python-keybinder / psutil from sbo
- pygobject3, pycairo,dbus-python are included in base Slackware
Terminator is able to start okay which is fine for me at the moment.
I cannot tell where was the pbm in first place as that bassically what I did..
Maybe my packages installation at the very first place messed up smth and the vte issue wasn't the root cause.
I will tag the title as solved even though there was no pbm after all ( sorry for the noise )
About the fact that python cannot import VTE, I think you have it right of course
Code:
ok i have tested your terminator version 0.97 need vte-0.28.2 because it contain a part of pygtk2 binding.
the vte-0.44.3 slackware-current doesn't contain this part.
from install/desinstall logs it vte-0.44.3 does not contain python vte package as you said
Thanks for the links, I'll keep them somewhere close for future needs !
The pbm wasn't at buildtime but at runtime, but at least precompiled package can save some headache ^_^
cheers !
Last edited by suprateam; 05-27-2017 at 08:22 AM.
Reason: tag the thread as solved fixed
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.