From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510 Galeon/1.3.13 Description of problem: Whenever I try to start KDE, I get the following error in my ~/.xession-error file. This happens for all users on the system: /etc/X11/xdm/Xsession: line 55: [: too many arguments XIM DEBUG: xset: bad font path element (#96), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax startkde: Starting up... ksplash: error while loading shared libraries: /usr/lib/qt-3.3/lib/libqt-mt.so.3: undefined symbol: XkbSetPerClientControls kdeinit: error while loading shared libraries: /usr/lib/qt-3.3/lib/libqt-mt.so.3: undefined symbol: XkbSetPerClientControls startkde: Could not start kdeinit. Check your installation. xmessage: error while loading shared libraries: /usr/X11R6/lib/libXaw.so.7: undefined symbol: XmuCvtGravityToString Warning: connect() failed: : No such file or directory ksmserver: error while loading shared libraries: /usr/lib/qt-3.3/lib/libqt-mt.so.3: undefined symbol: XkbSetPerClientControls startkde: Shutting down... Warning: connect() failed: : No such file or directory Error: Can't contact kdeinit! startkde: Running shutdown scripts... startkde: Done. The correct version of qt is installd for FC2, along with the xorg-libs package. No KDE app will start. GNOME will start up just fine. When trying to start xterm in failsafe mode (run level 5), I get the following: xterm: error while loading shared libraries: /usr/X11R6/lib/libXaw.so.7: undefined symbol: XmuCvtGravityToString I'm guessing that there's a package that needs to be installed that failed to install. Version-Release number of selected component (if applicable): kdebase-3.2.2-4 How reproducible: Always Steps to Reproduce: 1. Start KDE with startx 2. 3. Actual Results: X will start up, but then will crash with the above Expected Results: KDE should have started up. Additional info: I'm suspecting that a package may not have installed correctly. When I did my upgrade to FC2, the anaconda installer froze, and I had to reboot my system. It got stuck on the e2progs-devel program. After I restarted the upgrade, anaconda was able to pick up where it left off, but it may not have upgraded/installed all the packages that are needed. apt-get reported no broken packages though.
yes, it looks like that many packages are not correctly upgraded on your machine! First you have to find out which packages are not correctly installed and then upgrade them with --force. anyway it's not a bug in KDE
Created attachment 100407 [details] Upgrade log that was created before anaconda froze This was the first upgrade log that was created before the anaconda installer froze and hung the machine.
Created attachment 100408 [details] This is the second upgrade log This is the upgrade log that was created after I had to reboot the machine.
as i have said before, there are some packages, which have not been correctly installed on your machine. That caused this problem. to fix this problem, first you have to find out which packages are not correctly installed and then upgrade them with --force. for example: xorg.x11 and all qt/KDE packages if anaconda froze on your machine, it's a anaconda bug, but not KDE!