Announcement

Collapse
No announcement yet.

GIMP will not start

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    GIMP will not start

    On a fresh install o 11.04, GIMP will not start on its own. I have installed and uninstalled 6 times, all with the same results.

    In the terminal Konsole I can do: sudo gimp

    ...and it starts and runs fine, but without special "theming".

    I found this:

    http://kubuntuforums.net/forums/inde...opic=3116364.0

    ...but I cannot find out how to change a "GTK" theme...

    ideas

    #2
    Re: GIMP will not start

    Originally posted by spottedhog
    In the terminal Konsole I can do: sudo gimp
    Not a good idea - launching a graphical application from the console using sudo. Doing so is a good way to mess up your user /home directory. There is now the likelyhood that certain files in your /home/username directory are now owned by root. To remedy this, open a console and verify that you are in your users /home directory (which you should be). Then type:
    Code:
    sudo chown -R username:username *
    where username is your logon username.

    As to Gimp running 'normally', all I can say, is that here, when I installed Gimp, I installed, from the console, the following packages: gimp gimp-data gimp-data-extras, which resulted in the following packages being installed:

    gimp gimp-data gimp-data-extras libbabl-0.0-0 libcroco3 libgail18
    libgegl-0.0-0 libgimp2.0 libpoppler-glib6 librsvg2-2 libwebkitgtk-1.0-0
    libwebkitgtk-1.0-common libwmf0.2-7

    And here, Gimp runs as it should.
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      Re: GIMP will not start

      There is a solution I found here about setting your gtk appearance to Raleigh, launch Gimp once, and then change back to whatever theme you were using before.
      Processor: AMD FX-8320 Eight-Core @ 4.00GHz (8 Cores,) Motherboard: ASUS M5A97 R2.0, Memory: 32768MB
      Disk: 2000GB ST2000DM001-9YN1 + 1000GB ST31000340AS, Network: Realtek RTL8111/8168/8411
      Graphics: ASUS AMD Radeon HD 7850, Audio: C-Media CMI8788, Monitor: S220HQL

      Comment


        #4
        Re: GIMP will not start

        Well, with no joy in finding a solution, I reinstalled 11.04 and wiped out everything, for the 3rd time. This time, immediately after the installation was finished, I installed GIMP and made sure it would open. And yes, it finally did.

        thanks!

        Comment


          #5
          Re: GIMP will not start

          Originally posted by Melcar
          There is a solution I found here about setting your gtk appearance to Raleigh, launch Gimp once, and then change back to whatever theme you were using before.
          Worked perfectly for me. Thanks!

          Comment


            #6
            Re: GIMP will not start

            Changing GTK worked for me as well.

            Comment


              #7
              Re: GIMP will not start

              it lives!!! i would just like to state the obvious though: thats weird

              Comment


                #8
                Re: GIMP will not start

                Changing GTK to Raleigh worked for me as well.
                Oneiric 11.10 KDE Version 4.7.4<br />Duo core 1.8 Intel<br />4 gig ram<br />Nvidia Go 7300 Graphics<br />Dell E1505 Laptop<br /><br />I&#39;m a happy pappy with Linux on my lappy!!!

                Comment


                  #9
                  Re: GIMP will not start

                  Originally posted by Melcar
                  There is a solution I found here about setting your gtk appearance to Raleigh, launch Gimp once, and then change back to whatever theme you were using before.
                  Glad I found this. It worked great for me as well.

                  Comment


                    #10
                    Re: GIMP will not start

                    Everyone on this thread - remember this tip because I've run into a couple other apps (Hulu Desktop was the latest) that have the exact same solution.

                    Please Read Me

                    Comment


                      #11
                      Re: GIMP will not start

                      Ok I assumed the reference to GTK was a theme under Setting/System Settings/Workspace Appearance so that's where I went. Rayleigh isn't one of the choices nor is it available under "additional themes" so I must paraphrase a question, which was asked but not answered previously in this thread:

                      What is a GTK theme and how can I change it?

                      Simple, specific instructions would be greatly appreciated.

                      Incidentally, the CLI sequence listed in one of the early replies to this thread (I'd quote specifically but this reply screen doesn't permit me the luxury) didn't solve this problem. The username of this system is simply "user" and the exact syntax I used was as follows:

                      sudo chown -R user:user *

                      If I misunderstood the instructions, I'd appreciate being corrected. You've pointed out that it's a bad idea to run the gimp via sudo so I'd appreciate having another alternative. Thanks in advance.

                      Comment


                        #12
                        Re: GIMP will not start

                        In a terminal, you need to install the gtk2-engines-oxygen package:

                        Code:
                        sudo apt-get update && sudo apt-get install gtk2-engines-oxygen
                        You probably have to restart KDE for the new package to become effective -- if you don't know how to do that just reboot your computer.

                        After KDE is up, you can go to KMenu > Systemsettings > Application appearance (not workspace appearance), and in the panel on the left you will see an icon for "GTK+ Appearance". Click that, and the top part of the right-hand panel will show "Widget Style" with a drop-down menu. Click the menu and you should see a choice for "Raleigh" as well as "oxygen-gtk". So you choose Raleigh, and click the "Apply" button. Then you change it back to oxygen-gtk, and "apply". That should fix the gimp issue.

                        Comment


                          #13
                          Re: GIMP will not start

                          Raleigh is under System Settings > Application Appearance > GTK+ Appearance

                          My understanding is basically, the GUI toolkit used to develop applications for the KDE desktop is called QT and for Gnome desktop applications the toolkit is called GTK.

                          Rather than restricting KDE users to only QT developed apps, we are also able to install GTK apps, but they look different and use different packages and settings. So the GTK themes are available to change the way GTK apps look. Raleigh is the default (I think). I use oxygen-gtk because it resembles oxygen for QT, thus giving my desktop a more uniform appearance.

                          The reason to do the theme switch-aroo is a work-around of a recent bug. I suspect this will go away in the near future.

                          Re: the quote feature = yes indeed the forum software won't let you highlight and then quote a particular part of a previous post directly. You can, however, copy-and-paste a few lines and then highlight your pasted lines and click on the quote option in the BBC tags (just above the text box. The icon looks like a cartoon text balloon. Here's is the result of doing this:
                          Incidentally, the CLI sequence listed in one of the early replies to this thread (I'd quote specifically but this reply screen doesn't permit me the luxury) didn't solve this problem. The username of this system is simply "user" and the exact syntax I used was as follows:

                          sudo chown -R user:user *
                          I can't answer your above question regarding the chown command because you didn't say what you were trying to do or what your results were. The syntax you used would change the owner and group of all files in the current directory and all it's subdirectories to "user."

                          What Snowhog actually said was a common piece of advice given here and a wise bit at that. Here's my long explanation and way of saying it:

                          It is poor operating practice to execute any program that uses a GUI (Graphical User Interface) as superuser (with root privileges) using the command line prefix "sudo". This will invariably change the ownership of some files and directories within the user's home directory to root, thus leaving the user with a malfunctioning system.

                          The preferred method to execute a GUI program as root is to launch it using the command line prefix "kdesudo". This will cause the system to redirect root file and directory related actions to the root home rather than the user's home.


                          That should cover that topic...

                          Please Read Me

                          Comment


                            #14
                            Re: GIMP will not start

                            Originally posted by oshunluvr
                            Everyone on this thread - remember this tip because I've run into a couple other apps (Hulu Desktop was the latest) that have the exact same solution.
                            Yes, I was just about to post this as well. There are many apps that weren't made specifically for KDE that have this same issue. Just changing the GTK theme seems to be the solution for all of them so far.
                            You like Linux and/or security(hacking)? I&#39;ve got a site for that! [meeb0@terminallyuncretive ~] $

                            Comment


                              #15
                              Re: GIMP will not start

                              It seems to go against the linux ethic to just tell someone to do something odd in order to get something else to work...while I am glad this works, I would very much like to know why Gimp (and others) don't work as expected...and why this workaround is necessary...does anyone have a clue? It would seem to be oxygen-gtk related (in my case)...but this isn't my domain of expertise...thoughts? Perhaps if no one has nailed it down, but we pool our thoughts, we can get the appropriate bug filed in the appropriate place.

                              But anyway, thanks for the thread, it did solve my problem immediately.

                              Cheers.

                              Comment

                              Working...
                              X