User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0
Build Identifier: LibreOffice 188.8.131.52
On a dual-monitor setup, editing a connector seems to be a finite chance of putting the global display manager into a weird state so that:
- the cursor is updated like it's supposed to
- the rest of the display is not updated until I click on the other monitor, but then it's accurate according to what I did blindly
The problem then persists for all apps, not just LibreOffice.
Logging out and back in always fixes it.
Only connectors seem to have this problem: editing other objects appears to be completely safe, even if moving something that has a connector attached to it. Just as long as the connector is not directly being edited.
Steps to Reproduce:
1. Open a Drawing that has some objects and attached connectors.
2. Edit those connectors by copy/pasting or moving their endpoints and routing.
3. Continue playing with connectors until the display stops updating.
4. Do something in an unrelated app on a different monitor.
5. LibreOffice display suddenly updates on focus loss, but the unrelated app appears frozen.
6. Click away from unrelated app's monitor.
7. Unrelated app now updates its display.
8. Log off and back on.
9. Repeat from #1 as needed for diagnostics.
See Steps to Reproduce
See Steps to Reproduce
[Information automatically included from LibreOffice]
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Reset User Profile?No
It seems to have something to do with glue points too. The display froze as soon as I selected the option to add one to an object. This is before actually adding it or moving a connector to it.
As usual, I could add it blindly and move the connector to it with occasional clicks to the other monitor to explicitly refresh the display and check my work.
What desktop environment do you run? In case of KDE please update to 5.7.2, I read positive feedback regarding multiscreen... Ignore this, you are on LightDM.
As you say the issue happens not only for Libreoffice. So it seems to be NOTOURBUG. Or am I wrong?
It only starts when editing connectors or creating/editing gluepoints in LibreOffice. That's why I think it's caused by LibreOffice. Once it starts, it affects everything else.
I guess this issue will be hard to track down because multi-screen problems are often related to the hardware and to the very specific setup. For instance, Intel drivers are known to be much more buggy than Nvidia, and at some point I had to move my notebook from left-of to right-of the external display in order to cope with bugs when the lid is closed. And last but not least you are running a not so common desktop environment. I never experienced an issue like yours on KDE, LXQt or Windows.
So are you able to check against other desktop environments?
My Windows 10 host machine seems to be okay. It's a Dell laptop with both Intel (low power) and Nvidia (high performance) graphics.
The problem is in a fully-updated Lubuntu 16.04 LTS VirtualBox guest with the default display manager and a USB touchscreen mapped to its non-default monitor. I'm not using the touch to produce the problem, but it is present and working. Unmapping the touchscreen does not fix it.
I can't test anything else right now.
Before installing any software users need to do research about it like its developers and its functionalities. If it appears suspicious then simply do not install it. For email related issues and queries, visit https://www.aoltechsupportnumber.com/blog/how-to-close-a-free-aol-account/
Very Nice article, Thanks For Sharing
Aaron: can you try with Lubuntu 20.04: https://lubuntu.me/downloads/ ?
Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
It took me a while to get back to this. I hadn't used that virtual machine for years, as its purpose was done, but for some reason I kept it around. I fully updated it, and I can't reproduce the problem anymore.
I also tried a new virtual machine with a fresh install of Lubuntu 16.04.3 and then 20.04, and I can't reproduce it there either.
So I guess we can call it fixed by accident?