gnome-shell spams the journal with `Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value` multiple times every second for users using the lt_LT locale

Bug #2064656 reported by Marius Gedminas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

After upgrading to Ubuntu 24.04 LTS I ran journalctl -f and noticed that gnome-shell was spamming errors at the rate of 12 lines every second:

geg. 02 18:29:19 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value
geg. 02 18:29:19 blynas gnome-shell[3980]: Using untranslated default instead.
geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value
geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead.
geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value
geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead.
geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value
geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead.
geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value
geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead.
geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value
geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead.
geg. 02 18:29:20 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value
geg. 02 18:29:20 blynas gnome-shell[3980]: Using untranslated default instead.
geg. 02 18:29:20 blynas kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:c6:25:2f:1a:a1:27:08:00 SRC=192.168.1.180 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=30487 PROTO=2
geg. 02 18:29:21 blynas gnome-shell[3980]: Failed to parse translated string '„24h“' for key 'clock-format' in schema 'org.gnome.desktop.interface': 0:expected value
geg. 02 18:29:21 blynas gnome-shell[3980]: Using untranslated default instead.

My locale is lt_LT.UTF-8, which is relevant.

This is caused by a mistaken translation of the quote characters in "'24h'" which is used as the default value for a particular gsettings key. Specifically, this translation: https://translations.launchpad.net/ubuntu/noble/+source/gsettings-desktop-schemas/+pots/gsettings-desktop-schemas/lt/232/+translate.

Since I'm a member of the Lithuanian translators team, I've fixed the translation error in translations.launchpad.net, but my gnome-shell will continue to spam multiple errors every second until an updated language-pack-gnome-lt-base is released.

(I've also submitted a fixed translation upstream to l10n.gnome.org.)

Workaround: run dconf-editor, find /org/gnome/desktop/interface/clock-format, uncheck Use default value, click Apply.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu5
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu May 2 18:25:59 2024
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1786 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 46.0-1ubuntu9
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to noble on 2024-05-02 (0 days ago)

Revision history for this message
Marius Gedminas (mgedmin) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.