[Bug 146619] Remove unused #includes from C/C++ files
https://bugs.documentfoundation.org/show_bug.cgi?id=146619 --- Comment #76 from Commit Notification --- Gabor Kelemen committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/9a4eead9958d887d37a5c9bab9465cc6ddd0b213 tdf#146619 Drop unused 'using namespace' in: oox/ 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 160590] Impress crashes when skia is enabled without software rendering: EXC_CRASH (SIGABRT)
https://bugs.documentfoundation.org/show_bug.cgi?id=160590 --- Comment #3 from Giuseppe S. --- Hello, is Skia something external to libreoffice? Should I report this bug to other project? Thank you, Giuseppe S. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158642] Dark mode: "Text boundaries" set to "automatic" obscure the cursor when line is empty
https://bugs.documentfoundation.org/show_bug.cgi?id=158642 --- Comment #5 from John --- I was not able to reproduce this issue: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 76208] Frame border settings ignored
https://bugs.documentfoundation.org/show_bug.cgi?id=76208 --- Comment #12 from John --- I was unable to reproduce this bug in this version: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157214] [CRASH] Segmentation fault in kf5 + Wayland (/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5)
https://bugs.documentfoundation.org/show_bug.cgi?id=157214 Michael Weghorn changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #11 from Michael Weghorn --- (In reply to Rafael Lima from comment #10) > Yeah, I can confirm that it does not crash when I comment out these two > environment variables. I didn't know this trick, thanks for pointing it out. Thanks for confirming. > This bug is actually a pain when building and testing LO on my second > machine, where I run Wayland on Plasma 5.27... at least by commenting these > lines, I can get around this issue. It is indeed. Other workarounds are using a different VCL plugin (e.g. SAL_USE_VCLPLUGIN=qt6 ) or forcing the use of the X11/xcb QT platform plugin instead of the native Wayland one ( QT_QPA_PLATFORM=xcb ). > I agree that this is an upstream bug. But isn't Plasma 5.27 an LTS? So maybe > it should be a good idea to report this issue upstream. Without analyzing further, I'd rather expect this to be a Qt issue. The KDE community still has a "patch collection" for Qt 5, but since the issue doesn't cause any user-visible issues in a "normal" setup, my assumption is that the most likely way to actually get a fix would be to analyze in more detail and either identify what commit fixed this for Qt 6 and suggest a backport, or come up with a fix oneself. I wouldn't feel able to create a proper bug report without spending more time. And while this is indeed annoying when using Wayland, my personal focus is more on qt6 than kf5/qt5 when it comes to non-critical things. > I haven't built LO using Plasma 6 yet... so I can't tell whether the problem > is there too. I have only tested the PPA version of LO under Plasma 6, but > using the kf5 backend, since qt6 isn't being shipped yet in the PPA. Do you see the issue with kf5 with that PPA? (My initial assumption would be no, as I'd expect that to be a release build, where the environment variables causing the crash shouldn't be set.) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160592] Cannot Save as PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=160592 --- Comment #1 from Mike Kaganski --- 1. There must be a PDF export button on the toolbar. 2. There should be File->Export->Export as PDF menu item. Please provide a screenshot of your user interface with File->Export menu expanded. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160364] soffice --convert-to gives "Secure coding is not enabled for restorable state!" warning
https://bugs.documentfoundation.org/show_bug.cgi?id=160364 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160582] FILEOPEN: CSV, locale setting is not preserved in the import window (regression tdf#152336)
https://bugs.documentfoundation.org/show_bug.cgi?id=160582 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153306] Cursor leftovers keep being displayed when using Skia Vulkan/Metal
https://bugs.documentfoundation.org/show_bug.cgi?id=153306 --- Comment #28 from John --- I was not able to replicate this on my setup. I'm using a 1440p monitor on windows with the following version: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_DE); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160032] MASTER Document -- updating linked documents automatically: different setting for master documents (on opening)
https://bugs.documentfoundation.org/show_bug.cgi?id=160032 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160589] Charts are not updated after data entry if freezing of columns or rows is activated
https://bugs.documentfoundation.org/show_bug.cgi?id=160589 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160361] Export Preview Support
https://bugs.documentfoundation.org/show_bug.cgi?id=160361 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160360] Syntax Highlighting for Markdown
https://bugs.documentfoundation.org/show_bug.cgi?id=160360 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160345] Slow rendering of filled polygon
https://bugs.documentfoundation.org/show_bug.cgi?id=160345 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160273] Writing direction with rotated text in cell is inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=160273 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.
[Bug 160353] List images in order of document appearance in navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=160353 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160273] Writing direction with rotated text in cell is inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=160273 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157446] Not responding after opening the app, is the Windows Update the cause?
https://bugs.documentfoundation.org/show_bug.cgi?id=157446 --- Comment #7 from QA Administrators --- Dear Rosyad, 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 157325] Copying from an excel (From Excel 2019 program) to CSV (opened in Calc 7.5.6.2)
https://bugs.documentfoundation.org/show_bug.cgi?id=157325 --- Comment #2 from QA Administrators --- Dear Baranyai Zsolt, 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 157408] LibreOffice - Writer crashed when two databases (ods-files) are involved in one serial-letter.
https://bugs.documentfoundation.org/show_bug.cgi?id=157408 --- Comment #3 from QA Administrators --- Dear Benjamin B., 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 155354] Hidden field isn't hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=155354 --- Comment #6 from QA Administrators --- Dear davent, 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 99725] FILEOPEN RTF layout problem with footer (Normal view not showing some text)
https://bugs.documentfoundation.org/show_bug.cgi?id=99725 --- Comment #10 from QA Administrators --- Dear Óvári, 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 99724] FILEOPEN RTF layout problem with footer
https://bugs.documentfoundation.org/show_bug.cgi?id=99724 --- Comment #11 from QA Administrators --- Dear Óvári, 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 148171] FILEOPEN DOCX PageRef field with "Position of paragraph" option incorrectly imported
https://bugs.documentfoundation.org/show_bug.cgi?id=148171 --- Comment #2 from QA Administrators --- Dear Gabor Kelemen (allotropia), 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 148174] FILEOPEN DOCX Ref field incorrect with "Paragraph # in full context" and "Relative position of paragraph" enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=148174 --- Comment #2 from QA Administrators --- Dear Gabor Kelemen (allotropia), 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 97947] FILEOPEN RTF layout problem with table
https://bugs.documentfoundation.org/show_bug.cgi?id=97947 --- Comment #8 from QA Administrators --- Dear Óvári, 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 148173] FILEOPEN DOCX Ref field incorrect with "Paragraph # from marked paragraph" and "Relative position of paragraph" enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=148173 --- Comment #2 from QA Administrators --- Dear Gabor Kelemen (allotropia), 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 147463] Clicking on field link scrolls to page, but focuses only 1/3 of the page in question
https://bugs.documentfoundation.org/show_bug.cgi?id=147463 --- Comment #6 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 132215] .uno:EditStyle does not do anything in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=132215 --- Comment #6 from QA Administrators --- Dear Julien Nabet, 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 131599] Jumping to beginning of next page does not center view logically
https://bugs.documentfoundation.org/show_bug.cgi?id=131599 --- Comment #7 from QA Administrators --- Dear Stapler, 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 106859] DOCX formulas : greek letters not imported correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=106859 --- Comment #10 from QA Administrators --- Dear Pierre C, 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 159393] Writer shutdown after a Ctrl-Enter for new page in document
https://bugs.documentfoundation.org/show_bug.cgi?id=159393 --- Comment #4 from John --- This issue does not seem to be present in this version of LibreOffice Writer: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_DE); UI: en-US Calc: CL threaded I was not able to reproduce the bugs and page breaks were inserted as expected. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158850] Font Size in Menubar not Changeable
https://bugs.documentfoundation.org/show_bug.cgi?id=158850 --- Comment #2 from John --- This does not appear to be an issue in my version of LibreOffice. It behaves as expected as far as I can tell. I recommend following the steps that were commented previously and trying a new version. Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_DE); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160273] Writing direction with rotated text in cell is inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=160273 --- Comment #5 from Csábi Frigyes --- (In reply to Stéphane Guillou (stragu) from comment #4) > (In reply to V Stuart Foote from comment #2) > > You are mixing Table/Table Cell *text orientation* up with Character *text > > rotation*. > > > > Different attributes! > > > > Table layout BTLR is different to TBRL -- the 90 left rotation happens to > > match the layout of the BTLR orientation. Simply put, the 270 right > > rotation does not match layout of TBRL orientation. > > > > IMHO => NAB > I agree with Stuart here. Character rotation is a character effect, not a > whole-paragraph or whole-cell tool. > > (In reply to Csábi Frigyes from comment #3) > > Hmm, yes you are right, the 270 rotation is still left to right. My problem > > is, that it is very hard to read. And if i try to change it to right to left > > (Ctrl + Shift + D in Windows) it messes up the text. Would you consider this > > as a bug? > Why would you change an LTR script to RTL direction? In this case, the > character rotation and the writing direction features would be both > missused. If you want the text contained in a table cell to be read by > tilting your head to the right, cell rotation has to be used. What is wrong > with using cell rotation? Yes, using cell rotation would be the more convenient, but it raises a problem mentioned in Bug 160271, which seems to be considered NAB. Not to mention another issue. We have to work with merged AND rotated cells, and they dont break "well" when they continue on multiple pages, leaving sometimes half of the page empty (Even with allowing row breaking). Rotating the text instead of the cell fixes this as well. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160590] Impress crashes when skia is enabled without software rendering: EXC_CRASH (SIGABRT)
https://bugs.documentfoundation.org/show_bug.cgi?id=160590 --- Comment #2 from Patrick Luby (volunteer) --- (In reply to V Stuart Foote from comment #1) > Meaning probably that Skia Metal accelerated graphics are not supported on > your GPU. Actually rather common and why the raster framed "software" > rendering is fallback/default. So far, we only disable Skia/Raster for the following 2 GPU families: AMD Radeon Pro 5300M AMD Radeon Pro 5500M Reading the crash log in attachment #193575, it is LibreOffice's "Skia hang detector" code that is forcing LibreOffice to crash. That code monitors batches of calls into Skia and, if a batch doesn't finish within a few seconds or so, that code forces LibreOffice to crash. So, I assume that Skia/Metal has one or more very, very slow or hanging operations on the Intel HD Graphics 6000 GPU. Should I add that to the above "disable Skia/Raster" list? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160590] Impress crashes when skia is enabled without software rendering: EXC_CRASH (SIGABRT)
https://bugs.documentfoundation.org/show_bug.cgi?id=160590 V Stuart Foote changed: What|Removed |Added CC||guibomac...@gmail.com, ||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- Meaning probably that Skia Metal accelerated graphics are not supported on your GPU. Actually rather common and why the raster framed "software" rendering is fallback/default. IMHO if the Skia vector GPU rendering fails, NOT OUR BUG. Hardware, Driver or a mix of the two. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160591] FILESAVE PPTX: blue shape turns white, white text turns black
https://bugs.documentfoundation.org/show_bug.cgi?id=160591 Gerald Pfeifer changed: What|Removed |Added Keywords||bibisectRequest, regression -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160591] FILESAVE PPTX: blue shape turns white, white text turns black
https://bugs.documentfoundation.org/show_bug.cgi?id=160591 --- Comment #1 from Gerald Pfeifer --- Created attachment 193577 --> https://bugs.documentfoundation.org/attachment.cgi?id=193577&action=edit Visual comparison: PowerPoint (left) - Impress after saving as PPTX (right) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160591] New: FILESAVE PPTX: blue shape turns white, white text turns black
https://bugs.documentfoundation.org/show_bug.cgi?id=160591
Bug ID: 160591
Summary: FILESAVE PPTX: blue shape turns white, white text
turns black
Product: LibreOffice
Version: 24.8.0.0 alpha0+ Master
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Impress
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: ger...@pfeifer.com
Created attachment 193576
--> https://bugs.documentfoundation.org/attachment.cgi?id=193576&action=edit
Sample slide (PPTX)
1. Open the attached PPTX document in Impress.
Looks pretty much like in PowerPoint!
2. Save from Impress as PPTX under a different name.
3. Restart Impress and open the just saved document.
4. Yikes!
a. The white text in the center ("Am Dam Des") is now black.
b. The copyright notice in the lower left corner turned from white
to black, too.
c. The central element changed from blue to white.
Item 4.a and 4.b, text changing from white to black is a regression;
Version: 7.5.6.0.0+ (X86_64) / LibreOffice Community
Build ID: 0a5c49aa4f65c8e661f7da3934ab9bea8cacf662
CPU threads: 12; OS: Linux 6.8; UI render: default; VCL: gtk3
does not have it.
Full extent seen with
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 30c6e51fc9cb0fa864e1755271343d847fcced25
CPU threads: 12; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 160305] Export WebP : does not support transparency
https://bugs.documentfoundation.org/show_bug.cgi?id=160305 --- Comment #3 from Archie Cobbs --- Just a note... Bug #160588 was marked as a duplicate of this bug, but bug #160588 describes TWO problems, only one of which duplicates this bug (WEBP with white background instead of transparent). So in order not to lose track of the OTHER problem, I'm reproducing it here. My apologies if these are somehow actually the same bug - if so ignore this comment. The OTHER bug is that text in an PNG export loses its color (i.e., becomes transparent) when "Include transparency" is checked, but when "Include transparency" is not checked. 1. Open bug-example.odg in Draw 2. Export -> PNG -> Include transparency 3. [BUG] Notice text in image is missing color -> see png-with-transparency.png See bug #160588 for the test case. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160580] Provide config option for "Wraparound" of next/previous sheet shortcut in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=160580 --- Comment #5 from a...@patternjugglers.co.nz --- (In reply to ady from comment #4) > (In reply to alex from comment #3) > > To clarify, I am not suggesting a new shortcut to go to the first/last sheet > > - just that the former behaviour of the next/previous shortcuts be made > > available in some way. > > The request is clear. It would be some advance experimental setting, buried > within some not-so-obvious dialogue. > > OTOH, since there are no shortcuts available for "go to first/last > worksheets", having the possibility to assign a shortcut would be less > "advance/experimental". > > I was just taking part of your comment 0 and suggesting a possible > alternative way to solve the UX problem. > > > > > the buttons in the GUI > > retain this behaviour, and it existed prior to 24.2, so it's hard to imagine > > it needs something totally new built. > > For some users, the arrow UI icons to go to first/prior/next/last worksheet > are always grayed out, not clickable. You can click on a specific worksheet > tab, but not on the arrows. This is a separate bug report, but somewhat > related to this request. > > > > > Regarding exposing something new in the customise list, perhaps a separate > > entry for "next sheet - wrap at last" might be comprehensible to users? > > The functions I mentioned in my comment 2 would be "to first (work)sheet" > and "to last (work)sheet". These do not exist, AFAIK. Whether these would > deserve to be added, or to provide whichever alternative to this request, it > is for the UX Team and other devs to evaluate. Thanks for the extra info - I realise we're mostly agreeing and hope some improvement can come from the discussion! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160305] Export WebP : does not support transparency
https://bugs.documentfoundation.org/show_bug.cgi?id=160305 m_a_riosv changed: What|Removed |Added CC||archie.co...@gmail.com --- Comment #2 from m_a_riosv --- *** Bug 160588 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160588] FILESAVE: Transparency-related bugs with export to PNG and WEBP
https://bugs.documentfoundation.org/show_bug.cgi?id=160588 m_a_riosv changed: What|Removed |Added Resolution|--- |DUPLICATE CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |RESOLVED --- Comment #4 from m_a_riosv --- *** This bug has been marked as a duplicate of bug 160305 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158420] com.sun.star.text.ContentIndex seems to be missing boolean to enable AdditionalStyles
https://bugs.documentfoundation.org/show_bug.cgi?id=158420 --- Comment #3 from Olivier Hallot --- (In reply to Buovjaga from comment #2) > (In reply to jimmy1 from comment #1) > > I found out that the boolean I'm searching for is: > > `CreateFromLevelParagraphStyles`. > > > > Enabling this property works, but I had to dig into the LibreOffice source > > code to find it. It's missing within the official docs. > > > > So my follow-up question is: could this be added to the documentation? > > Yeah, I can't find it in https://api.libreoffice.org/docs/idl/ref/index.html The argument seems to be LevelParagraphStyles in https://api.libreoffice.org/docs/idl/ref/servicecom_1_1sun_1_1star_1_1text_1_1ContentIndex.html -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160580] Provide config option for "Wraparound" of next/previous sheet shortcut in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=160580 --- Comment #4 from ady --- (In reply to alex from comment #3) > To clarify, I am not suggesting a new shortcut to go to the first/last sheet > - just that the former behaviour of the next/previous shortcuts be made > available in some way. The request is clear. It would be some advance experimental setting, buried within some not-so-obvious dialogue. OTOH, since there are no shortcuts available for "go to first/last worksheets", having the possibility to assign a shortcut would be less "advance/experimental". I was just taking part of your comment 0 and suggesting a possible alternative way to solve the UX problem. > > the buttons in the GUI > retain this behaviour, and it existed prior to 24.2, so it's hard to imagine > it needs something totally new built. For some users, the arrow UI icons to go to first/prior/next/last worksheet are always grayed out, not clickable. You can click on a specific worksheet tab, but not on the arrows. This is a separate bug report, but somewhat related to this request. > > Regarding exposing something new in the customise list, perhaps a separate > entry for "next sheet - wrap at last" might be comprehensible to users? The functions I mentioned in my comment 2 would be "to first (work)sheet" and "to last (work)sheet". These do not exist, AFAIK. Whether these would deserve to be added, or to provide whichever alternative to this request, it is for the UX Team and other devs to evaluate. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160590] New: Impress crashes when skia is enabled without software rendering: EXC_CRASH (SIGABRT)
https://bugs.documentfoundation.org/show_bug.cgi?id=160590 Bug ID: 160590 Summary: Impress crashes when skia is enabled without software rendering: EXC_CRASH (SIGABRT) Product: LibreOffice Version: 24.2.1.2 release Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: graphics stack Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: libre...@sguazz.it Created attachment 193575 --> https://bugs.documentfoundation.org/attachment.cgi?id=193575&action=edit Apple crash report Hello, I am trying all libreoffice options in order to get more performance on my MacBook Air. Every time I activate skia and remove the software rendering, the application crashes. This is my hardware details: Model: MacBookAir7,2, BootROM 489.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 1,8 GHz, 8 GB, SMC 2.27f2 Graphics: Intel HD Graphics 6000, Intel HD Graphics 6000, Built-In Display: Color LCD, 1440 x 900 (Widescreen eXtended Graphics Array Plus), Main, MirrorOff, Online The Apple crash report (attached to this bug) displays this stack trace: thread 0:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x7ff80f3a mach_msg_trap + 10 1 libsystem_kernel.dylib 0x7ff80f999ca8 mach_msg + 56 2 IOKit 0x7ff812389a7c io_connect_method + 387 3 IOKit 0x7ff812389889 IOConnectCallMethod + 186 4 IOAccelerator 0x7ff81837898f ioAccelResourceFinalize + 165 5 CoreFoundation 0x7ff80fb6a046 _CFRelease + 244 6 Metal 0x7ff8183a7e62 -[MTLIOAccelResource dealloc] + 278 7 Metal 0x7ff8183a7d3f -[MTLIOAccelBuffer dealloc] + 333 8 libskialo.dylib0x10cae954b GrMtlBuffer::onRelease() + 43 9 libskialo.dylib0x10c9e8a3f GrGpuResource::release() + 15 10 libskialo.dylib0x10c9fb647 GrResourceCache::notifyARefCntReachedZero(GrGpuResource*, GrIORef::LastRemovedRef) + 567 [...] Thank you, Giuseppe -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160582] FILEOPEN: CSV, locale setting is not preserved in the import window (regression tdf#152336)
https://bugs.documentfoundation.org/show_bug.cgi?id=160582 ady changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from ady --- Using 24.8 alpha built 2024-04-08, I can confirm that the regional setting in the import dialog is taken from menu Tools > Options > Languages and Locales > (Formats) Locale setting. I modified both the UI language and the Locale setting Options to different values. After restarting LO, the "Locale" setting in the import dialog changed according to the "Locale setting:" field used in Options. I have not tested the other field in the import dialog, "Character set". Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 748561425774fa40ab685fed80d113f7e8301158 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160399] Print Preview freezes with whole row merged in large spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=160399 --- Comment #13 from Telesto --- @Stéphane Guillou Would you mind to test this? It's still slow for me regardless all the effort put into it on Windows - similar as described in comment 8 - when using "Deelnemers en Plaatsnummers Fout" (I haven't retested it on mac) Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 748561425774fa40ab685fed80d113f7e8301158 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101522] [META] Media playback bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101522 --- Comment #24 from Julia --- This valuable insight is a treasure trove for anyone looking to expand their knowledge. Receiving such detailed insights is truly enriching, and I'm eagerly looking forward to delving deeper into this fascinating subject matter. https://reminimod.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160589] Charts are not updated after data entry if freezing of columns or rows is activated
https://bugs.documentfoundation.org/show_bug.cgi?id=160589 Robert Großkopf changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||rob...@familiegrosskopf.de Ever confirmed|0 |1 OS|Windows (All) |All Keywords||regression --- Comment #1 from Robert Großkopf --- Have changed the value in C3 of first table from 25 to 40. Refreshes immediately in Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 6; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded Doesn't refresh in LO 24.2.2.2 on the same system (OpenSUSE 14.6 64bit rpm Linux). Have to press F9 to recalculate. Set this one to NEW and regression -- You are receiving this mail because: You are the assignee for the bug.
[Bug 100497] The information dr3d:vpn is not evaluated in case of parallel projection
https://bugs.documentfoundation.org/show_bug.cgi?id=100497 --- Comment #10 from Regina Henschel --- Still not implemented in Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148251] Use std::swap instead of using temporary values
https://bugs.documentfoundation.org/show_bug.cgi?id=148251 --- Comment #14 from Commit Notification --- AmandaQuaresmaCoutinho committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/ccebd10bc4bea1e65b606a054db3f98ab07850cf tdf#148251 Use std::swap instead of using temporary values 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 160580] Provide config option for "Wraparound" of next/previous sheet shortcut in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=160580 --- Comment #3 from a...@patternjugglers.co.nz --- To clarify, I am not suggesting a new shortcut to go to the first/last sheet - just that the former behaviour of the next/previous shortcuts be made available in some way. The change made in 24.2 alters long standing things that work:just hold down CTRL-PGDN and you end up at the last sheet. If you really need to get there fast, move to the mouse button. Both options give a certain outcome, while the new reaction of the shortcut is to create uncertainty about which sheet will be active. I don't understand any of the architecture, but the buttons in the GUI retain this behaviour, and it existed prior to 24.2, so it's hard to imagine it needs something totally new built. Regarding exposing something new in the customise list, perhaps a separate entry for "next sheet - wrap at last" might be comprehensible to users? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 143781] [META] Development- and code-related bug reports and tasks
https://bugs.documentfoundation.org/show_bug.cgi?id=143781 Bug 143781 depends on bug 159719, which changed state. Bug 159719 Summary: SfxItemPool::IsInRange crash: save and reload in Impress or Draw https://bugs.documentfoundation.org/show_bug.cgi?id=159719 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159719] SfxItemPool::IsInRange crash: save and reload in Impress or Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=159719 Armin Le Grand changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |armin.le.gr...@me.com |desktop.org | Status|NEW |ASSIGNED --- Comment #13 from Armin Le Grand --- @ilmari.lauhakan...@libreoffice.org: Thanks for checking! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 81880] Ability to search Gallery for graphics by description
https://bugs.documentfoundation.org/show_bug.cgi?id=81880 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #15 from Buovjaga --- Can this be closed as fixed now? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 99414] Windows File Browser displays "OpenOffice" as file type to csv format (calc)
https://bugs.documentfoundation.org/show_bug.cgi?id=99414 --- Comment #9 from robomurphy98 --- Still happens in version 7.6 and 24.2. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147132] Flatten Basic function implementations
https://bugs.documentfoundation.org/show_bug.cgi?id=147132 --- Comment #22 from Commit Notification --- AmandaQuaresmaCoutinho committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/bb89fe7ab67c1476b6cf250f236bd5b643a77c6e tdf#147132 Flatten Basic function implementations 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 160589] New: Charts are not updated after data entry if freezing of columns or rows is activated
https://bugs.documentfoundation.org/show_bug.cgi?id=160589 Bug ID: 160589 Summary: Charts are not updated after data entry if freezing of columns or rows is activated Product: LibreOffice Version: 24.2.0.1 rc Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dschei...@gmail.com Created attachment 193574 --> https://bugs.documentfoundation.org/attachment.cgi?id=193574&action=edit Sample file with several charts - with and without frozen columns/rows Charts should always update immediately when the data changes, without another command being executed. If column freezing or row freezing or both are used on a worksheet, the data is only updated after using "Recalculate" F9, or after changing the worksheet or scrolling to another cell range. If you have several charts on a worksheet with frozen columns and you click on one of the charts and then click again in a cell, this chart is updated immediately. The second chart will not. If you switch worksheets and return, all charts will not be updated immediately. I have not noticed the same behavior under Linux. After entering data and pressing Enter, the program was not updated immediately. However, if you made a second movement with the cursor keys, it was then updated. My System: Version: 24.2.0.1 (X86_64) / LibreOffice Community Build ID: b4d45829793cddfe67b58a53f495528c75738d8a CPU threads: 8; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (de_DE); UI: en-US Calc: threaded My tests under LO 7.6.6.3 or older behaved normally. Immediate update! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160481] Cut does not work on chart title text
https://bugs.documentfoundation.org/show_bug.cgi?id=160481 raal changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||r...@post.cz --- Comment #3 from raal --- Confirm with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: dff57d2b4f5abd1b51ebfb0015339471f61e72f9 CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160492] libcdr: recent CorelDraw files are not loaded
https://bugs.documentfoundation.org/show_bug.cgi?id=160492 raal changed: What|Removed |Added Product|LibreOffice |Document Liberation Project Version|24.2.2.2 release|unspecified Component|filters and storage |libcdr CC||r...@post.cz -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160588] FILESAVE: Transparency-related bugs with export to PNG and WEBP
https://bugs.documentfoundation.org/show_bug.cgi?id=160588 --- Comment #3 from Archie Cobbs --- Created attachment 193573 --> https://bugs.documentfoundation.org/attachment.cgi?id=193573&action=edit webp-without-transparency.webp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160588] FILESAVE: Transparency-related bugs with export to PNG and WEBP
https://bugs.documentfoundation.org/show_bug.cgi?id=160588 --- Comment #2 from Archie Cobbs --- Created attachment 193572 --> https://bugs.documentfoundation.org/attachment.cgi?id=193572&action=edit png-with-transparency.png -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160588] FILESAVE: Transparency-related bugs with export to PNG and WEBP
https://bugs.documentfoundation.org/show_bug.cgi?id=160588 --- Comment #1 from Archie Cobbs --- Created attachment 193571 --> https://bugs.documentfoundation.org/attachment.cgi?id=193571&action=edit png-without-transparency.png -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160588] New: FILESAVE: Transparency-related bugs with export to PNG and WEBP
https://bugs.documentfoundation.org/show_bug.cgi?id=160588 Bug ID: 160588 Summary: FILESAVE: Transparency-related bugs with export to PNG and WEBP Product: LibreOffice Version: 24.2.2.2 release Hardware: ARM OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: archie.co...@gmail.com Created attachment 193570 --> https://bugs.documentfoundation.org/attachment.cgi?id=193570&action=edit The ODG test file I'm using this build: https://git.libreoffice.org/core/+log/d56cc158d8a96260b836f100ef4b4ef25d6f1a01 The exports of PNG and WEBP have some bugs. To reproduce: 1. Open bug-example.odg in Draw 2. Export -> PNG -> Do not include transparency 3. Notice image appears normal -> see png-without-transparency.png 4. Export -> PNG -> Include transparency 5. [BUG] Notice text in image is missing color -> see png-with-transparency.png 6. Export -> WEBP 7. [BUG] Notice there is no option for "Include transparency" 8. Notice image appears normal -> see webp-without-transparency.webp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160587] New: Crash in: salhelper::Thread::launch()
https://bugs.documentfoundation.org/show_bug.cgi?id=160587 Bug ID: 160587 Summary: Crash in: salhelper::Thread::launch() Product: LibreOffice Version: 24.2.1.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dcyoung...@frontiernet.net This bug was filed from the crash reporting server and is br-fcbc1d68-5d1e-4fb6-80a8-0bc6c31540a8. = This is PORTABLE version 24.2.1.2 but installed on non-portable media(hard drive). Opened existing spreadsheet from a non-root directory. Changed view to second sheet. Made changes to a chart in area of data range, stretched image. Changed view to first sheet. "Save as", entered a name. Got windows message: application has stopped working. Same thing happens with simple "Save". This has been happening with older versions, not necessarily every save, some work. 23G+ free space on HD. CLUE: On older versions sometimes get "general failure" message. Do not have accurate saved info on these. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101704] Allow extensions to register their own button within a tab in the Notebookbar
https://bugs.documentfoundation.org/show_bug.cgi?id=101704 --- Comment #14 from Szymon Kłos --- The problem is that current Notebookbar architecture and how it work makes it extremely hard to customize... There is no "api" for that. Requirement about adding buttons to existing tabs intersects with general customization of notebookbar - adding / removing items from Customization dialog. I was thinking about that in the past. I think the only complete solution would require lot of work and significant change in the approach to building notebookbar. It needs to be more like our toolbars - build from the definition created using some xml / JSON . Then we can modify the list to add something and it means it is possible to dynamically add something to it (currently not possible, you can only hide item). It has also tradeoff - it will be less flexible on the fly (you will need some coding to get new type of a notebookbar layout). Currently it is possible to just edit .ui file in Glade to do anything. We did mistake when planning - we set as a priority usage of .ui file to make it easy to modify by developers/designers (but in fact it's not easy! Andreas knows something about it :) ). But we should rather focus on providing best experience for the end user as a priority - real customization as a requirement. That is what I think from a time perspective :) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 154715] "Edit Fields" for cross-reference fields should open on the type, format, and selection of the inserted field
https://bugs.documentfoundation.org/show_bug.cgi?id=154715 --- Comment #14 from Commit Notification --- Caolán McNamara committed a patch related to this issue. It has been pushed to "libreoffice-24-2": https://git.libreoffice.org/core/commit/843b3abd2ab05c66533b12ef6a4b155247f99e58 Resolves: tdf#154715 don't use last-used field setting when editing field It will be available in 24.2.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.
[Bug 154715] "Edit Fields" for cross-reference fields should open on the type, format, and selection of the inserted field
https://bugs.documentfoundation.org/show_bug.cgi?id=154715 Commit Notification changed: What|Removed |Added Whiteboard|target:24.8.0 |target:24.8.0 target:24.2.3 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160179] [LOCALHELP] Add description for expert configuration "RecalcOptimalRowHeightMode" options
https://bugs.documentfoundation.org/show_bug.cgi?id=160179 Olivier Hallot changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |olivier.hallot@libreoffice. |desktop.org |org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160586] LibreOffice 7.6 does not load under Windows 10 64 bit.
https://bugs.documentfoundation.org/show_bug.cgi?id=160586 510jrb2...@gmail.com changed: What|Removed |Added CC||510jrb2...@gmail.com --- Comment #1 from 510jrb2...@gmail.com --- Created attachment 193569 --> https://bugs.documentfoundation.org/attachment.cgi?id=193569&action=edit Window troubleshooting report. Windows 10 reports the the soffice file installed under LO 7.6 is "incompatible" and thus will not load. With respect to the "choose file" tab above, I've listed a Writer file which won't open under 7.6. The browser does not list 7.6 on the Desktop. But the icon does show there. JRB -- 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 --- Comment #3 from ady --- FWIW, I never typed either "General" nor "Standard" in the Custom Code box. I either select the General/Standard item from the list, or simply delete the content of the Box and [ENTER] / click OK. When the content of the Custom Code Box is deleted and confirmed (by OK or [ENTER]), the resulting code is General/Standard. @Timur, Perhaps this is not working in the same way in some languages (other than those I am used to use in spreadsheets)? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160370] [META] Grouped objects
https://bugs.documentfoundation.org/show_bug.cgi?id=160370 Bug 160370 depends on bug 160369, which changed state. Bug 160369 Summary: Group anchored to cell below hidden row moves to next cell at save (+ visual left behind, so seems unselectable) https://bugs.documentfoundation.org/show_bug.cgi?id=160369 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107943] [META] Save bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107943 Bug 107943 depends on bug 160369, which changed state. Bug 160369 Summary: Group anchored to cell below hidden row moves to next cell at save (+ visual left behind, so seems unselectable) https://bugs.documentfoundation.org/show_bug.cgi?id=160369 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 Bug 87740 depends on bug 160369, which changed state. Bug 160369 Summary: Group anchored to cell below hidden row moves to next cell at save (+ visual left behind, so seems unselectable) https://bugs.documentfoundation.org/show_bug.cgi?id=160369 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159719] SfxItemPool::IsInRange crash: save and reload in Impress or Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=159719 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 159719] SfxItemPool::IsInRange crash: save and reload in Impress or Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=159719 --- Comment #12 from Commit Notification --- Armin Le Grand (allotropia) committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/b4626d809b50f1d5c1aa8a9644dd3913f5b15503 tdf#159719 reset SfxPoolItemHolder when Pool changes 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 --- Comment #14 from ady --- (In reply to Mike Kaganski from comment #13) > (In reply to m_a_riosv from comment #12) > > This is a very important issue. Please file it as a regression bug. That is now tdf#160582. -- 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 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0582 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160582] FILEOPEN: CSV, locale setting is not preserved in the import window (regression tdf#152336)
https://bugs.documentfoundation.org/show_bug.cgi?id=160582 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2336 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108912] [META] Sheet-level bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108912 ady changed: What|Removed |Added Depends on||160580 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160580 [Bug 160580] Provide config option for "Wraparound" of next/previous sheet shortcut in Calc -- You are receiving this mail because: You are the assignee for the bug.
[Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=98259 ady changed: What|Removed |Added Depends on||160580 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160580 [Bug 160580] Provide config option for "Wraparound" of next/previous sheet shortcut in Calc -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160580] Provide config option for "Wraparound" of next/previous sheet shortcut in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=160580 ady changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6311 CC||heiko.tietze@documentfounda ||tion.org, ||sorot...@gmail.com Blocks||98259, 108912 Hardware|x86-64 (AMD64) |All --- Comment #2 from ady --- While I agree with the request to have a keyboard shortcut(s) to go to the first/last worksheet(s), there are several problems with the request, unfortunately. The first problem to bind a keyboard shortcut to "navigate/go to first worksheet" (and another shortcut for the last worksheet) is that the function is not defined/listed in the Customize list. I am not sure, but I believe a new UNO command would be needed? The "second" problem related to this request is that the arrows that should allow to navigate to first/prior/next/last worksheets are not working. STR: 1. New Calc. 2. Add 3 (empty) worksheets. 3. Try to use the arrow "icons" to navigate to first/prior/next/last worksheets by clicking on any of them. > the arrows are all grayed out. AFAIR, these never worked. There is probably some bug report about this other issue. While this "second" issue is about mouse interaction instead of using the keyboard, these are probably related/connected in some area. Since this request is a consequence of tdf#156311, I am CC'ing Denis Sorotnik and Heiko. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98259 [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108912 [Bug 108912] [META] Sheet-level bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160575] The "x" to close a document near the upper right hand corner is not seen when multiple documents are open
https://bugs.documentfoundation.org/show_bug.cgi?id=160575 V Stuart Foote changed: What|Removed |Added Version|24.8.0.0 alpha0+ Master |Inherited From OOo CC||vsfo...@libreoffice.org Severity|normal |enhancement Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from V Stuart Foote --- Interesting, closing all but the last open document (of any module) restores the closing 'X' of the final document. It also will "expose" the 'LibreOffice Update Available' icon. The 'X' close clickable icon button of any one document in a current session seems worth implementing. Though keyboard (e.g. +w) or by menu does provide the action. But this seems to have been inherited. Behavior present back to the 3.3.0 build. Did OOo ever support the 'X' close button when more than one document is open? =-testing-= Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 30c6e51fc9cb0fa864e1755271343d847fcced25 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 24.2.2.1 (X86_64) / LibreOffice Community Build ID: bf759d854b5ab45b6ef0bfd22e51c6dc4fb8b882 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 7.6.5.1 (X86_64) / LibreOffice Community Build ID: 7d3edae2c3c6b0c6667bcb9e3f9988f28eb82295 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 7.5.9.2 (X86_64) / LibreOffice Community Build ID: cdeefe45c17511d326101eed8008ac4092f278a9 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 6.4.7.2 (x64) Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158556] DOCX Document That Opens/Loads Extremely Slowly
https://bugs.documentfoundation.org/show_bug.cgi?id=158556 --- Comment #19 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "libreoffice-24-2": https://git.libreoffice.org/core/commit/4126c6b94e87f7ad2a1aa93d66bbb3edf67ec790 tdf#158556 speedup docx load It will be available in 24.2.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.
[Bug 160399] Print Preview freezes with whole row merged in large spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=160399 --- Comment #12 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "libreoffice-24-2": https://git.libreoffice.org/core/commit/02b100e8ecbe47bd8d70d81dbefcb24be0501b8b tdf#160399 speed up print preview It will be available in 24.2.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.
[Bug 160399] Print Preview freezes with whole row merged in large spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=160399 Commit Notification changed: What|Removed |Added Whiteboard|target:24.8.0 |target:24.8.0 target:24.2.3 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160586] New: LibreOffice 7.6 does not load under Windows 10 64 bit.
https://bugs.documentfoundation.org/show_bug.cgi?id=160586 Bug ID: 160586 Summary: LibreOffice 7.6 does not load under Windows 10 64 bit. Product: LibreOffice Version: 7.6.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: 510jrb2...@gmail.com Description: When I updated libreOffice to 7.6 and installed it with the Windows installer, then restarted the computer, the link to 7.6 would not install. Neither would any of my .odt files load. This looks like a serious problem since I followed all the instructions in the download site and the Windows installer. Steps to Reproduce: 1.open Windows 10 2.Click on the icon 3.Click on the Open tab Nothing happens. Actual Results: Windows appears to start the load then stops soon afterword Expected Results: LO should load as usual Reproducible: Always User Profile Reset: No Additional Info: Is it a software problem or a problem with the Windows 10 interface? Note for userprofile. I cannot open the LO so I cannot check the userprofile from within LO. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101704] Allow extensions to register their own button within a tab in the Notebookbar
https://bugs.documentfoundation.org/show_bug.cgi?id=101704 --- Comment #13 from Sassitude --- I completely agree with your point. Providing more APIs for extensions to register buttons within existing tabs would indeed offer greater flexibility to developers. This would allow them to integrate their features more seamlessly into the user interface, enhancing the user experience. It's a suggestion that the LO development team should definitely consider. https://geometry-free.com -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160585] Mozilla ARchive (mar) on Win builds not correcting build version in the Win appwiz.cpl
https://bugs.documentfoundation.org/show_bug.cgi?id=160585 --- Comment #3 from Mike Kaganski --- See bug 68274 comment 34. This was anticipated; and the cosmetic issue of wrong displayed version is just a minor thing - much more severe will be modifying / repairing the installation. And I see no way of handling that - given that it's only possible using MSI mechanism, and we don't use that in the MAR technology (which isn't an issue for Mozilla, which never used MSI). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160585] Mozilla ARchive (mar) on Win builds not correcting build version in the Win appwiz.cpl
https://bugs.documentfoundation.org/show_bug.cgi?id=160585 --- Comment #2 from V Stuart Foote --- Created attachment 193568 --> https://bugs.documentfoundation.org/attachment.cgi?id=193568&action=edit the windows registry installer key for LO after MAR update The LO install Windows registry stanzas following MAR update from 24.2.0.3 install to 24.2.2.1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160585] Mozilla ARchive (mar) on Win builds not correcting build version in the Win appwiz.cpl
https://bugs.documentfoundation.org/show_bug.cgi?id=160585 --- Comment #1 from V Stuart Foote --- Created attachment 193567 --> https://bugs.documentfoundation.org/attachment.cgi?id=193567&action=edit the windows registry uninstaller key for LO after MAR update The LO uninstall Windows registry stanzas following MAR update from 24.2.0.3 install to 24.2.2.1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160585] Mozilla ARchive (mar) on Win builds not correcting build version in the Win appwiz.cpl
https://bugs.documentfoundation.org/show_bug.cgi?id=160585 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=68 ||274 CC||mikekagan...@hotmail.com, ||sberg@gmail.com, ||vsfo...@libreoffice.org Blocks||54242 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=54242 [Bug 54242] [META] Incremental update + automatic update support -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54242] [META] Incremental update + automatic update support
https://bugs.documentfoundation.org/show_bug.cgi?id=54242 V Stuart Foote changed: What|Removed |Added Depends on||160585 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160585 [Bug 160585] Mozilla ARchive (mar) on Win builds not correcting build version in the Win appwiz.cpl -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160585] New: Mozilla ARchive (mar) on Win builds not correcting build version in the Win appwiz.cpl
https://bugs.documentfoundation.org/show_bug.cgi?id=160585 Bug ID: 160585 Summary: Mozilla ARchive (mar) on Win builds not correcting build version in the Win appwiz.cpl Product: LibreOffice Version: 24.2.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Installation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vsfo...@libreoffice.org Mozilla ARchive (mar) on Win builds not correcting build version in the Win appwiz.cpl A new install of 24.2.0.3 with a 'setx LIBO_UPDATER_TEST_ENABLE "1" /M' applied, will perform MAR update cycle on initial launch. Currently from 24.2.0.3 --> 24.2.2.1 (bf759d8), but stops there. Is the 24.2.2.2 final not yet processing? Beyond that, opening the Windows "Programs and Features" dialog (appwiz.cpl from cmd prompt) the updated LibreOffice install is still 'Named' LibreOffice 24.2.0.3 from the initial package install, but also continues to show 'Version' 24.2.0.3 which is not helpful. Other MAR updated programs, e.g. Firefox or Thunderbird, record and show the current 'Version' on the appwiz panel and in the Windows registry. Panel clips for the Windows registry install and uninstall keys attached. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160495] FILESAVE, FORMATTING
https://bugs.documentfoundation.org/show_bug.cgi?id=160495 --- Comment #2 from s.un...@checkpointmedia.com --- Created attachment 193566 --> https://bugs.documentfoundation.org/attachment.cgi?id=193566&action=edit testfile with line break over problem in combined cells Hello, please find a testfile with the line break over problem enclosed. Please have a look at the combined cells in the 'print range' marked area. If the the format is corrected by using the line break over button all seems fine. But once the file is saved and opened again with the latest LE version 24.2.2 (and 24.2.1) the line breakovers are gone again. If an older file is opened all the line breakovers are missing too. One can correct that by touching up all cells, but the changes are lost on reopening too. I reverted back to 7.6.4.1 for now as I need the software for daily work. Hence this version is not having that issue I can not test this behaviour currently. Best regards -- You are receiving this mail because: You are the assignee for the bug.
[Bug 89606] [META] Table of Contents and Indexes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=89606 Bug 89606 depends on bug 160067, which changed state. Bug 160067 Summary: Fileopen: table of content missformatted (wrapped to next page without visible reason) https://bugs.documentfoundation.org/show_bug.cgi?id=160067 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160182] Short cut to next page (ELEMENT)
https://bugs.documentfoundation.org/show_bug.cgi?id=160182 --- Comment #5 from jeffreyreed...@gmail.com --- Thank you Dieter for your efforts. I understand why you could not confirm, I believe. I got the issue "almost" resolved by adjusting the size to be undersized. I say "almost" because it doesn't seem to be an appropriate parameter to effect the process. I did this on a Mac Mini M2 running Sonoma. I don't think it is a Mac issue only but it could be. I have successfully gotten 10 files to work. I don't know if it is worth any additional effort. I have 40 more files to adjust and if I have another issue T will submit another bug report, or amend this, if I can find it. Thank you for your help Jeff Reed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160458] Char unveiled in Calc and Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=160458 --- Comment #6 from Marc Cabana --- Created attachment 193565 --> https://bugs.documentfoundation.org/attachment.cgi?id=193565&action=edit Strange char in input bar Menu->Insert->Special char looks like this! Strange char in input bar -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160458] Char unveiled in Calc and Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=160458 --- Comment #5 from Marc Cabana --- (In reply to m_a_riosv from comment #4) > You can use Menu/Insert/Special character > > Also introducing the hexadecimal code plus [Alt+X] > 2713+[Alt+X] > > https://help.libreoffice.org/24.8/en-US/text/shared/01/0410. > html?&DbPAR=CALC&System=WIN > https://help.libreoffice.org/24.8/en-US/text/shared/04/0101. > html?&DbPAR=CALC&System=WIN#unicode_shortcut I'm using a MacBook so I'm in MacOS! Visibily all chars are confused Look to the capture of the april 8th! -- You are receiving this mail because: You are the assignee for the bug.
