Perpetual Validation Error when editing Task details

Bug #19656 reported by Dean Michael Berris
8
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Fix Released
Medium
Sebastien Bacher

Bug Description

Evolution 2.2.1.1 does not allow the editing of task details -- it always
complains of a validation error in the Date Completed field even if valid inputs
are present in the field. This makes it impossible to enter details to tasks,
and it also does not allow the creation of tasks using the New->Task form.

To reproduce:
1. Click on the New drop-down button and choose Task
2. Enter required information (at least the summary) and then click on OK

Additional Information:
The installation is an Ubuntu Hoary Hedgehog which inherited settings from a
previous 1.4.x installation.

Revision history for this message
Dean Michael Berris (mikhailberis-gmail) wrote :

The bug disappeared when I expunged the old settings inherited from evolution
1.4.x (thanks to the advice of hondje @ irc.free.net.ph:#ubuntu) and started
from a scratch evolution invocation.

The fix was as follows:
1. move the old .evolution/ directory to something like .evolution-old/
2. Run evolution (it will create the new .evolution directory)
3. Import all important information from .evolution-old/

NOTE: This does not fix the bug, but it merely circumvents the issue by starting
evolution from scratch and importing all necessary information.

Revision history for this message
Dean Michael Berris (mikhailberis-gmail) wrote :

It (the bug) has resurfaced, and oddly enough is encountered when a new user
startes evolution for the first time. Creating tasks is possible, however adding
additional information to tasks causes a Validation error. Above sidestepping of
the issue did not help either.

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

Thanks for your bug. Did you assign it to yourself on purpose? Does that match
the description of http://bugzilla.gnome.org/show_bug.cgi?id=304709 ?

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

does the workaround of http://bugzilla.gnome.org/show_bug.cgi?id=300216 work for
you?

Revision history for this message
Dean Michael Berris (mikhailberis-gmail) wrote :

Yes it matches the description of both the links you've provided above. However,
It refers to upgrading the installed evolution version up to 2.2.2 -- I have not
seen a package for evolution 2.2.2 just yet in hoary though. It might be a known
issue in 2.2.1.1. I have not tried installing evolution 2.2.2 just yet.

Perhaps this should be addressed still in Hoary instead of prolonging it for the
Breezy release? ;)

BTW, I hadn't assigned it to me on purpose... Maybe I misinterpreted the use of
the reassignment of the bug when I closed it a couple days ago.

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

We don't update versions for a stable release but we can patch annoying issue.
There is no obvious changelog entry for the fix and it's fixed with the current
version. There is also not a lot of complain about that and a workaround. I'm
tempted to just mark the bug as FIXED, bug if somebody wants to come with a
patch for the issue he's welcome.

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

That works fine with GNOME 2.12/the packages for Ubuntu 5.10, I'm closing it.
Feel free to reopen if you have the issue with it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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