1. New Text Document.
2. Insert Table 2x2.
3. In cell A1 Insert Table 2x2.
4. Delete nested table.
5. Click mouse in cell where nested table used to be.
6. No cursor, but can type and cursor reappears.
If the document is saved, closed, and reopened, then the cursor is visible.
Confirmed in 126.96.36.199, Debian Sid. The cursor disappears as specified.
However, did three more tests, inserting the table before, between and after a letter in the A1 cell. Did it with the same steps but inserting the following step:
Step 2.5: According to 1 of 3 cases, type 'a' and position the cursor before or after the letter. Or, type 'aa' and place the cursor between the letters.
Inserting the table after the letter the bug does also occur.
Inserting the table before the letter the bug does not occur.
Inserting the table between two letters the bug does not occur.
** Please read this message in its entirety before responding **
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 on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
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)
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: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
Confirmed again on 188.8.131.52 under Ubuntu 14.04.
*** Bug 105330 has been marked as a duplicate of this bug. ***
Build ID: cac5c9f6081590b0548d3116bc4cd4a2509ec576
CPU threads: 4; OS: Windows 6.19; UI render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2017-07-01_00:41:48
Locale: it-IT (nl_NL); Calc: CL
Versie 184.108.40.206 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89)
but not in
Build ID: 3215f89-f603614-ab984f2-7348103-1225a5
Build ID: 505ce3a2ba3adeef46daecbf9b14c42cea211408
CPU threads: 8; OS: Linux 4.9; UI render: default; VCL: gtk3;
Locale: nl-BE (en_US.UTF-8); Calc: group
Build ID: SlackBuild for 5.3.4 by Eric Hameleers
CPU Threads: 8; OS Version: Linux 4.9; UI Render: default; VCL: kde4; Layout Engine: new;
Locale: nl-BE (en_US.UTF-8); Calc: group
Created attachment 136743 [details]
demo@Demo:~/bibisect-43all$ git bisect bad
d3f11a2232b85bc3ab3e69000f571c0eba1930fd is the first bad commit
Author: Bjoern Michaelsen <firstname.lastname@example.org>
Date: Wed May 2 19:14:52 2012 +0200
Author: Stephan Bergmann <email@example.com>
AuthorDate: Mon Apr 23 11:47:45 2012 +0200
Commit: Stephan Bergmann <firstname.lastname@example.org>
CommitDate: Mon Apr 23 11:47:45 2012 +0200
Do not fail for legacy rdb that only contains root key
:100644 100644 b453a604fc3c5fb4f63f3aed412de93d20c55f20 30cc0b83db3fdcc1184dc05167bee66d47065710 M ccache.log
:100644 100644 5b0c05d5b6e9bda9bd68f447b69ed7bed74e3f33 06d353cf5a0dd1d1225f43c0f21e1401f4316324 M commitmsg
:100644 100644 c6128a76d64ef1fe9d7cfd8fbb4cddb737fcf551 e9791ae34f56f896af9eeb3ad1a21850bb54b086 M dev-install.log
:100644 100644 c0a3d2e12aaac1a7028a9d2c80d22e60efd1998f 43a4d682bdd87ac9421ebe7a42ce229c9f1acba7 M make.log
:040000 040000 39dc0b7004ecedf0b4458a6b1df2c44f75bb8725 ae3ab874138db9d0d407fc0f11d1738a17f398b8 M opt
:100644 100644 3098f58f38447b6f729b16c23f3edcc4ae973b8a 27ab6b5b5adb9e65e24651db698082531c3d5593 M patch.log
Created attachment 136744 [details]
No repro with
Build ID: d1bc14b318c9a412a761d243085da0895a1aed4a
CPU threads: 4; OS: Mac OS X 10.12.6; UI render: default;
Locale: nl-NL (nl_NL.UTF-8); Calc: group threade
Also for me not reproducible in
Version: 220.127.116.11.alpha0+ (x64)
Build ID: d64ce643275e0b2b0dea9e532fc261391dc8793c
CPU threads: 4; OS: Windows 10.0; UI render: GL;
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-03-01_03:24:30
Locale: de-DE (de_DE); Calc: CL
But see bug 116144
Telesto, you opened the new bug 116144. So do you think, we can close this bug as WORKSFORME?
Thanks for the confirmation: Closing WFM