[Bug 1843366] [NEW] [eoan][2.30] locale woes, 12 hour clock and other issues

[Frode Nordahl]

Public bug reported:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu Eoan Ermine (development branch)
Release:	19.10
Codename:	eoan

After the recent update of libc and locale packages to 2.30 I'm
experiencing issues on my developer workstation.

The most visible change is that my terminal will format the clock in 12
hour AM/PM format regardless of settings.  I am able to restore the 24
hour clock by forcing LC_TIME to C.

However, this also affects applications doing datetime calculations, an
example being the Zaza test framework written in Python suddenly
generating TLS certificates with a not valid until time into the future,
with the consequence of test runs failing.

So there is something more unnerving than a mere time display format
change going on.

Will try to dig up some more details, but wanted to flag this here in
case someone know more about what has changed and/or are seeing similar
issues.

** Affects: glibc (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1843366

Title:
  [eoan][2.30] locale woes, 12 hour clock and other issues

Status in glibc package in Ubuntu:
  New

Bug description:
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:	Ubuntu
  Description:	Ubuntu Eoan Ermine (development branch)
  Release:	19.10
  Codename:	eoan

  After the recent update of libc and locale packages to 2.30 I'm
  experiencing issues on my developer workstation.

  The most visible change is that my terminal will format the clock in
  12 hour AM/PM format regardless of settings.  I am able to restore the
  24 hour clock by forcing LC_TIME to C.

  However, this also affects applications doing datetime calculations,
  an example being the Zaza test framework written in Python suddenly
  generating TLS certificates with a not valid until time into the
  future, with the consequence of test runs failing.

  So there is something more unnerving than a mere time display format
  change going on.

  Will try to dig up some more details, but wanted to flag this here in
  case someone know more about what has changed and/or are seeing
  similar issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1843366/+subscriptions