The latest update to Raspberry Pi OS

We’ve just released the latest version of Raspberry Pi OS.

This time around, it is mostly a wrapping-up of all the bug fixes and new versions of software which have been released since the previous image in April; but there are a few small tweaks to the user experience which we should probably mention…

New searchable main menu

For people who would rather type than move the mouse, we have modified the main menu plugin on the taskbar to allow text searching. Just hit the Raspberry key on your keyboard (which is usually the Windows key on a non-Raspberry Pi keyboard) to open the main menu, and start typing the name of the application you want to launch. When you start typing, a search box appears, along with a list of all the applications whose names contain the text you have typed.

You can move the cursor with the up and down arrow keys, and then just hit enter to launch the one you want, or double-click it with the mouse.

If you don’t start typing anything, the main menu will continue to work exactly as it did before; this is just additional functionality, not a replacement for the existing menu. Note that the search box only appears once you start to type text; you don’t see it if you just open the menu and use it as normal.

New audio input control

In previous releases, the volume icon on the taskbar could be used to select both output and input audio devices. For this release, this has been split into two separate icons, one for output and one for input. If you connect an audio device which is capable of input, either via USB or Bluetooth, a microphone icon will appear on the taskbar next to the existing speaker icon.

To select the audio input device, right-clicking the microphone will show a list of the input devices available, and you can then click the one you want to use.

Also, left-clicking the microphone icon brings up a volume control which can be used to adjust input level or mute the microphone completely.


This release includes the new Picamera2 Python camera interface. This is a higher-level interface than the existing libcamera and is easier to use, and warrants its own blog post with a full description. Look out for this over the next few days!

New keyboard shortcuts

One thing that a few people have pointed out is that it is not possible to access the Bluetooth and Wi-Fi menus on the taskbar from the keyboard; you need a mouse to use them.

In this release, we have added keyboard shortcuts to access this functionality – hitting Ctrl-Alt-B opens the Bluetooth menu, and Ctrl-Alt-W opens the Wi-Fi menu. Once the menu is open, the cursor up and down keys can be used to navigate. Enter selects the highlighted item, and escape closes the menu.

NetworkManager compatibility

In previous releases, we have used a piece of software called dhcpcd to manage a lot of the networking functionality. In particular, it manages connection to Wi-Fi networks – when you click the network icon on the taskbar and choose a Wi-Fi network from the menu, this is all controlled by dhcpcd.

Many other Linux distributions are now using a piece of software called NetworkManager to do the same job, which seems to be becoming the de-facto standard, so we have added the option to use NetworkManager in Raspberry Pi OS. At present, dhcpcd is still the default – you need to switch to NetworkManager if you want to use it – but in some future release, NetworkManager will become the default.

Why switch? Mainly because NetworkManager adds a bunch of extra features which you may find useful. It allows you to easily connect to wireless networks with hidden SSIDs. It makes managing VPN connections more straightforward. And it allows you to easily configure a Raspberry Pi as a Wi-Fi access point.

NetworkManager support should be regarded as a beta feature for now – there may be the odd situation where something doesn’t work as expected. If you rely on a Pi to have glitch-free networking, the safest thing to do is to stay on dhcpcd for now; but if you want the new features and are happy to live with the possibility that it may be slightly less reliable, then feel free to try NetworkManager – you can always switch back to dhcpcd if you have problems.

To switch to NetworkManager, just open a terminal window and type:

sudo raspi-config

This launches the configuration tool. Go into option 6, Advanced Options, and then into option AA, Network Config – choose option 2, NetworkManager, and then reboot when prompted.

Once rebooted, NetworkManager should be running – to check, open the Wi-Fi menu on the taskbar. It should now include an additional sub-menu at the bottom, Advanced Options – this is where you can connect to a hidden network, create a hotspot or set up VPN connections. There are also a couple of useful information dialogues which allow you to see and change parameters for any network connection already configured.

Once you have switched to NetworkManager, you will need to re-connect to any Wi-Fi network to which you were connected under dhcpcd – connections do not automatically transfer between the two systems. Similarly, if you have made any customisations to a wired connection, such as setting a static IP address, you will need to redo those customisations under NetworkManager. (Most of these settings can be accessed via the connection editor, accessed from the “Edit Connections” option in the Advanced Options sub-menu.)

In order to use a VPN, you need to install the relevant VPN plugin. The OpenVPN plugin is useful for many networks. To add it, open a terminal window and type:

