|
Hi, I’ve run into an annoying issue with KDE on
FreeBSD. KDE will not start when the home directory is mounted over NFS
and rpc.lockd is running. I’ve conducted detailed tests that
confirm this. When a user with a NFS mounted home directory attempts to
login through KDM, KDE will hang on the “initializing peripherals” portion
of the splash screen and then the splash screen will disappear and only a kde
(blue) background screen remains. The only way out is a
ctrl-alt-backspace to restart kdm, but the kdeinit processes remain and are
listed as defunct in the process list. It seems to happen when “startkde”
gets to the kcminit stage of the initialization. As I said before, it
only happens when rpc.lockd is running. If I disable rpc.lockd it logs in
just fine. However, any application that requires locking over NFS does
not function properly, particularly openoffice. Open office complains
that it’s component manager isn’t available, which is just a fancy
way of saying that it can’t create a lock on any NFS mounted files.
This wasn’t an issue before I upgraded to FreeBSD 6.0 and KDE 3.5.
Everything worked fine before I upgraded. When I did a fresh install of FreeBSD
6.0, KDE 3.5.1 and qt 3.3.5, I ran into this issue, but could get around it by
deleting the .qt directory in the user’s home directory. But now I have
upgraded to KDE 3.5.2, qt 3.3.6 and deleting the .qt directory doesn’t
work anymore. My only recourse may be downgrading to KDE 3.5.1 and qt
3.3.5, but I would prefer to stay at KDE 3.5.2. Any ideas as to a work around? I would very much
appreciate them. Eric |
_______________________________________________ kde-freebsd mailing list [email protected] http://freebsd.kde.org/mailman/listinfo/kde-freebsd
