# GTK GTK is a free, open-source, cross-platform widget toolkit for building applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## GTK 4.24 Released With Better Fractional Scaling, More Precise GDK Frame-Clock DevFeed: [GTK 4.24 Released With Better Fractional Scaling, More Precise GDK Frame-Clock]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-12T10:52:32Z Content type: news Language: en Sources: [Phoronix]() Topics: [GTK](), [Wayland](), [SVG](), [Android](), [bug]() Tags: [android](), [bug-fixes](), [desktop](), [desktop-linux](), [feature](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [release](), [svg](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview GTK 4.24 is a stable feature release that improves fractional scaling, frame timing, reduced-motion behavior, SVG support, and Wayland integration. It also includes Android frame-timing improvements and many bug fixes, while session save and restore has moved to GTK 4.26. ### Source excerpt GTK 4.24 released on Friday as the newest stable feature release to the GTK4 toolkit. It's quite a nice update to GTK4 for pairing with next week's GNOME 51 desktop release... ## Supporting Wayland's XDG activation protocol with Gtk/Glib DevFeed: [Supporting Wayland's XDG activation protocol with Gtk/Glib]() Original publisher: [Read original article]() Author: Wladimir Palant Published: 2026-02-03T10:55:20Z Content type: tutorial Language: en Sources: [Almost Secure]() Topics: [Wayland](), [GTK](), [implementation](), [browser]() Tags: [application](), [browser](), [protocol](), [required](), [using](), [wayland]() ### AI overview This tutorial explains how Wayland's XDG activation protocol transfers focus between applications with consent, and documents its implementation in Gtk/Glib. It covers activation tokens, Gio.AppInfo launch contexts, StartupNotify, and manual environment-variable handling. ### Source excerpt One of the biggest sore points with Wayland is its focus stealing protection. The idea is good: an application should not be able to bring itself into focus at an unexpected time, only when the currently active application allows it. Support is still lacking however, which might also be due to Gtk/Glib implementing the required XDG activation protocol but not really documenting it. It took me a bit of time to figure this out without any public information, this article will hopefully make things easier for other people. Contents How the XDG activation protocol works State of implementation in Gtk/Glib Starting applications via Gio.AppInfo Starting applications by other means How the XDG activation protocol works The main idea behind the XDG activation protocol is that focus transfer from one application to another requires consent. With X11 a file manager could just launch the browser for an HTML file and the browser would immediately take focus, even if that browser was already running. With Wayland the file manager has to indicate that the browser is allowed to take focus. It does that by giving the browser its XDG activation token, typically via XDG_ACTIVATION_TOKEN environment variable. The browser can then use that activation token to prove consent and take focus. For this to work the protocol has to be supported on both ends: the file manager must know how to retrieve an activation token and pass it on via XDG_ACTIVATION_TOKEN environment variable, and the browser has to know how to use that token. State of implementation in Gtk/Glib The receiving side has been implemented in Gtk with merge request 7118 and is available starting with Gtk 4.14.6 and 4.15.1. This is the unproblematic part: it is handled automatically and doesn't require the application developer to change anything. The sending side has been implemented in Gtk with merge request 3502 and Glib with merge request 3090, so it is available starting with Gtk 4.10.0 and Glib 2.75.1. This is the part wh ## What's new with Himitsu 0.9? DevFeed: [What's new with Himitsu 0.9?]() Original publisher: [Read original article]() Author: August 8 Published: 2025-08-08T00:00:00Z Content type: article Language: en Sources: [Drew DeVault]() Topics: [Linux](), [Security](), [ui](), [GTK]() Tags: [linux](), [release](), [security](), [ui]() ### AI overview The article reviews Himitsu 0.9, a Linux secret storage manager that stores passwords and other secrets with associated metadata. It highlights the new hiprompt-gtk GTK4 prompter, implemented in Hare, and notes that Himitsu and its cryptographic dependencies have not been independently audited. ### Source excerpt Last week, Armin and I worked together on the latest release of Himitsu, a "secret storage manager" for Linux. I haven't blogged about Himitsu since I announced it three years ago, and I thought it would be nice to give you a closer look at the latest release, both for users eager to see the latest features and for those who haven't been following along.1 A brief introduction: Himitsu is like a password manager, but more general: it stores any kind of secret in its database, including passwords but also SSH keys, credit card numbers, your full disk encryption key, answers to those annoying "security questions" your bank obliged you to fill in, and so on. It can also enrich your secrets with arbitrary metadata, so instead of just storing, say, your IMAP password, it can also store the host, port, TLS configuration, and username, storing the complete information necessary to establish an IMAP session. Another important detail: Himitsu is written in Hare and depends on Hare's native implementations of cryptographic primitives - neither Himitsu nor the cryptography implementation it depends on have been independently audited. So, what new and exciting features does Himitsu 0.9 bring to the table? Let me summarize the highlights for you. A new prompter The face of Himitsu is the prompter. The core Himitsu daemon has no user interface and only communicates with the outside world through its IPC protocols. One of those protocols is the "prompter", which Himitsu uses to communicate with the user, to ask you for consent to use your secret keys, to enter the master password, and so on. The prompter is decoupled from the daemon so that it is easy to substitute with different versions which accommodate different use-cases, for example by integrating the prompter more deeply into a desktop environment or to build one that fits better on a touch screen UI like a phone. But, in practice, given Himitsu's still-narrow adoption, most people use the GTK+ prompter developed upstream. U ## Mobian's Early 2025 Developments: Debian Packages, Device Support, and a New Login Screen DevFeed: [Mobian's Early 2025 Developments: Debian Packages, Device Support, and a New Login Screen]() Original publisher: [Read original article]() Author: Mobian team Published: 2025-02-19T00:00:00Z Content type: article Language: en Sources: [Mobian's Blog]() Topics: [Mobile](), [Debian](), [GTK](), [kernels](), [Wayland]() Tags: [adaptive](), [debian](), [kernels](), [mobile](), [patches](), [wayland]() ### AI overview The article reviews recent Mobian developments, including new device support, improved Debian and Mobian packages, plans to reduce the Mobian package repository to mostly Mobian-specific and hardware-support packages, and progress toward a new default mobile login screen. ### Source excerpt Over the past few months, and especially since the last holiday season, many exciting things have happened in Mobian: new devices are (about to be) officially supported, many new and improved packages have made their way into both Debian and Mobian, and we're getting ready for our next stable release! Towards a "device-specific only" repository Thanks to the involvement of upstream developers (by either accepting or writing patches to ensure their applications can be used on mobile devices) and the work of the relevant Debian teams, many GNOME and KDE apps were made adaptive and could be uploaded to the main Debian archive without any additional downstream patch. This allowed us to drop (almost) all of the applications we were distributing through the Mobian package repository: Evince has been replaced with Papers, Loupe is now used instead of EOG and our main camera app is now Snapshot, all available directly from Debian! GNOME Text Editor now works well enough on mobile devices, as do Software and Settings We plan on getting rid of the remaining few ones before the Trixie release: Millipixels (Librem 5 camera app) will be replaced by Megapixels v2 once it hits the Debian archive wake-mobile will likely be dropped as it's no longer maintained, and upstream offers .deb packages for download anyway Except for a patched version of GTK 3 which we will keep maintaining until Phosh is ported to GTK 4, this means all packages in the Mobian archive will be either Mobian-specific (mainly metapackages) or hardware support packages (kernels and device-specific tweaks). A better tomorrow greeter Another major milestone we're about to reach is the move to a new default login screen: back in 2022, we decided that user session management on mobile devices shouldn't get any special treatment, and we should rely on a "display manager" similar to GDM/LightDM/SDDM, for instance. This would bring many benefits, the most prominent ones being multi-user setups for those who need it (e.g ## postmarketOS Release: v21.06 Service Pack 3 DevFeed: [postmarketOS Release: v21.06 Service Pack 3]() Original publisher: [Read original article]() Published: 2021-10-10T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [Mobile](), [Kernel](), [Pinephone](), [Qualcomm](), [GPU](), [GTK](), [Firewall]() Tags: [firewall](), [gpu](), [kernel](), [linux](), [mobile](), [pinephone](), [postmarketos](), [qualcomm](), [release]() ### AI overview postmarketOS v21.06.3 is a stable service pack containing backported features and fixes. It updates Sxmo and Tweaks, improves modem and GPU support for some devices, fixes hotspot functionality with the firewall enabled, and adds optional GTK 3 and GTK 4 themes. ### Source excerpt New month, new service pack! As always, new features and fixes have been backported from postmarketOS edge to the stable version after tough testing by our tough community members on edge. Overview Sxmo 1.5.2: as usually we've coordinated with the Sxmo team on what should be in the service pack, and thanks to them, got Sxmo 1.5.2 in. This is the tried and tested 1.5.1 version from edge, with just minor extra fixes on top. Tweaks 0.8.1 has a new sound panel, better notch support, some bugfixes for the background daemon and fixed touch navigation on the mobile layout. linux-postmarketos-qcom-sdm845 5.14 improves the OnePlus 6 and 6T ports: among other improvements it ships initial modem support and more GPU performance. ModemManager 1.18.2 was required for modem support in the SDM845 kernel. As nice benefit it should improve call and SMS handling. NetworkManager 1.32.10 was backported to fix hotspot functionality while having the firewall enabled. postmarketos-theme can now be installed to get GTK 3 and GTK 4 postmarketOS themes (see photo). Details ModemManager This release backports the calling stack from edge. The new release of ModemManager brings a lot of improvements for the devices supported in community and will help a lot with the stability of the modem when the PinePhone awakes from deep sleep. This release also adds support for the modem in Qualcomm Snapdragon 845 devices. The full calling functionality on those devices is not working yet but it means that at least mobile data and SMS is usable. postmarketos-theme This release also includes the new postmarketOS theme as an optional package. This currently contains a GTK 3 and GTK 4 theme which is based on Adwaita but replaces the standard blue highlights in the theme with postmarketOS green. There's also the oled and paper variant of the theme that are completely black and completely white. This will mainly look great on oled displays, as the name suggests. It's possible to try this on your own device now b ## GTK, fast lexer, money, deep testing, and our first commercial product DevFeed: [GTK, fast lexer, money, deep testing, and our first commercial product]() Original publisher: [Read original article]() Author: Unknown (noreply@blogger.com) Published: 2020-03-20T19:00:00Z Content type: article Language: en Sources: [Red]() Topics: [Red](), [GTK](), [Testing](), [reactive]() Tags: [automated](), [bug](), [code](), [experimental](), [floating-point](), [gui](), [identifier](), [implementation](), [money](), [operating-systems](), [reactive](), [testing]() ### AI overview A Red team update covering progress on GTK support and a fast lexer, automated view testing for GUI bugs, and new datatypes including the planned money! type for accurate financial calculations. ### Source excerpt It's been a busy start to the year for the team. Work has continued on many fronts, and we have some new team members helping us to keep the momentum going. We announced in January that GTK and the Fast Lexer were close, and they are even closer now. The hard part about making announcements is that some of this work is unpredictable and changes in scope after we do. Or the world steps in and a pandemic throws a wrench into your plans. @bitbegin has done an enormous amount of work on the GTK branch. You can check out the GTK branch to see some of what goes into supporting a new GUI system. The more features we include in Red, the more that have to be ported and maintained. Unfortunately, most operating systems and UI systems have large, complicated sets of APIs and interactions. Because GUI systems are so complex, and Red not only has to handle them, but also adds its own reactive framework, there are more places for bugs to hide. And users are involved, which is the worst part. They do nothing but cause problems. To that end, in addition to his normal deep diving and bug hunting, @hiiamboris has been working on an automated view test system, which is no small feat. @9214 has joined him on the hunt, and we will squash a good number of bugs for our next release. The fast lexer was in near-final testing when we decided that it was worth delaying its merge in order to incorporate some new lexical forms that we had planned to include. Then we looked at some old tickets related to modulo and division operators, and a couple lexing questions came up related to tag!. Suddenly the fast lexer work was back in code mode. New lexical forms usually means new datatypes, and that's the case here. New Datatypes One we've expected for some time, and thanks to @9214 it's now a reality. Money! is coming. There is a branch for it, but no need to comment at this time. There are a few features, like round still to be completed, but the bulk of the work is done. @BeardPower did some great ## November 2019 in Review DevFeed: [November 2019 in Review]() Original publisher: [Read original article]() Author: Unknown (noreply@blogger.com) Published: 2019-12-04T22:07:00Z Content type: opinion Language: en Sources: [Red]() Topics: [Red](), [Testing](), [GitHub](), [GTK]() Tags: [community](), [contributors](), [review](), [testing]() ### AI overview Red's November 2019 review highlights restored historic automatic builds, Red's addition to Stackshare, plans for beta testers for a new Red-built product, a proposal for standardizing series evolution, and more than 60 commits to the GTK branch. ### Source excerpt Welcome to December, friends of Red. It's an intent and focused time of year as we wind down 2019, and the core team is making important moves (sometimes literally!) to set us up for an ambitious 2020. But first, here are just a few things that happened in November. First and foremost, it's always great when community members help compile resources for use by others, and we'd like to acknowledge @rebolek for his excellent compendium of historic automatic builds: https://rebolek.com/builds/ (they weren't available for a hot minute, but now they're back). They can be useful if you're in need of a previous version for a specific project. Of course, you can always go here for Red's daily automated builds. But seeing as how we've a goal of being a self-sustaining, self-selecting group of do-ers, this spirit of providing collective resources is perfectly aligned with the Red-Lang we always want to be. From the community, to outreach: thanks to community member @loziniak, Red is now on Stackshare, so be sure to follow us there and chime in. As a repo with 4.1k GitHub stars (and infinite possibilities), Red has a lot to offer the wider community of developers and engineers, and Stackshare is a great place to help compare and contrast us with other languages. Now, a challenge! In the coming new year we'll be needing beta testers willing to lend their expertise in refining a new product built with Red. You read that right! If you think you'd like to be one of the contributors to spearhead a move into our next phase, we want YOU! Drop a line to @greggirwin to get in on the ground floor. An appreciation to @hiiamboris for his deeply thought out proposal regarding "series evolution," a framework for standardizing and testing the functions we use in Red for manipulating series. Design is hard, and we have a number of initiatives in the works taking a lot of brain power right now. Over 60 commits were made to Red's GTK branch in November, making it almost ready for "prime time." T ## Software tutorials on Bash completion, Ruby GTK, Linux text processing, and API mocking DevFeed: [Software tutorials on Bash completion, Ruby GTK, Linux text processing, and API mocking]() Original publisher: [Read original article]() Author: Lazarus Lazaridis Published: 2019-09-12T21:00:00Z Content type: article Language: en Sources: [Lazarus Lazaridis]() Topics: [Bash](), [Ruby](), [GTK](), [Linux](), [developer tooling](), [Sorting](), [API](), [Docker Image](), [To-Do]() Tags: [api](), [bash](), [development](), [docker-image](), [friday](), [linux](), [ruby](), [sorting](), [tool](), [tutorial]() ### AI overview A roundup of tutorials covering Bash programmable completion, a GTK ToDo application in Ruby, composing effective emails in a software-development context, removing duplicate Linux file lines with awk, and dynamically mocking API endpoints with DuckRails. ### Source excerpt A tutorial for adding tab completion to your scripts using the Bash Programmable Completion functionality. A tutorial for creating a simple GTK ToDo application with Ruby fs How to write better emails Tips for composing effective emails avoiding misunderstandings with examples from the software development world. How to remove duplicate lines of a file in Linux without sorting or changing their order (awk one-liner explained). ## Fedora 17 Tweaks DevFeed: [Fedora 17 Tweaks]() Original publisher: [Read original article]() Published: 2012-07-07T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [Fedora](), [GTK](), [browser](), [Terminal](), [Vim]() Tags: [chromium](), [fedora](), [file](), [fonts](), [gnome](), [hacks](), [icons](), [installation](), [post](), [terminal]() ### AI overview A collection of post-installation tweaks for Fedora 17, covering GNOME settings, fonts, themes, extensions, and a workaround for slow Nautilus startup. ### Source excerpt A collection of post-installation fixes and hacks