Hi there, On Sat, 25 May 2024, novaTopFlex wrote:
I have installed QEMU 9.0.0 and have effectively attempted to remove my native QEMU 6.2.0 installation by pushing the 9.0.0 commands into the “/usr/bin/“ directory.
Mr. Garcia gives good advice but I think this is off-topic for QEMU. Basically you're saying you broke your operating system with some ill-advised changes, and now you need to fix it. The fact that the ill-advised changes involved a new version of QEMU is irrelevant. My advice would be *never* make any manual modification to the content of system directories like /usr/bin in an Ubuntu system, but instead let the package manager do it all for you. The directory structures in Debian-based systems are sometimes fiendishly complex and you could do more damage than you've already done - to the point of making your system unbootable - if you get one character wrong in a shell command when you're logged in as root. Every now and then I'll do that myself because I haven't taken my own advice, but when I trash a system it's very rare that I can't fix it without telling anybody. I'll probably, nevertheless, mutter things about my own folly while I'm doing it. If you're using a distribution like Ubuntu or Debian you already have the facility to have different versions of packages installed on the same system at the same time. If I wanted to have a newer version of a system-installed package I might for example put the executables in /usr/local/bin/, and my environment setup would then have a PATH where /usr/local/bin/ was found earlier than /usr/bin/. That way I can run either version from the command line by typing the full pathname of the relevant executable, and if I just use the executable name without the path then I'd get the 'local' one. Of course you might want to do it the other way around, so that you'd get the old version by default. Here's the PATH on my desktop box: PATH=/home/me/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin As you can see I can build packages for installation in /home/me/bin/ and I'll get them by default instead of a system-installed version but anybody else who uses the system won't unless they're logged in as me or they've made a similar modification to their PATH. (This begs all sorts of questions about permissions, where to find any libraries, and what versions of everything will be required. If you stray away from the package management system then you have to figure all that out and attend to it by yourself, and maybe *nobody* will be able to help you if you screw up.) Anyway to get slightly back on-topic you can use these techniques to have a 'development' version of QEMU available, but keep the 'stable' version available on your system too. Starting things from a GUI is Yet Another Topic I won't go into now.
I can no longer access various elements of my Ubuntu Linux (22.04.1 LTS system formerly with native QEMU 6.2) system, and some of these applications are absolutely essential to my caseload such as Chromium. I have also lost access to the NetworkManager service
NetworkManager is usually one of the first things I uninstall, but if It Works For You you might try just reinstalling it. Something like sudo apt install network-manager might be all that's needed, or you might need to do some configuration if your network setup is complex or/and you've tweaked it in the past. If you just broke networking this might fix your browser problems, but if you did more than that it might not be the end of your troubles.
because of pushing the installation of QEMU 9.0.0 forward and do not want to lose various pieces of my data to this issue. What is proper procedure for navigating through this issue?
Unless there's enemy action, there's very little that can never be recovered. But first, if you wish and off-list since this is well OT, tell me about your routine backup procedures. -- 73, Ged.
