When yast2 in another session didn’t fully terminate…
Posted by jpluimers on 2014/01/26
Sometimes you get this when starting yast2:
System management is locked by the application with pid #### (@@@@@@).
Close this application before trying again.
This means another yast2 process with pid #### and name @@@@@@ is active, or hasn’t shut down properly.
@@@@@@ usually equals /usr/lib/YaST2/bin/y2base or /usr/sbin/packagekitd.
First, view what the process is about by issusing this ps command that shows you a bit more context around the single pid ####:
ps afup ####
Then kill it by pid if it is the right one:
kill ####
If that doesn’t help, evaporate it by sending it the SIGKILL (9) signal:
kill -9 ####
–jeroen
via: linux – System Management is locked by … packagekitd – Super User.
The Wiert Corner - irregular stream of stuff 
Leave a comment