Bug 706783

Summary:	Running meld gives "Cannot import: pygtk"
Product:	[Fedora] Fedora	Reporter:	Mark Stock <mstock>
Component:	meld	Assignee:	Dominic Hopf <dmaphy>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	14	CC:	christoph.wickert, dmaphy
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-18 12:05:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mark Stock 2011-05-23 00:17:44 UTC

When I run "meld" on my Fedora 14 desktop (upgraded from F13 recently), I receive the error messages:

$ meld
Cannot import: pygtk
No module named pygtk

My new netbook, which received a fresh F14 installation, does not exhibit this problem.

All other software is up-to-date. Meld is meld-1.5.1-1.fc14.noarch

I have tried "yum reinstall meld" and "yum reinstall meld pygtk2" to no avail. Not willing (yet) to "yum remove pygtk2", as it wants to yank most of gnome.

Googling the errors and "fedora 14" only returns my lonely post on fedoraforum.org.

I am open to suggestions. Thank you.

Mark

Comment 1 Christoph Wickert 2011-05-23 07:31:20 UTC

This is probably a duplicate of bug 649507. The problem only appears in upgraded versions of python.

Comment 2 Mark Stock 2011-05-24 15:47:03 UTC

Should I follow developments there? Do you need any more information to progress?

Comment 3 Dominic Hopf 2011-06-01 22:55:34 UTC

Hi Mark, since this seems to be a generic issue with current python versions it is likely this will be fixed soon. For you in special there is nothing special to do at present, you already did the most important thing and reported this issue. :)

Of course you can keep an eye on other similar python issues, but we would keep you up-to-date anyway.

Comment 4 Mark Stock 2011-06-12 22:15:00 UTC

Hiya,

I might have solved my own problem. I installed Vapor-2.0.0 a while ago, which comes with its own python (unbeknownst to me). The installation instructs the user to add

. /usr/local/vapor-2.0.0/bin/vapor-setup.sh

to his .bashrc. With that in place, "which python" returns

/usr/local/vapor-2.0.0/bin/python

I removed that entry, logged out and back in, and now meld (and pitivi) work.

I feel dumb for not even trying "which python" before, but so many other things worked, and I just didn't realize that so many programs are python under the hood.

Thanks for taking me seriously, even though this turned out to be user error (in a way).

Mark

Comment 5 Dominic Hopf 2011-07-18 12:05:44 UTC

Thanks very much for your feedback, Mark! I'm closing this bug. :)