Ubuntu 16.04 LTS: First weekday set incorrectly in the stock Calendar app (gnome-calendar, ver. 3.20.1)

Bug #1573636 reported by w1ssrukte9uoe7160yx5i5iz6jnqo0ka
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNOME Calendar
Fix Released
Medium
gnome-calendar (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

I use Ubuntu 16.04 (LTS) with the stock Calendar app (Gnome-calendar, ver. 3.20.1). My system language is en_US however my regional is fi_FI.

The Gnome Calendar Shell is showing the first day of the week as a monday (which is correct in this region) however the stock calendar app is still showing Sunday.

Here's my exact locale settings:
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=fi_FI.UTF-8
LC_TIME=fi_FI.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=fi_FI.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=fi_FI.UTF-8
LC_NAME=fi_FI.UTF-8
LC_ADDRESS=fi_FI.UTF-8
LC_TELEPHONE=fi_FI.UTF-8
LC_MEASUREMENT=fi_FI.UTF-8
LC_IDENTIFICATION=fi_FI.UTF-8
LC_ALL=

I've tried changing my "/usr/share/i18n/locales/en_US" values into this as a root user:

week 7;19971130;4
first_weekday 2
first_workday 2

the fi_FI is following:

week 7;19971130;4
first_weekday 2 % Monday
first_workday 2 % Monday

Then I did 'sudo locale-gen' and reboot the PC but it's still showing sunday as a first day of the week on the stock Calendar app.

Revision history for this message
w1ssrukte9uoe7160yx5i5iz6jnqo0ka (w1ssrukte9uoe7160yx5i5iz6jnqo0ka-deactivatedaccount) wrote :
summary: - Ubuntu 16.04 LTS: First weekday set incorrect in Gnome Calendar app
+ Ubuntu 16.04 LTS: First weekday set incorrectly in the stock Calendar
+ app (gnome-calendar)
summary: Ubuntu 16.04 LTS: First weekday set incorrectly in the stock Calendar
- app (gnome-calendar)
+ app (gnome-calendar, ver. 3.20.1)
affects: belocs-locales-data (Ubuntu) → gnome-calendar (Ubuntu)
Revision history for this message
w1ssrukte9uoe7160yx5i5iz6jnqo0ka (w1ssrukte9uoe7160yx5i5iz6jnqo0ka-deactivatedaccount) wrote :
tags: added: multiarch
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks, that's a known upstream issue, see https://bugzilla.gnome.org/show_bug.cgi?id=762428

Changed in gnome-calendar (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Changed in gnome-calendar:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in gnome-calendar:
status: Confirmed → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug has been fixed upstream with https://git.gnome.org/browse/gnome-calendar/commit/?id=5e05f998761c669e3e995051d658268b3d8e3a0d

the change should be in the next ubuntu update/SRU

Changed in gnome-calendar (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

Yes. 3.20.2 has the fix.

Changed in gnome-calendar (Ubuntu):
status: Fix Committed → Fix Released
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.