event time cannot be specified any more

Bug #357678 reported by Paolo Benvenuto on 2009-04-08
64
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evolution
Expired
Critical
language-pack-gnome-it (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: evolution

Since I updated to ubuntu jaunty beta, featuring gnome 2.26, I cannot manage my
events' time any more.

If I open en existing event that has its time specified, the time isn't showed
in the corresponding window field, and saving lets the event as an all-day-long
event.

If I add a new event, I have the same problem: I can generate only all-day-long
event. Trying to specify the time with the time drop down list results in the
time not been shown in the corresponding window element.

reported to gnome bugzilla too: http://bugzilla.gnome.org/show_bug.cgi?id=578224

Paolo Benvenuto (donpaolo) wrote :

I think this is a serious funcionality bug, i consider it should be fixed before jaunty release.

Changed in evolution (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Triaged
Changed in evolution:
status: Unknown → New
Paolo Benvenuto (donpaolo) wrote :

Why importance=low ? It's a serious problem that in evolution I cannot enter an event with the proper time indication!!!

Sebastien Bacher (seb128) wrote :

because you seem to be the only user having the issue until now

Paolo Benvenuto (donpaolo) wrote :

I have had the issue installing intrepid and upgrading to jaunty.

I see it:

- on my account (directory .evolution imported from previous pc)
- on the jaunty guest account

can't you reproduce it?

Paolo Benvenuto (donpaolo) wrote :

I intend that in my personal account (I imported .evolution from my previous installation) something from before could be generating the bug, but in the guest session all is like a virgin, nobody sees the bug there?

Paolo Benvenuto (donpaolo) wrote :

OK, I verified that the bug appears only when running evolution with italian locales:

$ locale
LANG=it_IT.UTF-8
LC_CTYPE="it_IT.UTF-8"
LC_NUMERIC="it_IT.UTF-8"
LC_TIME="it_IT.UTF-8"
LC_COLLATE="it_IT.UTF-8"
LC_MONETARY="it_IT.UTF-8"
LC_MESSAGES="it_IT.UTF-8"
LC_PAPER="it_IT.UTF-8"
LC_NAME="it_IT.UTF-8"
LC_ADDRESS="it_IT.UTF-8"
LC_TELEPHONE="it_IT.UTF-8"
LC_MEASUREMENT="it_IT.UTF-8"
LC_IDENTIFICATION="it_IT.UTF-8"
LC_ALL=

if I run it with LC_ALL=C the bug isn't present

Changed in evolution:
status: New → Confirmed
affects: evolution (Ubuntu) → language-pack-gnome-it (Ubuntu)
Changed in language-pack-gnome-it (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
Luca Ferretti (elle.uca) wrote :

Based on "heuristic" investigation from me and Milo Casagrande, this issue is relate to a change I applied in Italian translation in 2.26 cycle.

The change was replace the conversion specificator "%k" formatter for hours with "%-H". Please note that %k is not a supported specificator by stfrtime[1], it should be a GNU/glibc extension or similar; its usage was avoided in similar context, such as eel and/or nautilus translations.

So, while I'm not sure the real issue is in %k usage, I've reverted its usage in e-d-s translation for jaunty[2]. Could be great provide a new langpack to test it, as well as make it available for Jaunty final relase.

[1] http://opengroup.org/onlinepubs/007908799/xsh/strftime.html
[2] http://tinyurl.com/c8vjtz

Changed in language-pack-gnome-it (Ubuntu):
assignee: nobody → Italian translation teams in Launchpad (lp-l10n-it)
Luca Ferretti (elle.uca) wrote :

Sebastien, why did you re-assigned this bug to lp-l10n-it?

As I said we applied a "fix" in e-d-s translation in launchpad, the only missing action is provide a new langpack.

Also I think that importance should be increased, 'cause this bug prevent Italian users to add any appointment.

Changed in language-pack-gnome-it (Ubuntu):
assignee: lp-l10n-it → nobody
miobio (miobio) wrote :

I confirm this bug on several installations. Please fix it ASAP or at least move the importance to high.

Thanks

Milo Casagrande (milo) wrote :

@miobio:
as a workaround you can follow instructions here:

http://tinyurl.com/dnf4ea

The only other thing is waiting for a new language-pack for Ubuntu (probably one month after the release) or version 2.26.2 of GNOME (due around the 15th of May).

miobio (miobio) wrote :

I have already used the fix @ "https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-it/+bug/357678?comments=all" and I confirm it works.

You will agree with me, though, that this solution is hard to implement in large environments (100+ installations). Is there a way to anticipate the 15th of May date?

Could anyone build a .deb to automate the fix procedure?

Thanks for your help

Damiano Dallatana (damidalla) wrote :

I solved using the Launchpad PPA for Ubuntu Language Pack Builders at [1].
I suggest deactivating it after having updated the lag packs (it's a daily updated PPA - that means a lot of updates!) or downloading the italian packages only.

Damiano Dallatana (damidalla) wrote :

I solved using the Launchpad PPA for Ubuntu Language Pack Builders at [1].
I suggest deactivating it after having updated the lag packs (it's a daily updated PPA - that means a lot of updates!) or downloading the italian packages only.

[1]: https://edge.launchpad.net/~ubuntu-langpack/+archive/ppa

David Planella (dpm) on 2009-06-18
tags: added: l10n
Changed in evolution:
importance: Unknown → Critical
Changed in evolution:
status: Confirmed → Incomplete
Changed in evolution:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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