![]() Registered Member ![]()
|
Hello,
My KDE Neon installation today decided to upgrade itself to Ubuntu 19.10 underpinnings, is this expected as I thought it would only go to the latest LTS release? I haven't pulled the trigger on it yet as I would prefer to clarify first. TIA Steve PS in case it helps Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 Kernel Version: 5.3.0-28-generic OS Type: 64-bit Processors: 8 × Intel® Xeon® CPU E5462 @ 2.80GHz Memory: 23.5 GiB of RAM |
![]() Registered Member ![]()
|
This is NOT normal or expected. You are correct that Neon is LTS only, so doing the upgrade would make a fine mess, I imagine.
claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
|
![]() Registered Member ![]()
|
That's officially weird then.
Does anyone have any idea why? I have only updated with Discover except for some packages which I applied from third party repos to avoid using snaps or flatpacks ( I don't like them, sometimes they wont let me access my own files and I don't have the time or inclination to work around that when alternatives are available). At the very least, is there a way to make this ![]() go away permanently? Anxiously awaiting next updates (here and in Discover) Steve |
![]() Manager ![]()
|
Check your software sources, you probably have a source in it for Ubuntu 19.10
Running Kubuntu 22.10 with Plasma 5.26.3, Frameworks 5.100.0, Qt 5.15.6, kernel 5.19.0-23 on Ryzen 5 4600H, AMD Renoir, X11
FWIW: it's always useful to state the exact Plasma version (+ distribution) when asking questions, makes it easier to help ... |
![]() Registered Member ![]()
|
OK, sorry about the images, but I couldn't find another way to list them that I entirely trusted.
![]() ![]() Nothing in there is leaping out at me as being 19.10 related, are any of the things that are there likely to have any malevolent side effects? |
![]() KDE Developer ![]()
|
Possibly a combination of issues causing it.
- Ubuntu have just released new versions of their ubuntu-release-upgrader which supersede the Neon versions. That would mean that the upgrade checker could now be parsing the ubuntu release info url instead of the custom neon version. - You may have your system wrongly set to 'normal' in /etc/update-manager/release-upgrades instead of 'lts' Those 2 together would cause what you see. If this is the case, switching that release-upgrades file back to 'lts' should fix things until new Neon packages land. |
![]() Registered Member ![]()
|
We have a winner!
I saw the upgrader stuff in the updates and wondered what that was. I have no idea how the update manager thingie got set to 'normal', this is the first time I ever saw that file. I have changed it to 'lts' and everything looks fabulous again! Thank you very much everybody, that was extremely impressive. Steve |
![]() KDE Developer ![]()
|
Good to hear.
![]() Some of the gui tools available can change the release updates channel. For example in software properties..... ![]() |
![]() Registered Member ![]()
|
It took me a while to find that dialog, so I don't think I changed it before
and, of course, it says LTS releases only now. I reckon if I had changed it, I would also have been tempted to tick some of the boxes at the top under neon updates which are all clear at the moment. However, today, I am mostly leaving things alone! Thanks again ![]() |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]