On 05/07/2012 Rob Weir wrote:
On Wed, Jul 4, 2012 at 2:38 PM, Andrea Pescetti wrote:
I asked on the mailing lists in Italian; several users upgraded 3.2.x->3.4,
with the same experience as the 3.3 -> 3.4 upgrade (no issues for a slightly
customized installation, profile conversion problems if many extensions are
installed or heavy customizations are present). ...
Do we know if this is only a 3.3 -> 3.4 issue? Or will there also be
migration issues for 3.4 to 3.4.1?
The changes to user profile will be less invasive in 3.4.1. Actually,
the only issue is the size reduction to avoid 160 MBytes of data written
to every user profile. I don't know the exact details on how this was
implemented, but it shouldn't be a huge change with respect to the 3.3
-> 3.4 ones.
Do we have any steps that can reproduce the bug? Something more
specific than "many extensions or heavy customizations"? ...
Or could this be related to the
removal of berkelydb and this fix:
https://issues.apache.org/ooo/show_bug.cgi?id=118662 ??
Removing BerkeleyDB (while technically a good thing) is almost surely
the origin of this issue. Initially, it was assumed that all 3.3
settings and extensions would be dropped when updating to 3.4. Later, a
migration procedure was implemented, but it has shortcomings. I haven't
been able to distinguish a precise pattern so far, but there is a clear
trend suggesting that the more customizations/extensions a user applied
to 3.3, the more likely he will bump into an upgrade issue.
Unfortunately, the resulting problems can vary: some users report random
crashes, some see non-working dictionaries... But so far all of them
could solve the problem by renaming their user profile.
Regards,
Andrea.
