still can't get gimp to work under macports....

Ryan Schmidt ryandesign at macports.org
Sun May 6 21:06:33 PDT 2012


On May 6, 2012, at 21:47, Ian Wadham wrote:

> On 07/05/2012, at 9:56 AM, Ryan Schmidt wrote:
>> On May 6, 2012, at 18:39, Brad Allison wrote:
>>> I installed gimp using
>>> 
>>> $ sudo port install gimp +no_startupitem
>>> 
>>> Per the workaround instructions on the current bug thread.  But when I try to launch it it takes FOREVER to load.  It gives me a "not enough memory" error and then just sits there forever.
> 
> I did that too.  Everything built OK and ran for a while, but then I shut down
> my machine ...  Now nothing that involves dbus will run (e.g. no KDE or Qt apps).
> I guess +no_startupitem means "I don't want to start dbus when I start my machine."

"+no_startupitem" means "I don't want MacPorts to install a launchd plist, with which I could (but am not required to) have launchd start dbus when I start my machine."


>> "sudo port selfupdate" to make sure you have the latest port definitions in which the recent dbus problems were resolved. Then "sudo port install dbus" to reinstall dbus with its default variants (i.e. not using the +no_startupitem variant). Then follow the instructions it will print for loading dbus-session. Then programs like gimp that use dbus should work.
> 
> I did "sudo port -v self update" ( I hope this got the patch OK),

I hope you mean "sudo port -v selfupdate"

> then "sudo port install dbus",
> which produced the attached log,

Ok, the transcript you attached showed you successfully running selfupdate, then using "port list outdated"—see...

https://trac.macports.org/wiki/FAQ?#portlist

...for why that's probably not what you want)—then successfully installing dbus but encountering this error during dbus activation

Error: Target org.macports.activate returned: could not set owner for file "/Library/LaunchAgents/org.freedesktop.dbus-session.plist": no such file or directory

So I guess we haven't fixed the problem after all.


> So how do I get back to where I was before I did "port selfupdate" to macports 2.0.4 yesterday
> and struck the "Unable to open port: can't read "startupitem.install"" bug?

Until Jeremy or someone figures out and commits the real fix, you can always use...

https://trac.macports.org/wiki/howto/InstallingOlderPort




More information about the macports-users mailing list