Under OOo2, i tweaked many preferences ... and they are just gone when i start OOo3. People from IRC told me that Windows installer offers the choice to import the old user profile, and that, under Linux, when installation is performed by distro, the first launch should offer me the same choice. Fact is: - there is no message about this in elogs - I had not been ask anything when i started OOo3 first time. I put this bug 3.*, because 3.0.1 is about to come out, and this bug should affect all stable and unstable versions of ooo3. Unstable should be changed into new releases; stable may be just changed, without revision number change. This is very annoying problem, for people who are intensively using OOo, and can be frustrated by a "loss of profile without any message". For single user workstation, we would want ewarns to tell about this. For all systems, including large scale servers, we would want all users to be offered the opportunity to import their profile. Otherwise, people who wpent hours on customizing their profile will just say insults about OOo3 first time they use it. This is urgent. Please put high priority. Ewarn is trivial to do. Warning user on first start may be more difficult.
What I wrote produce wrong page layout; 4th alinea I meant: > I put title for this bug with label "OOo-3.*" because ...
Here is how to recover old profile manually: dhp@moon-gen-3:~$ mv .ooo3 .ooo3_old dhp@moon-gen-3:~$ cp -a .ooo-2.0 .ooo3 dhp@moon-gen-3:~$ This is not perfect, I still have bugs, but, it is the main thing to know to recover old settings very fast.
OOo 3.0 (the source version) actually does automatically migrate your settings from the 2.x-version the first time you start it. I did test this and it works. The binary on the other hand already has a warning, so as far as I see, everything you are asking for is already provided.
... but did not happen for me. You said you tested the source verbatim version ? I am telling about the Gentoo compiled one !
Created attachment 170175 [details] /tmp/emerge--info
(In reply to comment #4) > ... but did not happen for me. > > You said you tested the source verbatim version ? I am telling about the Gentoo > compiled one ! > No I didn't say that. I've been talking about app-office/openoffice package in portage cause that's what we support ;)
... just to check :) (In reply to comment #6) > No I didn't say that. I've been talking about app-office/openoffice package in > portage cause that's what we support ;) Of course :) => I am using app-office/openoffice-3.0.0 , not app-office/openoffice-bin-3.0.0 . If nobody cant repro, and every body else got the expected pop-up, just close this bug in a few weeks/month. In which place does OOo3 store the information that the user have been asked this choice ?
(In reply to comment #7) > ... just to check :) > > (In reply to comment #6) > > No I didn't say that. I've been talking about app-office/openoffice package in > > portage cause that's what we support ;) > > Of course :) => I am using app-office/openoffice-3.0.0 , not > app-office/openoffice-bin-3.0.0 . If nobody cant repro, and every body else got > the expected pop-up, just close this bug in a few weeks/month. In which place > does OOo3 store the information that the user have been asked this choice ? > Like I said before, all this is done automatically, so the users are not asked at alll
That's not cor(In reply to comment #8) > (In reply to comment #7) > > ... just to check :) > > > > (In reply to comment #6) > > > No I didn't say that. I've been talking about app-office/openoffice package in > > > portage cause that's what we support ;) > > > > Of course :) => I am using app-office/openoffice-3.0.0 , not > > app-office/openoffice-bin-3.0.0 . If nobody cant repro, and every body else got > > the expected pop-up, just close this bug in a few weeks/month. In which place > > does OOo3 store the information that the user have been asked this choice ? > > > > Like I said before, all this is done automatically, so the users are not asked > at alll No, that's not accurate. The problem is that the Gentoo openoffice-bin package does not use the vanilla defaults. OpenOffice.org expects to find user profile directory at: ~/.openoffice.org2 In the Gentoo ebuild, the directory goes to: ~/.ooo-2.0 If OpenOffice.org 3.0 does not find a profile directory in the expected location, it assumes a new install and never prompts the user to transfer personal data. The OOo default profile locations are: ~/.openoffice.org2 and ~/.openoffice.org/3 Judging by the form of the new path, I suspect it will remain this way for future releases, with only the version number changing. These paths are set in the global bootstraprc.
(In reply to comment #9) Very interesting; could please check if it is the same for the source version (aka not "-bin") ? Thanks :)
(In reply to comment #10) > (In reply to comment #9) > > Very interesting; could please check if it is the same for the source version > (aka not "-bin") ? Thanks :) Do I have to? I have a working binary installation now and it will take me hours to build from sources. This is easy enough for you to test yourself if you are running a source build. Make a backup of your .ooo3 directory, copy .ooo-2.0 to .openoffice.org2, then restart OpenOffice. >
(In reply to comment #11) I have a source installed. I dont think i need to rebuild to make the test at all. But, how do I test this ? strace ? your comment 9 does not say anything about *how* you determined what you said ...
(In reply to comment #12) > (In reply to comment #11) > > I have a source installed. I dont think i need to rebuild to make the test at > all. But, how do I test this ? strace ? your comment 9 does not say anything > about *how* you determined what you said ... I read the OpenOffice documentation, spoke with somebody in the IRC channel, and tested it. You need to follow my instructions and see what happens. If OpenOffice asks if you want to transfer personal data when you start it up after making the changes, then those changes have worked and the bug is valid.
(In reply to comment #9) > That's not cor(In reply to comment #8) > > (In reply to comment #7) > > > ... just to check :) > > > > > > (In reply to comment #6) > > > > No I didn't say that. I've been talking about app-office/openoffice package in > > > > portage cause that's what we support ;) > > > > > > Of course :) => I am using app-office/openoffice-3.0.0 , not > > > app-office/openoffice-bin-3.0.0 . If nobody cant repro, and every body else got > > > the expected pop-up, just close this bug in a few weeks/month. In which place > > > does OOo3 store the information that the user have been asked this choice ? > > > > > > > Like I said before, all this is done automatically, so the users are not asked > > at alll > > No, that's not accurate. Sorry, but this gets a bit annoying, (In reply to comment #9) > That's not cor(In reply to comment #8) > > (In reply to comment #7) > > > ... just to check :) > > > > > > (In reply to comment #6) > > > > No I didn't say that. I've been talking about app-office/openoffice package in > > > > portage cause that's what we support ;) > > > > > > Of course :) => I am using app-office/openoffice-3.0.0 , not > > > app-office/openoffice-bin-3.0.0 . If nobody cant repro, and every body else got > > > the expected pop-up, just close this bug in a few weeks/month. In which place > > > does OOo3 store the information that the user have been asked this choice ? > > > > > > > Like I said before, all this is done automatically, so the users are not asked > > at alll > > No, that's not accurate. > > The problem is that the Gentoo openoffice-bin package does not use the vanilla > defaults. OpenOffice.org expects to find user profile directory at: We've been talking about the source-based version all the time, so I don't quite know how your observations should be helpful here, they simply don't apply in the latter case.
(In reply to comment #11) > This is easy enough for you to test yourself if you are running a source build. > Make a backup of your .ooo3 directory, copy .ooo-2.0 to .openoffice.org2, then > restart OpenOffice. That advice is plain wrong, you are making assumptions based on the binary version, which are not true for the source based release (because they are NOT the same).
(In reply to comment #15) > (In reply to comment #11) > > This is easy enough for you to test yourself if you are running a source build. > > Make a backup of your .ooo3 directory, copy .ooo-2.0 to .openoffice.org2, then > > restart OpenOffice. > > That advice is plain wrong, you are making assumptions based on the binary > version, which are not true for the source based release (because they are NOT > the same). Assumptions? I am not making any assumptions: I'm describing a test protocol to determine if the source version is behaving the way the vanilla OpenOffice.org distribution behaves. And the bug summary says: "app-office/openoffice-3.* installation should warn about user directory to be forgotten, and offer to import old profile" It says nothing about whether we're discussing the source or binary ebuild. I'm going to let the proof be in the pudding. So far, you've failed to address the original poster's question. Are we going to fix the problem or not?
(In reply to comment #16) > I'm going to let the proof be in the pudding. So far, you've failed to address > the original poster's question. Are we going to fix the problem or not? As comments more and more look like forum-trolls (stupid ideas around, uncomplete descriptions, quotes of quotes of quotes ...), I think I will close this bug, and create a new one from scratch, and hope it will be considered a bit more seriously. Stephen, how did you determine what you state in comment 9 ? strace ?
(In reply to comment #17) > Stephen, how did you determine what you state in comment 9 ? strace ? No, I didn't do it with strace. I read the OpenOffice documentation and spoke with some people in the OOo IRC channel. I tested it by renaming the Gentoo OpenOffice.org profile directory (.ooo-2.0) to the default (.openoffice.org2), then restarted OpenOffice.org 3. After doing that, it asked if I wanted to transfer personal data, as expected. It's pretty straightforward. Try it yourself. Either way, the openoffice-bin package should be fixed so that this doesn't happen. I can't speak to the source version as I don't use it.
(In reply to comment #18) > I read the OpenOffice documentation and spoke with some people in the OOo IRC > channel. I tested it by renaming the Gentoo OpenOffice.org profile directory > (.ooo-2.0) to the default (.openoffice.org2), then restarted OpenOffice.org 3. So, from what you say, the real problem is not OOo3 not asking question, but OOo2 in Gentoo not storing the profile at the place it should ? This is still a backward compatibility; and the more we wait, more users will get angry against profile loss. Think that every day passing, dozens people update their Gentoo. Soon I can close this bug "deprecated" :) Anyway, if the problem is that Gentoo version 2 did not store profile at the official place it should, our OOo3 should still take this into consideration. I will test this in a few minutes.
I did dhp@moon-gen-3:~$ mv .ooo3 .ooo3_ dhp@moon-gen-3:~$ cp -a .ooo-2.0 .openoffice.org2 And on next start, I have not been asked anything, and macro were disabled (macros used to be enabled in my #2 profile). Then I did dhp@moon-gen-3:~$ rm -rf .ooo3 strace ooffice >/tmp/ooffice.strace.log 2>&1 but, I found only this in the log: stat64("/home/dhp", {st_mode=S_IFDIR|0755, st_size=32768, ...}) = 0 stat64(".", {st_mode=S_IFDIR|0755, st_size=32768, ...}) = 0 we wont go far with this. Stephen, I just tried what you said, and it fails for me. Using source version. Maybe I should pack my source version, and try installing the bin package for test ... I am just too lame tonight. Keep in touch.
(In reply to comment #20) > Stephen, I just tried what you said, and it fails for me. Using source version. > Maybe I should pack my source version, and try installing the bin package for > test ... I am just too lame tonight. Keep in touch. Like I said before: The paths Stephen gave are wrong for the ooo-build / source-based version, so no wonder nothing happens here. They are indeed the default paths for the binary version, but we change them during the install process for a simple reason: Using the same ones as for the source version, so people can change between both without loosing their settings. This breaks the migration stuff with -bin but we actually warn about this in the ebuild. But you've been asking about the source based version and that's what my earlier answers have been focused on accordingly. As I don't seem to have made this clear enough, let's give it another try: Your user settings should be automatically moved over from .ooo-2.0 to .ooo3 the first time you start OOo 3.x (or any later time if you don't yet have a .ooo3 user install). There is no graphical migration wizard, no "pop-up", nothing like that, just the data being migrated from the old to the new directory.
(In reply to comment #21) Your user settings should be > automatically moved over from .ooo-2.0 to .ooo3 the first time you start OOo > 3.x (or any later time if you don't yet have a .ooo3 user install). There is no > graphical migration wizard, no "pop-up", nothing like that, just the data being > migrated from the old to the new directory. Do you migrate every thing, or are there exceptions ? I can hardly determine because the only important setting I had set in OOo2 that I can remember of is "allowing macros", and, a guy on IRC told me that the migration process disables it any way during the migration "for security reasons". If OOo should migrate everything, then it is not the case. If it should migrate everything except a short list of params concerning security, then I have to find and remember an other param as witness.
(In reply to comment #21) Your user settings should be > automatically moved over from .ooo-2.0 to .ooo3 the first time you start OOo > 3.x (or any later time if you don't yet have a .ooo3 user install). There is no > graphical migration wizard, no "pop-up", nothing like that, just the data being > migrated from the old to the new directory. No. Tested again, there is no migration. Not even a blind one. After dhp@moon-gen-3:~$ rm -rf .ooo3 According to what you say, I should inherit my old OOo2 profile silently. I will stop telling about macros being disabled, because the guy on IRC told me it was disabled anyway during the migration process. Then, I want in the "recent open documents", and the list was empty; and I sware I opend hundreds documents per month: it should not be empty. Then I have gone in the "save" settings, and found an "autosave every ..." = 15mn, whic IS the default settings, what is really too much for me (I usually put 1 mn). Then, I removed .ooo3 and restaured the .ooo3 I build by copying .ooo-2.0 and open OOo again. Now, the "recently open documents" list contains a list of about 10 files, amongst which I see files I last open BEFORE my OOo3 migration. And the autosave time is 7mn (not 1mn because I had to increase the value last month). I also checked for the language set for spell check, and few other things, but they are identical; lang is set to en_UK which is my locale, so it is impossible to know if migration set lang to en_UK because of inheritance, or because of ENV vars. The only thing that was kept during migration, and that I can not imagine how a fresh OOo3 could guess is that ... I found my real name in the author/owner settings (my real name is not in /etc/passwd or exports). So, if we forget about macros, migration still looses the recent document list, and the save time; in the best case, I may admit it kept in memory my name as author for documents. 3 params lost over 6 test points I can remember. A more subjective point: the toolbars on top of the GUI: when opening the same document with either no .ooo3 or the one I copied manually ... I dont have the same toolbars on top. This is more subjective because I am not really sure how this is stored in profile, and, how deep it should be compatible after update.
(In reply to comment #21) > But you've been asking about the source based version and that's what my > earlier answers have been focused on accordingly. As I don't seem to have made > this clear enough, let's give it another try: Your user settings should be > automatically moved over from .ooo-2.0 to .ooo3 the first time you start OOo > 3.x (or any later time if you don't yet have a .ooo3 user install). There is no > graphical migration wizard, no "pop-up", nothing like that, just the data being > migrated from the old to the new directory. So, in the source version, it does this silently?
(In reply to comment #24) > > So, in the source version, it does this silently? > Exactly
Original report is invalid see the comments above
