[Bug 76005] UI missing to set document properties: "TabsRelativeToIndent", "TabOverMargin"
https://bugs.documentfoundation.org/show_bug.cgi?id=76005 --- Comment #15 from Commit Notification --- Mohit Marathe committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/b51271b85387a57b4cdd20ee6277c1a955706fc1 tdf#76005 add TabsRelativeToIndent, TabOverMargin compat option to dialog 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 76005] UI missing to set document properties: "TabsRelativeToIndent", "TabOverMargin"
https://bugs.documentfoundation.org/show_bug.cgi?id=76005 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 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 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=72 ||972 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 72972] EDITING: Option to use short names or numbers for bibliography entries should be made clearer
https://bugs.documentfoundation.org/show_bug.cgi?id=72972 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5633 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101258] [META] Bibliography bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101258 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||155633 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155633 [Bug 155633] Can't use a custom bibliography database source for Insert > TOC & Indexes > Bibliography Entry -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101258] [META] Bibliography bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101258 Bug 101258 depends on bug 155633, which changed state. Bug 155633 Summary: Can't use a custom bibliography database source for Insert > TOC & Indexes > Bibliography Entry https://bugs.documentfoundation.org/show_bug.cgi?id=155633 What|Removed |Added Status|CLOSED |UNCONFIRMED Resolution|INVALID |--- -- 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 URL||https://ask.libreoffice.org ||/t/writer-how-to-use-a-spre ||adsheet-as-bibliographic-da ||tabase/92049 Blocks||101258 Summary|INFORMATION REQUEST:|Can't use a custom |Bibliography in Writer, how |bibliography database |does it work? |source for Insert > TOC & ||Indexes > Bibliography ||Entry Status|CLOSED |UNCONFIRMED Resolution|INVALID |--- --- Comment #3 from Stéphane Guillou (stragu) --- (In reply to ajlittoz from comment #2) > The official documentation has nothing about custom bibliography sources (or > I skipped over it). > > I can turn this report into a bug: menu to choose a bibliography entry is > empty with a custom bibliography database. OK, let's do that. My steps: 1. Create a custom bibliography as an ODB file, e.g. with a table with variables Identifier, Author, Title 2. In Writer, go to Tools > Bibliography > Data Source and pick the database that was just created. Prompt says "The following column names could not be assigned": accept to edit the column arrangement, and match variables to columns. 3. Try to insert a reference with Insert > Table of Contents and Index > Bibliography Entry Result A: the dialog seems to require the availability of a "Short name" field. 4. Modify the bibliography database table to add a Short Name field; populate it 5. Repeat steps 2 (matching the new column to "Short name") and 3 Result B: the Short name dropdown is still empty. ajlittoz, do you agree these are the steps? Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 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 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101258 [Bug 101258] [META] Bibliography bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 109326] [META] Data filter bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109326 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160440 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160440 [Bug 160440] Paste as bitmap (PNG, BMP) of a chart is incorrect when source is filtered -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160440] Paste as bitmap (PNG, BMP) of a chart is incorrect when source is filtered
https://bugs.documentfoundation.org/show_bug.cgi?id=160440 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||109326 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109326 [Bug 109326] [META] Data filter bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160440] Paste as bitmap (PNG, BMP) of a chart is incorrect when source is filtered
https://bugs.documentfoundation.org/show_bug.cgi?id=160440 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEW OS|Linux (All) |All Blocks||108479, 90486 Whiteboard| QA:needsComment| Version|7.6.5.2 release |4.4.0.3 release Keywords||implementationError Summary|Paste as bitmap of a chart |Paste as bitmap (PNG, BMP) |is incorrect when source is |of a chart is incorrect |filtered|when source is filtered Ever confirmed|0 |1 --- Comment #1 from Stéphane Guillou (stragu) --- Thanks for the report. I reproduce in: Version: 7.6.6.3 (X86_64) / LibreOffice Community Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7 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 As well as a recent trunk build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 695e8742da850bbb15c2e6d2b5d4c99a0daf4925 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Already the case in 4.4.0.3, when PNG and BMP paste were made available, so assuming it is an implementation error. Also an issue on Win11. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=90486 [Bug 90486] [META] Chart bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108479 [Bug 108479] [META] Paste special bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108479] [META] Paste special bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108479 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160440 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160440 [Bug 160440] Paste as bitmap (PNG, BMP) of a chart is incorrect when source is filtered -- 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||160440 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160440 [Bug 160440] Paste as bitmap (PNG, BMP) of a chart is incorrect when source is filtered -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157857] Ctrl+W closes all open documents, not just the active window
https://bugs.documentfoundation.org/show_bug.cgi?id=157857 --- Comment #5 from Damon Anderson --- I also can not reproduce this bug. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159679] pdf digital signature, fails to access to the list of my openpgp signature in kleopatra
https://bugs.documentfoundation.org/show_bug.cgi?id=159679 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160614] Master document - Incorrect index page numbers in subdocuments
https://bugs.documentfoundation.org/show_bug.cgi?id=160614 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160619] Create Separate Print Jobs for collated output fails
https://bugs.documentfoundation.org/show_bug.cgi?id=160619 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157445] Portrait / landscape
https://bugs.documentfoundation.org/show_bug.cgi?id=157445 --- Comment #3 from QA Administrators --- Dear robert, 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 153671] Drop "Use printer metrics" feature completely
https://bugs.documentfoundation.org/show_bug.cgi?id=153671 --- Comment #6 from QA Administrators --- Dear Gabor Kelemen (allotropia), Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157941] bookmarks without text in writer
https://bugs.documentfoundation.org/show_bug.cgi?id=157941 --- Comment #2 from QA Administrators --- Dear Gianfranco Maria Gentili, 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 157909] All unfilled date fields in form are implicitly filled 1.1.1900
https://bugs.documentfoundation.org/show_bug.cgi?id=157909 --- Comment #10 from QA Administrators --- Dear Petr Poruban, 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 157725] Signing a PDF has no visible effect, signature is not listed
https://bugs.documentfoundation.org/show_bug.cgi?id=157725 --- Comment #3 from QA Administrators --- Dear Yves57, 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 157701] LibreOffice Calc crashes when trying to apply formatting to entire row
https://bugs.documentfoundation.org/show_bug.cgi?id=157701 --- Comment #8 from QA Administrators --- Dear dennis, 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 95555] FILEOPEN RTF Frames overlap in document created by Oracle Reports
https://bugs.documentfoundation.org/show_bug.cgi?id=9 --- Comment #17 from QA Administrators --- Dear Dženan Zukić, 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 80412] FILESAVE: DOC save breaks correct Normal style font and font size in Word for Mac 2011 & 2016 ver 15
https://bugs.documentfoundation.org/show_bug.cgi?id=80412 --- Comment #13 from QA Administrators --- Dear mitja, 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 61357] DOC import: Equation numbering missing. DATA LOSS when saving.
https://bugs.documentfoundation.org/show_bug.cgi?id=61357 --- Comment #14 from QA Administrators --- Dear A.S., 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 62185] FILEOPEN PPTX Text reflections not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=62185 --- Comment #14 from QA Administrators --- Dear Ofir, 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 72511] Comment note on a DOC from MS Word for Mac 2008 appears wrongly on Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=72511 --- Comment #18 from QA Administrators --- Dear Kumāra, 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 60205] Multi-column 1-page RTF(not doc) with text box (absolute position to margin with "Layout in table cell") opens with wrong frame position
https://bugs.documentfoundation.org/show_bug.cgi?id=60205 --- Comment #19 from QA Administrators --- Dear rj_libreoffice, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 126996] FILESAVE DOCX The wideslash from a formula is not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=126996 --- Comment #7 from QA Administrators --- Dear hmslima1992, 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 119010] Page area hatch doesn't work correctly in a Writer document with mirrored pages.
https://bugs.documentfoundation.org/show_bug.cgi?id=119010 --- Comment #10 from QA Administrators --- Dear Robin Henderson, 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 118962] "Tab position relative to paragraph style indent" issues in ToC where tab stop position less than “before text”
https://bugs.documentfoundation.org/show_bug.cgi?id=118962 --- Comment #8 from QA Administrators --- Dear Timur, 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 111635] OFFLINE HELPS (English US x64) install fine, but LibreOffice x64 says it isn't installed!
https://bugs.documentfoundation.org/show_bug.cgi?id=111635 --- Comment #9 from QA Administrators --- Dear DavidC, 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 104103] FILEOPEN DOC: Textbox isn't separated from drawing canvas
https://bugs.documentfoundation.org/show_bug.cgi?id=104103 --- Comment #9 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159375] Opening Tools > Options dialog takes too long
https://bugs.documentfoundation.org/show_bug.cgi?id=159375 --- Comment #11 from Hossein --- (In reply to Bayram Çiçek from comment #9) > > I think another approach can be creating a search database at compile time. > > In this way, it will be ready at execution time, without any delays. You may > > initialize the dialogs, dump strings and write them to some files, and then > > re-use that at runtime. You may need to do this for each and every language, > > as the translations are important here. > We tried this approach but we saw that this approach makes the > implementation more complex - especially when it comes to different > languages (translations etc...) Could you please describe how did you try this approach? And what were the issues that made it so complex? (In reply to Stéphane Guillou (stragu) from comment #10) > I think you misunderstood me. I mean: compile-time indexing does not include > the extra panels that might be added to the Options dialog when the user > installs an extension after installation, and therefore would not be > included in the search results. Aha, OK! Now I understand what you mean. We can have a compromise for that: index pre-built options at compile time, and then add indexes for the remaining at run-time. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148407] Need ability to cancel an ongoing paste action
https://bugs.documentfoundation.org/show_bug.cgi?id=148407 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||151167 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151167 [Bug 151167] [META] Make long operations cancellable -- You are receiving this mail because: You are the assignee for the bug.
[Bug 137147] Provide a way to cancel formula calculation in Calc (e.g., by hitting ESC key)
https://bugs.documentfoundation.org/show_bug.cgi?id=137147 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||151167 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151167 [Bug 151167] [META] Make long operations cancellable -- You are receiving this mail because: You are the assignee for the bug.
[Bug 150239] Show progress while performing lengthy operations and allow to interrupt
https://bugs.documentfoundation.org/show_bug.cgi?id=150239 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||151167 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151167 [Bug 151167] [META] Make long operations cancellable -- You are receiving this mail because: You are the assignee for the bug.
[Bug 89340] Functionality request : Cancel running a pdf export
https://bugs.documentfoundation.org/show_bug.cgi?id=89340 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||151167 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151167 [Bug 151167] [META] Make long operations cancellable -- You are receiving this mail because: You are the assignee for the bug.
[Bug 136524] [META] Performance/hang/lag/high CPU issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136524 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||151167 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151167 [Bug 151167] [META] Make long operations cancellable -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49701] Provide UI button to abort loading of a file
https://bugs.documentfoundation.org/show_bug.cgi?id=49701 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||151167 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151167 [Bug 151167] [META] Make long operations cancellable -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151167] [META] Make long operations cancellable
https://bugs.documentfoundation.org/show_bug.cgi?id=151167 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Depends on||49701, 89340, 137147, ||148407, 150239 Alias||cancel-long-operations Blocks||136524 Status|UNCONFIRMED |NEW Summary|All potentially very long |[META] Make long operations |operations should be|cancellable |cancellable.| --- Comment #3 from Stéphane Guillou (stragu) --- (In reply to Heiko Tietze from comment #2) > I would keep this ticket as META. Done. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=49701 [Bug 49701] Provide UI button to abort loading of a file https://bugs.documentfoundation.org/show_bug.cgi?id=89340 [Bug 89340] Functionality request : Cancel running a pdf export https://bugs.documentfoundation.org/show_bug.cgi?id=136524 [Bug 136524] [META] Performance/hang/lag/high CPU issues https://bugs.documentfoundation.org/show_bug.cgi?id=137147 [Bug 137147] Provide a way to cancel formula calculation in Calc (e.g., by hitting ESC key) https://bugs.documentfoundation.org/show_bug.cgi?id=148407 [Bug 148407] Need ability to cancel an ongoing paste action https://bugs.documentfoundation.org/show_bug.cgi?id=150239 [Bug 150239] Show progress while performing lengthy operations and allow to interrupt -- You are receiving this mail because: You are the assignee for the bug.
[Bug 136524] [META] Performance/hang/lag/high CPU issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136524 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEEDINFO|NEW CC||stephane.guillou@libreoffic ||e.org --- Comment #3 from Stéphane Guillou (stragu) --- (In reply to Buovjaga from comment #2) Let's merge bug 113510 into this one? Can you Ninja it? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155155] Japanese, vertical RTL text: left-side text not displayed after IME text input on new line
https://bugs.documentfoundation.org/show_bug.cgi?id=155155 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|FIXED |WORKSFORME --- Comment #3 from Stéphane Guillou (stragu) --- Thanks Rob. As we're unsure what fixed it, let's mark as "resolved - works for me". Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103303] [META] Desktop integration bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103303 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||149610 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149610 [Bug 149610] Whether and how to present iconography should adhere to what the host-OS or desktop-environment mandate (e.g. KDE Plasma Application Style settings) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 149610] Whether and how to present iconography should adhere to what the host-OS or desktop-environment mandate (e.g. KDE Plasma Application Style settings)
https://bugs.documentfoundation.org/show_bug.cgi?id=149610
Stéphane Guillou (stragu) changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED |NEEDINFO
Blocks||103303
CC||m.wegh...@posteo.de
Summary|Whether and how to present |Whether and how to present
|iconography should adhere |iconography should adhere
|to what the host-OS or |to what the host-OS or
|desktop-environment |desktop-environment mandate
|mandate.|(e.g. KDE Plasma
||Application Style settings)
--- Comment #5 from Stéphane Guillou (stragu)
---
(In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #3)
> Created attachment 187009 [details]
> Icons KCM configuration.
As you are using the gtk3 VCL plugin for LO (as seen in your version info),
have you tried changing the settings with "Configure GNOME/GTK application
style" on the right-hand side of the dialog?
And the other way around: are the settings as depicted followed if you start LO
with:
SAL_USE_VCLPLUGIN=kf5 libreoffice
@Michael, I thought this might be right up your alley.
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=103303
[Bug 103303] [META] Desktop integration 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 #8 from Jim Raykowski --- (In reply to Stéphane Guillou (stragu) from comment #7) +1 Tracks exactly with what I was thinking all the way down to the "Position History" length compared to the "Wrong table formula" length. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153158] fontconfig alias not respected on SVG import
https://bugs.documentfoundation.org/show_bug.cgi?id=153158 Stéphane Guillou (stragu) changed: What|Removed |Added CC||xiscofa...@libreoffice.org --- Comment #6 from Stéphane Guillou (stragu) --- (In reply to Julien Nabet from comment #4) > I did all this (+fc-cache -fv to force font cache recreation from scratch) > but Inkscape still shows Linux Biolinum whereas I would expect it displays > "Andale Mono". Did I miss something? If the font is unavailable, its name is still shown in the Text and Font tab, but crossed out with a red line. Can you see that? (Using Inkscape 1.3.1) (In reply to Julien Nabet from comment #5) > Also the weird thing is I don't see anymore Linux Biolinum in LO. The test requires not having Linux Biolinum installed, so that would expected. @Xisco, maybe you have an idea? -- 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 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|Rename "Navigation" toolbar |Rename "Navigation" toolbar |to clarify its role, avoid |to clarify its role, avoid |confusion, and relate to|confusion, and relate to |"Recency" |"Navigate by - Recency" -- 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 "Recency"
https://bugs.documentfoundation.org/show_bug.cgi?id=160732 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #7 from Stéphane Guillou (stragu) --- Sounds like "Position History" is the top contender - which makes me think: do we also want to make the Navigate By dropdown's text consistent with it, by replacing "Recency" with "Position History"? "Navigate by - position history" works well. I think it would make sense and clarify the role. "Recency" makes it sound like "how recently the object was created". In that list, it's the only element out of 21 that is about about "things that don't exist anymore". All other elements are about "what currently exists in the document" (or session, for Reminders). We better make that extra clear with an appropriate, consistent label. "Position History" (16 chars) wouldn't be too long for that Navigate By list - "Wrong table formula" is already longer (20 chars). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160431] Inverts webp file image when inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=160431 Stéphane Guillou (stragu) changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160816] New: Can't paste text copied from PDFs
https://bugs.documentfoundation.org/show_bug.cgi?id=160816 Bug ID: 160816 Summary: Can't paste text copied from PDFs Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stokest...@gmail.com Description: Not sure what the critical factor is, but attempting to paste text from some PDFs does nothing in writer... although it can be pasted into other applications. Steps to Reproduce: 1. Start a Writer document. 2. Copy some body text from https://www.coralrestoration.org/_files/ugd/60a969_0d6d400dd3264652bc74b25c1de38e46.pdf 3. Try to paste it into the document. Actual Results: Nothing happens, although Paste is enabled and I can paste the text into other applications (like TextMate). Expected Results: The text is pasted. Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.2.2 (AARCH64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 10; OS: macOS 14.4.1; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Mac OS 14.4.1 (Apple Silicon) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160629] Bullets and Numbering dialog in Writer does not say it's about an implicit list style
https://bugs.documentfoundation.org/show_bug.cgi?id=160629 --- Comment #4 from Olivier Hallot --- Looking from the other side, cleaning implicit list is not possible with Ctrl+M, and is one of the most exhausting task we have in editing the Guides. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160815] Anchor option "At Page" missing from context menu and menu bar
https://bugs.documentfoundation.org/show_bug.cgi?id=160815 --- Comment #2 from Kira Tubo --- @V Stuart Foote, I understand that this bug is a WNF, but if that's the case, perhaps we should update the online help documentation? Just to clarify to end users that "At Page" is only available in the "Position and Size" dialog. Here's some help documentation that I think need to be updated. There may be more... https://help.libreoffice.org/24.8/en-US/text/shared/01/05260100.html?DbPAR=SHARED#bm_id271692908662893 https://help.libreoffice.org/24.8/en-US/text/swriter/guide/anchor_object.html?DbPAR=WRITER#bm_id3147828 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160814] DOCX comments (replies) are in the wrong order
https://bugs.documentfoundation.org/show_bug.cgi?id=160814 --- Comment #2 from Justin L --- If I disable NS_ooxml::LN_EG_RangeMarkupElements_commentRangeEnd (so there is no range, just a single entry point) then the comments are back in the right order. So the problem is related to the fact that w:commentRangeEnd w:id="2/3/4"/> comes before is inserted. Thus the remaining comments (2 and 4) try to import into SwPaM start[SwPosition (node 9, offset 10)] mark[SwPosition (node 9, offset 10)] -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159829] Update en_ZA locale (ThousandSeparator and DecimalSeparator)
https://bugs.documentfoundation.org/show_bug.cgi?id=159829 ady changed: What|Removed |Added Whiteboard|target:24.8.0 |target:24.8.0 ||inReleaseNotes:24.8 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140702] Removal of "To page" anchor context menu entries for frames, images, OLE objects (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=140702 V Stuart Foote changed: What|Removed |Added CC||kira.t...@gmail.com --- Comment #37 from V Stuart Foote --- *** Bug 160815 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160815] Anchor option "At Page" missing from context menu and menu bar
https://bugs.documentfoundation.org/show_bug.cgi?id=160815 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- *** This bug has been marked as a duplicate of bug 140702 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160804] If the separator is different from the standard locale, stretching the determinant with the fill handle will change the separator and result in a different formula
https://bugs.documentfoundation.org/show_bug.cgi?id=160804
--- Comment #3 from ady ---
(In reply to ady from comment #2)
> _My_ settings are probably not typical:
>
> * Array Row separator: semicolon (";")
> * Array Column separator: vertical bar ("|" hex 7c, dec 124)
>
>
> 1. A1: ={1;2;3} [ENTER]
Of course that for older versions, the introduction of the array (formula)
needs to be performed by [CTRL]+[SHIFT]+[ENTER] (instead of the sole [ENTER]).
In newer versions, Calc automatically recognizes this as an array even when
only using [ENTER].
When using CSE, I can reproduce the same behavior I described in comment 2 with
LO 3.3 too.
Before setting this report to "inherited", I would rather have confirmation
that what I described in comment 2 is indeed the same problem that is
(apparently) reported in comment 0 (because I am not sure, considering the
differences in my results).
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 160813] LibreOffice Writer - Tabbed UI not scaled
https://bugs.documentfoundation.org/show_bug.cgi?id=160813 --- Comment #3 from V Stuart Foote --- Created attachment 193845 --> https://bugs.documentfoundation.org/attachment.cgi?id=193845=edit Tabbed UI at LO 24.2.2 on Windows, os/DE 200% UI scaling w 150% bigger text Here Notebook Bar "Tabbed UI" MUFFIN mode with mix of Windows os/DE 200% UI scale and 150% "bigger text". Icon theme set to Colibre (SVG + dark). Note the "Styles Preview" panel is the only really degraded area. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160804] If the separator is different from the standard locale, stretching the determinant with the fill handle will change the separator and result in a different formula
https://bugs.documentfoundation.org/show_bug.cgi?id=160804
--- Comment #2 from ady ---
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ea43cbbb7371a743f470d949762a0e92f196e652
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (es_AR); UI: en-US
Calc: CL threaded
_My_ settings are probably not typical:
* Array Row separator: semicolon (";")
* Array Column separator: vertical bar ("|" hex 7c, dec 124)
1. A1: ={1;2;3} [ENTER]
1.1. Array result:
A1: 1
A2: 2
A3: 3
2. Select A1:A3 (the whole array).
3. Expand the array to add one row, A1:A4.
3.1. Array result:
A1: 1
A2: 1
A3: 1
A4: 1
4. Expand the array to add one row, A1:A5.
4.1. Array result:
A1: 1
A2: 2
A3: 3
A4: #N/A
A5: #N/A
5. Expand the array to add _two_ rows, A1:A7.
5.1. Array result:
A1: 1
A2: 1
A3: 1
A4: 1
A5: 1
A6: 1
A7: 1
6. Expand the array to add one row, A1:A8
4.1. Array result:
A1: 1
A2: 2
A3: 3
A4: #N/A
A5: #N/A
A6: #N/A
A7: #N/A
A8: #N/A
I can even reduce the size of the array; the amount of rows (plus or minus) are
not a factor.
The factor is: one time I get "ones", the next time I get the original array
plus #N/A (as much as needed to fulfill the new size of the array), and then
the cycle repeats.
I can also replicate this cycle when expanding the array from rows to multiple
columns. The difference is that the "ones" are expanded to "twos", and so on
(according to number of columns) and then #N/A's and then the cycle repeats.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 160813] LibreOffice Writer - Tabbed UI not scaled
https://bugs.documentfoundation.org/show_bug.cgi?id=160813 V Stuart Foote changed: What|Removed |Added Blocks||107237 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107237 [Bug 107237] [META] Notebookbar Tabbed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 V Stuart Foote changed: What|Removed |Added Depends on||160813 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160813 [Bug 160813] LibreOffice Writer - Tabbed UI not scaled -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146297] NB TABBED: Styles Preview Widget does not implement scaling (visible in qt / kf5)
https://bugs.documentfoundation.org/show_bug.cgi?id=146297 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0813 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160813] LibreOffice Writer - Tabbed UI not scaled
https://bugs.documentfoundation.org/show_bug.cgi?id=160813 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org Status|NEW |RESOLVED Resolution|--- |NOTABUG See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6297 --- Comment #2 from V Stuart Foote --- (In reply to quachvan from comment #0) > Expected Results: > Should be scaled like in MS-Office And? The "Tabbed UI" flavor of the Notebook Bar does not use native MS Ribbon API libs. Instead it is a mix of GTK .UI, and UNO button actions. Supplementing the legacy Menu/Toolbar/Dialog and Sidebar decks. In fact it scales well cross platform, with exception of the "Styles Preview" panel (bug 146297). If you need the NB UI to scale for 4K or HiDPI screens, scale your os/DE. So, on Windows on a 4K display use the system Settings -> Display -> 'Make text bigger' slider and apply-- 170% should make the NB comfortable to use on HiDPI. Distinct from your other os/DE scale factor. Again, the NB "Tabbed UI" is not native Windows Ribbon API--many features of the Windows Ribbon are simply not achievable. IMHO => NAB with only substantive issue the "Styles Preview" of the noted bug. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159829] Update en_ZA locale (ThousandSeparator and DecimalSeparator)
https://bugs.documentfoundation.org/show_bug.cgi?id=159829 Eike Rathke changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Eike Rathke --- Added to release notes https://wiki.documentfoundation.org/ReleaseNotes/24.8#Changes_to_locale_data -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing
https://bugs.documentfoundation.org/show_bug.cgi?id=160783
Julien Nabet changed:
What|Removed |Added
CC||mikekagan...@hotmail.com,
||noelgran...@gmail.com
--- Comment #4 from Julien Nabet ---
I kept digging and noticed this commit (2020-02-12)
2b702f7436acf6883b41508277441e5ea0a53d51
which includes this change:
static bool isVulkanBlacklisted(const VkPhysicalDeviceProperties& props)
{
static const char* const types[]
= { "other", "integrated", "discrete", "virtual", "cpu", "??" }; //
VkPhysicalDeviceType
+OUString driverVersion = OUString::number(props.driverVersion >> 22) + "."
+ + OUString::number((props.driverVersion >> 12) &
0x3ff) + "."
+ + OUString::number(props.driverVersion & 0xfff);
+OUString vendorId = "0x" + OUString::number(props.vendorID, 16);
+OUString deviceId = "0x" + OUString::number(props.deviceID, 16);
SAL_INFO("vcl.skia",
"Vulkan API version: "
<< (props.apiVersion >> 22) << "." << ((props.apiVersion >>
12) & 0x3ff) << "."
- << (props.apiVersion & 0xfff) << ", driver version: "
- << (props.driverVersion >> 22) << "." <<
((props.driverVersion >> 12) & 0x3ff)
- << "." << (props.driverVersion & 0xfff) << std::hex << ",
vendor: 0x"
- << props.vendorID << ", device: 0x" << props.deviceID <<
std::dec
- << ", type: " << types[std::min(props.deviceType,
SAL_N_ELEMENTS(types))]
+ << (props.apiVersion & 0xfff) << ", driver version: " <<
driverVersion
+ << ", vendor: " << vendorId << ", device: " << deviceId << ",
type: "
+ << types[std::min(props.deviceType,
SAL_N_ELEMENTS(types) - 1)]
<< ", name: " << props.deviceName);
-return false;
+return DriverBlocklist::IsDeviceBlocked(getBlacklistFile(), driverVersion,
vendorId, deviceId);
}
so before this commit, we used apiVersion, afterwards, we started to use
driverVersion.
For api version, Skia uses this macro:
#define VK_MAKE_VERSION(major, minor, patch) \
(((major) << 22) | ((minor) << 12) | (patch))
in addition with these:
#define VK_VERSION_MAJOR(version) ((uint32_t)(version) >> 22)
#define VK_VERSION_MINOR(version) (((uint32_t)(version) >> 12) & 0x3ff)
#define VK_VERSION_PATCH(version) ((uint32_t)(version) & 0xfff)
it corresponds well with the LO part:
146 static OUString versionAsString(uint32_t version)
147 {
148 return OUString::number(version >> 22) + "." +
OUString::number((version >> 12) & 0x3ff) + "."
149+ OUString::number(version & 0xfff);
150 }
but driverVersion uses this one:
#define GR_GL_DRIVER_VER(major, minor, point) ((static_cast(major) <<
32) | \
(static_cast(minor) <<
16) | \
static_cast(point))
So I suppose LO should be adapted.
But a last thing, in Skia we got:
typedef struct VkPhysicalDeviceProperties {
uint32_tapiVersion;
uint32_tdriverVersion;
uint32_tvendorID;
uint32_tdeviceID;
VkPhysicalDeviceTypedeviceType;
char
deviceName[VK_MAX_PHYSICAL_DEVICE_NAME_SIZE];
uint8_t pipelineCacheUUID[VK_UUID_SIZE];
VkPhysicalDeviceLimits limits;
VkPhysicalDeviceSparsePropertiessparseProperties;
} VkPhysicalDeviceProperties;
apiVersion is uint32_t ok, but driverVersion is uint64_t when reading the
macro.
So even if we change LO part, it seems there's a bug in Skia, doesn't it?
Noel/Mike: perhaps one of you might be interested in this one?
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 159829] Update en_ZA locale (ThousandSeparator and DecimalSeparator)
https://bugs.documentfoundation.org/show_bug.cgi?id=159829 --- Comment #5 from Commit Notification --- Eike Rathke committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/92ea59703da91771ca78ade82ca796077c066da8 Resolves: tdf#159829 DecimalSeparator '.' period, ThousandSeparator ',' comma 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 159829] Update en_ZA locale (ThousandSeparator and DecimalSeparator)
https://bugs.documentfoundation.org/show_bug.cgi?id=159829 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 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing
https://bugs.documentfoundation.org/show_bug.cgi?id=160783 --- Comment #3 from V Stuart Foote --- GLview and vulkaninfo utils both return the uint32_t of "2315452416" as driverVersion for this nVidia GPU. And both convert its ID string to "552.12.0.0" vulkaninfo.exe run GPU0: VkPhysicalDeviceProperties: --- apiVersion= 1.3.277 (4206869) driverVersion = 552.12.0.0 (2315452416) vendorID = 0x10de deviceID = 0x1380 deviceType= PHYSICAL_DEVICE_TYPE_DISCRETE_GPU deviceName= NVIDIA GeForce GTX 750 Ti pipelineCacheUUID = e1b3e8ed-3cf0-cbc3-9cd7-33f3274361af But we end up with "552.48.0", and following along in SkiaHelper.cxx at 166 we convert to use the 3 part versionAsString() against the uint32_t of the driverVersion. Hunted around at Khronos, and reddit [1] and it looks like the driver version is supposed to be vendor controlled--and nVidia makes the uint32_t driver version a 4-part string. While Khronos and generic get a 3-part driver string. I couldn't figure out the masking by hand, but does 3-part "552.48.0" match the 4-part "552.12.0.0" conversion of the driverVersion "2315452416"? If so, guess it would not be an issue that they don't match. Or might be better for to just use the uint32_t "driverVersion" as returned, and not convert it? =-ref-= [1] https://www.reddit.com/r/vulkan/comments/fmift4/how_to_decode_driverversion_field_of/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160815] New: Anchor option "At Page" missing from context menu and menu bar
https://bugs.documentfoundation.org/show_bug.cgi?id=160815 Bug ID: 160815 Summary: Anchor option "At Page" missing from context menu and menu bar Product: LibreOffice Version: 7.3.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kira.t...@gmail.com Description: If you insert a shape, and view the Anchor options, the "At Page" option is missing from context menu and menu bar Steps to Reproduce: 1. Open Writer 2. Insert any shape 3. Right click on the shape to open the context menu 4. Go to Anchor and note options 5. Go to Format > Anchor and note options 6. Right click on the shape to open the context menu 7. Click on "Position and Size" or "Properties" 8. Note Anchor options Actual Results: "At Page" anchor option missing from context menu (step 4) and menu bar (step 5) Expected Results: "At Page" is an anchor option that is available from the context menu and menu bar Reproducible: Always User Profile Reset: Yes Additional Info: Reproduced in: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0957ee9f5d379c80fca4027c187b471118d0490d CPU threads: 6; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 7.3.3.2 (x64) / LibreOffice Community Build ID: d1d0ea68f081ee2800a922cac8f79445e4603348 CPU threads: 6; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL NOT reproduced in: Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 6; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Most likely a regression. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160431] Inverts webp file image when inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=160431 --- Comment #14 from KJP --- That works for me! Well done. Thanks for fixing it so quickly! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160810] Writer: comment thread broken
https://bugs.documentfoundation.org/show_bug.cgi?id=160810 raal changed: What|Removed |Added CC||gokaysa...@gmail.com, ||r...@post.cz Keywords||bibisected, bisected Regression By||Gökay Şatır --- Comment #2 from raal --- This seems to have begun at the below commit in bibisect repository/OS linux-64-24.2. Adding Cc: to Gökay Şatır ; Could you possibly take a look at this one? Thanks b970a50fba146993a9ca672d81a7297c2e433f0c is the first bad commit commit b970a50fba146993a9ca672d81a7297c2e433f0c Author: Jenkins Build User Date: Thu Oct 5 16:49:03 2023 +0200 source sha:c0187d9f5e6ab5129b6fc4682555f2f8775d6f67 157019: SW comments: Provide parent / child relations without position. | https://gerrit.libreoffice.org/c/core/+/157019 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160814] DOCX comments (replies) are in the wrong order
https://bugs.documentfoundation.org/show_bug.cgi?id=160814 Justin L changed: What|Removed |Added Version|4.3.0.4 release |4.3 all versions --- Comment #1 from Justin L --- The order they appear in word/comments.xml is the order in which they should appear in the document as well (at least for this example). Based on reading the 4.3 patch's writerfilter code, I don't see anything that would change the order. Indeed, it still calls PopAnnotation in this order: 0 // First coment (note that the 1 is from list numbering - which is lost in LO) 1 // 1.1 second reply. 3 // 1.2 third reply. Only reply on whole thread… 5 // 1.3 2 // 2. second comment 4 // 2.1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160215] Saving to smb share with activated backup not possible
https://bugs.documentfoundation.org/show_bug.cgi?id=160215 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3202 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160315] Saving files to SMB3 network shares no longer works
https://bugs.documentfoundation.org/show_bug.cgi?id=160315 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3202 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153202] FILESAVE: saving .odt to a smb network drive is slow (with excess download traffic)
https://bugs.documentfoundation.org/show_bug.cgi?id=153202 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0215, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0315 Blocks||104742 Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de --- Comment #10 from Dieter --- Devseppala, it seems, that nobody could confirm this bug since more than one year. So I‘d like to ask, if it is still reproducible for you. Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/current.html? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Please have also a look at bug 160215 and 160315. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104742 [Bug 104742] [META] Network-involved bugs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 104742] [META] Network-involved bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=104742 Dieter changed: What|Removed |Added Depends on||153202 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153202 [Bug 153202] FILESAVE: saving .odt to a smb network drive is slow (with excess download traffic) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 152848] When using accents in a table (spanish), a cell break occurs.
https://bugs.documentfoundation.org/show_bug.cgi?id=152848 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #9 from Dieter --- Zchronos, it seems, that nobody could confirm this bug since more than one year. So I‘d like to ask, if it is still reproducible for you. Could you please try to reproduce it with LO 24.2 or with a master build from http://dev-builds.libreoffice.org/daily/master/current.html? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151029] In serial print wizard ... running the functions modifies single documents or saves composed documents, I do not get the documents with the intended recipients.
https://bugs.documentfoundation.org/show_bug.cgi?id=151029 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de --- Comment #6 from Dieter --- Claudio, it seems, that nobody could confirm this bug since more than one year. So I‘d like to ask, if it is still reproducible for you. Could you please try to reproduce it LO 24.2 or with a master build from http://dev-builds.libreoffice.org/daily/master/current.html? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160629] Bullets and Numbering dialog in Writer does not say it's about an implicit list style
https://bugs.documentfoundation.org/show_bug.cgi?id=160629 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #3 from Cor Nouws --- lovely topic, Gábor. Snake pit as well ;) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160350] Replies to comment are in reverse order
https://bugs.documentfoundation.org/show_bug.cgi?id=160350 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0814 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160814] New: DOCX comments (replies) are in the wrong order
https://bugs.documentfoundation.org/show_bug.cgi?id=160814 Bug ID: 160814 Summary: DOCX comments (replies) are in the wrong order Product: LibreOffice Version: 4.3.0.4 release Hardware: All OS: All Status: UNCONFIRMED Keywords: bibisected, bisected, regression Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jl...@mail.com CC: jl...@mail.com Blocks: 112916 Comments in a DOCX file might not import in the correct order. Steps to reproduce. 1.) Open commentsInWord.docx (attachment 193829 from bug 160350) The order of the comments should look like attachment 193828. The comments were correctly ordered until LO 4.3's commit 0761f81643a6890457e9ef7d913ab5c88c2593a4 Author: Oliver-Rainer on Wed Jan 8 15:58:35 2014 +0100 123792: complete annotations on text ranges feature Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112916 [Bug 112916] [META] DOCX (OOXML) comment issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 112916] [META] DOCX (OOXML) comment issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112916 Justin L changed: What|Removed |Added Depends on||160814 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160814 [Bug 160814] DOCX comments (replies) are in the wrong order -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160644] Upon opening, LibreOffice sometimes crashes (perhaps once a week)
https://bugs.documentfoundation.org/show_bug.cgi?id=160644 --- Comment #17 from Patrick Luby (volunteer) --- (In reply to Sam from comment #15) > (In reply to Patrick Luby (volunteer) from comment #14) > > Thank you! Update: I'm monitoring LO memory usage in the Activity Monitor. > It's currently on more than 5 GB although no files are open in LO (I've > opened several and printed them to PDF, and worked on others without ever > quitting LO). > > No more system crash yet but I'll report ASA there is one. Wow! 5 GB with no documents open is a huge amount of memory. I have to think that LibreOffice has a memory leak somewhere. Now the trick is to narrow down what activity in LibreOffice triggers the memory leak. You may want to quit and restart LibreOffice when memory gets that high. That should hopefully prevent a system crash while we try to find where the memory leak is. If you can continue watching Activity Monitor while you are using LibreOffice and if you see memory usage jump a large amount (i.e. 1 GB or more increase), can you try to post what you were doing in LibreOffice immediately before you noticed the large memory usage increase? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159893] Upgrade to Kernel 6.5.0 (from 5.15) produces unreliable Mouse Behavior in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=159893 Buovjaga changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160242] Enhancement: Make possible 2 or more impress in fullscreen each on a dedicated monitor AND each seekable indipendently with user-defined hotkeys per each file.
https://bugs.documentfoundation.org/show_bug.cgi?id=160242 Cor Nouws changed: What|Removed |Added CC||c...@nouenoff.nl --- Comment #4 from Cor Nouws --- Looks a very reasonable request to put in work with a second laptop ;) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159893] Upgrade to Kernel 6.5.0 (from 5.15) produces unreliable Mouse Behavior in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=159893 CP changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |FIXED --- Comment #3 from CP --- Tested as requested and can confirm that the issue is not present with AppImage 24.2. On this basis I would be happy to close this ticket - with my thanks for your suggestion. I will return to the Mint Forum and post an update and see if I can nudge Clem and the Team to move to later App versions. (One of the oddities of Mint is that they refresh some desktop apps - like Firefox, but not others - like LibreOffice). Really appreciate your response. Thank you. ***Issue fixed with later release. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157240] PRINTING text lines disappear (in fact become white) when printing in grayscale
https://bugs.documentfoundation.org/show_bug.cgi?id=157240 Mike Kaganski changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159683] Crash on closing LibreOffice with certain content on the clipboard
https://bugs.documentfoundation.org/show_bug.cgi?id=159683 Miklos Vajna changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |vmik...@collabora.com |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160579] Printing doesn't work with overlapped objects
https://bugs.documentfoundation.org/show_bug.cgi?id=160579 Buovjaga changed: What|Removed |Added Ever confirmed|0 |1 CC||ilmari.lauhakangas@libreoff ||ice.org Status|UNCONFIRMED |NEEDINFO --- Comment #4 from Buovjaga --- I don't have access to a physical printer at the moment, but Microsoft Print to PDF works fine with the steps. How does the problem manifest itself? Can you reproduce by printing to PDF? I assume that step 2 involves right-click - Arrange - Send to back. Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 2; OS: Windows 10.0 Build 22621; 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 136339] Standard (aka "Reset to Parent") button in paragraph styles doesn't function for the highlighting tab (does not switch between "None" and "Color")
https://bugs.documentfoundation.org/show_bug.cgi?id=136339 --- Comment #9 from Glen Campbell --- (In reply to Stéphane Guillou (stragu) from comment #8) > - "Reset" resets the setting to whatever it was when the dialog/tab was > opened. I think I agree with the resolution in bug 135834: it should only > apply to the current tab. No need for a two-step process (which is Heiko's > point, I believe). > - On the other hand, "Reset to Parent" has the clear role of "use whatever > setting is used by the parent style". E.g., if the child uses Highlighting > > Color, and the parent has Highlighting > None, "Reset to Parent" should > switch to None. OK - will look into it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160686] "Left Page" and "Right Page" are nonsensical and should be removed
https://bugs.documentfoundation.org/show_bug.cgi?id=160686 --- Comment #38 from David --- (In reply to Eyal Rozenberg from comment #37) > (In reply to David from comment #36) > > And how do you propose to remove headers, for instance, on just the first > > page? > > On the menus, go to: Format > Page Style... > Header > > and deselect "Same header of first page". You can also get different headers > or alterating pages of the same sequence. Let me rephrase this question. You proposed a "single page style with the "Mirrored" layout option." Let us suppose now that a user has a document that maybe for the first page of each chapter or a section such as an appendix they wish not to have an element, such as the header, on that initial page. It is unknown how many pages might be in the rest of the chapter or appendix. But let's assume there will probably be many pages. The attachment I already gave can be used for a simple example (https://bugs.documentfoundation.org/attachment.cgi?id=193769). Without using any direct formatting inserts (since the user shouldn't be expected to have to do/undo direct inserts if the preceding page count changes), how can a document be configured using only styles so that only the initial page (i.e., not alternating pages) of a chapter or section does not have a header? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108170] Hyperlinks don't highlight 'Internet Link' entry in character styles list
https://bugs.documentfoundation.org/show_bug.cgi?id=108170 V Stuart Foote changed: What|Removed |Added CC||rayk...@gmail.com, ||vsfo...@libreoffice.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||2253 --- Comment #10 from V Stuart Foote --- Still reproduced. But with Spotlight of Applied character styles enabled--shift Stylist deck from CS to PS and back--and the CS for the Hyperlinks is picked up. But seems an issue with the Spotlight applying to canvas for the Hyperlinks. They are styled as visited on document canvas, but the applied spotlight notes them just as hyperlinks. And a bit less clear with changes for bug 132253 to remove the Hyperlink formatting from the Character dialog. Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 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 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160673] Color popovers in Area dialog are cutoff, overflow out of display (GTK, Wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=160673 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #3 from Buovjaga --- (In reply to Caolán McNamara from comment #2) > There is no great solution in the sense that under wayland you don't really > know the position of the toplevel application window on screen. Seems like this protocol would solve it: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/156 >From a comment: "this is just telling the compositor where a representation of a toplevel is located (e.g. button in a panel)". -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160649] Calc scrolling in the calc main window is disabled while the "Manage Conditional Formatting" dialog is opened
https://bugs.documentfoundation.org/show_bug.cgi?id=160649 Buovjaga changed: What|Removed |Added Status|UNCONFIRMED |NEW Priority|medium |low Ever confirmed|0 |1 --- Comment #2 from Buovjaga --- It's a so-called modal window, which prevents interaction elsewhere when open. The same behaviour is often seen on websites as well. I suppose it doesn't make sense to keep as modal. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160606] Writer EDITING: Copied text using Ctrl + click-drag needs two click to deselect.
https://bugs.documentfoundation.org/show_bug.cgi?id=160606 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Resolution|FIXED |WORKSFORME -- 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 "Recency"
https://bugs.documentfoundation.org/show_bug.cgi?id=160732 --- Comment #6 from Jim Raykowski --- +1 for "Position History" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106228] [META] Icon theme issues
https://bugs.documentfoundation.org/show_bug.cgi?id=106228 V Stuart Foote changed: What|Removed |Added Depends on||158932 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158932 [Bug 158932] Icons for promote / demote outline level should be improved -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158932] Icons for promote / demote outline level should be improved
https://bugs.documentfoundation.org/show_bug.cgi?id=158932 V Stuart Foote changed: What|Removed |Added CC||kain...@gmail.com, ||riz...@libreoffice.org, ||vsfo...@libreoffice.org Blocks||106228, 103030 OS|All |Windows (All) --- Comment #4 from V Stuart Foote --- An iconography issue, best left to the icon theme designers. Currently only Rizal's "Karasa Jaga" icon theme uses a stylized outline for both demote/promote outline and move up/down of headings. Our other icon themes use single triangle/arrow pointers, with just the "Colibre" icon theme using a double pointer motif by default on Windows. Personally I have no issue with the "Colibre" theme on Windows, and not clear it is necessary to shift all artwork for the button icons to something other than direction pointers. -1 from me. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103030 [Bug 103030] [META] Navigator sidebar deck and floating window (also "Target in Document") https://bugs.documentfoundation.org/show_bug.cgi?id=106228 [Bug 106228] [META] Icon theme issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103030] [META] Navigator sidebar deck and floating window (also "Target in Document")
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 V Stuart Foote changed: What|Removed |Added Depends on||158932 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158932 [Bug 158932] Icons for promote / demote outline level should be improved -- You are receiving this mail because: You are the assignee for the bug.
