| 1 |
* Dirk Mueller <mueller@×××.org> [021104 22:43]: |
| 2 |
|
| 3 |
>I've just finished uploading the KDE 3.1.0 RC2 tarballs. |
| 4 |
|
| 5 |
>You can find them at |
| 6 |
|
| 7 |
>ftp://ktown.kde.org/pub/kde/unstable/latest/ |
| 8 |
|
| 9 |
>Download, test, hammer on it, file bugreports against showstoppers on |
| 10 |
|
| 11 |
>http://bugs.kde.org/ |
| 12 |
|
| 13 |
>to ensure that we have a stable release. |
| 14 |
|
| 15 |
|
| 16 |
Using it on my machine, it's getiing better and better. Thankfully last |
| 17 |
big bug in qt-copy is fixed now (the one related to LANG and LC_CTYPE). |
| 18 |
|
| 19 |
Yet I have a strange problem with kdm which shows up and vanishes since |
| 20 |
some post 3.0.x version on cvs. With that I mean that on some |
| 21 |
compilations it works fine while it fails on others. It worked on |
| 22 |
3.1_beta2, but fails on both rc1 and rc2. |
| 23 |
The problem is that using kdm as the X login frontend, my keyboard does |
| 24 |
not work. The mouse does, hence if I enable a pasword-less login I can |
| 25 |
load the whole KDE. However the keyboard won't work either. I cannot |
| 26 |
even Ctrl+Alt+Fx to go a console. The only way is choosing 'Console |
| 27 |
Login' from kdm. |
| 28 |
This does not happen at all if I use xdm or Gnome's gdm. Even if I login |
| 29 |
in a kde session, the keyboard will still work fine. |
| 30 |
|
| 31 |
I've been unable to track this bug down. There were some bigger problems |
| 32 |
with kdm in the past, at least I had them, but it was with cvs HEAD |
| 33 |
versions and at then end it was a font-related problem. |
| 34 |
|
| 35 |
With this on the other hand I don't see anything strange in my logs, |
| 36 |
neither from kernel, from kdm nor from XFree86. |
| 37 |
|
| 38 |
The problem arises whether I try different kernels and X versions. |
| 39 |
Even different hardware, my machine is VIA+AthlonXP+MatroxG400 based but |
| 40 |
I came across it on a IntelBX+PIII+NVidia system. |
| 41 |
|
| 42 |
Both were using Gentoo Linux, though. Which I installed. |
| 43 |
Both use gcc 3.2 and glibc 2.3.1 although it happened with glibc 2.2.5 |
| 44 |
too. |
| 45 |
|
| 46 |
Can anyone shed a light on were the problem might be so I can finally |
| 47 |
track down the bug and get rid of it? |
| 48 |
The first thing I tried and verified was working well was PAM since it |
| 49 |
was the responsible for all the permissions, but I couldn't see any |
| 50 |
problem there. |
| 51 |
|
| 52 |
|
| 53 |
-- |
| 54 |
Javier Marcet <jmarcet@×××××.com> |
Archives