sudo apt install network-manager-openvpn-gnome

When this has installed, choosing the “Add VPN Connection” option from the Advanced Options menu will open a dialog offering OpenVPN as a connection type.

If you find that NetworkManager is causing problems, you can use raspi-config to go back to dhcpcd – just enter the Network Config option as described above, and choose option 1, dhcpcd.

How do I get it?

The new image is available for download from the usual place: our Downloads page. It can also be flashed straight to an SD card using Raspberry Pi Imager.

To update an existing image, use the usual terminal command:

sudo apt update
sudo apt full-upgrade

Then, in order to load the new taskbar plugins, launch Appearance Settings from the Preferences section of the main menu, and on the Defaults tab, press the button corresponding to the size you prefer. Then reboot – this will reload the taskbar and load the new plugins.

To install NetworkManager on an existing image, open a terminal and type:

sudo apt install network-manager

As ever, all feedback is welcome, so please leave your comments below!


Al Stevens avatar

Good to see a fresh release, as some of the updates since 2022-04-04 release were becoming a notable post-install burden (I’m looking at you, Wolfram!) on fresh setups.

As I don’t have any current Gnome-based environments around, is there a NetworkManager plugin for WireGuard yet? A far better and faster VPN solution than OpenVPN these days, I would suggest!

Simon Long avatar

There are only two VPN plugins I can see in the Debian apt repo – the OpenVPN one and one for Fortinet SSLVPN; I can’t see one for WireGuard, but there may be one in some other repo somewhere.

Fantu avatar

don’t need plugin for it, Network manager have already native wireguard support

The Unknown Cynic avatar

We had great hopes for integrating our available Pi3’s and Pi4’s under this same OS for a vehicle-mounted security system.
What we’re finding is that this OS’s DNS only works sporadically whereas the older Raspians OS’s work fine (all observations being on the “bench”, as it were).
If we use Raspberry Pi’s at all we’ll probably have to use a heterogeneous deployment of older Raspian OS’s and MotionEyeOS.
We can speculate about the Unbound implementation, though our other OS’s also employ Unbound and they work just fine.
Is this related to the Pi’s continual attempts to contact to TestNet#3? We don’t and won’t allow that.

Simon Long avatar

I’ve no idea why a Pi would be trying to connect to TestNet#3 – I’m not aware of anything anywhere in the system which would be doing that. Are you running the desktop or the lite version? And where are you seeing that this attempted connection is taking place – is there a log file or similar which shows it?

Alan avatar

Thanks for the update. Reading through this reminded me – Generally the default appearance settings for different screen sizes are handy. However, it would work better if the default icons functionality could be separated from the default sizing function (e.g. an extra button dedicated to resetting the panel items). If you just want to simply reset or adjust the sizings for the screen, it’s something of a pain that at the same time it resets the application launch bar programs and the panel applets/plugins to the minimal defaults (following reboot), and it also loses the preferences/options for them..

Simon Long avatar

That’s a good suggestion – I’ll look into that for a future release.

David Gordon avatar

I’m not seeing the searchable menu or the WiFi & Bluetooth shortcuts on a 64bit PiOS on a Pi 4B after upgrading using ‘apt’ in the normal way. I also selected ‘Default’ for large screens in Preferences -> Appearances Settings, and rebooted. Is this because I’m on a 64bit OS?

Simon Long avatar

No, those should all work fine on 64-bit.

When you have rebooted, open the Panel Settings dialog and on the Plugins tab, check that you have “Menu (Searchable)” loaded instead of just “Menu” – you may need to do this manually, as it sounds as if something in your config has prevented the new defaults from loading.

Brian Dowd avatar

Pi4: clicking on panel > Panel Applets > Add > shows “Menu with Search”. But LXPanel does not respond with a search box to a “super” keypress on a PC105 keyboard.

Simon Long avatar

Did the same keypress pop up the menu previously? It shouldn’t have changed. The search box is only shown when text is entered when the menu is already displayed – so you need to press the Windows key to open the menu, and then start typing text to show the search box.

Brian Dowd avatar

Display “menu with search”, press super key and the Menu disappears.
Press super key again and menu reappears. Neither display of menu shows the search box at the top. This is with RaspiOS 64-bit.

Mark Routledge avatar

Thank you so much, this fixed not being able to search the programs menu. For some I don’t have a ‘plugins’ under panel settings, I had had to add the ‘Menu with Search’ applet and remove the standard ‘Menu’ applet. Works perfectly.

