Description: The drawing toolbar is always lagging behind when opening draw document. A small but noticeable delay when rendering. There is one file failing to load (but not sure if that's the cause). Z:\Program%20Files%20(x86)\LibreOfficeDev%206\share\config\soffice.cfg\simpress\layoutlist.xml Steps to Reproduce: 1. Open Draw 2. Check if the Draw toolbar is enabled and attached to the left side next to the slide pane. 3. Close the Draw document 4. Open Draw again from the start center (and notice a small delay before the toolbar gets added and everything gets re-positioned Actual Results: A small delay with the Draw toolbar Expected Results: The toolbar should be loaded at once, not lagging behind (as it did before in LibO5.1.03) Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 6.0.0.0.alpha0+ Build ID: cbf371e07fd5dea1ea08a1f299360d1273961ebd CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-06-14_23:13:57 Locale: en-US (nl_NL); Calc: CL and in Version: 5.2.5.0.0+ but not in Version: 5.1.0.3 Build ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737 CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; Locale: en-US (nl_NL) User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Created attachment 134167 [details] Screencast
Yep. Version: 5.4.0.1 (x64) Build ID: 962a9c4e2f56d1dbdd354b1becda28edd471f4f2 CPU threads: 4; OS: Windows 6.19; UI render: default; Locale: fi-FI (fi_FI); Calc: group Version: 5.0.2.2 (x64) Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: en-US (fi_FI)
No repro with: Version: 6.0.0.0.alpha0+ Build ID: c7fe625c8d41f648f89765abc40bb7b8fd4ed12a CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-07-16_02:04:02 Locale: nl-NL (nl_NL); Calc: CL
(In reply to Telesto from comment #3) > No repro with: > Version: 6.0.0.0.alpha0+ > Build ID: c7fe625c8d41f648f89765abc40bb7b8fd4ed12a > CPU threads: 4; OS: Windows 6.19; UI render: default; > TinderBox: Win-x86@42, Branch:master, Time: 2017-07-16_02:04:02 > Locale: nl-NL (nl_NL); Calc: CL I still repro.. Version: 6.0.0.0.alpha0+ (x64) Build ID: 7a743b472dadb817eb7a6ed8063cee80ce7412e8 CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-07-18_01:01:15 Locale: fi-FI (fi_FI); Calc: group
(In reply to Buovjaga from comment #4) Strange quirk at my end. It did work fine with 2017-07-16_02:04:02, but it's back again.. Repro with: Version: 6.0.0.0.alpha0+ Build ID: a9588baca8137f51e2ca72e40b1f448b0e1885d1 CPU threads: 4; OS: Windows 6.19; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-07-21_02:58:26 Locale: nl-NL (nl_NL); Calc: CL
~/bibisect-win32-5.2 $ git bisect bad b8eab43d8f2d8d9cb24eba64d8dc6b8e6552e7c3 is the first bad commit commit b8eab43d8f2d8d9cb24eba64d8dc6b8e6552e7c3 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sat Apr 30 00:00:49 2016 -0700 source e4ae5e2d4049765f65f8b5560216f3ffded19903 source e4ae5e2d4049765f65f8b5560216f3ffded19903 :040000 040000 268cc4a8618b2053c7e72c7c1a7300fe581543d1 4a35da6b9913e463c517af649e15e7b0890747ba M instdir ~/bibisect-win32-5.2 $ git bisect log # bad: [86cb9d229718f48f9538032b80037238ea79e8a5] source 78223678b7513ffe46804cb08f2dc5bc899b2bab # good: [1f670510f08cb800cbae2a1dd6ea70d3542e4721] source 49c2b9808df8a6b197dec666dfc0cda6321a4306 git bisect start 'origin/master' 'oldest' # good: [3f9909c4c2ada7a3c705eba0e7ff39f96fb4dcae] source b08e200c3dfa964f257c8b7719ef9c801fb107d7 git bisect good 3f9909c4c2ada7a3c705eba0e7ff39f96fb4dcae # good: [0679445193ab11c32226f60d9143f84a50f019e4] source caf64a8c814bf821eef302fc6c2570c05b7fb169 git bisect good 0679445193ab11c32226f60d9143f84a50f019e4 # bad: [66f17835fc732b60cd5b8e9d7d83c7cb59f30c7c] source f1ea2290e66ac3cbb0d43e9e0727d421f29388eb git bisect bad 66f17835fc732b60cd5b8e9d7d83c7cb59f30c7c # bad: [c6ef653722ed09e0ff8a6879c95a9f4dec5d2c90] source 015fd55c94b7b650ed8e572cafaf3b0f903b01b9 git bisect bad c6ef653722ed09e0ff8a6879c95a9f4dec5d2c90 # bad: [f771ec6e1080a4a69d995195011fb635193e22a7] source 0fa225fe5b5558b68fd29f208b1fbb8b03b80951 git bisect bad f771ec6e1080a4a69d995195011fb635193e22a7 # good: [b78317941c9b020cd7de4c4901e91c13435d8246] source 7b1b9d42b03032f50edf3f088f7d06b98895d21d git bisect good b78317941c9b020cd7de4c4901e91c13435d8246 # bad: [2ede71d46473c24f075aacf41f1baeff03683947] source 2465cb26763b2ed8de65f35bce791fb55fe0e746 git bisect bad 2ede71d46473c24f075aacf41f1baeff03683947 # good: [c60d6c731a2f9811db01ee2dd58c5bd683620d3c] source 817c3b17fa57a7c4c4f80569bc00a21001fb6807 git bisect good c60d6c731a2f9811db01ee2dd58c5bd683620d3c # bad: [30c3c2c8b19c7d037a388f6d0126d9f5f60b7cec] source 212bb39bb663a68ac30e25572101b687e729409e git bisect bad 30c3c2c8b19c7d037a388f6d0126d9f5f60b7cec # good: [ad0bb69c96ce13cf9613207b5d43d80f1256677d] source cc5f8c6bf09c88859a317f822800e569670873f8 git bisect good ad0bb69c96ce13cf9613207b5d43d80f1256677d # bad: [23ada7a73c502a4bf87ea7622cc4079f76b0d055] source f710c017a666621c5b837de1f4624662f6a32e5a git bisect bad 23ada7a73c502a4bf87ea7622cc4079f76b0d055 # good: [54a907030d1e6674d227e3f7d6ba6b6041bd1024] source f5cd030ee0d15ae0519d68b8675773ce0b223a36 git bisect good 54a907030d1e6674d227e3f7d6ba6b6041bd1024 # bad: [b8eab43d8f2d8d9cb24eba64d8dc6b8e6552e7c3] source e4ae5e2d4049765f65f8b5560216f3ffded19903 git bisect bad b8eab43d8f2d8d9cb24eba64d8dc6b8e6552e7c3 # first bad commit: [b8eab43d8f2d8d9cb24eba64d8dc6b8e6552e7c3] source e4ae5e2d4049765f65f8b5560216f3ffded19903
author Maxim Monastirsky <momonasmon@gmail.com> 2016-04-25 07:30:16 (GMT) committer Maxim Monastirsky <momonasmon@gmail.com> 2016-04-27 19:20:22 (GMT) commit e4ae5e2d4049765f65f8b5560216f3ffded19903 (patch) tree d518565bf81bd862dba8961b4c850c2f318b4e35 parent f5cd030ee0d15ae0519d68b8675773ce0b223a36 (diff) SubToolBarController: Use initialize to change tb bits update is called so late that the dropdown addition is noticeable by the user.
This isn't really a regression, as I reproduce it all the way back to at least 3.6.7.2 (didn't test with prior versions). There was only a small range of 5.1.0 - 5.1.4 where this bug apparently didn't exist. And my revert to the pre-5.1.0 state was for a good reason, as otherwise the dropdown arrows of the shapes buttons were showing with a noticeable delay. That's even worse in a horizontal toolbar (like the drawing toolbar in Writer or Calc), where adding a dropdown part pushes the reset of the buttons to the right, and might even result in some of them being hidden (if there's no enough space).
Inherited
** 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
still repro in Version: 6.2.0.0.alpha0+ Build ID: d9ad59da50c1172fe98f94370221c9c1b688200a CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-10-08_23:34:44 Locale: ru-RU (ru_RU); Calc: threaded but delay is less than 1 sec
Dear Telesto, 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 Telesto, 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