When upgrading glibc from 20040808-r1 to 20041102 or 20050125 while running under kdm, KMail will be unable to resolve hostnames after it was restarted. It is necessary to restart X (log out and back in) to restore KMail's ability to resolve hostnames. Other apps (like Firefox and ping) have no problems with resolving hostnames after such a glibc upgrade. Reproducible: Always Steps to Reproduce: 1. Start KMail, and check your mail (^L). 2. Upgrade glibc, to 20041102 or 20050125 (emerge -K =glibc-2.3.4.200.....) 3. Shut down KMail, restart it, and check your mail again. Actual Results: Peng: "Unkown hostname..." Expected Results: Keep on resolving, or tell me to restart X. Gentoo Base System version 1.6.9 Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20050125-r0, 2.6.10 i686) ================================================================= System uname: 2.6.10 i686 AMD Athlon(tm) XP 2800+ Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 8 2005, 12:30:54)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.4.21-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -Os -pipe -fomit-frame-pointer -fstack-protector" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -Os -pipe -fomit-frame-pointer -fstack-protector" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig distlocks notitles sandbox sfperms userpriv usersandbox" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="x86 3dnow X aim alsa apm arts avi berkdb bitmap-fonts cdr crypt curl emboss encode esd fam fbcon flac font-server ftp gdbm gif gpm hardened imagemagick imlib jabber jpeg kde libg++ libwww mad mbox mikmod mime mmx mpeg mysql ncurses nls oggvorbis opengl pam pdflib png python qt quicktime readline sasl sdl slang speex spell sse ssl svga tcltk tiff truetype truetype-fonts type1-fonts unicode xine xml xml2 xmms xsl xv zlib video_cards_via linguas_en linguas_eo linguas_es linguas_nl" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
> Expected Results: > Keep on resolving, or tell me to restart X. Okay, restart X.
This is not a bug but a normal behavior. This is normal as I think that the explanation is that kmail depends on kdelibs for the socket access, so you restarted kmail and it loaded the new glibc libraries, while kdelibs was using the old ones and this created a sort of conflict. Other program not depends on other libs so one time they restarted they work without problems.
> This is not a bug but a normal behavior. Yes, it's normal behaviour. But it's confusing when you don't expect it. Therefore the glibc postinstall messages should tell me to restart X in case I'm running KDE, to avoid this resolving issue.
this applies to more than just KDE, we cant list every app in the ebuild you shouldnt need to restart X, just KDE
