Still [Reproducible] with Server installation of Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) ENGLISH UI [Build ID: 485138f-e92bf75-4c1bcb5]" Win-x86@6 – 2011-12-06_21:37:02). 

Steps to reproduce:
0. Close all LibOs
1. Check User Profile folder. My Build created a new 
   "C:\Users\user\AppData\Roaming\LOdev\3" 
2. rename subfolder "3" to "3_bak"
3. Copy / Paste folder "3" from 3.4.4 user profile
4. Start Libo Master! Everything seems to work fine, but I see the 
   reported effect

My conclusion:
a) I do something forbidden, if yes this Bug should be closed with some hints. But on <http://wiki.documentfoundation.org/UserProfile> I can't see an explicit prohibition.
b) The situation is the same as the new 3.5.0 will find when it tries to use the
   existing User Profile from 3.4

If b) we might have a fatal bug causing update problems

But the problem does not appear when I create a fresh new profile with 3.4.4 and copy / Paste it to the profile folder of 3.5. 

Further investigations shows that it's something within "registrymodifications.xcu". I attach a "registrymodifications.zip", using registrymodifications.xcu.bak (after renameing, of course" everything works fine, using "registrymodifications.xcu" from my old 3.4.4 profile causes the problem. 

Simply copying that "registrymodifications.xcu" into user profile of an other 
master build reproduces the reported problem.

Created attachment 54247 [details]
Test kit

Please see comment before how to use!

@Cédric:
Please feel free to reassign (or reset Assignee to default) if it’s not your area or if provided information is not sufficient. Please set Status to ASSIGNED if you accept this Bug.

I had the opportunity to test with 2 other PC, Problem did not appear. So it might be a problem with that particular "registrymodifications.xcu", no longer "most annoying".

I only se that with 1 particular Master + Profile configuration, nowhere else reproducible, so I close this one.

I again see this problem using  "LibreOffice 3.5.4.2  German UI/Locale [Build-ID: 165a79a-7059095-e13bb37-fef39a4-9503d18] on German WIN7 Home Premium (64bit) 
and
Server Installation of  "LibreOffice 3.6.0beta1  English UI/Locale [Build-ID: 1f1cdd8] on German WIN7 Home Premium (64bit) 
alternating with the same old user profilel

Attached new test kit contains a text document
- Read only with registrymodifications_readonlyeffect.xcu
- Works fine with
  -- registrymodifications_worksfine_new.xcu from newly created user profile
  -- registrymodifications_lastwhatworkedfine.xcu from User Profile
     backup before I started 3.6.0 the first time

Created attachment 62849 [details]
Test Kit New

Created attachment 62852 [details]
Different Behavior

"Different Behavior" contains a registrymodifications.xcu with what (on MY PC) documents will open correctly with 3.4.5, but read only with Server Installation of  "LibreOffice 3.6.0beta1  German UI/Locale [Build-ID: 1f1cdd8] on German WIN7 Home Premium (64bit)

I have opened 'sample.odt' (Test Kit New) w/ LibO 3.6.0beta1, and my customized user profile.
Works largely as expected.

Questions:

(1) Your step 5.
"Document looks like "read only", TOC and variables are white"

That may depend on Tools > Options > Appearance > Custom Colors > Text Document
☐ / ☑ Index and table shadings (and selected colors).

(2) Your step 5.
"additionally margin marks and similar are not shown"

That may depend on menu View > Text boundaries.

(3)
"TOC can be updated, texts can be edited, but paragraph and page formatting are
greyed out in Menu 'Format'."

- That may depend on the cursor position 
(only in TOC: grayed out; because: '☑ Protected against manual changes').

BTW: Replacing my LibO 3.6.0beta1 user profile with a copy of my pretty customized LibO 3.5.4 user profile (upgrade simulation) caused loss of user settings (e.g.: Options...User Data[!], Appearance) / files (e.g.: autotext, basic) with a *first* (not verfied) test. But that might be another bug report.

@manj_k:
So it is! 
 
My latest results are that the documents are again "pseudo write protected" using the affected registrymodifications.xcu, reasons are as you expect.

Details
-------
a) Index and table shadings: was unchecked
   Checking brings grey background back
b) View Text Boundaries: was unchecked
   Checking brings them back
c) My report might have been unclear, only "TOC can be updated" was TOC related,
   rest related to normal text on page. I am no 100% sure that I really
   moved caret out of toc before I checked, Caret in TOC shows the greyed out 
   menu Format icons, what would be quite normal.

So the Question remains why these settings are modified after update.

I even saw this problem after an pseudo-update 

from

- Server Installation of  "LibreOffice 3.6.0.4  German UI/Locale [Build-ID:  932b512] on German WIN7 Home Premium (64bit)

to

-Server Installation of  "LibreOffice 3.6.1.0+  English UI/ German Locale [Build-ID:  b0aac2a] on German WIN7 Home Premium (64bit)  {tinderbox: Win-x86@9, pull time 2012-08-11 00:16:39}

I still have the 3.6.0.4 server installation and added 3.6.1.0+, what uses the same user profile like 3.6.0.4

My observations:

Opening the same WRITER document with
- 3.6.0.4: Tools > Options > Appearance > Custom Colors > Text Document
  ☑ Index and table shadings 
- 3.6.1.0+: Tools > Options > Appearance > Custom Colors > Text Document
  ☐ Index and table shadings

The question is, is this still happening with the LO 4.x versions?

I change status to NEEDINFO.
we need to now if this issue is still present during 3.6.x to 4.0.x upgrade.

Dear Bug Submitter,

Please read the entire message before proceeding.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

The content of attachment 62852 [details] has been deleted

The content of attachment 62849 [details] has been deleted

The content of attachment 54247 [details] has been deleted