[Libreoffice-bugs] [Bug 157319] LibreOffice after version 7.5.0.3 Refuses To Install On Window 11 Pro.
https://bugs.documentfoundation.org/show_bug.cgi?id=157319 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report. Are you still experiencing this issue with the latest releases, currently 7.5.7.1 and 7.6.2.1? Quite a few bugs have been fixed since then. Please also try backing up and removing your user profile to see if it is linked: https://wiki.documentfoundation.org/UserProfile -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157309] Crash in: SwContentFrame::MakeAll(OutputDevice *) after loading document
https://bugs.documentfoundation.org/show_bug.cgi?id=157309 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #6 from Stéphane Guillou (stragu) --- (In reply to Yves Poissant from comment #4) > I just tried loading the document in version 24.2.0.0.alpha0+ and it didn't > crash. Thanks for testing the daily build. Can you please also update to version 7.6.2.1 and see if it is resolved there too? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 48213] EDITING: Number (ful context) references are rendered as plain "n", omitting the "after" data stablished in "Options" tab from "Bullets and Numbering" dialog.
https://bugs.documentfoundation.org/show_bug.cgi?id=48213 --- Comment #16 from peterpan --- Still present in: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: cs-CZ Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147906] Use hypot function for Pythagorean addition
https://bugs.documentfoundation.org/show_bug.cgi?id=147906 --- Comment #27 from Commit Notification --- Ankit_Jaipuriar committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/89367021a4c960b6873370ea9472b36457c51ef3 tdf#147906 Use std::hypot for Pythagorean addition It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157016] Calc can't set different values for 'overlap' and'spacing' parameters for primary and secondary axes in the 'data series' options
https://bugs.documentfoundation.org/show_bug.cgi?id=157016 --- Comment #22 from Piotr Osada --- (In reply to Stéphane Guillou (stragu) from comment #21) > From your attachment 189294 [details], I understand that MS Office is able > to keep those overlap/spacing settings as they are when saving as XLSX? Right, MS Office keeps those settings for both axes separately in XLSX. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154929] [META] Accessibility Check sidebar deck, Automatic Accessibility Checking
https://bugs.documentfoundation.org/show_bug.cgi?id=154929 Bug 154929 depends on bug 157370, which changed state. Bug 157370 Summary: A11y sidebar: Highlight item when clicking on issue https://bugs.documentfoundation.org/show_bug.cgi?id=157370 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157505] Data > XML Source . Cannot import record level
https://bugs.documentfoundation.org/show_bug.cgi?id=157505 --- 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 157505] Data > XML Source . Cannot import record level
https://bugs.documentfoundation.org/show_bug.cgi?id=157505 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157471] Display error in form text fields
https://bugs.documentfoundation.org/show_bug.cgi?id=157471 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157471] Display error in form text fields
https://bugs.documentfoundation.org/show_bug.cgi?id=157471 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157255] feature [Draw] Color option to identify the layer
https://bugs.documentfoundation.org/show_bug.cgi?id=157255 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157348] Bad font rendering with 7.5 and higher because freetype interpreter-version is ignored
https://bugs.documentfoundation.org/show_bug.cgi?id=157348 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157305] [1] Feature request: linking sections without changing order of lists
https://bugs.documentfoundation.org/show_bug.cgi?id=157305 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157255] feature [Draw] Color option to identify the layer
https://bugs.documentfoundation.org/show_bug.cgi?id=157255 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156964] Support idiom of title bar moving up or down according to main box contents
https://bugs.documentfoundation.org/show_bug.cgi?id=156964 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156964] Support idiom of title bar moving up or down according to main box contents
https://bugs.documentfoundation.org/show_bug.cgi?id=156964 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156510] Support list styles or paragraph styles "not sticking" when the style in the other category changes
https://bugs.documentfoundation.org/show_bug.cgi?id=156510 --- 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 155263] Need a increasing-by-appearance sequence field with an initial value property
https://bugs.documentfoundation.org/show_bug.cgi?id=155263 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154051] Support table (cell) border transparency
https://bugs.documentfoundation.org/show_bug.cgi?id=154051 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114031] [META] LibreOffice Snap/Snappy package bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=114031 Bug 114031 depends on bug 153947, which changed state. Bug 153947 Summary: On RHEL Server 7.9, Libreoffice 7.5.1.2 crashes immediately with osl::Thread::create failed https://bugs.documentfoundation.org/show_bug.cgi?id=153947 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103266] [META] Command line bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103266 Bug 103266 depends on bug 153947, which changed state. Bug 153947 Summary: On RHEL Server 7.9, Libreoffice 7.5.1.2 crashes immediately with osl::Thread::create failed https://bugs.documentfoundation.org/show_bug.cgi?id=153947 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153947] On RHEL Server 7.9, Libreoffice 7.5.1.2 crashes immediately with osl::Thread::create failed
https://bugs.documentfoundation.org/show_bug.cgi?id=153947 --- Comment #5 from QA Administrators --- Dear david, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153674] book editing -- Master Document inner Title property overrides section titles
https://bugs.documentfoundation.org/show_bug.cgi?id=153674 --- Comment #4 from QA Administrators --- Dear peter josvai, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154573] Toolbars don't persist
https://bugs.documentfoundation.org/show_bug.cgi?id=154573 --- Comment #2 from QA Administrators --- Dear Tom Franczak, 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 153608] Crash in: libc.so.6
https://bugs.documentfoundation.org/show_bug.cgi?id=153608 --- Comment #4 from QA Administrators --- Dear acelere, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153385] Crash in: libc.so.6
https://bugs.documentfoundation.org/show_bug.cgi?id=153385 --- Comment #3 from QA Administrators --- Dear Steve Kelem, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135489] Image caption numbering shows 1 or inconsistent on copy paste to new or same document
https://bugs.documentfoundation.org/show_bug.cgi?id=135489 --- Comment #8 from QA Administrators --- Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154290] crash if I open page layout , under more options and under area tab , , clicking none crashes app
https://bugs.documentfoundation.org/show_bug.cgi?id=154290 --- Comment #2 from QA Administrators --- Dear Abhishek, 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 154289] WRITER: Enabling outline folding disables character style application
https://bugs.documentfoundation.org/show_bug.cgi?id=154289 --- Comment #4 from QA Administrators --- Dear ajlittoz, 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 92193] Window re-drawn at old position after opening file (un-doing user action to move it)
https://bugs.documentfoundation.org/show_bug.cgi?id=92193 --- Comment #16 from QA Administrators --- Dear Jim Avera, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80713] Missing string reference keys [KeyID] in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=80713 --- Comment #28 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 47773] EDITING embedded OLE EXCEL Spreadheet in particular .ppt moves view area after object has been left
https://bugs.documentfoundation.org/show_bug.cgi?id=47773 --- Comment #14 from QA Administrators --- Dear sasha.libreoffice, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 48213] EDITING: Number (ful context) references are rendered as plain "n", omitting the "after" data stablished in "Options" tab from "Bullets and Numbering" dialog.
https://bugs.documentfoundation.org/show_bug.cgi?id=48213 --- Comment #15 from QA Administrators --- Dear Rainer Hurtado Navarro, 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 44946] Editing Microsoft Equation 3.0 equations imported from Word loses Greek characters ( steps in comment 4 )
https://bugs.documentfoundation.org/show_bug.cgi?id=44946 --- Comment #18 from QA Administrators --- Dear Orion Poplawski, 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 119772] insert field always goes to layout layer, even if it is not the active layer and despite layout layer is locked
https://bugs.documentfoundation.org/show_bug.cgi?id=119772 --- Comment #5 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118200] frame of 100% relative height can't be set to 'wrap: none', switches to 'wrap: through' by itself
https://bugs.documentfoundation.org/show_bug.cgi?id=118200 --- Comment #5 from QA Administrators --- Dear Yury, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115040] Conditional formatting "between" - incorrect tab order
https://bugs.documentfoundation.org/show_bug.cgi?id=115040 --- Comment #8 from QA Administrators --- Dear Dan Dascalescu, 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 156980] "Delete chapter" error message and action in relation to folded headings is inverted in Navigator context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156980 --- Comment #6 from Jim Raykowski --- (In reply to sdc.blanco from comment #0) > > Test 1: > 1. Place cursor in ”Heading Level 2 – folded” > 2. Use Navigator, right-click on ”Heading Level 1 – open”, choose ”Delete > Heading” > > Actual: Dialog box appears, with ”You are trying to delete folded (hidden) > content.” > Expected: Either heading and text is deleted or request a confirm before > deleting. I repro this bug. > Test 2: > 1. Fold outline of ”Heading Level 1” > 2. Place cursor in Heading Level 2. > 3. Use Navigator, right-click on ”Heading Level 1 – open”, choose ”Delete > Heading” > > Actual: Nothing happens. > Expected: In light of test 1, I now would expect to get the dialog box that > appeared in test 1. After I set outline folding not to include sub levels I was able to repro this. I agree that the dialog box should be shown. > Test 3: > > 1. Use Navigator, right-click on "Heading Level 2 - folded", choose > "Delete Heading" > > Actual and expected: Get error message about trying to delete hidden content To repro this, I needed to first fold "Heading Level 2 - folded". Reading comment 2, I see you had clarified this. > I think there is one more variation (that I cannot always repeat) where I > add a new heading, and the first time I get the error dialog, then I toggle > the heading closed and open, and then it is deleted. I'll look into why Test 1 and 2 don't show the dialog box. Same happens when the "Instructions:" heading is folded. I wonder if this has always been the behavior or if something has changed that has caused this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51330] FILEOPEN: Vertical Text in .pptx becomes horizontal when imported
https://bugs.documentfoundation.org/show_bug.cgi?id=51330 --- Comment #19 from Volga --- (In reply to Regina Henschel from comment #18) > The text is not in a drawing shape but in a presentation object (here > title). Such presentation objects are not able to rotate the text > independent from the shape rotation. > An alternative would be a writing-mode setting similar as available in > frames in Writer. But the needed values are not implemented in Draw/Impress > at all. So you have to fix bug 104835 and bug 103720 first, then it's possible to add compatibilities for PPT/PPTX. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157556] Incorrect image link leads to corrupted document AFTER being saved in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=157556 Kira Tubo changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected CC||kira.t...@gmail.com, ||qui...@gmail.com --- Comment #4 from Kira Tubo --- Bibisected win64-7.3. Added Tomaž Vajngerl to cc. Regression occurring at: https://git.libreoffice.org/core/+/2bfad80805c248b47d099c1707ce4f1926867b82 - commit 2bfad80805c248b47d099c1707ce4f1926867b82[log] author Tomaž Vajngerl Wed Jul 20 22:01:31 2022 +0200 committer Xisco Fauli Wed Jul 27 16:48:14 2022 +0200 tree9fd3033fbbb3696698665ed1906e693ed3b0a245 parent d4f5877a6a9bb5cbe70c5d60634aabe1282b96af [diff] -- a0cf2b657093950abcebc063c38a83761efb0008 is the first bad commit commit a0cf2b657093950abcebc063c38a83761efb0008 Author: Norbert Thiebaud Date: Wed Jul 27 07:57:25 2022 -0700 source sha:2bfad80805c248b47d099c1707ce4f1926867b82 --- Reproduced on: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: dd7fc07f83416a3d8a444947b7d28f7347520d6a CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157556] Incorrect image link leads to corrupted document AFTER being saved in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=157556 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Keywords||bibisectRequest, regression --- Comment #3 from m.a.riosv --- Reproducible with: Version: 7.4.7.2 (x64) / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL and Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded and Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9eb419b0b0f019f5fbc48ff1a11977e8b041edee CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo regression from (not reproducible with): Version: 7.2.7.2 (x64) / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157567] New: Text disappears from slides in Impress slide decks after file is saved and reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=157567 Bug ID: 157567 Summary: Text disappears from slides in Impress slide decks after file is saved and reopened Product: LibreOffice Version: 7.4.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: roncte...@gmail.com Created attachment 189966 --> https://bugs.documentfoundation.org/attachment.cgi?id=189966&action=edit slide deck with disappearing text In some slides decks text entered on a slides is not being saved. The text appears on the slide after saving for as long as the deck is open but if you close the file and reopen it, on some slides, text that was entered is no longer there. Re-adding text to slides where it was missing, saving the file, closing the file and reopening the file results in the same behavior, the text that was re-added is missing again. If however you re-add the missing text to an affected slide, make a copy of the slide, save the file, close the file, open the file again, the re-added text remains on the copy of the affected slide but is missing again on the original affected slide. Attached is a slide deck displaying this behavior. The hidden slides are the ones effected by the disappearing text bug. The slides immediately following the hidden slides are copies of the corrected versions of the affected slides. The bug can be reproduced by editing the hidden slides to make them look like the slides that immediately follow then, save the file, close the file, reopen the file. The hidden slides will have the text that was added missing where the copies of the slides will remain unaffected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157566] Data lost or misplaced when pasting into Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=157566 Stan Troeh changed: What|Removed |Added CC||stantr...@gmail.com --- Comment #1 from Stan Troeh --- Created attachment 189965 --> https://bugs.documentfoundation.org/attachment.cgi?id=189965&action=edit Zipped Win32 executable to create the copy/paste content The attachment is a .zip file containing a Windows 32-bit .exe file for creating the copy/paste errors referenced in the problem description. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157566] New: Data lost or misplaced when pasting into Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=157566 Bug ID: 157566 Summary: Data lost or misplaced when pasting into Writer Product: LibreOffice Version: 7.6.0.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stantr...@gmail.com Description: When pasting a Psalm with verses numbered via superscript, the numbered lines may be omitted entirely, or may be collected and poorly formatted at end of non-numbered text. Steps to Reproduce: Run provided sample program, click "Load, Highlight 1, Copy", then paste into empty Writer document. On sample program, click "Load, Highlight 2, Copy", then paste into Writer document again. Actual Results: The first paste omits all numbered lines that were copied from the source. The second paste (whose last line is numbered) will first include the unnumbered source content followed by the numbered content, with the first and second of the numbered lines concatenated. Further, the first numbered line is correctly indented and the remaining numbered lines were missing the indent. Expected Results: Writer should have pasted the content in a form roughly matching that shown in the sample program, with the numbered content interspersed with the unnumbered content, and indentation should have been consistent with a small amount on the numbered lines and slightly larger amount on the unnumbered lines. Reproducible: Always User Profile Reset: Yes Additional Info: LibreOfice The Document Foundation LibreOffice is a modern, easy-to-use, open source productivity suite for word processing, spreadsheets, presentations and more. This release was supplied by The Document Foundation. Copyright (c) 2-2023 LibreOffice contributors. LibreOffice was based on OpenOffice.org Version Information: Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154051] Support table (cell) border transparency
https://bugs.documentfoundation.org/show_bug.cgi?id=154051 Eyal Rozenberg changed: What|Removed |Added Summary|Border transparency |Support table (cell) border ||transparency -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154051] Border transparency
https://bugs.documentfoundation.org/show_bug.cgi?id=154051 --- Comment #5 from Eyal Rozenberg --- Created attachment 189964 --> https://bugs.documentfoundation.org/attachment.cgi?id=189964&action=edit Example slide with table where semi-transparent table border and background are useful I would like to have the table borders be white, but less pronounced relative to the background. I would also like the cell background to be semi-transparent rather than fully-transparent or fully-opaque. That would make the table be readable enough, while showing the background well enough (but not too well). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157547] FILEOPEN "Write error. The file could not be written"
https://bugs.documentfoundation.org/show_bug.cgi?id=157547 Michael Dewsbury changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #2 from Michael Dewsbury --- Version: 7.5.6.2 (X86_64) / LibreOffice Community Build ID: f654817fb68d6d4600d7d2f6b647e47729f55f15 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156994] Can't have text area shape the same as the drawing object's area shape
https://bugs.documentfoundation.org/show_bug.cgi?id=156994 --- Comment #9 from Eyal Rozenberg --- (In reply to Stéphane Guillou (stragu) from comment #7) > As it is possible to wrap text in parallel around a custom-shape's > "contour", I can see how users could expect to be able to do something > similar _inside_ the shape. Actually, it's deeper than that. If you're not used to MS Office (or existing LO behavior), I claim user will expect not just to be _able_ to do this, but for this to be the default. If the shape is an ellipse, than the text should be bounded by the ellipse (possibly with some margin). > > given that I found it hard to find questions from users looking for such a > feature You have found it hard because office suite users have it drilled into our heads that text in shapes fits inside a rectangle. It is actually not uncommon that fundamental bugs don't get reported for years, because people encounter them on day one of using the software, get used to them, and forget they may have wanted something else. We've had this a bunch of times w.r.t. RTL bugs. > I think this is low priority. So, here's the thing. In the sense that people are used to this - you're right, it is low priority. But if you think about what newbie users expect - I would say it's high priority that we change the default. > If this is ever implemented, please: > - make the feature optional, and > - do not make it the default, for compatibility's sake Again, I'm arguing that the current behavior is a bug. It's an MSO-compatible bug, but a bug nonetheless. I claim this needs to be the default, with the current behavior used for compatibility (i.e. when opening MSO documents, or if this is introduced in an ODF version, then opening older versions would default to the text-area-is-rectange choice). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156994] Can't have text area shape the same as the drawing object's area shape
https://bugs.documentfoundation.org/show_bug.cgi?id=156994 Eyal Rozenberg changed: What|Removed |Added Attachment #189234|0 |1 is obsolete|| --- Comment #8 from Eyal Rozenberg --- Created attachment 189963 --> https://bugs.documentfoundation.org/attachment.cgi?id=189963&action=edit Example of a rectangular vs shape-fitting text area Made the comparison between the two kinds of shaping of text more apples-to-apples (same font color, same alignment, similar length of text). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153043] Writer should not declare CJK (RTL-CTL) fonts when CJK (resp. RTL-CTL) support disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153043 --- Comment #14 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #13) > Wait, is only Style 1 a predefined default or both of them? Grammar ambiguity > ... In my scenario, the three styles: Style 1, Style 2, and Style 3, were all pre-defined; e.g., they could be "Heading 1", "Body Text", and "Block Quotation". > Also, it seems you're assuming the default pre-defined styles are the same > on A and B's system. Why are you making this assumption? Grammar ambiguity ;) What specifically do you mean by "the same"? I assume that the styles are "the same" in the sense that they have the same name. But otherwise, I do not assume their same *formatting* - if they were "the same" formatting-wise, it would make it safe and would not create problems. (In reply to Eyal Rozenberg from comment #11) > In fact, I believe your approach sometime results in the need for more need > for style conflict resolution, because if two people write a document from > scratch, and then want to merge it - with your approach, they will need to > harmonize the differences in all undefined styles they had not even given > any though to (and may not even know about). These words imply, that two people - starting *from scratch*, and wanting to *merge* - have conflicts in all *undefined* styles - i.e., they have the problem in styles they didn't use (but that implies, that these styles still existed in their "from scratch" document, which leads to the standard styles). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157305] [1] Feature request: linking sections without changing order of lists
https://bugs.documentfoundation.org/show_bug.cgi?id=157305 --- Comment #2 from hugoferna...@gmail.com --- I have just updated LO and got the same behavior (using the files attached in the initial comment). Version: 7.5.7.1 (X86_64) / LibreOffice Community Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126 CPU threads: 24; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: pt-BR (pt_BR); UI: pt-BR Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155263] Need a increasing-by-appearance sequence field with an initial value property
https://bugs.documentfoundation.org/show_bug.cgi?id=155263 --- Comment #2 from Eyal Rozenberg --- Created attachment 189962 --> https://bugs.documentfoundation.org/attachment.cgi?id=189962&action=edit An MS Word document exemplifying SEQ field behavior So, I can't show _exactly_ what I've asked for in MS-Word, but almost that. In the attached document, the same field with the same identifier is used multiple times. But - the first time has a different switch to set the count to its initial value. So it's not literally copying the exact same field, but it's almost the same: SEQ foo \r 123 vs SEQ foo \n . -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113134] Hebrew Dagesh/Mapiq mis-rendered with Culmus fonts in special chars dialog and when inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=113134 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||3144 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113144] Selecting a Hebrew character with the mouse doesn't select its diacritics
https://bugs.documentfoundation.org/show_bug.cgi?id=113144 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||3134 --- Comment #8 from Eyal Rozenberg --- Still seeing this (as well as bug 113134) with: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f8e591ab9182e0a61c4ae5b8f77b166fcaeaa877 CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157564] Attempting to open a Writer document i Norwegian Windows ends in "Not responding".
https://bugs.documentfoundation.org/show_bug.cgi?id=157564 Julien Nabet changed: What|Removed |Added Version|7.6.0.3 release |7.6.2.1 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146619] Remove unused #includes from C/C++ files
https://bugs.documentfoundation.org/show_bug.cgi?id=146619 --- Comment #20 from Commit Notification --- Gabor Kelemen committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/3e753f484910fb65065dd7eb81d2131b51990fe9 tdf#146619 Recheck include/s* with IWYU It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153043] Writer should not declare CJK (RTL-CTL) fonts when CJK (resp. RTL-CTL) support disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153043 --- Comment #13 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #12) So, about templates: I think that people who collaborate should probably use a proper OTT template, which defines everything they expect to use or maybe simply everything, period, in a way that's stylistically consistent. And that means I am not that worried about collaborators who start writing from scratch having to then harmonize different style choices they each introduce during their work. > > if two people write a document from > > scratch, and then want to merge it - with your approach, they will need to > > harmonize the differences in all undefined styles they had not even given > > any though to (and may not even know about). > > No. > "From scratch" case would not make it easier in even a slightest bit. Even > if you imagine the case where collaborator A has their from-scratch document > (using *pre-defined, default* Style 1 and Style 2) Wait, is only Style 1 a predefined default or both of them? Grammar ambiguity > without any other styles > in the ODF, and collaborator B has their from-scratch document (using > *pre-defined, default* Style 2 and Style 3) same question. Please clarify so that I can understand the rest of the scenario. Also, it seems you're assuming the default pre-defined styles are the same on A and B's system. Why are you making this assumption? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157558] FILEOPEN PPTX: graphics too bright in presentation mode (only) - transparency issue?
https://bugs.documentfoundation.org/show_bug.cgi?id=157558 Gabor Kelemen (allotropia) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Keywords|bibisectRequest |bibisected, bisected CC||kelem...@ubuntu.com, ||noelgran...@gmail.com --- Comment #3 from Gabor Kelemen (allotropia) --- Confirmed in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2902ab24ecc5ffbf4907ea83b2028508b9de6364 CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded Especially the shape named "Pentagon 91", which has multi step gradient bg is way brighter than in PP. Seems to have begun in https://git.libreoffice.org/core/+/81994cb2b8b32453a92bcb011830fcb884f22ff3 author Noel Grandin Fri Apr 16 20:33:10 2021 +0200 committer Noel Grandin Tue Jul 25 08:38:12 2023 +0200 Convert internal vcl bitmap formats transparency->alpha (II) Adding CC to: Noel Grandin -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156756] Icon sizes for the toolbar don't correspond to the actual sizes of icons
https://bugs.documentfoundation.org/show_bug.cgi?id=156756 --- Comment #11 from BogdanB --- Noel, I am testing this bug, and I get a crash, but not from this change, but could be related: please try this: 1. Change icons to Small, press Apply. → Everything fine. 2. Now try to change the Icon Theme to something else. → Crash. Was working until recently. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d97b5849f3cfcecbdd929dca7bd7ac2c4fa31f8b CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157542] Arrow and line style drop down menu selectors icons missing
https://bugs.documentfoundation.org/show_bug.cgi?id=157542 BogdanB changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #15 from BogdanB --- In today master everything fine. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d97b5849f3cfcecbdd929dca7bd7ac2c4fa31f8b CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156510] Support list styles or paragraph styles "not sticking" when the style in the other category changes
https://bugs.documentfoundation.org/show_bug.cgi?id=156510 --- Comment #3 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #2) > Still missing STR. 1. Set the paragraph style to Text Body. 2. Set some list style, e.g. "Bullet -" 3. Type some text 4. Press Enter to get to a new paragraph 5. Change the style to Title Expected results: List style is dropped in favor of the default list style (i.e. No List) or rather - expecting to be able to choose whether the list style should be dropped or not Actual results: List style persists in the Title paragraph if we switch to Heading 1 though, instead of Title - the "Bullet -" style does not persist. Why can the user not configure whether they want persistence of the list style or not, when switching to a given style? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 79512] [META] OOXML WordArt not parsed faithfully in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=79512 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||157529 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157529 [Bug 157529] FILEOPEN PPTX: Text shows that is invisible in PowerPoint -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157529] FILEOPEN PPTX: Text shows that is invisible in PowerPoint
https://bugs.documentfoundation.org/show_bug.cgi?id=157529 Gabor Kelemen (allotropia) changed: What|Removed |Added Ever confirmed|0 |1 Blocks||79512 Status|UNCONFIRMED |NEW Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=79512 [Bug 79512] [META] OOXML WordArt not parsed faithfully in LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157529] FILEOPEN PPTX: Text shows that is invisible in PowerPoint
https://bugs.documentfoundation.org/show_bug.cgi?id=157529 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com --- Comment #2 from Gabor Kelemen (allotropia) --- Created attachment 189960 --> https://bugs.documentfoundation.org/attachment.cgi?id=189960&action=edit The example file in PP 2016 and Impress Confirming in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2902ab24ecc5ffbf4907ea83b2028508b9de6364 CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded We have fontwork here, and the network word has seemingly a different font color + transparency given on different letters: 2c8685 and white color plus 100% transparency in PP, becomes 2c8685 and no transparency in Impress. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156964] Support idiom of title bar moving up or down according to main box contents
https://bugs.documentfoundation.org/show_bug.cgi?id=156964 --- Comment #4 from Eyal Rozenberg --- Created attachment 189959 --> https://bugs.documentfoundation.org/attachment.cgi?id=189959&action=edit Illustration of the requested feature in an exported (non-LO) slide deck Have a look at the slides in the attached deck. The slide title does not have a fixed position on the slide; instead, it is placed at some distance atop of the main slide content: If the slide content has many lines, the title appears further up the slide. If the slide content has few lines, the title appears closed to the v-middle of the slide. @Heiko: Is it clearer now? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157555] FILEOPEN PPTX: One of three links shows in different color (white instead of orange)
https://bugs.documentfoundation.org/show_bug.cgi?id=157555 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com --- Comment #4 from Gabor Kelemen (allotropia) --- Interestingly this is good under Windows nightly and bibisect 7.6, 7.5: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2902ab24ecc5ffbf4907ea83b2028508b9de6364 CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded but I see it on my Linux boxes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157561] Invalid error message opening .mdb/.accdb file
https://bugs.documentfoundation.org/show_bug.cgi?id=157561 --- Comment #2 from Robert Großkopf --- You have to create a *.odb-file (Base) to connect to a database file for access (*.mdb). Only tables and views from *.mdb-file will be available in *.odb-file. Have a look here: https://wiki.documentfoundation.org/Faq/Base/How_to_connect_to_a_Microsoft_Access_database -- 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 Robert Großkopf changed: What|Removed |Added Component|Base|LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122599] Classification: Signing: paragraph signing doesn't change to invalid when the paragraph is splitted with Enter
https://bugs.documentfoundation.org/show_bug.cgi?id=122599 Timur changed: What|Removed |Added Regression By||Ashod Nakashian CC||ti...@libreoffice.org --- Comment #6 from Timur --- IIUC this report is only for immediate invalidation, because saving and reopening is OK. -- 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 --- Comment #3 from truer0man --- Bug is still exist in 7.6.2.1 version of SDK. I'm using .NET 7. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157471] Display error in form text fields
https://bugs.documentfoundation.org/show_bug.cgi?id=157471 --- Comment #4 from S --- This version is NOT affected by the problem: Version: 7.4.7.2 / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (en_IE.UTF-8); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157135] LibreOffice 7.6 stalls under Windows 11
https://bugs.documentfoundation.org/show_bug.cgi?id=157135 --- Comment #15 from Buovjaga --- Noticing Mike's addition to See Also, wow, looks like we have a Norwegian connection! Bug 157564: "The error is not reproduced in Windows US version, where the Writer document behaves normally." -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157471] Display error in form text fields
https://bugs.documentfoundation.org/show_bug.cgi?id=157471 --- Comment #3 from S --- This is the used build: Version: 7.5.7.1 (X86_64) / LibreOffice Community Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (en_IE.UTF-8); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156980] "Delete chapter" error message and action in relation to folded headings is inverted in Navigator context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156980 --- Comment #5 from Buovjaga --- (In reply to Stéphane Guillou (stragu) from comment #4) > (In reply to Buovjaga from comment #3) > > Can you advise how to do it? I followed the instructions from > > https://help.libreoffice.org/latest/en-US/text/swriter/01/ > > outlinecontent_visibility.html but Ctrl does nothing and there is no Outline > > Folding item in the context menu for headings in the Navigator. > > You don't get the right-hand-side arrow when hovering the titles? > Is this setting on? Tool > Options > LO Writer > View > Show Outline-Folding > Buttons Ok, that was the missing step, I did not have it activated. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157564] Attempting to open a Writer document i Norwegian Windows ends in "Not responding".
https://bugs.documentfoundation.org/show_bug.cgi?id=157564 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7135 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157135] LibreOffice 7.6 stalls under Windows 11
https://bugs.documentfoundation.org/show_bug.cgi?id=157135 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7564 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108742] [META] Shape points (glue points) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108742 Bug 108742 depends on bug 157543, which changed state. Bug 157543 Summary: FILEOPEN PPT: object specific glue points are missing for import from binary ppt https://bugs.documentfoundation.org/show_bug.cgi?id=157543 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153527] LibreOffice 7.5 Calc: unable to apply formatting to all cells in spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=153527 --- Comment #30 from LeroyG --- (In reply to robert from comment #26) > > 65 CC's on, from your own website, some 200,000,000 users? My 0.01% was > still way too optimistic!!! That "only" 65 users are involved in this question means that a lot of people are interested. There are many who don't bother to add their duplicate comment, and many more that don't know how to do it (or that it is possible to comment). Those who participate here are only the tip of the iceberg. Please, someone hide my comment as obsolete (as per this question). Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157565] New: The Font Color chooser does not show color names any more since 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=157565 Bug ID: 157565 Summary: The Font Color chooser does not show color names any more since 7.6 Product: LibreOffice Version: 7.6.2.1 release Hardware: x86 (IA32) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j.f.lant...@inter.nl.net Description: When choosing a color for fonts, hovering the color matrix does not show any color names. This is very cumbersome, because various colors almost look the same. This chooser is different from the one in the Table menu for Backgrounds. Steps to Reproduce: 1.open the color matrix 2.hover any color square 3.nothing shows up Actual Results: no color ident Expected Results: something like before: Red 3, Green 1, ... Reproducible: Always User Profile Reset: No Additional Info: Version 7.6.2.1 (X86_64) Build 56f7684011345957bbf33a7ee678afaf4d2ba333 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157471] Display error in form text fields
https://bugs.documentfoundation.org/show_bug.cgi?id=157471 raal changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||r...@post.cz --- Comment #2 from raal --- No repro with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0f2918c25daab25cd0721d69f0506fe04456262d CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Please copy and paste here the contents of your Help - About from your LibreOffice. This allows us to know more about your system. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156756] Icon sizes for the toolbar don't correspond to the actual sizes of icons
https://bugs.documentfoundation.org/show_bug.cgi?id=156756 --- Comment #10 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/8275b70aae25f48817747bdfbfcfcaf1197c550c tdf#156756 Icon sizes for the toolbar wrong It will be available in 7.6.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156756] Icon sizes for the toolbar don't correspond to the actual sizes of icons
https://bugs.documentfoundation.org/show_bug.cgi?id=156756 Commit Notification changed: What|Removed |Added Whiteboard|target:24.2.0 |target:24.2.0 target:7.6.3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157561] Invalid error message opening .mdb/.accdb file
https://bugs.documentfoundation.org/show_bug.cgi?id=157561 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #1 from raal --- I'm not Base expert, but please see https://ask.libreoffice.org/t/how-to-opening-mdb-files/48095 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119951] FILEOPEN PPTX: Some row heights in table different from MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=119951 Timur changed: What|Removed |Added Regression By||Andras Timar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157550] Writer refuses to scroll
https://bugs.documentfoundation.org/show_bug.cgi?id=157550 --- Comment #4 from Sciuriware --- Thanks for your time. Btw.: going to safe mode resets a lot: it took me 30 minutes to check and reset everything. Fortunately I stored screen shots of every chapter. I will file a new bug: the colors do not have names any more in the color chooser; very clumsy. ;JOOP! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157564] New: Attempting to open a Writer document i Norwegian Windows ends in "Not responding".
https://bugs.documentfoundation.org/show_bug.cgi?id=157564 Bug ID: 157564 Summary: Attempting to open a Writer document i Norwegian Windows ends in "Not responding". Product: LibreOffice Version: 7.6.0.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: morten.tinnes...@gmail.com Description: Attempting to edit a Writer (odt) document in Norwegian Windows environment stops with a "Not responding" situation. The main testing is performed in Windows 10 but it also fails in similar way in Windows 11 (Norwegian edition) --- Testing the same document in US Windows 10 works as expected Steps to Reproduce: 1. Open a writer (odt) document from Windows Explorer 2. Wait 3. Click inside the writer Window Actual Results: Document does not open but title shows the document name e.g "20231002_Simple.odt - LibreOffice Writer (Svarer ikke)" "Svarer ikke" is the Norwegian translation of "Not responding" Expected Results: Document is opened and ready for editing Reproducible: Always User Profile Reset: Yes Additional Info: Also tested with a "clean" user profile with same result. Version information: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 1; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: nb-NO (nb_NO); UI: nb-NO Calc: threaded --- The error is not reproduced in Windows US version, where the Writer document behaves normally. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135310] [META] Writer outline folding bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=135310 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156980 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156980 [Bug 156980] "Delete chapter" error message and action in relation to folded headings is inverted in Navigator context menu -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156980] "Delete chapter" error message and action in relation to folded headings is inverted in Navigator context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=156980 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks|103030 |135310 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||rayk...@gmail.com --- Comment #4 from Stéphane Guillou (stragu) --- I reproduce the three tests in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e3c961e6a3917d95534652e0f982918cc1079015 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Jim, any change you could have a look at these special cases? (In reply to Buovjaga from comment #3) > Can you advise how to do it? I followed the instructions from > https://help.libreoffice.org/latest/en-US/text/swriter/01/ > outlinecontent_visibility.html but Ctrl does nothing and there is no Outline > Folding item in the context menu for headings in the Navigator. You don't get the right-hand-side arrow when hovering the titles? Is this setting on? Tool > Options > LO Writer > View > Show Outline-Folding Buttons Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103030 [Bug 103030] [META] Navigator sidebar deck and floating window https://bugs.documentfoundation.org/show_bug.cgi?id=135310 [Bug 135310] [META] Writer outline folding bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|156980 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156980 [Bug 156980] "Delete chapter" error message and action in relation to folded headings is inverted in Navigator context menu -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157127] Make "Merge adjacent line styles" merge between tables
https://bugs.documentfoundation.org/show_bug.cgi?id=157127 --- Comment #17 from Jim Avera --- > The user sets the border to half thickness when the tables are on same page > and > on full thickness when tables on different pages. Ok, I think this is the point of misunderstanding. The user can not do that because the user can not know where page breaks will occur. The height of each table is unpredictable because it is data-dependent (e.g. sometimes line wraps occur, making rows higher etc.) and thererfore a long list of touching tables will be split across pages unpredictably. It is not subject to human formatting of individual tables because the data is generated and inserted with software (you can imagine LibreOffice macros doing it, although in my application the technology is different). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 58685] Add *option* for proposing a file name based on the content of the document on first save (comment 13 for suggested sources in priority order)
https://bugs.documentfoundation.org/show_bug.cgi?id=58685 Stéphane Guillou (stragu) changed: What|Removed |Added CC||hoss...@libreoffice.org Keywords||needsDevEval -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 58685] Add *option* for proposing a file name based on the content of the document on first save (comment 13 for suggested sources in priority order)
https://bugs.documentfoundation.org/show_bug.cgi?id=58685 Stéphane Guillou (stragu) changed: What|Removed |Added CC||hw.stuur...@gmail.com --- Comment #28 from Stéphane Guillou (stragu) --- *** Bug 157563 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157563] Saving a file
https://bugs.documentfoundation.org/show_bug.cgi?id=157563 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the suggestion! This is already requested in bug 58685, so marking as a duplicate. *** This bug has been marked as a duplicate of bug 58685 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157307] dictionaries don't store new words
https://bugs.documentfoundation.org/show_bug.cgi?id=157307 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Summary|Les dictionnaires |dictionaries don't store |n'enregistrent pas les |new words |nouveaux mots. | Version|unspecified |7.6.2.1 release Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Translated: > LibreOffice 7.6.1.2, Windows 11. Dictionaries don't record new words. They are > not read-only. One needs to record new words in the relevant dictionary > manually > so they are taken into account. I don't reproduce the issue in: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Mourocq, can you please: - Test the new version 7.6.2.1: https://www.libreoffice.org/download/download-libreoffice/ - Reset your user profile (after backing it up), and test again. Please see: https://wiki.documentfoundation.org/UserProfile (or test with safe mode, "Aide > Mode sans échec") - If the issue persists, please let us know how exactly you try to record new words (Right-click on word? Inside the spellcheck dialog?) and what settings your use - And paste here the full information copied from Help > About LibreOffice If you need to, feel free to use automated translation to reply in English (our preferred language here). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157292] Consolidate Text should maintain vertical and horizontal placement of lines after consolidation
https://bugs.documentfoundation.org/show_bug.cgi?id=157292 Eyal Rozenberg changed: What|Removed |Added Summary|Consolidate Text should |Consolidate Text should |maintain vertical placement |maintain vertical and |of lines after |horizontal placement of |consolidation |lines after consolidation --- Comment #11 from Eyal Rozenberg --- (In reply to Stéphane Guillou (stragu) from comment #9) > Here is another test file, including character and paragraph formatting, as > well as text box formatting, to have the full picture. Good example to think about this problem, yes. > * (Noting that paragraph and character formatting _is_ conserved. Not text > box formatting.) Not exactly. That is, think of the horizontal endpoints of the text in the top textbox. If you consolidate it with the one below it - the paragraphs don't end at the same place, they end near the right edge of the combined textbox. So, the "right indent 0" is maintained, but not the right edge of the paragraph. If that were maintained, the vertical positioning of the text from the first textbox would also be maintained. > * Hoping to conserve relative position of the different pieces of text is > unrealistic. Your example uses the specific case of two text boxes that > happen to be left-aligned and that don't overlap in their X and/or Y > positions. Well, that is a trickier case, yes. However, if we supported negative vspace before paragraph, it would be possible (and easy) > But in other cases, consolidating will involve LTR boxes that are > not left-aligned and that would end up in an overlap. Why does the left-aligning matter? That's a paragraph-level feature. > * If we were to somehow implement what you are asking in a manner that > accommodates the above, the original paragraph formatting would have to be > amended with a new custom value for Below or Above Paragraph Spacing – which > would then propagate to new inserted paragraphs. It would, yes. > This means that it could go > _against_ the expectation of someone joining two text boxes in order to have > a more consistent document with equal spacing of paragraphs. 1. We are in Draw, not Writer. I might have accepted this line of reasoning there 2. The user knows they've consolidated text in a way which maintains vertical (and horizontal) positioning, i.e. that they get slightly "contorted" settings to make that happen. If they want a consistent text box with equal spacing etc. - they can clear the DF we introduce, very easily. But if we make things simple and consistent, the user can't, without significant effort and basing themselves on good memory, reposition the content. > (i.e. "Why did > this keep the wrong spacing? I wanted to get something consistent!") "Why? Since it looks the same as before the consolidation." "I want something consistent. This has a bunch of DF originating in PDF placement and textbox consolidation; let me clear the DF and set my own formatting" > Whatever the feature was designed for in the first place, it is not used > exclusively for PDF editing (even though it's particularly useful for it, as > the documentation says[1]) and it would be bad to break existing. So, Stuart made the opposite argument. I think the behavior I suggest is better fore the feature as-is: Maintaining rather than losing information. However, if we can sketch out an non-PDF-import use case when Textbox consolidation is supposed to act differently - then perhaps we could have either two version of the command's behavior, e.g.: * Post-command-application baloon widget, a-la the paste options balloon in MS Office, or * Simply two commands, e.g. "Consolidate" and "Consolidate Text" or whatever * A "maintain positioning?" dialog box -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157560] Calc incorrectly converts DEC2HEX function when saving as Mircosoft .xlsx
https://bugs.documentfoundation.org/show_bug.cgi?id=157560 Xisco Faulí changed: What|Removed |Added Resolution|INVALID |WORKSFORME --- Comment #3 from Xisco Faulí --- WORKSFORME sounds like the correct choise -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156982] Provide Option to specify browser agent string
https://bugs.documentfoundation.org/show_bug.cgi?id=156982 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||needsDevAdvice Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||michael.st...@allotropia.de ||, ||stephane.guillou@libreoffic ||e.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=55 ||073 --- Comment #1 from Stéphane Guillou (stragu) --- Adding "needsDevAdvice" as I am unsure of the implications. Maybe something for the expert configuration? Markus, if you know of documentation about those MS 365 restrictions, please do share a link. Also, please give more information on what method exactly you use to access remote files, as I suppose the user agent string depends on the route. Regarding getting blocked because "curl" is in there, it should at least be fixed for webdav since LO 7.3.4: bug 148429. Michael, any opinion? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 55073] Add more details to the LibreOffice User-Agent string
https://bugs.documentfoundation.org/show_bug.cgi?id=55073 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6982 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157560] Calc incorrectly converts DEC2HEX function when saving as Mircosoft .xlsx
https://bugs.documentfoundation.org/show_bug.cgi?id=157560 --- Comment #2 from Bruno Seifert --- You're entirely correct, Xisco. The newer version fixed it, I should have checked whether the version in the default Ubuntu PPA is up to date. Thank you for the help! I'm a bit unsure whether this should be marked as fixed or invalid, I chose invalid for now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156988] Find cannot find superscripted or subscripted text
https://bugs.documentfoundation.org/show_bug.cgi?id=156988 William Friedman changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #4 from William Friedman --- Confirmed, ticking the automatic box on Search For Formatting | Position works, with both the letter and the regex. This remains a bug, however, because automatic is not ticked by default, neither when super/subscripting nor when searching for super/subscripted text. (Also, I have no idea how automatic works, and the help is no help at all: "Automatically sets the amount by which the selected text is raised or lowered in relation to the baseline." Automatically based on what? And how is that different than the default "manual" percentage of 33%?) -- You are receiving this mail because: You are the assignee for the bug.
