Description: Following the discussion initiated on the ESC meeting from today (2020-07-16), in the past there has been multiple questions and reports about clipboard sometimes not working due to some weird Windows 10 version bugs or when a dedicated anti-malware solution has been installed. e.g. tdf#129987 If such a clipboard problem arises and the QA team is asking the end users to report the build info he has, we might face a chicken egg problem. This 'bug' report aims at keeping track of this use case. Steps to Reproduce: N/A Actual Results: May not have the ability to have build info if these are ony accessible from the clipboard and the latter is not working for some reason. Expected Results: Have a way to have build info always reachable. Reproducible: Always User Profile Reset: No Additional Info: N/A
What is the proposal then? To be able to save build info to a file? I guess taking a screenshot would go a long way as an emergency measure. I have not so far seen any issues with copying the build info. Bug 129987 does not mention any inability to do so.
(In reply to Buovjaga from comment #1) > What is the proposal then? To be able to save build info to a file? I guess > taking a screenshot would go a long way as an emergency measure. I have not > so far seen any issues with copying the build info. Bug 129987 does not > mention any inability to do so. Setting to NEEDINFO
Dear William Gathoye, 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 William Gathoye, 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