Download it now!
Bug 116050 - In multimonitor set up calc only works in primary display
Summary: In multimonitor set up calc only works in primary display
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: VCL-OpenGL Multimonitor
  Show dependency treegraph
Reported: 2018-02-27 04:26 UTC by c
Modified: 2019-06-08 02:58 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description c 2018-02-27 04:26:29 UTC
When calc is moved to secondary displays the window is either all white or unresponsive to user input. Moving window back to primary display resolves the issue

Steps to Reproduce:
1. Open Calc
2. Move Calc to secondary display

Actual Results:  
Window doesn't respond to input.

Expected Results:
Window responds to input

Reproducible: Always

User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no

Version: (x64)
Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
Locale: en-US (en_US); Calc: group

User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Comment 1 raal 2018-02-28 22:24:44 UTC
I'm using Calc on two monitors without problem. win7,LO 6.0.1. Try to disable openGL. Menu/Tools/LibreOffice/View
Comment 2 c 2018-02-28 23:06:12 UTC
Disabling OpenGL via Tools->options->LibreOffice->View resolved the issue.
Comment 3 raal 2018-03-01 10:51:02 UTC
(In reply to c from comment #2)
> Disabling OpenGL via Tools->options->LibreOffice->View resolved the issue.

Please could you provide your computer's OpenGL information?
Comment 4 c 2018-03-01 19:55:00 UTC
Renderer: Intel(R) HD Graphics 530
Vendor: Intel
Memory: 1024 MB
Version: 4.4.0 - Build
Shading language version: 4.40 - Build
Comment 5 Zineta 2018-10-03 12:24:48 UTC
I tested it in Win 10 Pro (x64), when Calc is moved to secondary display it respons to input and no such problem detected, no matter if OpenGL disabled or enabled.
Comment 6 Zineta 2018-10-03 13:20:17 UTC
...also in master

Version: (x64)
Build ID: 48cfa0b00b22f11ade53aec79b2fdddad253e1bd
CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win;
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-03_02:01:42
Locale: en-US (en_US); Calc: CL

Intel HD Graphics 4600
Comment 7 Timur 2018-10-03 14:44:49 UTC
Since testers couldn't reproduce, I set back to Needinfo for the Reporter to:
- test with LO Still 6.0.6 or Fresh 6.1.2.
- test with daily master from that will not interfere with regular installation 
- write monitors resolution, to confirm whether monitors are HiDPI
- test with other driver versions.
Comment 8 QA Administrators 2019-05-08 17:31:26 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2019-06-08 02:58:29 UTC
Dear c,

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