Description: I have a problem At Base in ver 7.1.22 LibreOffice jp version on win10. I cannot execute sql command in 'Tool-SQL' window. 'SQL command' and 'execute command' window is non reaction. I tried to typing,Copy and paste and etc, but that window done no indication. Thank you. Steps to Reproduce: 1.Click 'Tool' menu and click 'SQL(F)...'. 2.Type orr copy and paste sql commands in 'Execute command' window. 3. Actual Results: No typing or No copy and paste! Nothing is displayed. Expected Results: It's display Typing or copy and paste sql commands. Reproducible: Always User Profile Reset: Yes Additional Info: Non
Tested with LO 7.1.2.2 on OpenSUSE 15.2 64bit rpm Linux. Typed in Tools → SQL → Command to execute SELECT * FROM "Table" Switched «Show output of "select" statements» to 'yes' and pressed «Execute». No problem appears here under Linux. Could be it is a special Windows bug.
No repro either for me with LO7122 macOS BigSur
I can't reproduce it in Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: d4f116d9576453f5974eb63db37a33c59ac53bc9 CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded nor in Version: 7.1.2.2 (x86) / LibreOffice Community Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4 CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: threaded Could you please try to reproduce it with version 7.1.3.2 of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
I have also same problem in both version Version: 7.1.4.2 (x64) / LibreOffice Community Build ID: a529a4fab45b75fefc5b6226684193eb000654f6 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: threaded and Version: 7.1.3.2 (x64) / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: threaded. Why? Thak you.
Could you upgrade to 7.1.5 and give a try at https://wiki.documentfoundation.org/QA/FirstSteps ? If you still reproduce the hang, could you try to retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace)
7.2.5 has been released meanwhile, if you can give it a try with a brand new LO profile (see my previous comment).
Dear kei, 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 kei, 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
Resolved! HI Everyone. I am happy to report that the problem has been resolved. It was caused by a mismatch with win10 settings. I have weak eyesight, so that, I set it to 200% in win10 settings 'Easy operation' -> 'Display' -> 'Enlarge characters'. Furthermore, 'Display' -> 'Enlarge the whole' was set to 120%. For this reason, when I open the 'Tools'->'SQL'->'Execute SQL statement' window of Base, the 'execution command' column etc. were not displayed normally. This prevented me from entering SQL commands. By changing 'Display' -> 'Enlarge the whole' to 100% (recommended), I'm now able to successfully display the 'Execute SQL statement' window and execute the SQL command. Thanks QA Administrators,Julien Nabet and everyone.
Thank you for the feedback, let's put this one to WFM then.