Didn’t work… I tried three installs. The last one I did the following.
Installed Netrunner. Shutdown (to remove installer USB stick). Restarted. Went to Muon Package Manager. Noticed 1 upgradeable package. Opened Software Sources and unchecked the two backport entries (…kubuntu-ppa\backports…). Closed Software Sources window. Waited for “Updating Software Sources” and “Rebuilding Search Index.” Now 341 upgradeable packages. Clicked Check for updates. Again, 341 upgradeable. This is exactly the same thing I did the other two times up to this point.
The first time, at that point I closed MPM and opened Muon Update Manager and did install of all updates, marked and extras at once. While installing, the Muon Suite, etc. were gutted.
The second time, rather than close MPM, I clicked “Full Upgrade” then “Apply Changes,” entered password and the download began. At around 5% into the install (Committing Changes) I checked the Launcher and the gutting had occurred.
This last install, I closed MPM and restarted the PC. Then opened MPM again, checked for updates again. Then did Full Upgrade, checked for updates again which kicked me back to main MPM window so I clicked on Full Upgrade again, Apply changes, entered password, downloading packages. Again, once committing changes popped up, I clicked on the Launcher and saw that Muon was still there, but then at 4-5% it again gutted Muon, etc.
Is this even supposed to prevent Muon, etc. from being removed or are you guys talking about something else? I did notice that the second time I tried, I saw mostly 220.127.116.11 attached at the end of various files (this could be my bad memory since I also tried the Terminal steps after this and that may be where I saw all of the 18.104.22.168). The third time, I noticed 22.214.171.124 at the end. When I say first, second, third, I mean first, second, third installations of Netrunner. I did a clean install after each failure. I thought I was doing something wrong but either the instructions aren’t clear or they just don’t work which would mean it is something else causing the issue.
Shot in the dark… The install that I got updated without issue was the only install on an HDD. No other installs were found on the system at that point (no boot loader screen). With these attempts, I was installing to a USB 3.0 32GB thumbdrive and it was creating a boot loader each time since the HDD install is present. Before the HDD install I also had dual and triple boot installs testing at once at times (that’s what caused my time issue, maybe Ultimate Edition or installing KDE desktop on Ubuntu, whatever, it stuck through later installs). I also may have installed several things on the HDD install before downloading the updates. Could extra packages installed alongside Chrome or XBMC or Disks or KNemo have something to do with it? I also noticed on my HDD install that a few new package updates have come up over the last few days. Maybe that changed something in the Full Upgrade between your attempts and mine. I don’t know. It really needs to be figured out though. Many people abandon distros for this kind of stuff. I was just wanting to get a full update on a test install for installing and testing Catalyst drivers before possibly ruining my HDD install. Hopefully, testing on the nonupdated stick install will be sufficient.