Version: 1.9.4 (using KDE 3.5.4, compiled sources) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.18-davidb For whatever reason, restart X, i.e. by control/backspace on an active KDE session with kmail running. Will often come back up with the "another instance running". I choose to start kmail anyway. It starts up just fine, but lo and behold, system is very slow with something eating CPU like mad. Go to top and see two kmail instances. One I just (re-)started and an older one consuming the CPU. It can be safely killed.
*** This bug has been marked as a duplicate of bug 188067 ***
This is not a duplicate of 188067. This bug is related to kde3, the other one to kde4. The symptons are quite different, too.
Hmm, I see the problem that an "head"less instance of kmail is started and not displayed. This is reported to happen when kmail is started by the session manager - as in this case.
Totally different error, because here the session manager got killed and left a kmail instance behind. The other bug talks about a fresh start, nothing killed before, like after a reboot. And the kmail process doesn't eat all the ressources left, but just runs and doesnt display the main window (it's just running in the background and calling kmail manually displays the main window immediately, no loading time, no "another instance running")
Well, do you think in this case a kmail process survived the X restart? Then it would be another bug. I think it is more probable that the running instance of kmail described in this bug has been started by the session manager. In that case it is probable an earlier version of the same bug. The main problem for me is that a kmail process can keep on running after the window has been closed - or can be already running without showing a window. I think all these symptoms are based on the same problem.
In my opinion not. This bugreport talks about a hard reset of the X server. In this case kmail had been running before and it is possible that it hangs (we're talking about a pretty old version of kmail here), because it's still listening on a socket or something. The other bug does appear even if no kmail instance was loaded before, therefore kmail doesn't hang, it's just not showing its main window.
Well, as you wish :) In that case I want to know if the problem still occured with a more recent version of kmail. I haven't seen it.
Me neither. Thanks, I think this is the better solution :)