[Libreoffice-bugs] [Bug 152026] EDITING: Add a "Simple markup" view to Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152026 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Heiko Tietze --- We have "Show TC", which can be used to hide all modifications, and means to see either deletions or insertions in the document margin. The proposed function would add something intermediate and actually I don't see the use case for it. Why would you need an indicator for TC when you hide it? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152033] New: Memory leakage when using Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152033 Bug ID: 152033 Summary: Memory leakage when using Writer Product: LibreOffice Version: 7.4.2.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nagyhadn...@gmail.com Description: I open a document, then I see that the used physical memory of LO Writer is constantly growing. Even if I don't change the document just reading it and using the window slider. Obviously this growth results in crash when memory is full. The bug doesn't occur in LO safe mode, but resetting user config didn't solve the problem. Steps to Reproduce: 1. Open a doc 2. Start doing anything in it 3. When you monitor memory consumption, it constatly grows Actual Results: Memory full and crash Expected Results: Don't leak memory Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: hu Module: StartModule [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103691] Change in API needed for language tools to display errors in colour
https://bugs.documentfoundation.org/show_bug.cgi?id=103691 Heiko Tietze changed: What|Removed |Added CC||misc2...@danielnaber.de --- Comment #9 from Heiko Tietze --- (In reply to Rafael Lima from comment #8) > In case this request is still valid, it would be nice to have someone from > the LanguaTool team providing more info about which error categories should > be supported. Daniel? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152019] Header/Footer popup tab causes lag (repeatable)
https://bugs.documentfoundation.org/show_bug.cgi?id=152019 Telesto changed: What|Removed |Added Keywords||perf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151966] Format not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=151966 --- Comment #6 from Robert Großkopf --- Could confirm all content for footer isn't saved right in *.xls-format. There only appears the 'Page …', nothing else. Saving the file as *.xlsx will save all informations and format like *.ods-files have been saved. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151966] Format not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=151966 Robert Großkopf changed: What|Removed |Added CC||rob...@familiegrosskopf.de --- Comment #5 from Robert Großkopf --- Did you really save the Calc file as *.xls? Only *.ods will save all information for Calc in the right way. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152021] A preset default "date" in a table will not be shown correctly in FORM when creating a new record
https://bugs.documentfoundation.org/show_bug.cgi?id=152021 Robert Großkopf changed: What|Removed |Added CC||rob...@familiegrosskopf.de --- Comment #4 from Robert Großkopf --- You are mixing different problems here. I will only write about 'default value'. GUI of Base offers a 'default' value for the tables. It will be saved in the Base file and will appear every time you create a new row in the table. GUI of Base offers also a 'default' value for form controls. It could be different to the value of the table, because it is only saved in the description for the form control. Seems you would use the same 'default' here. You have to change the default in the form for this value. Don't know a reason to use such a default value, created in for tables or form controls, for a date values. It will always be the same date … Default, created by SQL for the database, won't be shown in a table or a form. It will be saved if the field will be empty (NULL). To get date with the current date while saving the data will work with ALTER TABLE "Table" ALTER COLUMN "MyDate" SET DEFAULT CURRENT_DATE; -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152032] Open remote file (ssh/sshfs) does not open file
https://bugs.documentfoundation.org/show_bug.cgi?id=152032 Julien Nabet changed: What|Removed |Added CC||michael.st...@allotropia.de ||, serval2...@yahoo.fr --- Comment #1 from Julien Nabet --- Michael: thought you might be interested in this one. Indeed, I wonder if it could be related with ucb/curl part. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152019] Header/Footer popup tab causes lag (repeatable)
https://bugs.documentfoundation.org/show_bug.cgi?id=152019 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||caol...@redhat.com Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152019] Header/Footer popup tab causes lag (repeatable)
https://bugs.documentfoundation.org/show_bug.cgi?id=152019 --- Comment #4 from Mike Kaganski --- Created attachment 183575 --> https://bugs.documentfoundation.org/attachment.cgi?id=183575=edit Screencast Repro. This doesn't depend on the specific view mode (i.e., also happens in 1-page view). I screencasted it using debug build, to emphasize the effect. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152010] Add Native Support for Extension Icon Theme
https://bugs.documentfoundation.org/show_bug.cgi?id=152010 Adolfo Jayme Barrientos changed: What|Removed |Added Version|7.5.0.0 alpha0+ Master |Inherited From OOo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152010] Add Native Support for Extension Icon Theme
https://bugs.documentfoundation.org/show_bug.cgi?id=152010 Adolfo Jayme Barrientos changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Component|LibreOffice |Extensions CC||fit...@ubuntu.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152010] Add Native Support for Extension Icon Theme
https://bugs.documentfoundation.org/show_bug.cgi?id=152010 Adolfo Jayme Barrientos changed: What|Removed |Added Version|Inherited From OOo |7.5.0.0 alpha0+ Master Ever confirmed|1 |0 Status|NEW |UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108628] [META] Usability issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108628 Buovjaga changed: What|Removed |Added Depends on|136524 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136524 [Bug 136524] [META] Performance/hang/lag/high CPU issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136524] [META] Performance/hang/lag/high CPU issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136524 Buovjaga changed: What|Removed |Added Blocks|108628 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108628 [Bug 108628] [META] Usability issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152020] [META] bugs and enhancements around environmental impact of end user's computer
https://bugs.documentfoundation.org/show_bug.cgi?id=152020 --- Comment #9 from Buovjaga --- Jérôme: please discuss within the QA contributors group before doing decisions like this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152020] [META] bugs and enhancements around environmental impact of end user's computer
https://bugs.documentfoundation.org/show_bug.cgi?id=152020 Buovjaga changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||ilmari.lauhakangas@libreoff ||ice.org Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35217] Allow a child outline level to express the numerical value of its parent level with a different numbering style than the parent
https://bugs.documentfoundation.org/show_bug.cgi?id=35217 --- Comment #26 from Our Jharkhand --- Thank you so much for the post you do. I like your post and all you share with us is up to date and quite informative, i would like to bookmark the page so i can come here again to read you, as you have done a wonderful job. https://ourjharkhand.com/jharkhand-ranchi-personal-life-and-education-weather-top-touring-places/ https://ourjharkhand.com/jharkhand-logo-history-updated-logo-meaning-of-new-logo/ https://ourjharkhand.com/jharkhand-bijli-vitran-nigam-what-is-jbvnl-check-electricity-bill/ https://ourjharkhand.com/jharkhand-bhu-naksha/ https://ourjharkhand.com/jharkhand-rai-university/ https://ourjharkhand.com/weather-dhanbad-jharkhand/ https://ourjharkhand.com/aahar-jharkhand-gov-in/ https://ourjharkhand.com/chancellor-portal-jharkhand/ https://ourjharkhand.com/hazaribagh-jharkhand/ https://ourjharkhand.com/jharkhand-tourism/ Savitri Singh -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35217] Allow a child outline level to express the numerical value of its parent level with a different numbering style than the parent
https://bugs.documentfoundation.org/show_bug.cgi?id=35217 --- Comment #25 from Business Mart --- Thank you so much for the post you do. I like your post and all you share with us is up to date and quite informative, i would like to bookmark the page so i can come here again to read you, as you have done a wonderful job. https://mybusinessmart.com/ https://mybusinessmart.com/best-gaming-mouse-under-rs-1000/ https://mybusinessmart.com/pharmacy-franchise-opportunities/ https://mybusinessmart.com/best-otg-ovens-in-india/ https://mybusinessmart.com/business-ideas-opportunities-delhi/ https://mybusinessmart.com/small-manufacturing-business-ideas/ https://mybusinessmart.com/gaming-laptops-under-7-rupees/ https://mybusinessmart.com/best-shampoo-brands-in-india/ https://mybusinessmart.com/tyre-brands-in-india/ https://mybusinessmart.com/trading-business-ideas/ https://mybusinessmart.com/cheap-gaming-mouse-under-500/ Savitri Singh -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152026] EDITING: Add a "Simple markup" view to Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152026 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 35217] Allow a child outline level to express the numerical value of its parent level with a different numbering style than the parent
https://bugs.documentfoundation.org/show_bug.cgi?id=35217 --- Comment #24 from Mobile Number --- Nice post. I was checking constantly this blog and I am impressed! Extremely helpful information specially the last part I care for such info a lot. I was seeking this particular information for a very long time. Thank you and good luck. https://www.mobilenumbertrackeronline.com/cell-phone-number-tracker-faqs/ https://www.mobilenumbertrackeronline.com/free-phone-tracker-by-number/ https://www.mobilenumbertrackeronline.com/phone-number-location-tracker-2023/ https://www.mobilenumbertrackeronline.com/phone-tracker-by-number/ https://www.mobilenumbertrackeronline.com/imei-tracker-find-imei-number-without-phone-steps-to-track-phone-with-imei/ https://www.mobilenumbertrackeronline.com/imei-checker-gsm-networks-serial-number-how-to-find-your-phone-with-imei-number/ https://www.mobilenumbertrackeronline.com/phone-number-tracker-best-phone-no-tracker-people-search/ https://www.mobilenumbertrackeronline.com/mobile-phone-number-location-tracker-address-maps/ https://www.mobilenumbertrackeronline.com/mobile-number-tracker-online-free-with-location-in-india-map-exact-location-on-map/ https://www.mobilenumbertrackeronline.com/the-mobile-number-location-tracker-google-maps-in-india/ https://www.mobilenumbertrackeronline.com/best-mobile-number-tracker-with-google-map/ Savitri Singh -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151645] Hidden sections are present in the output document when they merged with option as individual documents
https://bugs.documentfoundation.org/show_bug.cgi?id=151645 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=54 ||703 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 54703] Hidden Sections are no longer hidden when printing or exporting pdf (see comment 16)
https://bugs.documentfoundation.org/show_bug.cgi?id=54703 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1645 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151946] Opening spreadsheet very slow
https://bugs.documentfoundation.org/show_bug.cgi?id=151946 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148688] Undo change of anchor positions image at wrong spot
https://bugs.documentfoundation.org/show_bug.cgi?id=148688 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151791] Calc-UI-Edit drop down menu-Cell protection
https://bugs.documentfoundation.org/show_bug.cgi?id=151791 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 151815] in print preview the normal-view viewing options are also visible
https://bugs.documentfoundation.org/show_bug.cgi?id=151815 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 151708] Unsaved documents are no longer recovered
https://bugs.documentfoundation.org/show_bug.cgi?id=151708 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 148857] Handle is not initialized exception when bootstrapping with .Net (but not in .Net Framework)
https://bugs.documentfoundation.org/show_bug.cgi?id=148857 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 151832] Keyboard shortcut cannot be assigned for Find and cannot be reset.
https://bugs.documentfoundation.org/show_bug.cgi?id=151832 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 151831] Expand animation not animating with Skia Raster enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=151831 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 151823] configuration formatting editing - default font changes, from 12pt to 11.3pt, after deleting pasted content, which was an email address
https://bugs.documentfoundation.org/show_bug.cgi?id=151823 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 151829] Writer TABLE: Optimal column width does not adjust columns that are too wide
https://bugs.documentfoundation.org/show_bug.cgi?id=151829 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 151822] Formatting: Text does not wrap around images after endnotes
https://bugs.documentfoundation.org/show_bug.cgi?id=151822 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 151966] Format not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=151966 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 151966] Format not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=151966 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149048] PDF editing Windows 11
https://bugs.documentfoundation.org/show_bug.cgi?id=149048 --- Comment #3 from QA Administrators --- Dear Jürgen, 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 147719] Calc freezes when resizing Properties pane
https://bugs.documentfoundation.org/show_bug.cgi?id=147719 --- Comment #10 from QA Administrators --- Dear grolschie, 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 115476] LibreOffice Crash after login if quickstarter is enabled and Use Open GL disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=115476 --- Comment #19 from QA Administrators --- Dear Kevin W. Gagel, 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 98490] Rulers that are off get turn on when opening a presentation with grids on
https://bugs.documentfoundation.org/show_bug.cgi?id=98490 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 98335] Paste split button arrow hides when disabling UI if clipboard isn't empty
https://bugs.documentfoundation.org/show_bug.cgi?id=98335 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 98039] Preview doesnt complete if custom animation set to slow speed
https://bugs.documentfoundation.org/show_bug.cgi?id=98039 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 97691] SVG gradient rotation not accurate
https://bugs.documentfoundation.org/show_bug.cgi?id=97691 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 96152] 'Numbering On/Off' button should be accessible in Outline view
https://bugs.documentfoundation.org/show_bug.cgi?id=96152 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 95906] VIEWING: Elements anchored as 'To Character' on last page of document appear on first page in Web Layout
https://bugs.documentfoundation.org/show_bug.cgi?id=95906 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 95059] Error bars indicator icons appearing with white background
https://bugs.documentfoundation.org/show_bug.cgi?id=95059 --- Comment #8 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 95044] Elements content panel has empty space for pie charts
https://bugs.documentfoundation.org/show_bug.cgi?id=95044 --- Comment #4 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 94764] Modified bitmap shouldn't be listed with the same name
https://bugs.documentfoundation.org/show_bug.cgi?id=94764 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 94909] Font name won't be selected when font list has recently used font section
https://bugs.documentfoundation.org/show_bug.cgi?id=94909 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 94289] Color drop down control doesnt highlight selected color
https://bugs.documentfoundation.org/show_bug.cgi?id=94289 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 90683] Pasting table as DDE Link resets undo
https://bugs.documentfoundation.org/show_bug.cgi?id=90683 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 93807] Updating cell style while in edit mode doesnt refresh text
https://bugs.documentfoundation.org/show_bug.cgi?id=93807 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 90630] Weird visual behaviour when activating/deactivating freeze pane
https://bugs.documentfoundation.org/show_bug.cgi?id=90630 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 90242] SIDEBAR: Navigator in Draw/Impress incorrectly naming, numbering and iconifying objects
https://bugs.documentfoundation.org/show_bug.cgi?id=90242 --- Comment #7 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 90585] Glue points shouldn't appear on shapes when drawing arrowed lines
https://bugs.documentfoundation.org/show_bug.cgi?id=90585 --- Comment #12 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 89745] DIALOG: Insert audio or video dialog shouldnt have preview in LO's custom dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=89745 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 89595] TOC: Rulers go full width of view area when cursor in Table of Contents
https://bugs.documentfoundation.org/show_bug.cgi?id=89595 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 89146] Formulas in Writer losing some formatting in docx and rtf files, compared to odt file
https://bugs.documentfoundation.org/show_bug.cgi?id=89146 --- Comment #9 from QA Administrators --- Dear mrk.signup, 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 89435] FILEOPEN: Images rendering on first page before being placed on suitable page
https://bugs.documentfoundation.org/show_bug.cgi?id=89435 --- Comment #8 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 88932] SIDEBAR: Styles still selectable when in shape edit mode
https://bugs.documentfoundation.org/show_bug.cgi?id=88932 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 85722] Collapsed Sidebar button panel shouldnt be clickable (summary in comment 8)
https://bugs.documentfoundation.org/show_bug.cgi?id=85722 --- Comment #16 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 72919] Other: UNO-API PDF Mass Export breaks layout
https://bugs.documentfoundation.org/show_bug.cgi?id=72919 --- Comment #17 from QA Administrators --- Dear Wahrendorff, 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 67327] Filesave DOC: maths formula is visually altered when reopened in LO (looks good in MSO)
https://bugs.documentfoundation.org/show_bug.cgi?id=67327 --- Comment #29 from QA Administrators --- Dear TDuell, 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 52006] FILEOPEN: can't open file with two leading slashes
https://bugs.documentfoundation.org/show_bug.cgi?id=52006 --- Comment #10 from QA Administrators --- Dear muzzol, 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 47953] "Error loading BASIC of document" error messages
https://bugs.documentfoundation.org/show_bug.cgi?id=47953 --- Comment #22 from QA Administrators --- Dear sam, 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 137822] Text boxes on docx do not have correct wrapping configuration on LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=137822 --- Comment #11 from QA Administrators --- Dear jake.weilhammer, 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 136884] Stuck forever on opening DOC file with chinese fonts and images contents
https://bugs.documentfoundation.org/show_bug.cgi?id=136884 --- Comment #4 from QA Administrators --- Dear Meriyi, 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 107216] Line border of animated image doesnt appear in slide show
https://bugs.documentfoundation.org/show_bug.cgi?id=107216 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 103726] Undo of disable contour applies auto-contour
https://bugs.documentfoundation.org/show_bug.cgi?id=103726 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 103139] Font name not selected when opening font name combobox
https://bugs.documentfoundation.org/show_bug.cgi?id=103139 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 101888] Paragraph tab type icons should be painted with dialog background color
https://bugs.documentfoundation.org/show_bug.cgi?id=101888 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 101069] Slides pane doesnt reopen immediately
https://bugs.documentfoundation.org/show_bug.cgi?id=101069 --- Comment #5 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 151903] Crash when using removeChildByIndex of node in TreeControl
https://bugs.documentfoundation.org/show_bug.cgi?id=151903 --- Comment #4 from Gabe --- After further testing, I confirmed that the cause of the crash was actually due to having set up a for-next loop in which the high range of the loop was changing. The code includes removal of nodes via the loop. However, as each node was deleted the high end of the range was changing. Seems more likely to be an issue regarding for-next loops and not the node deletion as I thought. My fix was easy - simply stepping backwards in the for-next loop -- i.el, "for i = oParentNode.getChildCount-1 to 0 step -1". The issue of the system crashing rather than throwing an error message remains but I think is low priority. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51733] Update icons for high-resolution HiDPI / Retina display
https://bugs.documentfoundation.org/show_bug.cgi?id=51733 --- Comment #45 from Adolfo Jayme Barrientos --- (In reply to richard.carree.com from comment #44) > Is fixing this issue included in the roadmap? No, for the simple reason that no roadmap exists. The Engineering Steering Committee does not mandate any of the contributors to work on any specific thing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148158] Icons and menus unreadable across Calc and Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=148158 --- Comment #10 from resherw --- In this version, I do not have the issue as initially reported. All menu items and icons appear fine. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148158] Icons and menus unreadable across Calc and Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=148158 resherw changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #9 from resherw --- Yes, I have both Windows and LibreOffice set to dark mode. I'm currently running this version Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152032] Open remote file (ssh/sshfs) does not open file
https://bugs.documentfoundation.org/show_bug.cgi?id=152032 Craig Harding changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=98 ||897 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98897] Open Remote File - Cannot Connect to Server via SSH
https://bugs.documentfoundation.org/show_bug.cgi?id=98897 Craig Harding changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2032 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152032] New: Open remote file (ssh/sshfs) does not open file
https://bugs.documentfoundation.org/show_bug.cgi?id=152032 Bug ID: 152032 Summary: Open remote file (ssh/sshfs) does not open file Product: LibreOffice Version: 7.3.6.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: craigwhard...@protonmail.com Description: Connecting to an ssh/sshfs share using xfce thunar, I previously used to be able to open a file (odt, xlx, docx, etc) remotely and save it properly using libreoffice6. I followed this bug https://bugs.documentfoundation.org/show_bug.cgi?id=98897 as I had this same issue with libreoffice5. When I upgraded to libreoffice6 then it was fixed and files would open and save approproately. Now with libreoffice7 I am back to the same issue as libreoffice5 Steps to Reproduce: 1. Open a ssh/sshfs share/filesystem using xfce4 thunar 2. (double) Click any file associated with libre office to open it on the remote server/share 3. Actual Results: File does not open Expected Results: file should open and user be able to edit it and save file Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.6.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: x11 Locale: en-CA (en_CA.UTF-8); UI: en-US Ubuntu package version: 1:7.3.6-0ubuntu0.22.04.2 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151966] Format not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=151966 --- Comment #3 from Stewart --- Created attachment 183574 --> https://bugs.documentfoundation.org/attachment.cgi?id=183574=edit The file when Re-Openned -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151966] Format not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=151966 --- Comment #2 from Stewart --- Created attachment 183573 --> https://bugs.documentfoundation.org/attachment.cgi?id=183573=edit The file as saved -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152031] Reducing width of RTL table creates "stairway" effect
https://bugs.documentfoundation.org/show_bug.cgi?id=152031 Eyal Rozenberg changed: What|Removed |Added Blocks|121772 |103100 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103100 [Bug 103100] [META] Writer table bugs https://bugs.documentfoundation.org/show_bug.cgi?id=121772 [Bug 121772] [META] Writer nested tables bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121772] [META] Writer nested tables bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=121772 Eyal Rozenberg changed: What|Removed |Added Depends on|152031 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152031 [Bug 152031] Reducing width of RTL table creates "stairway" effect -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103100 Eyal Rozenberg changed: What|Removed |Added Depends on||152031 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152031 [Bug 152031] Reducing width of RTL table creates "stairway" effect -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121772] [META] Writer nested tables bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=121772 Eyal Rozenberg changed: What|Removed |Added Depends on||152031 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152031 [Bug 152031] Reducing width of RTL table creates "stairway" effect -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104444] [META] DOCX (OOXML) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=10 Eyal Rozenberg changed: What|Removed |Added Depends on||152031 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152031 [Bug 152031] Reducing width of RTL table creates "stairway" effect -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Eyal Rozenberg changed: What|Removed |Added Depends on||152031 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152031 [Bug 152031] Reducing width of RTL table creates "stairway" effect -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152031] Reducing width of RTL table creates "stairway" effect
https://bugs.documentfoundation.org/show_bug.cgi?id=152031 Eyal Rozenberg changed: What|Removed |Added Blocks||121772, 43808, 10 --- Comment #4 from Eyal Rozenberg --- The document had originally been imported from MS Word (a DOCX), but had undergone some editing in LO. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=43808 [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL) https://bugs.documentfoundation.org/show_bug.cgi?id=10 [Bug 10] [META] DOCX (OOXML) table-related issues https://bugs.documentfoundation.org/show_bug.cgi?id=121772 [Bug 121772] [META] Writer nested tables bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152031] Reducing width of RTL table creates "stairway" effect
https://bugs.documentfoundation.org/show_bug.cgi?id=152031 Eyal Rozenberg changed: What|Removed |Added OS|All |Linux (All) Hardware|All |x86-64 (AMD64) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152031] Reducing width of RTL table creates "stairway" effect
https://bugs.documentfoundation.org/show_bug.cgi?id=152031 --- Comment #3 from Eyal Rozenberg --- Created attachment 183572 --> https://bugs.documentfoundation.org/attachment.cgi?id=183572=edit Before and after table size reduction Before-and-after pair of partial screenshots. Taken with: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2486d99c6053af1414117faac2c0db18c0d344c4 CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152031] Reducing width of RTL table creates "stairway" effect
https://bugs.documentfoundation.org/show_bug.cgi?id=152031 --- Comment #2 from Eyal Rozenberg --- Sorry, in the attached file the table width starts at 5.00 and you need to reduce it a lower value. Try 4.0". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152031] Reducing width of RTL table creates "stairway" effect
https://bugs.documentfoundation.org/show_bug.cgi?id=152031 --- Comment #1 from Eyal Rozenberg --- If you then undo the change, the "stairway" effect remains, but - switches sides, so that rows are shifted to the left. Wonderful :-( -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152031] New: Reducing width of RTL table creates "stairway" effect
https://bugs.documentfoundation.org/show_bug.cgi?id=152031 Bug ID: 152031 Summary: Reducing width of RTL table creates "stairway" effect Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com Created attachment 183571 --> https://bugs.documentfoundation.org/attachment.cgi?id=183571=edit Document exhibiting the bug Consider the attached file. If you right-click the table, enter the properties dialog and reduce the table with to, say, 5" (it's currently 5.45"), then you get this weird "stairway" effect, where each table row is shifted further and further to one direction - e.g. to the right - with lower lines disappearing entirely off the page. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152030] Allow regular deletion of selection containing an entire generated index/table
https://bugs.documentfoundation.org/show_bug.cgi?id=152030 Eyal Rozenberg changed: What|Removed |Added Summary|Allow deletion of selection |Allow regular deletion of |containing an entire|selection containing an |generated index/table |entire generated ||index/table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152030] Allow deletion of selection containing an entire generated index/table
https://bugs.documentfoundation.org/show_bug.cgi?id=152030 Eyal Rozenberg changed: What|Removed |Added Summary|When selecting content |Allow deletion of selection |before, after and including |containing an entire |a generated index - allow |generated index/table |deletion| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152030] When selecting content before, after and including a generated index - allow deletion
https://bugs.documentfoundation.org/show_bug.cgi?id=152030 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152030] When selecting content before, after and including a generated index - allow deletion
https://bugs.documentfoundation.org/show_bug.cgi?id=152030 Eyal Rozenberg changed: What|Removed |Added Blocks||89606 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=89606 [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=89606 Eyal Rozenberg changed: What|Removed |Added Depends on||152030 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152030 [Bug 152030] When selecting content before, after and including a generated index - allow deletion -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152030] New: When selecting content before, after and including a generated index - allow deletion
https://bugs.documentfoundation.org/show_bug.cgi?id=152030 Bug ID: 152030 Summary: When selecting content before, after and including a generated index - allow deletion Product: LibreOffice Version: 7.0.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com If your document has some regular content, then a generated table or index (e.g. a ToC), then some more content; and if you make a selection starting before and stopping after the table or index - you should be allowed to delete your selection. Instead, if you delete (e.g. by pressing the Delete key on your keyboard) you are told that "Write-protected content cannot be changed". This is: 1. Confusing, since the selection may be very long (dozens of pages) and you don't even know what the message is talking about. 2. Nonsensical, since it's not as though you're trying to delete _part_ of the index or table, you're deleting all of it. so, such deletion should simply be allowed. I'd say that even if you select just whole table/index and nothing else - you should already be allowed to delete it. I believe this behavior has been around since forever, but I don't remember exactly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147938] Crash in: msvcp140.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=147938 --- Comment #6 from Tex2002ans --- I also got crash in current dev: Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 55cd20e6228a06836285c14ca6726adb1bb4ffcb CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded NO CRASH in: - Version: 4.1.6.2 - Build ID: 40ff705089295be5be0aae9b15123f687c05b0a -- You are receiving this mail because: You are the assignee for the bug.
