Version: SVN BRANCH 3.5 (using KDE Devel) Installed from: Compiled sources Compiler: gcc-3.4.4-2.fc3 OS: Linux How to Reproduce: 1. Set my SVN install of KDE to be "active" in my ~/.bash_profile 2. Log in. 3. Every time I do this, the login hangs at the same point, as described below. Expected Behaviour: 1. Set my SVN install of KDE to be "active" in my ~/.bash_profile 2. Log in sucessfully. I have been having issues logging in to KDE from BRANCH 3.5. What happens is the splash screen hangs at "Starting System Services" Eventually, it will just time out, and the screen goes blank (not black, but some kind of greenish or blueish color) No icons, nothing. I Can do "Ctrl | Alt | <--" and I am (thankfully) immediately taken back to the login screen. Here are the steps that I've gone through to try to get this to work before reported this: 1. Completely fresh install (not an upgrade) of Fedora Core 3. EVERY package chosen, and then fully updated via YUM. The only repositories that I used during the update are the same ones I used when I used to be able to log into KDE: updates released, base, gstreamer, kde-redhat. The install completed with no problems. 2. I completely removed all of my KDE SVN checkouts and redownloaded every one of them. 3. I made sure that the following was in ~/.bash_profile when I built the modules: > export YACC='byacc -d' > QTDIR=/usr/local/qt-src > PATH=$QTDIR/bin:$PATH > MANPATH=$QTDIR/doc/man:$MANPATH > LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH > export QTDIR PATH MANPATH LD_LIBRARY_PATH > > KDEDIR=/usr/local/kde-svn > PATH=$KDEDIR/bin:$PATH > LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH > LIBRARY_PATH=$LD_LIBRARY_PATH > export KDEDIR PATH LD_LIBRARY_PATH LIBRARY_PATH 4. All of the modules that I've installed so far (arts, kdelibs, kdebase - in that order) I've compiled using the following commands: unsermake -f Makefile.cvs ./configure --enable-debug=full --prefix=/usr/local/kde-svn unsermake "su" to root unsermake install All appeared to go well up to this point. 5. Log out, and the try to log back into KDE (with the above QT and KDE paths active in my ~/.bash_profile 6. Result: splash screen still hangs at "Starting System Services" Because compiling KDE from TRUNK (before TRUNK became KDE4) always "just works" for me, I don't have a clue about where to look for any log files that may be of help. There did not appear to be anything of any use in /var/log Just in case there is aything in /var/log that might be of help to you on this, you can see selected contents of that directory here: http://www.afolkey2.net/log My ~/.xsession-errors is located there.
I saw a number of bugs apparently just like this one, spanning about 3-4 years. Those were all resolved, and I saw nothing in any of them that I could do to try to avoid this report. In fact, the well-intended suggestions that were given to the reporters didn't fix it for them, either.
I don't know if this has anything to do with the apparent bug described above, but when I uncomment the lines in my ~/.bash_profile that are quoted above, and do "su - steve" in a terminal window, and then proceed to open, lets say, KRename or Krusader (really, any graphical application that uses mime types), I get an error message about no mime types being installed. This is odd, since I compiled and installed kdelibs and kdebase from fresh downloads from BRANCH 3.5 one right after another. The downloads were done at the same time, as well as the compilation process. I am going to try compiling, unsermake uninstall, then recompiling and installing to see what happens. If this continues, and if you say this is unrelated, let me know and I'll file an appropriate bug report.
Try deleting the ksycoca cache (in your /var/tmp/kdecache-*) and also check that there are no ~/.DCOPserver_* files. Also the sockets in your /tmp/ksocket-* can be a problem. From what I understand, the bug is more or less that KDE at start tries to find a non-existing DCOP server and hangs. (At least that is my experience; I do not know if it is this bug.) Another point: from your description of the bug, you tell that you modify the .bash_profile but that you "log in". As you do not tell that you use "startx", I suppose that you do not log in a shell, so any bash resource file are *not* read. Also be careful when you configure that any $KDEDIR and $KDEDIRS variables do not contradict the prefix that you use. Have a nice day!
Is this still an issue? And if yes, is there anything useful printed on stdout or stderr?
This is no longer an issue. I don't know what (if anything) I did to fix it. Don't even remember how long the issue lasted. But, I am still running KDE from Branch 3.5 (fully updated yesterday) and I can log in perfectly.
Since you were the only one with this issue, and it because it seems to be fixed for you, I'll close this report then.