Mostly #wayland stuff around #gnomeshell, #gstreamer, #Firefox, #Pipewire, #libcamera, #linuxmobile - @collabora
Generally thing that make the Linux desktop use graphics hardware features. And sometimes random boosts.
Based in Berlin.
Member of the German green party.
| Gnome Gitlab | https://gitlab.gnome.org/rmader |
| FDO Gitlab | https://gitlab.freedesktop.org/rmader |
| Github | https://github.com/rmader |
| Mozzila Bugzilla | https://bugzilla.mozilla.org/user_profile?user_id=588045 |
Just want to quickly share with #linuxmobile folks that the new #libcamera softwareISP does indeed work with the #librem5 - and with a #PipeWire + #GStreamer pipeline. Here's a first image running Warp (from Flathub).
There's still some stuff to iron out to make this work reliably and ship to users - but things are falling into place.
For Gst/Gtk4/Tuba performance test purposes.
What I really like about #GNOME46 is that it turned out to be a great release for old and low-end devices. One of my test devices is Thinkpad T400. That hardware is over 15 years old and actually got faster over the last few years - especially this release.
One of my favorite improvements here, headed by Christian Hergert, was the boost to VTE. Terminals using #gtk4 are now much faster and responsive. I mean, damn, even switching tabs doesn't trigger a full redraw!
If you run Gnome, you can enable the opaque region overlay, which draws green or purple overlays over the content whenever Mutter is compositing - and shows the content normally when doing direct-scanount / zero-copy.
You can enable it via alt+f2 -> "lg" -> "Flags" -> OPAQUE_REGION
When things work correctly, you should get a purple overlay when in windowed mode or player controls are visible - and a normal image when fullscreen without controls.
I guess I should have elaborated a bit more why and what for I'm asking for testing. So my main goal is to find remaining cases where the output looks like one of the attached images, which are complete deal breakers for users.
These are usually driver bugs - in Mesa or the kernel - and optimally should get reported accordingly. But if you see something like this are you are not sure where to report it - please feel free to DM me!
