[Bug 108014] [META] Writer character style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108014 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||148949 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148949 [Bug 148949] Libreoffice crash when trying to delete the "Standard" character style using API. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 127592] [META] LibreOffice Basic macros incl."Option Compatible" modules
https://bugs.documentfoundation.org/show_bug.cgi?id=127592 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||148949 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148949 [Bug 148949] Libreoffice crash when trying to delete the "Standard" character style using API. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148949] Libreoffice crash when trying to delete the "Standard" character style using API.
https://bugs.documentfoundation.org/show_bug.cgi?id=148949 Stéphane Guillou (stragu) changed: What|Removed |Added Version|3.3.0 release |Inherited From OOo CC||stephane.guillou@libreoffic ||e.org, ||vmik...@collabora.com Crash report or||["SwUndoFormatDelete::SwUnd crash signature||oFormatDelete","libswlo.so" ||] Blocks||127592, 108014 --- Comment #7 from Stéphane Guillou (stragu) --- Still reproduced in recent daily build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f4ef5435df5560e6b6b061ce4053c71e2819bf51 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Getting crash signature "libswlo.so" in 24.2.2: https://crashreport.libreoffice.org/stats/crash_details/9335bff0-065d-4fb3-8adc-6a1ecb80111f And "SwUndoFormatDelete::SwUndoFormatDelete" in 6.2.0.3 and 6.3.0.4: - https://crashreport.libreoffice.org/stats/crash_details/820f9935-060f-4ed7-b36d-c0e8298dbf1c - https://crashreport.libreoffice.org/stats/crash_details/550ba548-9293-459e-8592-dd8d68dda885 Running the same macro in 6.1.0.3 and earlier, it does not crash, and instead can't find the "Standard" character style: BASIC runtime error. An exception occurred Type: com.sun.star.container.NoSuchElementException Message: . Name "Standard" exists since: commit 9d754a59154c40235c240bb0e7f47a2006fa85bd author Miklos VajnaMon Jul 09 18:03:04 2018 +0200 committerMiklos VajnaMon Jul 09 20:04:26 2018 +0200 sw: give the 'Default Style' char style a programmatic name Reviewed-on: https://gerrit.libreoffice.org/57191 (this is [eaeddeb2c1de88ee0ee9f4be7316efefe0e44f24] in linux-64-6.2 bibisect repo) So one can crash it earlier than 6.2 by using e.g. "Default Style" instead. Back in OOo 3.3, it would be "Default" and would crash all the same. (Miklos, copying you in in case you're interested) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108014 [Bug 108014] [META] Writer character style bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=127592 [Bug 127592] [META] LibreOffice Basic macros incl."Option Compatible" modules -- You are receiving this mail because: You are the assignee for the bug.
[Bug 127592] [META] LibreOffice Basic macros incl."Option Compatible" modules
https://bugs.documentfoundation.org/show_bug.cgi?id=127592 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|[META] LibreOffice Basic|[META] LibreOffice Basic |incl."Option Compatible"|macros incl."Option |modules |Compatible" modules -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160739] Raise a matrix to an exponential with Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=160739 --- Comment #6 from xhertan --- Today I updated to version 24.2 and this error persists. Version: 24.2.2.1 (X86_64) Build ID: 420(Build:1) I noticed that this report remains UNCONFIRMED. Any progress on this? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156807] LibreOffice Calc and Writer - button and input line decoration offset, rendered on canvas
https://bugs.documentfoundation.org/show_bug.cgi?id=156807 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|Libreoffice calc and writer |LibreOffice Calc and Writer |- gray marks on interface |- button and input line |rendering |decoration offset, rendered ||on canvas Blocks||112286 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112286 [Bug 112286] [META] gtk3 themeing -- You are receiving this mail because: You are the assignee for the bug.
[Bug 112286] [META] gtk3 themeing
https://bugs.documentfoundation.org/show_bug.cgi?id=112286 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156807 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156807 [Bug 156807] LibreOffice Calc and Writer - button and input line decoration offset, rendered on canvas -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133686] Crash or lag/freeze changing master slide on several slides (Linux with gen backend)
https://bugs.documentfoundation.org/show_bug.cgi?id=133686 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Blocks||103460 Keywords||perf Summary|Crash or lag changing |Crash or lag/freeze |templates (Linux with gen |changing master slide on |backend)|several slides (Linux with ||gen backend) --- Comment #4 from Stéphane Guillou (stragu) --- Still struggling/hanging with gen VCL plugin; not reproduced with gtk3, kf5, win. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f4ef5435df5560e6b6b061ce4053c71e2819bf51 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: x11 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Telesto, can you still crash it? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103460 [Bug 103460] [META] Master Slides deck/tab of the sidebar -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103460] [META] Master Slides deck/tab of the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=103460 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||133686 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=133686 [Bug 133686] Crash or lag/freeze changing master slide on several slides (Linux with gen backend) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160659] LibreOffice crashed while adding Google Drive service
https://bugs.documentfoundation.org/show_bug.cgi?id=160659 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160509] Modal Window on FILEOPEN for Read-Only (e.g. out of an eMail) SECOND file is hidden behind
https://bugs.documentfoundation.org/show_bug.cgi?id=160509 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160701] OpenPGP warning when encrypting with an untrusted public key: rename from "Error" to "Warning"
https://bugs.documentfoundation.org/show_bug.cgi?id=160701 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160694] One user interface does not have the same menu as another
https://bugs.documentfoundation.org/show_bug.cgi?id=160694 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160697] Writer opens blank window temporarily at launch
https://bugs.documentfoundation.org/show_bug.cgi?id=160697 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113196] [META] Korean language-specific CJK issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113196 Bug 113196 depends on bug 157280, which changed state. Bug 157280 Summary: Impress's parenthesis rendering is wrong on Korean texts https://bugs.documentfoundation.org/show_bug.cgi?id=157280 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157280] Impress's parenthesis rendering is wrong on Korean texts
https://bugs.documentfoundation.org/show_bug.cgi?id=157280 --- Comment #10 from QA Administrators --- Dear DaeHyun Sung, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156807] Libreoffice calc and writer - gray marks on interface rendering
https://bugs.documentfoundation.org/show_bug.cgi?id=156807 --- Comment #13 from QA Administrators --- Dear Barabba, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158042] FILEOPEN : PDF : Error when opening PDF file
https://bugs.documentfoundation.org/show_bug.cgi?id=158042 --- Comment #6 from QA Administrators --- Dear intmail01, 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 98162] Page-anchored image skips to edge when moved by mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=98162 --- Comment #5 from QA Administrators --- Dear Stanislav Horacek, 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 157938] Possible missing font for %kappa in pdf with embedded fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=157938 --- Comment #2 from QA Administrators --- Dear Dan Brown, 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 129826] Storing language based user defined format codes of cells does not work for color code based entries.
https://bugs.documentfoundation.org/show_bug.cgi?id=129826 --- Comment #8 from QA Administrators --- Dear Ralf Hendel, 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 132410] UI: Image properties Keep ratio is inherent from previous session
https://bugs.documentfoundation.org/show_bug.cgi?id=132410 --- Comment #5 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 148532] FILEOPEN RTF Line shapes anchored in table are positioned vertically lower than in Word
https://bugs.documentfoundation.org/show_bug.cgi?id=148532 --- Comment #3 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 126873] Rotated text boxes have abnormally large hit area / hot zone
https://bugs.documentfoundation.org/show_bug.cgi?id=126873 --- Comment #13 from QA Administrators --- Dear DarkTrick, 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 104009] Layout and visibility cell content changes while zooming out (with non-monospace fonts)
https://bugs.documentfoundation.org/show_bug.cgi?id=104009 --- Comment #8 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 141578] Libreoffice unusable with different scale factors used for different screens in multimonitor setup (on kf5/qt5/qt6 vcl + wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=141578 --- Comment #58 from typing...@gmail.com --- (In reply to Michael Weghorn from comment #45) > * The LO window is displayed properly on one of the screens at least, so > moving the window to that screen should be a functioning workaround. In my case, I have two monitors: 1080p (secondary) and 4K (main), and LO looks normal on the 1080p, and looks tiny on the 4K. So, "moving the window to that screen" is not really a good workaround, because I have to work on the small secondary monitor. Unless... there is a way to choose on which of the two monitors LO can look normal? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160878] Crash in: vcl::Window::ImplGetWinData()
https://bugs.documentfoundation.org/show_bug.cgi?id=160878 --- Comment #2 from Stéphane Guillou (stragu) --- (In reply to Stéphane Guillou (stragu) from comment #1) > Result: > - picture fits the margins automatically when inserted > - no crash Tested with: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160878] Crash in: vcl::Window::ImplGetWinData()
https://bugs.documentfoundation.org/show_bug.cgi?id=160878 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org OS|All |Windows (All) Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO Hardware|All |x86-64 (AMD64) --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report, Ellen. I tested the following: 1. Open Writer 24.2.2 2. Insert this large PNG picture: https://upload.wikimedia.org/wikipedia/commons/thumb/e/e2/Large_Magellanic_Cloud_rendered_from_Gaia_EDR3.png/2048px-Large_Magellanic_Cloud_rendered_from_Gaia_EDR3.png 3. Make smaller using top right corner 4. Make smaller using bottom right corner Result: - picture fits the margins automatically when inserted - no crash If you are able to reproduce with more precise steps, and attach a sample document/image to use, it would be very much appreciated! Please also share the version info copied with the button in Help > About LibreOffice. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115518] [META] Old user profile causing problems when upgrading to new release
https://bugs.documentfoundation.org/show_bug.cgi?id=115518 Bug 115518 depends on bug 160879, which changed state. Bug 160879 Summary: Find and replace only work in safe mode https://bugs.documentfoundation.org/show_bug.cgi?id=160879 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115518] [META] Old user profile causing problems when upgrading to new release
https://bugs.documentfoundation.org/show_bug.cgi?id=115518 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160879 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160879 [Bug 160879] Find and replace only work in safe mode -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160879] Find and replace only work in safe mode
https://bugs.documentfoundation.org/show_bug.cgi?id=160879 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |WORKSFORME Version|7.6.6.3 release |7.2.3.2 release Status|UNCONFIRMED |RESOLVED Blocks||115518 CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- Thanks for the report, Ray. Let's mark as "works for me" as your issue is resolved after a full reinstall, and it will be difficult to investigate further without profiles to compare + knowledge of which LO version you were using before going from 6 to 7. For good measure I tested: 1. create a new user profile with LO 6.4.8+ (linux-64-6.4 bibisect repo's master) 2. copy across that profile to an installation of LO 7.2.8+ (linux-64-7.2 bibisect repo's master) 3. Test Ctrl + H with Writer 7.2: it works. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=115518 [Bug 115518] [META] Old user profile causing problems when upgrading to new release -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160880] Poor visibility of enabled menu items in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=160880 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #2 from Stéphane Guillou (stragu) --- Thanks for the report. Which Windows theme are you using? Looks like the same issue as bug 152534. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160879] Find and replace only work in safe mode
https://bugs.documentfoundation.org/show_bug.cgi?id=160879 --- Comment #1 from Ray Shain --- The bug originally appeared after an update. I just completely deleted Libre Office from my machine, including Appdata entries but without editing the registry. I then did a clean install, and find and replace works in normal mode. This seems to indicate some issue with the automating scripts in the upgrade process of the install program. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160880] Poor visibility of enabled menu items in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=160880 ZhongLi changed: What|Removed |Added CC||ryanjiang2...@21cn.com --- Comment #1 from ZhongLi --- Created attachment 193914 --> https://bugs.documentfoundation.org/attachment.cgi?id=193914=edit Unreadable Text image -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160880] New: Poor visibility of enabled menu items in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=160880 Bug ID: 160880 Summary: Poor visibility of enabled menu items in dark mode Product: LibreOffice Version: 24.2.0.0 alpha0+ Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ryanjiang2...@21cn.com Description: in Writer, I chose the tabstrip layout, and it turns out that the light yellow background of the enabled items and the white text makes it hard to read. I am using this version of LibreOffice Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: zh-CN (zh_CN); UI: zh-CN Calc: CL threaded Steps to Reproduce: 1. Open Writer in dark mode 2. choose Tabstrip UI mode 3. Click on any tabstrip with an enabled item Actual Results: "Enabled" items were shown with a white font on a light yellow background, making the text unreadable Expected Results: The text become black or the background become dark blue, etc, making the text more clear. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: zh-CN (zh_CN); UI: zh-CN Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160879] New: Find and replace only work in safe mode
https://bugs.documentfoundation.org/show_bug.cgi?id=160879 Bug ID: 160879 Summary: Find and replace only work in safe mode Product: LibreOffice Version: 7.6.6.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: raysh...@gmail.com Created attachment 193913 --> https://bugs.documentfoundation.org/attachment.cgi?id=193913=edit Windows config from about This problem occurs in version 7.6.6.3, and in the prior version I was using, 7.2.3.2. When in normal mode, neither clicking the find and replace menu item under edit nor the keyboard CTRL-H will bring up the find and replace dialog window. When I reopen Writer in safe mode, all works as intended. My machine info is attached as windows spec.jpg. I have no user installed extensions in writer. I've restarted in safe mode, resetting my entire user profile to factory settings and archiving my old profile. After testing find and replace successfully, I've restarted in normal mode, saving as appropriate, and the function again fails to appear when selected. I first noticed this issue when I went from version 6 to version 7. I was trying to wait for a fix in later versions, but the same thing happens after each update. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160878] New: Crash in: vcl::Window::ImplGetWinData()
https://bugs.documentfoundation.org/show_bug.cgi?id=160878 Bug ID: 160878 Summary: Crash in: vcl::Window::ImplGetWinData() Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ellen.sann...@alumni.stanford.edu This bug was filed from the crash reporting server and is br-174bc3b2-33dd-48fe-9de6-174e9ebe5259. = I was resizing a photo that I had added to my document because it did not fit within the margins. I change it from the top the first time using the right corner arrow to proportionally shorten the photo. Then I looked at the bottom of the page and the picture was still too long for the page. I attempted to resize the photo from the bottom right and it crashed. The photo was a .png of white text on a black background. FORMATTING -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160873] Usability: "OLE Object" probably not familiar language (Menu: Insert/OLE Object)
https://bugs.documentfoundation.org/show_bug.cgi?id=160873 Stéphane Guillou (stragu) changed: What|Removed |Added Component|Writer |UI --- Comment #2 from Stéphane Guillou (stragu) --- (changed component to "UI" because it would have to be changed outside of Writer too, e.g. in Calc) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 85811] [META] Main menu bar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=85811 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160873 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160873 [Bug 160873] Usability: "OLE Object" probably not familiar language (Menu: Insert/OLE Object) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160873] Usability: "OLE Object" probably not familiar language (Menu: Insert/OLE Object)
https://bugs.documentfoundation.org/show_bug.cgi?id=160873 Stéphane Guillou (stragu) changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Blocks||85811 --- Comment #1 from Stéphane Guillou (stragu) --- In essence, I agree that users might not use that submenu because of how obscure the name is to them. But if we go further and actually rename from "OLE object" to something else, there are many places where the term is used, including the Navigator. And then there's hundreds of updates for help pages and guides. How would one differentiate OLE objects from others then? It would have to be more verbose, like "Linked or Embedded Objects". So I guess my opinion is: OK to not use "OLE" in the menu, but against changing it to something else elsewhere. (In reply to jan d from comment #0) > I could not find out if QR-Code actually uses OLE, > since there is no editing capability exposed and the result seems to be > handeled as an image, which is what OLE actually should overcome. I was actually wondering about that. Seems like QR/Barcode shouldn't be in there anyway. And when the feature was recently shared on social media, users were surprised it was so hidden away. +1 to pull those out of the OLE submenu if possible, or use a more intuitive categorisation so it doesn't get too big. (It's already the biggest menu in Writer with View and Format.) Also: chart is not in the OLE submenu, but it is an OLE object! Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=85811 [Bug 85811] [META] Main menu bar bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160732] Rename "Navigation" toolbar to clarify its role, avoid confusion, and relate to "Navigate by - Recency"
https://bugs.documentfoundation.org/show_bug.cgi?id=160732 --- Comment #12 from Stéphane Guillou (stragu) --- (In reply to V Stuart Foote from comment #11) > (In reply to Eyal Rozenberg from comment #10) > > How about "Navigate History" or "Navigate Positions"? > I think the idea is to remove navigate/navigation/navigator from the mix and > avoid any potential to misidentify. Indeed, and it has the added benefit of being able to use the same string in Navigate By (without repeating "Navigate"). I think we need both "history" for the familiarity with browsers, and "position" to clarify it's about cursor position (and not age of objects). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155633] Can't use a custom bibliography database source for Insert > TOC & Indexes > Bibliography Entry
https://bugs.documentfoundation.org/show_bug.cgi?id=155633 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEEDINFO|NEW -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160732] Rename "Navigation" toolbar to clarify its role, avoid confusion, and relate to "Navigate by - Recency"
https://bugs.documentfoundation.org/show_bug.cgi?id=160732 --- Comment #11 from V Stuart Foote --- (In reply to Eyal Rozenberg from comment #10) > How about "Navigate History" or "Navigate Positions"? > > I'm also ok with "Position History", although I like that less. I think the idea is to remove navigate/navigation/navigator from the mix and avoid any potential to misidentify. "Position History" seems to work best in that context. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160810] Writer: comment thread broken for comments without selected text
https://bugs.documentfoundation.org/show_bug.cgi?id=160810 Timur changed: What|Removed |Added Summary|Writer: comment thread |Writer: comment thread |broken |broken for comments without ||selected text -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160877] New: Paragraph Signature deleted after visualizing printout or when opening (paragraph signed) file
https://bugs.documentfoundation.org/show_bug.cgi?id=160877 Bug ID: 160877 Summary: Paragraph Signature deleted after visualizing printout or when opening (paragraph signed) file Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: framework Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: olivier.hal...@libreoffice.org Blocks: 123810 Summary: After signing several paragraphs, print visualization remove all signatures. Steps: 1) create a new text file 2) add text 3) Sign paragraph 4) Visualize printout 5) close visualization Results: all paragraph signatures are gone Expected results: all signatures maintained. Similar issue when opening writer file 1) sign paragraph in a text files 2) save 3) close file 4) open file Results: all paragraph signatures are gone Expected results: all signatures preserved. Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: pt-BR Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=123810 [Bug 123810] [META] Classification bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 123810] [META] Classification bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=123810 Olivier Hallot changed: What|Removed |Added Depends on||160877 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160877 [Bug 160877] Paragraph Signature deleted after visualizing printout or when opening (paragraph signed) file -- You are receiving this mail because: You are the assignee for the bug.
[Bug 85094] When printing ODT with mixed portrait and landscape, last page has incorrect orientation
https://bugs.documentfoundation.org/show_bug.cgi?id=85094
Julien Nabet changed:
What|Removed |Added
CC||serval2...@yahoo.fr
--- Comment #18 from Julien Nabet ---
Just for the record, if I use this patch to revert print part in old Armin's
patch:
diff --git a/vcl/source/gdi/print.cxx b/vcl/source/gdi/print.cxx
index 06625a4227bd..dbdf8c9bafe2 100644
--- a/vcl/source/gdi/print.cxx
+++ b/vcl/source/gdi/print.cxx
@@ -1307,23 +1307,10 @@ bool Printer::SetPaperSizeUser( const Size& rSize )
const Size aPixSize = LogicToPixel( rSize );
const Size aPageSize = PixelToLogic(aPixSize,
MapMode(MapUnit::Map100thMM));
-bool bNeedToChange(maJobSetup.ImplGetConstData().GetPaperWidth() !=
aPageSize.Width() ||
-maJobSetup.ImplGetConstData().GetPaperHeight() != aPageSize.Height());
-
-if(!bNeedToChange)
-{
-// #i122984# only need to change when Paper is different from
PAPER_USER and
-// the mapped Paper which will created below in the call to
ImplFindPaperFormatForUserSize
-// and will replace maJobSetup.ImplGetConstData()->GetPaperFormat().
This leads to
-// unnecessary JobSetups, e.g. when printing a multi-page fax, but
also with
-// normal print
-const Paper aPaper = ImplGetPaperFormat(aPageSize.Width(),
aPageSize.Height());
-
-bNeedToChange = maJobSetup.ImplGetConstData().GetPaperFormat() !=
PAPER_USER &&
-maJobSetup.ImplGetConstData().GetPaperFormat() != aPaper;
-}
-
-if(bNeedToChange)
+if ( (maJobSetup.ImplGetConstData().GetPaperFormat() != PAPER_USER) ||
+ (maJobSetup.ImplGetConstData().GetPaperWidth() != aPageSize.Width())
||
+ (maJobSetup.ImplGetConstData().GetPaperHeight() !=
aPageSize.Height())
+)
{
JobSetup aJobSetup = maJobSetup;
ImplJobSetup& rData = aJobSetup.ImplGetData();
preview in print dialog works well (first page in portrait, second in
landscape, third in portrait)
Also we've been using libtiff since 2022-05 so perhaps the whole patch is
obsolete.
"itiff.cxx" is now in vcl/source/filter/itiff and only contains 360 lines
"ccidecom.hxx" and "ccidecom.cxx" don't exist anymore in LO codebase.
To be sure, we'd need someone who has a fax and able to test a build with the
above patch, not simple I suppose...
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 155633] Can't use a custom bibliography database source for Insert > TOC & Indexes > Bibliography Entry
https://bugs.documentfoundation.org/show_bug.cgi?id=155633 --- Comment #4 from ajlittoz --- (In reply to Stéphane Guillou (stragu) from comment #3) > (In reply to ajlittoz from comment #2) > ajlittoz, do you agree these are the steps? Yes -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160836] unable to resize table row height with mouse, if contains an image which cropped by the fixed row height
https://bugs.documentfoundation.org/show_bug.cgi?id=160836 --- Comment #3 from Commit Notification --- László Németh committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/38b6e89c9483fdfe3d26bef3b25f890528aef84e tdf#160836 sw: fix narrow selection area of cell border 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 160870] Continues footnote number is flipped
https://bugs.documentfoundation.org/show_bug.cgi?id=160870 ardv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Bug 56408] Writer always breaks lines at text direction change, leaving orphan bracket
https://bugs.documentfoundation.org/show_bug.cgi?id=56408 خالد حسني changed: What|Removed |Added CC||kava...@yahoo.com --- Comment #27 from خالد حسني --- *** Bug 160854 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160854] in Arabic right to left text parenthesis will be broke
https://bugs.documentfoundation.org/show_bug.cgi?id=160854 خالد حسني changed: What|Removed |Added CC||kha...@libreoffice.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from خالد حسني --- *** This bug has been marked as a duplicate of bug 56408 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160874] Calc fails to suggest correction for formula cell without equal sign
https://bugs.documentfoundation.org/show_bug.cgi?id=160874 --- Comment #3 from ady --- (In reply to ady from comment #2) > If this behavior is implemented, it would mean that instead of the current > suggestion (i.e. adding the apostrophe and changing the value from numerical > to text), the new behavior would silently skip any suggestion and would > automatically add the initial equal sign, turning the cell into a formula. I would like to suggest, if the request from comment 0 is implemented, instead of being silently and automatically converted into a formula, that a suggestion should still be presented, as it is currently the case (just with a different suggestion, converting the cell into a formula rather than into a text cell). A silent and automatic action would allow mistakes that would not be easy to spot in real time, especially when the current behavior would stop such mistake. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160876] New: user.documentfoundation.org account generation fails
https://bugs.documentfoundation.org/show_bug.cgi?id=160876 Bug ID: 160876 Summary: user.documentfoundation.org account generation fails Product: LibreOffice Version: 7.5.7.1 release Hardware: Other OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dbaker...@dlbaker.us Description: I tried to create an account on user.documentfoundation.org, after getting sent there by LibreOffice Online Help. It seemed to go well until I tried to log in - only to find that what I had just entered was Invalid. Cheers or Jeers Actual Results: Invalid Account notice Expected Results: I expected it to work Reproducible: Didn't try User Profile Reset: No Additional Info: Accepted what I had just put into it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160874] Calc fails to suggest correction for formula cell without equal sign
https://bugs.documentfoundation.org/show_bug.cgi?id=160874 --- Comment #2 from ady --- IMHO, there are enough issues with unary operators. If the cell contains a simple negative numeric value and users want to modify the cell to contain instead a formula, then the initial equal sign should also be (manually) added by the user. That's just my personal subjective opinion. Having Calc guessing the user's intention is nice, until each user wants the guess to be different. That's how we (users) get the "initial sometimes-hidden apostrophe" (which some users are unaware of, or don't understand its meaning), or "why this column in my csv file is imported as text instead of as numbers", or the exact opposite reports/questions. Now, if the request from comment 0 (to automatically add the equal sign when the user modifies a simple negative/positive numeric value, turning it into what could probably be interpreted as a formula), then all sorts of regression tests should be added too, in order to reduce follow-ups such as "my csv is imported differently now", or, if some other behavior is modified as a consequence, it should be clearly described too (instead of finding out just by chance, in the best case). If this behavior is implemented, it would mean that instead of the current suggestion (i.e. adding the apostrophe and changing the value from numerical to text), the new behavior would silently skip any suggestion and would automatically add the initial equal sign, turning the cell into a formula. When there is no additional operator edited, clicking on another cell should leave the original cell without change and the clicked-on cell would be the new active cell. This is the current behavior and should not change. Please note that the reported behavior happens not only with negative values, but with any numerical value. Please also note that the reported behavior happens only when editing existing numerical values. When the cell has no prior content (and it is not pre-formatted as text), then the initial equal sign is indeed automatically added when clicking on some other cell. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160875] New: Calc partially fails, requires computer restart
https://bugs.documentfoundation.org/show_bug.cgi?id=160875 Bug ID: 160875 Summary: Calc partially fails, requires computer restart Product: LibreOffice Version: 7.5.7.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dbaker...@dlbaker.us 2023 Mac M2 mini, Sonoma 14.4.1 I tried to edit a graph in Calc, and the Format Axis box refused to allow me to change the number type. Clicking on the format types did not respond. Furthermore, About LibreOffice does not respond. Restarting LibreOffice doesn't work. I have to restart the computer. In the middle of my work. At least I was able to save it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158221] Insert bookmarks dialogue takes a very long time to appear when there are many bookmarks
https://bugs.documentfoundation.org/show_bug.cgi?id=158221 BogdanB changed: What|Removed |Added Regression By||Michael Stahl -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158221] Insert bookmarks dialogue takes a very long time to appear when there are many bookmarks
https://bugs.documentfoundation.org/show_bug.cgi?id=158221 --- Comment #5 from bdgri...@mailbolt.com --- Insert > Bookmark also fails for me in version 7.6.2.1 and also in the latest version 24.2. It looks like the same problem. I select Insert > Bookmark and just after the Bookmark dialog appears, the document starts paging through the pages on its own. This will go on for 15 minutes or so. If I don't want for it to finish and instead click on any of the document pages as it is flipping by, it freezes the paging, but displays a hourglass (blue rotating circle) and appears to hang with all of Writer controls being disabled. There are hundreds of pages in the document. The last version where Insert > Bookmarks WORKED for me was: Version: 7.4.7.2 (x64) / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded So a change must have been added after 7.4.7.2 that caused this problem. It has been nearly 6 months since this problem has been reported. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160324] Column resize handle touch-target too small
https://bugs.documentfoundation.org/show_bug.cgi?id=160324 --- Comment #7 from Eyal Rozenberg --- (In reply to jon.macca...@gmail.com from comment #0) > The column resize handle touch target is only 1-2px wide, It's at least 4 px wide, if not 5, for me. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ffccbf4762a9ae810bcdd21c41fccdd436e7bfc9 CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US Could this be a Windows-specific problem? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160732] Rename "Navigation" toolbar to clarify its role, avoid confusion, and relate to "Navigate by - Recency"
https://bugs.documentfoundation.org/show_bug.cgi?id=160732 --- Comment #10 from Eyal Rozenberg --- How about "Navigate History" or "Navigate Positions"? I'm also ok with "Position History", although I like that less. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 143387] CRASH: undoing paste ( debug build )
https://bugs.documentfoundation.org/show_bug.cgi?id=143387 --- Comment #14 from Commit Notification --- Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/17b2f3d96fb21dcfc2fb8e54ca9670a8c58840f1 tdf#143320, tdf#143387: sw_uiwriter4: Add unittest 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 143387] CRASH: undoing paste ( debug build )
https://bugs.documentfoundation.org/show_bug.cgi?id=143387 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 143320] Crash at paste/undo paste again (swlo!BigPtrArray::Index2Block+0xc8)
https://bugs.documentfoundation.org/show_bug.cgi?id=143320 Commit Notification changed: What|Removed |Added Whiteboard|target:7.3.0 target:7.2.0.2 |target:7.3.0 target:7.2.0.2 ||target:24.8.0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160806] Cannot ascend accessibility tree from calc document to app
https://bugs.documentfoundation.org/show_bug.cgi?id=160806 Michael Weghorn changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de |desktop.org | Status|NEW |ASSIGNED --- Comment #9 from Michael Weghorn --- (In reply to Joanmarie Diggs from comment #0) > Steps to Reproduce: > 1. Launch Calc > 2. Launch the attached accessible-event listener in a terminal The order is actually relevant: The issue is (more) reproducible when starting Calc before starting running the script. The commit from comment 7 makes the case when AT is started before LO more reliable, but further analysis + fixing is needed in particular for the case where LO is started first. (I have an approach in mind now.) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160806] Cannot ascend accessibility tree from calc document to app
https://bugs.documentfoundation.org/show_bug.cgi?id=160806 --- Comment #8 from Commit Notification --- Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/be543e321552d4331e7dddca954a2b57f4c7f379 tdf#159369 tdf#160806 gtk3 a11y: Drop fallback dummy a11y obj 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 159369] Cursor off screen at high document zoom level and high Gnome magnification (Wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=159369 --- Comment #13 from Commit Notification --- Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/be543e321552d4331e7dddca954a2b57f4c7f379 tdf#159369 tdf#160806 gtk3 a11y: Drop fallback dummy a11y obj 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 160837] ACCESSIBILITY: toolbar positions are incorrectly reported to AT-SPI2
https://bugs.documentfoundation.org/show_bug.cgi?id=160837 --- Comment #2 from Commit Notification --- Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/252b1591d5e4e3adbf7063b56c2b578fe046ad3d tdf#159369 tdf#160806 tdf#160837 gtk3 a11y: Don't skip parents one way 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 160806] Cannot ascend accessibility tree from calc document to app
https://bugs.documentfoundation.org/show_bug.cgi?id=160806 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 160837] ACCESSIBILITY: toolbar positions are incorrectly reported to AT-SPI2
https://bugs.documentfoundation.org/show_bug.cgi?id=160837 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 160806] Cannot ascend accessibility tree from calc document to app
https://bugs.documentfoundation.org/show_bug.cgi?id=160806 --- Comment #7 from Commit Notification --- Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/252b1591d5e4e3adbf7063b56c2b578fe046ad3d tdf#159369 tdf#160806 tdf#160837 gtk3 a11y: Don't skip parents one way 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 159369] Cursor off screen at high document zoom level and high Gnome magnification (Wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=159369 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 159375] Opening Tools > Options dialog takes too long
https://bugs.documentfoundation.org/show_bug.cgi?id=159375
Bayram Çiçek changed:
What|Removed |Added
CC||kolafl...@kolahilft.de
--- Comment #14 from Bayram Çiçek ---
(In reply to kolAflash from comment
https://bugs.documentfoundation.org/show_bug.cgi?id=49895#c30) (Moving &
replying the comment here)
> @Bayram Çiçek
>
> It seems your patch slowed down loading the options dialog noticeably.
> https://git.libreoffice.org/core/+/
> a4633dadb4233ad5587bd238449671d610540c81%5E%21
> With LibreOffice-24.2 it's about 10 times slower than with LibreOffice-7.6.
> (before LibreOffice-7.1 the options loaded slow because of bug 146852)
>
> It's not a disaster. But on slower computers you really have to wait
> multiple seconds since LibreOffice-24.2. I guess on older computers this can
> exceed 10 seconds while being 1 second in LibreOffice-7.6.
Yes, unfortunately we have to initialize all dialogs to get their UI string
values to include them in searching. Otherwise, they are not accessible...
> Reproduction:
> Tools -> Options
> Measure the time until the Options window is opened.
> NOTE:
> It's just the first time the Options are being opened after starting
> LibreOffice. For repeating the test you have to restart LibreOffice.
That's true. We save the UI strings -at the time of opening Tools>Options- into
a list and they live until the LibreOffice application closes. In that way, we
don't need to initialize the all dialogs again and again; we just read the
strings from the list, if the Options dialog is opened again (without closing
the LO application)
> I've tested exactly your commit using this Git repo with binaries.
> https://bibisect.libreoffice.org/linux-64-24.2.git
> See also: https://wiki.documentfoundation.org/QA/Bibisect
> The binary commit 418e06688 in that repo corresponds to the a4633dadb commit
> in https://git.libreoffice.org/core/
> 418e06688^ is fast and 418e06688 is slow.
>
> On my Ryzen-5650U @ 2.3 GHz (4.2 GHz boost) notebook CPU it's just half a
> second. But if I slow down the CPU to the minimum of 1.6 GHz and disable the
> boost it's already over a second. While LibreOffice-7.6 stays nicely below
> half a second.
> /sys/devices/system/cpu/cpufreq/boost
> /sys/devices/system/cpu/cpu*/cpufreq/{boost,scaling_max_freq}
>
> I've got a low power Celeron-J4105 CPU system on which it's below 1 second
> with 418e06688^ and over 4 seconds with 418e06688
> If I throttle the CPU to 800 MHz 418e06688^ stays below 1 second while
> 418e06688 needs over 8 seconds.
> And I guess on a Raspberry Pi 4 or 5 used as a desktop computer it's even
> slower.
>
>
> Even on high speed CPUs you can see it clearly if you "cpulimit" to limit
> the computing power available to the process. On my Ryzen-5650U limited to
> 1.6 GHz with boost disabled this is over 8 seconds with 418e06688
> https://packages.debian.org/bookworm/cpulimit
> # first shell (limit process to CPU core 0)
> soffice
> # second shell
> sudo cpulimit -fv -l2 -e soffice.bin
>
> Operating system on all machines: Debian-12
> Same results for Upstream-LibreOffice-7.6, Debian-12-LibreOffice-7.4 and
> LibreOffice 418e06688^
>
>
>
> The problem seems to boil down to this eager preloading.
> initializeFirstNDialog(25);
> https://git.libreoffice.org/core/+/3b50600e8f817409f5a21249871d9f82728e4987/
> cui/source/options/treeopt.cxx#1201
I was expecting that slowness on low-power systems. There are almost 70 dialogs
need to be initialized. If 25 of them are so slow, then I can't imagine the
slowness of initializing the 70 of them during search...
> Although if I reduce the number from 25 to 1, I get a strange effect that
> didn't exist in 418e06688^. Some sections in the options dialog like
> LibreOffice->View get loaded really slow when clicking them. But not all
> sections are affected.
I need to check that strange effect. I remember we had issues like that in some
OSes (especially on Windows)
>
> So I'd consider removing this preloading (equivalent to setting the value to
> 1) less bad than the situation since LibreOffice-24.2. Because then you've
> only have to wait when clicking one of the slow sections or when using the
> search function (initializing the search takes some time with a value of 1).
> Ideally a user would only have to wait when using the new search feature.
> But I haven't figured out yet if or how that's possible.
I asked myself & thought the same while working on Options dialog. However, as
I mentioned earlier, you can't access anything without open/initialize the
dialog(s). This makes the implementation very difficult than it should be.
(regarding the topic, see also:
https://bayramcicek.github.io/libreoffice-dev/2023/06/18/week-03-gsoc-report.html)
> (very ideally a user never has to wait ;-) but I guess the new search
> feature just needs time to
[Bug 160646] GIF don't animate in edit mode; are rendered as still images
https://bugs.documentfoundation.org/show_bug.cgi?id=160646 Telesto changed: What|Removed |Added OS|All |Windows (All) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159375] Opening Tools > Options dialog takes too long
https://bugs.documentfoundation.org/show_bug.cgi?id=159375 --- Comment #13 from Mike Kaganski --- Is it possible to start gathering the strings in a dedicated thread (immediately at dialog start, but without blocking it)? And if a user starts searching, block until that thread finished. I bet, that in 90%+, users won't be that fast to notice the delay. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160874] Calc fails to suggest correction for formula cell without equal sign
https://bugs.documentfoundation.org/show_bug.cgi?id=160874 --- Comment #1 from Dan Dascalescu --- Created attachment 193912 --> https://bugs.documentfoundation.org/attachment.cgi?id=193912=edit Spreadsheet to reproduce the bug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160874] New: Calc fails to suggest correction for formula cell without equal sign
https://bugs.documentfoundation.org/show_bug.cgi?id=160874 Bug ID: 160874 Summary: Calc fails to suggest correction for formula cell without equal sign Product: LibreOffice Version: 24.2.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ddascalescu+freedesk...@gmail.com Created attachment 193911 --> https://bugs.documentfoundation.org/attachment.cgi?id=193911=edit Screencast If you edit a cell and type an incomplete formula, e.g. `=-5 *` then click a cell, Calc will paste the cell's address at the cursor in the formula, e.g. `=-5 * A3`. If you edit a cell that contains a negative number, e.g. `-5` and add `* 2`, Calc will correctly interpret that as a formula, `-5 * 2`. But if you edit a cell consisting of a negative number, type an operator (e.g. `-5 * `), then click another cell, Calc won't paste that cell's address. Please see the attached screencast, recorded with the attached spreadsheet. Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 20; OS: Linux 6.7; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159375] Opening Tools > Options dialog takes too long
https://bugs.documentfoundation.org/show_bug.cgi?id=159375 Bayram Çiçek changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=49 ||895 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 114287] fo:text-indent and fo:margin-left from paragraph style has to overrule those from list style
https://bugs.documentfoundation.org/show_bug.cgi?id=114287 Michael Stahl (allotropia) changed: What|Removed |Added Whiteboard|target:7.6.0 target:24.8.0 |odf target:7.6.0 |target:7.6.8 target:24.2.4 |target:24.8.0 target:7.6.8 ||target:24.2.4 Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #9 from Michael Stahl (allotropia) --- 1. the bug in the description, we already concluded last year that it's a bad idea to fix it because it would break interop with other ODF applications like Word 2. the bug that the commits were about is a different bug best described by https://bugs.documentfoundation.org/show_bug.cgi?id=156146#c3 but now it turned out that fixing that is also a bad idea; it would improve interop with Word, but break other things and it turns out that Word can't even roundtrip this thing itself -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145318] direct formatting indentation does override style indentation in lists
https://bugs.documentfoundation.org/show_bug.cgi?id=145318 Bug 145318 depends on bug 114287, which changed state. Bug 114287 Summary: fo:text-indent and fo:margin-left from paragraph style has to overrule those from list style https://bugs.documentfoundation.org/show_bug.cgi?id=114287 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Bug 78175] Changing paragraph style does not change first line indent
https://bugs.documentfoundation.org/show_bug.cgi?id=78175 Bug 78175 depends on bug 114287, which changed state. Bug 114287 Summary: fo:text-indent and fo:margin-left from paragraph style has to overrule those from list style https://bugs.documentfoundation.org/show_bug.cgi?id=114287 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Bug 94587] [META] Properly support existing ODF features
https://bugs.documentfoundation.org/show_bug.cgi?id=94587 Bug 94587 depends on bug 114287, which changed state. Bug 114287 Summary: fo:text-indent and fo:margin-left from paragraph style has to overrule those from list style https://bugs.documentfoundation.org/show_bug.cgi?id=114287 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Bug 92762] WRITER paragraph with list style is different from paragraph style + separate list style
https://bugs.documentfoundation.org/show_bug.cgi?id=92762 Bug 92762 depends on bug 114287, which changed state. Bug 114287 Summary: fo:text-indent and fo:margin-left from paragraph style has to overrule those from list style https://bugs.documentfoundation.org/show_bug.cgi?id=114287 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Bug 132248] Image or frame wrap settings do not work in footnotes area
https://bugs.documentfoundation.org/show_bug.cgi?id=132248 Michael Stahl (allotropia) changed: What|Removed |Added Whiteboard|target:7.2.0 target:7.1.5 | CC|michael.st...@allotropia.de | --- Comment #14 from Michael Stahl (allotropia) --- oh, i didn't intend to fix the bug reported here, it was just a regression from a different bugfix that happened to crash with the attachment of this bug, and our commit-notifications-bot is a bit overmotivated... -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160870] Continues footnote number is flipped
https://bugs.documentfoundation.org/show_bug.cgi?id=160870 --- Comment #2 from ajlittoz --- Created attachment 193910 --> https://bugs.documentfoundation.org/attachment.cgi?id=193910=edit Bad rendering of field value This bug report is a follow-on to https://ask.libreoffice.org/t/continues-footnote-numbering-problem/105328/ The bug is more generic than what @ardv describes. IMHO it is related to the way field value is inserted in text. Once the value of a field is determined , it is converted into a string of characters. This string "loses" any Unicode property, notably the script associated to characters, and it is inserted as a "neutral" collection of glyphs. The characters are inserted one after the other using the writing directionality of the context. In my attachment, I took the opposite disposition of @ardv: inserting Arabic text inside English. I defined a reference over this Arabic text for later use. I created a lengthy note. Tools>Footnotes & Endnotes is configured to insert continuation notices start as "0123456789 alef beh teh theh to page" and end as "0123456789 alef beh teh theh from page". We see that the Arabic strings are inserted in this order instead of "theh teh beh alef 0123456789 to/from page". The same occurs when a cross-reference tries to duplicate the source. Field "value" seems to be considered as already laid out and is passed without further manipulation to display (I voluntarily don't use word "rendering" as it seems skipped). Here LO 7.6.63 (x86_64) VCL kf5 (cairo+xcb) But occurs also on my other computer with LO 24.2.2.2 and kf6 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107832] [META] Writer list style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107832 Bug 107832 depends on bug 159366, which changed state. Bug 159366 Summary: List styles add paragraph direct formatting on loading Writer document https://bugs.documentfoundation.org/show_bug.cgi?id=159366 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159366] List styles add paragraph direct formatting on loading Writer document
https://bugs.documentfoundation.org/show_bug.cgi?id=159366 Michael Stahl (allotropia) changed: What|Removed |Added Resolution|--- |FIXED CC||rb.hensc...@t-online.de Assignee|libreoffice-b...@lists.free |michael.st...@allotropia.de |desktop.org | Status|NEW |RESOLVED --- Comment #11 from Michael Stahl (allotropia) --- should be fixed now; after a new examination we concluded the change was a bad idea and hence reverted. it turns out that this document structure with the automatic style having the same list style as the parent style also happens by normal editing (found in 290 out of 19360 ODT files), so removing it automatically is probably another bad idea, but i have a python script that can be run manually with the LO bundled python to remove it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 118006] Add support for Quattro Pro .qpw format, looking for sample documents[libwps]
https://bugs.documentfoundation.org/show_bug.cgi?id=118006 --- Comment #14 from Devansh Varshney --- (In reply to Dennis Roczek from comment #13) > Well you are picking the rare corner cases. Understood. I would like to take this but maybe first I will close my some almost complete PRs first https://gerrit.libreoffice.org/q/owner:varshney.devansh...@gmail.com Moreover, I have also requested to work on the support of the Histogram chart (if I get selected) else the Box and Whisker chart in LO. :) But, if time permit how would I first approach this? By introducing the similar structure of the code as it's already there for the .wb* file formats for the qpw files. Then eventually add the support for the formats which are there in the qpw files. I mean creating the new set of source files for the .qpw filter, such as qpw.cxx, qpwform.cxx, and qpwstyle.cxx, in the same directory sc/source/filter/qpro . First might look like - a. Identifying and validating the .qpw file format. b. Reading the file header and extracting relevant information. c. Parsing the file structure and identifying the different components. TL;DR - how do I approach this? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160873] Usability: "OLE Object" probably not familiar language (Menu: Insert/OLE Object)
https://bugs.documentfoundation.org/show_bug.cgi?id=160873 jan d changed: What|Removed |Added Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160873] Usability: "OLE Object" probably not familiar language (Menu: Insert/OLE Object)
https://bugs.documentfoundation.org/show_bug.cgi?id=160873 jan d changed: What|Removed |Added Summary|Usability: Insert/OLE |Usability: "OLE Object" |Object probably not |probably not familiar |familiar language |language (Menu: Insert/OLE ||Object) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160873] New: Usability: Insert/OLE Object probably not familiar language
https://bugs.documentfoundation.org/show_bug.cgi?id=160873 Bug ID: 160873 Summary: Usability: Insert/OLE Object probably not familiar language Product: LibreOffice Version: 7.6.3.1 rc Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: d_...@ymail.com Description: Description: Some objects (Formulas, QR-Codes and general OLE Object) can be inserted via the Insert/OLE-Menu point. Steps to Reproduce: Visit in Menu: Insert/OLE-Object Actual Results: "OLE Object" is a technical term that probably many users are not familiar with Expected Results: Do not expose names of internally used technologies to users if they are not familiar with the terms. Possible Solutions: Dissolve the OLE-Menu point and pull the items in the main insert menu. Reproducible: Always User Profile Reset: No Additional Info: Context: OLE means "Object Linking and Embedding" and is the name of a technology that Microsoft developed to allow the integration of both display- and editing capabilities into different programs. The term is technical jargon, describing an underlying technology rather than what users can do. The Insert/OLE Object/Formula shows the typical behavior for OLE: When editing an OLE object, another program is basically overlayed over the main (embedding) application. I could not find out if QR-Code actually uses OLE, since there is no editing capability exposed and the result seems to be handeled as an image, which is what OLE actually should overcome. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102495] [META] KDE (kf5) VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Bug 102495 depends on bug 160838, which changed state. Bug 160838 Summary: LibreOffice does not report the correct cursor position for IME at certain places unless using gtk3 VCL plugin https://bugs.documentfoundation.org/show_bug.cgi?id=160838 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160872] New: Printed results are incorrect when there is a vertical string of Kanji characters in a table.
https://bugs.documentfoundation.org/show_bug.cgi?id=160872 Bug ID: 160872 Summary: Printed results are incorrect when there is a vertical string of Kanji characters in a table. Product: LibreOffice Version: 7.5.0.0 alpha0+ Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kein...@gmail.com Description: When I print the following docx and dot files, the Kanji characters in the table are misaligned and printed over the other characters. Steps to Reproduce: 1.Create a table that is at least 2x2 2.Create a cell (a) that spans multiple rows in a table 3.Write a vertical string containing Kanji characters in cell (a) 4.In the cell next to (a), write the characters in (a) that contain the Kanji characters. Actual Results: https://ask.libreoffice.org/uploads/asklibo/original/3X/f/4/f4eed95150b1ac086af5bbcb2f786c09fbab44a9.png Expected Results: https://ask.libreoffice.org/uploads/asklibo/original/3X/c/4/c470b5de4ed07be12ab35a8c55d2d7884440506d.png Reproducible: Always User Profile Reset: Yes Additional Info: Ubuntu22.04 LibreOffice(Ver7.3.7.2) print result normal (LibreOffice version installed by default) Ubuntu23.10 LibreOffice(Ver7.6.5.2) Abnormal print result (LibreOffice version installed by default) Ubuntu24.04 LibreOffice(Ver24.2.2.2) Abnormal print result (LibreOffice version installed by default) Ubuntu24.04 LibreOffice(Ver7.3.7.2) print result normal LibreOffice7.3.7.2 is installed by default Ubuntu 22.04 Ubuntu24.04 LibreOffice(Ver7.4.7.2) print result normal 7.4.7.2 was also normal Ubuntu24.04 LibreOffice(Ver7.5.9.2) print result is abnormal Ubuntu24.04 LibreOffice(Ver7.6.6) print result is abnormal -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153032] Writer crashes after few hours of editing large DOCX file with some compatibility options on
https://bugs.documentfoundation.org/show_bug.cgi?id=153032 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #18 from Stéphane Guillou (stragu) --- The crash signature has last been seen in 7.6.2.1. Wondering if this is resolved for you in version 24.2? Seeing you are working with a DOCX, I'm wondering if the many recent improvements in floating table handling have helped. (In reply to Ziggy_N from comment #16) > I will try to isolate the faulty option. Any luck with that? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160730] QR and Barcodes behind other objects instead of on top (Writer, Calc)
https://bugs.documentfoundation.org/show_bug.cgi?id=160730 raal changed: What|Removed |Added Ever confirmed|0 |1 CC||r...@post.cz Status|UNCONFIRMED |NEW --- Comment #1 from raal --- Confirm with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5740d3fa83e9725a2771e5f00ba4aaf9965f0be2 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 107733] [META] Hyperlink bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107733 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160867 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160867 [Bug 160867] Hyperlinks of text / objects inside frames doesn't export to HTML -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160805] Conditional formatting range does not respond to insert/delete rows/columns
https://bugs.documentfoundation.org/show_bug.cgi?id=160805 raal changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #3 from raal --- Thanks, closing -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160805] Conditional formatting range does not respond to insert/delete rows/columns
https://bugs.documentfoundation.org/show_bug.cgi?id=160805 --- Comment #2 from d...@anteunis.com --- I confirm solution by raal Just downloaded 24.2.2.2 and the problem is gone. I tried inserting rows and entering values for many different combinations: insert before/after a matching condition 1, insert before/after a match condition 2, insert before/after a value that does not match any of the conditions and ALL BEHAVE AS EXPECTED. Thank you for the solution. Dirk -- You are receiving this mail because: You are the assignee for the bug.
[Bug 127592] [META] LibreOffice Basic incl."Option Compatible" modules
https://bugs.documentfoundation.org/show_bug.cgi?id=127592 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||151064 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151064 [Bug 151064] CRASH: executing macro with .uno:InsertObjectChart -- You are receiving this mail because: You are the assignee for the bug.
[Bug 90486] [META] Chart bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=90486 Bug 90486 depends on bug 151064, which changed state. Bug 151064 Summary: CRASH: executing macro with .uno:InsertObjectChart https://bugs.documentfoundation.org/show_bug.cgi?id=151064 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 90486] [META] Chart bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=90486 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||151064 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151064 [Bug 151064] CRASH: executing macro with .uno:InsertObjectChart -- You are receiving this mail because: You are the assignee for the bug.
