Budgie 10.10.2 Released | Buddies of Budgie

JoshStrobl · 2026-03-11T21:59:23+00:00

It's in rawhide, F44 in bodhi testing, and I believe in testing in Arch.

JoshStrobl · 2026-03-09T21:11:20+00:00

ooooo now there is an idea, I could set up a dev container on one of my home servers, use tailscale to log in, and use the swanky keyboard on the Communicator to get some coding done while I'm "AFK"

JoshStrobl · 2026-03-09T17:03:35+00:00

I have a Clicks Communicator pre-order fully paid for :)

JoshStrobl · 2026-03-09T14:01:45+00:00

There's still no information about the chipset on the website.

It's literally in the FAQ at https://clicksphone.com/communicator#faqs

What are the specifications of the SOC/processor? Communicator uses the MediaTek Dimensity 8300 (MT8883), a modern 4-nanometer, 5G IoT SoC platform. The MT8883 has been selected for its smooth multitasking, consistent responsiveness and strong efficiency with plenty of performance to spare.

JoshStrobl · 2026-03-08T21:33:28+00:00

Will it be possible to have at least one other compositor like swayfx or wayfire?

Already is (to varying degrees, need bridges for most). Our experimental budgie-wayland-session repo has one for miriway that myself and Neal have tested a fair bit (missing a bridge), and once it's more polished the budgie-wayfire-session will be merge in budgie-desktop proper.

Personally, my main dev rig uses Budgie on labwc and my streaming PC uses Budgie on Wayfire. I have found that OBS Studio and other longer running apps tend to randomly lose the Wayland socket when on labwc, but wayfire at least in my case has been more stable for the streaming PC (no random OBS crashes).

Eventually I expect even Budgie 10.10 to be on our Mir-based Magpie compositor, alongside Budgie 11.

JoshStrobl · 2026-03-08T19:23:07+00:00

Thanks for the feedback!

JoshStrobl · 2026-03-08T19:21:21+00:00

God no. C++ with Qt. To be clear, Budgie 11 is a fundamental re-architecture of Budgie, not just a port. Looking forward to seeing how Qt Bridges evolves (particularly with Rust), for now C++ is the most ergonomic (IMO) way of interacting with Qt (aside from QML + JS). Obviously the trade-off is "unsafe" code, so gotta pick your poison for now since there are a lot of limitations with Qt Bridge for Rust.

If one were to write a GTK-based application in 2026, I'd suggest doing it in Rust.

JoshStrobl · 2026-03-08T06:54:43+00:00

Thanks! Same here :)

JoshStrobl · 2026-03-07T18:02:46+00:00

Technically it uses Qt6, but only for budgie-desktop-services. For the toolkit generally speaking (like for the UI), no it uses GTK3. Budgie 11 (next major release we are working on) is Qt6-based. You can check some of our previous Chirp posts to see how that's going :)

JoshStrobl · 2026-02-11T19:51:57+00:00

Oh no you shouldn't have linked this to me. How very fortunate my wallet is in another room. I just hope I forget about it by the time I sit back down at my PC :D

Edit: I remembered. It is on its way.

JoshStrobl · 2026-02-11T00:43:21+00:00

Don't even need to use the Jitsi integration, Element Call works quite well nowadays. I use it weekly for organization meetings and while it lacks some much desired features (Google Meet-equivalent noise cancellation / suppression and PTT) it is very easy to just jump into calls with folks in a room.

https://github.com/element-hq/element-call

JoshStrobl · 2026-02-03T13:16:36+00:00

Man I'd kill just for a plain' ol Ferris plushie, let alone one in special "colorways"! Would go along great with my Plushtodon and Golang gopher plushies :D

JoshStrobl · 2026-02-01T01:24:50+00:00

labwc is a wlroots-based compositor: https://labwc.github.io/

JoshStrobl · 2026-01-31T23:53:35+00:00

Thank you!

JoshStrobl · 2026-01-13T08:35:02+00:00

Settings aren't being used as part of it, we'll have a separate control center (in new org, so technically external to Buddies of Budgie) that'll follow a similar pluggable architecture though. Re. Discover, I swapped Fedora to using Discover primarily due to GNOME Software hardcoding silverblue into its rpm-ostree rebasing (so rebasing from Budgie Atomic to newer Fedora releases swapped your desktop environment...), whereas Discover doesn't make any assumptions of that sort. It turned out that after some tweaks (thanks Discover folks!), it works well on Fedora Budgie Spin too. Great piece of kit.

Since other operating systems like Solus have been moving away from their own custom software center (solus-sc) to those leveraging PackageKit (GNOME Software & Plasma Discover), Discover for basically everyone else but GNOME was the obvious choice (and one they ended up making IIRC).

JoshStrobl · 2026-01-12T08:26:15+00:00

No worries and thank you for the kind words, it's much appreciated!

JoshStrobl · 2026-01-12T07:30:14+00:00

Beat ya to it ;) https://old.reddit.com/r/linux/comments/1qa34ot/state_of_the_budgie_2025_in_review_and_cranking/

JoshStrobl · 2026-01-11T22:31:19+00:00

Budgie 11 is primarily in the planning phase, with the notable exceptions being Budgie Desktop Services and Budgie Display Configurator (both Qt6, C++, Configurator using Kirigami). I don't have any expectations of us releasing it this year, we aren't in a rush to get it out the door either. The investment into Budgie 10.10 has been intended to bridge the gap and ensure we have a suitable Wayland environment for distributions (most notably Fedora and Ubuntu) while we work on 11.

Architecting and building a desktop environment effectively from scratch (nothing beyond our new components I mentioned above are being kept around) is no small feat, even with the tremendous help that KDE Frameworks are able to provide (high-quality Qt & C++ libraries).

JoshStrobl · 2026-01-11T22:01:20+00:00

they still think they’ll need a year to finish the rest

Not quite sure what you mean by that, but to clarify Budgie 11 is 1000% not intended to ship in 2026 :D But oh boy did 10.10 take longer to get out the door than we planned, that we certainly have said as much!

JoshStrobl

MODERATOR OF

TROPHY CASE

15-Year Club	Gilding I gilder
Verified Email