Created attachment 64994 [details] Unexpected behaviour while launching new instance of KDevelop Version: 4.2.2 (using KDE 4.6.5) OS: Linux KDevelop locks the current session. If I try to launch new instance of KDevelop, it displays message box saying that KDevelop failed to lock the session. Then gives up and shuts down. Reproducible: Didn't try Steps to Reproduce: 1) Launch KDevelop 2) Open a session (e.g. X) 3) Launch another instance of kdevelop (from windows manager menu, console, does not matter), but do not use any command line switches 4) Observe message that the session X is already opened and can not be locked Actual Results: See screenshot Expected Results: KDevelop should check if session is already opened. If session is opened, KDevelop should launch with new empty session. In my opinion, that's the behaviour most users would expect.
I agree
Just got the same problem using version: Qt: 4.8.0 KDE Development Platform: 4.8.1 (4.8.1) KDevelop: 4.3.0 I'm not quite sure how I triggered the bug. Now I have no idea where the lock is registered so I'm not sure how to open the session again. I also agree, if I try to open kdevelop and it finds that the "default session" is already opened, my intent is to open an empty (or different) session.
If try to start a new instance of Kdevelop while there is already at least one running using the K-Menu or the context menu in the panel/task bar, the splash screen from Kdevelop appears for a fraction of a second and nothing happens after that.