Description: I'm running LO 6.2.5.2 on MacOS 10.14.5 on an early 2015 MacBook Air. I had the same problem on an older MacBook Pro. I don't have the numbers handy for that one right now, but it was at least a pretty recent operating system. Might have been High Sierra. I'm using a program called Express Scribe. It runs in the background and lets me control audio playback with hotkeys while typing directly into a word processor. One of the hotkey functions copies the current timestamp, which I can then paste into my work. When I paste the timestamps into Writer, there's a hashtag / pound sign at the end. Like so: 00:02:03# This happens no matter what hotkey combination I assign to this function, and so far it only happens in LibreOffice Writer. When I copied a timestamp into a Reddit post, it appeared normal at first, but after publishing the post, the unicode replacement character was attached to the final number. I assume whatever character or code Reddit rendered as the replacement character, is the same thing that Writer is rendering as a hashtag. Copying a timestamp into Google Docs or Microsoft Word, however, produces nothing except the timestamp itself. I've also noticed that if I copy anything within Writer itself, the next time I go to copy and paste a timestamp, it instead pastes the previously copied text. But if I paste into another application (without re-copying the timestamp) it correctly pastes the timestamp. I've "solved" this second issue by actively clicking back into Express Scribe and copying the timestamp again, which seems to reset whatever's going on there. Similar / related issue: I'm using Text Expander 6.5.2. If I copy any text within Writer, the next time I type something that is supposed to expand, it instead stalls and then pastes the copied text. This one seems easier to fix—I just have to click into another application, and then back into Writer. So far, I haven't had the hashtag / pound sign issue with Text Expander. Oddly enough, none of these problems are happening in Calc. I haven't tested it in any other LO applications. Steps to Reproduce: 1. Copy a timestamp in Express Scribe (it has a free trial). 2. Paste the timestamp into Writer. 3. Copy text within Writer. 4. Copy another timestamp without actively clicking into Express Scribe, just letting it run in the background. 5. Try to paste the timestamp you just copied. 6. Try to paste the timestamp into Google Chrome, WITHOUT copying it again. 7. Click into Express Scribe. Copy another timestamp. 8. Paste that timestamp into Writer. 9. Set up a Text Expander snippet. (It also has a free trial.) 10. Utilize the snippet in Writer. 11. Copy text within Writer. 12. Try to use the snippet again. 13. Click into any other program. 14. Click back into Writer. 15. Try the snippet again. Actual Results: The first timestamp pastes in with a hashtag attached. The second timestamp does not paste into Writer at all. The previously copied text is pasted instead. However, the second timestamp does paste into Google Chrome, with no hashtag. The third hashtag pastes into Writer as usual, with a hashtag attached. The first Text Expander snippet works just fine. The second Text Expander snippet does not work. Writer stalls, and then pastes in the copied text instead. The third Text Expander snippet works just fine. Expected Results: Regarding the hashtags: I wish there was an easy way to dictate how Writer should handle unidentified characters, so I could make a selection like "ignore and delete" and set that as the default. Regarding the copy and paste overwrites: The last thing I actually copied should be what I get when I paste, and the clipboard should not be interfering with Text Expander. Reproducible: Always User Profile Reset: No Additional Info: I realize this issue involves other programs, and may therefore be out of LibreOffice's hands.
This is a very complicated set of steps requiring at least 2 other software applications in order to try and confirm, and involving installing those applications under conditions in which the testers may not feel entirely happy doing so (particularly if they are not open source programs), so it seems unlikely that this report will ever be confirmed. That isn't to say that it won't be, but the reality of the situation is that there are relatively few testers on macOS, and most of them are probably loathe to install proprietary software they don't need. That aside, and FWIW, there is currently ongoing development to try and improve the copy/paste mechanisms within LO, so hopefully one of those code changes might bring a positive change to your problem in the near-ish future. Additionally, the copy/paste mechanism is inevitably dependent on how the OS handles such data.
(In reply to Alex Thurgood from comment #1) > This is a very complicated set of steps requiring at least 2 other software > applications in order to try and confirm, and involving installing those > applications under conditions in which the testers may not feel entirely > happy doing so (particularly if they are not open source programs), so it > seems unlikely that this report will ever be confirmed. > > That isn't to say that it won't be, but the reality of the situation is that > there are relatively few testers on macOS, and most of them are probably > loathe to install proprietary software they don't need. > > That aside, and FWIW, there is currently ongoing development to try and > improve the copy/paste mechanisms within LO, so hopefully one of those code > changes might bring a positive change to your problem in the near-ish > future. Additionally, the copy/paste mechanism is inevitably dependent on > how the OS handles such data. Yeah, I totally understand. I was asking around online just to see if anyone had any ideas about what I could do, and someone suggested that I file a report here for the sake of documenting it. I'm just switching to another program for now. That's very encouraging to hear re: copy/paste development. I've definitely seen other people with similar problems while I was Googling around for a solution.
(In reply to foundintranscription from comment #2) > I've definitely > seen other people with similar problems while I was Googling around for a > solution. So perhaps you can motivate them to confirm this bug.
This one is Unconfirmed and I don't see it will be, so I'll close. Or you may put some sample document and simple steps, if you can. Sorry, this is not realistic to follow.
Note: bug 128714 Copy and paste within same document pasting previous buffer entry. bug 90120 Editing: Pasting text to Writer from web, e-mail or documents sometimes doesn't work, it's a random beahaviour. bug 57147 EDITING: Paste stops working after several copy-paste (steps: comment 28)