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

Abierto
#222 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
desktop

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
C
Estrellas
173
Forks
52
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de linuxmint/xapp

Todos los issues de linuxmint/xapp

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.