Hello,
although I have activated automatic updates, the updates are not installed by themselves.
The period is set to daily and I have activated everything below.
The update icon has been showing the same updates for over a week now and there are more to come.
What goes wrong here?
BR
Michael
This post misses any real information. Show what you configured. And e.g. which “updates” are not installed.
Remember that we basicaly do not believe what peple say, but what the computer says. Because what people say are mostly conclusions and we want to see the facts where the conclusions are based on. Maybe others come to other conclusions and that is probably one of the main reasons that you ask for help: a new¸ unbiased view on the facts.
What is needed? Which logs or configs?
>zypper se update
| Name | Zusammenfassung | Typ
---+-------------------------------------+--------------------------------------------------------------------+-----------
| FirmwareUpdateKit | Assist with DOS-based firmware updates | Paket
| aacsupdater | Keeps AACS database up-to-date | Paket
| aacsupdater | Keeps AACS database up-to-date | Quellpaket
| aacsupdater-debuginfo | Debug information for package aacsupdater | Paket
| aacsupdater-debugsource | Debug sources for package aacsupdater | Paket
| bs-update | Automate maintenance of packages in a Build Service | Paket
| dns24-update | Simple update client for the dns24.ch DynDNS service | Paket
| etc-update | Configuration file update handler | Paket
| ez-ipupdate | A Small Utility for Updating a Dynamic DNS Service | Paket
| fwupdate | Tools to manage UEFI firmware updates | Paket
| fwupdate-devel | Development headers for libfwup | Paket
| fwupdate-efi | UEFI binaries used by libfwup | Paket
| geoipupdate | GeoIP update client code | Paket
| geoipupdate-legacy | GeoIP Lagacy Format Updater | Paket
| ghc-auto-update | Efficiently run periodic, on-demand actions | Paket
| ghc-auto-update-devel | Haskell auto-update library development files | Paket
i | kconf_update5 | Configuration file access | Paket
| libqrupdate1 | Fortran library for fast updates of QR and Cholesky decompositions | Paket
| package-update-indicator | Package update status notification applet | Paket
| package-update-indicator-lang | Translations for package package-update-indicator | Paket
| patterns-base-update_test | Tests für den Aktualisierungsprozess | Paket
| pk-update-icon | Software Update Notifier based on PackageKit | Paket
| pk-update-icon-lang | Translations for package pk-update-icon | Paket
i | plasma5-pk-updates | Software Update Manager for Plasma | Paket
i | plasma5-pk-updates-lang | Translations for package plasma5-pk-updates | Paket
| qrupdate | Fortran library for fast updates of QR and Cholesky decompositions | Paket
| qrupdate-devel | Development files for qrupdate library | Paket
| qrupdate-static | Static version of qrupdate library | Paket
| transactional-update | Transactional Updates with btrfs and snapshots | Paket
| transactional-update-zypp-config | Zypper rule to prevent uninstallation of transactional-update | Paket
i | translation-update | Translation Updates | Paket
| translation-update-upstream | Tool for Translation Update from Upstream | Paket
i | update-alternatives | Pflege symbolischer Links für Standardkommandos | Paket
| update-bootloader-rpm-macros | RPM macros for update-bootloader | Paket
| update-checker | Scripts to check for new updates and migration targets | Paket
i | update-desktop-files | Ein Entwicklerwerkzeug zum aktualisieren von Desktop-Dateien | Paket
| update-test-32bit-pkg | Test update that contains a 32bit package | Paket
| update-test-32bit-pkg-32bit | Test update that contains a 32bit package | Paket
| update-test-affects-package-manager | Test update that requires a software stack restart | Paket
| update-test-broken | Test update which should not be installable | Paket
| update-test-feature | Test update that includes new features | Paket
| update-test-interactive | Test update that requires confirmation | Paket
| update-test-optional | Test update that is not mandatory | Paket
| update-test-reboot-needed | Test update that requires a system reboot | Paket
| update-test-relogin-suggested | Test update that requires a session restart | Paket
| update-test-retracted | Test update that should be marked as retracted | Paket
| update-test-security | Test update that includes security fixes | Paket
| update-test-trivial | Package for testing the update stack during product development | Paket
| update_test | Tests für den Aktualisierungsprozess | Schema
i | yast2-online-update | YaST Online Update (YOU) Aktualisierungsprogramm | Paket
i+ | yast2-online-update-configuration | Konfiguration vom Online-Update | Paket
i | yast2-online-update-frontend | YaST Online Update (YOU) Aktualisierungsprogramm | Paket
i | yast2-update | YaST2 - Update | Paket
| yast2-update-FACTORY | YaST2 - Update | Paket
| yum-refresh-updatesd | Tell yum-updatesd to check for updates when yum exits | Paket
| yum-updatesd | YUM update notification daemon | Paket
Well, for the configuration take a screen shot of what you confuigred and upload it to https://susepaste.org/
Post the link of the page (not the image) in your post.
Then for your output:
First it is much better to include your prompt-command line before the ouput and also the new prompt line after the output within your copy/post. Then we see exactly what you saw.
Then, when “xypper se update” is realy he command that generated this output, then you should read the documentation
man zypper
The very first line of the description of the zypper search" (or “zypper se”) command says
Search for packages matching any of the given search strings.
So that list is the list of all packages (in the repos your are subscribed to) with names containing the string “update” (and look at those names, they have!). And thus NOT a list of packages that “have Updates”/
You may also have the wrong idea about YaST Online Update. It does install the packages i the Update repos (only two, Update OSS and Update-non-OSS belonging to the standard repos (only two, OSS and non-OSS). These are so called Patches. Thus when you want a list of Patches vailable for a system, read the man page to find out how to list Patches.
And then a personal advise. I would never do any patching or updating “automatic”. Every now and then it maybe a fatal package that is replaced while you are using it. While it is well know that Unix/Linux can survive a lot of this (programs that are loaded from the old file will run and still use that old file until finished), large products can run into problems. The most weel known is the Kernel, where the advice is to reboot asap after updating. But I found out that e.g. Firefox is also prone to malfunctioning until exited and restarted.
Sorry, I misunderstood about the updates.
Actually, I have less updates in the queue today, apparently some were installed.
I don’t know what I did differently now, if I had the updating on “weekly” until recently? I know that I had set it to “weekly” in the beginning.
I installed openSUSE Leap at some friends and family members. Often at the age of 70+.
There I have set automatic updates and hope that it works reliably. Therefore I have installed openSUSE Leap! Of course there is always a residual risk, but if openSUSE Leap disappoints me here, I would generally question GNU/Linux.
So now the main question is, does it work for you as you want or not. That means does your configuration og YOU indeed install Patches (from the Update repos) at the moment and/or the interval you planned?
The above it not quite clear to me from your last post.** If it is not solved**, then please show evidence like I asked above. You have already seen that your conclusion that there were updates in the pipeline was based on a list of all installed and not installed packages with the string “update” in their name. This is a good example why we want to see the facts and not the conclusions.
And about my advice, it is up to you to take the risks, it is just an advice. And this behaviour is not specific for openSUSE, The risk that an update results in a “not working until restarted” program (inclusing the kernel), specialy complicated ones that consist of more files, is the same for all Unix/Linux.
Gotta watch this but I think it’s okay now. Thank you!