Description: the copy function (and paste) Cntrl C or V are totally unreliable in the Libre Office installed with Ubuntu 20.04LTS .. It was fine in Ubuntu 18 LTS. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded Steps to Reproduce: 1. just try copying anything .. sometimes Copy works sometimes needs two or three attempts .. either using the bar copy function or the shortcut 2. 3. Actual Results: chaos .. critical bug rendering the whole application unsafe Expected Results: chaos .. critical bug rendering the whole application unsafe Reproducible: Always User Profile Reset: No Additional Info: copy and paste as normal
copy and pasting is such a common feature and being unreliable leads to all sorts of mistakes when it goes wrong. It renders the applications totally useless as you spend more time recopying / checking than you do actually working
Thanks for reporting this bug. According to bug 128803 this is likely a bug in the mutter package (part of GNOME) in Ubuntu 20.04, instead of a bug in LO. Please upgrade your mutter package to version 3.36.2 and see if that solves your problem.
There are many paste bugs already open. This one is probably duplicate, reporter should have searched before reporting. https://bugs.documentfoundation.org/show_bug.cgi?id=62196 https://bugs.documentfoundation.org/show_bug.cgi?id=116983 https://bugs.documentfoundation.org/show_bug.cgi?id=57147 https://bugs.documentfoundation.org/show_bug.cgi?id=90120 https://bugs.documentfoundation.org/show_bug.cgi?id=65606 https://bugs.documentfoundation.org/show_bug.cgi?id=99818 https://bugs.documentfoundation.org/show_bug.cgi?id=128803 Test ad advised and mark duplicate.
If this were a beta version I would agree I should have checked. This however was supposed to be 20.04 LTS .. a stable release. Sadly, its catastrophic .. from fundamental errors like cut and paste (I increasilngly think its more the OS than the application as it seems to lose content cross application ) to a humming sound (reported elsewhere but unhelpfully replied to) and then a load of minor look and feel issues .. over to the trivial with the sudoko pad upside down. A user in the LTS shouldn't have to be tracking down bugs that are so fundamental .. the kernel shouldn't have been released in the first place. Bug reports of this nature are the alpha testing team or beta testing team area. One of the beauties of Ubuntu was it wasn't the Microshaft approach of let the user find the problems ......... it seems developers have left Microshaft to destroy the competition...
[Automated Action] NeedInfo-To-Unconfirmed
By opening a new bug instead of search, you are just adding to problem,not a solution. Just see links and mark duplicate. Your report is unclear so I don't exactly which it is. Please no further discussion because it's no value.
No helpful comment so I assume this is a duplicate. *** This bug has been marked as a duplicate of bug 128714 ***
the other bugs mention Wayland or X11 ... neither of which I am running. I am running Ubuntu 20.04LTS and LibreOffice Version: 6.4.3.2 Build ID: 1:6.4.3-0ubuntu0.20.04.1 CPU threads: 4; OS: Linux 5.5; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded The concept of just randomly saying the bug is similar to another one and then closing it when there are significant differences seems flawed. At least only when the bug reporter has agreed otherwise users will turn away. The cut and paste error is .. CRITICAL to a general user .. otherwise that old cliche GIGO results. A computer is useful for as long as it can be relied upon. If it transpires this bug is an OS then that should be jointly dealt with rather than a glib comment saying "its a mutter problem" (I am running Ubuntu not mutter) and closing off a bug (that actually appears in JUST the Write program even now as at 25 May on a full patched (Livepatch) system. THE BUYG IS STILL HERE .. just to be totally clear!
Ironic.. .I've had to install mutter to update it .... to try and fix a bug. Not sure how a bug can exist in software that isnt installed in the first place.
This was never confirmed. It still can be a duplicate (which reporter didn't confirm searhed and tested) or NoutOurBug but Ubuntu bug.
It is totally unacceptable to expect a user to know how the OS and so on work. A bug which is believed by one team to be in another part of the system should be passed over to that area by the team to whom it is reported. Simply accusing the user of being a time waster is insulting in the extreme. Moreover, also expecting them to go out and learn how the whole system interacts and operates is also totally unrealistic. As I mentioned I had to install something to prove it didnt cause the bug, ergo it can't have been the same if that is what is being stated as causing the bug. All I know is that now as a user I feel shafted in the same way Microshaft got such a bad reputation in the 90s for treating the user base like sh!t. I switched to Ubuntu years ago but as a user not a coder (and I did not expect to have to learn so I can fix others coding errors). Now being treated like a fool makes me reconsider that decision... a shame as its popularity was growing and I know I used to expound the OS over others. As a lay user, I thought I was helping by reporting a bug and how it affected my use. It does not seem to match others but then I do not know how the system fits together .. I merely know what was a sound stable OS in 18.04 has turned into total utter chaos and garbage given you cant trust a key critical operation. The cavalier manner where the reporter is deemed to be at fault is not helpful.
Incidentally the problem still exists where I have to sometimes click ten times on the copy icon to pick up the data and even then it fails to get the right material. Sometimes I can paste it multiple times as I wish whilst other times the buffer is wiped clean after one paste. This is solely in Libre Office word. Moreover a search on Gnome for this error even now kicks back a null return GNOME page return .......... Projects Groups Snippets Help Search What are you searching for? Group Project Code 0 Issues 0 Merge requests 0 Milestones 0 Comments 0 Wiki 0 Commits 0 Users 0 We couldn't find any comments matching cut and paste fails
For this to be confirmed needed are reproducible steps and other people reporducing. I saw improvement in paste in Windows (I didn't see problem in Linux but some folks did). To know if it's true in this case, please install and test master from https://dev-builds.libreoffice.org/daily/master/current.html - it's separate to working LO.
Version: 6.4.3.2 Build ID: 1:6.4.3-0ubuntu0.20.04.1 updated to latest build but the problem still persists .. I select some text and can see that the paste icon is still greyed out click copy a few times and then you can see the paste icon comes alive ... clicking once may activate it or it may need multiple clicks . up to 10 so far
You need to test daily master 7.1+.
Using Cntl C and V works for the ten times I've tested it so far but clicking on the copy icon still needed two clicks to active the paste icon.... well done for this but I'll still wish to carry on testing the copy/paste keyboard function !! :))
Just checked the version to update this page and discovered despite upgrading using the "apt-get install LibreOffice" command I am still now only on libreoffice is already the newest version (1:6.4.3-0ubuntu0.20.04.1). so that didnt take me to 7.1 so going to download the package and try that way. Please disregard my last comment
well .. I've installed 7.1 daily build e.g Setting up libreofficedev7.1-writer (7.1.0.0.alpha0-1) ... Now I try the find function to find the test I need to cut and paste and the fimd function finds it if I hit enter .. but neither of the up or down arrows to move to the next instance work. Check the about box and it still saying that is is Version: 6.4.3.2 Build ID: 1:6.4.3-0ubuntu0.20.04.1 CPU threads: 4; OS: Linux 5.5; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US this is getting from bad to worse ..........
Version: 7.1.0.0.alpha0+ Build ID: a3c8ea5e644ca2fc04de9f01ba9f8ace47f520f0 CPU threads: 4; OS: Linux 5.5; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-06-17_02:21:20 Calc: threaded sadly it is still happening
(In reply to alignedtraining from comment #8) > the other bugs mention Wayland or X11 ... neither of which I am running. I > am running Ubuntu 20.04LTS and You are certainly running a session either with X11 or Wayland. To find out which, open a terminal and run this: echo $XDG_SESSION_TYPE
alignedtraining: I understand that you are angry and dispointed, but could you please summarize your steps to reliably reproduce this issue? Many of us are using Ubuntu or Fedora or openSuse linux desktops, and thus bug, if it is really easy to reproduce, can not be existing for such a long time without being reproduced by others. So, would you please: 1. Reset your libreoffice user profile. It's located in your home folder in a hidden directory named ".config/libreoffice" (for a normal release build) or ".config/libreofficedev" (for a development build like alpha or master). Just rename it, do not delete, so that you csn restore it after the test. 2. Upgrade your ubuntu with sudo apt-get upgrade, download the most recent libreoffice, uninstall the old one, install thevnew one, run it. 3. Try to reproduce the bug, and do notice the simpliest steps to reproduce. 4. Put a comment here clearly explain the steps to reproduce. for example: 1) I open Calc; 2) I then typed in a cell the string "abc"; 3) I then select this cell, pressed Ctrl+C, and then used Ctrl+v to another cell in the same sheet (or another sheet? or another calc file? or or Writer? or some other applications? if another sheet, then is it created before this step, or after you have pressed any keys?...) 4) ... 5) explain what you see, and what you expect. 6) Copy past the lo version information and your OS information. It is important to show the steps in 1,2,3... list order so that other can follow one by one. This way it possible to find a solution quickly.
And if you are copying from another application into libreoffice, you should also mention itvin your steps clearly. Also check whether you are using any cliboard management software.
Dear alignedtraining, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear alignedtraining, 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 MassPing-NeedInfo-FollowUp