After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 711718 - no pygimp.env file
no pygimp.env file
Status: RESOLVED DUPLICATE of bug 711491
Product: GIMP
Classification: Other
Component: Windows Installer
2.8.8
Other Windows
: Normal normal
: 2.8
Assigned To: Jernej Simončič
Jernej Simončič
: 712644 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-11-09 08:46 UTC by Rod
Modified: 2013-11-30 20:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Rod 2013-11-09 08:46:10 UTC 
Python modules load but are not present after load in the menu.
After copying pygimp.env to the new gimp-2.8.8 lib/gimp/2.0/environ folder all works correctly.
Comment 1 André Klapper 2013-11-09 12:15:41 UTC 
How is this related to the "pygtk" package?
Comment 2 Rod 2013-11-10 10:35:58 UTC 
Sorry.I had no idea where to post the bug report.
Comment 3 André Klapper 2013-11-10 11:23:09 UTC 
-> GIMP (not correct either, but slightly closer)
Comment 4 Michael Schumacher 2013-11-11 09:51:31 UTC 
This could explain why some user don't get this problem - those who had a previous GIMP 2.8.x install (the installer is meant to be used to install just over them, but some users remove any trace before that, or it may be their first install).

Setting to the Installer component to see whether this fiule has been left out, or if there is a different problem. Maybe it is considered obsolete, and we're seeing some other symptom.
Comment 5 Jernej Simončič 2013-11-11 17:25:24 UTC 
My installer always shipped with empty pygimp.env - PYTHONPATH was set in default.env, but only on 64-bit installs (there's even a comment in the install script that writes the variable "//only needed on 64bit GIMP"). Looks like everything worked fine in older versions without setting the environment. I'll fix this, and release an updated installer.
Comment 6 Michael Schumacher 2013-11-21 00:09:26 UTC 
*** Bug 712644 has been marked as a duplicate of this bug. ***
Comment 7 Michael Schumacher 2013-11-30 20:03:46 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 711491 ***