Created attachment 124175 [details] OLE open OOo vs LO I try to insert OLE object... Further object... From file... File open dialogue erratically displays folder as empty folder. Also Impress may stuck or crash. Example contains screenshot OOo vs LO This work correctly in LO 4.4.7 but not work in 5.1.1
I can not confirm with 5.1.1.3, win7
Created attachment 124177 [details] Shot from Win7 Attached shot from Win7 and LO 5.1.1.3 Left dialogue = LO Impress Right = Windows Explorer
Created attachment 124178 [details] Win 8.1 LO 5.1.2.2 Just now installed update to LO 5.1.2.2 No difference
Hello, please test it with local disk. I see this problem on network disk, but it works for me on local disk (C:)
Shot from Win 8.1 shows my local disk.
Created attachment 124183 [details] Screen video "program" folder is empty? really?
This seems to have begun at the below commit. Adding Cc: to Michael Meeks; Could you possibly take a look at this one? Thanks 11823b0c00e287297206b62c30887683318664ec is the first bad commit commit 11823b0c00e287297206b62c30887683318664ec Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Tue Nov 24 19:28:29 2015 -0800 source d3cdd7efca82130c2c42e3062b5ab244461ce15c source d3cdd7efca82130c2c42e3062b5ab244461ce15c author Michael Meeks <michael.meeks@collabora.com> 2015-11-24 10:19:11 (GMT) committer Michael Meeks <michael.meeks@collabora.com> 2015-11-24 12:57:22 (GMT) commit d3cdd7efca82130c2c42e3062b5ab244461ce15c (patch) tree 340bd40fd80f4fcf5c446ec4c270e2a9a9c2e211 parent 5a08d3fa47cfcfe89ccefd5023c95f6b3775ab4f (diff) vcl: scheduler - split timeout calculation from idle invocation. I can reproduce on network drive, looks like some problem with delays.
Wow - that is the system file dialog that is not working well (?) that is quite amazing. I wonder if it is the update stack piece: - // Update timeout only when not in timer handler and - // only if smaller timeout, to avoid skipping. - if (bForce || (!pSVData->mnUpdateStack && - nMS < pSVData->mnTimerPeriod)) Hmm - this is indeed odd. I can't reproduce this using my -5-1 branch build - even with a remote windows share (though it is quite a fast one, and quite nearby on the network to me ). Hmm - any idea how I can get a slow windows network share to connect to ? I tried OneDrive - but I suspect it of being cached locally =) Thanks !
this problem not have dependence from network. in most cases this problem appear in local environment
In 5.2.2.2 (Win) a see no changes. :-(
Hi Andrew; thanks for testing - any chance you can get a dbgutil build - and generate a console output log with: SAL_LOG=+INFO.vcl.schedule+WARN.vcl.schedule set in the environment ? prolly necessary to launch from eg. a cygwin shell to get that. This should show us what the scheduler is doing - which is what the patch changes. Ultimately, I can't find a way to reproduce this locally - unfortunately.
Hi, got the same bug on Windows 76 x64 with v 5.2.2.3 x64 and 5.3.0.3 x64 I'll try to follow above instructions to get additional info. Regards, Eric Ficheux
Question: is there a simpler way to generate a trace? Regards, Eric Ficheux
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 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-20170830
Dear Bug Submitter, 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-20170929