Every time I try to open kdevelop a message appears: “Failed to lock the session , probably it is already active in another running instance”. But there’s no another instance running on my system.
I try to uninstall and install it again and the same result. Any suggestions ?
On 08/05/2012 03:16 PM, agunet74 wrote:
>
> Hi,
>
> Every time I try to open kdevelop a message appears: “Failed to lock
> the session , probably it is already active in another running
> instance”. But there’s no another instance running on my system.
>
> I try to uninstall and install it again and the same result. Any
> suggestions ?
>
> regards,
>
> Agu.
>
>
please mention your operating system and version…
we could guess you use KDE but we know that kdevelop probably will run
in Gnome, LXDE, and others–so please mention your DE and version…
as well tell us how (and from where) you
installed/uninstalled/reinstalled kdevelop…and which version of that
you installed…
and you mention a “failed to lock” message from somewhere…where did
you read the message and can you tell if it came from kdevelop, kde,
some other DE or even the kernel…
when you say no other instance of kdevelope is running, did you get that
from a ps command, or how?
did kdevelop run okay for a while (days, weeks, months?) before it
suddenly wouldn’t start?
and, please type kdevelop in a terminal and copy paste the results back
to here using these insturctions: http://goo.gl/i3wnr
with that info we might be able to find an answer…
On 08/05/2012 05:46 PM, agunet74 wrote:
>
> I’m Using Suse 12.1 , with KDE 4.7.2 “release 5”.
> Kdevelop4 is ron my machine.
>
> And yes, I said from a ps -ef command
>
> Yes, I ran kdevelp for weeks, before this start.
ok…tell us what changed? like maybe:
an update flowed in?
or a hardware change?
some config files edited as root?
or, a crash and a “hard shutdown” with maybe some file system damage…
or a full partition and that resulting crash
hmmmm…i wonder, did you sleep/hibernate the machine and this trouble
started immediately afterwards? have you rebooted since the trouble
began (i ask because i put my 11.4 into hibernate yesterday and some 12
hours later neither the networking or any browser would start (maybe
that a one time prob, i’ll know next time i try to hibernate for 12
hours…not often)
and: since ps -ef confirmed none other is running, let check and see if
there is a lock file in place, and if so delete it:
if ~/.kde4/share/apps/kdevelop/sessions/*/lock
> Result of fdisk:
thanks, but i don’t know why you included that…i didn’t ask for it…i
did, however, ask and didn’t get:
“tell us how you installed/uninstalled/reinstalled kdevelop” [did you
use an rpm command, zypper, YaST Software Management, a 1-Click button]
“which version of that [kdevelop] you installed” (did you install
version 4.2.3, 4.3.0, 4.3.1 (or other), from an openSUSE repo, or maybe
from kdevelop.org (or other)…
“you mention a “failed to lock” message from somewhere…where did
you read that message” (that is, did you see that message in a terminal,
or in a GUI popup? if i knew it was from a terminal i would not have had
to ask the next)
“please type kdevelop in a terminal and copy paste the results back
to here using these instructions: http://goo.gl/i3wnr”
if necessary i can explain why i asked each…but, like the next step
(find/delete a lock file) after learning ps was used would not be
prudent if another session was present but not seen in a GUI tool (in
that case instead of seeking a lock, it would be to just kill the other
instance)