Unable to add tasks in calendar, get "invalid time value" when clicking save

Bug #58210 reported by PAN007
36
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
Critical
GLibC
Won't Fix
Medium
evolution (Debian)
Fix Released
Unknown
evolution (Suse)
Fix Released
Critical
evolution (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs
glibc (Fedora)
Fix Released
Medium
glibc (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Version: 2.6.1-0ubuntu7 / Dapper
Problem: When adding a task in the calendar I get a dialog "invalid time value" when clicking "save". I have indeed chosen a time in the drop-down box (for instance 09:30). After clicking OK in the "invalid time value" dialog it reappears together with another dialog with the message: "Validation error: the starttime is wrong" (translated from the error message that is in norwegian).

A google search:

http://<email address hidden>/msg04216.html

In my case the time values always show up as hh:mm and changing the format to anything I can think of does not help (hh.mm, hh;mm, etc).

I have tried with a fresh $HOME/.evolution without sucess (it was a totally new user account with no custom configuration).

Revision history for this message
PAN007 (systemansvarlig) wrote :
Revision history for this message
PAN007 (systemansvarlig) wrote :
Revision history for this message
In , Piotr Engelking (inkerman42) wrote :

Currently, glibc displays dates in the pl_PL locale as:

pon sie 6 01:23:45 CEST 1984

This format violates several conventions for date abbreviations in the Polish
language. I include a patch against the current CVS localedata with the
following changes:

* non-standard weekday abbreviations are replaced with standard ones
* non-standard month abbreviations are replaced with standard ones (based on
Roman numerals)
* middle-endian format (never used in Poland) is replaced with the little-endian
one (by far the most popular)
* standard padding is introduced, i.e. h:m:s are zero-padded, day of the month
is not padded
* fields are properly separated

With the patch, dates are displayed as:

Pn, 6 VIII 1984, 01:23:45 CEST

which matches the most common usage.

Please notice that the abbreviations are no longer fixed-width. Since this is
also the case in several other locales, I suppose it is not a problem.

Revision history for this message
In , Piotr Engelking (inkerman42) wrote :

Created attachment 1267
LC_TIME fixes for pl_PL locale

Revision history for this message
In , Keld Simonsen (keld) wrote :

Subject: Re: New: LC_TIME for pl_PL doesn't match standard usage

On Thu, Aug 31, 2006 at 01:47:16AM -0000, inkerman42 at gmail dot com wrote:
> Currently, glibc displays dates in the pl_PL locale as:
>
> pon sie 6 01:23:45 CEST 1984
>
> This format violates several conventions for date abbreviations in the Polish
> language. I include a patch against the current CVS localedata with the
> following changes:
>
> * non-standard weekday abbreviations are replaced with standard ones
> * non-standard month abbreviations are replaced with standard ones (based on
> Roman numerals)
> * middle-endian format (never used in Poland) is replaced with the little-endian
> one (by far the most popular)
> * standard padding is introduced, i.e. h:m:s are zero-padded, day of the month
> is not padded
> * fields are properly separated
>
> With the patch, dates are displayed as:
>
> Pn, 6 VIII 1984, 01:23:45 CEST
>
> which matches the most common usage.

well, you could use that for the long format, but it seems not
convenient for the short (abbreviated) format. Both day names and month
names are variable length.

My understanding is also that day and month names in Polish are spelled
with small initial letters.

> Please notice that the abbreviations are no longer fixed-width. Since this is
> also the case in several other locales, I suppose it is not a problem.

The recommendation is that the abbreviated format be fixed
format/lenght, as this is intended to be used in log messages.

best regards
Keld

Revision history for this message
In , Drepper-fsp (drepper-fsp) wrote :

You have to provide evidence. Provide URLs of official documents, railway
publications, newspapers.

Revision history for this message
In , Piotr Engelking (inkerman42) wrote :

[Sorry for delay, I have been on vacation for the last few days.]

First, some background to answer Mr. Drepper's and Mr. Simonsen's questions.

Weekdays:

Weekday abbreviations are not part of any official standard. They ones described
above are, however, used nearly universally in calendars.

Examples of use:

* http://kalendarz.pwn.pl/ [calendar of PWN (Polish Scientific Publishers),
publisher of the largest and most authoritative Polish-language encyclopedias
and dictionaries]
* http://lot.pl/ [timetable of LOT, the largest Polish airline]

Please note that these abbreviations can only appear standalone or as part of a
standalone date (and yes, while Polish weekday names are lowercase, they are
not). To abbreviate weekday names in an intertextual context (which would be
quite uncommon), one would have to use an ad hoc abbreviation following standard
rules, i.e. match the case of the word, end with a consonant, and be followed by
a dot, e.g. 'poniedziałek' could be abbreviated as 'pn.', 'pon.', or 'poniedz.'.

Date:

Modern dictionaries of Polish language allow the following date abbreviations:

* 6 VIII 1984 (older dictionaries also allowed 6.VIII.1984)
* 6.8.1984, or 6.08.1984, or 06.08.1984

The use of other abbreviations (such as 1984.08.06) is explicitly discouraged,
unless neccessitated by specialized data processing requirements.

Online reference:

* http://so.pwn.pl/zasady.php?id=629747 [ortographical dictionary of PWN]

Examples of use:

* http://www.senat.gov.pl/senatrp/noty/dzieje.pdf [history of Senat, upper
chamber of the Polish parlament)]
* http://edukacja.sejm.gov.pl/historia_sejmu/ [history of Sejm, lower chamber of
the Polish parlament)]
* http://rjp.pl/?mod=uchwaly&id=2 [resolutions of the Polish Language Council,
official standarizing organization for the Polish language]
* http://intercity.pl/scripts/train/index.php?action=train_list [timetable of
PKP, the largest Polish railway company]
* http://lot.pl/ [timetable of LOT]

