Bug 133449 - VIEWING: openCL is not used even after confirm and restart
Summary: VIEWING: openCL is not used even after confirm and restart
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
6.4.3.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: possibleRegression
Depends on:
Blocks: OpenCL
  Show dependency treegraph
 
Reported: 2020-05-27 15:52 UTC by libre officer
Modified: 2024-10-02 03:17 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
openCL is not used. (18.36 KB, image/png)
2020-05-27 15:52 UTC, libre officer
Details
expected after LO restart (12.98 KB, image/png)
2020-05-27 15:54 UTC, libre officer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description libre officer 2020-05-27 15:52:35 UTC
Created attachment 161341 [details]
openCL is not used.

Description:
When I try to allow use of OpenCL, LO then asks to restart, after confirmation and restart, going again to OpenCL menu, I see that the "allow use of OpenCL" is not checked anymore and it say below it that "OpenCL is not used."

Steps to Reproduce:
1. Tools -> Options -> OpenCL.
2. Check "allow use of OpenCL" -> OK.
3. Click "Restart now", and wait for LO restart.
4. Tools -> Options -> OpenCL.

Actual Results:
* "allow use of OpenCL" not checked.
* "OpenCL is not used"

Expected Results:
* "allow use of OpenCL" checked.
* "OpenCL is available for use."


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 6.4.3.2 (x64)
Build ID: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8
CPU threads: 4; OS: Windows 10.0 Build 17763; UI render: default; VCL: win; 
Locale: fr-CH (fr_FR); UI-Language: en-US
Calc: threaded
______

Version: 7.0.0.0.alpha1 (x64)
Build ID: 6a03b2a54143a9bc0c6d4c7f1...
CPU threads: 4; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win; 
Locale: fr-FR (fr_FR); UI: en-GB
Calc: threaded


This bug is not present in LibreOffice 6.4.1.2 (x86), thus maybe it's a regression.
Comment 1 libre officer 2020-05-27 15:54:32 UTC
Created attachment 161342 [details]
expected after LO restart

working for LO 6.4.1.2 (x86)
Comment 2 QA Administrators 2022-05-28 03:34:15 UTC Comment hidden (obsolete)
Comment 3 Stéphane Guillou (stragu) 2024-03-04 00:21:58 UTC
(Please don't mark as "new" if you reported the bug, unless you bibisected it)

I reproduce in:

Version: 24.2.0.3 (X86_64) / LibreOffice Community
Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1
CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

However, what happens is that LO tests if OpenCL can be used, and turns the option off automatically if that's not the case. (See bug 106162)

But in you case, it could be a hardware-specific regression, and if you still experience the issue in a recent version, it would be very helpful if you could bibisect the issue with the 6.4 repository: https://bibisect.libreoffice.org/
Or it might be related to x86 vs x64.

Setting to "needinfo", please let us know if it still a problem, and if you'd like help bibisecting.
Comment 4 QA Administrators 2024-09-01 03:16:08 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2024-10-02 03:17:16 UTC
Dear libre officer,

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