From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10648 invoked by uid 1002); 9 Nov 2002 12:03:35 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 10625 invoked from network); 9 Nov 2002 12:03:34 -0000 From: Dan Armak Reply-To: danarmak@gentoo.org Organization: Gentoo Technologies, Inc. To: gentoo-dev@gentoo.org Date: Sat, 9 Nov 2002 14:01:26 +0200 User-Agent: KMail/1.5 References: <20021106154847.GA13805@jerry.marcet.dyndns.org> <3DC9C835.4060204@acm.org> <20021107153533.GC24303@jerry.marcet.dyndns.org> In-Reply-To: <20021107153533.GC24303@jerry.marcet.dyndns.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200211091401.27682.danarmak@gentoo.org> Subject: Re: [gentoo-dev] Re: KDE 3.1.0 RC2 still has odd kdm problem X-Archives-Salt: f9be0c5e-c35f-4108-8073-c81f07427c3e X-Archives-Hash: a733e7b97d618ebb638cb4df95f81fb0 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've wanted for some time to switch our kdebase ebuilds from patching/sedding the kdmrc generated by genkdmconf to providing a mostly static one (for tagged kde versions, anyway). This, to more easily incoroporate changes like making it use all the files from /etc/X11/xdm to eliminate this problem. It also makes it easier to throw in nice default settings like aa on by default, maybe a Gentoo logo. AFAICS from a brief perusal of genkdmconf.c, the files it generates only change via #ifdefs on different OSs, and should be the same across all linuxes, and certainly across all Gentoos. The only other case is that lilo support is only enabled by default on x86, but we use grub by default anyway, so I'l probably disable that by default. So, I guess I'll do it now. On Thursday 07 November 2002 17:35, Javier Marcet wrote: > Thanks Oswald and James. You both hit exactly my problem. > As James pointed out kdm was using the config files under > /usr/kde/3.1/share/config/kdm - that's where my kde installation is -, > and just as Oswald guesses there was a problem with Xservers. > > @@ -10,7 +10,7 @@ > # look like: > # XTerminalName:0 foreign > # > -:0 local@tty1 /usr/X11R6/bin/X vt7 > +:0 local /usr/X11R6/bin/X > > ### Don't change these two lines; they are hints for genkdmconf. ### > ### Version 1.99 ### > > Xservers on /etc/X11/xdm, which gdm and xdm were using, didn't force a > vt, while Xservers on /usr/kde/3.1/share/config/kdm forced vt7 which was > already used by a login. > That also explains why I got some garbage on my 7th console whenever I > run kdm. > > Well, given that not forcing a specific vt should always work, it'll > simple switch to the first one available, don't you think it's better to > just remove it altogether, leaving simply a call to /usr/X11R6/binX? In > fact, the reason some build were running fine while others were not, > seems to indicate that Xservers have changed between versions. I'll just > check it now... > > Yes, I checked the other box where beta2 is installed and Xservers on > /usr/.../kdm/ is identical to the one on /etx/X11/xdm. > The installation was done in exactly the same way with all versions, > might it be a difference in genkdmconf which AFAIK generates the kdm > config files? - -- Dan Armak Gentoo Linux developer (KDE) Matan, Israel Public GPG key: http://www.gentoo.org/~danarmak/danarmak-gpg-public.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9zPkXUI2RQ41fiVERAiSLAJ0YKiLuRY6zlUVbIbXGAfGA2IKIrgCdFlzj yjfF22n3Cr+FtFETcTWOaF8= =7V0c -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list