[gentoo-dev] Re: KDE 3.1.0 RC2 still has odd kdm problem

[gentoo-dev] Re: KDE 3.1.0 RC2 still has odd kdm problem

[Javier Marcet]

[-- Attachment #1: Type: text/plain, Size: 2129 bytes --]

* Dirk Mueller <mueller@kde.org> [021104 22:43]:

>I've just finished uploading the KDE 3.1.0 RC2 tarballs. 

>You can find them at

>ftp://ktown.kde.org/pub/kde/unstable/latest/

>Download, test, hammer on it, file bugreports against showstoppers on 

>http://bugs.kde.org/

>to ensure that we have a stable release. 


Using it on my machine, it's getiing better and better. Thankfully last
big bug in qt-copy is fixed now (the one related to LANG and LC_CTYPE).

Yet I have a strange problem with kdm which shows up and vanishes since
some post 3.0.x version on cvs. With that I mean that on some
compilations it works fine while it fails on others. It worked on
3.1_beta2, but fails on both rc1 and rc2.
The problem is that using kdm as the X login frontend, my keyboard does
not work. The mouse does, hence if I enable a pasword-less login I can
load the whole KDE. However the keyboard won't work either. I cannot
even Ctrl+Alt+Fx to go a console. The only way is choosing 'Console
Login' from kdm.
This does not happen at all if I use xdm or Gnome's gdm. Even if I login
in a kde session, the keyboard will still work fine.

I've been unable to track this bug down. There were some bigger problems
with kdm in the past, at least I had them, but it was with cvs HEAD
versions and at then end it was a font-related problem.

With this on the other hand I don't see anything strange in my logs,
neither from kernel, from kdm nor from XFree86.

The problem arises whether I try different kernels and X versions.
Even different hardware, my machine is VIA+AthlonXP+MatroxG400 based but
I came across it on a IntelBX+PIII+NVidia system.

Both were using Gentoo Linux, though. Which I installed.
Both use gcc 3.2 and glibc 2.3.1 although it happened with glibc 2.2.5
too.

Can anyone shed a light on were the problem might be so I can finally
track down the bug and get rid of it?
The first thing I tried and verified was working well was PAM since it
was the responsible for all the permissions, but I couldn't see any
problem there.


-- 
Javier Marcet <jmarcet@pobox.com>

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

[gentoo-dev] Re: KDE 3.1.0 RC2 still has odd kdm problem

[Javier Marcet]

[-- Attachment #1: Type: text/plain, Size: 2246 bytes --]

* James Richard Tyrer <tyrerj@acm.org> [021107 02:57]:

>>Can anyone shed a light on were the problem might be so I can finally
>>track down the bug and get rid of it?
>>The first thing I tried and verified was working well was PAM since it
>>was the responsible for all the permissions, but I couldn't see any
>>problem there.

>Wild Guess department:

>Are you using the same configuration files when you use KDM as when you 
>use GDM:

>	Xservers
>	Xwilling
>	Xaccess
>	Xsetup
>	Xreset
>	Xresources
>	Xstartup

>With KDE from source, they are by default in:
	
>	/usr/kde3/share/config/kdm/

>I had some problems with Xsession, but it couldn't be your problem 
>because it isn't called until after you login.  Some of the others are 
>irrelevant for the same reason.

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?


-- 
Javier Marcet <jmarcet@pobox.com>

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-dev] Re: KDE 3.1.0 RC2 still has odd kdm problem

[Dan Armak]

-----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