I am by no means a KDE expert (while Michael is, so his advice is
certainly more valid than mine). But if you haven't tried this yet,
maybe you could try recompiling KDE with make -DWANT_KDE_DEBUG (kdelibs
and kdebase should suffice) so that you can get some messages that
indicate what's going on. Since you're saying that KDE apps started from
an xterm don't work either, you could load up some random app such as
konsole and see what log messages it spits out. Also, you could run the
app from gdb and see what's going on.
Upgrading to a more recent version of KDE, by the way, is not as bad as
you think it might be. I personally would never run gnome-upgrade.sh
either because I want to be totally in control of what gets installed
and with what flags. After a good look at the script, I figured it
doesn't really do anything smart at all. IIRC, It deletes every port
that depends devel/glib20, does a portupgrade -a on everything that's
left and then reinstalls all the deleted ports. That's it. It just
conveniently keeps a list of the ports to be reinstalled for you. If you
have some more complex GNOME installation with ports that conflict with
the newer ones and such, the script might do something more advanced.
But when simply going from 6.0-RELEASE to current ports, that's all that
should be required. It certainly worked for me that way.
- Bartosz
_______________________________________________
kde-freebsd mailing list
[email protected]
http://freebsd.kde.org/mailman/listinfo/kde-freebsd
