Getting a message on running Yast2

English Applications
1

I am getting the following message over and over again when I run YaST2:

PackageKit is still running (probably busy).

Ask PackageKit to quit again?

though I am sure there is no such thing running.

2

(Assuming that is on using YaST > Software and not on one of the many other YaST functions).
How can you been sure? How did you check? Do you have the update applet in your desktop or not?

3

Are you sure? Show your logs:

erlangen:~ # journalctl -b -q -o short-monotonic -u packagekit.service 
   13.898002] hofkirchen PackageKit[1516]: daemon start
   13.899055] hofkirchen systemd[1]: Starting PackageKit Daemon...
   13.899628] hofkirchen systemd[1]: Started PackageKit Daemon.
   34.003401] hofkirchen PackageKit[1516]: daemon quit
   34.011850] hofkirchen systemd[1]: packagekit.service: Succeeded.
[41875.704227] hofkirchen PackageKit[14843]: daemon start
[41875.708643] hofkirchen systemd[1]: Starting PackageKit Daemon...
[41875.708972] hofkirchen systemd[1]: Started PackageKit Daemon.
[41892.246811] hofkirchen PackageKit[14843]: get-updates transaction /1_ccbdacad from uid 0 finished with success after 15510ms
[41911.005917] hofkirchen PackageKit[14843]: daemon quit
[41911.052606] hofkirchen systemd[1]: packagekit.service: Succeeded.
erlangen:~ #
4 

som@localhost:~> # journalctl -b -q -o short-monotonic -u packagekit.service
som@localhost:~> su 
Password: 
localhost:/home/som # # journalctl -b -q -o short-monotonic -u packagekit.service
localhost:/home/som #
5

Try YaST2-Services-manager and scroll down to see packagekit and packagekit-background.
If you did a default install you should see the packagekit daemon as Active (Running) which does no harm, and packagekit-background as Active for a few minutes after boot until it has checked whether there are updates to install (which locks other software management applications) and Inactive (Dead) thereafter, when you are able to change software on the system without messing things up.
If you don’t like Package Kit you can disable those services or uninstall PackageKIt and its dependencies altogether.

6

Without the hash # please…

7

Sorry rookie mistake. I am getting this:


localhost:/home/som # journalctl -b -q -o short-monotonic -u packagekit.service
   58.779172] localhost.localdomain systemd[1]: Starting PackageKit Daemon...
   58.888167] localhost.localdomain PackageKit[2303]: daemon start
   59.367588] localhost.localdomain systemd[1]: Started PackageKit Daemon.
   71.267533] localhost.localdomain PackageKit[2303]: uid 1000 is trying to ob>
   71.275324] localhost.localdomain PackageKit[2303]: uid 1000 obtained auth f>
   96.489251] localhost.localdomain PackageKit[2303]: refresh-cache transactio>
   99.335178] localhost.localdomain PackageKit[2303]: resolve transaction /2_e>
   99.341504] localhost.localdomain PackageKit[2303]: resolve transaction /3_a>
   99.348055] localhost.localdomain PackageKit[2303]: resolve transaction /4_c>
 1081.250046] localhost.localdomain PackageKit[2303]: get-updates transaction >
 1081.259537] localhost.localdomain PackageKit[2303]: resolve transaction /6_b>
 1090.001934] localhost.localdomain PackageKit[2303]: daemon quit
 1935.809383] localhost.localdomain systemd[1]: Starting PackageKit Daemon...
 1935.833912] localhost.localdomain PackageKit[4123]: daemon start
 1935.929769] localhost.localdomain systemd[1]: Started PackageKit Daemon.
 1938.136046] localhost.localdomain PackageKit[4123]: resolve transaction /1_e>
 1956.001571] localhost.localdomain PackageKit[4123]: daemon quit
lines 1-17/17 (END)
8

YaST2 seems to be working now. I have one last question. Has the upgrade from beta to stable been implemented automatically or one has to do something about it?

9

The last zypper dup to the released version (and then no zypper dup anymore!).

10

Are there any commands to run?

11

To make it clearer, after Lepa 15.2 is officially released (maybe next Thursday) you have to run

zypper dup

once more, for the last time.
After that the “normal” procedure for updates kicks in, that is by running

zypper up

or using one of the graphical apps you prefer.

12

You can do that already. The GM (gold master) was last Thursday, so the release was frozen at that point. There are already a few updates in the main update repo. Practically speaking, it is already released except for the official celebrations.

13

Hi
And unlocking so it goes out to the mirrors…

14

Yes, I missed that. You cannot yet download the official iso. For people who already have 15.2 installed, or who are upgrading online you can treat it as installed. But if you need the official iso to install 15.2, you still have two days to wait.

15

Sorry I didn’t get dup means duplicate, so OK there’s nothing to do.

16

dup (in the zypper context) means distribution-update.

See

man zypper
17

Done the things, I am all set then, good, thanks everybody for chipping in.