[Bug 160573] New: Long dual side printing does not work in libreoffice calc
https://bugs.documentfoundation.org/show_bug.cgi?id=160573 Bug ID: 160573 Summary: Long dual side printing does not work in libreoffice calc Product: LibreOffice Version: 7.4.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: azw...@free.fr Description: When I try to print multiple pages using "long side binding" it print with "short side binding" Steps to Reproduce: 1.create a sheet with at least two pages to print 2.select print with option "long side binding" 3.print Actual Results: result is not as expected, print come out with "short side binding" Expected Results: Print should be "long side binding" Reproducible: Always User Profile Reset: Yes Additional Info: = Libreoffice Version Version: 7.4.7.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Debian package version: 4:7.4.7-1+deb12u1 Calc: threaded == Operating system PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/"; SUPPORT_URL="https://www.debian.org/support"; BUG_REPORT_URL="https://bugs.debian.org/"; -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145538] Use range based for loops
https://bugs.documentfoundation.org/show_bug.cgi?id=145538 Aron Budea changed: What|Removed |Added Assignee|ashwani1235ku...@gmail.com |libreoffice-b...@lists.free ||desktop.org Status|ASSIGNED|NEW --- Comment #38 from Aron Budea --- This is a task multiple people can work on at the same time, let's leave it unassigned. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160570] build failure with ICU 75
https://bugs.documentfoundation.org/show_bug.cgi?id=160570 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #3 from Buovjaga --- Build issues should go to dev list, so can you at least post a reference there? https://wiki.documentfoundation.org/QA/BugReport#Not_all_bugs_go_to_Bugzilla -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160572] A code block blocks user input in the version 24.2 help page
https://bugs.documentfoundation.org/show_bug.cgi?id=160572 --- Comment #1 from nobu --- Created attachment 193554 --> https://bugs.documentfoundation.org/attachment.cgi?id=193554&action=edit code block blocks Input -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160572] New: A code block blocks user input in the version 24.2 help page
https://bugs.documentfoundation.org/show_bug.cgi?id=160572 Bug ID: 160572 Summary: A code block blocks user input in the version 24.2 help page Product: LibreOffice Version: 24.2.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tac...@hotmail.co.jp CC: olivier.hal...@libreoffice.org Description: A code block blocks user input in the version 24.2 help page. Steps to Reproduce: 1. Open a help page with a version 24.2 code block. ex. https://help.libreoffice.org/latest/en-US/text/sbasic/shared/01020300.html 2. Scroll down. Actual Results: 3. A basic code block will be placed on top of the top user input control. Expected Results: 3. The controls for user input are always on top. Reproducible: Always User Profile Reset: No Additional Info: (Translate by TexTra) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145538] Use range based for loops
https://bugs.documentfoundation.org/show_bug.cgi?id=145538 Ashwani kumar changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |ashwani1235ku...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160318] Display fails for certain display scales
https://bugs.documentfoundation.org/show_bug.cgi?id=160318 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 --- Comment #10 from Stéphane Guillou (stragu) --- Do you reproduce the same issue with another Desktop Environment, e.g. GNOME? Wondering if it is specific to Unity. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160319] Calc: add constraints on Format Cells - Format Code
https://bugs.documentfoundation.org/show_bug.cgi?id=160319 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Whiteboard| QA:needsComment| --- Comment #1 from Stéphane Guillou (stragu) --- We'd have to define what a "wrong" format is. Users might use any number of combinations of characters for their custom formatting, and we'd risk breaking some workflow. Some might have a format that is specific to their business / systems, with extra literal characters, for which they'd appreciate LO's flexibility. Can you describe what exactly would trigger such a warning? Looking at the Number Format Codes documentation[1], I'm wondering if it's even doable to find a suitable set of rules. (No idea how MSO does it.) Or maybe we just need to have a more obvious direct link to that documentation, instead of having to first go to the dialog's help page. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155774] [Impress][new feature] masters hierarchy / inheritance
https://bugs.documentfoundation.org/show_bug.cgi?id=155774 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160333] Setting extrusion color does not work, if shape geometry is an open line
https://bugs.documentfoundation.org/show_bug.cgi?id=160333 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147240] SLIDESHOW: long text "scroll through" animation starts from the wrong part without Skia (Windows-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=147240 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160327] PPTX: vertical flipped image with applied 3D properties are wrong after round-trip
https://bugs.documentfoundation.org/show_bug.cgi?id=160327 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160325] Page Style - Transparency Gradient has reversed colors on Export to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=160325 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160552] Strg+f replaced by ALT+F - WTF?!!!
https://bugs.documentfoundation.org/show_bug.cgi?id=160552 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160552] Strg+f replaced by ALT+F - WTF?!!!
https://bugs.documentfoundation.org/show_bug.cgi?id=160552 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.
[Bug 157146] Path file locations cannot be altered in Ver 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=157146 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 127592] [META] LibreOffice Basic incl."Option Compatible" modules
https://bugs.documentfoundation.org/show_bug.cgi?id=127592 Bug 127592 depends on bug 156839, which changed state. Bug 156839 Summary: Printing from macro creates empty page instead of the second sheet https://bugs.documentfoundation.org/show_bug.cgi?id=156839 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157146] Path file locations cannot be altered in Ver 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=157146 --- Comment #4 from QA Administrators --- Dear Glen Gordon, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146669] Function request: Calc equivalent of Excel "Converting Decimal Degrees..."
https://bugs.documentfoundation.org/show_bug.cgi?id=146669 --- Comment #5 from QA Administrators --- Dear G Whittaker, 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.
[Bug 156839] Printing from macro creates empty page instead of the second sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=156839 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156839] Printing from macro creates empty page instead of the second sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=156839 --- Comment #5 from QA Administrators --- Dear Gabor Kelemen (allotropia), Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 89343] ~SwXMailMerge() goes into endless SwCache::Check()
https://bugs.documentfoundation.org/show_bug.cgi?id=89343 --- Comment #6 from QA Administrators --- Dear Stephan Bergmann, 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.
[Bug 148304] Using toolbar in Calc to set object line, style, width or colour triggers Assertion `(typeid(*this) == typeid(SfxItemSet)) && "cannot call this on a subclass of SfxItemSet"' failed.
https://bugs.documentfoundation.org/show_bug.cgi?id=148304 --- Comment #3 from QA Administrators --- Dear Buovjaga, 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.
[Bug 145644] FILESAVE XLSX character color in header has changed to white
https://bugs.documentfoundation.org/show_bug.cgi?id=145644 --- Comment #5 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 144981] Insert Hyperlink dialog with artifacts in icons on the left bar (using kf5)
https://bugs.documentfoundation.org/show_bug.cgi?id=144981 --- Comment #7 from QA Administrators --- Dear Rafael Lima, 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.
[Bug 141546] FILESAVE invalid element in style element of family drawing-page
https://bugs.documentfoundation.org/show_bug.cgi?id=141546 --- Comment #2 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141398] Single reference search result should be highlighted (see comment 5 item 2)
https://bugs.documentfoundation.org/show_bug.cgi?id=141398 --- Comment #19 from QA Administrators --- Dear Christian Lehmann, 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.
[Bug 135492] The opening size of new document window is a bit unpredictable
https://bugs.documentfoundation.org/show_bug.cgi?id=135492 --- Comment #9 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 136943] TOOLBAR: Fonts Name Combobox has wrong height
https://bugs.documentfoundation.org/show_bug.cgi?id=136943 --- Comment #8 from QA Administrators --- Dear medmedin2014, 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.
[Bug 104187] Zoom slider position not updated when switching between page views in Print preview
https://bugs.documentfoundation.org/show_bug.cgi?id=104187 --- Comment #9 from QA Administrators --- Dear jlbraga, 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.
[Bug 160088] Conditional formatting not working with dates <1900
https://bugs.documentfoundation.org/show_bug.cgi?id=160088 Bill Maier changed: What|Removed |Added CC||libre.book...@passinbox.com --- Comment #3 from Bill Maier --- I agree with the comments by Werner Tietz and Rafael Lima. I think a question that must be asked is this: should the program allow users to treat dates as raw numeric values? If so then everything is working fine. If not, then when the user enters the condition "[date] > 0" an error should be flagged. For consistency I think dates should not be treated as numbers, but I can see this being defined either way. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160293] When clicking inside a pivot table, GroupedBar Compact hides all its groups except "File" and "Edit"
https://bugs.documentfoundation.org/show_bug.cgi?id=160293 Stéphane Guillou (stragu) changed: What|Removed |Added CC||jl...@mail.com --- Comment #2 from Stéphane Guillou (stragu) --- Justin, you digged a bit into the context sensitivity of the compact Groupedbar. Maybe this one is a more obvious fix than bug 123056? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49994] TABLES : jumps on selecting text in table in big cell on neighboring pages
https://bugs.documentfoundation.org/show_bug.cgi?id=49994 Stéphane Guillou (stragu) changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #17 from Stéphane Guillou (stragu) --- and thanks for the fix! :) Verified. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160293] When clicking inside a pivot table, GroupedBar Compact hides all its groups except "File" and "Edit"
https://bugs.documentfoundation.org/show_bug.cgi?id=160293 Stéphane Guillou (stragu) changed: What|Removed |Added Version|24.2.0.3 release|6.1.0.3 release Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords||implementationError Whiteboard| QA:needsComment| CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Reproduced in 6.1.0.3, likely an implementation error. Also in recent trunk build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 30c6e51fc9cb0fa864e1755271343d847fcced25 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160315] Saving files to SMB3 network shares no longer works
https://bugs.documentfoundation.org/show_bug.cgi?id=160315 Stéphane Guillou (stragu) changed: What|Removed |Added CC||kevin.ott...@enioka.com Status|UNCONFIRMED |NEEDINFO Keywords||possibleRegression Ever confirmed|0 |1 --- Comment #3 from Stéphane Guillou (stragu) --- Which version did you upgrade from? If it is a regression, and if you're up for it, you could bibisect the issue: https://bibisect.libreoffice.org/ @Kevin, maybe you have an idea? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160565] KDE/Qt UI - Program freezes after "save as"
https://bugs.documentfoundation.org/show_bug.cgi?id=160565 --- Comment #1 from Doug B --- This seems to be present on these VCL plugins: qt5, qt6, kf5, kf6. The Gtk related dialogs seemed to work ok. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107200] [META] Writer table and cell selection issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107200 Bug 107200 depends on bug 49994, which changed state. Bug 49994 Summary: TABLES : jumps on selecting text in table in big cell on neighboring pages https://bugs.documentfoundation.org/show_bug.cgi?id=49994 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106773] [META] Writer document canvas view / viewport jump issues
https://bugs.documentfoundation.org/show_bug.cgi?id=106773 Bug 106773 depends on bug 49994, which changed state. Bug 49994 Summary: TABLES : jumps on selecting text in table in big cell on neighboring pages https://bugs.documentfoundation.org/show_bug.cgi?id=49994 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49994] TABLES : jumps on selecting text in table in big cell on neighboring pages
https://bugs.documentfoundation.org/show_bug.cgi?id=49994 Jim Raykowski changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #16 from Jim Raykowski --- Thanks Stéphane for the reminder. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160563] Pasting very long string when editing in the formula input inserts newline(s)
https://bugs.documentfoundation.org/show_bug.cgi?id=160563 --- Comment #4 from Vlad-Mihai Sima --- For clarity, not sure if this should/could be fixed or just the documentation improved or warning added on paste when issues is hit. When trying to figure out if I am doing something wrong I stumbled upon https://wiki.documentfoundation.org/Faq/Calc/022 which does not describe sufficiently the maximum size related issues. Ideally someone understanding the code could update the wiki describing any limitations in a clear language (my current understanding would be "no line can be larger than ~16k and it will be forcefully split if larger"). The most frustrating was that it was really not obvious what was happening (you can for example paste a JSON larger than 16k if it is formatted with new lines and if you do not have any string larger than 16k, because then Calc will just split on the existing newlines). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145042] Calc slows down on filled cells when navigating
https://bugs.documentfoundation.org/show_bug.cgi?id=145042 --- Comment #13 from Armondo Lopez --- I am unable to reproduce this behavior in Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded or Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160342] Unwanted spaces in the printout
https://bugs.documentfoundation.org/show_bug.cgi?id=160342 Aron Budea changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |aron.bu...@gmail.com |desktop.org | Status|NEW |ASSIGNED --- Comment #5 from Aron Budea --- https://gerrit.libreoffice.org/c/core/+/165860 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147240] SLIDESHOW: long text "scroll through" animation starts from the wrong part without Skia (Windows-only)
https://bugs.documentfoundation.org/show_bug.cgi?id=147240 Armondo Lopez changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Armondo Lopez --- Thank you for reporting the bug. I can confirm that the bug is present in Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded as well as Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160571] FILEOPEN: Cropped SVG in .docx file (from winword) is rendered uncropped in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=160571 --- Comment #3 from Fredrik Stock --- Created attachment 193553 --> https://bugs.documentfoundation.org/attachment.cgi?id=193553&action=edit Screenshot of the document in WinWord -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160571] FILEOPEN: Cropped SVG in .docx file (from winword) is rendered uncropped in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=160571 --- Comment #2 from Fredrik Stock --- Created attachment 193552 --> https://bugs.documentfoundation.org/attachment.cgi?id=193552&action=edit PDF export from Writer showing the problem -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160571] FILEOPEN: Cropped SVG in .docx file (from winword) is rendered uncropped in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=160571 --- Comment #1 from Fredrik Stock --- Created attachment 193551 --> https://bugs.documentfoundation.org/attachment.cgi?id=193551&action=edit Sample document from WinWord -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160018] Defined Ranges in a single column with delimiting row corrupted by 7.6.5 (STR comment 5)
https://bugs.documentfoundation.org/show_bug.cgi?id=160018 Caolán McNamara changed: What|Removed |Added Regression By|Caolán McNamara |Henry Castro CC||hcas...@collabora.com -- You are receiving this mail because: You are the assignee for the bug.
[Bug 138571] LibreOffice freezes (often when running inactive in the background)
https://bugs.documentfoundation.org/show_bug.cgi?id=138571 --- Comment #5 from Armondo Lopez --- I'm unable to represent this behavior in Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded or Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded I often leave each version open for days at a time and it's always snappy when I open the window. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160571] New: FILEOPEN: Cropped SVG in .docx file (from winword) is rendered uncropped in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=160571 Bug ID: 160571 Summary: FILEOPEN: Cropped SVG in .docx file (from winword) is rendered uncropped in Writer Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: fred...@eltele.no Description: When a full-sized SVG image is cropped inside a word document, the original image remains in the docx zip and the cropping is done with in the document source. Sometime after 7.6 (problem not present in that version) Writer ignores the cropping and renders the full SVG. The resizing persists, so the vector image is thus smooshed too. Steps to Reproduce: 1. Winword: Insert an SVG image in a new doc 2. Winword: Crop the SVG, save the document 3. Writer: Open saved document Actual Results: The cropped SVG is rendered uncropped. Size transformations are still applied. Expected Results: Image should be rendered cropped. Reproducible: Always User Profile Reset: Yes Additional Info: This does not occur with SVG files added and cropped in Writer. Diff between the relevant xml nodes of a file from Writer and a file from Winword: diff --git "a/.\\graphic-winword.xml" "b/.\\graphic-writer.xml" index 553310a..02081ca 100644 --- "a/.\\graphic-winword.xml" +++ "b/.\\graphic-writer.xml" @@ -2,36 +2,32 @@ http://schemas.openxmlformats.org/drawingml/2006/picture";> http://schemas.openxmlformats.org/drawingml/2006/picture";> - - + + + + - + http://schemas.microsoft.com/office/drawing/2016/SVG/main"; r:embed="rId3"/> - - + + + + - + - - - - - -http://schemas.microsoft.com/office/drawing/2010/main"/> - - -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103182] [META] GTK3-specific bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103182 Bug 103182 depends on bug 160562, which changed state. Bug 160562 Summary: Colibre's Images icon looks too dark shaded when insensitive in the Navigator (gtk3) https://bugs.documentfoundation.org/show_bug.cgi?id=160562 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 117497] [META] Colibre icons
https://bugs.documentfoundation.org/show_bug.cgi?id=117497 Bug 117497 depends on bug 160562, which changed state. Bug 160562 Summary: Colibre's Images icon looks too dark shaded when insensitive in the Navigator (gtk3) https://bugs.documentfoundation.org/show_bug.cgi?id=160562 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103030] [META] Navigator sidebar deck and floating window (also "Target in Document")
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Bug 103030 depends on bug 160562, which changed state. Bug 160562 Summary: Colibre's Images icon looks too dark shaded when insensitive in the Navigator (gtk3) https://bugs.documentfoundation.org/show_bug.cgi?id=160562 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160562] Colibre's Images icon looks too dark shaded when insensitive in the Navigator (gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=160562 Caolán McNamara changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160562] Colibre's Images icon looks too dark shaded when insensitive in the Navigator (gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=160562 Commit Notification changed: What|Removed |Added Whiteboard||target:24.8.0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160570] build failure with ICU 75
https://bugs.documentfoundation.org/show_bug.cgi?id=160570 Rene Engelhard changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=49 ||885 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49885] sync custom breakiterator rules with icu originals
https://bugs.documentfoundation.org/show_bug.cgi?id=49885 Rene Engelhard changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||8108 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49885] sync custom breakiterator rules with icu originals
https://bugs.documentfoundation.org/show_bug.cgi?id=49885 Rene Engelhard changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0570 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158108] Build failure with ICU 74
https://bugs.documentfoundation.org/show_bug.cgi?id=158108 Rene Engelhard changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=49 ||885 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140634] calc: date values: problems with change from julian to gregorian calendar, fill functions fail
https://bugs.documentfoundation.org/show_bug.cgi?id=140634 --- Comment #4 from Armondo Lopez --- I'm unable to produce the same behavior in Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded or Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160570] build failure with ICU 75
https://bugs.documentfoundation.org/show_bug.cgi?id=160570 --- Comment #2 from Rene Engelhard --- In googling for the error I saw https://listarchives.libreoffice.org/global/dev/2012/msg05518.html ff. and the committed https://cgit.freedesktop.org/libreoffice/core/commit/?id=43084e8b30c101a44510b7a8267d5c2b316a17bb where something like this was an issue for icu 49. But I don't think the solution there applies here, does it? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160554] Crashes when creating a new Writer document or opening an existing one.
https://bugs.documentfoundation.org/show_bug.cgi?id=160554 --- Comment #4 from Armondo Lopez --- (In reply to Armondo Lopez from comment #3) > I'm unable to reproduce this behavior in > > Version: 24.2.1.2 (X86_64) / LibreOffice Community > Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac > CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: > win > Locale: en-US (en_US); UI: en-US > Calc: threaded > > or > > Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community > Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb > CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: > win > Locale: en-US (en_US); UI: en-US > Calc: threaded Please disregard this, I didn't see the version listed. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160554] Crashes when creating a new Writer document or opening an existing one.
https://bugs.documentfoundation.org/show_bug.cgi?id=160554 --- Comment #3 from Armondo Lopez --- I'm unable to reproduce this behavior in Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded or Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
libreoffice-bugs@lists.freedesktop.org
https://bugs.documentfoundation.org/show_bug.cgi?id=160536 raal changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||r...@post.cz --- Comment #3 from raal --- Setting to NEW. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160537] Support sheet protection option: Edit objects
https://bugs.documentfoundation.org/show_bug.cgi?id=160537 raal changed: What|Removed |Added CC||r...@post.cz Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from raal --- Setting to NEW. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160535] Support sheet protection option: Use AutoFilter
https://bugs.documentfoundation.org/show_bug.cgi?id=160535 raal changed: What|Removed |Added Ever confirmed|0 |1 CC||r...@post.cz Status|UNCONFIRMED |NEW --- Comment #4 from raal --- Setting to NEW. Should bug 122921 be closed? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160570] build failure with ICU 75
https://bugs.documentfoundation.org/show_bug.cgi?id=160570 --- Comment #1 from Rene Engelhard --- ICU 75.1 rc1 that is but I doubt there will be behaviour changes until its final so we need to do something about that anyways -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160570] build failure with ICU 75
https://bugs.documentfoundation.org/show_bug.cgi?id=160570 Rene Engelhard changed: What|Removed |Added Blocks||149092 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149092 [Bug 149092] [META] Bugs and enhancements related to ICU -- You are receiving this mail because: You are the assignee for the bug.
[Bug 149092] [META] Bugs and enhancements related to ICU
https://bugs.documentfoundation.org/show_bug.cgi?id=149092 Rene Engelhard changed: What|Removed |Added Depends on||160570 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160570 [Bug 160570] build failure with ICU 75 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160570] build failure with ICU 75
https://bugs.documentfoundation.org/show_bug.cgi?id=160570 Rene Engelhard changed: What|Removed |Added Summary|build failure with ICU 75.1 |build failure with ICU 75 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158108] Build failure with ICU 74
https://bugs.documentfoundation.org/show_bug.cgi?id=158108 Rene Engelhard changed: What|Removed |Added Blocks||160570 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160570 [Bug 160570] build failure with ICU 75.1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160570] build failure with ICU 75.1
https://bugs.documentfoundation.org/show_bug.cgi?id=160570 Rene Engelhard changed: What|Removed |Added Depends on||158108 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158108 [Bug 158108] Build failure with ICU 74 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160570] build failure with ICU 75.1
https://bugs.documentfoundation.org/show_bug.cgi?id=160570 Rene Engelhard changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||8108 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158108] Build failure with ICU 74
https://bugs.documentfoundation.org/show_bug.cgi?id=158108 Rene Engelhard changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0570 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160570] New: build failure with ICU 75.1
https://bugs.documentfoundation.org/show_bug.cgi?id=160570 Bug ID: 160570 Summary: build failure with ICU 75.1 Product: LibreOffice Version: 24.8.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: r...@debian.org Description: [tried on master but will also get a problem on 24.2 ] Debian just got ICU 75.1 in experimental and after the ICU 74 suprise (which is still not fixed :/) I unfortunately need to say that this breaks again. (after applying the patch for ICU 74.1 (see https://bugs.documentfoundation.org/show_bug.cgi?id=158108): [build BRK] CustomTarget/i18npool/breakiterator/sent.brk S=/home/rene/LibreOffice/git/master && I=$S/instdir && W=$S/workdir && /usr/bin/genbrk -r $S/i18npool/source/breakiterator/data/sent.txt -o $W/CustomTarget/i18npool/breakiterator/sent.brk createRuleBasedBreakIterator: ICU Error "U_BRK_RULE_EMPTY_SET" at line 109, column 1 make[2]: *** [/home/rene/LibreOffice/git/master/i18npool/CustomTarget_breakiterator.mk:92: /home/rene/LibreOffice/git/master/workdir/CustomTarget/i18npool/breakiterator/sent.brk] Error 11 rm /home/rene/LibreOffice/git/master/workdir/CustomTarget/i18npool/breakiterator/dict_word_nodash.brk /home/rene/LibreOffice/git/master/workdir/CustomTarget/i18npool/breakiterator/dict_word.brk /home/rene/LibreOffice/git/master/workdir/CustomTarget/i18npool/breakiterator/dict_word_hu.brk /home/rene/LibreOffice/git/master/workdir/CustomTarget/i18npool/breakiterator/count_word.brk /home/rene/LibreOffice/git/master/workdir/CustomTarget/i18npool/breakiterator/edit_word_he.brk /home/rene/LibreOffice/git/master/workdir/CustomTarget/i18npool/breakiterator/edit_word_hu.brk /home/rene/LibreOffice/git/master/workdir/CustomTarget/i18npool/breakiterator/dict_word_prepostdash.brk /home/rene/LibreOffice/git/master/workdir/CustomTarget/i18npool/breakiterator/dict_word_he.brk /home/rene/LibreOffice/git/master/workdir/CustomTarget/i18npool/breakiterator/line.brk /home/rene/LibreOffice/git/master/workdir/CustomTarget/i18npool/breakiterator/edit_word.brk make[2]: Leaving directory '/home/rene/LibreOffice/git/master' make[1]: *** [Makefile:278: build] Error 2 make[1]: Leaving directory '/home/rene/LibreOffice/git/master' https://cgit.freedesktop.org/libreoffice/core/tree/i18npool/source/breakiterator/data/sent.txt#n109 is the failing rule. What should we do with this one? Steps to Reproduce: 1. install ICU 75.1 2. build LO with system-icu Actual Results: createRuleBasedBreakIterator: ICU Error "U_BRK_RULE_EMPTY_SET" at line 109, column 1 Expected Results: builds Reproducible: Always User Profile Reset: No Additional Info: - -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160299] Improper display of boolean cell value stats in LibreOffice Calc status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=160299 --- Comment #5 from ady --- (In reply to Stéphane Guillou (stragu) from comment #3) > (e.g. M1:N2 sum in sample ODS should be 4 in status bar) I disagree. If the original request in comment 0 (i.e. show FALSE when relevant) cannot be implemented, I would _not_ change the current behavior of showing TRUE in order to always show a number. There is no point in changing a behavior that might be useful to some users (and it is already implemented) just because the counter-part cannot be implemented too. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160569] Dotted line is wrongly rendered in presentation mode if Skia is disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=160569 --- Comment #1 from Regina Henschel --- Created attachment 193550 --> https://bugs.documentfoundation.org/attachment.cgi?id=193550&action=edit Screenshot of rendering with and without Skia -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160569] New: Dotted line is wrongly rendered in presentation mode if Skia is disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=160569 Bug ID: 160569 Summary: Dotted line is wrongly rendered in presentation mode if Skia is disabled Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 193549 --> https://bugs.documentfoundation.org/attachment.cgi?id=193549&action=edit example document with dotted lines Open the attached document. In edit mode you see two dotted Bezier curves. Start presentation mode. If Skia is disabled the rendering is wrong. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 152336] Improve CSV field separator detection/behavior when several separators are selected on import
https://bugs.documentfoundation.org/show_bug.cgi?id=152336 --- Comment #11 from Commit Notification --- Gabriel Masei committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/2feda8ba21acdcf33a9b4ba94742f574c17839bd tdf#152336 Detect charset and separators for csv files It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 152336] Improve CSV field separator detection/behavior when several separators are selected on import
https://bugs.documentfoundation.org/show_bug.cgi?id=152336 Commit Notification changed: What|Removed |Added Whiteboard||target:24.8.0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160568] Is it possible to have .dll files be signed by a publisher for WDAC (Windows Defender Application Control)?
https://bugs.documentfoundation.org/show_bug.cgi?id=160568 Mike Kaganski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||cl...@documentfoundation.or ||g --- Comment #1 from Mike Kaganski --- Yes, cli_* assemblies are not signed, unlike the DLLs in the program files. Christian: is there a reason why we don't sign them? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160568] New: Is it possible to have .dll files be signed by a publisher for WDAC (Windows Defender Application Control)?
https://bugs.documentfoundation.org/show_bug.cgi?id=160568 Bug ID: 160568 Summary: Is it possible to have .dll files be signed by a publisher for WDAC (Windows Defender Application Control)? Product: LibreOffice Version: 7.6.6.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bz.32...@silomails.com Description: I have WDAC (Windows Defender Application Control) setup and during installation it fails because .dll files used at location: C:\Windows\assembly\tmp\XX\ during installation are blocked because they are not signed by a publisher. Below are examples of files WDAC complains about but I didn't go through each file (so there are additional files that need to be signed not including the below) examples: C:\Windows\assembly\tmp\XX\cli_basetypes.dll C:\Windows\assembly\tmp\XX\cli_ure.dll C:\Windows\assembly\tmp\XX\cli_uretypes.dll C:\Windows\assembly\tmp\XX\cli_uretypes.dll C:\Windows\assembly\tmp\XX\\policy.1.0.cli_basetypes.dll etc. Note: XX changes on a per install basis, I think LibreOffice being installed: LibreOffice_7.6.6_Win_x86-64 (non-enthusiast version) Windows 11 23H2 Thank you Actual Results: Install fails Expected Results: Install succeeds Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US 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.
[Bug 115474] Applying autoformat to a large number of cells takes too long (with row-alternate shading)
https://bugs.documentfoundation.org/show_bug.cgi?id=115474 --- Comment #7 from libruser --- Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 8; OS: macOS 11.7.1; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded in 24.2.2.2 (X86_64) / LibreOffice Community columns A-E take long, but format succeeds. Bug marked duplicate 124341 may not be a duplicate. "Selecting only part of the document works as intended." #124341 still fails. Difference in repro steps is "select all", instead of Columns A-E. This implies that the code is now more efficient, but not scalable to the default number of cells. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160557] High display scaling results in squeezed tabbed interface and slightly smaller icons
https://bugs.documentfoundation.org/show_bug.cgi?id=160557 --- Comment #6 from V Stuart Foote --- Don't think we can say the icons are resized. That is manifestation of differing dpi as the os/DE UI is being scaled. Only issue seems to be the inconsistent ratios at which the priority horizontal sizing asserts. Both in hiding NB widgets, but also the shift to the "compressed" padding for the tab labels. Other than issue of the ratio, seems more a dupe of see also bug 144134 suggesting incremental reduction in padding the NB tab labels. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160557] High display scaling results in squeezed tabbed interface and slightly smaller icons
https://bugs.documentfoundation.org/show_bug.cgi?id=160557 V Stuart Foote changed: What|Removed |Added Version|6.2.5.2 release |6.1.0.3 release CC||jl...@mail.com, ||szymon.k...@collabora.com --- Comment #5 from V Stuart Foote --- Is the .UI padding collapse being controlled by PriorityHBox sizing of vclHbox [1]? But then the inconsistent ratio comes from misread of os/DE scaling or pixel size calculation? =-ref-= [1] https://opengrok.libreoffice.org/xref/core/vcl/source/control/PriorityHBox.cxx?r=b595a93f#108 @Justin, Szymon any cycles to mull over this, and see also bug 144134? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160567] Impress templates: style A4 is duplicate and style A0 is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=160567 Laurent Balland changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |jumbo4...@yahoo.fr |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160567] New: Impress templates: style A4 is duplicate and style A0 is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=160567 Bug ID: 160567 Summary: Impress templates: style A4 is duplicate and style A0 is missing Product: LibreOffice Version: 7.0.6.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: trivial Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jumbo4...@yahoo.fr Description: Follow-up of tdf#158488: All Impress templates contain in their styles.xml file two identical A4 styles, and no A0 style Steps to Reproduce: 1. Open styles.xml in a bundled template 2. 3. Actual Results: There is two A4 styles, no A0 style Expected Results: A0 style with size 48 Reproducible: Always User Profile Reset: No Additional Info: d -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160566] formula object crops subscript
https://bugs.documentfoundation.org/show_bug.cgi?id=160566 --- Comment #2 from potassi...@protonmail.com --- Created attachment 193548 --> https://bugs.documentfoundation.org/attachment.cgi?id=193548&action=edit single character formula subscript cropped -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160566] formula object crops subscript
https://bugs.documentfoundation.org/show_bug.cgi?id=160566 --- Comment #1 from potassi...@protonmail.com --- Created attachment 193547 --> https://bugs.documentfoundation.org/attachment.cgi?id=193547&action=edit some examples of cropped subscript -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160566] New: formula object crops subscript
https://bugs.documentfoundation.org/show_bug.cgi?id=160566 Bug ID: 160566 Summary: formula object crops subscript Product: LibreOffice Version: 7.6.5.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: potassi...@protonmail.com Description: When I try to create a formula object with a single character and add a subscript, the subscript gets cropped. This also affects fractions, in this case, the subscript on the denominator is cropped. Steps to Reproduce: 1.open libreoffice writer 2.create a single character formula object with subcript Actual Results: formula object with cropped subscript appear Expected Results: subscript should not be cropped Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: ko Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160384] Writer: Opening & editing large files requires an unreasonable response time (many minutes).
https://bugs.documentfoundation.org/show_bug.cgi?id=160384 Greg changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113825] [META] Wizard bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113825 Bug 113825 depends on bug 75218, which changed state. Bug 75218 Summary: Letter Wizard does not respect locale anymore https://bugs.documentfoundation.org/show_bug.cgi?id=75218 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 75218] Letter Wizard does not respect locale anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=75218 Laurent Balland changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME CC||jumbo4...@yahoo.fr --- Comment #32 from Laurent Balland --- The page size of wizard documents is local dependent since LibO 7.5 and resolution of tdf#143956 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160557] High display scaling results in squeezed tabbed interface and slightly smaller icons
https://bugs.documentfoundation.org/show_bug.cgi?id=160557 --- Comment #4 from Rob --- Created attachment 193546 --> https://bugs.documentfoundation.org/attachment.cgi?id=193546&action=edit Difference between 100% and 200% scaling, with pixel measurements That's incredibly useful and interesting. Having done further testing with the scale set to 100%, 125%, 150%, 175%, and 200%, I am certain that it must be a scaling issue rather than merely a problem with the tabbed interface resizing poorly due to the available horizontal space. My device has a resolution of 2736 x 1824 px. At 100% scaling, I obtain the exact results you obtained (https://bug-attachments.documentfoundation.org/attachment.cgi?id=174702). Namely, that there is an adequate amount of padding at full screen (in my case 2736px), which is kept the same until you reach 1140px. Anything lower than that, and the Tabbed UI's padding will be reduce to merely the text. To check whether the removed padding was the result of available horizontal space or scaling, I measured the horizontal length of the tabs themselves at different scales. What follows are my results: At 100% scale: - Full width is 2736px - Padding is constant until 1140px (anything below, and the padding is drastically reduced) At 125% scale: - Full width is 2188px - Padding is constant until 913px At 150% scale: - Full width is 1824px - Padding is already reduced, but tabs aren't fully collapsed until 819px At 175% scale: - Full width is 1563px - Padding is already reduced, but tabs aren't fully collapsed until 715px At 200% scale: - Full width is 681px - Padding is already reduced, but tabs aren't fully collapsed until 681px It's worth noting that, already, anything above 125% results in the tabs having no padding. I have attached another picture (scaling_issue.jpg) to better illustrate the problem, with pixel count labelled (measured with pixel ruler). Indeed, it is very odd that, while scaled to 100%, the padding is present until 1140px, but at 200% scale, even with 681px (which is greater than the equivalent 570px), the padding is already gone and the collapsed tabs simply appear more even more compressed. In other words, even when there is more horizontal space than would be equivalently available at 100% scaling, the Tabbed UI makes no use of this space. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160562] Colibre's Images icon looks too dark shaded when insensitive in the Navigator (gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=160562 Caolán McNamara changed: What|Removed |Added Status|NEW |ASSIGNED Summary|Colibre's Images icon uses |Colibre's Images icon looks |wrong shade (dark variant) |too dark shaded when |in the Navigator (gtk3) |insensitive in the ||Navigator (gtk3) --- Comment #2 from Caolán McNamara --- This image is icon-themes/colibre/cmd/sc_insertgraphic.png I don't think it is actually the dark variant, which is icon-themes/colibre_dark/cmd/sc_insertgraphic.png I think because its mostly explicitly white (and not transparent like the other) that when gtk makes it insensitive it appears mostly gray and too dark beside the others. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155774] [Impress][new feature] masters hierarchy / inheritance
https://bugs.documentfoundation.org/show_bug.cgi?id=155774 Laurent Balland changed: What|Removed |Added CC||jumbo4...@yahoo.fr --- Comment #2 from Laurent Balland --- I do not agree to automatically modify the format of all the titles of different master pages, because in different master pages you may need different contrast and size according to the position and size of objects. For instance, Blue Curve template needs a dark title for the first master page and a light one for the second. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160299] Improper display of boolean cell value stats in LibreOffice Calc status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=160299 Stéphane Guillou (stragu) changed: What|Removed |Added Hardware|x86-64 (AMD64) |All Version|24.2.1.2 release|Inherited From OOo OS|Windows (All) |All CC||er...@redhat.com --- Comment #4 from Stéphane Guillou (stragu) --- erack, what's your opinion? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160299] Improper display of boolean cell value stats in LibreOffice Calc status bar
https://bugs.documentfoundation.org/show_bug.cgi?id=160299 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org --- Comment #3 from Stéphane Guillou (stragu) --- Created attachment 193545 --> https://bugs.documentfoundation.org/attachment.cgi?id=193545&action=edit sample ODS The behaviour is inherited from OOo, I see the same in OOo 3.3. >From what ady explained, I think the current distinction makes some sense. However, there is some inconsistency between the result of the function in cell and the status bar: Average() and Sum() always return numeric data, even for a single TRUE value as input. Shouldn't the status bar always match that? Another inconsistency is that the status bar returns boolean values if a range is selected with the cell cursor on a FALSE cell (see attached spreadsheet, select range B1:B2 starting from B2). Why not numeric, if a 0 is shown when a single FALSE cell is selected? I think I am leaning toward the most transparent, consistent and useful: always show a numeric value in the status bar. (e.g. M1:N2 sum in sample ODS should be 4 in status bar) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160313] Template not correctly rendered when saved to PowerPoint
https://bugs.documentfoundation.org/show_bug.cgi?id=160313 Laurent Balland changed: What|Removed |Added Summary|Possible instability in |Template not correctly |Impress |rendered when saved to ||PowerPoint -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160545] LO Writer not saving hyperlink in docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=160545 --- Comment #3 from arthur2024 --- OS is Linux Mint 21.3 Cinnamon. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160313] Possible instability in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=160313 Laurent Balland changed: What|Removed |Added CC||jumbo4...@yahoo.fr Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #4 from Laurent Balland --- (In reply to Peter Fletcher from comment #0) > I first used Focus with the colours just in the > corners however after saving and re-opening the colours then covered most of > the slide. I reworked using Blue Curve this time on re-opening the top blue > curve disappeared and left a white lettered heading which was very difficult > to change to black. It seems that the master slide was changed to the first one. I was not able to reproduce. Saving in PPT produced no bug for me for these two templates. Saving in PPTX, I got black text for placeholders where I did not entered text, which is a totally different bug. Please detail your procedure, and give your exact version, as suggested by m_a_riosv > Please paste here the information on Menu/Help/About LibreOffice (There is an > icon to copy) -- You are receiving this mail because: You are the assignee for the bug.
