Bug 131024 - WRITER TABLES: Change of text orientation in merged cells produces write-protected content
Summary: WRITER TABLES: Change of text orientation in merged cells produces write-prot...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Writer-Tables Writer-Tables-Alignment
  Show dependency treegraph
Reported: 2020-02-29 10:21 UTC by djnesic
Modified: 2023-12-06 03:17 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description djnesic 2020-02-29 10:21:09 UTC
I merge the cells in the table in LO Writer and try to orient the text from bottom to top. When I leave the table and click on the merged cells again and try to type or change the text LO Writer displays "Write - protected content cannot be changed". Is this happening to someone else or just me and how to fix it? I'm using LO 6.3.5 on Linux Mint OS 19.3.
Comment 1 Dieter 2020-03-02 17:49:49 UTC
I ca't confirm it with

Version: (x64)
Build-ID: dd0751754f11728f69b42ee2af66670068624673
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: threaded

To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present.
Comment 2 djnesic 2020-03-02 19:25:39 UTC
The profile is reset and it's all the same again. This only happens when the vertical cells merge (per column).
Comment 3 Ming Hua 2020-03-02 20:02:18 UTC
I think I can reproduce this. Detailed steps to reproduce:

1. Create a new blank document with Writer;
2. Table > Insert Table..., insert a 5-row by 5-column table;
3. Use mouse to drag and select the four vertical cells on the left-bottom corner, i.e., the first cells of row 2, 3, 4 and 5;
4. Table > Merge Cells;
5. Table > Properties... > Text Flow, change text direction to "vertical (bottom to top)";
6. Type two lines of random text, end each line with Enter key (for some reason the text is invisible on my system, but that's probably for another bug);
7. Click in anther cell and click back into the merged cell;
8. Press Backspace key;
9. Write protection dialog pops up.

Reproduced with both 6.3.5 and 6.4.1 RC1 on Windows 10:

Version: (x64)
Build ID: dd0751754f11728f69b42ee2af66670068624673
CPU threads: 2; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: zh-CN (zh_CN); UI-Language: en-US
Calc: threaded

版本: (x64)
Build ID: 56f3c78975db08733f771c53643b5d1aa7c57567
CPU 线程: 2; 操作系统: Windows 10.0 Build 18363; UI 渲染: 默认; VCL: win; 
区域语言: zh-CN (zh_CN); UI 语言: zh-CN
Calc: threaded

I'll refrain from confirming this bug until someone else (looking at Dieter :-) can reproduce with my steps.
Comment 4 Dieter 2020-03-02 20:23:55 UTC
Ming, if you can confirm a bug, you are also allowed to change status to NEW

=> NEW

But now I can also confirm it with

Version: (x64)
Build ID: 41177730421f9be9ad955766a5a19667d8003b11
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-GB
Calc: threaded
Comment 5 Ming Hua 2020-03-02 20:37:45 UTC
(In reply to Dieter from comment #4)
> Ming, if you can confirm a bug, you are also allowed to change status to NEW
Thanks Dieter, I know and I've done that for other bugs.

It's just that for this one, the reporter's description is so vague that I'm not sure I'm reproducing exactly what he experienced.  So I'd rather wait for a second (third?) opinion.
Comment 6 djnesic 2020-03-02 20:54:07 UTC
Ming Hua,your description is what is actually happening.
My English is weak and this is why it's a weaker description.
Comment 7 QA Administrators 2023-12-06 03:17:56 UTC
Dear djnesic,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team