Segen avatar

I had to turn off my num lock on the keyboard for the search function to work

Simon Long avatar

I’ll check that – I may need to look again at modifier keys when handling key presses in the menu.

Alan avatar

Thanks for the tip. Same here, the menu search doesn’t work with Num Lock enabled, only without. Hopefully it can be fixed as generally run with Num Lock enabled on a full size keyboard.
Using a ‘Generic 105 key’ keyboard, this has 2 windows keys left and right. It’s the left hand side one that brings up the menu for the search.
Something else I noticed whilst trying to get it work – if you just have the desktop without any programs open, and then use the right hand side windows key and start typing, then it brings up a ‘search box’ on the right hand side of the screen which can be typed in but doesn’t seem to be linked to anything.

Simon Long avatar

I’ve verified the bug with Num Lock (it affects Caps Lock as well) and have fixed it – a fixed version of the package will appear in the repos in the next few days, and will be installed the next time you update.

Johnny avatar

For me menu search is not working even I turn off the num lock or caps lock and wifi and blutooth manager shortcuts also aren’t working after fully update and upgrade. Rpi os 64bit

Simon Long avatar

Did you go into Appearance Settings, reset to defaults and then reboot?

Simon Long avatar

We’ve identified a bug in the handling of keyboard shortcuts on 64-bit – there is a fix, which should be in the repos in the next couple of days.

Lew avatar

The new Keyboard short cuts were working until I change to a dark theme. Now they don’t work even though I went back to the default.

Simon Long avatar

We don’t support themes other than our own PiXflat, I’m afraid.

Kevin avatar

The search box is not new. It allows you to select and open desktop icons from keyboard only. For example typing w will highlight the wastebasket icon. Now press [Enter] and the wastebasket will open.

Sheddyian avatar

I also had this happen, 64 bit OS. After the update, still had “menu” rather than “menu with search” and I don’t see the wifi or microphone icons on the taskbar.

Alan avatar

Not 100% sure, but seemed to take more than one shutdown/restart after the update for it to create a new “panel” file at ~/.config/lxpanel/LXDE-pi/panels/ panel
Although it may just have been that I’d made a backup file ~/.config/lxpanel/LXDE-pi/panels/ panel.bak (before the update/resetting the display defaults) which the system used and this somehow prevented the new panel file from being created. When I moved the backup file elsewhere it sorted itself out after restarting.

rclark avatar

Nice to see work continuing on the PI OS. I rarely run with a GUI as my preferred method of accessing all my PIs is using SSH and SFTP. But good to keep current :) . Thanks for all the hard work.
That said, I haven’t seen an RPI4 for sale in months (unless you want to pay scalpers triple the price), but I have enough stock in-house to keep me going for awhile anyway, so I am not hurting at the moment. Working more with various RP2040 based boards (the $1 chip seems to be quite a success!), which seem to be more in stock from various vendors.

Ananomis avatar


Protik avatar

When the NetworkManager becomes default, will it be transparent to the user? All my Pis are connected to wifi. I would hate them to lose connection after an update.

Simon Long avatar

In general, it would only become default on a new image – existing images would probably continue to use dhcpcd until you manually changed the option.

Protik avatar

I see. That’s nice.

If there were any way to provision NetworkManager, would be nice. I have been running my Pi headless for so long that I don’t even know where the HDMI cables are.

Simon Long avatar

Remote provisioning of Network Manager has already been implemented by a method similar to that used for dhcpcd in current images, but as the images ship with dhcpcd as the default, it is not used at present. It will be enabled when Network Manager becomes the default.

Elias Mimmis avatar

Have the keyboard changes between languages been fixed or at any restart we have to make keyboard settings again?

Simon Long avatar

I have fixed a bug in the Mutter window manager which was causing some issues with switching keyboards – if that was the problem you were having, then yes, this ought to have fixed it.

Brian Dowd avatar

First and foremost…you have a wonderful product and I feel guilty about posting issues but updating didn’t fix it , so mutter isn’t the issue.

Simon Long avatar

OK, in that case this is an issue I am not familiar with – can you please describe the problem? I’ve just tried setting a French AZERTY keyboard in Raspberry Pi Configuration; when I reboot, I still have an AZERTY keyboard, so it looks to me as if keyboard settings do survive reboots. Any more detail on how to repeat the problem you are seeing would be helpful.

