Not a really good start, eh... (YaST stuck and cannot be killed?)

English Applications
#1

So, I decided to give OpenSUSE a new try; it’s running on a Google VM. After trying to configure the firewall through Yast –and disconnecting due to a broken pipe–, seems like something got stuck.

Now when I try to run zypper, I get this error:

System management is locked by the application with pid 1859 (/usr/bin/ruby.ruby2.5).
Close this application before trying again. ```

I tried killing this process, but no SIGINT seems to get rid of it. Any ideas? Thanks in advance!

``` instance-1:/home/usurerocosmico4 # ps ux |grep 1859
root      1859  0.4  3.8 813804 290776 pts/0   Sl+  20:02   0:11 /usr/bin/ruby.ruby2.5 --encoding=utf-8 /usr/lib/YaST2/bin/y2start firewall ncurses -name YaST2 -icon yast
root      3702  0.0  0.0   7680   844 pts/2    S+   20:43   0:00 grep --color=auto 1859 ```
#2

As root in the terminal try

killall y2base
#3

There are other signals like SIGKILL.

#4 
**erlangen:~ #** **zypper if jalbum** 
System management is locked by the application with pid 29636 (/usr/bin/ruby.ruby3.1).
Close this application before trying again.
**erlangen:~ #** **kill 29636** 
**erlangen:~ #** zypper if jalbum 
System management is locked by the application with pid 29636 (/usr/bin/ruby.ruby3.1).
Close this application before trying again.
**erlangen:~ #** **kill -9 29636** 
**erlangen:~ #** **zypper if jalbum** 
Loading repository data... 
Reading installed packages... 


Information for package jalbum: 
------------------------------- 
Repository     : jalbum 
Name           : jalbum 
Version        : 28.1-1 
Arch           : x86_64 
Vendor         :  
Installed Size : 304.4 MiB 
Installed      : Yes 
Status         : up-to-date 
Source package : jalbum-28.1-1. 
Summary        :  
Description    :  

**erlangen:~ #**
#5

Yep, this is exactly what I tried, -9 and -11 but still no good results. Oh well, just wanted to learn what to do in such cases. I don’t really remember the last time a *NIX system refused to kill a task lol!

I had to reboot the machine anyway, so I guess I will have to see if it happens again. I hoped to find the issue persisting, but that was not the case sadly.

Thanks everyone for the awesome support though!

#6

IMHO you should not try to kill without knowing what you are going to kill. You should try to find out which other software management program is running that blocks your invocation of zypper.

Looks that you have YaST > Software > Software Management also running? Then stop it.

You can not run several programs doing openSUSE software managemnt at the same time (like zypper, YaST > Software Managemnt, PackageKit e.g. through the applet in some desktop). All are based on libzypp and that will avoid contradictory actions by allowing only one partner active at a time.