As of Gnome 2.4, it seems the Pango library is slotted. On my system I have both version 1.2.3 and 1.2.5 installed. According to a bug in Dia and/or Pango, Dia 0.91 is not compatible with pango 1.2.4+, causing various font problems: http://bugzilla.gnome.org/show_bug.cgi?id=123430 I've had such font problems since updating Gnome to 2.4, and currently don't get any fonts in Dia at all. However, the Dia ebuild partly seems to "be aware" of the problem, as the following dependency is present: DEPEND=">=x11-libs/gtk+-2.0.0 <=x11-libs/pango-1.2.3 ... Now, checking the shared libraries used by my running Dia process I found this: #>grep libpango- /proc/27007/maps 406b8000-406df000 r-xp 00000000 03:03 424776 /usr/lib/libpango-1.0.so.0.200.5 406df000-406eb000 rw-p 00026000 03:03 424776 /usr/lib/libpango-1.0.so.0.200.5 So, it seems that Dia is actually using the pango 1.2.5 shared libaries instead of the 1.2.3 shared libraries. I guess this is due to the slotting of the Pango library not being present when writing the Dia ebuild. I assume that the ebuild needs to be rectified to link to the correct ....200.3 versions of the Pango shared libraries. There is also a relevant discussion in the forums: http://forums.gentoo.org/viewtopic.php?t=84617 Reproducible: Always Steps to Reproduce: Actual Results: Due to this problem (probably), no fonts are visible in my Dia installation. Expected Results: Obviously, the fonts should be seen. Portage 2.0.49-r3 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-gentoo-r7)================================================================= System uname: 2.4.20-gentoo-r7 i686 Intel(R) Celeron(R) CPU 2.00GHz ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium2 -frerun-cse-after-loop -frerun-loop-opt -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /opt/tomcat/conf /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -march=pentium2 -frerun-cse-after-loop -frerun-loop-opt -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache fixpackages sandbox userpriv" GENTOO_MIRRORS="http://gentoo.linux.no/ http://trumpetti.atm.tut.fi/gentoo/ http://gentoo.oregonstate.edu" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 apm encode foomaticdb jpeg libg++ mad mikmod mmx ncurses nls quicktime xml2 xmms zlib gtkhtml gdbm berkdb slang readline tetex bonobo tcltk guile mysql sdl gpm tcpd pam libwww ssl perl python esd imlib motif opengl cdr apache2 avi cups dga doc emacs evo gnome gif gtk innodb java mozilla mozsvg mpeg oggvorbis oss pdflib pic png samba sis spell sse truetype usb X xv -alsa -arts -crypt -kde -svga -qt"
I've just verified that this is indeed the cause of my font problem in Dia. It can be demonstrated by testing Dia with the normal Pango installled, and then doing: emerge =pango-1.2.3 After that, Dia displays fonts just as it was supposed to.
On more careful consideration, looks like the Pango library isn't slotted at all. But how come that I got both version 1.2.3 and 1.2.5 installed after updating to Gnome 2.4. Indeed, if I now do "emerge -upv --deep dia gnome" it suggests updating Pango to 1.2.5, without showing the blocker that Dia should cause with Pango >= 1.2.4... Is this really a Portage or Pango bug?
The ebuilds did get reslotted. This shouldn't be a problem, only the pango problem with fonts turned up. Just remove the other pango directly or alltogether first if you have problems, but you already did that so it shouldnt be a problem anymore. The problem you describe is not portage but probably the suggested order of your emerge, the gnome part doesn't know about dia, dia is fine with the pango as it is and only after that gnome updates it to .5 .
Not quite sure I understood that answer completely. I now have this situation: * Gnome 2.4 requires Pango 1.2.5 * Dia 0.91 requires Pango < 1.2.4 or no fonts show at all So, isn't this a bug? At least Pango 1.2.5 should be considered unstable, or a similar solution. Dia 0.92 will be fixed in this respect. Also, have a look at bug #30663 which is another problem that is also caused by Pango 1.2.5.
i dont see it as one, afaik the problem is the dia usage of pango, not pango itsself. Same may be true for gdm, although i don't see that behaviour. About the deps i can't do much, they are correct in both cases : the gnome meta package just follows the release verions and i have little reason to believe pango is the problem (see up). That these two things conflict is unfortunate, but the number of gnome meta users is far greater than the number of dia users, so the last group has a bit of bad luck in this. But we could probably up the dia versions soon to one of the prereleases, although i'm not a big fan of these practices ;) Or someone could maybe extract the relevant pango patching for dia from CVS to use adapt to 0.91
Ok, I understand the reasoning. It is just so hard to be part of a minority... ;-) Maybe I also misread the Gnome Dia bug a bit. It seemed like the error was in Pango, but reading carefully between the lines it is possible that the problem was actually in Dia. (Oh, we developers, never admitting a bug to be ours...) http://bugzilla.gnome.org/show_bug.cgi?id=123430 Anyway, I'll see if I can make contact with the Dia developers about this. I'll get annoying again if I find a smoother solution.
well, dia-0.92_pre4 is now in portage. that should solve the pango dilema for the moment.
