This bug is unfortunately still in Evolution 2.6.0, and it has plagued me at least two times this day again. Last time I said it was sporadic, but since I'm using Evo 2.6.0 on Dapper it happens nearly every day.
In the upstream bug report I read that this bug is retargeted to Evolution 2.7.0. That would mean waiting another half year and coping with this evil bug before 2.7.0 is released. This is such a severe bug, would it be possible for the Ubuntu dev's to backport a fix for this bug once this bug has been fixed in Evolution's CVS? Or if the Evolution team will do a bug fix release, 2.6.1 or something, will that new version be available for Dapper?
This bug is unfortunately still in Evolution 2.6.0, and it has plagued me at least two times this day again. Last time I said it was sporadic, but since I'm using Evo 2.6.0 on Dapper it happens nearly every day.
In the upstream bug report I read that this bug is retargeted to Evolution 2.7.0. That would mean waiting another half year and coping with this evil bug before 2.7.0 is released. This is such a severe bug, would it be possible for the Ubuntu dev's to backport a fix for this bug once this bug has been fixed in Evolution's CVS? Or if the Evolution team will do a bug fix release, 2.6.1 or something, will that new version be available for Dapper?