Description: Since LO 4.0.x, it has been possible to close Draw's page pane and have that setting remembered. If you open a brand new drawing while your page pane is disabled, all toolbars are missing. If you click in the document, the toolbars come back and everything is peachy. If you try to enable the page pane again while the toolbars are missing, LO CRASHES. Steps to reproduce: 1. Open a new Draw drawing 2. If pane page is enabled, disable it (View -> Page Pane) 3. Close the drawing 4. Open a new drawing Expected: All toolbars should show and everything should look/work like normal. Actual: Only the main toolbar shows. At this point you can do one of two things: 1. If you click in middle of drawing, the screen redraws and the toolbars come back. 2. If you re-enable the page pane (View -> Page Pane) while the toolbars are still missing, LO will CRASH and you will lose any unsaved work. I can confirm this bug affects a number of versions: LO 4.1.4.2 under 32bit Windows 7 L0 4.1.4.2 under 32bit ArchBang L0 4.0.2.2 under 32bit Fedora17 L0 4.1.4.2 under 32bit Fedora17 LO 4.2.0.2 rc under 32bit Fedora17 I also tested LO 3.5.7.2 under Fedora 17, but in this version, it wasn't possible to permanently disable the page pane. Because of this, I'm setting the version to 4.0.0.3.
I can confirm that this still affects LO 4.2.1.1 under 32bit Fedora 17. This bug seems very very reproducible, so I'll go ahead and change status to New. I will also attempt to properly prioritize it according to the bug prioritization flowchart. Since this bug repeatably leads to a crash, that appears to automatically classifies it as a minimum of "medium-critical." https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg
I just tried to reproduce this bug on another system and realized that disabling desktop effects is vital to reproducing this bug. In all of my previous test environments, fancy desktop effects were disabled. These effects may cause the screen to redraw and make this bug untestible. For instance, to test under MS Windows, Control Panel -> System -> Performance Settings -> "Adjust for best performance" Under my Linux environments, I've been using IceWM and OpenBox with no effects enabled.
I think I figured out the primary cause of the bug: I have a toolbar docked to the left side of the page in my test environments. My guess is that side-docked toolbar positioning is somehow causing a conflict with the hidden page pane.
Confirmed in RHEL 6 + LO 4.3.4.1 and some older versions too. Had noticed this a long time ago but never reported it....my bad... especially since I do like to have the annoying page page hidden and I also have the "Drawing" toolbar on the left. As a possibly related problem- when I have the page page hidden, when I start a NEW draw document window, the "Drawing" toolbar doesn't even show on the screen until I click into the page area. Doesn't matter where you dock the "Drawing" toolbar. Should I report this as a different bug?
(In reply to crxssi from comment #4) > As a possibly related problem- when I have the page page hidden, when I > start a NEW draw document window, the "Drawing" toolbar doesn't even show on > the screen until I click into the page area. Doesn't matter where you dock > the "Drawing" toolbar. Should I report this as a different bug? You're right about the toolbar location not having anything to do with this bug. I was able to reproduce this bug without the toolbar on the left. Other than that, your description seems to match my original post, so I believe you are suffering from the same bug. Unfortunately, this bug is very intermittent for me. I'll go back to actively trying to figure out how to reproduce it.
OK, I think one of the factors is the theme. I started with a base system of archbang (openbox on arch linux) with LibreOffice 4.3.4.1 installed. Here are my steps/conclusions in order: 1. Removed my ~/.config/libreoffice/4 directory to start fresh 2. Start LO 3. New Drawing At this point everything came up correctly since I had a page pane and I haven't changed themes. 4. Disabled page pane (View->Page Pane) 5. Close drawing (Ctrl-w) 6. New Drawing At this point, everything came up correctly since we haven't changed themes. 7. Change theme to galaxy (Tools->Options->View->Icon Style to Galaxy 8. OK 9. Close drawing (ctrl-w) 10. New Drawing BUG! Only the "Standard Toolbar" at the top is visible. If you click anywhere, the other toolbars will redraw or if you perform a view->page pane, LO will crash. At this point, if I change the theme back to the default of Tango, everything is fine and I'm not able to trigger the bug. Themes that trigger bug: Hicontrast Crystal Galaxy Themes that do NOT trigger bug: Sifr Oxygen Tango I also tested this under LO 4.2.7.2 using Mint 17 using Xfce. The only theme installed was "Human" and that triggered the bug too.
This one isn't testable as of version 5.0 because of bug 90987, which is a regression that doesn't allow draw/impress to remember the previous states (open/close, hidden/shown) of the sidebar or page pane.
Checked on Win7 LO 5.1.0.0.alpha1+ Opening draw 2nd time indeed hides the left toolbar (the one with the shapes). Klicking to the doc brings it back. Reactivating the page pahe does not crash here, tried several times.
(In reply to Armin Le Grand from comment #8) > Checked on Win7 LO 5.1.0.0.alpha1+ > Opening draw 2nd time indeed hides the left toolbar (the one with the > shapes). Klicking to the doc brings it back. Reactivating the page pahe does > not crash here, tried several times. I can confirm your findings! The crash part at least appears to be fixed in the master nightly. LO 4.4.6.3 will, of course, still crash. And as mentioned above, LO 5.0.x versions have a bug where the page pane doesn't remember its state.
Since this bug no longer causes a crash, I've updated the title and have greatly reduced the importance fields. I even thought about closing it as worksforme, but the original description is still mostly valid. Also, for an update, bug 90987 was fixed in LO 5.0.4, so page pane state is back to being remembered again and this bug is once again testable on the 5.0 branch.
** 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.1.6 or 5.2.3 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-20170103
I can still reproduce this in Version: 5.3.0.3 Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: x11; Layout Engine: new; Locale: en-US (en_US.UTF-8); Calc: group
** 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 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
Dear tmacalp, 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://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
Dear tmacalp, 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
This is resolved since libreoffice-6.1.4.1 Checking with the linux-64-6.1 bibisect repo, the fixing commit is Caolán's 45519023aa44940a68f40643fdff6551a2b7adb3 for bug 119997 but not marking as a duplicate as it started at different times. Thanks Caolán and everyone else!