On Saturday, March 19th 2005 23:33 BandiPat wrote:
On Saturday 19 March 2005 03:36 pm, Vadym Krevs wrote:
Hmm, neither of the solutions discussed below work for me. I've upgraded to KDE 3.4 on two machines running Suse 9.2 Professional. Both machines had KDE 3.3.4 previously. Upgrade was performed via Yast2.
On one machine KDE works like a treat after the upgrade. No issues with arts or KDM, On another, no user can login via KDM - neither normal nor root - just like described below. Although starting X via "startx" works for any user. After some playing with the KDE startup scripts on the first machine, I've determined that the problem occurs on like 242 of /opt/kde3/bin/startkde:
LD_BIND_NOW=true kdeinit +kcminit
[...] ************
Have you tried running "/opt/kde3/bin/genkdmconfig" to generate a new kdmrc file/s? It sounds as if that might be your last resort. Leave the LD_BIND_NOW line alone, that's not causing you any grief to be sure.
Hi, I wrote "kdeint +knotify" between test -n "$KDEWM" && KDEWM=3D"--windowmanager $KDEWM" kwrapper ksmserver $KDEWM and it works (Well, it´s dirty too). Someone in the German suse-multimedia list wrote, that it is necessary for this method that in ~/.kde/share/config/knotifyrc the following things must be set Arts Init=3Dtrue KNotify Init=3Dtrue Use Arts=3Dtrue=20 bye René