> The recommendation is that the abbreviated format be fixed
> format/lenght, as this is intended to be used in log messages.

Ah, I wasn't aware of this recommendation. Perhaps it might be a good idea to
document it somewhere? Is there some particular reason why so many locales don't
follow it?

Which formats exactly should be fixed-width? For d_fmt, there should be no
problem. Weekday abbreviations can be made fixed-width as well, by using a
variant with N replaced with Nd. And while it isn't exactly common to mix
weekday abbreviations and numeric date format, I guess it can be done, too. How
about date_fmt? It's not fixed-width in the POSIX locale, either.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. What locale do you use?

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Untriaged → Low
status: Unconfirmed → Needs Info
Revision history for this message
PAN007 (systemansvarlig) wrote :

erlingre@skarphedin:~$ locale
LANG=nn_NO.UTF-8
LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en_GB:en
LC_CTYPE="nn_NO.UTF-8"
LC_NUMERIC="nn_NO.UTF-8"
LC_TIME="nn_NO.UTF-8"
LC_COLLATE="nn_NO.UTF-8"
LC_MONETARY="nn_NO.UTF-8"
LC_MESSAGES="nn_NO.UTF-8"
LC_PAPER="nn_NO.UTF-8"
LC_NAME="nn_NO.UTF-8"
LC_ADDRESS="nn_NO.UTF-8"
LC_TELEPHONE="nn_NO.UTF-8"
LC_MEASUREMENT="nn_NO.UTF-8"
LC_IDENTIFICATION="nn_NO.UTF-8"
LC_ALL=

Revision history for this message
Sebastien Bacher (seb128) wrote : Re: Unable to add tasks in calendar, get "invalid time value" when clicking save (nn_NO locale)

Happens on edgy too with that locale, I've forwarded it upstream: http://bugzilla.gnome.org/show_bug.cgi?id=356926

Changed in evolution:
importance: Low → Medium
status: Needs Info → Confirmed
Changed in evolution:
status: Unknown → Unconfirmed
Changed in evolution:
status: Unconfirmed → Confirmed
Revision history for this message
In , Piotr Engelking (inkerman42) wrote :

Has there been any activity on this bug recently? There has been no comment from
any of the developers for several months. I had submitted the requested
references, is that enough? My question about the formats, and which of them, if
any, should be changed to fixed-width hasn't been answered, either. Is there
anything else I can do to help?

Revision history for this message
In , Piotr Engelking (inkerman42) wrote :

The weekday abbreviations proposed by the above patch seem also to be identical
with ones used by Windows. (This is what the gtk2 calendar widget uses on
Windows XP, at least).

Revision history for this message
In , Drepper-fsp (drepper-fsp) wrote :

I applied the patch.

Revision history for this message
Erik I (erik-itland) wrote :

I have the same bug on feisty.

Trying to use the format hh.mm works for me (but I must choose it for both start and end. See the screenshot for a working workaround :)

Hope this helps, as the Evolution Calendar is almost useless for normal users at the moment.

Revision history for this message
PAN007 (systemansvarlig) wrote : Re: [Bug 58210] Re: Unable to add tasks in calendar,get "invalid time value" when clicking save (nn_NO locale)

