Bug 155104 - Merged cells in a column split if I reopen the file
Summary: Merged cells in a column split if I reopen the file
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.5.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-01 11:15 UTC by igor.arnautovic123
Modified: 2023-12-01 03:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
What happens if I reopen the saved file (179.67 KB, image/png)
2023-05-01 11:15 UTC, igor.arnautovic123
Details
What happens again (127.41 KB, image/png)
2023-05-01 11:15 UTC, igor.arnautovic123
Details

Note You need to log in before you can comment on or make changes to this bug.
Description igor.arnautovic123 2023-05-01 11:15:09 UTC
Description:
I was making a CV and I've made a table with programming languages. I made three another rows, filled them and merged the cells in the first column. Then saved and closed the file.

After the file is reopened, merged cell is split and only one cell is left and the other cells became paragraphs.

Steps to Reproduce:
1. Make 3x3 table.
2. Merge cells in left column.
3. Save and close file.
4. Reopen file.

Actual Results:
Merged cell is split after reopening file, making the table look like this:

| |_|_|
|_|_|_|
  |_|_|

Expected Results:
Three cells should stay merged.

| |_|_|
| |_|_|
|_|_|_|


Reproducible: Always


User Profile Reset: No

Additional Info:
When I split the remaing cell after reopening the file, I get this:
|_|_|_|
| |_|_|
|_|_|_|
Comment 1 igor.arnautovic123 2023-05-01 11:15:30 UTC
Created attachment 187030 [details]
What happens if I reopen the saved file
Comment 2 igor.arnautovic123 2023-05-01 11:15:45 UTC
Created attachment 187031 [details]
What happens again
Comment 3 m_a_riosv 2023-05-01 16:05:41 UTC
Works for me with
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a1acc2f46cc499631d66b1d7a923ed15ab4f28de
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Version: 7.5.3.1 (X86_64) / LibreOffice Community
Build ID: d29ee673721b12c92b3de9b9663473211414f0db
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded


Using any of odt, docx, doc formats.
Comment 4 Stéphane Guillou (stragu) 2023-05-03 12:57:37 UTC
Can't reproduce either with:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: fb3a6b82b55a298eabf8f431f1451dc826642acd
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Igor, can you please share an example file in which you can consistently reproduce the issue, with corresponding steps?
Thank you!
Comment 5 QA Administrators 2023-10-31 03:13:38 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2023-12-01 03:15:52 UTC
Dear igor.arnautovic123,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp