Created attachment 140945 [details] Hardcopy of a sixfold re-selection In Writer select two not contiguous text portions, using Ctrl for the second selection (for a contiguous selection there is a similar effect, but it's more difficult to describe). Then use Ctrl+Right or Ctrl+Left. Then, as it should be, the cursor jumps to the start of the next word or to the previous one. But the selection is not cancelled, it remains and will only vanish if you close the document. Thus it seems that only the surface representation is affected. This is confirmed by the fact that if you create a selection elsewhere and change the attributes, then only this new selection is affected. The object CurrentSelection also shows only the new selection or simply the cursor position. It seems that pressing Ctrl is the signal for retaining the selection, even though the combination Ctrl+Right or ...Left does something completely different. As someone pointed out to me, you can even cumulate the effect by again and again selecting parts of the same primary selection; I enclose a hardcopy of a sixfold selection, resulting in an ever deeper blue colour. I could reproduce this in Windows 10 for many LibO versions since 4.1.0.2.0. In versions 3.5.0rc3 and older and in OpenOffice this does not happen. For the intermittent versions I cannot say anything, as I had technical problems installing them. This behaviour has been reproduced twice by other people for different Linux installations and different LibO versions, too.
Same behavior in: Version: 5.4.5.1 Build-ID: 40m0(Build:1) CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: kde4; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group
Confirming with WIN10-Home 1709, 64-Bit; Version: 6.0.2.1 (x64) Build-ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89 CPU-Threads: 8; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group
Found in 4.0.0.3 but not in LibreOffice 3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5
Created attachment 140972 [details] bt with debug symbols On pc Debian x86-64 with master sources updated yesterday + enable-dbgutil, I don't reproduce this but have an assertion when trying to close the doc.
(In reply to Julien Nabet from comment #4) > Created attachment 140972 [details] > bt with debug symbols > > On pc Debian x86-64 with master sources updated yesterday + enable-dbgutil, > I don't reproduce this but have an assertion when trying to close the doc. The is no actual hang (in the sense of non-responding). The text selection is persisted
The title says that the section hangs, not the application. But to be precise we should say that the selection is cancelled correctly, whereas the selection marking still persists and is visible, which is at least confusing
Bibisected on Ubuntu 14.04 with 43all to range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=179a6db61ee30cf776747802f06edeef45fec461...558476135865d9ae7b8801a82c177fd1098386ff I am unable to locate a suspicious commit.
Dear Gerhard Weydt, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The bug is still present in versions 6.2.4.2 and 6.3.0.1
repro 7.3+. I couldn't find a suspicious commit either in the two-page range.
(In reply to Buovjaga from comment #7) > Bibisected on Ubuntu 14.04 with 43all to range > https://cgit.freedesktop.org/libreoffice/core/log/ > ?qt=range&q=179a6db61ee30cf776747802f06edeef45fec461... > 558476135865d9ae7b8801a82c177fd1098386ff > > I am unable to locate a suspicious commit. Well this commit is in range & meddling with cursor position code author Michael Stahl <mstahl@redhat.com> 2012-09-19 20:47:48 +0200 committer Michael Stahl <mstahl@redhat.com> 2012-09-19 21:02:13 +0200 commit af4b6c94c68b5f67b931cde8d0acda6ec8b288bb (patch) tree 9690c79ff900f320244e46a195f5a7df7677142e parent b74da58c7e85f92e6ce2d061dd3ced26e12a1dff (diff) rhbz#689053: fix crash following delete at last table cell https://cgit.freedesktop.org/libreoffice/core/commit/?id=af4b6c94c68b5f67b931cde8d0acda6ec8b288bb But well would need a revert (if still possible) to verify
1. Open attachment 178254 [details] 2. Select a 4 words with CTRL+Double click (but not 'bare foot') 3. SHIFT+CTRL+ARROW Right 4. Deselect.. notice 3 words still being in selected mode
Dear Gerhard Weydt, 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