The following sounds exactly like your problem:
The underlying bug in libxcvt seems to have been fixed about a year ago but Ubuntu 22.04.04 uses libxcvt 0.1.1 which is older than that.
The following sounds exactly like your problem:
The underlying bug in libxcvt seems to have been fixed about a year ago but Ubuntu 22.04.04 uses libxcvt 0.1.1 which is older than that.
Good to know, so with any luck this bug will just resolve itself over time when a newer version of libxcvt is being used by Ubuntu and other popular Linux distros.