Since a month or so my Tumbleweed laptop does system updates only through zypper dup.
The KDE update applet shows ‘Use zypper dup to update’ instead of the update button.
So I update in the terminal with zypper dup succesfully - but the next time updates are available It is the same ‘Use zypper dup to update’
What should I do to get back to normal?
That’s the correct way to update Tumbleweed.
The KDE update applet shows ‘Use zypper dup to update’ instead of the update button.
It is giving you a very big hint.
What should I do to get back to normal?
What you are seeing, is the new normal.
Really? Is this the new technological progress - forcing GUI users back to the command line?
How long from now will it take that we are forced to write office documents in in Vi?
Only for updating. The update applet never worked on Tumbleweed. It gave users a false sense of security. But Tumbleweed is a rolling distribution, so every update is really an upgrade. And the update-applet was never designed for that.
How long from now will it take to write office documents in in Vi?
Using “vi” together with “latex” can get you a long way. But nobody is going to force you to go to the command line for everything. Again, it’s only the updating that needs to be done at the command line.
Thanks for sending answers. The ‘vi’ command was a sarcastic one -sorry.
I never knew that you should not use the update applet. Havn’t read or heard that anywhere before. And updating with the KDE applet worked for me for as long as I have tumbleweed (2 years or so).
It’s been the subject of numerous threads and here…
https://en.opensuse.org/Portal:Tumbleweed
To keep Tumbleweed updated to the latest snapshot, run the following command as root (ideally inside a screen or tmux session):
zypper dup
And updating with the KDE applet worked for me for as long as I have tumbleweed (2 years or so).
That is just good luck. It can result in a broken operating system. To keep it rolling-along in sync with the TW repos, one must do a package upgrade.
You can also use Yast if you do not want to use zypper edit the file in etc / zypp / zypper.conf, or use apt, it also works on opensuse, it will be for Debian based nostalgics
This has been the case for TW, since it is NOT an update. Each version of TW is an Upgrade from a Previous Version to a New Version (read the release notes and other TW docs). Version Upgrades are only done using zypper dup, whether going from 42.3 to 15.0, or going from TW version A to TW version B … unless you use the actual installer, instead.
All that has really changed is that the team(s) are trying to make that Clearer to TW users that they must use zypper dup, since so many have been running into problems by not following this procedure.
And, regarding “forcing GUI users back to the command line”, it is made plain up front that TW is for the experienced and the brave, those wishing to be on the leading edge (or, precipice, if you will). This would naturally imply that you should expect some command line activity in your TW experiences, even if you did not bother to read the Release Notes or the Documentation.
according to this link it should be:
zypper dup --no-allow-vendor-change
I wonder why everyone still spreading the “zypper dup” way of life on TW.
Is it because we take for granted that nobody install pacman to have at least some extra codecs (just tried a fresh install of tw and doesn’t let see videos on my favorite porn website, including html5 based ones).
If someone doesn’t install codec/pacman would it be so bad to keep upgrading/updating with zypper dup --no-allow-vendor-change ??
Want it (and I guess many reall do, there’s so much praise on the web) or not tumbleweed is gaining popularity among non-experienced Linux users, I guess because of both the rolling model and the availability of newer packages (I really think no desktop user would want to Leap with a so much outdated version of Gnome/KDE/whatever).
That lwn link above is the first result of googling “how keep tumbleweed update”!!
Third result is from the official TW portal/webpage and still suggests zypper dup
Now a confession: sorry if I sound polemical, I just want to sound sharp because I’m a representative of the average dumb desktop user out there, which as that TW page says is not the target for such an OS but he/she/it will keep installing and using it because of many obvious reasons, in particular: the only way to experience OpenSUSE and a full btrfs experience without ““obsolete”” packages and because it’s adoption is encouraged, want it or not! 
PS: and I guess it’s to educate people to refer to it as a distro upgrade rather than an update, but until you become accustomed and devoted to your TW installation I guess it’s normal for people to address it, in general terms, as updating process, because imho, in general terms, it is!
Now
–no-allow-vendor-change
is the default in TW
The --no-allow-vendor-change switch is, and has been for quite some time now, the default switch in zypper dup, already activated by default so there is no need to add the switch.
Apparently, your googling appears to have missed the multitude of announcements mentioning that.
That lwn link above is the first result of googling “how keep tumbleweed update”!!
That is obviously an old, outdated link.
Third result is from the official TW portal/webpage and still suggests zypper dup
Which is the correct method, although actually adding the --no-allow-vendor-change will not hurt, since adding it has no effect, changes nothing.
Thanks for replies!
Please another question: how bad is to update TW using a terminal emulator (like Gnome Terminal) rather than a new Virtual Session (the ones you open with CTRL+ ALT + Fx, sorry for wrong wording)?
How many chances to bork the system because of running processes?
Cheers
On Mon 26 Nov 2018 08:16:03 AM CST, horizonbrave wrote:
Thanks for replies!
Please another question: how bad is to update TW using a terminal
emulator (like Gnome Terminal) rather than a new Virtual Session (the
ones you open with CTRL+ ALT + Fx, sorry for wrong wording)?
How many chances to bork the system because of running processes?
Cheers
Hi
Run the command screen, then do your update…
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Yes, this is what I use.
Sometimes an update will restart some process and crash the desktop. But screen keeps running.
I normally use “screen -L” to run updates. That way the output is logged to a file. If the desktop crashes, then I use
tail screenlog.0
to check the screen output. And it is sometimes still running. So I wait for everything to finish in the update before rebooting.
If I forgot the “-L”, then I instead use “ps” to see if “zypper” is still running somewhere. And I wait for that to finish.
On 11/26/18 3:16 AM, horizonbrave wrote:
>
> Thanks for replies!
>
> Please another question: how bad is to update TW using a terminal
> emulator (like Gnome Terminal) rather than a new Virtual Session (the
> ones you open with CTRL+ ALT + Fx, sorry for wrong wording)?
> How many chances to bork the system because of running processes?
>
> Cheers
>
>
I always use a konsole window for running
zypper dup
and never have any problems. just makw sure you logout/in or reboot
after the update.
–
Ken
unix since 1986
S.u.S.E.-openSUSE since 1998
What do you think should the Tumbleweed wiki page provide the full “screen” command?
I know I know Tumbleweed is not for noobs, but still… improving instructions doesn’t hurt, and noobs will keep doing things they shouldn’t anyway… you can’t stop them and this way they’ll steal valuable forum resources with their problems because of not fully detailed instructions. Just my 2 coins :)))
That might be a good idea.