Hi all, please excuse the basic nature of my queries, but I have two questions about upgrading Tumbleweed.
I used the steps described in the following locations, among others: https://en.opensuse.org/SDB:Upgrade_Tumbleweed
Basically, I cached the dup, then logged into a TTY and isolated to rescue.target.
Logged in as my (admin) user—not root—then zypper dupped.
As expected, zypper couldn’t connect to the repos but I already had the upgrade cached.
But, for some reason, zypper was saying that it would remove packages? Specifically, Discord, Steam, and another package.
Wasn’t sure why that was so I just ran zypper dupwithout changing to the rescue.target instead.
Went through that time with no issues.
My questions are:
Why the different zypper results between rescue.target and graphical.target with the upgrade cached?
Is it overkill to dup from the rescue.target? Is this the procedure that most people follow? Or is everyone dupping from the DE?
Logout. And then use
CTRL-ALT-F1
to get to a virtual console, where you can login as root at the command line. You can run “zypper dup” there.
Occasionally, you might see the graphic environment reappear during the update. If that happens, just repeat the
CTRL-ALT-F1
to get back to your command line session.
It’s like Deja Vu in here … seems I just read someone else in another thread wanting to cache a dup (scratching my head)
Overkill.
Don’t worry about an answer
Yes, overkill. No, most do NOT follow this procedure.
Most of us do the very complicated:
zypper dup
There, done
And no need to drop out of a GUI. Overkill.
Personally, I’ve done this with TW for years - two desktops and two laptops. While logged into a KDE Plasma session, I do:
a) open up a windowed console (konsole app as I’m On KDE).
b) execute “su”
c) zypper dup
d) when finished, “exit”, then “exit” (to exit and close konsole).
e) reboot if required.
Easy peasy. No extra zypper commands that offer zero advantages.
I have one comment though (sort of my ceterum censeo) , always use
su -
And in your KDE environment you can choose from the menu “Terminal - Super user mode” and that will do the su - for you, starting with asking for the root password. As a bonus it will spare you one exit at the end.
Show the actual commands and their complete output in each case and someone may have an idea. We cannot look over your shoulder and see what you see.
Well, GNOME Software does only offline update which is the safest way. KDE Discover can also be configured to do it. As for myself, I do not care, but I can also handle potential issues during online update from within full desktop environment.
I do something similar. However, before the “zypper dup”, I do:
screen -L
That isolates the update (in a “screen” session), so that if the GUI crashes, the updating continues anyway. And I can look at “screenlog.0” to see how it went and whether it has finished.
When I realized my “mis-guided” su command should have been “su -”, it was beyond the time to edit the post.
Anyway, and yes, I usually perform other commands while in the CLI, which is why I start at the user level konsole (i.e., my purpose is beyond running dup )
Is F1 not GDM/Gnomes default session location? Doesn’t GDM/Gnome run on F1 or F2 in openSUSE? I’m fairly sure your recommendation would not work for a Fedora/Gnome user, even though I haven’t had GDM or Gnome installed since last century.
Anyway, it’s the reason why I recommend Ctrl-Alt-F3, which works whether X is running on F1, F2, F7 and/or F8. X here runs via DM only on F7, but when started with startx on most recent distros, openSUSE included, X runs on the same tty startx is run from.
FWIW, when I dup, it’s usually from F3, because that’s where I login for admin activity that I don’t want risking interfering with anything I run in X. Update/upgrade trouble can’t readily crash anything that isn’t running.
At present, running KDE with GDM, that just gets me to my KDE session. And CTRL-ALT-F7 gets me a GDM login screen. So I use CTRL-ALT-F1. But use whatever works for you.