I typed that into google and it said that wayfire manages scaling and display stuff via wayfire.ini e.g.
[output:HDMI-A-1]
mode = 3840x2160@30000
position = 0,0
transform = normal
scale = 2.0
hmm… need to check but that kind of makes wdisplays interacting with wayfire kind of difficult.
As to numlock, lets say we added numlock as a configurable item in BCC, which section would it go in? guessing keyboard but would need to sketch out how it would look.
Please note - I’ve uploaded for the 26.04 wayland testing PPA labwc 0.20.0 plus the new wlroots 0.20. Logically this should be a seamless update.
This is the version that will be part of 26.10 - currently in proposed and waiting for final architecture builds before migrating to the release pocket.
When the monitor is turned off and the computer remains unused for an extended period (About 30min ~ 60min), Crystal-Dock and Budgie-Panel will disappear. Fix this bug promptly as it significantly impacts user experience. Thanks!
ubuntu@master:~$ <sys>:0: Warning: ../../../gobject/gsignal.c:1690: parameter 1 of type 'SynapseResultSet' for signal "SynapseDataSink::search-done" is not a value type
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:19.396: gtk_label_set_text: assertion 'GTK_IS_LABEL (label)' failed
INFO:root:start
INFO:root:Popover created
INFO:root:Fetcher started
** Message: 21:45:19.527: libsession.vala:45: DESKTOP_AUTOSTART_ID not set, session registration may be broken (not running budgie-desktop?)
(showtime-desktop:1322233): Gdk-CRITICAL **: 21:45:19.881: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.187: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.188: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.188: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.188: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.188: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.188: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.188: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.188: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.188: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.188: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.188: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
(budgie-panel:1321380): Gtk-CRITICAL **: 21:45:21.188: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
ubuntu@master:~$
ubuntu@master:~$ <sys>:0: Warning: g_bytes_compare: assertion 'bytes1 != NULL' failed
update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0 0): cannot write to "/var/lib/snapd/hostfs/usr/local/share/doc" because it would affect the host in "/var/lib/snapd"
update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot write to "/var/lib/snapd/hostfs/usr/share/gimp/2.0/help" because it would affect the host in "/var/lib/snapd"
update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot write to "/var/lib/snapd/hostfs/usr/share/xubuntu-docs" because it would affect the host in "/var/lib/snapd"
Missing chrome or resource URL: chrome://browser/skin/icons/system-users-symbolic.svg
check your processes - if its budgie-polkit-dialog spinning to 100% then that’s a known bug that is currently going through the SRU process. i’ve validated the fix and Canonical should release the fix in a week or so time.
First post updated with more details around the labwc updates and the 26.10 release of our budgie applets via budgie-extras.
Note - the wayland-test PPA has these same updates backported for 26.04 as well.
We’ll make a decision closer to release whether we’ll resurrect officially the ubuntu-budgie/backports PPA for 26.04 users so that they can use similar software as 26.10 end-users.
Regarding this, here is the error message the terminal has been displaying every time Stingray is updated for some time now:
Atteint : 7 https://ppa.launchpadcontent.net/ubuntubudgie-dev/wayland-test/ubuntu stonking InRelease
Err : 7 https://ppa.launchpadcontent.net/ubuntubudgie-dev/wayland-test/ubuntu stonking InRelease
Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 9A31450255A9A7E43DEB5ECBBCD74C7139A912F9 is not bound: No binding signature at time 2026-06-12T22:46:08Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Canonical are migrating/enforcing from sha1 to sha256 for PPAs - dunno when all of this is supposed to be resolved.
Current workaround:
sudo nano /etc/apt/apt.conf.d/99disable-sqv
Paste the following
APT::Key::GPGVCommand "1";
Save and close
Thanks, guru—it worked! 
Looking into this a bit further it seems the merge window this cycle from Debian to Ubuntu has pulled in the sqv package (what that is I have no idea) - this has a much stricter view of the signing keys Canonical uses on launchpad.
The TL;DR; - its a Canonical issue for the moment - I would imagine as we move closer to the release more people will starting raising flags around this area.
Tweaks and tucks.
Updated our meta package ubuntu-budgie-desktop to install wmenu, rofi, bemenu.
Whole screensharing for Matrix meetings should now be possible - just choose the screen on the menu displayed when you hit the screenshare button.
I don’t think wlroots/labwc supports per window screensharing but looking around it appears to be on the road-map.
Separately noted that xwayland had disappeared from recent ISOs. I’ve readded this to our environment package. Hopefully this will also fix the issue about the menu taking 10 seconds to appear when you click on the applet in the panel.
I believe now the daily is now feature complete for this cycle.
It contains the stonking stingray default wallpaper and a fix for the budgie-applications-menu opening issue.
v10.10.3 of budgie-desktop will miss this cycle due to upstream release dates not coinciding with Ubuntu freeze dates. We’ll make v10.10.3 available in the testing PPA for 26.04 and 26.10 users in due course - will be part of the 27.04 testing thread.
I’m aware of the plymouth splash screen missing - dunno why at this point. To be investigated.
Latest budgie-artwork updates has fixed plymouth and also the default user icon shown on the login screen.
Basically this release is now complete - just bug-fixing where necessary.
We’ll be preparing formally the budgie+wayfire offering in a release backports PPA together with the upcoming budgie-desktop 10.10.3 release - lots of nice goodies in that release which will form the UB 27.04 release.
The beta release is this week with first iso’s late on monday or sometime on tuesday. Would love more help folks with testing … and importantly entering thosr results on the ubuntu website.
If you can help, please shout. Happy to help folks / walk them through what to do.
It isn’t the final beta. Release team call it the beta RC. Missing latest kernel.
Beta release announced as the 1st Oct
Go test… feedback.
First official beta build is now avaliable to test
Always the same problem with the installer: when you select “French” and test the suggested keyboard by typing “azé,” the output is in QWERTY mode.
If you go to the next screen and then go back, the output is in AZERTY mode this time. 
sudo apt update
[sudo: authenticate] Password:
Hit:1 http://fr.archive.ubuntu.com/ubuntu stonking InRelease
Hit:2 http://fr.archive.ubuntu.com/ubuntu stonking-updates InRelease
Hit:3 http://fr.archive.ubuntu.com/ubuntu stonking-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu stonking-security InRelease
Get:5 https://ppa.launchpadcontent.net/ubuntubudgie/backports/ubuntu stonking InRelease [17,0 kB]
Err:5 https://ppa.launchpadcontent.net/ubuntubudgie/backports/ubuntu stonking InRelease
Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 237694670F1068D89D7EA18BBB53052A24597C20 is not bound: No binding signature at time 2026-09-27T11:58:14Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Warning: Signature verification failed: https://ppa.launchpadcontent.net/ubuntubudgie/backports/ubuntu stonking InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 237694670F1068D89D7EA18BBB53052A24597C20 is not bound: No binding signature at time 2026-09-27T11:58:14Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Error: The repository 'https://ppa.launchpadcontent.net/ubuntubudgie/backports/ubuntu stonking InRelease' is not signed.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
Installing additional applets from Budgie Welcome also results in an error message. 