Brian Dowd avatar

RP website shows a search box displayed at the top of the menu listing (like Linux Mint). Instead it is a small, single line window which only shows up when you start typing after you first click the ‘start-here’ raspberry icon in the taskbar.

Simon Long avatar

That is what I described in my reply to you above.

The menu view is hierarchical – it shows categories at the top level – and has no search box. The image on the post doesn’t show a search box at the top of the menu; it shows the view when searching, a search box at the top of a filtered non-hierarchical view. Using the hierarchy to display the search results would have made it much harder to navigate, so the two modes are distinct and not combined.

Paul avatar

I have a file server running 32bit Buster and a spare desktop on Buster 64bit is it possible to upgrade to the new one from any of these? I have been recently burnt by Linux Mint upgrade and being careful this time.

Simon Long avatar

Not easily – this is an update for Bullseye, not Buster. We don’t recommend updating between major Debian versions – we recommend starting from a clean Bullseye image.

Paul avatar

Looks like the file server will stay on Buster for the time being, but may be my 8GB RPi 4B might get an upgrade in the near future. I was so glad to have available when the Mint problems were going on. Once Mint has settled I will update the desktop

Luna bittin Jernberg avatar


Saw this when i browsed Phoronix today and has updated now :)

beta-tester avatar

what does “NetworkManager compatibility” mean?!
is the use of /etc/dhcpcd.conf obsolated, is /etc/network/interfaces agein the state of the art, or which are the new configuration files for the new standard?

Simon Long avatar

dhcpcd.conf will no longer be used. has the documentation for NetworkManager – we will be using vanilla NM with no Pi-specific customisation, so that documentation will be accurate for the Pi.

beta-tester avatar

thank you for the link.
when dhcpcd.conf isn’t used anymore, will the ‘sudo apt full-upgrade’ break systems with customized dhcpcd.conf ?

Simon Long avatar

No, it shouldn’t. We would probably only make Network Manager the default on a new image; old images would carry on using dhcpcd when upgraded until the user chooses to change.

rclark avatar

