Why don’t updates for Tumbleweed show up in Yast like they do in Leap.

There are no updates in Tumbleweed (well unless it’s an important one and placed in the Update repository), you should only be using zypper and dup, nothing else…

Yast online update is looking for patches. A patch is a special kind of file with update directions. The patches appear in the update repo.

Already, even using Leap, some updates don’t show up in Yast Only Update, because they are not patches. For Leap, these are mostly the packman updates.

Tumbleweed, because it is a rolling distribution, has to be handled differently. Using “zypper dup” makes it more of an upgrade to the next version of the rolling release, rather than an update to the current version.

I was inspired to write an article.


FWIW: Integration of ‘dup’ in packagekit is in progress. Won’t be in YaST though, since that is zypp based, not packagekit based like the plasmoid.

Ok. Thanks. That’s interesting.

I was aware of zypper dup and it had occurred to me that a gui version might be convenient.

I personaly doubt if that is a good idea. Because a zypper dup will install a new version of many packages, a lot of people prefer to have running as few processes as possible during that upgrade. Thus no GUI at all, but from run level 1.

You’ve got me curious.

Zypper tells us when a reboot is actually required; although, I’ve always rebooted anyhow.

What is the situation where a reboot is not required, but logging out of the desktop environment and switching to tty1, and then upgrading is not sufficient – i.e. it will also require switching to “run level 1” (i.e. rescue.target)](https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.systemd.html#sec.boot.systemd.boot) to avoid a problem when switching back to the login manager / desktop environment?

Or zypper ps -s, may just need to logout/login to restart processes…

What are the benefits of login out and login in as root, rather than simply doing

sudo zypper dup

Nothing related to the desktop environment can freeze or die in the middle of the upgrade.

If you want to avoid a reboot, then you want to make sure newly installed/upgraded packages aren’t going to try to use or interact with already loaded outdated processes or services. You can take it further and isolate the “rescue.target” as suggested by hcvv; although, I’m not clear on when that is needed (hence my question). Regardless, it’s the state where the fewest things are loaded, and will therefore be reloaded when switching back to “graphical.target”.

sudo IS a way of logging in as root.

It depends on the task, the circumstances and one’s personal preferences what one wants to use.

I do not run Tumbleweed, but I compare upgrading Tumbleweed with upgrading from e.g. openSUSE 15.0 to 15.1 (by changing the repo URLs and then doing zypper dup).

And I would do that by going into rescue.target (run level 1), loging in as root (an exception to the rule “never to log in directly as root”, but hey, in resque there aren’t much possiblities for others to see the password, when you look first over your shoulders). Then I would do the zypper dup (after changing the repos in the Leap upgrade case) and do a reboot because in the Leap upgrade case there would be a new kernel.

For less intruding tasks to be done by root, I would normaly use (using KDE) the “Terminal in Super User Mode” from the starter menu, which is the same as using Konsole and typing

su -

I never use sudo.
And of course I use YaST, which will also “go into Super User Mode” or " become root" or what ever popular expression you want to use for it.

And yes, as explained by others above, what is the use of running such a major upgrade from the GUI with Desktop where you are sure that many components of that same GUI/Desktop will be replaced when running? Linux is very forgivinf when replacing files in use by other files, but there is always the possibility that you are still using an old file, that then asks later for a new file (some library?) that then is already replaced and may be incompatible.

What you wrote I read as saying you would be performing a dup whilst in a target that hasn’t started networking. Have I misread? https://en.wikipedia.org/wiki/Runlevel#Linux_Standard_Base_specification

I always do my dups in multi-user.target, and usually do ups there too. I keep deltarpm uninstalled, and haven’t used yast for updating since around the time SuSE birthed openSUSE.

Run level 3 is multi-user.target is no GUI.
I assume run level 2 on openSUSE is multi-user no network, but I do not think I have a use for it. Either 1 or 3, or mostly 1 (for maintanace only) or 5 (for normal operation)…
Run level 1 is single user. no network is rescue.target.

Note you may not have Network up when logging to a terminal if you are wireless and have nt set Network Manager to allow other users. Since NM does not start by default until the user configuring it logs in.


Do you know the Tumbleweed Updater plasmoid for KDE? I discovered this plasmoid a month ago and published on it in https://www.alionet.org/content.php?889-Tumbleweed-Updater-un-plasmoid-pour-KDE-en-alternative-au-zypper-dup-en-console

You can find more information about Tumbleweed Updater in developper’s homepage:



This plasmoid does NOT use PackageKit to install the updates but zypper (it’s a kind of graphic frontend for the zypper dup command). I’ve been using it on Tumbleweed for a month now. It’s an alternative (not a total replacement) to zypper dup in terminal.

I like to know that I can use one of these 2 methods to do the updates, according to my personal choice.

Actually a patch is not necessarily the same as and might be considered a subset of updates.
Updating will replace with something newer, possibly a newer version with new features, not just critical fixes (usually security).
Patching only installs critical fixes and will not generally improve the performance and features of what is being replaced.

Although updating is recommended for practically everyone, those who maintain mission critical applications which run fine on currently installed versions of components, will not likely benefit from any non-critical improvements and put a premium on reliability will want to patch only.

And, accordingly there are separate zypper commands for updating and patching

zypper up
zypper patch


Do you know the Tumbleweed Updater plasmoid for KDE? I discovered this plasmoid a month ago and published on it in

I do now.

I like to know that I can use one of these 2 methods to do the updates, according to my personal choice.

I will agree with that.

Oh. It’s that thing that works without being root. I don’t like that though.

Exactly.! Yor description is not exact though. It does upates without asking for the root password (which is what annoys you and me), but installing system software can only be done by a root owned process.