Hello, Everyone
I honestly looked as closely at the output while I compiled a fresh copy of Gimp from CVS, as well as the output from the terminal that I started Gimp from:
http://www.afolkey2.net/gimp/01/gimp-2.3CVS-TerminalOutput.txt and I saw nothing that my relatively limited abilities could pick out as a potential starting point for clearing up this problem. For contrast, here is what it looks like when I start gimp 2.3.6 (compiled from the release tarball): http://www.afolkey2.net/gimp/01/gimp-2.3.6Release-TerminalOutput.txt

Further, before I typed this email, I ran "make uninstall" in the gimp from CVS directory, grabbed a fresh copy, re-compiled and ran "make install". Still, same issue.

The problem is, almost all of the image types that Gimp from CVS opened up earlier today (before my latest update from CVS) are gone. I discovered this when I attempted to open up a JPEG image. Here is a screen shot of the file selector dialog to show the lack of image types: http://www.afolkey2.net/gimp/gimp-FileTypes-CVS.jpg

Here is a screen shot of the file selector from Gimp 2.0.5: http://www.afolkey2.net/gimp/gimp-FileTypes-2.0.5.jpg

Also, here is a screen shot of the file selector from Gimp 2.2.10: http://www.afolkey2.net/gimp/gimp-FileTypes-2.2.10.jpg

Here are links to the entire output of all of the commands involved in compiling and installing Gimp:
http://www.afolkey2.net/gimp/01/gimpCVS-autogensh.txt http://www.afolkey2.net/gimp/01/gimpCVS-configure.txt http://www.afolkey2.net/gimp/01/gimpCVS-make.txt http://www.afolkey2.net/gimp/01/gimpCVS-MakeInstall.txt

Just noticed something else. It is probably related to the above mentioned issue.
Here you will notice by comparing the following two screenshots: http://www.afolkey2.net/gimp/gimp-2.3.6CVS-FileAcquire.jpg http://www.afolkey2.net/gimp/gimp-2.3.6Release-FileAcquire.jpg that Gimp compiled from CVS lacks the choice to Acquire Screenshot.

Here you will notice by comparing these two screenshots, that the Xtns menu in Gimp compiled from CVS is almost empty. Further, one of the two entries on the Xtns menu from Gimp from CVS is not even on the Xtns menu compiled from the 2.3.6 tarball: http://www.afolkey2.net/gimp/gimp-2.3.6CVS-Xtns.jpg http://www.afolkey2.net/gimp/gimp-2.3.6Release-Xtns.jpg

If you would like me to re-compile, re-install Any version of the Gimp and send you links to the output, I would be glad to. I am assuming that this is an issue that is confined to Fedora Core 3 (I hope not just to me :)) Also, if this is a known issue, I do apologize. I am subscribed to this list, and I've seen nothing about this. I also found nothing on your bugzilla.

Well, that's all that I have on this for now.

Steven P. Ulrick

On Mon, 2 Jan 2006 15:16:00 -0800 Carol Spears wrote:

On Mon, Jan 02, 2006 at 04:52:18PM -0600, Steven P. Ulrick wrote:

compiling and installing Gimp:
http://www.afolkey2.net/gimp/01/gimpCVS-autogensh.txt http://www.afolkey2.net/gimp/01/gimpCVS-configure.txt

when you build from cvs you use the autogen.sh script and not configure. autogen calls configure. i do not know what calling configure did again but that would be the first good place to start.

when you are building from cvs, don't type "./configure"

Hello, Carol
You are quite correct. I have been guilty of running "./autogen.sh" and "./configure". It has worked just fine up until this issue started, but I will not do it anymore.
Right now I am compiling a fresh download of Gimp from CVS, running only "./autogen.sh" instead of running "./autogen.sh" and "./configure" and see if that fixes the problem that I started this thread because of.

Steven P. Ulrick

On Mon, 2 Jan 2006 18:46:22 -0600 "Steven P. Ulrick" wrote:

On Mon, 2 Jan 2006 15:16:00 -0800 Carol Spears wrote:

On Mon, Jan 02, 2006 at 04:52:18PM -0600, Steven P. Ulrick wrote:

compiling and installing Gimp:
http://www.afolkey2.net/gimp/01/gimpCVS-autogensh.txt http://www.afolkey2.net/gimp/01/gimpCVS-configure.txt

when you build from cvs you use the autogen.sh script and not configure. autogen calls configure. i do not know what calling configure did again but that would be the first good place to start.

Right now I am compiling a fresh download of Gimp from CVS, running only "./autogen.sh" instead of running "./autogen.sh" and "./configure" and see if that fixes the problem that I started this thread because of.

Steven P. Ulrick

Hello, Everyone
Running only ./autogen.sh (instead of ./autogen.sh and ./configure) on a fresh download of Gimp from CVS still yields the results that I referred to in my original email on this thread. You can find links to all output, and appropriate screenshots in that email.

Steven P. Ulrick

On Mon, 2 Jan 2006 19:18:42 -0600 "Steven P. Ulrick" wrote:

Right now I am compiling a fresh download of Gimp from CVS, running only "./autogen.sh" instead of running "./autogen.sh" and "./configure" and see if that fixes the problem that I started this thread because of.

Steven P. Ulrick

Hello, Everyone
Running only ./autogen.sh (instead of ./autogen.sh and ./configure) on a fresh download of Gimp from CVS still yields the results that I referred to in my original email on this thread. You can find links to all output, and appropriate screenshots in that email.

Hello, Everyone
I almost hesitate to mention this, because it might seem really hard to believe, but ultimately, I feel that it bears mentioning. Before my last email on this thread, I had opened Gimp from CVS to see if the file types had returned. They had not. But for whatever reason (I probably just forgot to close it out) I kept Gimp from CVS open. Next, as an experiment, I ran "make uninstall" from the Gimp CVS directory and uninstalled that version of Gimp. I then started a fresh download of Gimp from CVS. While I was waiting for the download to finish, I noticed that I had not closed Gimp from CVS before I had ran "make uninstall" Not really knowing why I tried this, I proceeded to open up the File Selection dialog. Remember, the version of Gimp that I am "now" opening up the File Selector from has been uninstalled. Guess what? All of my image types are now accessible through the File Selector. Granted, there was nothing I could do with those images, since I had just uninstalled that version of Gimp, but none the less, the image types were back.
I am now compiling another fresh download of Gimp from CVS. If the image types (and the resultant ability to edit almost anything at all in the Gimp) are still gone, I will try the same experiment on the missing menu items that I referred to in my original message on this thread. Like I said in my last message on this thread, my original message is full of links to screenshots and output logs from my attempts to compile and install Gimp from CVS.

In closing, I feel the need to clarify that I had a fully functioning installation of Gimp from CVS until this issue with the image types disappearing started. So I most definitely have successfully compiled and installed (and used) Gimp from CVS on this system. The problems actually started right about the time that 2.3.6 was released.

Steven P. Ulrick

On Mon, 2 Jan 2006 16:52:18 -0600 "Steven P. Ulrick" wrote:

Hello, Everyone
I honestly looked as closely at the output while I compiled a fresh copy of Gimp from CVS, as well as the output from the terminal that I started Gimp from:
http://www.afolkey2.net/gimp/01/gimp-2.3CVS-TerminalOutput.txt and I saw nothing that my relatively limited abilities could pick out as a potential starting point for clearing up this problem. For contrast, here is what it looks like when I start gimp 2.3.6 (compiled from the release tarball): http://www.afolkey2.net/gimp/01/gimp-2.3.6Release-TerminalOutput.txt

Further, before I typed this email, I ran "make uninstall" in the gimp from CVS directory, grabbed a fresh copy, re-compiled and ran "make install". Still, same issue.

The problem is, almost all of the image types that Gimp from CVS opened up earlier today (before my latest update from CVS) are gone. I discovered this when I attempted to open up a JPEG image. Here is a screen shot of the file selector dialog to show the lack of image types: http://www.afolkey2.net/gimp/gimp-FileTypes-CVS.jpg

Hello, Everyone :)
Just tried compiling and installing Gimp from CVS from a fresh download, and had the wonderful discovery that this problem has been fixed in CVS.

Steven P. Ulrick