GTK-NoCSD: an LD_PRELOAD library to disable CSDs
While Libadwaita applications running in a GNOME desktop environment look great and nicely consistent, they look utterly out of place and jarring when run in Xfce, Pantheon, KDE, and others. The biggest reason for this is GNOME's insistence on using client-side decorations, which feel at home inside a GNOME environment, but out of place in envi
https://www.osnews.com/story/144473/gtk-nocsd-an-ld_preload-library-to-disable-csds/
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
PSA: Did you know that itβs **unsafe** to put code diffs into your commit messages?
Like https://github.com/i3/i3/pull/6564 for example
Such diffs will be applied by patch(1) (also git-am(1)) as part of the code change!
This is how a sleep(1) made it into i3 4.25-2 in Debian unstable.
My FOSDEM presentation ia now possible to watch online! π
https://fosdem.org/2026/schedule/event/JYGFRE-modular-in-the-daw/
A small talk about Cardinal's history/beginnings, differences vs Rack Pro and some tips&tricks.
See you all next year again!
You don't need to pay Apple or start a new subscription to unleash your creativity. We asked creatives what free software they use to get the job done and here are their picks.
A thread π§΅
@jimmysjolund @pscherbaum @ardour I would be interested to present something for sure, but not sure which project would be the best fit or have the biggest interest...
https://github.com/falkTX/Carla/ ? https://github.com/DISTRHO/Cardinal/ ? something more dev orientered like https://github.com/DISTRHO/DPF/ ?
A small update on the KXStudio repositories this month(ish).
Just a few updates, but added new "hamburger" distortion plugin.
https://kx.studio/News/?action=view&url=kxstudio-project-update-august-october-2025
@x42 what is your take on its quality vs other opensource implementations?
from the video it sounded as if everything else in opensource couldn't come close... π€
If you are π©πͺ German, you can now call many of your Bundestag members directly via https://fightchatcontrol.eu/ by clicking the "Call" button!
@amadeus @linuxaudioplugindevelopment
> This means that if a DAW does not offer X11 support (...) it neither can be run on X11 nor will X11 plugins work inside such a DAW
This is false, the 2nd part.
A wayland-only application cannot run under X11
But! a native wayland application can 100% load X11 plugin UIs without trouble, assuming XWayland is present.
Try it! If you have Carla and Wayland, run "carla -platform wayland" (ignore project file warning)
If the host calls into X11, it works
@amadeus @linuxaudioplugindevelopment yeah that is not quite correct...
> X11 applications and plugins work flawlessly on Wayland
add a "mostly flawlessly". the compatibility is not 100%, there are cases where it breaks.
> none of the popular plugin frameworks support Wayland directly
true-ish, not officially yet, but best to say its WIP. I am working on it for DPF and JUCE has unofficial implementation https://forum.juce.com/t/wayland-implementation-for-juce/66840/
(more on next message)
@pluto Bitwig does that, kinda. The engine is its own process and plugins go together with it, separate from the UI and session manager. This allows to protect against engine/plugin crashes. It's not really sandboxing though.
For true sandboxing flathub with audio plugins kinda does that right now, by loading plugins within that same sandbox. But it's quite inconvenient, apps from flathub do not see global/system-wide installed plugins (and if they do they break sandbox rules)
@pluto haha, I have bad news for you...
99% of DAWs and audio plugin hosts do no sandboxing or bridging.
But it's kinda expected, when we are dealing with 1000s of plugins that need to run in less than 0.5ms each. Dealing with context switching and thread sync across these many instances would waste time that could be better spent processing more plugins.
@valpackett why complicate things? my idea is just to use subsurfaces
my tests on https://github.com/falkTX/wayland-audio-plugin-test show its possible and works.
but now begins the long process of turning hacky tests into usable things.
Yay for audio plugins under Wayland.
Non-embedded type for now, but one step at a time we will get there.
Also, today I answered a question I had for a long time...
If an X11 host running under XWayland calls Wayland-native APIs manually, would it be able to load Wayland-UI based plugins?
The answer is yes - Carla running under Qt xcb "platform" can still show Wayland UIs.
The reverse is also true (Qt wayland "platform" with X11 UIs through XWayland)
Future is bright π