Just FYI, I had the same sort if problem after upgrading konqueror to unstable on a "mixed" system. It turned out that in my case, the reason was that there were still old "kdeinit4: ..." processes running, even though I had exited konqueror, and after killing those processes manually everything worked fine.
Maybe that information helps someone else stuck with the same problem. Two suggestions: 1) One the "Unexpected Program Termination" page, include information that more information may be found in .xsession-errors. I found that hinted at after some googling, and it contained the line symbol lookup error: /usr/lib/kde4/kio_http.so: undefined symbol: _ZN6KDebug13hasNullOutputE9QtMsgTypebib which in turn lead me to the two versions of libkdecore.so, and apparently the running kdeinit4 used the wrong one when launching the http-process. The information currently given on that page isn't particularly helpful when trying to pin down the error. 2) Consider removing and/or restarting the kdeinit4-processes as part of the upgrade process, if at all safely possible. -- Dirk Thierbach <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
