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

Organizer: clicking a GROMACS study blanks the window (black) for about 0.4 s

Open
#523 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
57/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c, linux
Domain
desktop

Research direction

Start in the Organizer tree selection handler and trace how selecting a GROMACS study rebuilds or lays out the main panel and when the first repaint occurs. Reproduce with the listed steps on Linux/GNOME/X11, then inspect the relevant event handling and rendering path. Done when switching between the study and another calculation no longer blanks the client area during the slow work.

Written by the indexing model from the issue text.

Description

Seen in the 2026-10-24 test round (dev build 63f1db9e, Linux, GNOME/X11, screen recording).

Clicking a GROMACS study in the Organizer's tree turns the whole client area black for about 0.4 s: menu bar, tree and table, everything except the toolbar and the run-state legend. A 7 s recording shows three such dark intervals, at about 1.4 s, 3.5 s and 5.6 s, each about 0.4 s long. Mean frame brightness drops from 214 to about 40.

Not yet investigated. Likely candidates: the study view rebuilds or re-lays-out the main panel while the event loop is blocked (GTK3 shows unpainted areas as black), or the selection change runs something slow before the first repaint. The fix should repaint before the slow work, or freeze the old content until it is done, rather than leave the window blank.

Steps: Organizer, a project containing a GROMACS study (New > GROMACS study), click the study in the tree, then another calculation, then the study again.

Dominant language
C
Stars
10
Forks
8
Avg merge
57m
Merged PRs (30d)
2

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 FriendsofECCE/ECCE

All issues in FriendsofECCE/ECCE

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.