tmsteph. ← home

Open source · desktop UX

GNOME
Paper Cuts.

I love GNOME's design philosophy. This is a constructive list of the little interactions that still make the desktop feel less finished than the ideas behind it.

Not a complaint wall. Each item should be reproducible, specific, respectful, and useful to someone who might actually fix it.

The rule: Describe the thing you were trying to do, what you expected, what happened, and the smallest improvement that would make the computer disappear again.

Observed in real use

Current paper cuts

01

Rearranging monitors should not rearrange my workspaces

Observed on Debian forky/sid with GNOME Shell 50.2, Wayland, two displays.

Trying to do
Change which physical display sits on the left or right.
Expected
The monitors move. My virtual desktops and application grouping stay intact.
Actual
Applications were reassigned across workspaces when the monitor layout changed.
Why it matters
A physical desk adjustment should not reorganize the user's mental workspace.

Status: update installed; needs retest on GNOME 50.5.

02

Remember what I plug into the headphone jack

Observed with a Realtek ALC3204 combo jack and PipeWire/WirePlumber.

Trying to do
Plug ordinary headphones into the same laptop jack I use all the time.
Expected
Route audio to the headphones, using the last successful choice unless something actually changes.
Actual
GNOME asks whether the device is headphones, a headset, or a microphone each time. Dismissing the dialog still leaves audio working.
Why it matters
A repeated question that can safely be ignored is interruption without information.

Possible workaround: Auto Select Headset extension. Better fix: remember a per-jack choice and provide an easy override.

This idea has history

GNOME already had the right concept.

The archived GNOME Shell Annoyances page described annoyances as interactions that may not be direct bugs but are hard or annoying “by design.” That framing is worth reviving.

Ubuntu's old “100 Paper Cuts” project attacked the same class of small, cumulative usability problems. The goal here is to keep that spirit alive while linking every item back to the modern upstream process.

Turn irritation into contribution

How this list should work

  1. Reproduce the behavior on a current GNOME release.
  2. Search GNOME GitLab for an existing open or closed issue.
  3. Link the upstream issue here, or prepare one focused report.
  4. Record workarounds without pretending they are fixes.
  5. When something is fixed, move it to a solved section instead of deleting the history.