What is Raspberry Pi Imager?
A tool (app) installed on Raspberry Pi OS that I can use to create new versions of RP OS to install either on same device or others
What current version do I have?
At CLI: rpi-imager –version
It comes back with: v2.0.11 (as of 20260925)
How to upgrade (to the newest version)?
sudo apt update
sudo apt install –only-upgrade rpi-imager
Q: What is apt, that I’m updating first?
A: When you run this, it goes out and checks various catalogs, so it knows what current versions are out there. It doesn’t actually update/upgrade any app on system yet.
Q: What is apt?
A: It is the Advanced Package Tool for Debian and other flavors of Linux. A convenient way of accessing applications in various data repositories for installation on Raspberry Pi, for example
Before running sudo apt update, I’m noticing some automatic updates pending in the OS, so doing that first.
I also opened the Imager app, and I’m seeing it saying there is an update available (version 2.0.11.1. Would I like the app to visit the website to download it?
Well.. might as well have the app do it by itself, versus me doing it manually at CLI, so I clicked on update. Well, this went to the www.raspberrypi.com/software website, and had me download the latest version for debian 64-bit. Now I have a file in my Downloads folder. This is a bit weird, as the website says to install you do: sudo apt install rpi-imager (but how do I know if that’s pointing at the download folder?)
I think I’m just going to do the above:
sudo apt update
It comes back with: All packages are up to date
sudo apt install –only-upgrade rpi-imager
It comes back with that the rpi-imager is already the newest version (2.0.11-1). This is annoying, because then why did it download something to the download folder (when I did within the app?). It wasn’t obvious that it completed the upgrade.
rpi-imager — version
Comes back again with version v2.0.11. Does this mean it actually upgraded?
Rebooted the system, as I had done the the updates within the OS feature at top right of desktop
Great. Now I have a flashing icon in top left of monitor after the reboot. Not sure what that means. Didn’t load the desktop.
Ctrl-Alt F1: Failed to start NetworkManager-wait-online.service; cloud-config.service; cloud-final.service; rpc-statd-notify.service
The Network Manager error could be because somehow the startup didn’t see the network connection, even though I have a Cat5 connected to a small switch. I see a green and yellow light on the RP port.
It’s possible there is a conflict as I think I have both wired and wireless configured at same time, but likely want to stick with wired. There’s something in boards about specifying which.
Unplugging the Cat 5 and reseating didn’t do anything, and the green light came back on again. I’m thinking the conflict is within WiFi connection.
I think the goal is to somehow get to a command line; stop the NetworkManager wait online service and then reboot.
Note: I can flip-flop between two screens by Ctrl-Alt-F1 and Ctrl-Alt-F2. F1 shows the startup errors.
Ctrl-Alt-F3. Nothing. I then tried, Ctrl-Alt-F1 thru F6, and could type I think on either F5 or F6.
sudo systemctl disable NetworkManager-wait-online.service
Nothing worked, so I pushed the on/off button on RP5 and it rebooted OK. Need to look in to this about also having WiFi configured, maybe.
Ran RP Imager – same thing. It still hasn’t completed the upgrade to 2.0.11.1
This is nuts. When I try the upgrade within the app, it’s not actually doing the upgrade. I shouldn’t have to be doing deep dives, to now figure out how to do chmod on an .Appimage download and run that, but here goes
The download went into /home/paul/Downloads
Within that is: imager_2.0.11.1_amd64.Appimage
chmod +x imager_2.0.11.1_amd64.AppImage (Note: Ensure case sensitivity)
./imager_2.0.11.1_amd64.AppImage
Comes back with No such file or directory. I don’t get this.
When I double-click the file within file manager, it says it is executable and do I want to execute it.
To be continued….
Addressing NetworkManager errors on startup, where I think there is an issue polling WiFi – and I have a Cat5 cable attached, and don’t see a need for both network connections simultaneously:
To fix NetworkManager errors when you do not use Wi-Fi on a modern Raspberry Pi OS (Bookworm or later), you can disable the wireless interface entirely in the system configuration.
- Open the boot config file in a terminal using:
sudo nano /boot/firmware/config.txt
- Add this line to the bottom of the file:
dtoverlay=disable-wifi
- Save and exit by pressing Ctrl+O, Enter, then Ctrl+X.
- Reboot your Raspberry Pi with
sudo rebootto stop NetworkManager from polling the missing wireless hardware
Outcome: After the reboot, in top right of screen, it now only showed a connection to the wired and not both wired and wireless. Progress.
As for upgrading to the latest .1 version of Raspberry Pi Imager, I’m not sure if it’s worth the efforts right now. Appears that it’s not really designed for upgrading a RP5 in place.
I now have the answer, and it includes how to read version numbers, and it also makes me move on from this sub-project of trying to update Raspberry Pi Imager:
The app is asking to upgrade because your terminal version (2.0.11-1) is actually an older release than the current app version (2.0.11.1). [1]
This confusion comes down to how your Linux system reads version numbers compared to how software developers format them:
2.0.11-1 (Debian Package Format): The hyphen (-) means this is the 1st package build of version 2.0.11.
2.0.11.1 (Upstream Software Version): The extra dot means this is a minor patch release (.1) explicitly pushed out after 2.0.11 to fix a quick bug (specifically a fix for Raspberry Pi Connect)
Because your system’s package manager (apt) treats the dash as a separator for packaging rather than part of the core software version, it sees your installed software version as exactly 2.0.11. Since 2.0.11.1 is a higher number than 2.0.11, the application flags it as an update.
So, I’m going with this option to address is: Ignore it: If the app is working perfectly for you, you can safely ignore the notification until your Linux OS repository automatically pushes out the 2.0.11.1-1 package update.