BioTube wrote:Is xterm installed? It doesn't seem to be included by default anymore, so it might be your session's closing when there's nothing to run.
I agree with your point that if xterm
(or whatever the failsafe login tries to run) is missing then the session would close immediately and that would explain what I am seeing. I can 't say whether xterm
was installed originally but I did succeed in starting a twm
session and created an xterm
from there and think that was before I installed any extra packages whatsoever. In any case, xterm
is certainly installed now and it makes no difference. I installed xdm
and found I could get to an xterm
based failsafe session that way. I switched back to kdm
and I'm back to square 1.
BioTube wrote:As for "failing safe", X should default to vesa or fbdev, both of which are generic drivers guaranteed to work on almost all hardware.
Your statement makes perfect sense to me but that is not what I observed. I started by asking if anyone knew what should happen. There is no point submitting a bug report that is so far from the mark it just gets ignored.
I got into this mess by upgrading lenny to squeeze on a machine with a SIS graphics chip set. It seems the (squeeze) sis driver crashes when a KDE session is closed. After the upgrade, for reasons unknown, the KDM greeter was set to failsafe session. So the first time I attempted to log in the session closed immediately and the X server crashed. This same thing happen with the upgrade of two more machines and it seemed to me KDE was very, very broken. Only when I thought I'll try a failsafe session did I discover that failsafe seemed to be part of the problem.
Now I'm looking into this problem using a machine with an Intel graphics chip set and there is no crash when a KDE session is closed: starting a failsafe session simply returns me to the login screen. If failsafe mode were using vesa
then I would expect behaviour on the Intel machine to be the same as one the SIS machines (but I'm no expert).
schmidtbag wrote:at this point would it really matter?
To those who know what they are doing, perhaps not, which is why such issues don't get fixed. To someone like myself, so long as I learn something from looking at the problem, it's fine. If I was not interested in learning I might still be using a commercial operating system. To a newbie, what I experienced would be enough for them to submit a bug report that would get laughed and that would be enough to persuade them to go elsewhere.
schmidtbag wrote:from a command line, you can easily modify your xorg.conf via nano and just run "startx" from there
See ... I've learnt something useful. Thank you very much for the tip.
schmidtbag wrote:i'm switching to arch
Perhaps Debian is not the best distribution for KDE fans. In which case, I'm definitely posting in the wrong forum !
If I changed distribution every time something went wrong I'd be installing a new one every week. I might even be trying the Great Brown distribution again. Good grief !