Description: LibO will access share\config\images_tango.zip for every cell when typing something into it (and the registrymodifications.xcu will be updated regularly) Steps to Reproduce: 1. Open A new 2. Use Process Monitor with Filter set ProcessName soffice.bin (https://docs.microsoft.com/en-us/sysinternals/downloads/procmon) 3. Type something like 'b' into cell A1 4. Press Down key or Enter 5. Type 'b' again 6. Repeat 3-5 7. Notice that LibO will keep reading: images_tango.zip Actual Results: Libo keeps accessing images_tango.zip Expected Results: Shouldn't happen Reproducible: Always User Profile Reset: No Additional Info: Found in: Version: 6.0.0.0.alpha0+ Build ID: 4020945651b4f3c636980e2103db440b5c55459c CPU threads: 4; OS: Windows 6.29; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-09-25_23:14:03 Locale: nl-NL (nl_NL); Calc: CL User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
~/bibisect-win32-5.0 $ git bisect good 547eeb4987de4a59a9d7c0946e0cbb5c0b511f94 is the first bad commit commit 547eeb4987de4a59a9d7c0946e0cbb5c0b511f94 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sun May 3 11:17:52 2015 -0500 source 583e9d834dd795e18e4f8245fc2fe45736607ef9 source 583e9d834dd795e18e4f8245fc2fe45736607ef9 :040000 040000 befc2a79dcd556cec5845589ebc9f0fbd4342ccb e395551d70383b702255db370311e977cdc1f992 M instdir ~/bibisect-win32-5.0 $ git bisect log # bad: [b7988d11e5d3751a4b366b2bfc9048f7a30e8526] source 87ac0b1e75a880a68ecb748bd4b34ae5a3d2ae98 # good: [f449493ae11ac76cc7396bddeaa624a60c565936] source 57d6b92b69a31260dea0d84fcd1fc5866ada7adb git bisect start 'origin/master' 'oldest' # bad: [66e2ae767eb4bb83444e3d03bcb90adcbe6d4991] source 5a308b1239a09417507b0d05090ff2d3418d5133 git bisect bad 66e2ae767eb4bb83444e3d03bcb90adcbe6d4991 # bad: [90c1dbb098a6d957f2293692716251ee5a6053ca] source 2813632238380e0bfe40c0e6404a07102cde1398 git bisect bad 90c1dbb098a6d957f2293692716251ee5a6053ca # bad: [5b8e174eb7b3d996d6c90862d7228e1b928a9787] source 4de09a9efdb62cf90ce18662852e556cf7148e14 git bisect bad 5b8e174eb7b3d996d6c90862d7228e1b928a9787 # bad: [175f015ea35c89712f927eaef03b6a77895fc1a9] source b46f781440130e6a629bf9ae14a62310d2a31021 git bisect bad 175f015ea35c89712f927eaef03b6a77895fc1a9 # bad: [b8cd2bb2104ad294e312019417ae140fdb87766e] source fdba97bb3940b2763167510fab91df4b33293115 git bisect bad b8cd2bb2104ad294e312019417ae140fdb87766e # good: [f0242df5af685c9704ec1082e83405b7a730ff2b] source af90d610e3c09c32b15beee2d42d86a4dd6aac4d git bisect good f0242df5af685c9704ec1082e83405b7a730ff2b # bad: [60dddf0d33af8ff464309da0c742f59014a59c43] source 27d75e7983f21e72ab4c2aff7f181bf21d8f5ed3 git bisect bad 60dddf0d33af8ff464309da0c742f59014a59c43 # bad: [a7ef69cbf73953a17e26449f351ebc954b23a6fd] source b6bdc6771199b7b05d4f9840b66ebce3bb61d7db git bisect bad a7ef69cbf73953a17e26449f351ebc954b23a6fd # bad: [4bad90893bcefbf1c8cac8f9bb5d8fbbf92fe6ad] source 360b988ea01d2b8dec0a15fab7d92df515e213c2 git bisect bad 4bad90893bcefbf1c8cac8f9bb5d8fbbf92fe6ad # bad: [f1e8d7643f4d509eafdf86116d2b3fb883cf2f9c] source 3181a7a10f79fd065af88e32c402874878715684 git bisect bad f1e8d7643f4d509eafdf86116d2b3fb883cf2f9c # good: [d17d8f7859e2eca34f44f0cf17d0c0eb59b5312b] source 1dbaaa73fe3528de36f19142a2950ec0661aa0e7 git bisect good d17d8f7859e2eca34f44f0cf17d0c0eb59b5312b # bad: [547eeb4987de4a59a9d7c0946e0cbb5c0b511f94] source 583e9d834dd795e18e4f8245fc2fe45736607ef9 git bisect bad 547eeb4987de4a59a9d7c0946e0cbb5c0b511f94 # good: [558ac16ef91985bac96df69af886b4e4f888b553] source 4e8df25adcc930657eb35cdc527bf8d751fc72e7 git bisect good 558ac16ef91985bac96df69af886b4e4f888b553 # first bad commit: [547eeb4987de4a59a9d7c0946e0cbb5c0b511f94] source 583e9d834dd795e18e4f8245fc2fe45736607ef9
Repro. The blamed commit is https://cgit.freedesktop.org/libreoffice/core/commit/?id=583e9d834dd795e18e4f8245fc2fe45736607ef9 "Present the (collapsed) sidebar also in Calc and Draw" Could the sidebar really be the culprit? Version: 6.0.0.0.alpha1+ (x64) Build ID: 7e03c4eed72452fdfb87341214a21956c08ba969 CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-10-26_00:58:29 Locale: fi-FI (fi_FI); Calc: group
(In reply to Buovjaga from comment #2) > Repro. > > The blamed commit is > https://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=583e9d834dd795e18e4f8245fc2fe45736607ef9 > "Present the (collapsed) sidebar also in Calc and Draw" > > Could the sidebar really be the culprit? > > Version: 6.0.0.0.alpha1+ (x64) > Build ID: 7e03c4eed72452fdfb87341214a21956c08ba969 > CPU threads: 4; OS: Windows 10.0; UI render: default; > TinderBox: Win-x86_64@42, Branch:master, Time: 2017-10-26_00:58:29 > Locale: fi-FI (fi_FI); Calc: group Indeed, I found it strange to. But I'm noticing now that the toolbar flickers a bit, when pressing enter, after typing something it cell. So it could be a refresh of the toolbar. Now I'm looking at it, is quite plausible when looking at the stack: 48 Flush 42 makesidebartoolbox 42 sfxlo.dll makeSidebarToolBox + 0x1346 43 sfxlo.dll makeSidebarToolBox + 0x1128 44 sfxlo.dll SfxShell::BroadcastContextForActivation + 0x47 45 sfxlo.dll SfxShell::Activate + 0x11 46 sfxlo.dll SfxShell::DoActivate_Impl + 0x238 47 sfxlo.dll SfxDispatcher::FlushImpl + 0x66d 48 sfxlo.dll SfxDispatcher::Flush + 0x22 49 sfxlo.dll SfxViewShell::AddSubShell + 0x5d 50 sclo.dll ScTabViewShell::SetCurSubShell + 0x244 51 sclo.dll ScTabViewShell::SetEditShell + 0xd3 52 sclo.dll ScTabViewShell::StopEditShell + 0x2d 53 sclo.dll ScTabViewShell::Notify + 0x82b 54 svllo.dll SfxBroadcaster::Broadcast + 0x6e
** 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
Repro with Version: 6.3.0.0.alpha0+ Build ID: 0b21f6556b6fff76290d1095089da89532365215 CPU threads: 4; OS: Windows 6.3; UI render: GL; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
The share\config\images_tango.zip issue is gone. The registrymodifications.xcu update appears to be much older Also found in: LibreOffice 3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b but not in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
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