Description: I was using Writer (6.0.7.3) in Linux (Mint 19 Cinnamon) and tried to repeat this in Win7/32 with actual Portable version in a VM: Both versions are not able to transfer a format with the paintbrush symbol... Same function in Impress works well. - format of characters (font, (background/foreground)color, size, ...) works - format of paragraphs doesn't work (left, right, distance to the (next / following) paragraph, ...) . Additional fault 1: ------------------- format of characters is only able to ADD a new attribute to a font. example: a) source font has a color ... target font has no color -- THEN it's possible to copy the attribute to the target. b) source font has NO color ... target font has already a color -- THEN it's not possible to transfer the "unformatted attribute" the the colored font. .. in the same time the font attribute (courier) will copied, but not the white backround or black color of the character. . Additional fault 2: ------------------- The certificate of Portable App (Installer) is from "RareIdeas LLC" ... serious? I make a download of an exe-file and get this meaningful description of the supplier? ANYONE is able to get such a funny name. How is this certificate able to protect me and other users from getting a virus? Any manufacturer of a virus is forced by law / will of course use a signature with a name like "dangerous company". Promised! . Which further informations ========================== ... are nesseccary to work on this issues? Steps to Reproduce: 1. use two paragraphs 2. format one paragraph 3. try to copy the format (of the paragraph) to the second one Actual Results: no changes with paragraph settings. character settings will be copied Expected Results: paragraph settings will also be copied (like in MS Office or in Impress) Reproducible: Always User Profile Reset: No Additional Info:
no seriously work will be done with this fault. please pay attention that a bugfix will need much more time to grow into a actual distribution... maintainers will restrain the most actual versions... in windows a update is more simple and fast
whats the meaning of: "no seriously work will be done with this fault." a) my description is bad? b) the fault is fixed for actual versions? c) the fault is not urgent? the fault is "working" in different versions for Linux & Windows... The fault is working in older versions and reproducable in all versions which I have access to. So I think that this fault is a very old one and nobody will fix this. Actually I'm working with ( I'll try to work with ...! ) a old version in Linux Mint.... And whats the meaning of: "in windows a update is more simple and fast"... should I change to windows again?
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Hello, because of using Linux Mint 19 I'm not able to use a newer version on this operationg system. But I've seen that the fault is also reproducable in Windows (portable version) ... as described. So the problem seems to be "old", and also existent in actual versions (of linux also). 1. Do you have any information about the possibility that the fault is solved? I'm able to try another portable version in Windows. 2. Are you able to reproduce the problem with your version? (Is my description good enough?) Ahh... I've a Kubuntu with 6.2.7.1... ;) The problem is there also: 1a. format of characters will be "added" to text with LESS format. (unformatted text will be coloured) 1b. format will not be subtracted when the source text has less format information (formatted text will not lose the informations.) you can ADD format informations, but not remove. 2. format of paragraphs will not copied! I tried: a) "indent"(?) and b) "space after the line". 3. I didn't try double-click for multiple use... My native language (german) would be helpfull to describe the issue. I hope this helps anyway ;)
Please understand this is not correct bug report, simple and clear, per https://wiki.documentfoundation.org/QA/BugReport. You need to write reproducible steps and expected and reproduced results just for a single issue.
Sorry for inconvenience :D Do you think, that it's helpfull to ignore a bug, because I'm "not able" to write a bug-report as reliant in your manual? Should I read the manual first? NO! Do you think, that it's helpfull for other users who want to use this programm / function? . My first assignment was to check: --------------------------------- a) install a newer version (within a distribution which delivers this old version?) b) test again c) report again! Perhaps do you think I have to learn to write the code of this unfit program? . I described the bug ------------------- ... and you should be able to reproduce the bug if you are wlling to read my detailed descriptions (Plural!). Did you tryed it once? Or do you want to show the stickler? Do you think, that every USER (german: "DAU" (most stupid assuming user)) should read and follow your manual "for correct writing bug-reports" first? You are funny! . Should I list ALL the "funny" bugs that I "found" in the last months in all "my (tried) linux distrubutions and programs" since I tried to change my OS from Windows to Linux? Including total crash down to BIOS without "bluescreen"? ... Including some total crashes of the graphic surface to the logon screen ... while copying files from one drive to another? I "heard about" sealed off sessions and if one session has a problem ... no other program is affected an not the whole OS chrashes with all running programms (incl. VM) and with all unsaved documents? Sounds good! ... but does not work in Linux! Such problems I've had with Windows 98 ... 15 years ago! You are very funny! Should I send you my list? . What do you think: For how many bug-trackers I have to sign up when changing my OS? 1a. Debian ... Ubuntu ... Kubunu ... Mint? ... Raspberian? 1b. Arch Linux ... Manjaro? 1c. Virtual Box? 2. for every Program I use? 3. Forums? . And for all bugs in these distros and programs I have to get an account in bug tracking platforms, manage new passwords, learn the differences of behavior and possibilities of these different bug-tracking-platforms (Mantis & Co.) and learn to write a correct bug report as instructed in "the manual"? . And then I have to translate my problem: a. try to find if it is my wrongdoing or a bug of the programm ... in different versions and different OS (Windows, Linux, PortableApp, ... perhaps android?) b. translate the problem and my steps into words... c. change this words from my native language into understandable/simple english? You are very, very funny! . If you have quaestions... ask! If you don't understand "my" english... invite somebody who is able to speak german to this bug report... and I'm willing to describe all parts in german! . Post Scriptum I --------------- take the bug and feel free to let this work-disability in the product. Are you interested to improve "your" program or not? You show a bad kind of work setting! Because of this (and of other unsupportive individualists (aka persons)) (Libre) Office (and many Linux programs) will not (never say never!) be better than MS Office. Not in the next 30 years! . This kind of unwilling to solve the problem is a reason to re-change the operating system! In spite of all errors of the company MS: Since many years MS consumes the fruits of the work that was made in the early 90s and all linux programmers seem to invest more power into different surfeaces of programs and distributions, instead of doing important things first. . Post Scriptum II ---------------- Please change the green sentence in the right upper corner: "After you've satisfied the request as best as you can ..." . "do it like that!" (Jean Luc Picard)
You didn't folow the rules, didn't provide what's required and now it's loosing your and out time. We can't say if it's a real bug or you just don't use Format Paintbrush properly like in Bug 103793 or Bug 112872. I close the bug as Invalid.
I read the "how-to" and found no errors on my site. Contrary to your own requirements, you do not seem to be willing to specify the passage in the wiki exactly where exact instructions can be found. I had to work through the whole text first. I met all requirements: - I described the error IN DETAIL - I described the expectations - I pointed to the different (newest) versions of "Writer" on which I performed the tests. Closing the bug as invalid does not help the buggy program and the bug at all. One of two referenced bugs was from Calc. Where should this ticket help me? I have also no problem with the PowerPoint counterpart and do not need a ticket number of this program, but with Writer I have a seemingly ancient problem that no one edited. Maybe you're more concerned with the problem, read my detailed description, and less concerned with the defense. Then the problem would probably not be so old, but already solved!
Insufficient data for simple test and confirmation. Wolfgang, this is your first bug report and you didn't follow our rules from Comment 5. We are volunteers who triage thousands of bugs and we cannot guess. Should you write exact steps for a single issue - and only then - you may set Unconfirmed. For example, just "format of paragraphs", not clear whether you hold down Ctrl when you click.