Thanks, but I hope it will be fixed soon. Workarounds as this works well
for power users, but is another reason for luddites to avoid computers.

ty den 03.04.2007 klokka 19:44 (+0000) skreiv Erik I:
> I have the same bug on feisty.
>
> Trying to use the format hh.mm works for me (but I must choose it for
> both start and end. See the screenshot for a working workaround :)
>
> Hope this helps, as the Evolution Calendar is almost useless for normal
> users at the moment.
>
> ** Attachment added: "A workaround for thr bug"
> http://librarian.launchpad.net/7132026/Skjermdump-Avtale%20-%20Trying%20to%20work%20around%20the%20bug.png
>

Revision history for this message
Erik I (erik-itland) wrote : Re: Unable to add tasks in calendar, get "invalid time value" when clicking save (nn_NO locale)

This one is solved for me now. Thanks a lot!

Revision history for this message
In , Julian (julian-redhat-bugs) wrote :

Description of problem:
After upgrade from fc6, date +%c gives the following (pl_PL):
N, 3 VI 2007, 02:27:59
before, it was looking like that
nie, 3 cze 2007, 02:27:59
I think that the second format is much more readable.

Revision history for this message
In , Tomek-jot23 (tomek-jot23) wrote :

This change introduced a bug with strptime function.
D_FMT format is set to "%-d %b %Y" and strptime
function does not seem to support "-" in "%-d"
format specifier. This leads to a problem described
here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243513

Revision history for this message
In , Piotr Engelking (inkerman42) wrote :

There are, indeed, two bugs in strptime() which prevent it from parsing d_fmt
correctly. Filed as:

* http://sources.redhat.com/bugzilla/show_bug.cgi?id=4772
* http://sources.redhat.com/bugzilla/show_bug.cgi?id=4773

Revision history for this message
In , Rathann (dominik-greysector) wrote :

There's significant uproar due to the month abbreviations change to roman
numerals. Though theoretically correct, it is not acceptable to the community at
large, and there are standards and expert opinions in favour of three-letter
abbreviations. Weekday abbreviations and field separator changes are under
debate, too. See bug 4789 for more details.

Revision history for this message
In , Karol (karol-redhat-bugs) wrote :

I think the Fedora should patch the glibc because the upstream does not want to
do it.
File to patching: <path_to_sourcedir>/localedata/locales/pl_PL (after
installation: /usr/share/i18n/locales/pl_PL ).

Revision history for this message
In , Karol (karol-redhat-bugs) wrote :

Reasons:
- at now the abmon is archaic mothod of abbreviation
- there are problems with applications (e.g. calendar in evolution)
- now it is useless and not user-friendly
The polish experts opinion says that the previous method of abreviating days and
months IS correct in computer industry.

Revision history for this message
In , Julian (julian-redhat-bugs) wrote :

I think something like Wto, 25 Sie 2007 looks a bit better.

Revision history for this message
In , Zbigniew Luszpinski (zbiggy) wrote :

Please revert pl_PL-LC_TIME.patch ASAP. Someone made a joke on you. This archaic
date stamping using roman month numbers was never officially approved, never in
widespread use. It is only used if author of a document wanted to gain artistic
effect. That is why roman numbering of months is usually found in documents
together with Gothic fonts and Anno Domini A.D. prefix before date.

I'm sure glibc maintainers implemented this patch having good will in mind. Next
time before applying such patch please ask Polish Linux translation teams if
future localization patches are not a hostile joke.

This patch make Polish Linux community suffer (broken apps, logs, errors in data
processing). This patch is proof of concept how big negative impact can have
single person on whole community.

This patch breaks national standards:
PN-EN 28601:2002 which is the same as ISO 8601:2004
http://www.pkn.pl/index.php?a=show&m=katalog&id=463318&page=1
here is free access via wikipedia:
http://en.wikipedia.org/wiki/ISO_8601

The PN-EN 28601:2002 (ISO 8601:2004) is required format for data sorting in data
processing machines. Example: 2007-09-24

In real life (government documents, administration, commerce) for comfortable
user view dd-MM-CCYY format is used. Where:
dd - day in two digits format
MM - month in two digits format
CC - century in two digits format
YY - year in two digits format
Example: 24-09-2007
On paper documents instead of dash "-" separator a "." dot can be found. However
because of growing computerization of country administration and increasing
number of personal computer users dash becomes more popular over dot because it
is better visible on screen and after printing.

