Version: (using KDE 4.3.3) Compiler: sys-devel/gcc: 4.3.4 OS: Linux Installed from: Gentoo Packages Completely new computer w/ clean install from gentoo live CD. everything emerged w/o a problem. Follow all advice and used make.conf defaults. launch /etc/init.d/xdm start KDE4 login screen appears. Accepts password for user Monitor goes black returns to KDE login screen
does a second attempt to log in succeed? if not, please follow the debugging instructions from the kdm README.
(In reply to comment #1) No it never succeeds, it just continues to return to login screen over & over again. The KDM README is of no help as kdm, kdm_greeter work perfect and product no errors (neither does X11). The function perfectly
Created attachment 40958 [details] kdm log
Created attachment 40959 [details] X11 log
and why exactly did you ignore both the hint in the readme and the explicit statement in the log that your system uses syslog? ;)
(In reply to comment #5) > and why exactly did you ignore both the hint in the readme and the explicit > statement in the log that your system uses syslog? ;) Well, I suppose the true reason is that we have ~ 400 systems running KDE3 on Linux of which 10 have just been upgraded to KDE4 w/o any problems and are running perfectly (we are very happy with the new look). And therefore I have never had occasion to read KDM README. This is the first virgin install of Linux and KDE4.3 on a brand new computer and am quite shocked that it has been so much trouble. Would you like to know any more details about our operation or our choices about using syslog or can we move on to fixing this problem? What would you like me to do? Ps I would also be happy to relate to you my experiences of upgrading my laptop to KDE4 w/o problems and the use of syslog while traveling in Europe (which was also a positive experience on many levels) and therefore never had the chance to peruse the KDE README.
the problem is not that you are using syslog, but that by ignoring that fact you provided me with pretty much useless logfiles. ;)
ah, well I have been trying very hard to read your mind, and thought I sensed something about log files, but you must be using your 'Moktar Stealth Haze' so I am afraid you just going to have come out and tell me what is you specifically want.
what's so hard about understanding that when you are using syslog, you have to actually look into the logfiles created via syslog to get useful information out of the system? i mean, one of the files attached *literally* tells you that, right at the top.
nothing at all!
well, then look into it and check whether there are any error messages tagged with kdm. ;) anyway, what you are likely seeing is an instant crash of the session, which would have absolutely nothing to do with kdm. examine the user's ~/.xsession-errors and/or verify whether kdm can start a failsafe session.
As I sure you would have guessed, I opened bug reports in other sites. I was fortunate enough to find someone to resolve this problem. While not as unusual or as interesting to correspond with as you, he was able to immediately articulate exactly what he needed to pinpoint the problem. And quite expert in finding the solution. In any case, thank you for the effort and attempt.
as you might have guessed, most bug reporters actually understand the instructions after being given them in three different ways. ;) anyway, until further notice i'll assume that this is no kdm problem, so luckily someone else will have to deal with it.