Update on this issue.
If I type "dbus-launch PathToGimp", gimp launches and the
file/open works fine. Can anyone tell me if dbus was implimented in
this new 2.2.17 version, or what exactly dbus does that gimp needs?
Martin Cracauer wrote:
Steven M. Dodier wrote on Mon, Aug 03, 2009 at
___
Gimp-user mailing list
Gimp-user@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Since you do not have control over your networked copy of Gimp I
suggest another route. As I recall the self loading Debian
Hello,
Hoping someone can help resolve this problem. I have done searches of
archives and web sites without much luck. I know this version is a
little old, but I don't have any control over updating the
installation. My problem is related to gimp (2.2.17). I can start gimp
from an nfs
So you think that the older gimp version that I am using is the issue?
If I had a newer gimp version, it would work just fine?
John Culleton wrote:
On Monday 03 August 2009 09:32:21 am Steven M. Dodier wrote:
Hello,
Hoping someone can help resolve this problem. I have done
Steven M. Dodier wrote on Mon, Aug 03, 2009 at 07:32:21AM -0600:
Hello,
Hoping someone can help resolve this problem. I have done searches of
archives and web sites without much luck. I know this version is a
little old, but I don't have any control over updating the
installation.
Hi Martin,
Thanks for your response. It's a little unclear to me how you
determined which libs needed to be moved out of the way. Can you
explain with a little more detail how you found out what needed moving,
and where you moved it to.
Thanks,
Steve
Martin Cracauer wrote:
Steven M.
