[SOLVED] virt-manager - No module named gi.repository
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I had virt-manager working great, until I installed pygobject3 from SBo. Now, I am getting the following error upon start up:
Traceback (most recent call last):
File "/usr/share/virt-manager/virt-manager", line 30, in <module>
from gi.repository import GObject
ImportError: No module named gi.repository
I'm thinking something is not playing nice between pygobject and py3cairo, but I can't quite put my finger on it. I've done some google searches already, but haven't found anything that would work yet. Hopefully someone here can be of better help. Thanks!
Ah, it appears that python3 is the culprit. I rebuilt pygobject3 after removing python3, and virt-manager is back to working normally. For some reason, it does not play nice when python3 is installed. I'll do some more testing before marking this thread as solved. Thank you willy for the quick reply as always. Likewise to rworkman.
Indeed, pygobject3 does not like having python3 installed. Well, virt-manager does not like that combination. So, I went ahead and built python3 after building pygobject3. So, I can mark this as solved. Thank you!