Description: Lately on Linux (under an X11 session particularly), it would appear that text copied from a cell in Calc is sometimes stored in the clipboard as a bitmap. Steps to Reproduce: 1. Open Calc. 2. Type "hello" into a cell. 3. Select the cell. 4. Press Ctrl+C / Ctrl+V over and over. Actual Results: Eventually, instead of text, an image containing "hello" will be pasted. Expected Results: The text should be copied and pasted as text always. Reproducible: Always User Profile Reset: No Additional Info:
It's useful to know that a recent update to mutter is at least partly to blame for this, as I cannot reproduce the issue on versions older than 3.34. Mutter 3.34 introduced a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34-Clipboard-Manager However, LibreOffice does seem to be doing something strange in its type requests from the clipboard (stand by for a comment from a colleague with more mutter knowledge), so I suspect there may be fault on both ends here.
Can confirm this suspected 'mutter' bad effect on calc 6.3.3 and mutter 3.34.1: -happen with a calc spreadsheet when trying to copy/paste a formula cell: 1) from a column's cell, right click to copy it 2) select the first same column's cell to paste: get a graphic created (kind of image with 4 cells which are draggable and extendable) instead of the normal pasting result. 3) deleting that graphic objet, then re-copying the original cell, finally the pasting is done as expected. This has been seen for each copy/paste since calc 6.3.3 upgrade, not prior. Also note that now LO is unable to load/open an ods file : after the Nov 11th upgrades; Does not get error from a terminal. Only get a dialog box telling calc has silently crashed and will then try to recover the ods file: but there is no file listed to recover. Indeed that ods file load/open as usual with version prior to Focal.
Note that when copy/paste is failing, some more icons are automatically added into the top taskbar, and then are removed when the graphic objet is deleted
*** Bug 129319 has been marked as a duplicate of this bug. ***
*** Bug 129626 has been marked as a duplicate of this bug. ***
Note that a selection's content is not stored in the clipboard (unless LibreOffice is exited) but upon pasting the target asks for the available formats and picks the best offered, that in this case should be the internal Calc format, which then would be transferred from source to target, but somehow here instead it gets a bitmap/image from the clipboard "manager" (apparently). (In reply to Marcus Tomlinson from comment #1) > However, LibreOffice does seem to be doing something strange in its type > requests from the clipboard (stand by for a comment from a colleague with > more mutter knowledge), so I suspect there may be fault on both ends here. So what would that "doing something strange" be?
Reportedly, if the Clipboard Indicator GNOME Shell Extension was installed, removing that cured the symptom.
The corresponding Mutter bug is https://gitlab.gnome.org/GNOME/mutter/issues/919
This bug is marked All and reproduced also on Windows.
Please note, I filed this but with a complaint about my system shutting down, and also not auto-saving. https://bugs.documentfoundation.org/show_bug.cgi?id=65509 As noted in that discussion, yesterday when I got the .bmp, LibreOffice shut down quickly thereafter. It may be that the bug causing the .bmp is also crashing the system. Don't know where/if the auto-save fits in.
Now that this bug is confirmed what next? Its is really annoying and making me consider other desktop environments other than GNOME.
Workaround: login to a Wayland session instead of X11 (or maybe X-Wayland?) session.
*** Bug 130816 has been marked as a duplicate of this bug. ***
I've found: 1. The initial CTRL-C works fine. 2. Subsequent attempts are OK if one presses CTRL-C twice on the source cell which seems to function as a workaround.
I am having the same problem. My work-around was to install XFCE from the Ubuntu repository. As soon as I logged into an XFCE session instead of a GNOME session the problem disappeared completely. I think the people who support mutter have this as a high severity bug.
*** Bug 130880 has been marked as a duplicate of this bug. ***
*** Bug 131631 has been marked as a duplicate of this bug. ***
(In reply to Timur from comment #9) > This bug is marked All and reproduced also on Windows. Shall we open a separate bug for Windows?
Does it even occur on Windows? If so, that would be a different cause (though highly likely some clipboard destroyer (AKA "manager") involved then as well). I'm marking this as not-All., i.e. Linux.
(In reply to Eike Rathke from comment #19) > Does it even occur on Windows? If so, that would be a different cause > (though highly likely some clipboard destroyer (AKA "manager") involved then > as well). > I'm marking this as not-All., i.e. Linux. It seems to happen occasionally with my web browsers and Text Editor, but very rarely so I can't be sure it's not tied up with LibreOffice. (Using Ubuntu 19.10.)
(In reply to Eike Rathke from comment #19) > Does it even occur on Windows? I see now that all reports are Linux. I wrote that I reproduced once also on Windows, but I cannot repeat now. So fine to stay marked Linux.
If the root cause of this bug is Mutter, why not closing this one as NotOurBug ? Best regards. JBF
*** Bug 132213 has been marked as a duplicate of this bug. ***
Indeed, NOTOURBUG.
(In reply to Eike Rathke from comment #24) > Indeed, NOTOURBUG. Interesting attitude. If you buy a Toyota and the engine goes bad, do you expect Toyota to say, "Sorry, not our problem, they sold us bad engines." Your name is on the product. The product is broken. As a consumer, I look to you to fix it, not some nefarious mix of different manufacturers (each maker of an OS, in this case). Seems like it would be in the best interest of the Document Foundation to at least work with Linux, Windows and Mac developers to find an overarching solution, or separate solutions, for this problem. You simply cannot have a viable product by taking a flyer on these kinds of issues, essentially saying "tough luck, it's not our problem" to the end user. Again, it's your name on the product, and the end user could care less what environment he is in, all he knows that YOUR product is busted. Just my two cents.
@Larry, no, that’s not how we roll in open source. Our communities identify problems in each other’s software all the time by forwarding bugs. In this case the problem was addressed in Mutter five months ago: https://gitlab.gnome.org/GNOME/mutter/-/commit/2fbbf657d51f14bdcb75c045637e6ebf4df10063 So the “NOTOURBUG” resolution is correct here.
I opened a bug report that was closed as a duplicate of this bug, so I think that this bug is the right place for me to post my comment now. I just want to point out that this problem still exists under Ubuntu 20.04 and Libre Office 6.4.2.2. Ubuntu 20.04 went into production status a few days ago and I did a clean install of it on my system. I use it exactly as it shipped with no customization of any kind. But my situation is worse now because the login screen no longer offers me an "Ubuntu on Wayland" session which was the work around for this bug.
@Larry, Mutter is not part of LibreOffice, it is part of your distribution. There is a bug report against Mutter on Ubuntu bug tracker : https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852183 As reported there, this bug does not only impact LibreOffice. As read in the launchpad bug report, the Mutter bug seems fixed in its 3.36.2 version. Best regards. JBF
(In reply to larrybradley from comment #25) > Interesting attitude. If you buy a Toyota and the engine goes bad, do you > expect Toyota to say, "Sorry, not our problem, they sold us bad engines." Interesting approach. I hate car allegories, but the broken part is not even part of the car. So if the bridge you want to ride over is broken you go to the car manufacturer and tell him to make your car fly. > Your name is on the product. The product is broken. No, the clipboard manager of the compositor of your window manager of your operating system is broken. That's why there is the Mutter bug linked and this bug here is flagged as notourbug. Additional findings from the linked Mutter bug are that the problem seems to be (also) related to the Clipboard Indicator GNOME Shell Extension, see already comment 7 here, so you may want to remove that.
*** Bug 130012 has been marked as a duplicate of this bug. ***
All reports suggest that the bug occurs under Linux+GNOME, yet all other Linux+GNOME applications do mouse copy/pastes OK.
Occurs in LO 7.0.0-Alpha too Linux+GNOME
*** Bug 133140 has been marked as a duplicate of this bug. ***
"Workaround: login to a Wayland session instead of X11 (or maybe X-Wayland?) session." Wayland is not suppoeted by Ubuntu 20.04 LTS. Probably neither in eny Debian based Linux.
In reply to Eike Rathke, Comment 29 Thank you for looking at this issue and for your feedback. I appreciate the work you do and respect your thoughts and opinions.
(In reply to Eike Rathke from comment #29) > (In reply to larrybradley from comment #25) > > Interesting attitude. If you buy a Toyota and the engine goes bad, do you > > expect Toyota to say, "Sorry, not our problem, they sold us bad engines." > Interesting approach. I hate car allegories, but the broken part is not even > part of the car. So if the bridge you want to ride over is broken you go to > the car manufacturer and tell him to make your car fly. > > > Your name is on the product. The product is broken. > No, the clipboard manager clipboard manager of the compositor of your window manager of your > operating system is broken. That's why there is the Mutter bug linked and > this bug here is flagged as notourbug. > > Additional findings from the linked Mutter bug are that the problem seems to > be (also) related to the Clipboard Indicator GNOME Shell Extension, see > already comment 7 here, so you may want to remove that. I may be nave or ignorant, you guess, but 20some programs running on Gnome daily work just fine. so my guess is that they programmed their applications for Gnome and it works. Why LO be an exception?.
Carlos, there is no reason to reply you. You seem to be ignorant to read ubuntu bug report and test fix in 20.04.
I certainly ignore many things. Thank you.
*** Bug 134517 has been marked as a duplicate of this bug. ***
This happens to me too but I don't use Mutter. I use Manjaro KDE (with Plasma) https://ask.libreoffice.org/t/lo-detects-ctrl-v-and-ctrl-z-twice/68041
@albertoma/Moshpirit: Please create a new bug as this one here is specifically about the Mutter situation.