[Libreoffice-bugs] [Bug 82982] FORMATTING: No available method for hidden text in a text box
https://bugs.documentfoundation.org/show_bug.cgi?id=82982 DoMyCourses changed: What|Removed |Added URL||https://domycourses.com/tak ||e-my-online-course.php Keywords||bisected --- Comment #8 from DoMyCourses --- I've read this article and will undoubtedly apply its advice. I appreciate your sharing. Domycourses offers initiative-based, understandable content. Each of the do my courses they offer is simple to follow and has content focused on the initiative. They supply courses as needed.https://domycourses.com/take-my-online-course.php -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108827] [META] Calc functions bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108827 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153539 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153539 [Bug 153539] EDITING Some Calc functions get extra leading space character every time the formula is edited (same with save + reload) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108253] [META] Calc cell formula bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108253 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153539 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153539 [Bug 153539] EDITING Some Calc functions get extra leading space character every time the formula is edited (same with save + reload) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153539] EDITING Some Calc functions get extra leading space character every time the formula is edited (same with save + reload)
https://bugs.documentfoundation.org/show_bug.cgi?id=153539 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||108827, 108253 Version|unspecified |Inherited From OOo Whiteboard| QA:needsComment| Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEW Summary|EDITING Some Calc functions |EDITING Some Calc functions |add extra space character |get extra leading space |for each cell's edition |character every time the ||formula is edited (same ||with save + reload) --- Comment #1 from Stéphane Guillou (stragu) --- Reproduced: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded No need for the final ENTER in each step from 6 to 9. I confirm that any kind of edit to the formula adds an extra space between the equal sign and the formula name, but only when there is a space between the formula name and the opening parenthesis. E.g., I could add extra elements (or remove them) to the formula after the function, to the same effect. Also, reopening/reloading the file also adds one extra leading space. You can test doing Ctrl + S then File > Reload. I can reproduce the same behaviour in 6.0, although back then, a space would be added both before *and* after the formula name: Version: 6.0.0.3 Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk2; Locale: en-AU (en_AU.UTF-8); Calc: group Finally, in OOo 3.3, the spaces would be added before and after the formula name even without changing the formula. Entering in edit mode is enough. OpenOffice.org 3.3.0 OOO330m20 (Build:9567) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108253 [Bug 108253] [META] Calc cell formula bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108827 [Bug 108827] [META] Calc functions bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153343] Forms: Label field creates wrong font height as default (default 10 pt, but shows only 8 pt)
https://bugs.documentfoundation.org/show_bug.cgi?id=153343 --- Comment #3 from Robert Großkopf --- (In reply to Dieter from comment #2) > > So my question Robert is: Why do you expect 10pt? Where do you set default > font size of text in label (same with text box) Open Writer. Form → Design Mode must be chosen Create a Label Field "Label Field" will appear as content. Right mouse click over this field → Control Properties General → Font: (Default) appears. Press the button with 3 points. Font → Size is shown as 10 pt. (but it is really 8 pt) This font and font size is the default of the window manager. Here, with KDE on OpenSUSE, I could set it as Default for all menu entries, headers of the windows … I could set this font to 12 pt. But if I draw the label field it is shown with 8 pt. And Font → Size will be set to 12 pt. Seems "8 pt" is hard coded somewhere in LO since LO 7.5. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140249] FRAME DIALOG: Duplicate items of previous/next links in options tab
https://bugs.documentfoundation.org/show_bug.cgi?id=140249 Dieter changed: What|Removed |Added Blocks||103305 --- Comment #4 from Dieter --- Still present in Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded But result is really worse: either drop down list is empty, or it shows only some other frames (and some of them as duplicates) or it shows every frame as duplicate. also tested in Safe Mode. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103305 [Bug 103305] [META] Frame dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103305] [META] Frame dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103305 Dieter changed: What|Removed |Added Depends on||140249 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140249 [Bug 140249] FRAME DIALOG: Duplicate items of previous/next links in options tab -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153477] LibreOffice Writer adds empty lines to some pages of the document after closing and opening again
https://bugs.documentfoundation.org/show_bug.cgi?id=153477 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 --- Comment #4 from Stéphane Guillou (stragu) --- Thank you for the screenshots. Unfortunately, without a document for us to test, it will be hard to find the issue. I could not reproduce the issue by creating my own document from scratch. - Do you have a minimal example document you could share, or more precise steps starting from an empty document? - How come the file says "PPTX" at the top of the window? Which format do you use? - Did this behaviour start with version 7.5? Do previous version of LibreOffice not add extra lines? - Finally, please paste here the information copied from Help > About LibreOffice. Thanks for your help! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153343] Forms: Label field creates wrong font height as default (default 10 pt, but shows only 8 pt)
https://bugs.documentfoundation.org/show_bug.cgi?id=153343 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de Whiteboard| QA:needsComment| Hardware|x86-64 (AMD64) |All OS|Linux (All) |All --- Comment #2 from Dieter --- Tested with Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de 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 Default font is Segoe UI 9pt. But I have no idea, why this should be default font and size. I don't know where I can set this default font. in Options -> LibreOffice Writer -> Basic Fonts the default font is Liberation Serif 12pt. So my question Robert is: Why do you expect 10pt? Where do you set default font size of text in label (same with text box) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136901] Unintuitive dragging of tabs in RTL UI
https://bugs.documentfoundation.org/show_bug.cgi?id=136901 Heiko Tietze changed: What|Removed |Added Attachment #185542|0 |1 is obsolete|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129661] [META] Right-To-Left (RTL) user interface issues
https://bugs.documentfoundation.org/show_bug.cgi?id=129661 Heiko Tietze changed: What|Removed |Added Depends on||136901 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136901 [Bug 136901] Unintuitive dragging of tabs in RTL UI -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136901] Unintuitive dragging of tabs in RTL UI
https://bugs.documentfoundation.org/show_bug.cgi?id=136901 Heiko Tietze changed: What|Removed |Added Status|NEEDINFO|NEW Blocks||129661 --- Comment #9 from Heiko Tietze --- Confirming with SAL_RTL_ENABLED=1. The trigger position for the tabs is completely messed up. The kf5 issue comes on top of it and is unrelated. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129661 [Bug 129661] [META] Right-To-Left (RTL) user interface issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153804] Footnotes disappeared in writer docx file after 7.5 update
https://bugs.documentfoundation.org/show_bug.cgi?id=153804 alidostnu...@yahoo.com 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 153804] Footnotes disappeared in writer docx file after 7.5 update
https://bugs.documentfoundation.org/show_bug.cgi?id=153804 --- Comment #3 from alidostnu...@yahoo.com --- Created attachment 185579 --> https://bugs.documentfoundation.org/attachment.cgi?id=185579=edit footnotes disappearing on libre office writer 7.5 with mac os 13.1.3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153515] LibreOffice does not remember the window position in fullscreen with more than one Screen
https://bugs.documentfoundation.org/show_bug.cgi?id=153515 Dieter changed: What|Removed |Added Blocks||104160 CC||dgp-m...@gmx.de Component|Writer |LibreOffice Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104160 [Bug 104160] [META] Bugs and features related to multiple monitor setups -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104160] [META] Bugs and features related to multiple monitor setups
https://bugs.documentfoundation.org/show_bug.cgi?id=104160 Dieter changed: What|Removed |Added Depends on||153515 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153515 [Bug 153515] LibreOffice does not remember the window position in fullscreen with more than one Screen -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117828] Positioning window to the left of the screen using setPosSize() leaves 7 px space.
https://bugs.documentfoundation.org/show_bug.cgi?id=117828 Andreas Heinisch changed: What|Removed |Added Resolution|--- |NOTABUG Status|NEW |RESOLVED --- Comment #7 from Andreas Heinisch --- IMO, not a bug since the width/height of the window is calculated using its decoration. Feel free to reopen it, if there are any concerns. -- 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 #14 from ady --- Sorry, sent prematurely. (In reply to ady from comment #13) After spending too-much time with attachment 179794 [details] and re-re-re-reading the posts here, (and also wasting additional time because Calc lacks "Trace dependents" features), I would say that there is no bug here (but, I could be wrong). I tested with LO 7.0.0.3 and with LO 7.4.5. In both, the first column A:A in the first sheet (named "Výpis CZK") is formatted as "D.M.". In either of these 2 versions the cells in this column are recognized as "DD.MM." or anything like that, other than "D.M.". Moreover, you are using the function CONCAT (for example in sheet "Výpočet 2" column C (e.g in C3) as criterion to compare to the aforementioned "date" cells, which then triggers the SUM in SUMIFS. You probably want some other function such as YEAR(), instead of a text-related function. Anyway, I would suggest checking: https://ask.libreoffice.org/c/czech-and-slovak/13 -- 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 #13 from ady --- After spending too-much time with attachment 179794 and re-re-re-reading the posts here, (and also wasting additional time because Calc lacks "Trace dependents" features), I would say that there is no bug here (but, I could be wrong). I tested with LO 7.0.0.3 and with LO 7.4.5. In both, the first column A:A in the first sheet (named "Výpis CZK") is formatted as "D.M.". In either of these 2 versions the cells in this column are recognized as "DD.MM." or anything like that, other than "D.M.". Moreover, you are using the function CONCAT (for example in sheet "Výpočet 2" column C (e.g in C3) as criterion to compare to the aforementioned "date" cells, which then triggers the SUM https://ask.libreoffice.org/c/czech-and-slovak/13 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153798] Line numbers should be aligned to the right in the Basic IDE
https://bugs.documentfoundation.org/show_bug.cgi?id=153798 Andreas Heinisch changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #6 from Andreas Heinisch --- Imho, valid enhancement. How should we treat them in the RTL mode? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35092] Inking functionality: Ink drawings / annotations with Stylus, Pen or Finger on Touchscreen or Tablet
https://bugs.documentfoundation.org/show_bug.cgi?id=35092 V Stuart Foote changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35092] Inking functionality: Ink drawings / annotations with Stylus, Pen or Finger on Touchscreen or Tablet
https://bugs.documentfoundation.org/show_bug.cgi?id=35092 --- Comment #178 from Jaguar landbase --- I appreciate you sharing this content. Very excellent and helpful information, thank you! Keep spreading, and thanks for the article. https://jaguarlandbase.com/elan-the-presidential-sector-106-gurgaon;>Elan The Presidential Sector-106 Gurgaon https://jaguarlandbase.com/elan-the-presidential-sector-106-gurgaon;>Elan The Presidential Sector-106 https://jaguarlandbase.com/elan-the-presidential-sector-106-gurgaon;>Elan The Presidential Gurgaon https://jaguarlandbase.com/m3m-jewel-sector-25-mg-road-gurgaon;>M3M Jewel Sector-25 Gurgaon https://jaguarlandbase.com/m3m-jewel-sector-25-mg-road-gurgaon;> M3M Jewel Sector-25 https://jaguarlandbase.com/m3m-jewel-sector-25-mg-road-gurgaon;>M3M Jewel Gurgaon -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153509] Offer easy-to-invoke split screens with a minimally visible user interface in Writer, using already existing LO functionality
https://bugs.documentfoundation.org/show_bug.cgi?id=153509 --- Comment #4 from j.a.sw...@gmail.com --- Thank you, Stéphane. We have requests to provide three different enhancements: 1. Distraction-free writing. (Bug 53895) In essence, nothing on the screen but a clean “virtual paper.” As with WriteRoom, OmmWriter, FocusWriter (open source), “distraction-free mode” in MS-Office, etc. 2. A “proofreading mode” by which to compare two different documents side by side. (Bug 31481, and more precisely defined there in Comment number 10) Lets you scroll both documents together in sync, in two panes in one window. As with the proofreading mode in MS-Office 2010. 3. A split screen for a single document. (Open Office bug 19291, https://bz.apache.org/ooo/show_bug.cgi?id=19291) Lets you independently scroll and edit two different parts of one document. Although each of these enhancements asks for minimal visible intrusion from the user interface, the three features are entirely different. Neither feature 1 nor feature 2 covers the use case for feature 3. Even though what Bug 31481 asks for is feature 2, what many of the users commenting there are pleading for is feature 3. Of the three features, feature 3 seems the one most often requested, but I couldn’t find a LO bug report for it. Before submitting Bug 153509, I saw Bug 31481. But what that asks for is feature 2. So I filed a separate bug to focus on feature 3 (and offer what seems like a feasible way to address it). Perhaps you might wish to leave all three of these bugs open and create a “meta-bug” to span all three, since they do all share a need to keep the user interface out of the way. By the way: Thanks to the devs for full-screen view, the “new window” feature, and the “Sidebar” view, all useful. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140567] Unwanted selection of outline content visibility button
https://bugs.documentfoundation.org/show_bug.cgi?id=140567 Jim Raykowski changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153325] LO 7.5 Draw adjusting connector lines (middle line handles)
https://bugs.documentfoundation.org/show_bug.cgi?id=153325 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153325] LO 7.5 Draw adjusting connector lines (middle line handles)
https://bugs.documentfoundation.org/show_bug.cgi?id=153325 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 153446] Tabbed UI - Hidden button don't work when displayed then used
https://bugs.documentfoundation.org/show_bug.cgi?id=153446 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 153515] LibreOffice does not remember the window position in fullscreen with more than one Screen
https://bugs.documentfoundation.org/show_bug.cgi?id=153515 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 153779] FILESAVE Calc takes 4 minutes to save a file
https://bugs.documentfoundation.org/show_bug.cgi?id=153779 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 148747] Bad use of the date in formulas
https://bugs.documentfoundation.org/show_bug.cgi?id=148747 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 153539] EDITING Some Calc functions add extra space character for each cell's edition
https://bugs.documentfoundation.org/show_bug.cgi?id=153539 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 153779] FILESAVE Calc takes 4 minutes to save a file
https://bugs.documentfoundation.org/show_bug.cgi?id=153779 --- 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 148747] Bad use of the date in formulas
https://bugs.documentfoundation.org/show_bug.cgi?id=148747 --- Comment #12 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111591] [META] File sending bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=111591 Bug 111591 depends on bug 70961, which changed state. Bug 70961 Summary: Other: Send document as e-mail doesn't work with webmail https://bugs.documentfoundation.org/show_bug.cgi?id=70961 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 70961] Other: Send document as e-mail doesn't work with webmail
https://bugs.documentfoundation.org/show_bug.cgi?id=70961 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 70961] Other: Send document as e-mail doesn't work with webmail
https://bugs.documentfoundation.org/show_bug.cgi?id=70961 --- Comment #6 from QA Administrators --- Dear Geoffrey, 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 137965] SwRedLineData pretty slow at undo
https://bugs.documentfoundation.org/show_bug.cgi?id=137965 --- Comment #7 from QA Administrators --- Dear Telesto, 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 149982] If Basic Fonts (Western) = Noto Serif then "Condensed" is forced
https://bugs.documentfoundation.org/show_bug.cgi?id=149982 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 149982] If Basic Fonts (Western) = Noto Serif then "Condensed" is forced
https://bugs.documentfoundation.org/show_bug.cgi?id=149982 --- Comment #3 from QA Administrators --- Dear David Snow, 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 145017] [Calc] The action of the New button in the Data Form seemed illogical
https://bugs.documentfoundation.org/show_bug.cgi?id=145017 --- Comment #3 from QA Administrators --- Dear Igor, 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 97206] Change Case functions not working with georgian text/alphabet
https://bugs.documentfoundation.org/show_bug.cgi?id=97206 --- Comment #6 from QA Administrators --- Dear nemzag, 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 68765] Requested clipboard format not available when right click on video
https://bugs.documentfoundation.org/show_bug.cgi?id=68765 --- Comment #7 from QA Administrators --- Dear bugcatcher1, 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 65229] superscript element in formula shifts formula baseline
https://bugs.documentfoundation.org/show_bug.cgi?id=65229 --- Comment #17 from QA Administrators --- Dear Yury, 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 63432] FORMATTING: "Change Case" does not work in some situations when symbols appear
https://bugs.documentfoundation.org/show_bug.cgi?id=63432 --- Comment #12 from QA Administrators --- Dear webofht-libreofficebugs002, 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 44196] FILEOPEN: Open .html file into Calc adds absolute path to relative HREF= URL
https://bugs.documentfoundation.org/show_bug.cgi?id=44196 --- Comment #12 from QA Administrators --- Dear g434, 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 140567] Unwanted selection of outline content visibility button
https://bugs.documentfoundation.org/show_bug.cgi?id=140567 --- Comment #3 from QA Administrators --- Dear Petr Valach, 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 140323] Forrmatting lost on redo
https://bugs.documentfoundation.org/show_bug.cgi?id=140323 --- Comment #4 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 135676] DDE link (ods-odt created by LibreOffice 6.4) not working in LibreOffice 7 (window 7, windows 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=135676 --- Comment #15 from QA Administrators --- Dear Vitaly, 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 130587] FILEOPEN DOCX Chart Y Axis Title position changed
https://bugs.documentfoundation.org/show_bug.cgi?id=130587 --- Comment #12 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 117880] UI: Save button doesn't gray out when you save an unchanged form.
https://bugs.documentfoundation.org/show_bug.cgi?id=117880 --- Comment #10 from QA Administrators --- Dear Balint Fodor, 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 116739] The functions toolbar does not get disabled when Manage Cells dialog is opened
https://bugs.documentfoundation.org/show_bug.cgi?id=116739 --- Comment #9 from QA Administrators --- Dear Emil Tanev, 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 112528] Can't make chart with specific information in a dynamic table
https://bugs.documentfoundation.org/show_bug.cgi?id=112528 --- Comment #14 from QA Administrators --- Dear Julian, 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 101837] EDITING: Calculation error for CHIINV function
https://bugs.documentfoundation.org/show_bug.cgi?id=101837 --- Comment #25 from QA Administrators --- Dear Alex Kempshall, 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 126862] [META] Issues with unusual builds / unit tests, rare test failures
https://bugs.documentfoundation.org/show_bug.cgi?id=126862 Bug 126862 depends on bug 153533, which changed state. Bug 153533 Summary: The test chart2_import fails on HIDPI display https://bugs.documentfoundation.org/show_bug.cgi?id=153533 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90796] [META] HiDPI / Retina bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=90796 Bug 90796 depends on bug 153533, which changed state. Bug 153533 Summary: The test chart2_import fails on HIDPI display https://bugs.documentfoundation.org/show_bug.cgi?id=153533 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153533] The test chart2_import fails on HIDPI display
https://bugs.documentfoundation.org/show_bug.cgi?id=153533 Hossein changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146404] Number Format Code: Not all color codes are saved
https://bugs.documentfoundation.org/show_bug.cgi?id=146404 m.a.riosv changed: What|Removed |Added CC||catmik2001-...@yahoo.co.uk --- Comment #2 from m.a.riosv --- *** Bug 153812 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 153812] [SAVE] Custom Number Format in Calc is not Retained
https://bugs.documentfoundation.org/show_bug.cgi?id=153812 m.a.riosv changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from m.a.riosv --- I was having problems with the mix between comma and decimal point. I can reproduce now. But this is a duplicate of tdf#146404 *** This bug has been marked as a duplicate of bug 146404 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153812] [SAVE] Custom Number Format in Calc is not Retained
https://bugs.documentfoundation.org/show_bug.cgi?id=153812 ady changed: What|Removed |Added Summary|Custom Number Format in |[SAVE] Custom Number Format |Calc is not Retained|in Calc is not Retained -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153812] Custom Number Format in Calc is not Retained
https://bugs.documentfoundation.org/show_bug.cgi?id=153812 ady changed: What|Removed |Added Status|RESOLVED|NEW Resolution|NOTABUG |--- Ever confirmed|0 |1 CC||jumbo4...@yahoo.fr --- Comment #3 from ady --- This "has" to be a bug (or more than one). Please keep reading. Using the American English spelling: 1. A1: [CTRL]+[1] 2. [COLOR22][$£-809]#,##0.00;[RED]-[$£-809]#,##0.00 (OK) 3. A1: 1 [ENTER] You can clearly see that the color format is accepted. 4. Save; you can still see the color. 5. Close the file and reopen it. > The color is gone and the [COLOR22] format in A1 is gone too. This happens for .ods and for .xls(x). I don't know whether the ODF specs actually accept this in some form or another. But, since Calc seems to initially accept the format, the this seems to be: A_ A saving problem (ods). B_ An export problem (xls and xlsx). C_ Lacks proper documentation? CC'ing Laurent Balland (who recently added some other custom number format support). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71324] EDITING: can't un-bold selection if it crosses hidden lines of an auto-filter
https://bugs.documentfoundation.org/show_bug.cgi?id=71324 --- Comment #17 from ady --- While this can still be reproduced in current versions (after more than 9 years), I'd like to post a semi-workaround to those users that might be interested (FWIW). 1. Select the relevant range of cells (after the filter was applied) from the first to the last cell of the relevant range. 2. Menu Edit > Select > Select Visible Rows Only. Now you can press [CTRL]+[B] several times and see the results (on visible cells only). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153806] Improve keyboard interaction for Special Characters dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=153806 --- Comment #3 from Michael Weghorn --- (In reply to Stéphane Guillou (stragu) from comment #2) > I agree that the current situation needs improvement, at the very least > allowing inserting directly from the search results with the keyboard, just > like in the favourite list. > > Interestingly, back in 6.3, I was able to insert from the search results by > using Space bar, then Enter (which would also close the dialog). Since 6.4, > I can't do that. Some kind of regression along the way? Reading this, another idea might be to distinguish between space and Enter key and have Enter key close the dialog in addition, as happens e.g. in the Insert -> Hyperlink dialog, too, so maybe sth like this (but then consistently for both, characters in the character table (like search results) *and* the favorites/recently used ones), so: * space key inserts the character, but leaves the dialog open * Enter inserts the character and closes the dialog (And still make putting focus into the search results make the "Insert" button usable right away.) What do you think? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153813] radial gradient with transition start renders wrongly in automatic steps if Skia is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153813 --- Comment #6 from V Stuart Foote --- (In reply to V Stuart Foote from comment #4 s/ bug 137523/ bug 136523 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151328] Skia with anti-aliasing enabled has moire in gradients in edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=151328 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3813 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153813] radial gradient with transition start renders wrongly in automatic steps if Skia is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153813 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1328 --- Comment #5 from V Stuart Foote --- Seems related, or even a dupe to bug 151328 and its bisect to https://cgit.freedesktop.org/libreoffice/core/commit/?id=6965bb07bb33429a7663a3f3ebe58ed89c4327d9 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136523] Stripes in gradient in presentation mode Skia Raster/Vulkan
https://bugs.documentfoundation.org/show_bug.cgi?id=136523 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3813 -- 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 V Stuart Foote changed: What|Removed |Added Depends on||153813 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153813 [Bug 153813] radial gradient with transition start renders wrongly in automatic steps if Skia is enabled -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153813] radial gradient with transition start renders wrongly in automatic steps if Skia is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153813 V Stuart Foote changed: What|Removed |Added CC||armin.le.gr...@me.com, ||l.lu...@collabora.com, ||vsfo...@libreoffice.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||6523 Blocks||129062 --- Comment #4 from V Stuart Foote --- Also confirming, With Skia Vulka or Skia raster libs rendering, using an increment value for the area gradient it is not as smooth as the "auto" checkbox achieves. Checked at each of 16, 32, 64, 128 and 256 level gradient. CPU GDI rendering, or with CPU HA those gradient steps increase in smoothness through 256 increments, matching the "automatic" at about 128 steps. The Skia based rendering of the gradient steps also increase--but they do not smooth out. So at 256 steps, still noticeable moiré and coarseness to the gradient. Did similar for https://git.libreoffice.org/core/+/a46cb5dc607d1d1af402ff3e8fce731e7427854d%5E%21 for bug 137523 for the liner gradients need to be done for radial area gradients? 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 140879] [META] Console noise
https://bugs.documentfoundation.org/show_bug.cgi?id=140879 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153814 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153814 [Bug 153814] many "configitem.cxx:423: ignoring XHierarchicalNameAccess ColorSchemes" warnings at startup -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153814] New: many "configitem.cxx:423: ignoring XHierarchicalNameAccess ColorSchemes" warnings at startup
https://bugs.documentfoundation.org/show_bug.cgi?id=153814 Bug ID: 153814 Summary: many "configitem.cxx:423: ignoring XHierarchicalNameAccess ColorSchemes" warnings at startup Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org Blocks: 140879 When launching LO from the console, I get many warnings of the type: warn:unotools.config:88010:88010:unotools/source/config/configitem.cxx:423: ignoring XHierarchicalNameAccess ColorSchemes/*['LibreOfficeDev']/DocColor/Color com.sun.star.container.NoSuchElementException message: "ColorSchemes/*['LibreOfficeDev']/DocColor/Color at /home/tdf/lode/jenkins/workspace/lo_gerrit/tb/src_master/configmgr/source/access.cxx:439" Seems to have started between 2da16ff9f018fae68c53a801e5a234dafc2ebcec (which is the last commit I have in the 7.6 bisect repo) and 6d9b9d1228cdee69e767833202442a1fed6174a6 (the current master build I have). Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6d9b9d1228cdee69e767833202442a1fed6174a6 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140879 [Bug 140879] [META] Console noise -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153533] The test chart2_import fails on HIDPI display
https://bugs.documentfoundation.org/show_bug.cgi?id=153533 --- Comment #3 from Commit Notification --- Hossein committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/573863d78ae55cdb8dfc9747aee47804a0b6f84c tdf#153533 Fix chart2_import test failure on HiDPI display It will be available in 7.6.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 153533] The test chart2_import fails on HIDPI display
https://bugs.documentfoundation.org/show_bug.cgi?id=153533 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153448] Footer and header missing on first page
https://bugs.documentfoundation.org/show_bug.cgi?id=153448 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for your report, Grobe. Could you please test it with a currently-supported version of LibreOffice (7.4 or 7.5), and let us know if you still see the issue? Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107739] [META] Field bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107739 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153488 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153488 [Bug 153488] The "Separator" field in the "Numbering by Chapter" section in the AutoCaption Dialog should only allow one character to be entered -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153488] The "Separator" field in the "Numbering by Chapter" section in the AutoCaption Dialog should only allow one character to be entered
https://bugs.documentfoundation.org/show_bug.cgi?id=153488
Stéphane Guillou (stragu) changed:
What|Removed |Added
Ever confirmed|0 |1
Blocks||107739
Keywords||bibisectRequest, regression
Status|UNCONFIRMED |NEW
CC||stephane.guillou@libreoffic
||e.org
Version|unspecified |5.2.0.4 release
--- Comment #3 from Stéphane Guillou (stragu)
---
reproduced with:
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 6d9b9d1228cdee69e767833202442a1fed6174a6
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded
It is a discrepancy that needs fixing as one can later on edit the field
("right-click > Edit fields..." or double-click on it) and see that the Edit
Fields dialog only allows on single character as a separator.
This is a regression as OOo 3.3 doesn't allow more than one character in the
AutoCaption settings:
OpenOffice.org 3.3.0
OOO330m20 (Build:9567)
But LO 5.2 does:
Version: 5.2.0.4
Build ID: 066b007f5ebcc236395c7d282ba488bca6720265
CPU Threads: 8; OS Version: Linux 5.15; UI Render: default;
Locale: en-AU (en_AU.UTF-8)
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=107739
[Bug 107739] [META] Field bugs and enhancements
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153503] FILEOPEN DOC: automatic Heading 1 numbering::None has followed-by tabstop instead of nothing
https://bugs.documentfoundation.org/show_bug.cgi?id=153503 --- Comment #3 from Justin L --- (In reply to Stéphane Guillou (stragu) from comment #2) > "Format > Bullets and Numbering > Position" being the same as "Tools > > Chapter Numbering > Position", right? Right. > Not inherited, as OOo 3.3 does not show an indentation (even though the > dialog does show "Numbering followed by: tab stop"). Yes, I'm not worried about whether it shows or not. I'm only concerned about the values. IF microsoft office DID have these settings (remember that when we export, they are lost) then likely it WOULD display an indentation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150432] Startup of app in Wayland is throwing errors: GDK_IS_WAYLAND_WINDOW assertion failure
https://bugs.documentfoundation.org/show_bug.cgi?id=150432 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords|bibisectRequest, regression | Version|6.3.6.2 release |6.1 all versions --- Comment #5 from Stéphane Guillou (stragu) --- (In reply to Stéphane Guillou (stragu) from comment #4) > I'm going to call this a regression as I don't see it in 6.1 I take that back, I can also see the failed assertion in linux-64-6.1 bibisect repo's oldest. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153813] radial gradient with transition start renders wrongly in automatic steps if Skia is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153813 --- Comment #3 from m.a.riosv --- Anyway, what looks to me very problematic it's the affecting by the Antialiasing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153813] radial gradient with transition start renders wrongly in automatic steps if Skia is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153813 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Reproducible. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ab20dba30769a5a52830220daa347772485db6a2 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153503] FILEOPEN DOC: automatic Heading 1 numbering::None has followed-by tabstop instead of nothing
https://bugs.documentfoundation.org/show_bug.cgi?id=153503 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Version|Inherited From OOo |5.2 all versions Keywords||regression CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- "Format > Bullets and Numbering > Position" being the same as "Tools > Chapter Numbering > Position", right? Confirmed in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6d9b9d1228cdee69e767833202442a1fed6174a6 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded No indentation in: Microsoft® Word for Microsoft 365 MSO (Version 2212 Build 16.0.15928.20196) 64-bit Not inherited, as OOo 3.3 does not show an indentation (even though the dialog does show "Numbering followed by: tab stop"). OpenOffice.org 3.3.0 OOO330m20 (Build:9567) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153811] When modify Offset of Page Number field, last Page Number is not shown
https://bugs.documentfoundation.org/show_bug.cgi?id=153811 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Reproducible also in Header. 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: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153812] Custom Number Format in Calc is not Retained
https://bugs.documentfoundation.org/show_bug.cgi?id=153812 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #2 from m.a.riosv --- In https://help.libreoffice.org/7.6/en-US/text/shared/01/05020301.html?=CALC=WIN " Color To set the color of a section of a number format code, insert one of the following color names in square brackets [ ]: CYAN,GREEN,BLACK,BLUE,MAGENTA,RED,WHITE,YELLOW " No other colors than that are accepted. The format code [COLOUR22][$£-809]#,##0.00;[RED]-[$£-809]#,##0.00 it is not accepted at all, when you enter it, push Ok, edit again the cell format, 'Standard' there. The first format, it's accepted and saved. Tested with: 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: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo To me, not a bug. Please if you are not agree, reopen it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153528] Libreoffice crashed after updating from 5.0.5.2 to 7.5.0.3 with Windows 7
https://bugs.documentfoundation.org/show_bug.cgi?id=153528 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Stéphane Guillou (stragu) --- Zaneli and NickM, can you please try version 7.5.1? https://www.libreoffice.org/download/download-libreoffice/?version=7.5.1 Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153813] radial gradient with transition start renders wrongly in automatic steps if Skia is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153813 --- Comment #1 from Regina Henschel --- Created attachment 185578 --> https://bugs.documentfoundation.org/attachment.cgi?id=185578=edit Screenshot Skia enabled -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153813] New: radial gradient with transition start renders wrongly in automatic steps if Skia is enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153813 Bug ID: 153813 Summary: radial gradient with transition start renders wrongly in automatic steps if Skia is enabled Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 185577 --> https://bugs.documentfoundation.org/attachment.cgi?id=185577=edit automatic steps vs maximal steps Open attached file. The shapes have a radial gradient with transition start (border) 50%. If Skia is enabled the border is not only outer but also inside the gradient. If Skia is disabled the shape looks the same as with maximal steps, which is the expected rendering. Disable anti-aliasing, otherwise you get moire effects in case of rendering with maximal steps. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153565] Minimally responsive (sluggish) and crashing almost randomly
https://bugs.documentfoundation.org/show_bug.cgi?id=153565 fpecq...@comcast.net changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from fpecq...@comcast.net --- It seems to have worked. I have used it several times without crashing. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71324] EDITING: can't un-bold selection if it crosses hidden lines of an auto-filter
https://bugs.documentfoundation.org/show_bug.cgi?id=71324 --- Comment #16 from Toby --- Retested on 7.5.0.3 This bug still exists. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153325] LO 7.5 Draw adjusting connector lines (middle line handles)
https://bugs.documentfoundation.org/show_bug.cgi?id=153325 Ezinne changed: What|Removed |Added Keywords||regression --- Comment #6 from Ezinne --- I checked an older version and noticed the bug is not present in: Version: 6.0.0.0.beta1 Build ID: 97471ab4eb4db4c487195658631696bb3238656c CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk2; Locale: en-AU (en_AU.UTF-8); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153325] LO 7.5 Draw adjusting connector lines (middle line handles)
https://bugs.documentfoundation.org/show_bug.cgi?id=153325 Ezinne changed: What|Removed |Added CC||nnamani.ezi...@collabora.co ||m Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #5 from Ezinne --- Reproducible in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4a0d671706306661c4a5072ce4769dc47bc65f71 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153529] Drag-and-drop a sound from the gallery fails unless cursor is on the page
https://bugs.documentfoundation.org/show_bug.cgi?id=153529 Stéphane Guillou (stragu) changed: What|Removed |Added OS|Linux (All) |All Summary|LibreOffice Writer - icons |Drag-and-drop a sound from |in sounds section in|the gallery fails unless |gallery doesn't appear in |cursor is on the page |page| Version|7.6.0.0 alpha0+ Master |5.3.0.3 release Ever confirmed|0 |1 Blocks||99671 Status|UNCONFIRMED |NEW CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Reproduced. My steps after testing: 1. Drag-and-drop a sound on the page 2. Drag-and-drop another: it is not inserted, only the first one remains. 3. Delete the sound on the page 4. Drag-and-drop another onto the page: it is not inserted 5. Click on page, then drag-and-drop a sound: it is inserted. So the issue as I see it is that inserting a gallery sound with drag-and-drop does not work if the cursor is not on the page. This differs from other gallery categories: e.g. an arrow can be inserted when another one is already selected or has just been deleted. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6d9b9d1228cdee69e767833202442a1fed6174a6 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded On Windows 10 too: 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-GB (en_GB); UI: en-GB Calc: threaded I already see it in 5.3: Version: 5.3.0.1 Build ID: 3b800451b1d0c48045de03b5b3c7bbbac87f20d9 CPU Threads: 8; OS Version: Linux 5.15; UI Render: default; VCL: gtk2; Layout Engine: new; Locale: en-AU (en_AU.UTF-8); Calc: group In 5.2, I can't insert any sound. I'm surprised I couldn't find a duplicate. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99671 [Bug 99671] [META] Gallery bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99671] [META] Gallery bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=99671 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||153529 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153529 [Bug 153529] Drag-and-drop a sound from the gallery fails unless cursor is on the page -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153812] Custom Number Format in Calc is not Retained
https://bugs.documentfoundation.org/show_bug.cgi?id=153812 --- Comment #1 from Michael Howard --- Should read COLOR22 not COLOUR22 English spelling used in error report by mistake:- [COLOR22][$£-809]#,##0.00;[RED]-[$£-809]#,##0.00 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153812] New: Custom Number Format in Calc is not Retained
https://bugs.documentfoundation.org/show_bug.cgi?id=153812 Bug ID: 153812 Summary: Custom Number Format in Calc is not Retained Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: catmik2001-...@yahoo.co.uk Custom Number Formatting (user defined) in a CALC spreadsheet such as:- [GREEN][$£-809]#,##0.00;[RED]-[$£-809]#,##0.00 which formats positive numbers as GREEN or negative numbers as RED works fine. It is possible to use more than the standard colours using COLORX e.g. [COLOUR22][$£-809]#,##0.00;[RED]-[$£-809]#,##0.00 This colours positive numbers in this case as DARK GREEN and this is displayed in the spreadsheet when applied. However when the spreadsheet (ODF) is saved, this formatting is not displayed and the custom format is lost. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153808] Preview in the Bullets and Numbering is not painting bullets/numbers in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=153808 Rafael Lima changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | Status|NEW |ASSIGNED --- Comment #2 from Rafael Lima --- Proposed patch here: https://gerrit.libreoffice.org/c/core/+/147664 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146168] Font attributes of certain list numbers have changed after 7.2, and I can't change them back
https://bugs.documentfoundation.org/show_bug.cgi?id=146168 Justin L changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #13 from Justin L --- (In reply to David de Cos from comment #11) > Than you very much for your help No problem. Thanks for reporting. This is a coding-disaster area, so double-checking never hurts anything. marking as WONTFIX since in the targeted case (.RTF) this still is needed and the document in question has RTF-comparable compatibility flags. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153798] Line numbers should be aligned to the right in the Basic IDE
https://bugs.documentfoundation.org/show_bug.cgi?id=153798 --- Comment #5 from Julien Nabet --- (In reply to Roman Kuznetsov from comment #2) > (In reply to Julien Nabet from comment #1) ... > But there is some space to right from numbers in PyCharm anyway > > I don't think it's so much matter, btw Very sorry, I misinterpreted what you said, I thought the line number was on the right of the code for these IDEs. Forget my previous comment then. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153811] New: When modify Offset of Page Number field, last Page Number is not shown
https://bugs.documentfoundation.org/show_bug.cgi?id=153811 Bug ID: 153811 Summary: When modify Offset of Page Number field, last Page Number is not shown Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jcs...@libreoffice.org Description: When modify Offset of a Page Number in the Edit fields dialog, the last Page Number field don't show the page number Steps to Reproduce: 1. Open a Writer document 2. Insert a (page) footer 3. Insert a Page Number in the footer 4. Double clic in the Page Number field to show Edit Fields dialog 5. Modify Offset 6. Ok to close dialog 7. The page number disappears in the last page 8. Write text or insert a page break to obtain a new page 9. The page number appears in the page but is not shown in the new page Actual Results: The page number disappears in the last page Expected Results: All the page should have a page number Reproducible: Always User Profile Reset: No Additional Info: The last page page number is not shown on a page preview nor when the page is printed. -- Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 14a36ad49518bcb5b606b0f1640e3ca56b636e89 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded -- Version: 7.4.4.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 2; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.UTF-8); UI: es-ES Ubuntu package version: 1:7.4.4-0ubuntu0.22.10.2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35538] Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal
https://bugs.documentfoundation.org/show_bug.cgi?id=35538 --- Comment #73 from Callegar --- > AFAIK both italic and oblique fonts are considered slanted variants of the > upright/roman ones As a matter of fact things are more complicated: there are fonts that include italic variants that are not slanted. Formally for some fonts "it is possible to have 'upright italic' designs that have a cursive style but remain upright". In other words, italics is about the letter shape not the slant, even if the large majority of italic fonts have slanted letters. As an example, Knuth's Computer Modern has an upright italics. A more modern example is the Literata font that was commissioned by Google for Play Books. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146168] Font attributes of certain list numbers have changed after 7.2, and I can't change them back
https://bugs.documentfoundation.org/show_bug.cgi?id=146168 --- Comment #12 from David de Cos --- Well, you might be right after all. I started as a teacher in 2016, so I just opened the first work sheet I created back then, and in the Properties section it says it was created in 2009. So I must have based it on someone else's previous document. I could have sworn I did it from scratch, but apparently I didn't. Than you very much for your help, and sorry for making you double check things when you were right the first time! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35538] Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal
https://bugs.documentfoundation.org/show_bug.cgi?id=35538 خالد حسني changed: What|Removed |Added Depends on|69254 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=69254 [Bug 69254] Mac: Handling of fonts with more than 4 styles (R/B/I/BI) is suboptimal -- You are receiving this mail because: You are the assignee for the bug.
