I have a table 5x8 I copy a text from a cell into another Text style is not kept. No specific style applied to any of the cells. If I go in the cell and type, the font style is coherent with the source. If I paste font style formatting is altered. I have added / removed lines at the end of the table.
Created attachment 116358 [details] printscreen I can confirm with Version: 5.1.0.0.alpha1+ Build ID: eb8c323d94bf13d4a373f88c6b932a97701c283b TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-06-05_00:59:00
works OK in LO 4.3.7, regression
(In reply to raal from comment #1) > Created attachment 116358 [details] > printscreen > > I can confirm with Version: 5.1.0.0.alpha1+ > Build ID: eb8c323d94bf13d4a373f88c6b932a97701c283b > TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: > 2015-06-05_00:59:00 Reproduced with copy+paste
This seems to have begun at the below commit. Adding Cc: to sbergman@redhat.com ; Could you possibly take a look at this one? Thanks 193ccffc25300d5c26e6f30ab06a2315b6bff879 is the first bad commit commit 193ccffc25300d5c26e6f30ab06a2315b6bff879 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sat Jul 11 20:21:02 2015 -0700 source c725ebaced006c02baeb9b0ee5ac6ac4625adc01 source c725ebaced006c02baeb9b0ee5ac6ac4625adc01 author Stephan Bergmann <sbergman@redhat.com> 2015-05-28 21:21:10 (GMT) committer Stephan Bergmann <sbergman@redhat.com> 2015-05-28 21:21:10 (GMT) commit c725ebaced006c02baeb9b0ee5ac6ac4625adc01 (patch)
(In reply to raal from comment #4) > This seems to have begun at the below commit. > Adding Cc: to sbergman@redhat.com ; Could you possibly take a look at this > one? Thanks > > 193ccffc25300d5c26e6f30ab06a2315b6bff879 is the first bad commit > commit 193ccffc25300d5c26e6f30ab06a2315b6bff879 > Author: Norbert Thiebaud <nthiebaud@gmail.com> > Date: Sat Jul 11 20:21:02 2015 -0700 > > source c725ebaced006c02baeb9b0ee5ac6ac4625adc01 > > source c725ebaced006c02baeb9b0ee5ac6ac4625adc01 > > author Stephan Bergmann <sbergman@redhat.com> 2015-05-28 21:21:10 (GMT) > committer Stephan Bergmann <sbergman@redhat.com> 2015-05-28 21:21:10 (GMT) > commit c725ebaced006c02baeb9b0ee5ac6ac4625adc01 (patch) raal, please provide either the commit message of the (last good) commit in the bibisect repo directly preceding this commit, or at least the URL of the bibisect repo (so I can determine that preceding commit myself). (Individual commits in bibisect repos often correspond to a range of source commits, so it is always important to know that full range.)
(In reply to Stephan Bergmann from comment #5) bibisect-win32-5.1 git bisect log # bad: [d07ec272f151832493f57ce3fde37a429eaf6014] source 233b9b0ec95069b5ce98aab942304459ca7344a8 # good: [c1efd324c6ad448ac9edb030dc9738b9e6899e4d] source ab465b90f6c6da5595393a0ba73f33a1e71a2b65 git bisect start 'd07ec272f151832493f57ce3fde37a429eaf6014' 'c1efd324c6ad448ac9edb030dc9738b9e6899e4d' # bad: [75b0ef076d724d10ed74681ba542db53f088b4ca] source 6dddd1aaf5dd3c54aaf87222712c9147466056f6 git bisect bad 75b0ef076d724d10ed74681ba542db53f088b4ca # bad: [7f6e13f8050660b9e6ff832b34e0a3f5c1f1a38d] source b998be6e42eeb57abf5131adc06aa45588542f62 git bisect bad 7f6e13f8050660b9e6ff832b34e0a3f5c1f1a38d # bad: [8a6b9507b0337ce070b2900f111fc3e947396a6a] source 970458c5ee4e6077836839397e556132544a3b6e git bisect bad 8a6b9507b0337ce070b2900f111fc3e947396a6a # bad: [ba88e179a3e86e459cfc4d15f78a4ffee7294656] source 9ce71b67f705ccbc6df327d1bb181ca20b3ed17f git bisect bad ba88e179a3e86e459cfc4d15f78a4ffee7294656 # good: [98f041edb433e0a07778c5f32af45d7c5be8a456] source 3185b6c8caf97afa602c864f588d079cbbe04038 git bisect good 98f041edb433e0a07778c5f32af45d7c5be8a456 # good: [ff59691aca3a1607445fcdb7ccd8b6640254552e] source cc7b8dab7522886f13780950c93033e3369da285 git bisect good ff59691aca3a1607445fcdb7ccd8b6640254552e # good: [e390804b0626adbb3df1da437d2124f62b017674] source 39f3039724f3933963f861f4afc24a92348eb991 git bisect good e390804b0626adbb3df1da437d2124f62b017674 # good: [c23c4d2e2c6ea524463f5be38b071dede1da0e5a] source 82f15336cfbcb766c060c4936d11ff33c54558e4 git bisect good c23c4d2e2c6ea524463f5be38b071dede1da0e5a # bad: [193ccffc25300d5c26e6f30ab06a2315b6bff879] source c725ebaced006c02baeb9b0ee5ac6ac4625adc01 git bisect bad 193ccffc25300d5c26e6f30ab06a2315b6bff879 # good: [cf5afac9e3bcb4c0b9c5b7468b223ce0b13c0588] source 9d6f44ccdd5eed7dd9f1a21612be3eca01aeb429 git bisect good cf5afac9e3bcb4c0b9c5b7468b223ce0b13c0588 # good: [95e1e9454be99fdd9c4755ebd7177a07a6e5ac67] source 53a066b7d1a639c6d31655bfc7c6257896fb57ef git bisect good 95e1e9454be99fdd9c4755ebd7177a07a6e5ac67 # good: [ee6ec68bde95dad4a5d07580a4e5b745e3a03935] source e17fa49d99ce8de3fb9d026b515a7c7e1f00d269 git bisect good ee6ec68bde95dad4a5d07580a4e5b745e3a03935 # first bad commit: [193ccffc25300d5c26e6f30ab06a2315b6bff879] source c725ebaced006c02baeb9b0ee5ac6ac4625adc01
sorry, I'm not looking for the output of "git bisect log" but of either "git log -1 193ccffc25300d5c26e6f30ab06a2315b6bff879^" or at least "cat .git/config"
(In reply to Stephan Bergmann from comment #7) > sorry, I'm not looking for the output of "git bisect log" but of either "git > log -1 193ccffc25300d5c26e6f30ab06a2315b6bff879^" or at least "cat > .git/config" git log -1 193ccffc25300d5c26e6f30ab06a2315b6bff879^ commit ee6ec68bde95dad4a5d07580a4e5b745e3a03935 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sat Jul 11 20:15:41 2015 -0700 source e17fa49d99ce8de3fb9d026b515a7c7e1f00d269 source e17fa49d99ce8de3fb9d026b515a7c7e1f00d269 cat .git/config [core] repositoryformatversion = 0 filemode = false bare = false logallrefupdates = true symlinks = false ignorecase = true hideDotFiles = dotGitOnly [remote "origin"] url = git://gerrit.libreoffice.org/bibisect-win32-5.1 fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master
> $ git log --oneline e17fa49d99ce8de3fb9d026b515a7c7e1f00d269..c725ebaced006c02baeb9b0ee5ac6ac4625adc01 > c725eba brown paper bag So that bibisect repo commit indeed corresponds to exactly that one source commit. But it looks suspicious that that Writer-specific fix (of a problem introduced a few commits earlier) should be related to this issue in Impress.
I cannot reproduce this with my own recent master (64 bit) build for Windows. Please describe exactly the steps how to reproduce.
(In reply to Stephan Bergmann from comment #10) > I cannot reproduce this with my own recent master (64 bit) build for > Windows. Please describe exactly the steps how to reproduce. new impress document insert table write some string into the cell set font italic select string ctrl+c select another cell ctrl+v pasted string is not italic
No, I still cannot reproduce (on a Win 7 box), even with the mentioned bibisect repo commit: > $ git clone git://gerrit.libreoffice.org/bibisect-win32-5.1 > $ cd bibisect-win32-5.1 > $ git checkout 193ccffc25300d5c26e6f30ab06a2315b6bff879 > $ instdir/program/soffice.exe --impress * select "Insert - Table..." * select "OK" * click into first column, first row * type "foo" * press Ctrl-A * press Ctrl-I, "foo" is now italic * press Ctrl-C * click into second column, second row * press Ctrl-V, italic "foo" is inserted
Hello Philippe, please could you test it with dev version? You can download it here: http://dev-builds.libreoffice.org/daily/master/ Thank you
Migrating Whiteboard tags to Keywords: (bibisected) [NinjaEdit]
** 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
Needinfo more that 6 months and his is not progressing. No repro for Stephan and me. Thanks to Raal but steps are not reproducible. There must be something else that affects that "sometimes". Philippe also didn't respond.