Bug 51267

So?  If the LO BASIC machinery stores in one part of UserInstallation (user/registrymodificiations.xcu) information about data it stores in another part (user/basic/), manually modifying only one place will likely get the machinery confused.  (I did not bother to check whether the machinery really works this way, but it looks highly likely.  And in any event, manually modifying the UserInstallation is not supported.)

Hey, and me being so naive to expect that a new registrymodifications.xcu respects data that is in the tree :-)

But - what the * - so I lose all my carefully defined custom colors too.. And what more? Ugh. Have to check and really need to add a warning to our FAQ about solving particular problems by dumping the registrymodifications.xcu.

have some question though ..

Hi Stephan,

Shout myself in the foot again with some for of this issue ;)

Now I tested with a fresh profile in 4.4.0.alpha2

(In reply to Stephan Bergmann from comment #1)
> So?  If the LO BASIC machinery stores in one part of UserInstallation
> (user/registrymodificiations.xcu) information about data it stores in
> another part (user/basic/), 

All that is stored, is data about the UI.
No sign of the new module or the new library that I added.

> ...  manually modifying only one place will likely
> get the machinery confused.  (I did not bother to check whether the
> machinery really works this way, but it looks highly likely.  

 ;)
Based on my experiment, I would say that there is no need for LibreOffice to overwrite basic.xlb and scripts.xlb when a new registrymodifications.xcu is written.

> And in any event, manually modifying the UserInstallation is not supported.)

On the other hand: the advise to start with a clean userprofile, i.e. remove the registrymodifications.xcu, is given on daily basis to many people around the world..

Interested in your thoughts and insight,
Cor

*** Bug 55005 has been marked as a duplicate of this bug. ***

(In reply to Cor Nouws from comment #4)
 
> All that is stored, is data about the UI.
> No sign of the new module or the new library that I added.


> Based on my experiment, I would say that there is no need for LibreOffice to
> overwrite basic.xlb and scripts.xlb when a new registrymodifications.xcu is
> written.

The same applies for colors in the standard.soc and probably more in /user/config/

(In reply to Cor Nouws from comment #4)
> On the other hand: the advise to start with a clean userprofile, i.e. remove
> the registrymodifications.xcu, is given on daily basis to many people around
> the world..

I hope nobody routinely gives the bad advice to remove registrymodifications.xcu.  What should be given as advice is to try with the existing user profile (i.e., the whole directory tree) moved away, cf. <https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile>.

(In reply to Stephan Bergmann from comment #7)
> I hope nobody routinely gives the bad advice to remove
> registrymodifications.xcu.

That probably is behaviour that I adapted myself, to reuse simply as much as possible from the previous config.

Removing registrymodifications.xcu results only in config colors and macro's to be lost..

I'll think if I can make a useful addition to the nice documentation on the wiki.

(In reply to Cor Nouws from comment #8)
> Removing registrymodifications.xcu results only in config colors and macro's
> to be lost..

Not sure I'm missing context here, but in general that's of course not true.  For example, virtually any setting made under "Tools - Options..." is lost when you remove registrymodifications.xcu.

(In reply to Stephan Bergmann from comment #9)
> (In reply to Cor Nouws from comment #8)
> > Removing registrymodifications.xcu results only in config colors and macro's
> > to be lost..
> 
> Not sure I'm missing context here, but in general that's of course not true.

I was too brief: of course I meant to say from what is stored in the directories that are inside /user

> For example, virtually any setting made under "Tools - Options..." is lost
> when you remove registrymodifications.xcu.

yep.