{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreickthk7ex4co6ybzqejamxwirn2rw2l4h53uvdrqf7d7a2n3shqwm",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mklcie6ozh32"
  },
  "path": "/viewtopic.php?t=33381&p=272926#p272926",
  "publishedAt": "2026-04-28T17:55:03.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": ">\n> Regarding themes, I'm not a theme user, but I downloaded several from the Pale Moon Themes page and they all seemed to install and work on my GTK3 version. If there are some that don't work, they could be put into a separate section, noting that they are for people running the \"unrecommended GTK2 version of Pale Moon with its unmaintained GTK2 libraries that may ultimately need to be deprecated\" - something like that.\n\nAgree. Also, I don’t think Pale Moon themes are that popular among Linux users. The whole idea is to have a gtk theme (gtk4/gtk3/gtk2) that gives a consistent look to every gtk application on your desktop.\nOff the top of my head I can’t name a single application in Debian Stable that still uses gtk2. Maybe the LXDE environment.\n\n\n>\n> Which goes back promoting the GTK3 binary to the #1 GNU/Linux position on the Downloads page, and beginning to communicate _**something**_ to the users so they know that this distros-dropping-support train is about to hit them right in the teeth in a very short period of time, and they need to start thinking about planning (or changing plans) accordingly.\n>\n> From what you said earlier, it would appear that _EVEN IF_ you shipped a GTK2 runtime with Pale Moon, it still probably wouldn't run with all plugins, and you would have various glibc mis-matches, etc. You apparently can't just fix people's problems by adding all the libraries to the official Pale Moon binaries.\n\nStevo that builds Pale Moon for MX Linux (and antiX) has taken a sensible approach in my opinion.\nIn 2021 he built Pale Moon gtk2 for MX main repo and put Pale Moon gtk3 builds in MX test repo.\nIn 2023 he stopped doing Pale Moon gtk2 builds and put Pale Moon gtk3 builds in MX main repo. (No one complained about that).\nWhen AVX builds were introduced by Pale Moon devs, Stevo continued to build Pale Moon SSE2 for MX main repo and put Pale Moon AVX builds in MX test repo. (No one complained about that).\nWell, one forum member complained that official Pale Moon wouldn’t run and was advised to install from the MX repo instead. There were quite a lot of non-AVX CPUs produced even in recent years (mobile Intel Celeron).\nGtk2 was declared dead by Gnome in 2020. Compared to AVX, gtk2 seems like a non-event to me.\n\nThat being said the ability to build Pale Moon using Python3 seems to be a very positive development.\n\n* * *",
  "title": "Platform Development • Re: Future of GTK2 and Pale Moon",
  "updatedAt": "2026-04-28T17:55:03.000Z"
}