KDevelop "failed to lock session" after crash

Question

My machine crashed with KDevelop running, and after rebooting it won't start, saying:

Failed to lock the session, probably it is already active in another running instance

However I definitely do not have it running anywhere.

How can I clear up whatever kind of lock it created and failed to clean up after itself?

score 1 · Accepted Answer · answered Jul 07 '13 at 21:13

1

You can manually remove any KDevelop lock files via:

sudo rm ~/.kde/share/apps/kdevelop/sessions/*/lock

answered Jul 07 '13 at 21:13

Drew Noakes

In recent versions (KDE 5) the location might have changed to `~/.local/share/kdevelop/sessions/*/lock`, at least based on what I'm seeing on my non-Ubuntu system. Maybe someone else can check this on Ubuntu. – David Z Jun 28 '20 at 22:40

score 1 · Answer 2 · answered Jul 26 '17 at 12:52

1

The accepted answer did nothing for me, however I didn't reboot my PC to try to fix the problem.

What worked for me was this:

killall -9 kdevelop

After killing all instances of kdevelop, I could start it again, and pick a session.

answered Jul 26 '17 at 12:52

BЈовић

2 Answers2