On 01/11/2014 23:45, Eric A. Borisch wrote:
Are you able to open something that uses a plugin, like a png? My gimp
starts up, but none of the plugins (required for most file types) are
working.
I have had a quick explore and I am finding the same as you - so I take
back what I said about MacPor
This is a known, upstream bug: https://trac.macports.org/ticket/45309
--Greg
On Sat, Nov 01, 2014 at 06:45:55PM -0500, Eric A. Borisch wrote:
> Are you able to open something that uses a plugin, like a png? My gimp
> starts up, but none of the plugins (required for most file types) are
> working.
Are you able to open something that uses a plugin, like a png? My gimp
starts up, but none of the plugins (required for most file types) are
working.
- Eric
On Sat, Nov 1, 2014 at 3:00 PM, David Rowe wrote:
> On 01/11/2014 16:35, Dave Horsfall wrote:
>
> . . . .
>
> Don't you get start-up mes
On 01/11/2014 16:35, Dave Horsfall wrote:
. . . .
Don't you get start-up messages like this?
| DaveHorsMacBook% gimp
| Error spawning command line `launchctl getenv
DBUS_LAUNCHD_SESSION_BUS_SOCKET': Child process killed by signal 11
| Dynamic session lookup supported but failed:
On Sat, Nov 1, 2014 at 1:24 PM, Dave Horsfall wrote:
> I'm still baffled, though. Signal 11 is SIGSEGV? That tells me "program
> bug".
>
Yes. Also not clear from this if it's the child of gimp that is segfaulting
or if the child had exec()ed launchtl by then (which would be an Apple
bug). But
On Sat, 1 Nov 2014, Brandon Allbery wrote:
> > Not enough memory? I've got 4GB here!
>
> The dbus client library synthesizes that error message when it can't
> connect to the dbus session agent, as indicated by the earlier messages.
That would be one of these two then:
| Error spawning comman
On Sat, Nov 1, 2014 at 12:35 PM, Dave Horsfall wrote:
> Not enough memory? I've got 4GB here!
The dbus client library synthesizes that error message when it can't
connect to the dbus session agent, as indicated by the earlier messages.
(That said, 4GB isn't much on OS X.)
--
brandon s allber
On Sat, 1 Nov 2014, David Rowe wrote:
> I have Gimp2 working just fine under Yosemite, MacPorts v2.3.2 and Xcode
> 6.1. It was a clean installation - after upgrading to Yosemite, I
> trashed my old MacPorts installation and started again to avoid trouble.
Don't you get start-up messages like th
I have Gimp2 working just fine under Yosemite, MacPorts v2.3.2 and Xcode
6.1. It was a clean installation - after upgrading to Yosemite, I
trashed my old MacPorts installation and started again to avoid trouble.
One simple point - MacPorts puts the launcher for Gimp in the folder
/Application
On 31 Oct 2014, at 23:50, Glenn Ramsey wrote:
> Hi,
>
> After installing the py-suds-jurko package only the top level modules seem to
> be
> available. Did I install it wrong?
>
Hi Glenn,
I can confirm that I see the same behaviour here.
The submodules are still there but need to be expor
Thanks for that. Everything's working properly again.
On Wed, Oct 29, 2014 at 1:33 PM, Christopher Jones wrote:
>
> Hi,
>
> I would suggest anyone who has foobar’ed up their systems by following the
> (badly thought out) instructions to replace bash with MacPorts version to
>
> a) put back the
11 matches
Mail list logo
