After emerging the particular version of xfree, neither kdm nor xdm worked anymore. Re-emerging kde-libs and kdebase didn't help. My platform is amd64, I don't know if this bug applies to other platforms as well.
Neither kdm nor xdm write anything to their log files "/var/log/?dm.log"
Does anything show up on the console when starting a *dm? Also, not using a *dm works fine right (i.e., just startx)?
nothing at all happens when you run kdm or xdm it just immediately returns, no change in console, no sign of it starting X using 'startx' works fine, yes. my theory is a config change, I'll let you know in a few (going to use the 4.3.0 config with 4.3.99) -Brad
ok /etc/X11/xdm/Xservers is the culprit For some reason, the 4.3.99.902 config comments out that last line, so what it distributes looks like this : # :0 local /usr/X11R6/bin/X but should be: :0 local /usr/X11R6/bin/X I guess we need to fix this in the e-build ?? Possibly a sed statement like this: sed -i -e 's/# :0/:0/' Xservers -Brad
It's not commented out for me. Same version etc. Is it on all AMD64's?
maybe it is specific to amd64 ?? don't know enough about the build process, etc .... but yes, it does appear all amd64's are affected, I kinda assumed other arches would be too ... Note it only happens if you blindly do a etc-update with -5 because you're too lazy to merge the 120 or so changes :/ I would have caught this the first time around otherwise. -Brad
Hm, same here. Fortunately I read this bug while emerging: Beginning of differences between /etc/X11/xdm/Xservers and /etc/X11/xdm/._cfg0000_Xservers --- /etc/X11/xdm/Xservers 2004-01-16 09:38:35.000000000 +0100 +++ /etc/X11/xdm/._cfg0000_Xservers 2004-01-16 01:18:43.000000000 +0100 @@ -10,4 +10,4 @@ # look like: # XTerminalName:0 foreign # -:0 local /usr/X11R6/bin/X -dpi 100 +# :0 local /usr/X11R6/bin/X End of differences between /etc/X11/xdm/Xservers and /etc/X11/xdm/._cfg0000_Xservers emerge info: Portage 2.0.49-r20 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.6.1-rc3-gentoo) ================================================================= System uname: 2.6.1-rc3-gentoo i686 Intel(R) Pentium(R) M processor 1400MHz Gentoo Base System version 1.4.3.10 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ http://mirrors.sec.informatik.tu-darmstadt.de/gentoo http://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo ftp://ibiblio.org/pub/Linux/distributions/gentoo/ http://www.gtlib.cc.gatech.edu/pub/gentoo " 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="X Xaw3d aalib acl acpi acpi4linux alsa apache2 apm arts autofs avi berkdb caps cdr clamav crypt cups curl dga dillo directfb dnd doc dv dvd encode esd ethereal etwin fam fbcon foomaticdb gdbm ggi gif gnome gphoto2 gtk gtk2 guile imagemagick imap imlib imlib2 ipv6 irda irmc java javascript jikes jpeg kde ldap libg++ libwww mad maildir matroska md5sum mikmod mmx mng motif mozilla mpeg mysql ncurses nls nocardbus offensive oggvorbis openal opengl oss pam pcap pcmcia pdflib perl pic plotutils png pnp postgres ppds pwdb python qt quicktime radeon readline samba scanner sdl slang snmp spell sse ssl svga tcltk tcpd tetex tiff transcode truetype uml usb v4l vim-with-x wxwin wxwindows x86 xface xine xml2 xmms xosd xv xvid zlib"
Well this is caused by patch: 7500_s390_4.0.1-nohardware.patch I have no idea where this patch came from but its applied in a general sense when according to naming convention it should only be applied for arch s390. This appears to be the case across all the xfree ebuilds currently ?? In futherance I just found out there currently isnt even a s390 profile for Gentoo, unless someone has an objection will move this patch to excluded/ ?? Anyone?
There will probably be soon, port's in progress. Not sure exactly what it's gonna be called though. BTW Andrew, you clearly aren't looking at the latest patchset, because all patches were renamed to apply all the time unless they break things for other arches. 7500_all_4.0.1-s390-nohardware.patch is current name. PATCH_VER=0.3. Anyway, excluding for now is fine.
OK just committed changes to all the ebuilds effected by this patch. Simple fix is to just uncomment the line; but if you feel the need remerge your version of xfree. Marking as FIXED.
