Linux: Quit from the dock only minimizes a visible GAIA window

Open Beginner friendly
  • Is something wrong?
#7,228 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, linux, node.js, python
Domain
desktop, devtools

Research direction

Start with src/gaia/apps/webui/services/quit-guard.cjs and inspect attachWindowGuards, especially the dockQuit condition described in the issue. Reproduce the steps on GNOME with a visible, focused GAIA window, then verify that choosing Quit from the dock exits GAIA on the first attempt.

Written by the indexing model from the issue text.

Description

bug electron needs-human p3

Dock > Quit on a visible GAIA window only minimizes it; a second Quit is needed.

Steps

  1. Stock GNOME, no tray extension, GAIA window open and focused.
  2. Open the overview, right-click GAIA in the dock, choose Quit.

Expected: GAIA quits.
Actual: The window minimizes ('Window minimized; no tray to hide it in'), GAIA keeps running with its dot in the dock. Choosing Quit again quits it. PR #6868 lists this as a known limit; the first-close notice tells users to 'right-click GAIA there and choose Quit', which then takes two tries when the window is showing.

Build: v0.26.0-rc18, fresh isolated profile (Fedora 44 under WSL, GNOME Shell 50, AppImage)
Found by: release test of v0.26.0-rc18, finding F55

🔍 Technical details
  • Suspected area: src/gaia/apps/webui/services/quit-guard.cjs attachWindowGuards: dockQuit is only true when the window is already minimized and unfocused.
  • Related PRs in this release: #6868
Dominant language
Python
Stars
1.6k
Forks
169
Avg merge
15h 33m
Merged PRs (30d)
832

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 amd/gaia

All issues in amd/gaia

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.