KDE Neon Plasma 5.21.4 - daily security updates
 

For several weeks, this has become a regular, almso daily event.

It shows up as security updates and it needs a reboot each time

What is going on?

Thanks
Alex

Need more info about what you are seeing.
What package is showing as needing to be updated?
Did you install and reboot as it asked?

The update each time is the Operating system itself, each time with some 54 packages, 101 or any other number.

It downloads the updates, and asks to reboot, there is nothing I do manually

Please see attached image, just now came up

Any suggestions?

Thanks
Alex

Yes, but did you?

This is a funny question....
Yes of course I did

Cheers
Alex

So are they the same packages each time or different ones?
I like using the command line to update since I can see what is being updated and the version number. You could be seeing lots of minor updates as part of a big update to Plasma and KDE Framework, plus any Ubuntu base updates.

I have not booted up my Neon box for awhile and don't use it much, so I tend to have a ton of updates when I check. I will try to leave it running for few days to see if has similar behavior.

add a picturesThe screen shot I attached yesterday is an example of one day, each time it comes up with another number, I have no idea of what apps are updated.

Attached today's event, same thing but another number of itesm

Thanks again for your time
Alex

I think the suggestion was to try and do the update from the command line instead of thru the updater so you can see what packages are being updated with version numbers. That may ease your concerns about the frequent updates as well as giving you a better feel for what is actually being done.

Needing to reboot with every update is uncommon.

I have in the meantime switched the Updates to Automatic, it was set to Manual and will see what to do next

Have no idea how to run it from command line

Thanks
Alex

Now you have distanced yourself even further from what is happening since you no longer have the chance to even interact with the updates.

Theoretically that is good as long as the distributor is 100% accurate in testing and there are no problems. However, the auto updates without allowing user control is one of the reasons I hate anything microsoft related. With auto updates, if a problem appears you have little chance of ever tracking down the cause since you are totally oblivious to the process.

Good luck in the future.

I wish it was. But the things I've seen here on LQ...
Thanks for answering it anyhow. Always be as precise as possible.

Is the number accumulative?
Maybe there is one thing behind it all that requires manual intervention, and blocks all subsequent updates, and now they're just piling up...
I agree with others, you should do it from the command line to get full control over the process.
Careful though: according to this you should use pkcon and not apt.

Good people, I will try from the command line, if I knew how

Thanks again
Alex

The command if you want to use the command line is:

You also need to open a terminal window to access the command line.
The command given above, when complete needs to be followed by
to finish the update.
That is directly from the linked page in post #12.

I appreciate all the suggestions here, thank you all

Now, back to my story.

I had my two machines (Intel NUC Desktop and a Lenovo Laptop) both with the same OS setup - KDE Neon Plasma 5.21.4. They were both set to "Manual" updates. I switched my desktop to "Automatic" and the "Problem" disappeared.

When I check for updates, it tells me that I am up to date...

Today, I tried running it from the command line manually (on my Lenovo Laptop) using the following command : sudo pkcon update it executed and updated 12, but Discover reported 13 packages. Trying to run again the command, this time with "Upgrade" failed, telling me it is not supported.

I think the "BUG" is in the environment setup FALSE message - it shows they are "Security" updates, where in fact they are not, and why - when I have it set as manual, it asks to reboot, but when I run the command from Terminal, it does not.

Why, for the past 6 months, I was not experiencing this, but for several weeks It came up?

Please see the attached images

Thanks again
Alex