Cairn
NousResearch/hermes-agent

Race condition on desktop app relaunch teardown

Cluster 107671 · apps/desktop. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

A race condition on the desktop app allows a new instance to launch before the prior one finishes tearing down, which can crash GNOME Shell. The accompanying fixes add a wait for teardown completion before relaunch.

Open issues1

  • Issue#107671Desktop: relaunching Hermes (e.g. right after 'hermes update') while a prior instance is still tearing down can crash GNOME Shell and kill the whole session

Open PRs1

  • PR#128506fix(desktop): wait for prior instance teardown before relaunch (#107671)

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #107690 fix(desktop): wait for prior instance teardown before relaunch · superseded by another PR
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
apps/desktop
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/107671.json
cluster/107671.md