452459 - Migration wizard for seamonkey TRUNK build should be more verbose when migrating from 1.x profile

Status: RESOLVED WONTFIX

(SeaMonkey :: Startup & Profiles, defect)

Description

[Martin Mokrejs]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.2pre) Gecko/2008082711 SeaMonkey/2.0a1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.2pre) Gecko/2008082711 SeaMonkey/2.0a1pre

The Wizard detects correctly user has no ~/.mozilla/seamonkey/ directory at converts data from ~/.mozilla/default/. Unfortunately, it shows a long listing of thing to be done, like "Preferences", ..., "Mail folders". Probably at the very top of the window it is supposed to show what is it currently doing. Instead, I saw only some "..." (dots) and had to wait for a loong time. Well, I do have a lot of email stored, sure, but the process should be more verbose.

Finally, I would like to see some summary what has happened, what files/directories were created and what has succeeded/failed.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.



Build platform
target
i686-pc-linux-gnu

Build tools
Compiler 	Version 	Compiler flags
gcc 	gcc version 4.3.1 (Gentoo 4.3.1-r1 p1.1) 	-Wall -W -Wno-unused -Wpointer-arith -Wcast-align -W -Wno-long-long -pedantic -fno-strict-aliasing -pthread -pipe
c++ 	gcc version 4.3.1 (Gentoo 4.3.1-r1 p1.1) 	-fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-long-long -pedantic -fno-strict-aliasing -fshort-wchar -pthread -pipe

Configure arguments
--disable-optimize '--enable-debug=-g3\ -O0\ -ggdb' --enable-debug-modules=all --enable-debugger-info-modules --enable-detect-webshell-leaks --enable-svg --enable-svg-renderer-libart --enable-image-decoders=all --with-qtdir=/usr/qt/3 --enable-application=suite --disable-freetype2 --enable-jprof --enable-default-toolkit=cairo-gtk2 --enable-xft --disable-gssapi

Comment 1

[Rainer Bielefeld]

@reporter:
Still a problem for you? Any way how to make the problem reproducible?

Comment 2

[Rainer Bielefeld]

The current 2.3x Versions do no longer support 1.x profile integration, and there will be no more fixes for 2.0 branch.

Comment 3

[Martin Mokrejs]

(In reply to Rainer Bielefeld from comment #2)
> The current 2.3x Versions do no longer support 1.x profile integration, and
> there will be no more fixes for 2.0 branch.

And this still does not mean current migration code cannot be made more verbose. No, I did not test it but somebody more skilled and knowledgeable of the code base could just check himself/herself if it could be made more verbose.