Problem description: when i copy&paste some text from gedit. Libreoffice inserts before each newline single space symbol. Steps to reproduce: 1. open gedit and print some text with newline(s): "aaa\nbbb\nccc" 2. open writer and copy-paste this text into new document 3. save like smth.odt Current behavior: After saving file looks pretty good, but if we close and open stored file the text will be "aaa \nbbb \nccc". Inside odt-archibe content.xml data tag which should contain "aaa" contains "aaa
". If we create new odt file and print text "aaa\nbbb\nccc", store and open it we'll see good text. Value inside content.xml is "aaa". Expected behavior: Data tage in content.xml should contain "aaa" instead of "aaa
". System: Debian Squeeze, Linux 2.6.32-5-amd64 #1 SMP x86_64 System charset: UTF-8 Operating System: Debian Version: 3.6.5.2 release
Hi, unable to reproduce with 3.8.3-203.fc18.i686.PAE and LO 3.6.5.2. Any more information available pls? Did you type anything else into either gedit or writer? Tks
Created attachment 77725 [details] content.xml file contains result of text "aaa\nbbb\nccc" storing by copy paste from gedit to libreoffice
No, noting else was printed either gedit or writer. Tried to reproduce same thing with Libreoffice 3.5.4.2 and got same result. Debian Squeeze, Linux 2.6.32-5-686 #1 SMP. I've added content.xml sample.
The bug is reproducable also with Xubuntu system, copy from mousepad-editor and insert into Libreoffice document (4.0.1.2).
The bug is reproducable also with Xubuntu system, copy from mousepad-editor and insert into Libreoffice document (4.0.1.2). Linux 3.8.0-17-generic #27-Ubuntu SMP i686
Additional information: all systems have UTF-8 as the default character set. All mentioned Libreoffice versions are for Russian language.
Created attachment 89636 [details] Comparison between Geany+Crunchbang11 vs gedit+Ubuntu1004. There has long been a problem with pasting plain text under Ubuntu 10.04 x86_64 from gedit v2.30.3 into various versions of LO. I have tested these versions: - v3.3.0.4 OOO330m19 Build: 6 - v3.4.6.2 OOO340m1 Build: 602 - v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b - v3.6.7.2 Build ID: e183d5b - v4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24 - v4.1.3.2 Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a The behaviour is identical for all versions and exactly as described in comment #0. The on screen display differs across versions as the screenshots show i.e., v4.0.6.2 and v4.1.3.2 show a large crossed out rectangle character that appears to be a carriage return (U+000d) as indicated in the report. In earlier versions the character does not display but it does impede cursor movement. For comparative purposes the same text entered into geany (text editor) under Crunchbang 11 x86_64 is also included. The original text files created by geany and gedit appear byte-for-byte identical (refer hexdumps) so the problem would seem to be either with gedit or the way in which LO is interpreting the clipboard data produced by gedit.
As per comment #7, confirmed. Status set to NEW. Version set to Inherited From OOo. I have only tested Writer, but if it is a clipboard issue then another component may be more appropriate.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT *Update the version field *Reply via email (please reply directly on the bug tracker) *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
Still an issue, at least on OSX, and has been for a while, however, this is not inherited from OOo, it has only recently appeared (as in, somewhere in the 4.x or 5.x branch)
*** Bug 96731 has been marked as a duplicate of this bug. ***
On OSX, the problem occurs when one copy/pastes text from within a Writer document.
(In reply to Alex Thurgood from comment #12) > On OSX, the problem occurs when one copy/pastes text from within a Writer > document. I'm not sure these are the same bug. I think the Writer bug was introduced by the "fix" to "bug" 34614.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
The problem still exists, so many years passed. :( Tested on version 5.2.2.2. Text "aaa bbb cd". ACT-1: Copying "bbb", insert it between "c" and "d", result "aaa bbb c bbb d". ACT-2 Copying "bbb", put cursor after "d", press space, make insert, result "aaa bbb cd bbb". Two spaces!!! Even when I need space before/after, I'm not sure that inserted symbol is really space (0x32). I have to move cursor to that blanks, remove them, add space. IMHO, PC must do what it is told to, without such "care". Really piss me off.
Putting back to NEW as there's no assignee to this bug
Changed version on bug from inherited to version 3.6.5.2 of first report. Testing with Ubuntu Xenial stock LibreOffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial1 CPU Threads: 2; OS Version: Linux 4.4; UI Render: default; Locale: en-US (en_US.UTF-8); Calc: group I get a different but still incorrect behavior. Can copy+paste between Geany and Gedit just fine. Copy+paste from either Geany or Gedit into LibreOffice *loses* the last character if the copied text ends with either a blank space or a newline. Otherwise, when the selection ends in a non-white (alphabetic) character, the copy+paste seems to work fine. So... it's not Gedit, etc. - it is LO. 1. I did not reproduce the originally reported buggy behavior - more like the inverse action - lost a character instead of getting an extra. 2. I tested with an older version of LO than Dmitry in his most recent test. 3. Could not reproduce reported extra character problem appearing after save+load. [the lost char didnt re-appear either] 4. No visible problem doing copy+paste FROM LibO. Upshot: LibreOffice 5.1.6.2 is losing terminal whitespace char in the paste from clipboard.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Dmitry, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Dmitry, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug