| Git Clone URL: | https://aur.archlinux.org/libadwaita-without-adwaita-git.git (read-only, click to copy) |
|---|---|
| Package Base: | libadwaita-without-adwaita-git |
| Description: | libadwaita; Includes a patch to not overwrite the system theme |
| Upstream URL: | https://gnome.pages.gitlab.gnome.org/libadwaita |
| Licenses: | LGPL-2.1-or-later |
| Conflicts: | libadwaita |
| Provides: | libadwaita, libadwaita-1.so |
| Submitter: | ich |
| Maintainer: | ich |
| Last Packager: | ich |
| Votes: | 27 |
| Popularity: | 0.69 |
| First Submitted: | 2022-04-08 09:57 (UTC) |
| Last Updated: | 2024-09-21 21:25 (UTC) |
Your latest update works. But the appearance of dark themes (e.g. Adwaita-dark) leads to a "gray" mush color instead of black. Is there a workaround for this? Update Reverting the GTK4 Version to 4:14.5 (from 4.16.2) resolves the issue.
Update 2 Still present @ GTK1:4.16.3. Dark colors are grayed out
Thanks for the notices. I updated to 1.6.0, which should fix these issues.
With version gtk4 1:4.16.1 GTK4 apps like gnome-calculator will not start:
gnome-calculator: symbol lookup error: gnome-calculator: undefined symbol: adw_spinner_new, version LIBADWAITA_1_0
Seems to broken since GTK 4.14.x (also broken if using the default libadwaita lib) on xfce4. It's a mess! Discovered with GTK 4.14.5
@ich upstream libadwaita updated before i've noticed your message to try your suggestion, and i first tried there
and i've noticed that with upstream libadwaita = 1.5.2 xsettingsd is working again!
@actionless This package only uses gsettings. Afaik gnome-settings-daemon is responsible to translate xsettings to gsettings. You may need to manually start that of you're not on gnome.
You could try gsettings get org.gnome.desktop.interface gtk-theme to see if your configuration gets propagated properly.
is the patch still actual?
i've tested it with several libadwaita apps (like baobab and easyeffects) - normal gtk4 apps and gtk3 apps are reacting on theme change via xsettingsd but libadwaita ones still react only if setting GTK_THEME env var for them
@ich: glib2-devel should only be a build dependency, not a runtime dependency.
@gromit Thanks for the notice. Just for claraification: The fix for this is adding ~glib2-devel~ as a dependency? I haven't updated glib2 yet, so could you check for me if that resolves the issue?
Edit: I added glib2-devel as a dependency, so this should be resolved. (The latest glib2 in my mirror was still 2.80.2, so I had to change mirrors)
I'm getting a build error for this package:
Program /usr/bin/glib-mkenums found: NO
src/meson.build:62:25: ERROR: Dependency 'glib-2.0' tool variable 'glib_mkenums' contains erroneous value: '/usr/bin/glib-mkenums'
This is a distributor issue -- please report it to your glib-2.0 provider.
See https://gitlab.archlinux.org/archlinux/packaging/packages/glib2/-/issues/7#note_190677 for a fix 👍
Pinned Comments
ich commented on 2022-04-08 10:17 (UTC) (edited on 2023-01-10 05:38 (UTC) by ich)
The version of libadwaita provided by this package will use the dconf-variable 'org.gnome.desktop.interface.gtk-theme' to load the theme. This is the same variable that other gtk4-apps (and gnome-tweaks) uses.
For this to work, your theme needs to support gtk4. There may also be some weird formatting until themes are updated to fully support the new widgets; The Arc-family of themes seems to already support most of libadwaita.
Since this replaces the system library, it will only work for apps that actually use it (that is, all apps in the main repo). You will still have to set GTK_THEME if you want to use Flatpaks / Snaps / Appimages
Edit: Please, never just report issues to other gtk projects while using this library. Please always check if the issue persists using extra/libadwaita, and report your issue only on this AUR package if it doesn't.