#nocsd
gtk-nocsd
An LD_PRELOAD library to disable CSD in GTK3/4, LibHandy, and LibAdwaita apps.
aur.archlinux.org
September 27, 2026 at 10:43 AM
June 8, 2026 at 4:32 PM
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 environments that otherwise do not use them. On top of that, Libadwaita’s/GNOME’s CSDs can interfere with non-GNOME window managers and their functionality, causing a whole host of problems. But what if you could turn CSDs off? GTK-NoCSD is an LD_PRELOAD library to disable CSD in GTK3/4, LibHandy, and LibAdwaita apps. CSD is client side decoration, there is also server side decoration, SSD, both serving as the titlebar of windows. GTK3 adopted CSD, where this thick headerbar is used with application controls embedded.This continued into the platform library, LibHandy, then into GTK4 and the platform library of that, LibAdwaita. This looks good on Gnome and makes these applications alike, but looks off everywhere else and can potentially break window managers and remove window manager provided functionality. This library restores the server side decoration, getting back the window manager titlebar, and moves the controls from the CSD to under it, into the window content. ↫ GTK-NoCSD’s Codeberg page This isn’t the first attempt at such a solution, and certainly won’t be the last, and I’m glad they exist. Do note that if you decide to use this library, any problems or bugs you run into in an application ‘modified’ by it should never be reported to the application’s developer, but to the developer of this library. If you encounter a bug in an application modified by this library, test the application in its unmodified state to ensure it’s actually a bug in the application before reporting it to the application’s developer. Developers who choose to use client-side decorations are not responsible for bugs and issues arising from you removing the CSD. Keep that in mind. That being said, whatever pixels appear on your screen is entirely up to you as a user, and you have the right to theme, alter, butcher, or mangle whatever application is running on your computer. If you dislike the way CSDs look and feel on your computer, you can opt to resort to a solution like this one, and that’s entirely fair game. There’s packages for Arch, Fedora, and Gentoo, and of course, you can build it yourself. As for my personal opinion – well, let’s just say I prefer KDE for many, many reasons, and my disdain for CSDs is certainly one of them. Call me old-fashioned and out-of-touch, but I like the classic distinction between titlebar, menubar, and toolbar.
www.osnews.com
February 24, 2026 at 11:42 AM
No nevypadá to lépe?

Moc se mi ten hack nelíbí, ale co už…

https://codeberg.org/MorsMortium/gtk3-nocsd/src/branch/master/README.md
June 5, 2025 at 5:46 AM
gtk-nocsd-git
A small LD_PRELOAD library to disable CSD in GTK3, GTK4 and LibAdwaita apps
aur.archlinux.org
November 13, 2025 at 12:24 AM
GTK4-nocsd Mostly that is the case for me as well. But there are certain apps where there aren't too many other options. The 2 most popular native XMPP apps, Dino and Gajim both have forced CSD...

Origin | Interest | Match
GTK4-nocsd / General discussion / Xfce Forums
forum.xfce.org
October 23, 2025 at 2:03 AM