After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 356926 - Unable to add tasks in calendar, get "invalid time value" when clicking save (nn_NO locale)
Unable to add tasks in calendar, get "invalid time value" when clicking save ...
Status: RESOLVED DUPLICATE of bug 344121
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-09-20 16:35 UTC by Sebastien Bacher
Modified: 2006-09-26 15:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Sebastien Bacher 2006-09-20 16:35:09 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/evolution/+bug/58210

"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://www.mail-archive.com/evolution-list@gnome.org/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).

http://librarian.launchpad.net/4043207/invalid_time_value1.jpg
Screenshot of the first dialog with the "invalid time value" message
...
> Thanks for your bug. What locale do you use?
...
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="

The same issue happens with GNOME 2.16.0 with a nn_NO locale. Might be a translation issue, is the program supposed to depend on translations for that?
Comment 1 André Klapper 2006-09-26 15:32:03 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 344121 ***