Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[flatpak] Gtk-warnings

Open
#82 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
fedora
Domain
desktop

Research direction

Reproduce the report with flatpak run io.github.ellie_commons.reminduck on Fedora and separate the Gtk warnings from the Mesa-Intel messages. The payload names no source file or test and does not define which warnings should be fixed, so clarify the expected outcome before locating the relevant application code.

Written by the indexing model from the issue text.

Description

  • v.: 2.2.0, as communicated by flathub.org; the version not even being communicated by the application itself.
  • OS: Fedora v. 43
  • DE: Gnome v. 49, Wayland session

Hello. Deluge of warnings related to Gtk.

$ flatpak run io.github.ellie_commons.reminduck

💲️ Command line mode started
 ✔️ Interface
✔️ Activated
Environment: GNOME detected!MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:949: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:981: FINISHME: support more multi-planar formats with DRM modifiers

(io.github.ellie_commons.reminduck:2): Gtk-WARNING **: 13:53:33.541: Trying to measure ReminduckMainWindow 0x55c7fe920040 for height of 457, but it needs at least 677

(io.github.ellie_commons.reminduck:2): Gtk-WARNING **: 13:53:33.566: Trying to measure GranitePlaceholder 0x55c7fe8eb1a0 for height of 251, but it needs at least 471

[...]
Dominant language
Vala
Stars
72
Forks
17
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elly-code/reminduck

All issues in elly-code/reminduck

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.