Firefox is taking that icon from your GTK theme. And that’s the maximize button in the Papirus theme. So this is intended behavior.
You’d have to modify the theme or tell Firefox to use a title bar to fix it.
Are you using an icon theme? Papirus?
Probably the biggest one is the next piece of the Wayland session restore puzzle clicking into place: David Edmundson has implemented support for the
xx-session-management-v1Wayland session restore protocol in Qt 6.10! This means that software built on top of Qt 6.10 (for example, Plasma and KDE apps) will be able to start implementing the protocol themselves. Once they do, then finally real session restore will work on Wayland
I hope we’re able to opt out of apps positioning their own Windows. My favorite thing about Wayland is that apps can’t control where their windows open, so they always open in a consistent location chosen by the compositor.
Annoys me whenever I use Windows, MacOS, or Xwayland apps that open up in seemingly random locations.
Clickbait. The VP Engineering for Ubuntu made a post that he was looking into using the Rust utils for Ubuntu and has been daily driving them and encouraged others to try
It’s by no means certain this will be done.
Overall, I don't think Mozilla is wrong. Without the Google Search deal, Firefox will have less resources to build a competent browser.
But Mozilla has also done a poor job at becoming financially stable without this search deal. It also doesn't help that Mozilla's CEO's salary keeps going up in spite of the declining market share.
It would have been nice is Mozilla was able to fill a niche like Proton: building a suite of secure and private services. But instead they're moving towards advertising.
I'm not going to deny that he can act aggressively, but his point is still valid. The anti-Rust sentiments of some maintainers has slowed down the upstreaming of Rust into the kernel. It doesn't make sense to waste people's time by letting R4L limp along in its current state.
R4L either needs to be given the go-ahead to get things upstreamed, to the dismay of some Linux maintainers who don't like Rust, or R4L should be killed and removed from the kernel so we can stop wasting people's time.
Personally, I think killing R4L would be a major mistake. Android's Linux fork with Rust support has been a major success for Google and significantly cut down on vulnerabilities. And the drivers for Apple's M chips has been surprisingly robust given how new they are and for being reverse engineered.
Before Wayland, there was X Window System, created in 1984. X Window System was designed in a time where you had one good computer connected to multiple displays used by different people. X went through many versions but version 11 (X11) stayed around for a long time.
But the architecture just isn't good. It wasn't designed for modern needs. MacOS used to use X, but replaced it to fit modern needs. Windows didn't use X, but they too updated Windows to fit modern needs. But Linux and other OSs stuck with X for a lot longer, hacking it to make it work. Honestly, it's amazing how well it does work.
But isn't not great. It wasn't designed with security in mind, it doesn't do multi-monitor well. Behind the scenes, it considers everything to be one giant display; issues arise when it comes to mixed-dpi displays and when monitor refresh rates don't match. It's also just a bloated, old code base that people don't want to work on. Fixing X would not only be difficult, but would break compatibility.
So people got working on a modern replacement for X aiming to avoid its issues. Wayland is leaner, more opinionated, and designed for how modern hardware operates. Wayland itself is just a protocol (like X11), and there's many different implementations of that protocol: Mutter, Kwin, wlroots, smithay, Mir, Weston, etc. Meanwhile X11 pretty much only had one relevant implementation, Xorg. Wayland's diversity has its pros and cons. Pros include (1) you can create your implementation in any programming language you want rather than being stuck to just one, (2) an implementation can fill just the needs on the person making it rather than trying to generalize it for everyone. But cons include the fact that this fragmentation leads to scenarios where one implementation supports something that others don't and implementation-specific bugs.
Wayland's opinionated design is also draws criticisms. It gives a lot of control to the compositors rather than windows, which is how Xorg, MacOS, and Windows work. Nvidia's wayland adoption was also slow and terrible. It took many years to get it into the only decent shape it's in now.
That was there before 133, don’t remember the exact release that added it.
I don’t get why this sort of picture always gets posted and upvoted when it’s wrong for most distros nowadays.
The TLDR is that Microsoft released a secure boot update that blocked insecure versions of GRUB. This update was only meant to go out to Windows users since releasing it to dual booted users could break GRUB. However, it was accidentally also released to dual-booted users.
The fix involves disabling dual boot, running a command to reset secure boot, then re-enabling.
Blender's Wayland support is not great because they're doing stuff from scratch. They're not using an existing toolkit like GTK, Qt, Electron, or even something like SDL to get Wayland support.
But if you're using an existing toolkit things are much easier and support is automatically there, you just need to do testing to ensure everything works.
The common biggest things that still use Xwayland are Chromium based apps and programs running under wine/proton. Chromium has an experimental Wayland mode that works well enough, but definitely has some bugs, especially around windowing. Wine Wayland is in the works.
I’ve had no issues with the ProtonVPN flatpak on Fedora Silverblue.