GIMP 2.8.14 on Yosemite Does Not Recognize Image File Types

Jeff Singleton gvibe06 at
Mon Nov 3 22:55:23 PST 2014

Looks like Ticket #45309 has been fixed. Adding a new patch 
"glib2-45309.patch" to fix the issue.

Wanted to say GOOD JOB to Jeremy for this.


On 10/26/14 6:46 PM, Ryan Schmidt wrote:
> On Oct 26, 2014, at 6:37 PM, Jeff Singleton wrote:
>> Upgraded to Yosemite, and after reading through the problems people were
>> having, I opted to delete MacPorts and re-install everything. I did not
>> change anything other than forcing the variant +quartz, and I choose to
>> compile everything.
>> Gimp will launch from the command line, as well as, from the native
>> application bundle I make from the GIMPskel scripts.
>> What happens:
>> - Launch Gimp
>> - File -> Open
>> - Browse to my Pictures folder
>>   - Inside the Open File window, in my Pictures Folder, no images
>>   - Changing to All Files, shows images
>>   - No previews are shown
>>   - Try to open an image (png) and get Error: File Type Not Recognized
>> - Searched Google for general issues first
>> - Uninstalled Gimp, Gegl, and Babl
>> - Checked to make sure all Image libs are installed
>>   - libpng, jpeg, libmng, tiff, giflib, jasper are all installed
>> - Recompiled Babl, Gegl, and Gimp
>>   - Same results
>> /opt/local/lib/gimp/2.0/plug-ins does have all of the file-* files for
>> each of the image types.
>> /opt/local/etc/ contains what is expected, pango, gtk-2.0, and gimp with
>> all of the module, loader, and rc files.
>>  From the command line I still see that DBUS error, and one other:
>>    Error spawning command line `launchctl getenv
>>    DBUS_LAUNCHD_SESSION_BUS_SOCKET': Child process killed by signal 11
>>    (gimp:27425): LibGimpBase-WARNING **: gimp: gimp_wire_read(): error
>> No other messages show up.
>> I have in the process of recompiling Gimp, deleted all .folders in my
>> home, as well as, ~/Library/Application Support/GIMP. To no avail, GIMP
>> still does not recognize anything except .xcf file types.
>> If this is a bug, is it on MacPorts, or is it something upstream?
> My first suspicion would be that using the +quartz variant may be responsible.
> Of course, undoing that selection is not so easy, since it may be any one of gimp's dependencies, and not just gimp itself, that needs to be rebuilt without the +quartz variant to fix this.

More information about the macports-users mailing list