I wrote:
> walt writes:
> > What I do when faced with an X problem is to type "X" at a console
> > prompt and see if the bare X server starts up normally, i.e. with the
> > black-and- white background pattern and the x-cursor. That at least
> > will separate the kde bugs from the xorg bugs.
>
> Yeah, that's what I did.
And that was the problem. I am pretty sure this just CANNOT be, but X runs
fine if I start it via startx or KDM. I think even if the checkerboard X
background I am used is no longer there, I should at least have seen the
mouse, but, whatever.
Oh, when I start X with fglrx in xorg.conf then, I get a blank screen again,
but the keyboard hangs, I have to to the Alt-SysRq-R trick to go back to a
text console. But that is also blank, the 'textmode' does not help, and I
have to reboot. But vesa or radeonhd seem to work, at least.
> I am not sure how the KDE upgrade went, all I can say yet is that using
> kontact on that machine right now via vnc works.
It did not work well. I cannot start any WM with KDM, after half a second
KDM just restarts. I had this before already, but I thought it was related
to the new ati drivers which I do not use now. XSESSION=kde-4.3 startx works
though.
But my desktop/session is a mess. Windows have no title bar or border, the
panel is cleared off most things, and such. I renamed ~/.kde4.2 to ~/.kde4
before that. But then I cannot start kmail, because it wants to write into
~/.kde4.2/share/appes/kmail/.
Should I start from scratch? Probably yes. I guess this problem comes from
switching from +kreprefix to -kdeprefix.
Wonko
