Bug 53074 - Index entry duplicated by copy and paste within source text of entry
Summary: Index entry duplicated by copy and paste within source text of entry
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.5.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: TableofContents-Indexes
  Show dependency tree / graph
 
Reported: 2012-08-02 22:25 UTC by mike.hall
Modified: 2023-05-29 03:15 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
index entry corruption example (13.18 KB, application/vnd.oasis.opendocument.text)
2013-06-26 09:56 UTC, mike.hall 		Details
Smaller example (9.76 KB, application/vnd.oasis.opendocument.text)
2015-03-23 10:35 UTC, Matthew Francis 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mike.hall 2012-08-02 22:25:13 UTC 
Steps to create:

New Document
write some text
insert an user defined index
create an index entry
update index - OK
select part of the text within the index entry, cut and paste elsewhere within the same index entry text
update index - not OK

Actual Result:
Two index entries, the cut and pasted text being the extra one plus one consisting of the original less the cut text. The extra entry seems to be 'buried' in the original. To reveal it, remove the main index entry and the cut and pasted one is then revealed.

Expected Result:
One index entry with the cut and pasted text in the intended position
Comment 1 Thomas Hackert 2013-06-25 13:45:28 UTC 
Hello Mike, *,
would you be so kind to give us a step-by-step instruction, please? You could also attach a test document to this issue, so we QA guys are able to reproduce your bug ... ;)

I am not sure, if I understand you correctly, sorry ... :( What kind of index do you want to insert and how have you done it (via "Insert - Indexes and Tables" and then...)? How have you updated the index? What do you mean with "cut and paste elsewhere within the same index entry"? Did you test it with a newer version of LO than 3.5.5.3? Does it occur there as well?

Sorry for the inconvenience
Thomas.
Comment 2 mike.hall 2013-06-26 08:18:53 UTC 
@Thomas

Thanks. No problem, I will respond later today after testing with 4.1 RC1.

The current step by step instructions look OK to me, but I will revise anyway and create a test file.
Comment 3 mike.hall 2013-06-26 09:56:30 UTC 
Created attachment 81460 [details]
index entry corruption example

@Thomas

I added you to the cc list so you would see the comments

The bug is unaltered in 4.1 RC1

The attachment includes amended step by step instructions and also illustrated the issue
Comment 4 mike.hall 2013-06-26 09:58:06 UTC 
oops, adding you didn't work...
Comment 5 Thomas Hackert 2013-06-26 12:41:48 UTC 
Hello Mike, *,
(In reply to comment #4)
> oops, adding you didn't work...

if I had enough time to follow all and one bug, where I added a comment to or did something else, I would CC me myself ... ;) But thanks anyways ... ;)

Though you have attached the document (thanks for that :) ), I had to test nearly 5 minutes to find out,
1. where and how you have created your "user-defined index" and
2. how did you updated them
... :( And for this reason I have asked you to give us a clear description ... ;) Remember, most of us QAer are volonteers here, who are doing this work in their spare time, not as their job ... ;)

But back to your bug: After playing around, I seem to reproduce your bug, when
1. Open attached document
2. Mark some words inside the text
3. Go to "Insert - Indexes and Tables - Entry..."
4. In "Insert Index Entry" changed "Index" to "User-Defined", let the filled-out "Entry" as it is, and click insert
5. Close the "Insert Index Entry" window
6. Used "Tools - Update - All Indexes and Tables" to update them
7. Marked some words in the aforementioned index, used <Ctrl>+<X> and dropped it to a different place inside the user-defined index
8. Repeated point 6

In your document, I can reproduce it without any problem, but if I create a new document with LO Version: 4.1.0.1 Build ID: 1b3956717a60d6ac35b133d7b0a0f5eb55e9155 under Debian Testing AMD64, it seems not possible to call "Tools - All Indexes and Tables", because it is greyed-out ... :( So not reproducable, but may be another bug?
Sorry for the inconvenience
Thomas.
Comment 6 mike.hall 2013-06-26 17:51:15 UTC 
@Thomas
You need to create an index entry before you can insert the index. Inserting an index works for me (on Win 7) in a new document if this step is taken first. If this isn't working on Debian, then of course it would be right for you to create a new bug report.

Contacting you privately re the QA process...
Comment 7 QA Administrators 2015-03-17 00:00:50 UTC Comment hidden (obsolete)
Comment 8 Jean-Baptiste Faure 2015-03-21 16:51:09 UTC 
This bug report has not been confirmed independently. Please do not mark your own bug report as NEW.
Set back to UNCONFIRMED.

Best regards. JBF
Comment 9 Matthew Francis 2015-03-23 10:35:15 UTC 
Created attachment 114267 [details]
Smaller example
Comment 10 Matthew Francis 2015-03-23 10:40:34 UTC 
Reproduced as follows on current 4.5 master:

- Open attachment 114267 [details]
- Cut (Ctrl+X) the word TEST on the first line
- Paste (Ctrl+V) it one word to the right (after "index")
- Right click on the index below, and "Update Index/Table"

Expected result:
- The original index entry is updated

Actual result:
- A second entry is additionally created for "TEST"


Setting -> NEW
Comment 11 A (Andy) 2015-04-04 19:32:42 UTC 
Reproducible with LO 4.4.1.2, Win 8.1
Comment 12 tommy27 2016-04-16 07:28:19 UTC Comment hidden (obsolete)
Comment 13 Jean-Baptiste Faure 2016-04-30 17:16:20 UTC 
Nothing changed in LO 5.1.4.0.0+ and master, both build at home under Ubuntu
16.04 x86-64.

I think the problem is that a part of an index entry copied is itself an index entry. If you paste it inside an index entry, you get two nested index entries.
You can verify this if you paste the copied part of the index entry on another line.
Not sure if LO can guess what the user wants, inserting a second index entry inside the first one or only modify it.

Best regards. JBF
Comment 14 mike.hall 2016-04-30 17:50:09 UTC 
IMHO it seems obvious what to do. An index entry within an index entry doesn't seem to make much sense. Therefore LO should paste in the copied content without the index characteristic, just as if it had been copied as ordinary text from elsewhere. That change might even be an easy hack.
Comment 15 QA Administrators 2017-05-22 13:39:35 UTC Comment hidden (obsolete)
Comment 16 Jean-Baptiste Faure 2017-07-22 16:04:22 UTC 
Nothing to add to my comment #13. Still reproducible in LO 5.4.1.0.0+ under Ubuntu 16.04.

Best regards. JBF
Comment 17 QA Administrators 2018-07-23 02:32:38 UTC Comment hidden (obsolete)
Comment 18 Thomas Lendo 2019-05-28 19:37:59 UTC 
Still reproducible.

Version: 6.3.0.0.alpha1+
Build-ID: 40e2a0d7039eee9c5377996da3949680903e1016
CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-05-22_13:55:35
Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE
Comment 19 QA Administrators 2021-05-28 04:50:47 UTC Comment hidden (obsolete)
Comment 20 QA Administrators 2023-05-29 03:15:13 UTC 
Dear mike.hall,

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

MassPing-UntouchedBug