Font settings widget saves nonexistent font families without validation - apps silently fall back to arbitrary fonts

Offen
#222 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
python
Bereich
desktop

Rechercherichtung

Start with xapp/SettingsWidgets.py and inspect how FontButton binds Gtk.FontButton.font-name to GSettings; the issue reports that the chooser accepts arbitrary typed family names. Check what family validation is available through GTK, fontconfig, or Pango, and how the widget is reused by settings modules. Done means nonexistent families are refused or clearly flagged instead of being silently saved; the issue gives no test file to run.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Environment

  • Cinnamon 6.6.7 on Gentoo (upstream settings UI: cinnamon-settings -> Font Selection module)
  • python3-xapp 3.0.2 / xapp 3.2.2 (Python widget xapp/SettingsWidgets.py)
  • GTK 3.24.52

Steps to reproduce

  1. Open System Settings -> Font Selection.
  2. On any row (e.g. "Default font"), open the font chooser, type into the Family field a family that is not installed - for example DejaVu Sans Semi-Condensed (DejaVu Sans only ships a "Condensed" variant, not "Semi-Condensed") - and confirm.
  3. The typed string is persisted verbatim into the gsettings key:
    • gsettings get org.cinnamon.desktop.interface font-name -> 'DejaVu Sans Semi-Condensed 11'
    • the same happens for document-font-name, org.nemo.desktop font and titlebar-font.

Observed

  • The stored family cannot be resolved by fontconfig: fc-match "DejaVu Sans Semi-Condensed" returns LiberationSans-Regular.ttf.
  • GTK applications then silently render with a different, unrelated font. Because every app/toolkit resolves the fallback differently, the UI becomes inconsistent - some parts use the intended font, others a fallback, with no error or warning shown anywhere.

Expected

  • The font widget should validate the selected family against fontconfig (e.g. against the GtkFontChooser family list, or fc-list / Pango) and refuse or flag families that cannot be resolved instead of saving them.

Root cause

  • xapp/SettingsWidgets.py -> FontButton binds Gtk.FontButton.font-name directly to the gsettings key (Gio.SettingsBindFlags.DEFAULT) with no validation.
  • GtkFontChooser's family entry also accepts arbitrary typed family names, so any typo or non-existent variant (e.g. a width such as Semi-Condensed that the family does not ship) reaches the settings keys.

Notes

  • The invalid value is spread to all GTK apps at once: csd-xsettings reads org.gnome.desktop.interface font-name and publishes it as the XSettings Gtk/FontName key.
  • The widget is reused by many Mint settings modules, so this silent path is not specific to one app.
  • A repair/warning on startup when a stored font family cannot be resolved would help users who already have such values in dconf.
Vorherrschende Sprache
C
Sterne
173
Forks
52
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus linuxmint/xapp

Alle Issues in linuxmint/xapp

Ähnliche Issues

Weitere Issues zu C

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.