[Libreoffice-bugs] [Bug 153916] Writer strange behavior with big pictures
https://bugs.documentfoundation.org/show_bug.cgi?id=153916 --- Comment #2 from Kurosh Tavassoli --- I've uploaded the buggy document in attachments. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153916] Writer strange behavior with big pictures
https://bugs.documentfoundation.org/show_bug.cgi?id=153916 Kurosh Tavassoli changed: What|Removed |Added CC||rubar...@tutanota.com --- Comment #1 from Kurosh Tavassoli --- Created attachment 185688 --> https://bugs.documentfoundation.org/attachment.cgi?id=185688=edit The bug indication -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151430] Groupedbar Compact UI : missing "columns..." entry of the "format" menu of the menu bar
https://bugs.documentfoundation.org/show_bug.cgi?id=151430 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||mentoring@documentfoundatio ||n.org Status|UNCONFIRMED |NEW Keywords|needsUXEval |difficultyBeginner, ||easyHack, skillDesign, ||topicDesign Ever confirmed|0 |1 Severity|normal |enhancement --- Comment #5 from Heiko Tietze --- We discussed the topic in the design meeting. The columns seems to be relevant enough to be accessible via the primary UI. We suggest to add it into the Insert menu. Code pointer: sw/uiconfig/swriter/ui/notebookbar_groupedbar_compact.ui Underneath add a similar child with the command .uno:PageColumnType -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153905] PDF files created with LibO print incorrectly to some printers
https://bugs.documentfoundation.org/show_bug.cgi?id=153905 --- Comment #7 from Callegar --- Created attachment 185687 --> https://bugs.documentfoundation.org/attachment.cgi?id=185687=edit How the document prints -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152657] Slower graphical performance and laggy behavior on data entry with large window (GTK)
https://bugs.documentfoundation.org/show_bug.cgi?id=152657 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #16 from Stéphane Guillou (stragu) --- (In reply to Caolán McNamara from comment #15) > caolanm->stragu: I'm not sure I can see this problem. With attachment 184401 > [details] clicking in A150 (default top left cell) and holding down "k" the > bibisect builds seem to me as responsive in 7.4 as 7.0. In my dbgutil build > there does seem to be a lag when enough "k"s are inserted to go multiline > but that could seems to be an artifact of the extra debugging checks and > there wasn't mention that the input string has to be crazy long for the > effect to be seen. > The difference is a bit subtle for me, but noticeable. I make sure I fullscreen the window, and zoom out a bit to view a large number of cells. Repeating the character is smooth before the commit, and a bit jumpy after the commit but smooth again if formula bar is hidden. lp.allard, it would be great if you could confirm that we are seeing the same issue by: - Testing version 7.0 and verifying that the issue is not there; - Deactivating the formula bar in View > Formula Bar to see if the performance issue disappears in recent versions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153916] New: Writer strange behavior with big pictures
https://bugs.documentfoundation.org/show_bug.cgi?id=153916 Bug ID: 153916 Summary: Writer strange behavior with big pictures Product: LibreOffice Version: 7.5.0.3 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rubar...@tutanota.com Description: When we add a pig picture to a document, we can insert infinite new lines without creating a new page. Steps to Reproduce: This happened to me twice with same picture on two different machines. 1- open a PDF with L.O. Draw 2- Copy a whole page as an image 3- Insert image on second page of a writer document 4- Try to insert new lines just after the image Actual Results: Writer does nothing. It just doesn't do anything. Expected Results: Writer is supposed to create new pages, when we reach end of the last page. Reproducible: Always User Profile Reset: No Additional Info: I've written bug description in the .odt file attached but I can't find anywhere to upload it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103100 Bug 103100 depends on bug 140173, which changed state. Bug 140173 Summary: paragraph properties do not spread across cells in a table - libreoffice writer https://bugs.documentfoundation.org/show_bug.cgi?id=140173 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140173] paragraph properties do not spread across cells in a table - libreoffice writer
https://bugs.documentfoundation.org/show_bug.cgi?id=140173 Dieter changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Dieter --- Bug no longer present in Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded => RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153636] "Use level from source chapter" does not work for Graphics and Frames in User-defined index
https://bugs.documentfoundation.org/show_bug.cgi?id=153636 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||dgp-m...@gmx.de Whiteboard| QA:needsComment| --- Comment #1 from Dieter --- I miss help about "Use level from source chapter", so I'm not sure about expected result. As far as I understand: "Heading OL 2" is PS Heading 5 (= chapter level 5) "Heading OL 3" is PS Heading 2 (= chapter level 2) So table 1 and figure should have same indent and table 2 and image, correct? If this is the expected result, I confirm the bug. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ab20dba30769a5a52830220daa347772485db6a2 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131196] Formcontrols: Borders couldn't be set to "no border" through macros
https://bugs.documentfoundation.org/show_bug.cgi?id=131196 --- Comment #10 from Mike Kaganski --- (In reply to Andreas Heinisch from comment #7) > If I set the border property to "NOBORDER (4096)" the border disappears. > Maybe there is a misunderstanding between "NONE" and "NOBORDER"? The description misses one important bit: "Look at UnoControlEditModel Service documentation at https://api.libreoffice.org/docs/idl/ref/servicecom_1_1sun_1_1star_1_1awt_1_1UnoControlEditModel.html#a54d3ff280d892218d71e667f81ce99d4, and see that the three documented values for the Border property are "0: No border", "1: 3D border", and "2: simple border"". It seems to me that Andreas could be right, suspecting the documentation issue here. Or maybe (better) the "0: No border" should be converted to the VCL-internal "0x1000 NOBORDER" in UnoControlFormattedFieldModel::convertFastPropertyValue (and likewise for other control model services having Border property with identical allowed value sets, after testing that they indeed also have the same issue). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153334] Support/default to a non-white page background in Dark Mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153334 Heiko Tietze changed: What|Removed |Added Severity|minor |enhancement Keywords|needsUXEval | Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||c...@nouenoff.nl --- Comment #17 from Heiko Tietze --- We discussed this topic in the design meeting. The convincing argument to not resolve WF likewise bug 152184 is using the night shift with the expectation that app colors (AC) follow. The AC are a user-defined list filled from hard-coded values (some like hyperlinks taken from the OS). Users can add schemes, modify colors, and delete any. We cannot trust in the existence of any scheme and the proposal was to remove AC in favor of hard-coded light and dark colors. (Nothing to say against a customization in terms of personalization aka LibreOffice theme later.) However, there are users who want to change the AC; the idea was to use the shipped AC schemes despite the mentioned issues and just inform the user if something is missing. We could also separate the light/dark AC schemes, add an option to follow the system color, and provide an option to use the user-defined AC. Wouldn't be a simplification but an acceptable compromise. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153905] PDF files created with LibO print incorrectly to some printers
https://bugs.documentfoundation.org/show_bug.cgi?id=153905 --- Comment #6 from Callegar --- As a final note, I would like to report that if you take the PDF file produced by LibO and you process it using `ghostscript` on a system that has the needed fonts, e.g. using gs -q -dNOPAUSE -dBATCH -dPDFSETTINGS=/prepress -sDEVICE=pdfwrite -sOutputFile=output.pdf input.pdf then the PDF file obtained by ghostscripts gets the fonts re-embedded as: name type encoding emb sub uni object ID - --- --- --- - AKSFEQ+DummyName Type 1C Custom yes yes no 7 0 FNPCHA+DummyName Type 1C Custom yes yes no 9 0 LKVFDZ+ArialMT TrueType WinAnsi yes yes yes 11 0 UNQEAT+DummyName Type 1C Custom yes yes no 13 0 TFLMGS+DummyName Type 1C Custom yes yes no 15 0 Once this is done, the PDF file prints perfectly. So, I would tend to think that there is an issue in how LibO embeds the fonts in the PDF file when it exports it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153882] [FONT] Rendering issues with the free font Wedgie.
https://bugs.documentfoundation.org/show_bug.cgi?id=153882 --- Comment #11 from igorc...@yahoo.it --- (In reply to Dennis Roczek from comment #10) > (In reply to igorchco from comment #6) > > Have you seen the image I have attached to the bug report?! > I did, no repro on Linux except underline. So most problems are only on Windows, thanks. > > > If you open the attached test file > > https://bugs.documentfoundation.org/attachment.cgi?id=185647 try to change > > the text dimensions. > > 14: all is well rendered except strike-though. > > 22: are well rendered only bold and bold-italic. > > 36: are well rendered only normal, italic and underlined. > Hence, it is always definitive better, if the reporter attaches the file. :-) > I attached the explicative image so that you can see how it works correctly/bad. However thanks for the text test file. > > All is well rendered in other softwares, including strike-though. > Might be, might be not. This is about LibreOffice. This is about LibreOffice that is expected to render the font the same all the other softwares do. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153905] PDF files created with LibO print incorrectly to some printers
https://bugs.documentfoundation.org/show_bug.cgi?id=153905 --- Comment #5 from Callegar --- The fonts in the PDF document are indeed reported as Type1 (you check them with the `pdffonts` utility as well, rather than using the information window in the PDF viewer). With this you get: name type encoding emb sub uni object ID - --- --- --- - BA+SourceSansPro-Light Type 1Builtin yes yes yes 24 0 CA+SourceSans3-Bold Type 1Builtin yes yes yes 19 0 DA+ArialMT TrueType WinAnsi yes yes yes 29 0 EA+SourceSans3-Regular Type 1Builtin yes yes yes 14 0 FA+SourceSans3-ItType 1Builtin yes yes yes 9 0 The fonts file are originally OpenType fonts. To the best of my understanding, OTF fonts can either contain font data in a TrueType-like format or in a Type1-like format, the main difference between the two being that the TrueType format encodes the font contours in quadratic splines, while Type1 uses cubic splines (and should, at least in principle, have a potential advantage in rendering quality). When the fonts get "embedded" in a PDF document, it is the actual font data that gets embedded, so that any font diagnostics will either report "TrueType" or "Type1". On github, Adobe distributes either the fonts as OTFs or TTFs. In both cases you get fonts that are recognized as OpenType by the system, but the OTF fonts contain Type-1 font data, while the TTF fonts contain TrueType font data. I am on Linux and in this case the fonts can be installed in multiple ways. If you have Arch/Manjaro, then they come with the distro, in the `adobe-source-sans-fonts` package. The Arch/Manjaro package uses the OTF version of the font, with the expectation that it should be (slightly) higher quality. However, I have also tried with an Ubuntu system, where the font is not available out of the box. In this case, I have downloaded the `OTF-source-sans-3.046R.zip` file from `https://github.com/adobe-fonts/source-sans/releases/tag/3.046R` and unpacked it into the `.fonts` directory in my home (in some systems you need to use `.local/share/fonts`). So that the fonts can be found by `fontconfig`. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153727] Calc inputwin for formula bar using system font, too small for CJK input
https://bugs.documentfoundation.org/show_bug.cgi?id=153727 Heiko Tietze changed: What|Removed |Added Hardware|x86-64 (AMD64) |All OS|Windows (All) |All CC|libreoffice-ux-advise@lists |c...@nouenoff.nl, |.freedesktop.org|heiko.tietze@documentfounda ||tion.org Keywords|needsUXEval | --- Comment #20 from Heiko Tietze --- We discussed this topic in the design meeting. a) some comments here are towards resolving as NAB The UI should be kept clean; however, at least based on the number of requests the desire is clear b) add an option to tools > options > calc > view This would be a simple solution but likely not usable as the needed font size in the formula bar depends on cell content. Plus, it inflates the options dialog further. c) have some kind of interaction on the control, could be a drop down with a couple of font sizes or some ctrl+wheel response specifically on the control This possible solution was not prioritized as it would be hard to figure out. d) follow the selected cell's font (maybe all attributes not just the size) Needs some work to make it working reliable (multi-selection) but will always end up in a jumping UI; was removed for bug 127066 e) follow the zoom factor on the sheet Not necessarily what users expect; but would be a straight-forward solution, easy to understand f) show the content somewhere else (or in a tooltip) Was not welcome as a good solution. The question is what issue exactly should be resolved. Make more content visible in the formula bar (the bar has an expander to show almost a novel) or make it better readable. Please elaborate the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107243] [META] Locale keyboard shortcut issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107243 Dieter changed: What|Removed |Added Depends on||153629 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153629 [Bug 153629] Wrong shortcuts in Swedish UI -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153629] Wrong shortcuts in Swedish UI
https://bugs.documentfoundation.org/show_bug.cgi?id=153629 Dieter changed: What|Removed |Added Summary|Probably a language issues |Wrong shortcuts in Swedish |with the 7.5.0.3 version. |UI CC||dgp-m...@gmx.de Blocks||107243 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107243 [Bug 107243] [META] Locale keyboard shortcut issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105605] [META] Digital signatures bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105605 Dieter changed: What|Removed |Added Depends on||153626 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153626 [Bug 153626] Unable to sign with existing digital signature, and inconsistent UI for digital signature in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153626] Unable to sign with existing digital signature, and inconsistent UI for digital signature in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153626 Dieter changed: What|Removed |Added Blocks||105605 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=105605 [Bug 105605] [META] Digital signatures bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 62032] Cannot specify a Paragraph Style to use a numbering level (over 1) for a chosen Numbering (List) style (See comment 35)
https://bugs.documentfoundation.org/show_bug.cgi?id=62032 --- Comment #57 from sdc.bla...@youmail.dk --- (In reply to Commit Notification from comment #55) > Affected users are encouraged to test the fix and report feedback. 1. "List Level" is not remembered (and not applied). Test A. Use existing PS, change List Level to "Level 2" (OK). Apply updated PS to paragraph Actual: Outline level is applied, List level is 1. Expected: Outline level is applied, List level is 2. Test B. Make a new PS. Set Outline Level 2, List Level 2 Apply new PS to paragraph Actual: Outline level is applied, List level is 1. Expected: Outline level is applied, List level is 2. Test C. With each PS from Test A and Test B. Set list level as "Same as outline level" Actual: Outline level is applied, List level is 1. Expected: Outline level is applied, List level is 2. In all cases, after opening the PS for editing, the list level had reverted to Level 1. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 46e74a8bf03c06776cb144418206db7c4b843b41 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108660] [META] Formula bar (input line) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108660 Bug 108660 depends on bug 88141, which changed state. Bug 88141 Summary: Calc - Formula Bar Font Size https://bugs.documentfoundation.org/show_bug.cgi?id=88141 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153727] Calc inputwin for formula bar using system font, too small for CJK input
https://bugs.documentfoundation.org/show_bug.cgi?id=153727 Heiko Tietze changed: What|Removed |Added CC||de...@speakeasy.net --- Comment #19 from Heiko Tietze --- *** Bug 88141 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88141] Calc - Formula Bar Font Size
https://bugs.documentfoundation.org/show_bug.cgi?id=88141 Heiko Tietze changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #7 from Heiko Tietze --- Usually we make the newer topic a duplicate of the older but in this case the discussion has been more intensive at bug 153727. Please join there. *** This bug has been marked as a duplicate of bug 153727 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | Severity|normal |enhancement CC|libreoffice-ux-advise@lists |c...@nouenoff.nl, |.freedesktop.org|heiko.tietze@documentfounda ||tion.org --- Comment #13 from Heiko Tietze --- We discussed this topic in the design meeting. If the modification is consistent for all type of indices the suggested label H# instead of E# (and HI instead of CI) is welcome. (In reply to Mike Kaganski from comment #11) > The E corresponds to "Entries" tab name. It's all about E# / Chapter No (now Heading No). I could live with Entry No too. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152189] styles list "new", plus "DUPLICATE" !
https://bugs.documentfoundation.org/show_bug.cgi?id=152189 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3634 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153634] Page styles: create new "duplicate" copy style
https://bugs.documentfoundation.org/show_bug.cgi?id=153634 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org Whiteboard| QA:needsComment| Blocks||108576 Keywords||needsUXEval See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2189 Summary|styles: create new |Page styles: create new |"duplicate" copy style |"duplicate" copy style --- Comment #1 from Dieter --- Since LO doesn't know inherited page styles (feature request in bug 41316), the method described in bug 152189 doesn't work. So we should rethink previous decision - at least for page styles cc: Design-Team Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108576 [Bug 108576] [META] Writer page style bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108576] [META] Writer page style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108576 Dieter changed: What|Removed |Added Depends on||153634 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153634 [Bug 153634] Page styles: create new "duplicate" copy style -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152775] [Enhancement] Emphasize the entry the mouse pointer is over in the Writer Navigator content tree
https://bugs.documentfoundation.org/show_bug.cgi?id=152775 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | Severity|minor |enhancement CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152775] [Enhancement] Emphasize the entry the mouse pointer is over in the Writer Navigator content tree
https://bugs.documentfoundation.org/show_bug.cgi?id=152775 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #11 from Heiko Tietze --- We discussed this topic in the design meeting (only the bold font weight). First of all it is unclear if the weight changes on hover or on click. Highlighting happens on both events. But more relevant is the missing use case. What problem is resolved by this special handling of tree nodes? Basically it's very clear what node is in focus/hovered. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153914] Realplatinumlife
https://bugs.documentfoundation.org/show_bug.cgi?id=153914 Julien Nabet changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153914] Realplatinumlife
https://bugs.documentfoundation.org/show_bug.cgi?id=153914 Julien Nabet changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED URL|https://realplatinumlife.co | |m/bluechew-subscription-rev | |iew/| CC|markus.mohrhard@googlemail. | |com | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153581] Style family buttons should be a dropdown
https://bugs.documentfoundation.org/show_bug.cgi?id=153581 --- Comment #4 from Heiko Tietze --- (In reply to Jim Raykowski from comment #3) > The styles family toolbar has a feature that allows an entry in the styles > list to be dragged to the family toolbar buttons... Isn't it drag 'n drop onto the styles _list_ adding this as a new style? Similar to New From Selection at the menu button. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153913] FILESAVE / FORMATTING: Failure to save cell background colour of otherwise empty cells
https://bugs.documentfoundation.org/show_bug.cgi?id=153913 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from Stéphane Guillou (stragu) --- Sounds like you are right about this being a duplicate of bug 46738, but please share an original ODS document for us to test, not the resulting XLS file. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131196] Formcontrols: Borders couldn't be set to "no border" through macros
https://bugs.documentfoundation.org/show_bug.cgi?id=131196 --- Comment #9 from Robert Großkopf --- Bug is still the same in LO 7.4.5.1 on OpenSUSE 15.3 64bit rpm Linux. Might be there is missing a refresh - no border won't change any pixel around a control. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561
--- Comment #12 from Mike Kaganski ---
And the already made change of the button [Chapter No.]->[Heading No.], and
tooltip (Chapter number->Heading number) would best be "Entry No." ("Entry
number") for consistency.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153561] Rename "Chapter -> Heading" and "E# -> H#" in Entries tab of Insert Table of Contents, Index, Bibliography dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153561 --- Comment #11 from Mike Kaganski --- I definitely dislike [E#]->[H#] change. The E corresponds to "Entries" tab name. It corresponds to "Insert->Table of Contents and Index->Index Entry" menu. It corresponds to [E] (and the relation is unambiguous and natural: "first entry number, then entry text"). It is neutral. The [E] is used in other types of the index (Alphabetical, Table of Figures, ...), so should not be changed itself. The entry can also be created from other types of paragraphs, which may not be headings, but contain numbering. Overall: indexes consist of entries. Introducing "heading" term here does nothing good, but complicates and confuses things. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153915] Save to PDF fails to preserve animation in an inserted gif
https://bugs.documentfoundation.org/show_bug.cgi?id=153915 Mike Kaganski changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from Mike Kaganski --- As explained in https://ask.libreoffice.org/t/inserted-gif-animation-works-but-not-when-saved-as-pdf/34683/3 : PDF does not support animated GIFs. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 Buovjaga changed: What|Removed |Added Assignee|pradyumnarut...@gmail.com |libreoffice-b...@lists.free ||desktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153915] New: Save to PDF fails to preserve animation in an inserted gif
https://bugs.documentfoundation.org/show_bug.cgi?id=153915 Bug ID: 153915 Summary: Save to PDF fails to preserve animation in an inserted gif Product: LibreOffice Version: 7.2.7.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: drmcnel...@gmail.com Description: After creating a presentation with several gif animations, the slide show is exported to pdf. In the pdf file, the gif images show only the first slide and do not animate, Steps to Reproduce: 1. Create an impress document 2. Insert an animated gif 3. Export to pdf 4. View the pdf, there is no animation Actual Results: No animation Expected Results: animation Reproducible: Always User Profile Reset: No Additional Info: N/A -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153914] Realplatinumlife
https://bugs.documentfoundation.org/show_bug.cgi?id=153914 realplatinumlife changed: What|Removed |Added URL||https://realplatinumlife.co ||m/bluechew-subscription-rev ||iew/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153914] New: Realplatinumlife
https://bugs.documentfoundation.org/show_bug.cgi?id=153914 Bug ID: 153914 Summary: Realplatinumlife Product: cppunit Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: realplatinuml...@gmail.com CC: markus.mohrh...@googlemail.com Realplatinumlife offers you all the latest in trend information regarding health, love, relationship, and men's health. You will get to read all the latest articles on various topics. You will be able to get answers to all your queries related to all these fields. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 62174] Italic Greek symbols (iGreek set) fails if UI Language is changed
https://bugs.documentfoundation.org/show_bug.cgi?id=62174 --- Comment #14 from Valdas --- Bug is still there. ... Version: 7.4.5.1 / LibreOffice Community Build ID: 40(Build:1) CPU threads: 16; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: lt-LT (lt_LT.UTF-8); UI: en-US 7.4.5-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 rutvik_pradyumna changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |pradyumnarut...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153648] fresh past content in dark bacground CALC spreadsheet not invisible in grid
https://bugs.documentfoundation.org/show_bug.cgi?id=153648 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153650] PRINTING - Writer does not print multiple copies on Brother MFC-J1205W
https://bugs.documentfoundation.org/show_bug.cgi?id=153650 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153647] Impress Linked Video or Image Hyperlink Address Not Visible
https://bugs.documentfoundation.org/show_bug.cgi?id=153647 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153626] Unable to sign with existing digital signature, and inconsistent UI for digital signature in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153626 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153638] Add "Ignore Print Area" print option for Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=153638 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153636] "Use level from source chapter" does not work for Graphics and Frames in User-defined index
https://bugs.documentfoundation.org/show_bug.cgi?id=153636 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153634] styles: create new "duplicate" copy style
https://bugs.documentfoundation.org/show_bug.cgi?id=153634 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147982] macOS: Monterey + Ventura 13.1 + LibreOffice 7.3 frequent crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=147982 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153632] LibreOffice 'Window' does not switch docs/sheets
https://bugs.documentfoundation.org/show_bug.cgi?id=153632 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153629] Probably a language issues with the 7.5.0.3 version.
https://bugs.documentfoundation.org/show_bug.cgi?id=153629 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153646] Impress Linked Video Repeat Not Always Saved
https://bugs.documentfoundation.org/show_bug.cgi?id=153646 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147982] macOS: Monterey + Ventura 13.1 + LibreOffice 7.3 frequent crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=147982 --- Comment #49 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150757] Freeze setting for rows and columns not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=150757 --- Comment #3 from QA Administrators --- Dear marco, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140671] Cannot display or edit bad existing formula in table cell
https://bugs.documentfoundation.org/show_bug.cgi?id=140671 --- Comment #11 from QA Administrators --- Dear Ulrich Windl, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90353] FILEOPEN DOC: all frames document - bad / overlapping placement
https://bugs.documentfoundation.org/show_bug.cgi?id=90353 --- Comment #7 from QA Administrators --- Dear Ivan, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90907] FILEOPEN: OOXML TIME field locale always en-US
https://bugs.documentfoundation.org/show_bug.cgi?id=90907 --- Comment #11 from QA Administrators --- Dear Peter Szucs, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90022] FILEOPEN PPT Incorrect text box size
https://bugs.documentfoundation.org/show_bug.cgi?id=90022 --- Comment #9 from QA Administrators --- Dear michaelrmgreen, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88153] FILEOPEN RTF Character set discrepancy with DOC filter
https://bugs.documentfoundation.org/show_bug.cgi?id=88153 --- Comment #8 from QA Administrators --- Dear Urmas, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89573] Can not type non-breaking space into Find & Replace dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=89573 --- Comment #14 from QA Administrators --- Dear Jim Avera, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87739] FILEOPEN : XLSX - formulas linked to other sheets are not refreshed when opening file (hard recalc needed)
https://bugs.documentfoundation.org/show_bug.cgi?id=87739 --- Comment #10 from QA Administrators --- Dear dpierret, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87183] FILEOPEN: No checkbox symbol displayed for empty mail merge field on .doc import
https://bugs.documentfoundation.org/show_bug.cgi?id=87183 --- Comment #11 from QA Administrators --- Dear Timon, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86706] Wrong data being highlighted when selecting a point on scatterplot
https://bugs.documentfoundation.org/show_bug.cgi?id=86706 --- Comment #11 from QA Administrators --- Dear Riccardo Vianello, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81442] EDITING: When doing a Search and Replace All, "Current selection only" becomes deselected.
https://bugs.documentfoundation.org/show_bug.cgi?id=81442 --- Comment #9 from QA Administrators --- Dear Nick, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 62174] Italic Greek symbols (iGreek set) fails if UI Language is changed
https://bugs.documentfoundation.org/show_bug.cgi?id=62174 --- Comment #13 from QA Administrators --- Dear Valdas, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71676] EDITING: Find and replace: replace button does not step to the next search result
https://bugs.documentfoundation.org/show_bug.cgi?id=71676 --- Comment #11 from QA Administrators --- Dear Zoltán Hegedüs, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137107] Unwanted scroll to cursor when deleting header
https://bugs.documentfoundation.org/show_bug.cgi?id=137107 --- Comment #5 from QA Administrators --- Dear Telesto, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 54355] VIEWING: Connector copied from Draw horizontally shifted and disconnected after zoom
https://bugs.documentfoundation.org/show_bug.cgi?id=54355 --- Comment #16 from QA Administrators --- Dear Lekow, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140730] UI, keyboard: Form field properties dialog does not get keyboard focus when it opens
https://bugs.documentfoundation.org/show_bug.cgi?id=140730 --- Comment #2 from QA Administrators --- Dear Tim in 't Veld, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131196] Formcontrols: Borders couldn't be set to "no border" through macros
https://bugs.documentfoundation.org/show_bug.cgi?id=131196 --- Comment #8 from QA Administrators --- Dear Robert Großkopf, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124595] Style does not inherit change
https://bugs.documentfoundation.org/show_bug.cgi?id=124595 --- Comment #4 from QA Administrators --- Dear TorrAB, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124357] Find & Replace in "Current selection only" not available
https://bugs.documentfoundation.org/show_bug.cgi?id=124357 --- Comment #5 from QA Administrators --- Dear Christian Lohmaier, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123659] Conditional formatting does not reflect fontseffect and font names
https://bugs.documentfoundation.org/show_bug.cgi?id=123659 --- Comment #6 from QA Administrators --- Dear thinkedsfoxe, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113888] Setting Original for background image ignores dpi
https://bugs.documentfoundation.org/show_bug.cgi?id=113888 --- Comment #6 from QA Administrators --- Dear Regina Henschel, 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 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153779] FILESAVE Calc takes 4 minutes to save a file
https://bugs.documentfoundation.org/show_bug.cgi?id=153779 --- Comment #4 from christothemagnific...@aussiebroadband.com.au --- I have captured the behaviour with simplescreenrecorder as per below link; https://aussiebroadband-3.wistia.com/projects/l56b2kwuv0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152184] Dark Mode: Application Colors > Color Scheme should automatically follow System Settings > Appearance
https://bugs.documentfoundation.org/show_bug.cgi?id=152184 --- Comment #15 from Sierk Bornemann --- FYI, just for info, maybe it might help to orientate and maybe follow the same way, because it's not bad and has proved its worth: Microsoft Support document: Dark Mode in Word – Word for Microsoft 365, Word for Microsoft 365 for Mac, Word 2021 https://support.microsoft.com/en-us/office/dark-mode-in-word-e17b79a3-762f-4280-a81c-a15a859a693a#ID0EDD=MacOS Incl. what and how to change the settings to change/adjust the defaults. Sidenote (see screenshots and text in the document): for example, among other things: the default page background in dark mode is: a _dark_ page background, not a white one per default. Dark Mode in Word offers a dark color scheme for both the menu controls and the document background. Dark Mode can help to reduce eye strain and also provides a more modern feel to Word. The dark page background does not convey how your document will print, or the default view your collaborators will see when they open it. … Turn on Dark Mode To turn on Dark Mode in the Word, you need to enable Dark Mode for Mac OS. 1. Go to Settings > General 2. In the Appearance options, select Dark [Screenshot] Alternatively, you can select Auto, which will switch between Light and Dark modes based on your specified Night Shift schedule in MacOS. [Screenshot] 3. To turn off Dark Mode, go to Word > Preferences > General > Personalize and select Turn off Dark Mode [Screenshot] inclusive this section: Personalize ● Turn off Dark Mode ○ Dark mode has a dark page color ○ Dark mode has a white page color … Set the page background color Once Dark Mode has been turned on, you can toggle between the dark and light page background colors. 1. In the ribbon, go to the View tab. 2. Select Switch Modes to change the page background color. Word will remember the state of this toggle for future Dark Mode sessions. [Screenshot] Disable the dark page background You can disable the dark page background in Dark Mode and keep the page light. Go to Word > Preferences > General > Personalize. Select Dark Mode has a white page color. [Screenshot] Check the appearance Regardless of your Dark Mode settings, your document will print with the light mode page color. Also, your Dark Mode settings do not impact your collaborators, and Word will respect individual view preferences. To preview your document for printing and sharing, use the Switch Modes button to change the page background to light. … -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152324] Document title jumps from Untitled 1 to Untitled 3 when text is is copied
https://bugs.documentfoundation.org/show_bug.cgi?id=152324 --- Comment #9 from darkwolf...@rocketmail.com --- Any updates on this? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 32249] Make it easier to edit text in imported PDFs
https://bugs.documentfoundation.org/show_bug.cgi?id=32249
--- Comment #40 from wtambell...@rws.com ---
Splitting ("divide and conquer") is a good idea Eyal and I see you did it so
congrats.
Tks
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137704] Enable Edit > Index when cursor is not on a field
https://bugs.documentfoundation.org/show_bug.cgi?id=137704
sdc.bla...@youmail.dk changed:
What|Removed |Added
CC||sdc.bla...@youmail.dk
--- Comment #3 from sdc.bla...@youmail.dk ---
Halfway solution:
Use Tools - Customize to add "Go to Next Index Mark" and "Go to Previous Index
Mark" (search on "Index" in the Customize Dialog) to {toolbar, context menu,
shortcut key}, according to preference. This will move the cursor from an
arbitrary position to an index entry, but you still need to open Index Entry.
(Could make a custom toolbar with these two commands, plus
.uno:IndexEntryDialog, which opens the Edit Entry dialog, when the cursor is on
an Index Entry (there are two "Insert Entry" options). You still have to close
the Edit dialog each time, but it might make life a little easier.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153548] F4 Absolute Cell Referencing not working in specific circumstances
https://bugs.documentfoundation.org/show_bug.cgi?id=153548 Justin L changed: What|Removed |Added Keywords|regression | Regression By|Justin Luth | Version|7.1.0.0.alpha0+ |5.3 all versions --- Comment #4 from Justin L --- Ignoring the bibisect result - is OP reporting something that he noted that worked in the past, but no longer works anymore? I don't think so. I tested in LO 7.0, and if I start from sheet 2, and try to build an equation from sheet 1, then F4 never works. So I think the general problem has pre-dated my patch. In fact, following these procedures, prior to my patch there WASN'T any ability to build a formula. 1.) Open F4 Test.ods in LO 7.0 and place the cursor in Sheet 1.B2 2.) Press "=" to start a new formula, click on Sheet 2 cell A1 -observe - nothing happens in 7.0, still just an equal sign, so nothing to use F4 on. 3.) Cancel the current build. place cursor in D2 4.) Press "=" to start a new formula, click on Sheet 2 cell A1 -observe - "=$Sheet2.A1", but pressing F4 does nothing. After my patch(7.1), doing steps 1 and 2 now looks like the result from 3 and 4. -observe - "=$Sheet2.A1", but pressing F4 does nothing. The ability to press F4 started after 4.4 and before 5.3 - and I don't have the ability to bibisect in that range. Almost certainly it has never worked. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153885] UI : LibreOffice VCL GTK Backend on Linux has menus cutoff
https://bugs.documentfoundation.org/show_bug.cgi?id=153885 --- Comment #5 from rushing27al...@gmail.com --- It's Wayland. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153913] FILESAVE / FORMATTING: Failure to save cell background colour of otherwise empty cells
https://bugs.documentfoundation.org/show_bug.cgi?id=153913 --- Comment #1 from avoga...@gmail.com --- Created attachment 185686 --> https://bugs.documentfoundation.org/attachment.cgi?id=185686=edit Garden Spreadsheet -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153913] New: FILESAVE / FORMATTING: Failure to save cell background colour of otherwise empty cells
https://bugs.documentfoundation.org/show_bug.cgi?id=153913 Bug ID: 153913 Summary: FILESAVE / FORMATTING: Failure to save cell background colour of otherwise empty cells Product: LibreOffice Version: 4.3.0.4 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: avoga...@gmail.com Description: Repeatedly encountered an issue with the background cell colour not being saved in a .xls file when using Calc. I had been using LibreOffice 7.4.03 and have upgraded to 7.4.5.1 in the hope of fixing this issue but this did not help. The spreadsheet I've been working on saves the background colour of some cells, but fails to save the background colour for other cells. I'm not entirely sure but I think the cells where it isn't saving the background colour are ones on lines where I inserted rows. However, this is not consistent behaviour if true; error seems to mostly affect sheet 2 and 3 of the file. This appears to be less of a problem when saving the file as .xlsx but sometimes still causes the error. Reliable workaround: If I write text in the cells with a background colour, the text and the background colour is saved. Error persists in safemode. Possible duplicate of Bug 46738. Steps to Reproduce: 1) Set background colours for cells. 2) Save using the keyboard shortcut "Ctrl+s" or by clicking the save icon. 3) The file appears to have been saved (no longer shows the "unsaved" symbol). 4) Close the file. Actual Results: Reopen the file and the cells have reverted to no-background colour. Expected Results: Reopen the file and the cells retain formatting. Reproducible: Sometimes User Profile Reset: Yes Additional Info: Version: 7.4.5.1 (x64) / LibreOffice Community Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153905] PDF files created with LibO print incorrectly to some printers
https://bugs.documentfoundation.org/show_bug.cgi?id=153905 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org --- Comment #4 from Stéphane Guillou (stragu) --- Latest version of the font is available here: https://github.com/adobe-fonts/source-sans/releases/tag/3.046R Looking at the attached PDF, you used: - SourceSansPro-Light - SourceSans3-Bold - SourceSans3-Regular - SourceSans3-It ...all of them reported as "Type 1" by my PDF reader. Which format did you use to install the fonts? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 50564] PDF: can't select text in LO alert (specifically PDF export problem)
https://bugs.documentfoundation.org/show_bug.cgi?id=50564 --- Comment #12 from skierpage --- Still a bug in LibreOffice Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Flatpak Calc: threaded The same thing happens if I open the attached SVG, which opens it in LO Draw, and export it as PDF/A-1b (now the lowest PDF/A archive version). So as you'd expect the bug is not specific to Writer but lies in the toolkit implementation of this and probably other alert dialogs, for at least the Linux Flatpak. So the Bugzilla component should either "graphics stack" or "UI", I chose the latter. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153904] [ENHANCEMENT] Allow for inline (= run-in) paragraph styles
https://bugs.documentfoundation.org/show_bug.cgi?id=153904 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #1 from Regina Henschel --- Created attachment 185685 --> https://bugs.documentfoundation.org/attachment.cgi?id=185685=edit Inline heading by CSS in HTML Do you look for something like display:inline as known from CSS in HTML? (See attachment) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 50564] PDF: can't select text in LO alert (specifically PDF export problem)
https://bugs.documentfoundation.org/show_bug.cgi?id=50564 --- Comment #11 from skierpage --- Created attachment 185684 --> https://bugs.documentfoundation.org/attachment.cgi?id=185684=edit open this (in Draw), export as PDF/A-1b, get a warning dialog whose text you can't select -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153912] New: software changes and adds bookmarks
https://bugs.documentfoundation.org/show_bug.cgi?id=153912 Bug ID: 153912 Summary: software changes and adds bookmarks Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: conradcaball...@gmail.com I am creating a document with multiple bookmarks with names such as "John 1", "John 2", "John 3", etc. After awhile when going through my bookmark list I note that my bookmark names have changed, not all but some. The changes are of a nature as "John 1" being changed to "John 11" and "John 2" to "John 22". Sometimes I note not changes but additions to my book marks such as after "John 1" there will be "John 11" and even a "John 111" after that. I am working with Mac OS. I have never had the opportunity or need to use bookmarks before and am wondering if I am doing something wrong. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153895] No page preview in Print dialog (kf5 / qt5)
https://bugs.documentfoundation.org/show_bug.cgi?id=153895 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected Component|Printing and PDF export |UI Regression By||Michael Weghorn CC||m.wegh...@posteo.de See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2073 --- Comment #4 from Stéphane Guillou (stragu) --- Bisected with linux-64-7.5 repo to first bad commit 3715a9f25ed4675fba49ef7df7036c1b2ec853d5 which points to core commit: commit 7a6cbff566122113b753fd31e7c73be8725f48f2 author Michael WeghornTue Jan 31 16:08:53 2023 +0100 committer Michael Stahl Thu Feb 02 11:27:30 2023 + treebaac257d57c51c86ea36cbb61ceaa13aa9450897 parent 52216e9aad59c6c43b47f3d29d73bde9d11280d3 tdf#152073 qt: Draw background when drawing frame For native drawing of a frame (border), use the window background color as default color. [...] Change-Id: I08e6d05d0fc3d0e54952a65cd28dee92615df0a3 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146419 Michael, can you please have a look? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153885] UI : LibreOffice VCL GTK Backend on Linux has menus cutoff
https://bugs.documentfoundation.org/show_bug.cgi?id=153885 --- Comment #4 from Caolán McNamara --- is it wayland, is it x11? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103309] [META] Print dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103309 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153895 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153895 [Bug 153895] No page preview in Print dialog (kf5 / qt5) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153906] PRINTING/CALC: Not printing selected sheets, preview and print is empty
https://bugs.documentfoundation.org/show_bug.cgi?id=153906 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3895 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153895] No page preview in Print dialog (kf5 / qt5)
https://bugs.documentfoundation.org/show_bug.cgi?id=153895 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||103309 CC||stephane.guillou@libreoffic ||e.org Keywords||bibisectRequest, regression Status|UNCONFIRMED |NEW Summary|No page preview in Print|No page preview in Print |dialog |dialog (kf5 / qt5) Ever confirmed|0 |1 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3906 --- Comment #3 from Stéphane Guillou (stragu) --- Can't repro in with gtk or gen VCLs, but I can with kf5: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Same with qt5 (qfont+xcb) and kf5 (cairo+wayland). Regression, as I can't repro in: Version: 7.4.5.1 / LibreOffice Community Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103309 [Bug 103309] [META] Print dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153911] New: Warning when opening files with other files already open
https://bugs.documentfoundation.org/show_bug.cgi?id=153911 Bug ID: 153911 Summary: Warning when opening files with other files already open Product: LibreOffice Version: 7.5.0.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nadie.nada.nu...@mail.com Every time I try to open a Word or Excel file from, say, an email, when I already have another office file open, LibreOffice does nothing until I close the other documents. Only then, it does launch the file, but first, it presents me with a message offering to “recover the state of the files” I was working on before the crash. But there was no crash at all, I just had some documents open and then closed them. I am forced to "Discard All", then say I'm sure, then sometimes confirm again and sometimes not (IIRC) before the file I wanted to open actually opens. (Yes, I have associated LO with MS Office files. People send me MS Office files through email. But the files I am usually working on are native LO Calc files.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153910] New: textbox in Writer does not resolve style:writing-mode="page" to the writing mode of the page
https://bugs.documentfoundation.org/show_bug.cgi?id=153910 Bug ID: 153910 Summary: textbox in Writer does not resolve style:writing-mode="page" to the writing mode of the page Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: x86-64 (AMD64) URL: https://docs.oasis-open.org/office/OpenDocument/v1.3/o s/part3-schema/OpenDocument-v1.3-os-part3-schema.html# __RefHeading__1420264_253892949 OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 185683 --> https://bugs.documentfoundation.org/attachment.cgi?id=185683=edit Page style with vertical writing mode The page style in the attached document is set to "Right-to-Left (vertical)". That is the writing mode suitable for texts in East Asian scripts. All places relevant for the text box are set to style:writing-mode="page" in the file markup. Open the file. Error: The text in the text box is horizontal. The text should be vertical, see the linked part of the ODF spec. The API shows TextWritingMode="LR_TB" and WritingMode="0", corresponding to the wrong rendering. A text box is able to render vertical text. There even exists a predefined text box for vertical text. So the problem is not the rendering itself, but the fact that vertical rendering is not used. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104444] [META] DOCX (OOXML) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=10 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153891 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153891 [Bug 153891] Crash in: writerfilter::dmapper::DomainMapperTableHandler::endTable(unsigned int, bool) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148747] Bad use of the date in formulas
https://bugs.documentfoundation.org/show_bug.cgi?id=148747 --- Comment #33 from JPT --- (In reply to m.a.riosv from comment #32) > > Please, with what date format in Statement.A:A and what string in > calculation.C1 works for you?. On the original platform statement is "D.M.". In the calculation in cell C1 (only "") works in both versions. In the calculation in cells D1:O1, "MM." works in version 7.1.8.1 and below. In version 7.4.5.1 (probably from version 7.2.6 and above), ".M." works on that same statement. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153827] Crash à l'ouverture du programme
https://bugs.documentfoundation.org/show_bug.cgi?id=153827 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- Palongo, are you using the 32-bit or 64-bit version? Some crashes were fixed for 7.5 and I think your issue might be resolved with version 7.5.1: https://www.libreoffice.org/download/download-libreoffice/?version=7.5.1 Please test it and let us know! -- You are receiving this mail because: You are the assignee for the bug.
