Bug 127828 - Shaking Buttons (with and without Macros)
Summary: Shaking Buttons (with and without Macros)
Status: RESOLVED DUPLICATE of bug 121963
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-27 16:01 UTC by office
Modified: 2019-09-27 17:58 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
The Video shows the Buttons "shaking" (4.81 MB, video/mp4)
2019-09-27 16:01 UTC, office
Details

Note You need to log in before you can comment on or make changes to this bug.
Description office 2019-09-27 16:01:37 UTC
Created attachment 154600 [details]
The Video shows the Buttons "shaking"

Hello,

I've got a strange behavior with LO 6.3
In LO 6.2 there is no such problem.

My buttons (German: Steuerelement-Schaltfläche) are shaking and CPU load is going to 90% on one core.

If I want to execute a macro with that button, I've to click on the button and then enter Draft-Mode, so that the shaking ends and the macro runs.

I've tried several things to avoid this:
turning opengl, hardwareacc off doesn't help.
Removing the underlying macros does not help (so the macro itself can't be the reason), buttons still shaking on click.
Trying to change the executing action to "onmouseclick" or "onmouseclickend" (sorry for bad english expressions) doesn't help.

Even on an portable version it's the same with 6.3.X and works on 6.2.X.

I've discussed this in a german forum also (https://www.libreoffice-forum.de/viewtopic.php?f=6&t=24187) but of course without solutions, that's why I write here.

I am reverting back to 6.2.7 and the problem is gone, but it would be nice to resolve the problem so I can use the newest version soon.

My Hardware: DELL XPS 13 wit Windows 10 1903 (latest Updates installed)

Thanks in advance!
Comment 1 Xisco Faulí 2019-09-27 17:58:17 UTC
Thanks for reporting this issue.
This is a duplicate of bug 121963

*** This bug has been marked as a duplicate of bug 121963 ***