Package Details: gtk2 2.24.33-5

Git Clone URL: https://aur.archlinux.org/gtk2.git (read-only, click to copy)
Package Base: gtk2
Description: GObject-based multi-platform GUI toolkit (legacy)
Upstream URL: https://www.gtk.org/
Licenses: LGPL-2.1-or-later
Provides: libgailutil.so, libgdk-x11-2.0.so, libgtk-x11-2.0.so
Submitter: City-busz
Maintainer: City-busz
Last Packager: City-busz
Votes: 41
Popularity: 27.11
First Submitted: 2025-10-28 08:37 (UTC)
Last Updated: 2025-10-28 09:01 (UTC)

Latest Comments

1 2 3 Next › Last »

micwoj92 commented on 2025-11-24 23:05 (UTC)

@City-busz from the still open issue pop-gtk-theme package. https://gitlab.archlinux.org/archlinux/packaging/packages/pop-gtk-theme/-/issues/1

Better probably if gtk2 optdeps were removed from it.

City-busz commented on 2025-11-24 17:16 (UTC)

@micwoj92, the pixbuf engine was always included in the gtk2 package. I can see no strong reason to add it to provides=().

FabioLolix commented on 2025-11-24 17:03 (UTC)

@OzzyHelix this will not be added to chaotic aur, see https://github.com/chaotic-aur/packages/issues/3963#issuecomment-3513815909 Unfortunately GTK2 has been EOL since 2020, so this is not right for us to add

micwoj92 commented on 2025-11-24 16:54 (UTC)

@City-busz, could you implement https://gitlab.archlinux.org/archlinux/packaging/packages/gtk2/-/issues/1 ?

OzzyHelix commented on 2025-11-24 13:56 (UTC)

is there any interest in having this on the chaotic aur? I know that we are retiring gtk2 but I know some apps still need it like davinci resolve for example

merlock commented on 2025-11-18 23:38 (UTC)

FWIW, it built fine in a clean chroot for me.

D3SOX commented on 2025-11-15 18:20 (UTC)

No, only adding that fails with the same gettext msgfmt error

Lone_Wolf commented on 2025-11-15 18:18 (UTC)

I notice 2 changes there : disabling LTO and reducing optimization level .

Has just using options=(!lto) been tested ?

D3SOX commented on 2025-11-15 17:21 (UTC)

Claude already suggested using -j1 didn't make a difference. Not sure if you read my comment about the working PKGBUILD

andreas_baumann commented on 2025-11-15 12:59 (UTC) (edited on 2025-11-15 13:05 (UTC) by andreas_baumann)

Interesting, borked toolchain and/or memory issues (or general hardware issues) come to my mind now.. :-)

I also built in a new chroot with gcc 15.2.1, so I doubt it is the toolchain..

gdb info <pid> should give some info, with debug symbols maybe there is a stacktrace, where the thing fails. Also, you can try to build with '-j1' in makepkg.conf instead of parallel, maybe the presure on the system is lower, so the build has a chance to succeed.

1 2 3 Next › Last »