Good one :) . Ha Ha! No, NetworkManager has, yet another, new configuration file or files. NetworkManager.conf for one, which appears can be located in any place — ie. depending on how distro packages it. New ‘tools’ to use to like nmcli (for those of us using the good o’ command-line. No, network management isn’t as easy as using the tried and true (what we are all used too from years of working with Linux). Someone is always looking for a better mouse trap it seems. Point is … another learning curve coming up.

rclark avatar

This was reply to beta-tester …. Whoops.

William Stevenson avatar

I always look immediately to the comments section after a major change liken this- usually my problems have already been described by someone else, and the solution offered. This was again the case, so thanks for the improvements

Wayne O. avatar

I followed the guide and everything seems to have worked, except I don’t have the search feature in the main menu for some reason. I tried pressng the raspberry button and it opens the menu but there’s no search available.

Simon Long avatar

Search appears when you start to type – hit the raspberry button to show the menu, and then hit the first letter of what you want to search for – the search box will then appear.

Gordon Cummings avatar

I have a pi compute. But this is what I got for the full upgrade. Doesn’t this work for the Compute?
pi@raspberrypi:~ $ sudo apt full-upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pi@raspberrypi:~ $

Simon Long avatar

You need to do “sudo apt update” first, before “sudo apt full-upgrade”.

HayRide avatar

Hi hope you don’t mind my question on screen size. In this thread. I stream TV on two Pi’s to both 65 inch and a 50 inch TV’s in monitor mode. But I can not get it to size correctly on either screen using the canned routines. Can you suggest a fix?

MW avatar

Totally depends on Operating System / Version, ALL Raspberry Pi SBC & Compute Module support Raspberry Pi OS Bullseye ARMHF, whilst ARMv8 models also support the ARM64 release….

Seth avatar

I did what this said. I had to watch my storage fade away into almost nothing.

Seth avatar

I only have 5.4 GB / 16 BB free space !!!

Simon Long avatar

How much free space did you have before? There is nothing particularly large in this upgrade; Network Manager is a few tens of megabytes.

Patrick avatar

I have found upgrade or full-upgrade has not worked, even after rebooting a few times. I did try to install network-manager manually but it failed to run on reboot.
Linux raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux
Sources are standard bullseye

Simon Long avatar

Did you remember to do “sudo apt update” first?

Antonio Gadong avatar

You have a 32bit version with recommended software. For 64bit version, why is there not one with recommended software?

Simon Long avatar

The version with recommended software is primarily intended to be flashed onto the SD cards which are sold with Raspberry Pi kits and the like – these always use the 32 bit version at present for maximum compatibility.

Very few people will ever need all the recommended software; for most people it makes much more sense to download the standard image, either 32 or 64 bit, and just use the Recommended Software app to install what they actually want.

john avatar

I’m sad to see no LXQt rebase…
everything else is just fine!

Simon Long avatar

We don’t use LXQt, and we aren’t planning to move to it. It would be a huge amount of work for very little benefit over the well-tried and tested LXDE which does everything we need it to.

MW avatar

If you desire LXQt Desktop Environment, there is no reason why you couldn’t install it yourself, preferably on Raspberry Pi OS Lite:

Vu avatar

What? The new network manager is enable automatic after update and reboot? I lost remote access to to my oversea device now, can’t config any more…..
My local device have no “wireless and wire network” icon in system tray after reboot. Pita now…

Simon Long avatar

No, the new network manager is not automatically enabled. It will only be enabled if you go into raspi-config and enable it. Unless you have done that, then your system is still running exactly the same dhcdpcd as before.

Andrew avatar

This is for Bullseye? I use my Pi exclusively headless through xRDP and the desktop was very slow, prompting me to revert to Buster. Has the situation changed at all?

Simon Long avatar

Not with regards remote desktop speed on Bullseye. For remote desktop use via our preferred solution, VNC, we switch back from the mutter window manager to the older openbox – this improves speed significantly; you may want to try that.

Andrew avatar

I find that VNC uses more resources than xRDP and VNC also echos the local logged in user which I find inconvenient, whereas RDP starts a new login session separate to the connected screen user.
However, I shall give it a try, thank you for the suggestion.

CV avatar

Not sure how controversial this is but would it be possible to use just Ctrl+C/Ctrl+V everywhere, including the terminal, rather than Ctrl+Shift+C/Ctrl+Shift+V?
And thanks for the hard work!

AndrewS avatar

Ctrl+C in the terminal is the keypress used to interrupt / terminate a running command. But you can still use the Terminal’s menu options to copy’n’paste, if you find the keyboard shortcuts too confusing.

Simon Long avatar

Unfortunately not. The reason those shortcuts are different in the terminal is because Ctrl-C and Ctrl-V have specific meanings within the terminal other than their use in GUI environments for cut and paste – so Ctrl-C sends a specific signal to the remote system to which the terminal is connected. There’s no way around this without rendering the terminal non-standard, and that would cause even more annoyance!

Paul Baumann avatar

This update breaks the definitely the network connectivity of my raspi4. After this update it booted, but is no more reachable via network. No ssh, no reply to ping. As it is in a remote location this is really a mess!
Is there anything I can do?

Simon Long avatar

Nothing should have changed in networking unless you have gone into raspi-config and deliberately chosen to switch to NetworkManager.

Vu avatar

Same boat, update via apt + sudo reboot. lost 2 device connections, 1 oversea pi4 using wifi, 1 local pi4 using ethernet. the ethernet one can’t connect automatically to lan eth0, no (new) ip, just stay disconnected after reboot. Both pi4 installed wireguard…
to save my local pi4, must connect the monitor, mouse, keyboard to run raspi-config to restore the old dhcpcd to make it connect again. It’s may not related but then my home assistant samba addon stop working because cant connect to eth0 interface.

Asiantuntia avatar

I have the same problem after just sudo apt update && sudo apt upgrade -y. After reboot, no network at all. Cant connect to wifi. How do I fix this? This was a headless machine. Connected it to a screen and it hangs for a minute to trying to start NetworkManager-wait-for-online. I have not enabled the networkmanager.

Supra avatar

If Picamera2 is already installed. Can I do this import picamera2?

David Plowman avatar

Yes – lots of examples here: and more info to appear on this blog shortly.

Milliways avatar

I preface this with the caveat that I have not tried NetworkManager on Raspberry Pi OS but have used it under Ubuntu on both the Pi and conventional computer.
NetworkManager works well enough on a conventional computer but IMO has a number of drawbacks for the Pi.
1. It is not easy to setup without GUI
2. Most significantly the use of Predictable Network Names in config files makes it unsuitable for my normal usage.
I setup Raspberry Pi OS on one Pi then clone to other SD Cards and often swap between Pi – HOWEVER using Predictable Network Names means that every network has to be setup on every Pi (as they have different MAC).
PS I currently use a mixture of dhcpcd and systemd-networkd. The latter seems to be increasingly used on Linux distos (including Ubuntu server) although WiFi seems to be poorly supported.

Alan Dawson avatar

Thanks for keep RpiOS updated, i`v updated my 32 bits OS and all worked fine at first attempt at glance, i have only to chose my connection again and enter my password. About the 64 bits version the usability on My 3B become poor, maybe i use it only for CLI or headless tests with Kubernetes and Docker, IMHO an full 64 bits version would be nice for Pi 4 owners.

Rob avatar

Hi, does this release bring the pipewire support up to date?
I’m thinking specifically of the libraries required in this blog post:

Simon Long avatar

We’ve not done any work on pipewire for this release.

Tomas Lindén avatar
David Plowman avatar

Yes, thanks for listing the correct URL. With this release happening the manual has spontaneously become “non-draft” so there’s been a slight synchronisation issue in getting everything updated!

John Hagensieker avatar

I ran the upgrade on a CM4 (64bit) and on a Pi 4 (32 bit). Update then full-upgrade. I don’t have the Network manager option under AA. Both just have option 1 dhcpd. Also I get this when I back out of raspi-config.

Failed to get unit file state for NetworkManager.service: No such file or directory

Simon Long avatar

As the instructions said, the NetworkManager option in raspi-config will only appear on an update if you manually install the network-manager package.

John Hagensieker avatar

This happens when I try to install network-manager:

pi@NASPI:~ $ sudo apt install network-manager
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Package network-manager is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package ‘network-manager’ has no installation candidate

MW avatar

You are running Raspberry Pi Operating System Bullseye ?

Have you APT upgrade / full-upgrade ?

network-manager has been in Debian Repositories for several years:

John Hagensieker avatar

Yes to Bullseye from the 4-22 version. update and full-upgrade. One is easy enough to start over with but another one is buried deep in my camper with a 4G and GPS Hat on it. Getting it out isn’t impossible but would be no fun. It’s on a CM4 with Pi OS on the eMMC.

Simon Long avatar

I’ve just tried this here – I flashed a standard 32-bit desktop April 22 image to a new SD card, ran through the setup wizard, and then did an apt update / full-upgrade. The resulting image installed network-manager without problem.

It looks as if something may have got corrupted in the apt configuration on your image; I’d suggest copying the contents of /etc/apt and all subdirs from a clean image over whatever is in the same directory on your image, and trying again. The apt data and the server both look good to me, so the problem is with your image, I’m afraid.

Chris Barnes avatar

Had problems on two Rpi4s with 64bit OS after update. Real VNC server didn’t work. Both solved by reinstalling. Open a Terminal window…type
sudo apt-get install realvnc-vnc-server

Ruben Tomas avatar

Just installed the Lite version and I’ve noticed that sound via HDMI is not working anymore. The PCM volume control for the device from alsamixer do not exists.

Gavin Baker avatar

I have done a full upgrade to the Buster OS version and installed network manager as describe in the very informative article above. I rebooted several times but can not get the new task bar icons or the search menu. Yes I have looked in panel addons but only menu is listed…
I am sorry if I have missed something simple but any help would be great.

Gavin Baker avatar

I take it the new features will work with the Buster OS version and don’t need the Bullseye OS version. Is there a way of updating to Bullseye OS keeping all the currently installed software and data, rather then having to start again with a fresh OS image.

Simon Long avatar

No, we do not support older versions of the desktop; we only support the current version. Porting all changes to previous versions would be a massive maintenance headache, and we simply do not have the resource to support old versions with anything other than security-critical fixes.

Instructions for upgrading a Buster image to Bullseye can be found at Bear in mind that we do not recommend or support the process of migration of images between major version releases, as while the suggested process works on clean images, we cannot guarantee it will work correctly in all circumstances. We strongly recommend taking a backup first, and such upgrades are at your own risk.

Graziel Hernandez avatar

Everytime I try to update or get software recommendations I get this error updating package data -E: wheezy/ InRelease is not (yet) available (Something wicked happened resolving ‘’m:http’ no address associated with host name

Simon Long avatar

OK, you seem to be running Raspbian Wheezy, which is about six years out of date now, and you are using an apt repository which is nothing to do with us! I’d suggest starting again with a clean copy of the latest image.

Rick Barnich avatar

After latest update, Network Manager won’t accept WIFI SSID. Maybe it doesn’t like underscore characters? Worked before.

tong avatar

Can’t wifi be turned on using wpa_supplicant.conf?

Aderbal Nunes avatar

After updating network-manager, my RPi4 disconnected and the icon for network settings no longer appears. Even if I do a reboot.

longtime pi-er avatar

I have some old Pi 2 lying around that I want to try this on,
but I cannot find the compatibility list, eg. I would have expected some compatibility statement at
Where have I missed this.

Simon Long avatar

There is no need for a compatibility list. Every 32-bit version of the OS we have ever released will run on every single model of Raspberry Pi which was available at the time of the release. Not only will this latest release run on a Pi 2, it will also run on an original Pi 1!

CooliPi avatar

How do I get virtual desktops and correct switching between ALL windows using Alt-Tab ? Or how do I downgrade to the previous version that had worked for me (in this regard)?

stefan avatar

have put in he update command to the terminal on my raspberry pi and it won’t update

Asiantuntia avatar

Latest update breaks networking. I dont even have enabled networkmanager but it was installed during last update? I cant connect with ethernet or wifi.

Asiantuntia avatar

NetworkManager was enabled automatically. The fix was running raspi-config and changing to dhcpcd from there got the network working again. I had to drive 400km to do this. Please test the updates before distributing them.

Asiantuntia avatar

And test the updates as a user or administrator before updating. If you can. You cant trust anymore to just use basic “apt update && apt upgrade -y”.

Simon Long avatar

We always test updates, on a vanilla install of the previous version of the image. (And updates must always be run as an administrator, so testing as a user would be meaningless.)

But we cannot test every possible configuration which users may be running – there are limitless possibilities for what a user may have installed or uninstalled or changed, and any update, even one from upstream Debian, has the potential to break some aspect of a running system. We always recommend backing up before updating on any critical system.

Simon Long avatar

We are not installing NetworkManager on an update. For it to be enabled automatically, you must already have installed it yourself, for whatever reason, and this would be unwise if you were still relying on dhcpcd.

onepiece avatar

I used two methods to connect the raspberry pi to wifi, the first method, added wpa_supplicant.conf, ssh, userconf.txt files to the boot partition. In this method, I can log in to the Raspberry Pi remotely, but the default dhcpcd cannot connect to other wifi, showing No wireless interfaces found. The second method uses the Raspberry Pi Imager configuration, the default is dhcpcd, which is in line with this update, and can also connect to other wifi . How to set up dhcpcd so that it can connect to other wifi in the first method?

Peter avatar

Do your RaspberryPi OS Updates follow Debain Updates?
eg. Debian 11.5 was released Sept 10 2022. Will there be updates to PiOS to reflect those Debian Updates? Or do you all just sync up at major releases? eg. Debian 12 ‘BookWorm’ will be the next major release.
Just curious how your cadence follows theirs..

Liz Upton avatar

For mainline releases it’s always (usually much) less than three months – our goal is always to be as close as we can, and we try to cap that at three months. We don’t tend to track fractional releases like 11.5; we’ll pick that up with the next big release.

Lawrence avatar

When DHCPCD is Eventually replaced with network manager, will wpa_supplicant.conf Still work? I Use this feature to set up my Wi-Fi connection since the Orca screen reader requires an Internet connection to install it, and I can’t always connect my raspberry pi to ethernet because I’m using a shared router. If not, will there be some kind of work around that doesn’t require Internet to get Orca working?

Milliways avatar

Network Manager does use wpa_supplicant.service but it is not configured like other network managers.
It can be configured at the command line with nmcli
e.g. nmcli connection show
Each WiFi network has a separate config file in /etc/NetworkManager/system-connections/

henning engelbrecht larsen avatar

I tried to switch to NetworkManager (NM) as per the description in this blog. However NM is not and option – Only dhcpd. It is using raspi-config version 20221018 and bullseye lastest full-upgrade. What is up/down in this?

Squonk avatar

Yesterday – 21 Nov 2022 – I implemented this update to Pi OS on my Raspberry Pi. I wished to utilise Network Manager.

I have version 20221018 of Raspi-Config.

Network Manager is not present as an option. I can only see ‘1 dhcpcd’ within the ‘AA Network Config’ submenu.

Any ideas ?

Comments are closed