Results 1 to 3 of 3

Thread: The GIMP not starting.. I think it's a conflict with GLib

  1. #1
    Join Date
    Sep 2011
    Location
    New York City
    Beans
    212
    Distro
    Ubuntu 11.10 Oneiric Ocelot

    Question The GIMP not starting.. I think it's a conflict with GLib

    I had just put up an update to a RAW processing program today called Darktable from a Deb file. After that I've been having a sudden problem opening up Gimp. When I typed in "gimp" in terminal I get the following message:

    (gimp:25542): GLib-WARNING **: /build/buildd/glib2.0-2.28.6/./glib/goption.c:2132: ignoring no-arg, optional-arg or filename flags 8 on option of type 0
    paulw@ubuntu:~$



    It seems to me, a noob when it comes to these dependencies that there is a conflict of some kind going on. I can only at this point attribute it to my Darktable update. How do I find out what that programs dependencies are and if they are in conflict with GIMP in any way?
    Last edited by PayPaul; November 16th, 2011 at 02:15 AM. Reason: correction of paste
    When in doubt, check it out!

    If all else fails, check the plug!

  2. #2
    Join Date
    May 2011
    Location
    Florida
    Beans
    Hidden!
    Distro
    Xubuntu

    Re: The GIMP not starting.. I think it's a conflict with GLib

    https://bugs.launchpad.net/ubuntu/+s...mp/+bug/775586

    seems to address something similar if not the same thing (?)

    it seems like the ultimate solution/workaround was to make a hidden directory for gimp.. didn't really read the whole thing but there were other relevant results on google, when I just searched for the bulk of your error message.

  3. #3
    Join Date
    Sep 2011
    Location
    New York City
    Beans
    212
    Distro
    Ubuntu 11.10 Oneiric Ocelot

    Wink Re: The GIMP not starting.. I think it's a conflict with GLib

    Quote Originally Posted by desktorp View Post
    https://bugs.launchpad.net/ubuntu/+s...mp/+bug/775586

    seems to address something similar if not the same thing (?)

    it seems like the ultimate solution/workaround was to make a hidden directory for gimp.. didn't really read the whole thing but there were other relevant results on google, when I just searched for the bulk of your error message.
    It apparently corrected itself on reboot. This was almost giving me a deja vu experience ala Microsoft.
    When in doubt, check it out!

    If all else fails, check the plug!

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •