In the past I have upgraded my various openSuSE machines using zypper while the system was live.
Is this still available for upgrading to 15.0? I could not find the page of instructions and that has always been easy before.
In the past I have upgraded my various openSuSE machines using zypper while the system was live.
Is this still available for upgrading to 15.0? I could not find the page of instructions and that has always been easy before.
Sure.
I upgraded that way.
I could not find the page of instructions and that has always been easy before.
It’s the same as always. Change the repo URLs to point to the new version (i.e. replace 42.3 with 15.0) with YaST->Software Repositories or edit the files in /etc/zypp/repos.d/, and then run “zypper dup” to upgrade.
Thank you; I found the instruction and am upgrading the first computer now.
Memo to self: must improve my searching process!
I did a live upgrade and had small issues
the pinned launchers on the plasma 5 menubar had lost their icon (they still launched the appropriate applications) I just removed and re-added the apps I had pined
I found that SuSEfirewall2 was still installed and active while firewalld was disabled it was my understanding that firewalld replaced SuSEfirewall2?
I uninstalled SuSEfirewall2 and set the firewalld service to active
if you have an nvidia graphic card you need to manually install vlc-vdpau
there wore a few issues with intel users and vdpau I guess the devs decided to package it separately and not have it installed by default this might crash vlc
I also found an issue with vlc and opengl
https://forums.opensuse.org/showthread.php/531206-vlc-crash
which might be related with the nvidia driver or it could be an internal vlc 3.0 issue as I’ve read other distro’s have that same issue
https://ubuntuforums.org/showthread.php?t=2388949
I doubt that these issues are related to doing a live upgrade…
I found that SuSEfirewall2 was still installed and active while firewalld was disabled it was my understanding that firewalld replaced SuSEfirewall2?
It has.
But an upgrade won’t replace one with the other, to avoid surprises/disruptions.
There’s a tool to automatically migrate the config from SuSEfirewall2 to firewalld, but that doesn’t work in (and cannot support) all cases AFAIK.
PS: I had no problem with vlc here, using intel. (I don’t have vlc-vdpau installed)
yes but the broken vlc and missing icons are update related as I had no such issues with 42.3
the opengl issue is probobly code from vlc 3.0 but the missing vdpau plugin was an opensuse decision
Sure, but you’d probably have had the same issues when doing a fresh installation.
the opengl issue is probobly code from vlc 3.0 but the missing vdpau plugin was an opensuse decision
openSUSE doesn’t even ship the vdpau plugin, and never did (it was part of vlc-codecs previously, which was/is only available on Packman and VideoLAN).
Btw, vlc-vdpau does supplement vlc-noX, so it should get automatically installed when installing vlc.
I don’t know why that doesn’t work, I remember that those supplements were missing in the Packman repo in the past because they use a (old) Debian version of createrepo to generate the repo metadata. I thought that would be fixed meanwhile, but probably not.
I.e. this (that vlc-vdpau doesn’t get installed automatically) is likely a “bug” in the Packman repo.
I thought the missing icons was related to the plasma 5 desktop update I wasn’t sure if the plasma 5 menubar did something different to icons as they appeared fine in the start menu only pinned icons wore affected
and yes it was the packman team that split the plugin but it will effect all nvidia users, strangely enough the vlc-codec-gstreamer got re-installed even tho I had it uninstalled this too is packman decision
Sure it’s related to the Plasma update, it’s probably a glitch in the config migration from 5.8 to 5.12.
But the same would likely have happened if you had done a fresh installation with keeping your home partition/directory.
Impossible to say what happened exactly without seeing your config files before and after though.
I never had a problem with this either, but I’m always using the latest Plasma, i.e. I had 5.12.5 on 42.3 already.
and yes it was the packman team that split the plugin but it will effect all nvidia users, strangely enough the vlc-codec-gstreamer got re-installed even tho I had it uninstalled this too is packman decision
Well, actually there is only one vlc package and that is maintained in OBS. Packman and VideoLAN just link to it and builds with the codecs enabled.
So it’s not necessarily a decision by the Packman team actually.
yes but you do agree that for live 42.x->15.0 upgrades SuSEfirewall2 should be removed firewalld enabled and for nvidia users vlc-vdpau installed?
My upgrade to the first computer is chugging along and is nearly finished. My only question at present is the message for every packa ge
“warning: Unsupported version of key: V3”
which i am hoping is benign
Have deleted SUSEFirewall and firewalld is now working fine. But, though I have a WiFi connection listed by firewalld, I cannot make any connections to the outside world. (I tried a wired Ethernet with the same results.) Any suggestions?
sadly I don’t know I had issues with kdeconnect which wore fixed by opening ports 1714-1764
I’d say try the new firewall yast module (it’s for firewalld)
on my machine the network is set as public (even tho it’s private) and the only services I have enabled (they wore enabled by default) are dhcpv6-client and ssh
and as far as I can tell firewalld is active
you can enable http and https in the yast module see if that helps
I am using wicked on a wired network if you are using nm try switching to wicked?
OK I now have a substantive question; I finished the “upgrade” and rebooted. Where is my computer? The logon screen is unfamiliar and seems to require a mouse to do anything. If I click(spit) on by user name an supply a valid passwod and click again (which I hate) I see for a second or so tty1 with a window superimposed which then goes back to the login screen. If I log in as root I get some totally unfamiliar desktop.
I do not use a desktop with clicking all the time – I run (ran?) fvwm driven from xdm interface, with xterms and emacs mainly. I did guess how to log out of the root desktop but how do I actually use the computer? How do I get access to my environment?
Or is Leap 15.0 not usable? Luckily this is on a rarely used test computer so I can still do stuff on Leap42.3 when I can get a more recent gcc installed.
Very disappointed, apart from the graphics while booting which I quite liked. I did read the annoying bugs and release notes and saw no indication that it had this basic an annoying bug!
you didn’t say if network worked with Firewall2
when I did one of the older 42.1 to 42.2 upgrades my network got turned off I just had to go in yast-> network and turn it on again
I’m not really sure I understand your question I use plasma 5 with sddm and while both the sddm theme and plasma 5 wallpaper are new I had no issues
I even logged out of plasma 5 and into lxqt sddm looked and worked the same as in 42.3 and xdm hasn’t changed in decades
if I remember right xdm can not be used to select a desktop environment it logs in to the default one
why do you even login to a root desktop
you should open a new thread for your issues
Well, it doesn’t matter much whether I do agree or not.
If you have a custom firewall setup, it could be very problematic if the upgrade just switches to firewalld automatically (without migrating the config). Keeping SuSEfirewall2 active is staying on the safe side, and likely the better decision IMHO, as the firewall should continue to work exactly as before the upgrade.
And as I already wrote, vlc-vdpau should actually be installed by default anyway. That it’s not is a problem with the Packman repo (missing metadata) I think. The same problem existed with vlc-codecs itself too in the past, but that was workarounded by explicitly recommending it by the vlc package.
Indeed.
This thread originally was just a question about how to do a live upgrade.
Now it starts to become a messy discussion about random problems with Leap 15.0…
Regarding the login screen: the way to configure the login manager to be used has changed. Run this and choose which one you want:
sudo update-alternatives --config default-displaymanager
You can also install and use yast2-alternatives for this.
See also the Release Notes:
https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/index.html#sec.desktop.set-login-manager-session
The default desktop session is set by update-alternatives now too.
(if you want to use xdm, you need to set it properly, with other DMs you should be able to choose it at the login screen)
sudo update-alternatives --config default-xsession.desktop
@john_hudson:
A firewall (neither SUSEfirewall2 nor firewalld) should block connections to the outside.
Probably your /etc/resolv.conf got “corrupted” and is missing a proper nameserver value.
This is a known problem with NetworkManager, it seems to overwrite the file under some circumstances (that haven’t been determined exactly yet) and break DNS resolution.
http://bugzilla.opensuse.org/show_bug.cgi?id=1092352
Try to delete the file and reboot, or run “sudo netconfig update -f” that should fix it.
No, as soon as I booted into Leap 15, the wi-fi was shown and still shows as connected but I cannot make any connections with it; I removed Firewall2 after reading the earlier post in this thread.
I have tried with a wired connection and I get the same result; the connection is reported as existing but I cannot connect with anything.
All other devices including my spare computer on which I am writing this continue to work fine.
Yes, that sounds exactly like the mentioned problem, that DNS resolution is not working because NetworkManager overwrote /etc/resolv.conf with a broken one.
So try what I wrote.
If it doesn’t help, open a new thread with a fitting title in the appropriate forum section and provide more information about your system (e.g. what network cards, are you using NetworkManager or Wicked, the /etc/resolv.conf, the output of “ip addr”, …).