1. create a new document. Shortest way to test is to use an envelope size page or other short page. 2. Format -> Page and click Header, turn header on, uncheck Same Content on First Page 3. Type a line into the Header (possibly two lines) 4. Click to begin typing in the main body 5. Format -> Columns and select two columns 6. Start typing in short lines. 7. Once a new line of typing puts you into the 2nd column, the header disappears, and is completely uneditable, and Undo does not restore it. Does not occur if one types all content first and then formats a header and columns. If you do it this way then you can edit the columns all you want and the header stays.
Hi Shannon, thanks for the issue. I do not have this problem - will attach a test file: continue typing in there after the last bla bla line to test. Can you attach your test file? best, Cor
Created attachment 89946 [details] test file with header / colums
It looks like the issue is (perhaps also) triggered by a tab in the Header. I could not reproduce this today using the above instructions. It is hard to pin down but I am still able to get it to reliably behave badly very quickly. One extra thing I would do is type in the header, then tab until the cursor is at the right margin. typing a few more words you can see it is automatically right-aligned. Then press return and type a little into the second line of the header. I was able to get the crash just by backspacing and altering the header all by itself. However the columns appeared to make the problem occur the other day. At some point one of two things will happen: the header will disappear, and/or LibreOffice will crash. I was going to write up the crasher separately, but ran out of time. Perhaps they are related anyway. This is on Windows 7 Home Premium SP1, Intel I5-4430 in case that matters.
Created attachment 90010 [details] example file for header/column crasher/disappearance bug This is a starting point for creating the behavior. As I mentioned in my comment, the appearance of the problem is unpredictable, but it is soon after where I have left off in creating this document. Basically I was attempting to format a recipe on a 3x5 index card. Hope this helps.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Unable to reproduce header disappearance or crash. Shannon: if you can still get it to crash, you could try getting a backtrace: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg Tested on Win 7 64-bit Version: 4.4.0.0.alpha1+ Build ID: b167d1127e1579468a74c4414e7f4f33d9d24122 TinderBox: Win-x86@51-TDF, Branch:MASTER, Time: 2014-11-02_03:04:44
I can reproduce with Version: 4.5.0.0.alpha0+ Build ID: a272f5b7b30f356418ecf28eb95d066f081d1624 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-01-09_09:50:59
Created attachment 112318 [details] gdbtrace
Created attachment 112319 [details] printscreen of freeze to reproduce write some text and delete some text, then in header delete text, use TAB keys and write text to header on right side
** 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.4 or later) 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
** 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.2.5 or 5.3.0 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
This is hardly repeatable bug and no response to QA ping. So I put it in Needinfo to see if it happens with fresh LO 6.3.3 or master.
Dear Shannon W., This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Shannon W., 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