@mvidaldp pamac-gtk
seems to be a Manjaro package, so I can't test it on my system, but here's what I've gathered:
pamac-gtk
does not only depend on version 1.4.2
of libadwaita, but specifically the second epoch of it (this is what the 1:
means).
As far as I know, an AUR package cannot override a specific epoch of another package, so there is no way for me to update the PKGBUILD
to solve your problem.
I don't know why pamac-gtk
does this. I don't think there even was a first epoch of libadwaita 1.4.2.
Here's how you can solve this:
-
You could ask the maintainer of the package to set the version to something more reasonable (like
1.4.2
) if there is no reson to require the epoch. -
You could clone this repository, replace
'libadwaita>=1:1.4.2'
with'libadwaita>=1.4.2'
in thePKGBUILD
and runmakepkg -si
to installpamac-gtk
without the additional dependency. However, you will have to do this every time the package updates in the future.
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.