Neui

> > I guess there is some kind of "race" of an name being acquired or something. > > They are calling it at some point late in their main...

Probably it wants to say the *runtime* used (Gnome Platform v41) is End of Life, not GTG itself. Upgrading to a newer Gnome Platform runtime [currently doesn't work](https://github.com/getting-things-gnome/gtg/issues/846) because of...

It should work, assuming it is using Flatpak/Flathub.

While this is still open and didn't decided yet what to do, I started to create a library to make the bridging easier and to demo it: https://pypi.org/project/glib-log-bridge/ (Still in...

Can you run gtg in `gdb` (like `gdb --args gtg --debug`), and when it crashes, type `bt` and enter, and copy-paste the printed stuff (depending on the size gdb used...

Oh I forgot since gtg is running via python (an separate interpreter), you need to run something like `gdb --args python3 /usr/bin/gtg --debug`

Can you test a possible workaround for me? Open `~/.config/gtg/gtg.conf` in an plain-text editor such as GNOME editor, vim or whatever you like, and under `[browser]`, find a line `font_name...

Why? From what I can see, it adds nothing for us (unless mesen wants the pkg-config files?). In fact, we could remove `libsecret-1.0` because `gir1.2-secret-1` already depends on it (according...

`.in` files are to be post-processed (usually by the build system). In this case, it is for the version (replacing `@VCS_TAG@` with the version). I don't like this solution because...