When emerging packages depending on libXfont, the following error is returned: bdftopcf: symbol lookup error: /usr/lib/libXfont.so.1: undefined symbol: serverClient This occurs when emerging unifont and konsole. nm /usr/lib/libXfont.so.1 returns: U serverClient I have seen other users with the same error on forums.gentoo.org. Some resolved it by re-emerging bdftopcf or libXfont, while others (myself included) have not had success with this method.
Created attachment 83792 [details] Output of 'emerge --info' I know I am using some unsupported things, but this bug is not isolated - other users are experiencing the same problem.
Created attachment 83793 [details] Output of 'emerge unifont'
Still an issue with 1.1? Please reopen when you reply.
This is not fixed in 1.1.0-r1.
This seems to be a problem of the utility bdftopcf rather than libxfont. I had this problem when compiling kde 3.5.2 with xorg 7.0.0 I bypassed the problem by replacing the binary /usr/bin/bdftopcf with another taken from an older installaton of xorg 6.8.2. Kde-3.5.2 then compiled ok.
I would agree with you, but the unresolved symbol lies in libXfont. nm shows the symbol serverClient to be unresolved in that library. Unfortunately, I don't have a copy of the old bdftopcf handy (I've been using xorg 7.0.0/kde 3.5 for some months now).
This is a symbolic link issue. Look for libXfont.so* files in /usr/lib. There should be a libXfont.so.1.4.1 file, libXfont.so and libXfont.so.1 should be links to that file. On my system, there was also libXfont.so.1.5, and libXfont.so.1 pointed to that file instead. Setting the link correctly made kdebase-3.5.2 compile for me.
libXfont.so.1 was linked to libXfont.so.1.5; fixing the link seems to have cleared the error. Does anyone know where this fix needs to be instituted so that fresh emerges don't duplicate the problem? I don't think the bug should be marked 'resolved' until this issue is addressed.
Also, it appears that after emerging a package that requires libXfont, the link is re-made to the 1.5 library. This occurred after emerging unifont and again after emerging konsole. Is there any harm in removing the libXfont.so.1.5 library altogether?
(In reply to comment #9) > Also, it appears that after emerging a package that requires libXfont, the link > is re-made to the 1.5 library. This occurred after emerging unifont and again > after emerging konsole. Is there any harm in removing the libXfont.so.1.5 > library altogether? > What's the output of 'equery b libXfont.so.1.5'? Equery is part of the 'gentoolkit' package.
'equery b libXfont.so.1.5' returns '[ Searching for file(s) libXfont.so.1.5 in *... ]' but no other output. Also, I tried renaming libXfont.so.1.5 (to *.garbage, in fact), and have not noticed any system instabilities over the last few days. I'm not exactly sure where this broken library came from, but removing it seems harmless to me.
It appears it might be left over from old xorg-x11 versions. I'm assuming you've upgraded from 6.8.2?
(In reply to comment #12) > It appears it might be left over from old xorg-x11 versions. I'm assuming > you've upgraded from 6.8.2? > Yeah, a while ago. Deleting the libXfont.so.1.5 seems to have had no ill effects, so I'm closing this bug.
And what happens if I do not have libXfont-1.4.1.so ? I just have libXfont-1.5. How do I get libXfont-1.4.1.so? I've try recompiling xorg-x11 with no solution.
(In reply to comment #14) > And what happens if I do not have libXfont-1.4.1.so ? I just have libXfont-1.5. > > How do I get libXfont-1.4.1.so? I've try recompiling xorg-x11 with no solution. > I unmerged libXfont and double-checked that all the libXfont*.so files had been removed from /usr/lib (they had). Then I re-emerged libXfont, and it put libXfont-1.4.1.so with proper symlinks in the right place. Try that.
(In reply to comment #15) > (In reply to comment #14) > > And what happens if I do not have libXfont-1.4.1.so ? I just have libXfont-1.5. > > > > How do I get libXfont-1.4.1.so? I've try recompiling xorg-x11 with no solution. > > > > I unmerged libXfont and double-checked that all the libXfont*.so files had been > removed from /usr/lib (they had). Then I re-emerged libXfont, and it put > libXfont-1.4.1.so with proper symlinks in the right place. Try that. > Oh, also make sure that libXfont.so.1.5 is removed from /usr/lib/ before re-emerging.
There are another problem, I can't emerge libXfont without unmask a lot of packages. This is contradictory because I need to unmask a lot of packages in order to emerge the latest stable KDE... Ah, and I forgot to mention that I use xorg-x11 stable (6.8.2-r8). This is the output of emerge libXfont and all the packages that I unmasked: # emerge -pv libXfont These are the packages that would be merged, in order: Calculating dependencies... done! [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-misc/util-macros-1.0.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/xproto-7.0.7) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/fontsproto-2.0.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libXfont-1.1.0-r1) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libfontenc-1.0.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/fontcacheproto-0.1.2) [blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/xtrans-1.0.0-r1) [ebuild N ] x11-misc/util-macros-1.0.2 USE="-debug" 37 kB [ebuild N ] x11-proto/xproto-7.0.7 USE="-debug" 130 kB [ebuild N ] x11-proto/fontsproto-2.0.2 USE="-debug" 44 kB [ebuild N ] x11-libs/libfontenc-1.0.2 USE="-debug" 223 kB [ebuild N ] x11-proto/fontcacheproto-0.1.2 USE="-debug" 37 kB [ebuild N ] x11-libs/xtrans-1.0.0-r1 USE="-debug" 86 kB [ebuild N ] x11-libs/libXfont-1.1.0-r1 USE="ipv6 -debug" 577 kB
What platform are you running on? xorg-x11 7.0-r1 is stable on x86, and has many improvements over 6.x. Basically, 7.0 is far more modular, so the monolithic 6.8 is blocking components needed for 7.0. There are several how-tos for migrating to modular xorg. As far as unmasking, I don't see how unmasking packages for libXfont is contradictory to unmasking packages for KDE. Also, if your portage tree is up to date there shouldn't be any masking issues for packages marked stable; typically masking is used for experimental/untested things (like e17, which will be _very_ cool when it stabilizes). Out of curiosity, what version of KDE are you trying to emerge? Latest stable is 3.5.2, and I don't see any masking issues with it.
You can't install libXfont (a modular X package) and xorg-x11-6.8 at the same time.
*** Bug 139092 has been marked as a duplicate of this bug. ***
I unmerged libXfont, deleted the .15 lib, re-emerged libXfont, checked and the symlinks were OK, re-emerged bdftopcf, but it still gave the same error.
Hi again, bug SOLVED by emerging the latest stable xorg-x11 (7.0-r1). Thanks all.
(In reply to comment #22) > Hi again, bug SOLVED by emerging the latest stable xorg-x11 (7.0-r1). Thanks > all. > Nope, it isn't. I upgraded from 6.8.2 (don't recall the revision right now) right into 7.0-r1 stable, and crashed and burned. Still without a fix... Just to let the devs know, i upgraded xorg-x11 properly. Unmerged the old one, re-emerged xorg-x11, stumbled on this problem, unmerged libXfont, removed old libXfont files, re-emerged libXfont, re-emerged bdftopcf, but the bdftopcf error persists. Perhaps the bug state RESOLVED INVALID should be reconsidered?
Try unmerging libXfont, removing all instances of libXfont*.so, remerging libXfont, check to make sure the symlinks are correct, then remerging bdftopcf.
*** Bug 157604 has been marked as a duplicate of this bug. ***