To all maintainers (no matter if it is glibc or other project): Please always
verify all localization patches by sending them (in human understandable format)
to official translation teams of a given Language/Region. This will keep Linux
safe and not compromised.

Revision history for this message
In , Julian Sikorski (belegdol) wrote :

How about something like that:
Pon, 6 sie 1984 01:23:45 CEST
Looks nicer, has non-broken endianess and fixed-width names.

Revision history for this message
In , Jakub (jakub-redhat-bugs) wrote :

We now have 3 different groups, each pushing a different format.
For %b wrz vs. IX vs. 9, and then various different layouts of D_T_FMT, D_FMT
and T_FMT.
If you want this changed, can you (or ask somebody else to) please organize an
internet poll among Polish Linux users, which states all the various proposed
changes and let people choose from them, then invite people in various LUGs,
distros, those commenting in the various bugzilla bugs about this, etc.

Revision history for this message
In , Karol (karol-redhat-bugs) wrote :
Revision history for this message
In , Marcin Gil (marcin.gil) wrote :

ISO is an already established, widely used, adopted by PN (Polska Norma/Polish
Norm) standard. Using everything else, like fancy roman formatting, is useless
and troublesome.

Revision history for this message
Przemek K. (azrael) wrote :

I have the same bug in Gutsy, on PL_pl (polish) locale.
I'm attaching a screenshot.
First popup says "Validation error: the starttime is wrong", and the second means "Invalid date".
I can't add any tasks or meetings - Evolution is unusable.

Revision history for this message
In , Karol (karol-redhat-bugs) wrote :

There has not been a lot of interest about poll, but I think I can sum it up.
In conclusion of poll about day abbs:
# pon, wto, śro, czw, pią, sob, nie (47%, 425 Votes)
# Pn, Wt, Śr, Cz, Pt, So, Nd, (27%, 249 Votes)
# pn., wt., śr., czw., pt., sob., ndz. (10%, 95 Votes)
# PN,WT,SR,CZW,PT,SO,ND (5%, 48 Votes)
# pon., wto., śro., czw., pią., sob., nie. (4%, 38 Votes)
# Po,Wt,Śr,Czw,Pt,So,N (3%, 25 Votes)
# inna (podaj w komentarzu) (2%, 18 Votes) <= in comments are e.g. "pn, wt, śr,
cz, pt, so, nd"
# pon., wt., śr., czw., piąt., sob., niedz. (1%, 11 Votes)
Well... in the glibc should be these abbreviations:
nie
pon
wto
śro
czw
pią
sob

Abbreviations of months:
# trzy pierwsze litery (sty,lut,mar,kwi,maj,cze,lip,sie,wrz,paź,lis,gru) (81%,
519 Votes)
# rzymskie liczby (I,II,III,IV,V,VI,VII,VIII,IX,X,XI,XII) (17%, 108 Votes)
# inna zgodna z normami (podaj w komentarzu) (3%, 17 Votes)
So in the glibc should be these abbreviations:
sty
lut
mar
kwi
maj
cze
lip
sie
wrz
paź
lis
gru

The D_FMT:
# liczbowa arabska z uzupełniającym zerem (01,02…12), %d.%m.%Y, np. 01.01.1970
(62%, 528 Votes)
# z użyciem skrótów miesięcy, %d %b %Y, np. 01 I 1970, 01 sty 1970 (36%, 303 Votes)
# inna (podaj w komentarzu) (3%, 22 Votes) <= most of these votes are for iso-8601
I did not organize more polls (e.g. for D_T_FMT). I think good idea is to not
change D_T_FMT (IMHO there should be change only abbs not *FMT, but I made a
poll as you wish).

Revision history for this message
In , Ulrich (ulrich-redhat-bugs) wrote :

I've made changes upstream in cvs.

Revision history for this message
In , Karol (karol-redhat-bugs) wrote :

I think I can close the bug. :)

Revision history for this message
Rafal Kwasny (mag) wrote :

This bug is also present in final Gutsy release
this renders Evolution Calendar unusable with polish locale

Revision history for this message
Tomasz Sterna (smoku) wrote :

It works for americans - it works. :-/
The rest of the world should switch to en_US, plain ASCII and ANSI standards.

Cute...

Revision history for this message
Jarek Kownacki (jarek-gazik) wrote :

As smoku said...poles are american's friends :-/ Maybe Ubuntu is part of Microsoft with CIA as the head?

Revision history for this message
Sebastien Bacher (seb128) wrote :

