[Libreoffice-bugs] [Bug 113388] Support for Client Side Windows Decorations in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=113388 --- Comment #23 from Heiko Tietze --- (In reply to third='beedell', first='roke', second='julian lockhart' from comment #22) > GitLab provides reactions for issues, but Bugzilla doesn't. Up and down voting... would be nice. Btw, you can tag comment as off-topic. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124093] EDITING Selecting filtered cells with hidden rows in between causes a bug in filter reset.
https://bugs.documentfoundation.org/show_bug.cgi?id=124093 --- Comment #19 from Heiko Tietze --- (In reply to ady from comment #18) > (In reply to Heiko Tietze from comment #17) > > The filter cannot be applied to a selection, it always expands to the full > > range. > > That's incorrect. Both the Standard Filter and the AutoFilter can be applied > to a _selection_ that does not include every-and-all adjacent cells. You are right, the selection is not extended into leading cells. But if you select something like A1:A4 the trailing A5 will be added. Why not extending the selection in both directions? Is there a good use case to sort/filter data only partially? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155939] LibreOffice-7.5.4.2 Writer hangs when changing language of text
https://bugs.documentfoundation.org/show_bug.cgi?id=155939 Stéphane Guillou (stragu) changed: What|Removed |Added CC||doug...@proton.me --- Comment #10 from Stéphane Guillou (stragu) --- *** Bug 156185 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 156185] Freeze when setting spell check language for all text (and text contains image)
https://bugs.documentfoundation.org/show_bug.cgi?id=156185 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #7 from Stéphane Guillou (stragu) --- I think this is the same as bug 155939, already fixed in 7.5.5. Can you please try the 7.5 pre-release to confirm it is fixed? https://www.libreoffice.org/download/download-libreoffice/?type=deb-x86_64&version=7.5.5&lang=en-US Thank you! *** This bug has been marked as a duplicate of bug 155939 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155790] Forms - Tab stop: With Tab Order = 0 tab stop follows order of fields in form navigator and couldn't be sorted
https://bugs.documentfoundation.org/show_bug.cgi?id=155790 --- Comment #3 from Robert Großkopf --- (In reply to Dieter from comment #2) > Couldn't find settings for "Tab Order" in control properties. > Order follows also order of drawing objects in navigator. So perhaps if it > would be possible to sort the, this would also solve the problem within form > navigator Open the control properties. Choose tab "General". There will be entries for Tabstop → Yes/No Tab Order → Integer But this won't solve the problem, because direct jumping to a control with Alt + Character will only work when tabstop is set to 'no'. Bug 87069 is only missing sorting in form navigator as a "nice to have", but bug 155790 describes the problems of moving through a form with tabulator while input data. And this depends on the sorting in the form navigator. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95150] Border of tablecontrol doesn't show color
https://bugs.documentfoundation.org/show_bug.cgi?id=95150 --- Comment #13 from Robert Großkopf --- Bug still exists with LO 7.5.5.1 on OpenSUSE 15.4 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143137] FORMNAVIGATION: When switching from Form to "Data source as Table" last changes won't be saved
https://bugs.documentfoundation.org/show_bug.cgi?id=143137 --- Comment #4 from Robert Großkopf --- Bug still exists with LO 7.5.5.1 on OpenSUSE 15.4 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155740] Support distinction rather than override of conflicting subdocument styles
https://bugs.documentfoundation.org/show_bug.cgi?id=155740 --- Comment #15 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #14) > Mike, I think you might may be making an implicit assumption that the author > of the master document has written the subdocuments with the prior intent to > place them in a master document. Exactly; I even stated that explicitly: (from comment #12) > 1. Master documents is an advanced feature, not *designed* as something to > be used without a bit of learning. A proposal designed to enable use like "I > suddenly decided to use this feature with a set of documents not designed > with master documents in mind" is not a proper scenario here. I strongly believe that what you explain below is not a proper use of master documents feature: > I'm thinking in this issue more about the > user who wants to integrate an independently-authored document, which would > have stood on its own, into the master document. > > Here's another use case, exemplifying this perhaps more strongly: I'm > working on some legal brief, or report, to which I want to attach documents > somebody else has written (and luckily for me, they are available as (maybe > read-only) ODT's or DOCX's). Each of those documents has its styles defined > via Text Body, Normal, Heading 1,2,3 etc. and so on. And - they might be > different. When I use these as subdocuments - I want all of their styles > _preserved_. Any LibreOffice *document* is a *source*, i.e. an artifact allowing to *author* the content. The *authoring* is the primary goal of existence of all the office document formats, the reason why we don't use raster bitmaps for our documents. (I exaggerate, just to emphasize my point.) Indeed, people might want to store these artifacts, instead of dumping in the end after creation of a hard copy. But this is still to be able to reuse, change, or inspect the structure - if not these reasons, PDF would be a better choice for storing after the document is finished. But specifically for the "legal brief", the insertion of *other document sources* into your document is *incorrect*: these documents' structures do *not* contribute your document's structure; you are not expected to edit them, but these other documents are just replicas of some state of those documents in some specified moment in time. And while I want to stress, that your own "legal brief" example is, IMO, *strong* case where master documents should *not* be used (and, e.g., scans/PDFs of those documents should be inserted), I also say that it would hold for *any* case when you collect multiple documents into one, when the sources were *not* created with master document / consistent style in mind, and you want to keep the heterogenous styling of sources in the end result. I can see a Paste Special (*not* master document!), which would convert source style names to unique names on paste, or convert everything to DF. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156024] .docx containing Rich Text Content Control Remains interactive after converting to PDF via CLI
https://bugs.documentfoundation.org/show_bug.cgi?id=156024 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 155944] Irrelevant page positioning when maximizing a tiled window
https://bugs.documentfoundation.org/show_bug.cgi?id=155944 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 156017] Printer settings not used by LibreOffice (display, printing or exporting pdf)
https://bugs.documentfoundation.org/show_bug.cgi?id=156017 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 156019] Headings are illegible when printing docx
https://bugs.documentfoundation.org/show_bug.cgi?id=156019 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 156179] LibreOffice crashes repeatable just by fast scrolling through a writer document
https://bugs.documentfoundation.org/show_bug.cgi?id=156179 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155870] Format Word 2003 XML not supported
https://bugs.documentfoundation.org/show_bug.cgi?id=155870 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 155983] Strange black squares appear when loading PDFs with LibreOffice Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=155983 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 155980] select a control close to the vertical scrollbar, it is not select
https://bugs.documentfoundation.org/show_bug.cgi?id=155980 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 156179] LibreOffice crashes repeatable just by fast scrolling through a writer document
https://bugs.documentfoundation.org/show_bug.cgi?id=156179 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152414] Firefox is open - LibreOffice installed - Firefox breadcrumbs do not work anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=152414 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152414] Firefox is open - LibreOffice installed - Firefox breadcrumbs do not work anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=152414 --- Comment #3 from QA Administrators --- Dear stefaneink, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146696] IMPRESS PRINTING: Only part of slide is rendered when trying to print from Screen 16:10 format
https://bugs.documentfoundation.org/show_bug.cgi?id=146696 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143879] Incorrect data labels on scatter plot in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=143879 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146696] IMPRESS PRINTING: Only part of slide is rendered when trying to print from Screen 16:10 format
https://bugs.documentfoundation.org/show_bug.cgi?id=146696 --- Comment #4 from QA Administrators --- Dear Ian, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143879] Incorrect data labels on scatter plot in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=143879 --- Comment #5 from QA Administrators --- Dear rheath78+bug, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107923] [META] Zoom issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107923 Bug 107923 depends on bug 139470, which changed state. Bug 139470 Summary: Zooming with touchpad is very hard https://bugs.documentfoundation.org/show_bug.cgi?id=139470 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139470] Zooming with touchpad is very hard
https://bugs.documentfoundation.org/show_bug.cgi?id=139470 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139470] Zooming with touchpad is very hard
https://bugs.documentfoundation.org/show_bug.cgi?id=139470 --- Comment #5 from QA Administrators --- Dear Arnab, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152915] unwanted upper by lower case replacement
https://bugs.documentfoundation.org/show_bug.cgi?id=152915 --- Comment #2 from QA Administrators --- Dear gmildner, 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 37591] Writer incorrectly saves property of list
https://bugs.documentfoundation.org/show_bug.cgi?id=37591 --- Comment #15 from QA Administrators --- Dear sasha.libreoffice, 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 152894] random crashes in Writer (Windows)
https://bugs.documentfoundation.org/show_bug.cgi?id=152894 --- Comment #2 from QA Administrators --- Dear Bobby, 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 126965] [EMF] Drawing with underlined text looks fail
https://bugs.documentfoundation.org/show_bug.cgi?id=126965 --- Comment #6 from QA Administrators --- Dear faludiz, 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 122897] FILESAVE XLSX Spreadsheet with Database Range is incorrect when the document is opened in Excel
https://bugs.documentfoundation.org/show_bug.cgi?id=122897 --- Comment #14 from QA Administrators --- Dear NISZ LibreOffice Team, 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 107843] EDITING: No cropping options in Writer if the image is pasted from Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=107843 --- Comment #11 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 156185] Freeze when setting spell check language for all text (and text contains image)
https://bugs.documentfoundation.org/show_bug.cgi?id=156185 --- Comment #6 from doug...@proton.me --- It's already the latest from AMD. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 44763] Cell styles with localized names, in Pivot Table, replaced with en-US named styles, if pivot changed in en-US UI
https://bugs.documentfoundation.org/show_bug.cgi?id=44763 --- Comment #30 from kelseyradley --- Thank you for sharing your detailed testing and observations regarding the pivot table styles in LibreOffice. It's great to hear that the issue seems to be resolved in the version you tested (Version: 7.1.1.2 / LibreOffice Community). https://rainbowfriendschapter2.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 44597] FORMATTING: Margin notes (similar to footnotes, but vertically linked to content) should be enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=44597 --- Comment #21 from kelseyradley --- It's great that the solution worked for you in the latest stable version of LO5.2.0. Thank you for sharing the steps you followed to achieve the desired result. https://pgeoutagemap.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 79357] Trend line can't be added by the Insert menu
https://bugs.documentfoundation.org/show_bug.cgi?id=79357 --- Comment #20 from kelseyradley --- It's great that the solution worked for you in the latest stable version of LO5.2.0. Thank you for sharing the steps you followed to achieve the desired result. https://bitlife2.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155177] Writer: Widow/orphan behaviour not reliably predictable
https://bugs.documentfoundation.org/show_bug.cgi?id=155177 --- Comment #4 from kostu...@gmail.com --- Before deciding anything further I am just trying to understand how the ticket/bug process and Foundation work, as I am not sure how to interpret certain terminologies. Does the term "Not Assigned" above mean what it states and that no one is actively investigating this particular bug at this time? I am trying every new version as it comes out with no changes in the noted behavior observed as of yet. And the behavior seemed to continue even after I tried uninstalling the latest and installing an earlier version of Libre that appeared to work just fine previously. So it might be that some part(s) of the application is not being totally removed when uninstalling and reinstalling. Whether related or not, the behavior started around the same time as when Libre temporary files started appearing on my desktop by the ton when trying to work with the application, commonly then staying there the rest of the day. (I did check the path for such files and it is what it is supposed to be according to Libre documentation.) Some type of virus, conflicting program, or hardware issue with my computer is always possible (Windows 10 Pro), though I am not convinced of that at this time. Any update at all would be appreciated, as I have been unable to finish revising a book project due to these basic issues and really need to get back to that soon one way or another. Thank you very much. I really appreciate it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156185] Freeze when setting spell check language for all text (and text contains image)
https://bugs.documentfoundation.org/show_bug.cgi?id=156185 --- Comment #5 from m.a.riosv --- I can't reprodauce Version: 7.5.5.1 (X86_64) / LibreOffice Community Build ID: 2c5e46c1980ec5241359fd65d751dc518205e7af CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded or with Skia/Vulkan; You can try updating your graphics card drivers directly from the vendor. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156185] Freeze when setting spell check language for all text (and text contains image)
https://bugs.documentfoundation.org/show_bug.cgi?id=156185 doug...@proton.me 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 156185] Freeze when setting spell check language for all text (and text contains image)
https://bugs.documentfoundation.org/show_bug.cgi?id=156185 --- Comment #4 from doug...@proton.me --- Created attachment 188241 --> https://bugs.documentfoundation.org/attachment.cgi?id=188241&action=edit Sample odt file Adding requested sample file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156185] Freeze when setting spell check language for all text (and text contains image)
https://bugs.documentfoundation.org/show_bug.cgi?id=156185 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #3 from m.a.riosv --- Please can you attach a sample file showing the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156183] DATA > TEXT TO COLUMNS : trashes cells on the right to the one being converted
https://bugs.documentfoundation.org/show_bug.cgi?id=156183 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- I can't reproduce with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d74344f6cae0cf1c12f08249c8f49be1374fb98f CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en- Calc: CL threaded Version: 7.5.5.1 (X86_64) / LibreOffice Community Build ID: 2c5e46c1980ec5241359fd65d751dc518205e7af CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156185] Freeze when setting spell check language for all text (and text contains image)
https://bugs.documentfoundation.org/show_bug.cgi?id=156185 --- Comment #2 from doug...@proton.me --- I have tested both English and Portuguese, and also tested the other "for paragraph" and "for selection" options - they work. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156176] After a Reboot LibreOffice 7.5.5.1 deletes new extensions!
https://bugs.documentfoundation.org/show_bug.cgi?id=156176 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- It's a strange situation, looks like the system is recovering those files or folders, to a previous state. You can try before reboot, copy the folder of LibreOffice profile. https://wiki.documentfoundation.org/UserProfile or doing it with Menu/Help/Restart in Safe Mode. Also, you can test with 7.6.beta, which is installed in parallel, not overwritten the 7.5 version. https://qa.blog.documentfoundation.org/2023/06/14/libreoffice-7-6-beta1-is-available-for-testing/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156185] Freeze when setting spell check language for all text (and text contains image)
https://bugs.documentfoundation.org/show_bug.cgi?id=156185 doug...@proton.me changed: What|Removed |Added Summary|Writer freezes when setting |Freeze when setting spell |spell check language for|check language for all text |all text (and text contains |(and text contains image) |image) | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156185] Writer freezes when setting spell check language for all text (and text contains image)
https://bugs.documentfoundation.org/show_bug.cgi?id=156185 --- Comment #1 from doug...@proton.me --- I've tested with a different image file, and the result is the same - it freezes. You can use any image to reproduce this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156185] New: Writer freezes when setting spell check language for all text (and text contains image)
https://bugs.documentfoundation.org/show_bug.cgi?id=156185 Bug ID: 156185 Summary: Writer freezes when setting spell check language for all text (and text contains image) Product: LibreOffice Version: 7.5.4.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Linguistic Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: doug...@proton.me CC: so...@libreoffice.org Description: When I try to set a language for all text, LibreOffice Writer freezes and must be force-closed. The file currently open contains an image in it. The problem does not occur if the image is removed. Steps to Reproduce: 1. I have English (US) and Portuguese (Brazil) languages available, with English being default. 2. Automatic spell checking is on. 3. Have an image inserted in the document. 4. Tools > Language > For All Text > choose a language Actual Results: The editor freezes and must be force-closed. Expected Results: Should not freeze/crash. Reproducible: Always User Profile Reset: Yes Additional Info: Windows 11 22H2 Build 22621.1848 Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125504] Notebookbar Tabbed / Compact Tabbed UI ParaStyle-controls/FontName-controls stop applying after a print preview
https://bugs.documentfoundation.org/show_bug.cgi?id=125504 Justin L changed: What|Removed |Added Summary|Notebookbar Tabbed /|Notebookbar Tabbed / |Compact Tabbed UI style |Compact Tabbed UI |controls stop applying |ParaStyle-controls/FontName |styles after a print|-controls stop applying |preview |after a print preview See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||4884 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156179] LibreOffice crashes repeatable just by fast scrolling through a writer document
https://bugs.documentfoundation.org/show_bug.cgi?id=156179 --- Comment #2 from Ingo Koglin --- Hello Stéphane The other reported bugs under the number 149527 sound very similar to what I Encounter. I checked the setting of Skia. The hardware supported rendering was activated from the installation (I haven’t touched the setting before). I’ve activated the software mode now for further tests. But I couldn’t reproduce the error even before. But I have a suspicion, what could have triggered the crash. Since I’m writing on a Windows Tablet (CSL Panther Tab HD) I tend to use a Software Keyboard/Mouse-switch that works over LAN called Barrier https://sourceforge.net/projects/barrier.mirror/ (v 2.3.4-release c43597c2). When the crashes happened I used the mousewheel over Barrier to scroll through my document. After closing the program (to work undisturbed on my main PC) I didn’t encountered the crashes anylonger on my Tablet. I can provide you with a System Information file if necessary. Best regards Ingo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155673] Changing the style of outer borders, also draws some inner borders
https://bugs.documentfoundation.org/show_bug.cgi?id=155673 --- Comment #9 from Alhay94 --- Created attachment 188240 --> https://bugs.documentfoundation.org/attachment.cgi?id=188240&action=edit test in version 7.5.4.2 Normally, changing the style of borders, must change only the borders already drawned ? Is it not true ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155902] writer crashes regularly after updating to dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155902 --- Comment #12 from Stéphane Guillou (stragu) --- No problem. For you, the log we are after is likely in: C:\Users\J.Hamilton\AppData\Roaming\libreoffice\4\user\cache\skia.log -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 69183] EDITING: insert a table with ctrl-v changes the formating of the table and the following Paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=69183 Matt K changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |matt...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141058] PPTX to PDF: Images from deeper layers (covered by other objects) aren't omitted, and their decorative flag is ignored.
https://bugs.documentfoundation.org/show_bug.cgi?id=141058 --- Comment #7 from Commit Notification --- Michael Stahl committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/2f75278ff1f437228d39cc3f71d6fa98d58fc1c1 tdf#141058 oox,sw: OOXML import/export of decorative on shapes It will be available in 7.6.0.0.beta2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141058] PPTX to PDF: Images from deeper layers (covered by other objects) aren't omitted, and their decorative flag is ignored.
https://bugs.documentfoundation.org/show_bug.cgi?id=141058 Commit Notification changed: What|Removed |Added Whiteboard|target:24.2.0 |target:24.2.0 ||target:7.6.0.0.beta2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118559] Calc: Bug with copy+paste for joined cells that breaks neighbor cells into pieces (and breaks Undo/Redo in LO 5.x)
https://bugs.documentfoundation.org/show_bug.cgi?id=118559 --- Comment #26 from ady --- Following comment 19 on MS Windows using attachment 143325 from comment 1, for me this is repro up to LO 7.0, and solved since LO 7.1. I have not tested under other OSes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 63356] EDITING: Unable to change tabs in multiple paragraphs when paragraphs have different indent
https://bugs.documentfoundation.org/show_bug.cgi?id=63356 --- Comment #18 from Peter Nowee --- Bug still present. I can still reproduce it using the sample documents in attachment 84948 and attachment 116501. Version: 7.4.5.1 / LibreOffice Community Build ID: 40(Build:1) CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Debian package version: 4:7.4.5-3 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155740] Support distinction rather than override of conflicting subdocument styles
https://bugs.documentfoundation.org/show_bug.cgi?id=155740 --- Comment #14 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #11) > 2. ... Even in your > example, there's no way every part would need *every* bit different; and > most likely, it would need *most* (but a couple of details) consistent. > Fonts, their sizes, spacing, headings, ... In this case, implementing your > proposal breaks the fundamental principle of the master documents (which you > refuse), which is - ability to set the style centrally, and have all the > sub-documents look consistent. Someone making the final preparations, and > deciding to change something, would have to edit individual documents on > each and every thing they need to change globally. But that's only if they explicitly chose to keep all of the subdocument styles, i.e. only if they wanted this to happen. And - they may well want this to happen! See further about this below. > Direct formatting, or separate styles per chapter, which is something that > the creator would be perfectly aware of, is the solution to your example. Direct formatting is only even a solution for something which happens once. Formatting in a subdocument happens many times; I gave a page style as an example - maybe it's a base style of several page styles? Or maybe what I want to keep is one of the character or paragraph styles etc. Mike, I think you might may be making an implicit assumption that the author of the master document has written the subdocuments with the prior intent to place them in a master document. I'm thinking in this issue more about the user who wants to integrate an independently-authored document, which would have stood on its own, into the master document. Here's another use case, exemplifying this perhaps more strongly: I'm working on some legal brief, or report, to which I want to attach documents somebody else has written (and luckily for me, they are available as (maybe read-only) ODT's or DOCX's). Each of those documents has its styles defined via Text Body, Normal, Heading 1,2,3 etc. and so on. And - they might be different. When I use these as subdocuments - I want all of their styles _preserved_. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155740] Support distinction rather than override of conflicting subdocument styles
https://bugs.documentfoundation.org/show_bug.cgi?id=155740 --- Comment #13 from Eyal Rozenberg --- (In reply to David from comment #10) > Is there a reason why modifying the settings for the section > in the master document to which the subdocument is linked wouldn't work as > designed to set the background for that section to match the linked > document? Given your example and my understanding of it, I fail to > comprehend the problem. It would work. But you will need to do this for _every_ setting of _every_ style of _every_ subdocument which is overridden by the master document. And you should not have to. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108342] BASE, Editing: list field in table grid shows status row changed on opening form when it's first column
https://bugs.documentfoundation.org/show_bug.cgi?id=108342 --- Comment #15 from Gerhard Weydt --- Bug is still present in Version: 7.6.0.0.beta1 (X86_64) / LibreOffice Community Build ID: be55b15d98c5f059483845a183fcb5ea8023d27c CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130697] Print preview of SVG images rendered pixelated (macOS-only) and crash with LO from master branch
https://bugs.documentfoundation.org/show_bug.cgi?id=130697 --- Comment #11 from Alec K --- This bug is no longer reproducible in Version: 7.5.4.2 (AARCH64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 10; OS: Mac OS X 13.4; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded The image render in print preview has better quality than both provided screenshots. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155902] writer crashes regularly after updating to dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155902 --- Comment #11 from jim hamilton --- The instructions are a bit beyond me.. Activating Skia, rebooting LO and reviewing the log as best I understand, I get C:\Users\J.Hamilton\.cache\youtube-dl So, I don't see it My graphics card is a NVIDIA GeForce GTX 745 [Display adapter] -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156184] Bullets created when saving or copying/pasting
https://bugs.documentfoundation.org/show_bug.cgi?id=156184 --- Comment #2 from Stephen Zemlicka --- Created attachment 188239 --> https://bugs.documentfoundation.org/attachment.cgi?id=188239&action=edit This is an example of the problem This is a result of opening the original template file and Save As new file. Bullets are not visible in Impress but are visible in Powerpoint. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156184] Bullets created when saving or copying/pasting
https://bugs.documentfoundation.org/show_bug.cgi?id=156184 Stephen Zemlicka changed: What|Removed |Added CC||stevezemli...@gmail.com --- Comment #1 from Stephen Zemlicka --- Created attachment 188238 --> https://bugs.documentfoundation.org/attachment.cgi?id=188238&action=edit Original Template File In this example, which I believe was created with a much older version of Impress, no bullets are present when opening from either Impress or Powerpoint. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156184] New: Bullets created when saving or copying/pasting
https://bugs.documentfoundation.org/show_bug.cgi?id=156184 Bug ID: 156184 Summary: Bullets created when saving or copying/pasting Product: LibreOffice Version: 7.5.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stevezemli...@gmail.com Description: When saving a PPTX file, bullets are created that don't appear in Impress but do appear in Powerpoint. In my case, I have PPTX files I use as templates. When opened and saved, hidden bullets are created by Impress. They do not show up in Impress but when opened in Powerpoint, they do appear. This also occurs if the slides are copied to a new presentation and saved using Impress. Steps to Reproduce: 1. Open Example template. 2. Save As another file 3. Open new file in Powerpoint Actual Results: Bullets are created for every line in slides 2 and beyond. Bullets do not appear in Impress but do appear in Powerpoint and need to be manually removed. Expected Results: No visible bullets should show in Powerpoint if they are not in Impress. Minimally, I would expect to see the bullets in Impress. But ideally, the hidden bullets should not be created at all. Reproducible: Always User Profile Reset: No Additional Info: Noticed a similar bug https://bugs.documentfoundation.org/show_bug.cgi?id=155240 One difference is this is the Callibri font and not Arial. May be unrelated. This has been going on for well over a year but I haven't had a chance to report it until now. Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 16; OS: Linux 6.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US 7.5.3-2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136344] [UI] Keyboard shortcut for Table - Sort Ascending and Sort Descending not working
https://bugs.documentfoundation.org/show_bug.cgi?id=136344 --- Comment #7 from Alec K --- This bug is still present in Version: 7.5.4.2 (AARCH64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 10; OS: Mac OS X 13.4; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded No sort/re-order/change is seen in a table comprised of one letter or number per cell within a column when hitting F4 after binding F4 to 'Sort Ascending' as described. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136807] RTF Paste doesn't include image caption frame
https://bugs.documentfoundation.org/show_bug.cgi?id=136807 --- Comment #5 from Alec K --- This bug is still present in Version: 7.5.4.2 (AARCH64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 10; OS: Mac OS X 13.4; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded No frame after retained Ctrl+Shift+V - RTF, however selecting HTML or LibreOffice in the Ctrl+Shift+V dialog retains the frame. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155944] Irrelevant page positioning when maximizing a tiled window
https://bugs.documentfoundation.org/show_bug.cgi?id=155944 Alec K changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Alec K --- Thank you for reporting the bug. I can confirm that the bug is present in Version: 7.5.4.2 (AARCH64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 10; OS: Mac OS X 13.4; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded When resizing a window from small to large while in multi-page view, a different page is presented than what was most recently edited. It appears that the page shown after the window size changes is roughly double the original page number (page 33 -> pages 65 and 66). Reducing the window size (without scrolling in the document) returns the document to the original/recently-edited page. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156089] When setting the Heading/Outline Numbering for a level to "None", still getting separators
https://bugs.documentfoundation.org/show_bug.cgi?id=156089 --- Comment #10 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #9) > (In reply to Eyal Rozenberg from comment #8) > I don't buy the use case. You may exactly want to use None with > some prefix - and any modification is unwanted. I was replying to your use case of "you accidentally switch to None." This use case you now claim - does not exist. Why? Using "none with some prefix" means using a fixed symbol which doesn't advance with additional paragraphs; that is called: A bullet. I challenge you to demonstrate a reasonable use case in which anyone wants to use No-numbering with a prefix, and a bullet is not more appropriate. > > 2. How about if we only deleted it when the user had _not_ manually set the > > values since last arriving at the pane? > You probably mean settings made in a previous session. No, I don't. We could do that too, that's a third alternative. But we could just add a couple of "edited while pane is in focus" booleans to the code, which, when true, guard these fields against being reset. That said, I agree with your claim that it > Sounds like a lot of work for no good reason. ... and actually believe it is of basically zero use to maintain the prefix and suffix settings when you switch to None. I believe you are throwing up nonexistent or super-niche use cases to defend the surprising and cumbersome behavior in the common use case. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141058] PPTX to PDF: Images from deeper layers (covered by other objects) aren't omitted, and their decorative flag is ignored.
https://bugs.documentfoundation.org/show_bug.cgi?id=141058 --- Comment #6 from Commit Notification --- Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e751d59264c369cfc342dab5f0759be12341d306 tdf#141058 oox,sw: OOXML import/export of decorative on shapes It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141058] PPTX to PDF: Images from deeper layers (covered by other objects) aren't omitted, and their decorative flag is ignored.
https://bugs.documentfoundation.org/show_bug.cgi?id=141058 Commit Notification changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156183] DATA > TEXT TO COLUMNS : trashes cells on the right to the one being converted
https://bugs.documentfoundation.org/show_bug.cgi?id=156183 --- Comment #1 from Alec K --- Thank you for reporting the bug. I can not reproduce the bug in Version: 7.5.4.2 (AARCH64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 10; OS: Mac OS X 13.4; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Updating A1 via 'text to columns' did not appear to impact the format/content of B1 during my testing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105948 Bug 105948 depends on bug 118559, which changed state. Bug 118559 Summary: Calc: Bug with copy+paste for joined cells that breaks neighbor cells into pieces (and breaks Undo/Redo in LO 5.x) https://bugs.documentfoundation.org/show_bug.cgi?id=118559 What|Removed |Added Status|RESOLVED|NEW Resolution|WORKSFORME |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108844] [META] Cut/copy bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108844 Bug 108844 depends on bug 118559, which changed state. Bug 118559 Summary: Calc: Bug with copy+paste for joined cells that breaks neighbor cells into pieces (and breaks Undo/Redo in LO 5.x) https://bugs.documentfoundation.org/show_bug.cgi?id=118559 What|Removed |Added Status|RESOLVED|NEW Resolution|WORKSFORME |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118559] Calc: Bug with copy+paste for joined cells that breaks neighbor cells into pieces (and breaks Undo/Redo in LO 5.x)
https://bugs.documentfoundation.org/show_bug.cgi?id=118559 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Resolution|WORKSFORME |--- Status|RESOLVED|NEW --- Comment #25 from Buovjaga --- Comment 24 did not mention reproducing with an older version and now I tested with 6.3, couldn't repro, so I think we need to hear from marcusman and Xavier. Setting back to NEW. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156172] The link to the help button in the "Protect Spreadsheet Structure" Dialog is inconsistent.
https://bugs.documentfoundation.org/show_bug.cgi?id=156172 Alec K changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Alec K --- Thank you for reporting the bug. I can confirm that the bug is present in: Version: 7.5.4.2 (AARCH64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 10; OS: Mac OS X 13.4; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155902] writer crashes regularly after updating to dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155902 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||129062 CC||serval2...@yahoo.fr OS|All |Windows (All) Resolution|FIXED |WORKSFORME --- Comment #10 from Stéphane Guillou (stragu) --- (In reply to jim hamilton from comment #9) > It appears the Libre Writer crash scenario has stopped though the > deactivation of Skia. > Thanks! Thank you Jim for testing and reporting back. Skia is a graphics engine that can make use of GPU for rendering. Unfortunately, Skia can misbehave with various graphics card. If you can find the time for it, could you please do the following to help us out: - Turn "Force Skia software rendering" off again, restart LO - Share with us the Skia log: https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_(_Skia_) That information can help us make LO better for other users too, as we can blacklist the graphics card you are using. Cheers! Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129062 [Bug 129062] [META] Skia library bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||155902 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155902 [Bug 155902] writer crashes regularly after updating to dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156183] New: DATA > TEXT TO COLUMNS : trashes cells on the right to the one being converted
https://bugs.documentfoundation.org/show_bug.cgi?id=156183 Bug ID: 156183 Summary: DATA > TEXT TO COLUMNS : trashes cells on the right to the one being converted Product: LibreOffice Version: 7.5.4.2 release Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mbett...@gmail.com Description: Text to columns to a single column trashes cells on the right to the one being converted when converting dates. Converting from column A to a single output column, removes the content of column B Also, performing, for instance, Text to columns on Column A, with three output columns, affets Column D even if it should just affect columns A,B,C Steps to Reproduce: 1. Create a new sheet 2. Format cell A1 as text 3. Enter '2020-01-01' in A1 4. Enter 'Goes trashed' in B1 5. Select A1 6. Data->Text to columns 7. Click on 'Standard' above the Cell text 8. Select Date (YMD) (as the text is YMD, but the bug happens on all Date types) 9. Press OK Actual Results: A1 is now an actual date (formatting as number shows 43831) B1 has been trashed Expected Results: B1 shoud be preserved, as we elected to convert to ONLY ONE COLUMN Reproducible: Always User Profile Reset: No Additional Info: It happens on older versions too and on different computers too (linux & older macos) The bug is independent of locales, it happens with any date format and under different langauges as well -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156165] Writer acts changes style for unknown reason
https://bugs.documentfoundation.org/show_bug.cgi?id=156165 Baole Fang changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |baole.f...@gmail.com |desktop.org | --- Comment #9 from Baole Fang --- Indeed, it is caused by 083975f9666e3dc6fd665dc0418e6c3130628359. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156182] FORMATTING Automatic text color can be unreadable with darker cell colors
https://bugs.documentfoundation.org/show_bug.cgi?id=156182 ady changed: What|Removed |Added Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124093] EDITING Selecting filtered cells with hidden rows in between causes a bug in filter reset.
https://bugs.documentfoundation.org/show_bug.cgi?id=124093 --- Comment #18 from ady --- (In reply to Heiko Tietze from comment #17) > The filter cannot be applied to a selection, it always expands to the full > range. That's incorrect. Both the Standard Filter and the AutoFilter can be applied to a _selection_ that does not include every-and-all adjacent cells. Just select a range and try; for instance, leave the first cell of the range out of the selection before activating the (auto)filter. > We should do the same for Reset (and don't disable). That suggestion is a contradiction, and it goes against what I already explained in prior comments. Currently, the Reset acts on the _selection_; and when there is no specific selection, it acts on the filter that is relevant to the range that includes the active cell. My comments are still consistent with your screencast of comment 17; it just happens that you are not selecting any specific range/cell, and that the Reset menu entry acts only on 1 of the areas – I don’t know what’s the algorithm for it. If possible, "Reset" should be allowed to act multiple times (unless there is no filter left active to reset on any area), but should not expand automatically to the whole range when a specific range is selected; it should act on the selected range only. The "Clear" button acts on the whole affected area. There might be possible enhancements there too. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139532] [META] DOCX Floating table related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=139532 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||156059 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156059 [Bug 156059] A DOCX has two pages, but should have one -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113388] Support for Client Side Windows Decorations in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=113388 --- Comment #22 from third='beedell', first='roke', second='julian lockhart' --- (In reply to Heiko Tietze from comment #21) > (In reply to third='beedell', first='roke', second='julian lockhart' from > comment #20) > > ...I'd like to be able to demonstrate that I oppose... > You disagree with CSD? Comments are welcome. If you want a pull, happy to > put it on Twitter or Mastodon. What do you want to ask exactly (given > ordinary users have no idea of CSD)? I don't want to ask anything. I want to allow people to oppose or support this initiative, but without notifying everyone subscribed. GitLab provides reactions for issues, but Bugzilla doesn't. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152370] MariaDB direct connection: Access through socket to separate instance of MariaDB impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=152370 Adam664 changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155229] FILEOPEN DOCX/DOC/RTF Table with row heights set as "At least" gets smaller row heights (MSO atLeast 10 is larger than MSO exact 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=155229 Justin L changed: What|Removed |Added Summary|FILEOPEN DOCX/DOC/RTF Table |FILEOPEN DOCX/DOC/RTF Table |with row heights set as "At |with row heights set as "At |least" gets smaller row |least" gets smaller row |heights |heights (MSO atLeast 10 is ||larger than MSO exact 10) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155229] FILEOPEN DOCX/DOC/RTF Table with row heights set as "At least" gets smaller row heights
https://bugs.documentfoundation.org/show_bug.cgi?id=155229 --- Comment #12 from Justin L --- Created attachment 188237 --> https://bugs.documentfoundation.org/attachment.cgi?id=188237&action=edit 155229_atLeast0.51cm.docx: 2 page document in MSO This is the identical document, with "exact" changed to "atLeast". The MSO documentation of course indicates that they OUGHT to be the same size. So this must be an MSO implementation detail. Thus it will be rather hard to guess what algorithm difference they use to determine the layout row height in these two cases. (Guessing wrong will lead to regressions in the other direction of having rows be too large, or round-tripping with a bigger TWIP result.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155229] FILEOPEN DOCX/DOC/RTF Table with row heights set as "At least" gets smaller row heights
https://bugs.documentfoundation.org/show_bug.cgi?id=155229 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #11 from Justin L --- Created attachment 188236 --> https://bugs.documentfoundation.org/attachment.cgi?id=188236&action=edit 155229_exact0.51cm.docx: 1 page document that becomes 2 pages with w:hRule="atLeast" Satya discovered that in Microsoft Office, "atLeast" heights are actually larger than "exact" heights - at least in their layout. Simply changing w:hRule="exact" to w:hRule="atLeast" will cause this 1-page document to become two pages in MSO. (I used MSO 2010 - the difference can easily be seen in the UI by simply selecting the table and changing the row heights from exact to at least.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108912] [META] Sheet-level bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108912 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156174 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156174 [Bug 156174] Bug in VLOOKUP formula if delete a sheet -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156174] Bug in VLOOKUP formula if delete a sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=156174 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||6926 Component|LibreOffice |Calc OS|Windows (All) |All Blocks||108912 Keywords||bibisected, bisected, ||regression CC||er...@redhat.com, ||tund...@gmail.com Version|7.5.4.2 release |7.2.1.2 release Regression By||Tünde Tóth Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #4 from Stéphane Guillou (stragu) --- Confirmed in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d74344f6cae0cf1c12f08249c8f49be1374fb98f CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded If other sheet deleted, no bug. If Sheet Feuille13 is moved to before UPN, and then deleted, no bug. Bibisected with linux-64-7.2 repo to first bad commit c7baa2dd3209b9db60ee0699536135109918915d which points to core commit 957d1e977d25385151c99e401124ad58217e53dd which is a cherrypick of: commit 0c0444c44107f1a18f23dd0833d462d8dbf56569 author Tünde Tóth Wed Jul 21 16:04:37 2021 +0200 committer Eike Rathke Fri Jul 30 17:57:10 2021 +0200 tdf#126926 sc DBData: delete the database range if some part of the reference became invalid. Reviewed-on: https://gerrit.libreoffice.org/c/core/+/119354 Not reproduced in 7.1, but once Large Spreadsheets is turned on, I get crashes, so maybe related to a potential UPN column name? Crash reports, for the record: - 7.1: https://crashreport.libreoffice.org/stats/crash_details/c091cdc8-841d-4518-b25d-c78a2dce096e - 7.2: https://crashreport.libreoffice.org/stats/crash_details/ac78a34f-b721-48eb-840a-62a69c227f25 - 7.3: https://crashreport.libreoffice.org/stats/crash_details/9a54f65a-64e7-4a8e-bb16-4494ee19de04 - No crash since 7.4. Tünde, can you please have a look? Eike, what are your thought on what looks to me like an "off-label" use of a sheet name in the second argument of a VLOOKUP()? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108912 [Bug 108912] [META] Sheet-level bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83670] color gradient (cell background) not displayed correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=83670 Buovjaga changed: What|Removed |Added URL|https://gbplusapps.com/yowh | |atsapp-apk-download/| Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156182] FORMATTING Automatic text color can be unreadable with darker cell colors
https://bugs.documentfoundation.org/show_bug.cgi?id=156182 --- Comment #1 from Myndex --- Created attachment 188235 --> https://bugs.documentfoundation.org/attachment.cgi?id=188235&action=edit An image showing examples of how automatic text color issues and solution See first post for description. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156182] New: FORMATTING Automatic text color can be unreadable with darker cell colors
https://bugs.documentfoundation.org/show_bug.cgi?id=156182 Bug ID: 156182 Summary: FORMATTING Automatic text color can be unreadable with darker cell colors Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m...@andysomers.com Description: When the text color is set the automatic, the colors for text are frequently illegible with darker cell backgrounds. At present, the text color flips from black to white only when the cell is darker than about #3f3f3f. For accessible contrast for readability, the central contrast point is much higher, approximately #a4a4a4. I have an example image showing the current LibreOffice flip point, and then APCA, luminance at 36Y, and the old WCAG2: https://www.myndex.com/PUB/IMG/libreofficetextproblem.png Will attach here as well As you can see on the image the current flip point is too dark. Either APCA or a simple luminance flip point at 0.36Y brings the contrast to ~perceptual center. NOTE: WCAG 2 math also fails for dark colors, and is not fit for use here, as can also be seen on the example. Assuming sRGB, the following simple code will take eight bit RGB values and convert to a relative luminance value, that then can be used to determine the flip point. ``` // ANDY'S DOWN AND DIRTY LUMINANCE™ // Rs Gs Bs are 0-255 sRGB values. JS shown. // FlipY is a value 0.0-1.0, and 0.36 is a good point to flip text black or white. // For purists: Yea this is NOT the IEC piecewise, but it's fast and simple let flipY = (Rs/255.0)**2.2*0.2126+(Gs/255.0)**2.2*0.7152+(Bs/255.0)**2.2*0.0722; ``` Steps to Reproduce: 1. Set text color to automatic 2. Set the cell color to a very dark color but is lighter than about #3f3f3f 3. Some example cell backgrounds are #6d3400, #444, #005682 4. This is an accessibility fail but it is also a failure for all users as text becomes essentially unreadable. Actual Results: Unreadable with insufficient contrast and too dark Expected Results: Ideally text should be readable in most cases. The simplest answer, the text should flip from black to white or vice versa, when the luminance of the cell color is approximately 0.36Y There is a demonstrator repo with links to examples and discussion: https://github.com/Myndex/fancyfontflipping Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 8; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155388] Context menu in SlideShow mode temporarily disables SlideShow mode
https://bugs.documentfoundation.org/show_bug.cgi?id=155388 --- Comment #10 from Roman Kuznetsov <79045_79...@mail.ru> --- Still rerpo with Skia/Vulcan Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d74344f6cae0cf1c12f08249c8f49be1374fb98f CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded but no repro with Skia/Raster Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d74344f6cae0cf1c12f08249c8f49be1374fb98f CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded It looks like as video driver problem, interesting how I can update it here just for checking -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147953] Autosize text frame stops working
https://bugs.documentfoundation.org/show_bug.cgi?id=147953 --- Comment #13 from Panos Stokas --- I'm following the steps and I can't reproduce the bug anymore. Like bug 151728, this one seems to have been fixed in 7.6 too -- thanks to whoever fixed bug 151974 ! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113388] Support for Client Side Windows Decorations in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=113388 --- Comment #21 from Heiko Tietze --- (In reply to third='beedell', first='roke', second='julian lockhart' from comment #20) > ...I'd like to be able to demonstrate that I oppose... You disagree with CSD? Comments are welcome. If you want a pull, happy to put it on Twitter or Mastodon. What do you want to ask exactly (given ordinary users have no idea of CSD)? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124093] EDITING Selecting filtered cells with hidden rows in between causes a bug in filter reset.
https://bugs.documentfoundation.org/show_bug.cgi?id=124093 --- Comment #17 from Heiko Tietze --- Created attachment 188234 --> https://bugs.documentfoundation.org/attachment.cgi?id=188234&action=edit Screencast (In reply to ady from comment #16) > FWIW, I don't understand what you mean. The filter cannot be applied to a selection, it always expands to the full range. We should do the same for Reset (and don't disable). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105362] FILEEXPORT: Slides nearly black and unreadable when exported to PNG with transparency enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=105362 Armin Le Grand changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |armin.le.gr...@me.com |desktop.org | --- Comment #10 from Armin Le Grand --- Well, there are two options: (a) in the save-dialog (file-dialog), choose 'selection' or not (b) in the PNG-options dialog, choose 'Save transparency' or not not b -> all OK b -> fully transparent PNG Thus the problem seems (b). (a) has no effect, probably because there is no selection (and none possible - no objects on the page, only on MasterPage) Will take a look what makes the difference... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113478] Rename 'Decimal separator key' to 'Numpad decimal key'
https://bugs.documentfoundation.org/show_bug.cgi?id=113478 Heiko Tietze changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |dochieon...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113477] [META] Decimal separator key bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113477 Bug 113477 depends on bug 113478, which changed state. Bug 113478 Summary: Rename 'Decimal separator key' to 'Numpad decimal key' https://bugs.documentfoundation.org/show_bug.cgi?id=113478 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113478] Rename 'Decimal separator key' to 'Numpad decimal key'
https://bugs.documentfoundation.org/show_bug.cgi?id=113478 Heiko Tietze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
