GNOME Bugzilla – Bug 698952
GnomeWallClock "clock" property is NULL if the locale is not UTF-8
Last modified: 2013-09-06 18:37:30 UTC
The GnomeWallClock "clock" property is always NULL if the current locale doesn't specify UTF-8 encoding.
I'm betting on broken i18n given the lack of calls to bind_textdomain_codeset(). If that code worked before, it was purely accidental.
*** Bug 699353 has been marked as a duplicate of this bug. ***
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report. the relevant commit is https://git.gnome.org/browse/gnome-desktop/commit/?id=a4dd7815aba059c8798094a277acccfdbc2f7179 https://bugzilla.gnome.org/show_bug.cgi?id=699325#c7 Correct me if I am wrong
(In reply to comment #3) > This problem has been fixed in the development version. The fix will be > available in the next major software release. Thank you for your bug report. > > the relevant commit is > https://git.gnome.org/browse/gnome-desktop/commit/?id=a4dd7815aba059c8798094a277acccfdbc2f7179 > > https://bugzilla.gnome.org/show_bug.cgi?id=699325#c7 Then it's a dupe and needs to be marked as such. > Correct me if I am wrong Did you not test this? *** This bug has been marked as a duplicate of bug 699325 ***
(In reply to comment #4) > (In reply to comment #3) > > This problem has been fixed in the development version. The fix will be > > available in the next major software release. Thank you for your bug report. > > > > the relevant commit is > > https://git.gnome.org/browse/gnome-desktop/commit/?id=a4dd7815aba059c8798094a277acccfdbc2f7179 > > > > https://bugzilla.gnome.org/show_bug.cgi?id=699325#c7 > > Then it's a dupe and needs to be marked as such. > > > Correct me if I am wrong > > Did you not test this? > I have tested it https://bugzilla.gnome.org/show_bug.cgi?id=698942#c4 However it does not fixes the gnome-clocks issue, as was initially assumes it should. That is why I would like to double check it by someone else. Can you confirm this as well? > *** This bug has been marked as a duplicate of bug 699325 ***
(In reply to comment #4) > (In reply to comment #3) > > This problem has been fixed in the development version. The fix will be > > available in the next major software release. Thank you for your bug report. > > > > the relevant commit is > > https://git.gnome.org/browse/gnome-desktop/commit/?id=a4dd7815aba059c8798094a277acccfdbc2f7179 > > > > https://bugzilla.gnome.org/show_bug.cgi?id=699325#c7 > > Then it's a dupe and needs to be marked as such. Thank you. You are right. > > > Correct me if I am wrong > > Did you not test this? > > *** This bug has been marked as a duplicate of bug 699325 ***
This was fixed for me only because I have a patch applied locally: https://bugzilla.gnome.org/show_bug.cgi?id=696497#c18 the issue is caused by the g_date_time_format (now, format_string) function which returns NULL, if format_string contains an utf-8 character!!!
Master seems to work fine: $ LC_ALL=en_GB.ISO8859-1 ./test-wall-clock Thu 19:29 ^C $ LC_ALL=C ./test-wall-clock Thu 19:30 How exactly do I reproduce the problem?
(In reply to comment #8) > Master seems to work fine: > > $ LC_ALL=en_GB.ISO8859-1 ./test-wall-clock > Thu 19:29 > ^C > $ LC_ALL=C ./test-wall-clock > Thu 19:30 > > How exactly do I reproduce the problem? As I have mentioned in my previous comment, the format string should contain at least one unicode character, like COLON, in all your tested cases only plain colon ":" were shown. So a locale in which COLON is used will fail.
Which is a known bug in glib, see bug 707599. So I'll close this. *** This bug has been marked as a duplicate of bug 707599 ***