such comments are not useful, nobody denied there was a bug and most of the ubuntu distribution team is actually in Europe, the issue is that there is ten of thousand of open bugs and a limited number of people working on those

Changed in evolution:
status: Confirmed → Triaged
Revision history for this message
Przemek K. (azrael) wrote :

Any news on this bug? The workaround mentioned above doesn't work for me.

Revision history for this message
Przemek K. (azrael) wrote :
Revision history for this message
Przemek K. (azrael) wrote :
Revision history for this message
Przemek K. (azrael) wrote :
Revision history for this message
Przemek K. (azrael) wrote :
Changed in evolution:
status: Unknown → New
Changed in evolution:
status: Unknown → Incomplete
Revision history for this message
Przemek K. (azrael) wrote :

Everybody: please go to http://bugzilla.gnome.org/show_bug.cgi?id=477753 for further investigation.

Revision history for this message
In , Marcin (marcin-redhat-bugs) wrote :

Sorry for digging up a bug closed almost 2 months ago, but I have just installed
F8 (earlier had FC6) and noticed that "locale's date representation" (date +%x)
had been changed.
In previous versions there was %Y-%m-%d (e.g. 2007-12-20), now %d.%m.%Y
(20.12.2007). At it was detailed in already mentioned bug:
http://sourceware.org/bugzilla/show_bug.cgi?id=3156#11
in Poland accepted standard is PN-EN 28601:2002 (aka ISO_8601).
http://www.pkn.pl/index.php?a=show&m=katalog&id=463318&page=1 (Polish Committee
for Standarization)
http://en.wikipedia.org/wiki/ISO_8601
which defines date as 2007-12-20.

Because there was no question about that date format in Karol's poll (it appears
only in the first question about fixed number of digits with leading zeros vs.
that with months abbreviation (like 01 I 1970, 01 sty 1970)) I suspect that it
could be changed accidentally in Fedora version and unnecessary breaks standard.

Revision history for this message
In , Julian (julian-redhat-bugs) wrote :

It was not included, since it is an international format that can be obtained
easily. There are comments about that in one of the sourceware bugs iirc.

Changed in evolution:
status: Unknown → Confirmed
Revision history for this message
Tomasz Sterna (smoku) wrote :

There is a solution given at the linked b.g.o entry.
When we can expect it in Ubuntu?

Changed in evolution:
status: Incomplete → Confirmed
Changed in evolution:
status: Confirmed → Incomplete
Revision history for this message
In , Program-spe (program-spe) wrote :

(In reply to comment #11)
> PN-EN 28601:2002 which is the same as ISO 8601:2004
> http://www.pkn.pl/index.php?a=show&m=katalog&id=463318&page=1

Here is something for you to criticise:
<http://en.wikipedia.org/wiki/Date_and_time_notation_by_country#Poland>

Revision history for this message
Przemek K. (azrael) wrote :

At the discussion at the linked Gnome bug (http://bugzilla.gnome.org/show_bug.cgi?id=477753) it has been found out that the reason for this bug might be the way glibc handles dates.

BTW: anyone checked if the bug still appears in Hardy?

Revision history for this message
Przemek K. (azrael) wrote :

Ok, I've checked it: the bug is fixed in Evolution 2.22 in Ubuntu 8.04 alpha (today's build).

Revision history for this message
Tomasz Sterna (smoku) wrote :

Yes, it is fixed in Hardy.

Changed in evolution:
status: Incomplete → Fix Released
Changed in glibc:
status: Unknown → Fix Released
status: Unknown → Won't Fix
Changed in evolution:
status: Confirmed → Incomplete
Revision history for this message
Przemek K. (azrael) wrote :

I'm closing this bug since it is fixed in Hardy. If it still appears for someone, then please reopen it.

Changed in glibc:
status: New → Invalid
Changed in evolution:
status: Triaged → Fix Released
Changed in evolution:
status: Incomplete → Fix Released
Changed in evolution (Debian):
status: New → Fix Released
Changed in evolution:
importance: Unknown → Critical
Changed in glibc:
importance: Unknown → Medium
Changed in evolution (Suse):
importance: Unknown → Critical
Revision history for this message
In , Jackie-rosen (jackie-rosen) wrote :

*** Bug 260998 has been marked as a duplicate of this bug. ***
Seen from the domain http://volichat.com
Page where seen: http://volichat.com/adult-chat-rooms
Marked for reference. Resolved as fixed @bugzilla.

Changed in glibc (Fedora):
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.