New spreadsheet; enter simple text data in cells A1, A2, A3; Ctrl-C column A; Ctrl-V on column B results in soffice.bin running at 100% for a long time, with screen frozen. i.e. I am copying column A with only 3 text values in it to column B and I get the freezing behaviour. When there are bugs like this in the software it makes it unusable, because you never know if the next key press is going to lock the program and you lose all your work. It reminds me of Excel V6 back in the early 90's.
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
After resetting the user profile the problem is still there
Hello, This is very strange indeed. Is OpenCL enabled ( Tools - Options - OpenCL ) ? if so, What happens if you disable it ?
Hi, In Tools - Options - OpenCL there were two options: 1) Allow use of Software Interpreter (even when OpenCL is not available) 2) Allow use of OpenCL I unchecked the first [Allow use of Software Interpreter (even when OpenCL is not available)] and the problem went away. I tried checking the second either with or without the first one checked, and it seemed to accept it, but when I restarted Libreoffice the second was always unchecked i.e. it didn't save it over a restart - and of course it doesn't take effect unless you restart. What does unchecking the first option do (apart from apparently fixing my problem)? Thanks for your help.
(In reply to ads from comment #4) > Hi, > > In Tools - Options - OpenCL there were two options: > > 1) Allow use of Software Interpreter (even when OpenCL is not available) > 2) Allow use of OpenCL > > I unchecked the first [Allow use of Software Interpreter (even when OpenCL > is not available)] and the problem went away. > > I tried checking the second either with or without the first one checked, > and it seemed to accept it, but when I restarted Libreoffice the second was > always unchecked i.e. it didn't save it over a restart - and of course it > doesn't take effect unless you restart. > > What does unchecking the first option do (apart from apparently fixing my > problem)? > > Thanks for your help. OpenCL uses your graphics card's processing abilities for calculations. Software interpreter thus uses CPU.
(In reply to ads from comment #4) > [...] > What does unchecking the first option do (apart from apparently fixing my > problem)? Calc don't use the new formula interpreter needed by OpenCL implementation. For the second option, I think that that means that Calc made tests to check if OpenCL driver works well and found that it does not work well and must be not used for Calc. See Hardware Acceleration in https://people.gnome.org/~michael/blog/2017-02-01-under-the-hood-5-3.html Best regards. JBF
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Hi, I just tried to recreate with my current version of libreoffice which is Version: 5.3.7.2.0+ Build ID: 5.3.7-5 CPU Threads: 4; OS Version: Linux 4.13; UI Render: default; VCL: gtk2; Layout Engine: new; Locale: en-GB (en_GB.UTF-8); Calc: single Copy and paste columns now works as expected, whether or not I allow use of OpenCL. Is there any point downloading the fresh version?
(In reply to ads from comment #8) > Hi, I just tried to recreate with my current version of libreoffice which is > > Version: 5.3.7.2.0+ > Build ID: 5.3.7-5 > CPU Threads: 4; OS Version: Linux 4.13; UI Render: default; VCL: gtk2; > Layout Engine: new; > Locale: en-GB (en_GB.UTF-8); Calc: single > > Copy and paste columns now works as expected, whether or not I allow use of > OpenCL. > Is there any point downloading the fresh version? It's ok to test it with 5.3.7.2 as well. Thanks for retesting. Closing as RESOLVED WORKSFORME