Shotwell doesn't respect 24-hour clock

[Benji]

Here are my settings for "locale":
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=de_DE.UTF-8
LC_NUMERIC=de_DE.UTF-8
LC_TIME=de_DE.UTF-8
LC_COLLATE=de_DE.UTF-8
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_ALL=

The time should be displayed in a 24-hour time format. Other programs respect this issue. But shotwell only shows the am/pm time (12-hour time) in the picture information.

According to Bug 689055 (https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/689055) this bug should have been fixed in version 0.8. The current version in Ubuntu is 0.12.3. For me, the bug remains.

[Lucas Beeler (lucas-yorba)]

Hi Benji,

Is there any reason why you have a mixed-language environment on your computer? This is to say, your LANG environment variable specifies US English as your system language but you're using German numbers, dates, and times. Much more worryingly, your LC_MESSAGES environment variable is totally out of whack with all of your your other language collation (e.g. LC_xxx) variables. LC_MESSAGES specifies US English but all your other LC_xxx variables specify German. This is likely your problem.

Lucas

[Adam Dingle (adam-yorba)]

Thanks for the bug report. I think this is a bug: Shotwell should use LC_TIME to determine the time format used for displaying messages, independently of other environment variable settings. This bug is known upstream at

http://redmine.yorba.org/issues/2462

[Benji (benjim)]

Thank you Adam.

@Lucas: I like to have my programs and messages in "English" but with all units etc. should be in German, because I live there and like the metric system way better. :-) Which should be no problem, because that's what the different locales are for.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

is that still an issue in the current version?

[TomasHnyk (sup)]

Yes, it is.

[TomasHnyk (sup)]

Oh no, actually it seems to be fixed.

[Jim Nelson (yorba-jim)]

I don't believe this bug has been fixed. See bug #1318847 and https://bugzilla.gnome.org/show_bug.cgi?id=716533.

[Christian González (droetker)]

This bug is still present in 16.04.

[Sebastien Bacher (seb128)]

upstream fixed it in git with https://git.gnome.org/browse/shotwell/commit/?id=45dfd34

[Paul White (paulw2u)]

Changelog shows fixed in version 0.24.0-1