Summary: | KDE hangs at "Starting system services" and does not recover | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Steven P. Ulrick <lists> |
Component: | general | Assignee: | Stephan Kulow <coolo> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | nicolasg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Steven P. Ulrick
2005-07-29 17:08:32 UTC
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. |