[Libreoffice-bugs] [Bug 156290] In Calc/Win11, copying any cell hangs with 100% CPU (not corrupt user profile)

2023-09-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156290 Buovjaga changed: What|Removed |Added Resolution|--- |DUPLICATE CC|

[Libreoffice-bugs] [Bug 156290] In Calc/Win11, copying any cell hangs with 100% CPU (not corrupt user profile)

2023-08-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156290 --- Comment #3 from ericbressle...@gmail.com --- Using the command prompt with this command as suggested by Barry Kramer did prevent the hanging from using Copy and Cut on my system. "C:\Program Files\LibreOffice\program\scalc.exe" The

[Libreoffice-bugs] [Bug 156290] In Calc/Win11, copying any cell hangs with 100% CPU (not corrupt user profile)

2023-08-12 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156290 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this

[Libreoffice-bugs] [Bug 156290] In Calc/Win11, copying any cell hangs with 100% CPU (not corrupt user profile)

2023-08-09 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156290 --- Comment #2 from ysui2...@gmail.com --- can't reproduce with Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan;

[Libreoffice-bugs] [Bug 156290] In Calc/Win11, copying any cell hangs with 100% CPU (not corrupt user profile)

2023-08-02 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156290 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You

[Libreoffice-bugs] [Bug 156290] In Calc/Win11, copying any cell hangs with 100% CPU (not corrupt user profile)

2023-07-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156290 --- Comment #1 from Barry L. Kramer --- Not sure, but this could be a duplicate of Bug 153131 but on a different system and OS. The problem looks similar, but I didn't see it when I first did the search for this problem existing already.