Hi all, Question about the fontconfig programs now being needed by some programs. The latest Gimp build, 1.3.20 complains about fontconfig when trying to start with the standard XFree86 files installed. Although XFree86 includes fontconfig, programs like Gimp are not seeing that without having the fontconfig program installed separate from the XFree86. Correct me if my logic or thoughts are wrong, please. Now I have the fontconfig rpms, but when trying to install them, of course, XFree86 complains, XFree86-devel complains, xf86tools and XFree86-libs. So how does one proceed at this point? Install with a --replacefiles? Rebuild the src XFree86 rpms, altering the spec files not to include fontconfig or? Suggestions, comments welcome! Pat -- --- KMail v1.5.3-3 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
On Tuesday 09 September 2003 08:20 pm, BandiPat wrote:
Hi all,
Question about the fontconfig programs now being needed by some programs. The latest Gimp build, 1.3.20 complains about fontconfig when trying to start with the standard XFree86 files installed. Although XFree86 includes fontconfig, programs like Gimp are not seeing that without having the fontconfig program installed separate from the XFree86. Correct me if my logic or thoughts are wrong, please.
Now I have the fontconfig rpms, but when trying to install them, of course, XFree86 complains, XFree86-devel complains, xf86tools and XFree86-libs.
So how does one proceed at this point? Install with a --replacefiles? Rebuild the src XFree86 rpms, altering the spec files not to include fontconfig or?
Suggestions, comments welcome! Pat -- ================
Answering my own email folks, but seems this is not as big a problem as I thought it might be. When trying to install the separate fontconfig programs manually, several conflicts came up, but I then gave YaST2 a go at it and it wonderfully handled things with no conflicts and now Gimp 1.3.20 works! I think I saw James Ogley's name in the bugzilla about this same thing, where he got the same result. Install fontconfig and Gimp works. Pat -- --- KMail v1.5.3-3 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
Answering my own email folks, but seems this is not as big a problem as I thought it might be. When trying to install the separate fontconfig programs manually, several conflicts came up, but I then gave YaST2 a go at it and it wonderfully handled things with no conflicts and now Gimp 1.3.20 works! I think I saw James Ogley's name in the bugzilla about this same thing, where he got the same result. Install fontconfig and Gimp works.
Don't believe that thee were no conflicts - YaST just didn't tell you about them, it did a forced install, which is what I did. This means that your rpm database is inconsistent, and if you've got the ttf-bitstream-vera package from my site, you may have problems with the Vera fonts, because the fontconfig package will have overwritten the local.conf file from the vera package. It's unlikely this will happen though, as SuSE's fonts.conf file does have support for the Vera fonts I only installed it to test is Sven's theory was correct, I then removed the fontconfig packages, and reapplied the conflicting packages, and resolved to stick with Gimp 1.3.19 until SuSE 9.0 comes out, because I assume that conficting installs like this will cause problems for APT users (Richard feel free to correct me if I'm wrong) Now, if Mike F did XFree86 etc packages to go alongside the fontconfig packages, so you didn't have to force that aspect of the install, and I could remove the local.conf from the vera package to make it all good... ;) James -- James Ogley, Webmaster, Rubber Turnip james@rubberturnip.org.uk http://www.rubberturnip.org.uk Jabber: riggwelter@myjabber.net Using Free Software since 1994, running GNU/Linux (SuSE 8.2). GNOME updates for SuSE: http://www.usr-local-bin.org
On Wednesday 10 September 2003 02:57 am, James Ogley wrote:
Answering my own email folks, but seems this is not as big a problem as I thought it might be. When trying to install the separate fontconfig programs manually, several conflicts came up, but I then gave YaST2 a go at it and it wonderfully handled things with no conflicts and now Gimp 1.3.20 works! I think I saw James Ogley's name in the bugzilla about this same thing, where he got the same result. Install fontconfig and Gimp works.
Don't believe that there were no conflicts - YaST just didn't tell you about them, it did a forced install, which is what I did.
This means that your rpm database is inconsistent, and if you've got the ttf-bitstream-vera package from my site, you may have problems with the Vera fonts, because the fontconfig package will have overwritten the local.conf file from the vera package. It's unlikely this will happen though, as SuSE's fonts.conf file does have support for the Vera fonts
I only installed it to test is Sven's theory was correct, I then removed the fontconfig packages, and reapplied the conflicting packages, and resolved to stick with Gimp 1.3.19 until SuSE 9.0 comes out, because I assume that conficting installs like this will cause problems for APT users (Richard feel free to correct me if I'm wrong)
Now, if Mike F did XFree86 etc packages to go alongside the fontconfig packages, so you didn't have to force that aspect of the install, and I could remove the local.conf from the vera package to make it all good... ;)
James -- ================
James, The fontconfig files seemed to behave after being installed. I check my /etc/fonts/local.conf and it was unchanged with the Bitstream Vera fonts left intact. Normally after doing a --force install, you still get the conflicts messages when you enter the Install/Remove software, but this is not the case, so I am not sure what Mike F. did, but the files seem to have integrated in the system ok. I have not seen any problems yet, but have seen some advantages. Not sure yet if the advantages are good or bad. ;o) I guess one could compile the src rpms for XFree86, XFree86-libs, XFree86-devel and xf86tools, adjust the spec files to not use the old fontconfig, then all would work nicely. Those were the 4 files that complained when I tried installing fontconfig & fontconfig-devel from Mike's site. Side note: I didn't get the Bitstream Vera fonts support until I added or replaced the local.conf file from the fonts package. IIRC, there was no local.conf file in /etc/fonts before I added it. Pat -- --- KMail v1.5.3-3 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
On Tue, 2003-09-09 at 20:20, BandiPat wrote:
Hi all,
Question about the fontconfig programs now being needed by some programs. The latest Gimp build, 1.3.20 complains about fontconfig when trying to start with the standard XFree86 files installed. Although XFree86 includes fontconfig, programs like Gimp are not seeing that without having the fontconfig program installed separate from the XFree86. Correct me if my logic or thoughts are wrong, please.
Now I have the fontconfig rpms, but when trying to install them, of course, XFree86 complains, XFree86-devel complains, xf86tools and XFree86-libs.
<snip> Is this the reason why every time I try and start the new gimp it segfaults when it tries to initialize the fonts??? I got it to compile without errors but it will not start. Just curious. -- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
Hello, Out of the box 8.2 doesn't seem to support the audigy2 - sound only comes out of the headphones socket. So I uninstalled the supplied alsa and installed the latest cvs version (0.9.6) & specified options snd-emu10k1 index=0 extin=0x3fcf extout=0x1fcf in my modules.conf. Wonderfully it all worked! However whenever i try to install any rpms yast complains that dependencies require me to install alsa (the old version) & i have to fiddle about with telling it to never install it. How can i stop it doing this? I couldn't find an rpm of 0.9.6, should i not have uninstalled the old version? Thanks, Robin p.s. it seems to have stopped work suddenly after running suse update, so i guess i'm going to have to do the whole thing again. might be nice if i can do it right this time!
On Wed, 2003-09-10 at 06:09, Robin Marlow wrote:
Hello,
Out of the box 8.2 doesn't seem to support the audigy2 - sound only comes out of the headphones socket. So I uninstalled the supplied alsa and installed the latest cvs version (0.9.6) & specified options snd-emu10k1 index=0 extin=0x3fcf extout=0x1fcf in my modules.conf. Wonderfully it all worked! However whenever i try to install any rpms yast complains that dependencies require me to install alsa (the old version) & i have to fiddle about with telling it to never install it. How can i stop it doing this? I couldn't find an rpm of 0.9.6, should i not have uninstalled the old version?
I have a Audigy2 also. I have got the thing to work with the help of Charles Philip Chan's help. It is on the archives of this list. Worked for me. Also Curtis Rey can be another one that might be able to help. -- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
Is this the reason why every time I try and start the new gimp it segfaults when it tries to initialize the fonts??? I got it to compile without errors but it will not start. Just curious.
Yes. Basically the different versions of fontconfig appear to be API compatible, but not fully ABI compatible. (Based upon next to no research just on the fact that there's no need to recompile ;) ) -- James Ogley, Webmaster, Rubber Turnip james@rubberturnip.org.uk http://www.rubberturnip.org.uk Jabber: riggwelter@myjabber.net Using Free Software since 1994, running GNU/Linux (SuSE 8.2) GNOME updates for SuSE: http://www.usr-local-bin.org
Yes.
Basically the different versions of fontconfig appear to be API compatible, but not fully ABI compatible.
(Based upon next to no research just on the fact that there's no need to recompile ;) )
Thanks! I think I also will stay with 1.3.20 until something can be done. -- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
participants (4)
-
BandiPat -
James Ogley -
Marshall Heartley -
Robin Marlow