[Libreoffice-bugs] [Bug 145625] In Options – LibreOffice – Application Colors, the part User interface elements has two Key-id codes.
https://bugs.documentfoundation.org/show_bug.cgi?id=145625 --- Comment #1 from kees...@gmail.com --- Created attachment 176185 --> https://bugs.documentfoundation.org/attachment.cgi?id=176185=edit screen shot of the bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145625] New: In Options – LibreOffice – Application Colors, the part User interface elements has two Key-id codes.
https://bugs.documentfoundation.org/show_bug.cgi?id=145625 Bug ID: 145625 Summary: In Options – LibreOffice – Application Colors, the part User interface elements has two Key-id codes. Product: LibreOffice Version: 6.3 all versions Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kees...@gmail.com Description: In Options – LibreOffice – Application Colors, the part User interface elements has two Key-id codes. Because of that the word ”On” appears before the name. See attachment for more details. Steps to Reproduce: 1.Go to Tools - LibreOffice - Application Colors 2. 3. Actual Results: The part is called "On User interface elements" Expected Results: It should be called "User interface elements" without "On" Reproducible: Always User Profile Reset: Yes Additional Info: The Key-id code s9Q, that generates the "On", should not be there. Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: Skia/Vulkan; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81507] FILESAVE: DOCX - w:sdtContent not exported correctly resulting in missing line breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=81507 Vasily Melenchuk (CIB) changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |vasily.melenc...@cib.de |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145610] The numbering of numbered list doesn't show when changing bulleted for numbered list
https://bugs.documentfoundation.org/show_bug.cgi?id=145610 Vasily Melenchuk (CIB) changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |vasily.melenc...@cib.de |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145282] Group of objects doesn't retain its position when page is moved up
https://bugs.documentfoundation.org/show_bug.cgi?id=145282 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEW Keywords||bibisectRequest, regression CC||dgp-m...@gmx.de Whiteboard| QA:needsComment| Blocks||108640 Ever confirmed|0 |1 --- Comment #3 from Dieter --- I confirm it with Version: 7.3.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 742b8befecbcfc0cfab87cfcd87c83b7d8ef32ab CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL but not with Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108640 [Bug 108640] [META] Object meta bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108640] [META] Object meta bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108640 Dieter changed: What|Removed |Added Depends on||145282 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145282 [Bug 145282] Group of objects doesn't retain its position when page is moved up -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120326] User events originating from Impress Remote must reset screensaver timer
https://bugs.documentfoundation.org/show_bug.cgi?id=120326 Mike Kaganski changed: What|Removed |Added Keywords||difficultyMedium, easyHack, ||skillCpp --- Comment #5 from Mike Kaganski --- Code pointers: The place where we should insert calls to inform OS about user input is Receiver::executeCommand in sd/source/ui/remotecontrol/Receiver.cxx Additionally/alternatively, we might consider setting an OS flag on remote connection/initiated slideshow start, and clear it on disconnection/slideshow end. This needs to be done at Communicator ctor and dtor in sd/source/ui/remotecontrol/Communicator.cxx The code to inform OS is necessarily OS/WM-specific. For Windows, informing OS about user input (in Receiver) should be done using SendInput [1], as discussed at [2]. Using PowerSetRequest [3] and/or SetThreadExecutionState [4] may be used in the Communicator, as these calls do not represent some events, but rather some state. [1] https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-sendinput [2] http://stackoverflow.com/a/1675793/1889329 [3] https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-powersetrequest [4] https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-setthreadexecutionstate -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145508] kf5: Assert hit when starting Impress presentation after e4abf879f4a24258bcc560eb58ca78b147768d46
https://bugs.documentfoundation.org/show_bug.cgi?id=145508 Michael Weghorn changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #6 from Michael Weghorn --- Thanks! Fix verified with Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: 373b27e7038cf4010a04163861ebec48984b4353 CPU threads: 12; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded and the same version on X11 as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128412] Cannot start word after line break with small letter
https://bugs.documentfoundation.org/show_bug.cgi?id=128412 --- Comment #4 from david.cortes.riv...@gmail.com --- Version: 7.2.2.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 16; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Debian package version: 1:7.2.2-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145108] Read-only documents can still be changed by drag-and-droping text
https://bugs.documentfoundation.org/show_bug.cgi?id=145108 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145350] LibreOffice Writer Guide 7.1 (PDF) Error Regarding Superscript and Subscript Character Styles
https://bugs.documentfoundation.org/show_bug.cgi?id=145350 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145349] SLIDESHOW animation in wrong order
https://bugs.documentfoundation.org/show_bug.cgi?id=145349 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145348] Formating, character, highlighting
https://bugs.documentfoundation.org/show_bug.cgi?id=145348 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145342] Filesave as doc saves lists with russian character numbering as simple digit numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=145342 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145332] Consider updating Calc help for ROUNDDOWN and TRUNC functions
https://bugs.documentfoundation.org/show_bug.cgi?id=145332 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141646] Crash in: GtkInstanceEntry::signal_activate
https://bugs.documentfoundation.org/show_bug.cgi?id=141646 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141646] Crash in: GtkInstanceEntry::signal_activate
https://bugs.documentfoundation.org/show_bug.cgi?id=141646 --- Comment #3 from QA Administrators --- Dear Tomas, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141332] The program becomes very slow when I insert an image
https://bugs.documentfoundation.org/show_bug.cgi?id=141332 --- Comment #4 from QA Administrators --- Dear Sergio Hernández Pitarch, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141332] The program becomes very slow when I insert an image
https://bugs.documentfoundation.org/show_bug.cgi?id=141332 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90486] [META] Chart bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=90486 Bug 90486 depends on bug 137396, which changed state. Bug 137396 Summary: Using svg symbols in charts crashes Calc https://bugs.documentfoundation.org/show_bug.cgi?id=137396 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137396] Using svg symbols in charts crashes Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=137396 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137396] Using svg symbols in charts crashes Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=137396 --- Comment #8 from QA Administrators --- Dear Adam Johnston, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142270] Calc and Writer crashes. tried reinstalling and it is worse even in safe mode.
https://bugs.documentfoundation.org/show_bug.cgi?id=142270 --- Comment #2 from QA Administrators --- Dear btsneddon, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142142] Liberation Serif does not display Cyrillic characters in previously created docs
https://bugs.documentfoundation.org/show_bug.cgi?id=142142 --- Comment #7 from QA Administrators --- Dear Andy, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98520] ODF Validator reported error: attribute "text:start-value" on element "text:list-level-style-number" has a bad value: "0"
https://bugs.documentfoundation.org/show_bug.cgi?id=98520 --- Comment #6 from QA Administrators --- Dear Franklin Weng, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142131] The menus are empty when the window is too large
https://bugs.documentfoundation.org/show_bug.cgi?id=142131 --- Comment #6 from QA Administrators --- Dear Olivier DENIZOT, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91901] Clicking on an image causes Paste toolbar button to loose drop down button
https://bugs.documentfoundation.org/show_bug.cgi?id=91901 --- Comment #4 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89288] Extra space displayed when Indic text meets non-Indic.
https://bugs.documentfoundation.org/show_bug.cgi?id=89288 --- Comment #13 from QA Administrators --- Dear ssmithg1, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 46967] RTF lists don't inherit style of their paragraph (leveltext doesn't scale bullet point with font size)
https://bugs.documentfoundation.org/show_bug.cgi?id=46967 --- Comment #13 from QA Administrators --- Dear soren.hein, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36548] HTML import: display of nested tables broken
https://bugs.documentfoundation.org/show_bug.cgi?id=36548 --- Comment #19 from QA Administrators --- Dear Christina Rossmanith, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128713] missing grid pixels ...
https://bugs.documentfoundation.org/show_bug.cgi?id=128713 --- Comment #2 from QA Administrators --- Dear Michael Meeks, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128702] In nested lists, unexpected results when trying to move unnumbered/non-bulleted entries
https://bugs.documentfoundation.org/show_bug.cgi?id=128702 --- Comment #3 from QA Administrators --- Dear Alex, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128697] Tangled-up Indent functions
https://bugs.documentfoundation.org/show_bug.cgi?id=128697 --- Comment #4 from QA Administrators --- Dear Alex, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128496] Printing a "form letter" with database fields ignores document print settings and tries to print with "default printer?"
https://bugs.documentfoundation.org/show_bug.cgi?id=128496 --- Comment #6 from QA Administrators --- Dear Duncan Bellamy, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128436] Range for Name forced to lowercase
https://bugs.documentfoundation.org/show_bug.cgi?id=128436 --- Comment #6 from QA Administrators --- Dear Jonny Grant, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128412] Cannot start word after line break with small letter
https://bugs.documentfoundation.org/show_bug.cgi?id=128412 --- Comment #3 from QA Administrators --- Dear david.cortes.rivera, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120326] User events originating from Impress Remote must reset screensaver timer
https://bugs.documentfoundation.org/show_bug.cgi?id=120326 --- Comment #4 from QA Administrators --- Dear Mike Kaganski, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117700] .html to .odt conversion (headless) sets asymmetrical margins
https://bugs.documentfoundation.org/show_bug.cgi?id=117700 --- Comment #9 from QA Administrators --- Dear jonas, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108112] Date in conditional text makes the text disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=108112 --- Comment #15 from QA Administrators --- Dear tobias.fr, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145624] New: Cut and paste does not work, except from inside libreoffice.
https://bugs.documentfoundation.org/show_bug.cgi?id=145624 Bug ID: 145624 Summary: Cut and paste does not work, except from inside libreoffice. Product: LibreOffice Version: 6.0.2.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: blth...@gmx.com Description: Very often pasting from other sources other than libreoffice apps do not work. The last item copied from a libreoffice app will be pasted instead. This bug has been reported and discussed ad nauseam but no fix seems to be provided. Steps to Reproduce: 1. Copy/cut from outside libreoffice 2. Paste into libreoffice writer / calc 3. Actual Results: Nothing Expected Results: paste what I have copied Reproducible: Sometimes User Profile Reset: No Additional Info: Version: 6.0.6.2 (x64) Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 CPU threads: 8; OS: Windows 10.0; UI render: default; Locale: en-MY (en_MY); Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145623] New: LibreOffice freezes when the last opened file was open through NFS and is not available any longer.
https://bugs.documentfoundation.org/show_bug.cgi?id=145623 Bug ID: 145623 Summary: LibreOffice freezes when the last opened file was open through NFS and is not available any longer. Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: framework Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mongolie2006-freedesk...@yahoo.fr I'm on Fedora 35 workstation (Gnome), connected through NFSv4 with fstab options "nfs4 x-systemd.automount,x-systemd.idle-timeout=300,async0 0". If I open a document through NFS, close it, close LibreOffice, cut the network by unplugging the Ethernet cable or turning the NFS server off, reopen LibreOffice, the latter freezes. If I reboot and open LibreOffice, it still freezes. If I plug on the network and open LibreOffice, it works. If I close Libreoffice, reopen it without opening a document through NFS, close LibreOffice, cut the network, reopen LibreOffice: it works. But If I then go to "Recent documents", LibreOffice freezes. If I close and reopen it, then chose recovery (of a local document), it freezes. If I close it and reopen it, choosing to discard recovery, it freezes too. If I plug the computer to the network, go to tools → options → LibreOffice → Open Expert Configuration → org.openoffice.Office.Common → History → PickListSize, set it to 0, open a document through NFS, close LibreOffice, unplug from the network and reopen LibreOffice, it works. There should be a short timeout (for instance 20 s: nowadays networks don't need minutes for NFS connection): the last open document, specially if it was normally closed by the user, is not essential and could be ignored, and/or removed from the "Recent documents" list, rather than blocking LibreOffice forever. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145599] Calc Charts display gets corrupted when you draw a line inside them
https://bugs.documentfoundation.org/show_bug.cgi?id=145599 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from m.a.riosv --- Reproducible. Version: 7.2.3.1 (x64) / LibreOffice Community Build ID: 1d5dee817bde88d78dbcc0d00f88492568e131d5 CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL Seems the issue is in save/reopen. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145615] Recalculation Issue: changes in field value not recalculated.
https://bugs.documentfoundation.org/show_bug.cgi?id=145615 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Please attach a sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145619] EDITING Rounding issue when re-enter Row height in millimeters
https://bugs.documentfoundation.org/show_bug.cgi?id=145619 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from m.a.riosv --- *** This bug has been marked as a duplicate of bug 144247 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108734] [META] Character dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108734 Bug 108734 depends on bug 110003, which changed state. Bug 110003 Summary: Lower-case ß is capitalized as SS instead of ẞ https://bugs.documentfoundation.org/show_bug.cgi?id=110003 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=71732 Bug 71732 depends on bug 110003, which changed state. Bug 110003 Summary: Lower-case ß is capitalized as SS instead of ẞ https://bugs.documentfoundation.org/show_bug.cgi?id=110003 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145622] New: Recording a Macro in Calc, not generating the proper code
https://bugs.documentfoundation.org/show_bug.cgi?id=145622 Bug ID: 145622 Summary: Recording a Macro in Calc, not generating the proper code Product: LibreOffice Version: 7.1.6.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: debu...@gmail.com Description: I have created a macro to sort columns of numbers or letters many times with no issues. Now when I create the same macro and assign it to a button, it does not work. When I look at the code for the macro I notice it is missing a large number of args() lines. Example of missings lines: args3(0).Name="Byrows" args3(0).value=true ETC.. Completely mystified. Steps to Reproduce: In Calc create a short list of Letters and Numbers in columns. Maybe 6 rows. Now RECORD a Macro to sort the LETTERS in ASCENDING order. And RECORD a macro to sort the NUMBERS in DECSENDING order. Create 2 buttons and assign the macros to the proper buttons. Once done, click the buttons and the letters or numbers should be sorted in proper order, basedon the assigned macro. Actual Results: THE MACROS DO NOT SORT THE ROWS. Expected Results: SORTED THE ROWS Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.1.6.2 IF YOU EDIT THE MACRO, YOU WILL SEE THE LINES ARGx(0).Name="Byrows" etc.. are missing. Also notice below the REM in front of the DISPATCHER line. below rem -- dim args2(0) as new com.sun.star.beans.PropertyValue args2(0).Name = "ToPoint" args2(0).Value = "$A$4:$B$9" dispatcher.executeDispatch(document, ".uno:GoToCell", "", 0, args2()) rem -- rem dispatcher.executeDispatch(document, ".uno:DataSort", "", 0, Array()) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139629] Page style not properly copy/pasted
https://bugs.documentfoundation.org/show_bug.cgi?id=139629 --- Comment #11 from Telesto --- (In reply to Justin L from comment #10) > I would call this not a bug after reading the comments. Surely you do not > want your currently defined page styles over-written when pasting some > content from another document. Well this more exercise reframing/redefining the actual issue. Which fine - deeper investigation - however I still see a problem 1. Open the attached file 2. Go to page 5 3. Say I want to copy chapter 1 4. Press arrow left the place cursor left of Chapter 1 5. CTRL+SHIFT ARROW DOWN number of times to select content of Chapter 1 5. CTRL+C 6. CTRL+N 7. CTRL+V Result Chapter 1 page style being copied & pasted Endnote page style skipped, but endnotes are pasted (making even more complicated) --- 8. CTRL+N 9. Sidebar -> Styles -> Page Style tab 10. Create a new page style called Chapter 1 11. On the page tab set orientation to landscape 12. Press OK (style isnt applied, only present) 13. CTRL+V Result. Conflicting page styles with same name. The existing - in document - page style is kept above the one on the clipboard. If there is no conflict the page style is simply pasted The solution would be to make the copy/paste style unique. So if they same style name is present in source as target document, the style from source document needs to renamed to something else. Instead of using an arbitrary page style with the same name Another option would be to not copy/paste the page style in any case The current is mishmash of both worlds -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145610] The numbering of numbered list doesn't show when changing bulleted for numbered list
https://bugs.documentfoundation.org/show_bug.cgi?id=145610 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4578 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145610] The numbering of numbered list doesn't show when changing bulleted for numbered list
https://bugs.documentfoundation.org/show_bug.cgi?id=145610 raal changed: What|Removed |Added CC||vasily.melenc...@cib.de Keywords|bibisectRequest |bibisected, bisected --- Comment #3 from raal --- This seems to have begun at the below commit. Adding Cc: to Vasily Melenchuk; Could you possibly take a look at this one? Thanks ece145a9256e41b9eab649aeacf536f7e547b894 is the first bad commit commit ece145a9256e41b9eab649aeacf536f7e547b894 Author: Jenkins Build User Date: Mon Oct 4 15:37:10 2021 +0200 source sha:e6bf21d2d5efb231c877eb985997b28033198600 https://git.libreoffice.org/core/+/e6bf21d2d5efb231c877eb985997b28033198600 tdf#144578: numbering: generate include upper levels for UI -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145621] Crash swlo!IDocumentMarkAccess::IsLegalPaMForCrossRefHeadingBookmark+0x2681 at overwriting certain area
https://bugs.documentfoundation.org/show_bug.cgi?id=145621 Telesto changed: What|Removed |Added Blocks||133092 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Telesto changed: What|Removed |Added Depends on||145621 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145621 [Bug 145621] Crash swlo!IDocumentMarkAccess::IsLegalPaMForCrossRefHeadingBookmark+0x2681 at overwriting certain area -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145621] Crash swlo!IDocumentMarkAccess::IsLegalPaMForCrossRefHeadingBookmark+0x2681 at overwriting certain area
https://bugs.documentfoundation.org/show_bug.cgi?id=145621 Telesto changed: What|Removed |Added Keywords||bibisectRequest, regression --- Comment #3 from Telesto --- Still OK with Version: 6.4.0.0.alpha0+ (x64) Build ID: c56bf1479cc71d1a2b0639f6383e90c1f7e3655b CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145621] Crash swlo!IDocumentMarkAccess::IsLegalPaMForCrossRefHeadingBookmark+0x2681 at overwriting certain area
https://bugs.documentfoundation.org/show_bug.cgi?id=145621 --- Comment #2 from Telesto --- Created attachment 176184 --> https://bugs.documentfoundation.org/attachment.cgi?id=176184=edit BT without symbols -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145621] Crash swlo!IDocumentMarkAccess::IsLegalPaMForCrossRefHeadingBookmark+0x2681 at overwriting certain area
https://bugs.documentfoundation.org/show_bug.cgi?id=145621 --- Comment #1 from Telesto --- Created attachment 176183 --> https://bugs.documentfoundation.org/attachment.cgi?id=176183=edit Example file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145621] New: Crash swlo!IDocumentMarkAccess::IsLegalPaMForCrossRefHeadingBookmark+0x2681 at overwriting certain area
https://bugs.documentfoundation.org/show_bug.cgi?id=145621 Bug ID: 145621 Summary: Crash swlo!IDocumentMarkAccess::IsLegalPaMForCrossRefHeading Bookmark+0x2681 at overwriting certain area Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Crash swlo!IDocumentMarkAccess::IsLegalPaMForCrossRefHeadingBookmark+0x2681 at overwriting certain area Steps to Reproduce: 1. Open the attached file 2. Press arrow left 3. Press CTRL+SHIFT+Arrow RIGHT 4. Press CTRL+C 5. Press CTRL+V Or 1. Open the attached file 2. Press arrow left 3. Press CTRL+SHIFT+Arrow RIGHT 4. Press CTRL+C 5. CTRL+N 6. CTRL+V 7. CTRL+Z 8. CTRL+V -> Crash Actual Results: Crash Expected Results: No crash Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 73334560b2dd2d60ac58d2cc2b1a5295490b03e1 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145610] The numbering of numbered list doesn't show when changing bulleted for numbered list
https://bugs.documentfoundation.org/show_bug.cgi?id=145610 raal changed: What|Removed |Added CC||r...@post.cz Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from raal --- Confirm with Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: a14b783bbe8eda32b4b79530d85ffc48b6ed0305 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145582] Query → Edit in SQL-View treats file as changed when no changes have occurred
https://bugs.documentfoundation.org/show_bug.cgi?id=145582 raal changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected CC||caol...@redhat.com, ||r...@post.cz --- Comment #5 from raal --- This seems to have begun at the below commit. Adding Cc: to Caolán McNamara ; Could you possibly take a look at this one? Thanks 2a82ac4cd48a43ff63eb367b8804735565bc9a4b is the first bad commit commit 2a82ac4cd48a43ff63eb367b8804735565bc9a4b Author: Jenkins Build User Date: Tue Aug 3 16:50:39 2021 +0200 source sha:5b98dd53c7dc101d3a5ff693d3f0520ec1abd3d1 https://git.libreoffice.org/core/+/5b98dd53c7dc101d3a5ff693d3f0520ec1abd3d1 tdf#143657 'execute' button doesn't get enabled when contents changed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145584] Writer crashes on exporting as PDF with its Range in PDF Options set to 'Selection'
https://bugs.documentfoundation.org/show_bug.cgi?id=145584 Julien Nabet changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | Status|NEW |ASSIGNED --- Comment #6 from Julien Nabet --- I gave a try with https://gerrit.libreoffice.org/c/core/+/125014 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145393] Calc becomes unresponsive after a search, turning off "show this dialog" and doing a second search
https://bugs.documentfoundation.org/show_bug.cgi?id=145393 Frank changed: What|Removed |Added Ever confirmed|0 |1 Resolution|NOTOURBUG |--- Status|RESOLVED|REOPENED --- Comment #8 from Frank --- Bug is still there: Version: 7.2.2.2 / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-NZ (en_NZ.UTF-8); UI: en-US Flatpak Calc: threaded Does not happen with all spreadsheets, but is repeatable with this one: https://assets.mylotto.co.nz/assets/uploads/423829ee-4265-11ec-900f-90817b0e0c2d.xlsx Do a 'Find a number' 3 or 4 times and Calc hangs. After the 'unresponsive' message it closes. Then try to start Calc again and the progress bar remains blank. It completely hangs and the process needs to be killed. A subsequent attempt to 'recover' after opening (and a system restart) also hangs Calc. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108310] FILEOPEN: particular docbook .xml is truncated.
https://bugs.documentfoundation.org/show_bug.cgi?id=108310 --- Comment #7 from Terrence Enger --- I still see the problem in a local build of commit 631aa911 (2021-11-09) built and running on debian-buster. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145620] Tabs added in text box of Writer module using the ruler do not function.
https://bugs.documentfoundation.org/show_bug.cgi?id=145620 --- Comment #1 from tragou...@mac.com --- This report was created because I received an email asking to determine if the bug has been fixed in the latest version of LibreOffice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145620] New: Tabs added in text box of Writer module using the ruler do not function.
https://bugs.documentfoundation.org/show_bug.cgi?id=145620 Bug ID: 145620 Summary: Tabs added in text box of Writer module using the ruler do not function. Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tragou...@mac.com Description: Adding tabs in a text box in the Writer app using the ruler do not function properly. The tab appears in the ruler and looks functional, but when you press the tab key to move the cursor to the desired tab stop the cursor moves in the default 1/2" increments. It's as if you pressed tab prior to adding the custom tab positions in the ruler. Using the Format —> Paragraph window allows me to add tab stops in the text box successfully. They appear in the ruler as expected and pressing the tab key moves the cursor to each custom tab position consecutively. Only tabs added by clicking on the ruler don't work. NEW DISCOVERY: After adding the tabs to the ruler while the cursor is in the text box I then used my mouse to place the cursor OUTSIDE the text box in the location it had been prior to adding the text box. All the tabs I added on the ruler while the cursor was inside the text box were there and functioning OUTSIDE the text box. In other words, the tabs added to the ruler are being added to the document rather than to the text box. I hope that helps! Steps to Reproduce: 1.Create a text box in LibreOffice Writer Document. 2.Click on the ruler to add tabs that are different from the 1/2" defaults. 3.Attempt to use th tabs to enter text at tab positions. Actual Results: The ruler shows the tabs in the positions clicked on, but when you press the tab key to move the cursor to the tab position it moves in the standard 1/2" increments instead. Expected Results: The cursor should move to each tab stop in succession as seen on the ruler, skipping the default tab stops at the 1/2" increments. Reproducible: Always User Profile Reset: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Mac OS X (All) OS is 64bit: no >From LibreOffice menu on Mac "About Libre Office": Version: 7.2.2.2 / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Additional Information: Using the Format –> Paragraph window I can add and remove tabs successfully. They show up on the ruler as expected and function perfectly when typing the tab key to position the cursor in the next position. It is only the tabs added from the ruler that fail to work properly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145619] New: EDITING Rounding issue when re-enter Row height in millimeters
https://bugs.documentfoundation.org/show_bug.cgi?id=145619 Bug ID: 145619 Summary: EDITING Rounding issue when re-enter Row height in millimeters Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: regeirs.fo...@gmail.com Affected versions of LibO - tested today On Windows 10 Version: 7.2.2.2 (x86) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: nb-NO (nb_NO); UI: en-US Calc: threaded On Fedora 33, Mate Version: 7.0.6.2 Build ID: 00(Build:2) CPU threads: 4; OS: Linux 5.14; UI render: default; VCL: gtk3 Locale: nb-NO (en_US.UTF-8); UI: en-US Calc: threaded Pre-configuration in order to reproduce: - Options --> LibreOffice Calc --> General - Measurement unit = Millimeter - Tab stops = 12,7 mm - Options --> Language settings - User Interface = Default - English (USA) - Locale settings = Norwegian, Bokmål Steps to reproduce - Open empty spread sheet - Select any row (row 11 for instance) - Type a new value (9,00 in a particular test) and OK/close - Select the same row again and re-enter the Row height menu (only to observe). Expected value to be stored in Height text edit field: «9,00» Observed value on Windows 10 / LibO 7.2.2.2 : «8,9958 mm» On Fedora 33 / LibO 7.0.6.2 : «9,00 mm», but if I enter 8 instead and then re-opening row height dialog for the same row, then I observe «8,01 mm». -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141474] Documentation specifies incorrect parameter names for Basic functions
https://bugs.documentfoundation.org/show_bug.cgi?id=141474 --- Comment #11 from Vladimir Sokolinskiy --- Thanks again! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141474] Documentation specifies incorrect parameter names for Basic functions
https://bugs.documentfoundation.org/show_bug.cgi?id=141474 --- Comment #10 from Commit Notification --- Alain Romedenne committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/b902fbcc87b0baf76b3dd501f0feff40bb1f3711 tdf#141474 Atn, Cos, Sin, Tan function signatures -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141474] Documentation specifies incorrect parameter names for Basic functions
https://bugs.documentfoundation.org/show_bug.cgi?id=141474 Commit Notification changed: What|Removed |Added Whiteboard|target:7.2.0|target:7.2.0 target:7.3.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113375] [META] Database wizard bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113375 Bug 113375 depends on bug 106427, which changed state. Bug 106427 Summary: failure to diagnose invalid file: URL https://bugs.documentfoundation.org/show_bug.cgi?id=106427 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106427] failure to diagnose invalid file: URL
https://bugs.documentfoundation.org/show_bug.cgi?id=106427 Terrence Enger changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #13 from Terrence Enger --- In a local build of commit 631aa911, built and running on debian-buster, when I try to save the .odb, LO gives the message Error code: 1 firebird_sdbc error: *Unable to complete network request to host "file". *Failed to locate host machine. *The specified name was not found in the hosts file or Domain Name Services. caused by 'isc_create_database' /home/terry/lo_hacking/git/libo6/connectivity/source/drivers/firebird/Util.cxx:68 and LO gives the same message for "Test Connection". I am setting bug status RESOLVED WORKSFORME. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118017] support macOS dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118017 --- Comment #11 from Michael Warner --- (In reply to Pedro from comment #3) > It is licensed under GPL3 as LO, so maybe we could bring their code to > mainline LO. LO is Mozilla Public License 2 --- and as far as I know it wants to stay that way --- so we certainly cannot drop GPL code into it. Other GPL components we use are built as separate executables and then have some sort of IPC communication or we read their output files or something like that, but techniques like this won't be useful for adding in dark mode support. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145618] Update button changes the height of the menu bar and makes it jump
https://bugs.documentfoundation.org/show_bug.cgi?id=145618 Denis Abakumov changed: What|Removed |Added CC||denisa...@gmail.com --- Comment #1 from Denis Abakumov --- Created attachment 176182 --> https://bugs.documentfoundation.org/attachment.cgi?id=176182=edit GIF to demo the bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145560] VLOOKUP does not work when calc file is imported from Lotus 1-2-3 release 4 for windows
https://bugs.documentfoundation.org/show_bug.cgi?id=145560 Michael Warner changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #3 from Michael Warner --- >From email: Attached is a Lotus 1-2-3 file that shows the problem. This is not the file that I first found the problem, but a much simpler file that shows the problem. The file that first showed the problem is too large with too much personal info. In the attached file, Input a income amount in cell E4 and cell F4 should show the amount of taxes. When you first import the spreadsheet into Libre calc cell C4 shows 2 and cell F4 shows 2002 which is correct but when the spreadsheet is recalculated cell F4 shows Err:502. Simply re enter 2 or any number into cell E4 to recalculate the spreadsheet and see the error. I figured out what is causing the problem, but not a easy fix. The problem is caused by the index number in the VLOOKUP function. VLOOKUP is looking for a number in column A,B or C of the spreadsheet depending on the index number. Lotus 1-2-3 wants the index numbers to start at 0. In this case, Columns A,B or C would be 0,1 or 2. Libre Calc wants the index numbers to start at 1. In this case, Columns A,B or C should be 1,2 or 3. I could change the index numbers after the file is imported, but this requires a lot of work as my spreadsheets are very large. This would work if it was a one time import but I must maintain the file on an older computer because of the Lotus Macro language programing in the file. I wish to import the file to another computer that will not run Lotus 1-2-3 but as you can see from the attached file the VLOOKUP function does not work. Thank you for your assistance Stuart Sabatini -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145560] VLOOKUP does not work when calc file is imported from Lotus 1-2-3 release 4 for windows
https://bugs.documentfoundation.org/show_bug.cgi?id=145560 --- Comment #2 from Michael Warner --- Created attachment 176181 --> https://bugs.documentfoundation.org/attachment.cgi?id=176181=edit TaxTest Received attachment via email. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145617] Documentation for CINT%: inappropriate, incomplete and misleading
https://bugs.documentfoundation.org/show_bug.cgi?id=145617 Olivier Hallot changed: What|Removed |Added Blocks||80430 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=80430 [Bug 80430] [META] Documentation gap for new features -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 80430] [META] Documentation gap for new features
https://bugs.documentfoundation.org/show_bug.cgi?id=80430 Olivier Hallot changed: What|Removed |Added Depends on||145617 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145617 [Bug 145617] Documentation for CINT%: inappropriate, incomplete and misleading -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145618] New: Update button changes the height of the menu bar and makes it jump
https://bugs.documentfoundation.org/show_bug.cgi?id=145618 Bug ID: 145618 Summary: Update button changes the height of the menu bar and makes it jump Product: LibreOffice Version: 7.2.1.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: trivial Priority: medium Component: graphics stack Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: denisa...@gmail.com Description: When any Libre Office app is activated in Windows 10, an Update button is added to the menu bar, which adds to the menu bar 4 pixels of height. Due to this, the visual effect is as if the whole app jumps when activated/deactivated. Steps to Reproduce: 1. Open at least 2 instances of Writer, Calc, or Draw. 2. Activate the first Libre Office app window. 3. Activate the second Libre Office app window. Actual Results: On steps 2 and 3 a noticeable jumping of the window content is observed due to the menu bar growing and shrinking by 4 px as the Update button comes and goes. Expected Results: The addition/removing of the Update button should not change size of the menu bar. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Tested in Windows 10 only (Version 21H1 Build 19043.1288), in Writer, Calc, and Draw. Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 12; OS: Windows 10.0 Build 19043; 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.
[Libreoffice-bugs] [Bug 143396] nVidia GPU Skia Vulkan -- Quadro K2000 (Device: 0xffe)-- resizing floating Sidebar and dragging deck wider while crossing onto main LO window frame.
https://bugs.documentfoundation.org/show_bug.cgi?id=143396 V Stuart Foote changed: What|Removed |Added Summary|nVidia GPU Skia Vulkan -- |nVidia GPU Skia Vulkan -- |Quadro K2000 -- resizing|Quadro K2000 (Device: |floating Sidebar and|0xffe)-- resizing floating |dragging deck wider while |Sidebar and dragging deck |crossing onto main LO |wider while crossing onto |window frame. |main LO window frame. --- Comment #9 from V Stuart Foote --- OK, had an opportunity to test on a more modern nVidia Quadro RTX 4000 with Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL resize dragging width of the undocked SideBar deck across the app frame does not crash. A Geforce GTX-750 TI and this Quadro RTX 4000 have no issues with crossing the app frame. So, probably the best thing is to deny list the Quadro K2000 (Device: 0xffe) from Vulkan rendering. =-skia.log-= RenderMethod: vulkan Vendor: 0x10de Device: 0x1eb1 API: 1.2.155 Driver: 462.124.0 DeviceType: discrete DeviceName: Quadro RTX 4000 Denylisted: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115121] [META] Chapter numbering dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=115121 Dieter changed: What|Removed |Added Depends on||145308 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145308 [Bug 145308] Chapter Numbering: "Before" characters from level are added, that have no numbering -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103370] [META] Outline/Chapter numbering bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103370 Dieter changed: What|Removed |Added Depends on||145308 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145308 [Bug 145308] Chapter Numbering: "Before" characters from level are added, that have no numbering -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145308] Chapter Numbering: "Before" characters from level are added, that have no numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=145308 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Summary|chapter numbering: |Chapter Numbering: "Before" |separator when higher level |characters from level are |has no numbering|added, that have no ||numbering Blocks||115121, 103370 CC||dgp-m...@gmx.de Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEW --- Comment #1 from Dieter --- I confirm it with Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Steps to reproduce 1. Add three paragraphs to a document and assign the following styles: Heading 1, Heading 2, Heading 3 2. Tools => chapter numbering 3. Level 1: Number [None] Paragraph Style [Heading1] 4. Level 2: Number [1,2,3...] Paragraph Style [Heading2] Separator: "." Before Actual result .1 in preview and also in document after pressing O.K. 4. Level 2: Number [None] 5. Level 3: Number [1,2,3...] Paragraph Style [Heading3] Separator: "." Before Actual result ..1 in preview and also in document after pressing OK Explanation: LO doesn't respect, that level 1 and 2 have no numbers and adds the dots from those levels. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103370 [Bug 103370] [META] Outline/Chapter numbering bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=115121 [Bug 115121] [META] Chapter numbering dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121546] CRASH undoing table paste
https://bugs.documentfoundation.org/show_bug.cgi?id=121546 --- Comment #14 from Caolán McNamara --- https://gerrit.libreoffice.org/c/core/+/124999 seeems to fix the assert and also the initially reported crash -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105537] [META] Assertion failed crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=105537 Bug 105537 depends on bug 145508, which changed state. Bug 145508 Summary: kf5: Assert hit when starting Impress presentation after e4abf879f4a24258bcc560eb58ca78b147768d46 https://bugs.documentfoundation.org/show_bug.cgi?id=145508 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Bug 102495 depends on bug 145508, which changed state. Bug 145508 Summary: kf5: Assert hit when starting Impress presentation after e4abf879f4a24258bcc560eb58ca78b147768d46 https://bugs.documentfoundation.org/show_bug.cgi?id=145508 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145508] kf5: Assert hit when starting Impress presentation after e4abf879f4a24258bcc560eb58ca78b147768d46
https://bugs.documentfoundation.org/show_bug.cgi?id=145508 Jan-Marek Glogowski changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145617] New: Documentation for CINT%: inappropriate, incomplete and misleading
https://bugs.documentfoundation.org/show_bug.cgi?id=145617
Bug ID: 145617
Summary: Documentation for CINT%: inappropriate, incomplete and
misleading
Product: LibreOffice
Version: 7.3.0.0 alpha0+ Master
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Documentation
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: giecr...@stegny.2a.pl
CC: olivier.hal...@libreoffice.org
Description:
The documentation for the function CINT% is inappropriate, incomplete and
misleading.
Steps to Reproduce:
1. Examine the documentation for CInt Function.
Actual Results:
CInt Function
Converts any string or numeric expression to an integer.
Syntax:
CInt (Expression)
Return value:
Integer
Parameters:
Expression: Any numeric expression that you want to convert. If the Expression
exceeds the value range between -32768 and 32767, LibreOfficeDev Basic reports
an overflow error. To convert a string expression, the number must be entered
as normal text ("123.5") using the default number format of your operating
system.
This function always rounds the fractional part of a number to the nearest
integer.
Error codes:
5 Invalid procedure call
Example:
Sub ExampleCountryConvert
MsgBox CDbl(1234.5678)
MsgBox CInt(1234.5678)
MsgBox CLng(1234.5678)
End Sub
Expected Results:
CInt Function
Converts any string or numeric expression to an integer.
Syntax:
CInt (Expression)
Return value:
Integer
Parameters:
Expression: Any numeric or string expression that you want to convert.
If the Expression is a number that exceeds the value range between -32768 and
32767, LibreOfficeDev Basic reports an overflow error.
A string parameter will be interpreted in a locale-specific way as specified in
the operating system settings for floating-point number format. Initial blanks
will be skipped and all trailing characters beginning with a non-digit will be
ignored. Initial signs are allowed but any space following them will cause the
string to be converted to 0.
If the trimmed string begins with a base indicator or , the string will
interpreted in the corresponding base using an universal integer format.
Trailing letters that do not represent digits in the corresponding base
(including ALL letters in base 8) immediately following the number will cause
the function to unconditionally return 0.
This function always rounds the fractional part of a number, if applicable, to
the nearest integer.
Error codes:
5 Invalid procedure call
Example:
Sub ExampleCountryConvert
IF CINT% (" 1A ") <> 1 THEN STOP
IF CINT% ("+ 1") <> 0 THEN STOP
IF CINT% (" 1,235E2") <> 124 THEN STOP
IF CINT% (" 1235E-1") <> 124 THEN STOP
IF CINT% (" +:A ") <> THEN STOP
IF CINT% (" - ") <> - THEN STOP
IF CINT% (" ") <> 0 THEN STOP
IF CINT% (" -:X ") <> - THEN STOP
End Sub
Reproducible: Always
User Profile Reset: Yes
OpenGL enabled: Yes
Additional Info:
https://help.libreoffice.org/7.3/en-US/text/sbasic/shared/03100500.html >
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145605] Crash in 0, 5 - 4 minutes after start on Wayland/X11 on AMD Graphics
https://bugs.documentfoundation.org/show_bug.cgi?id=145605 sergej.alexe...@gmail.com changed: What|Removed |Added Summary|Crash in 0,5 - 4 minutes|Crash in 0,5 - 4 minutes |after start on Fedora |after start on Wayland/X11 |Silverblue (Flatpak) Ryzen |on AMD Graphics |5000 Series | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145616] PRINTING: unable to print or generate PostScript from Writer Document with embedded grayscale images
https://bugs.documentfoundation.org/show_bug.cgi?id=145616 --- Comment #2 from wisch...@bfw-online.de --- Created attachment 176180 --> https://bugs.documentfoundation.org/attachment.cgi?id=176180=edit PostScript file generated by LibO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145616] PRINTING: unable to print or generate PostScript from Writer Document with embedded grayscale images
https://bugs.documentfoundation.org/show_bug.cgi?id=145616 --- Comment #1 from wisch...@bfw-online.de --- Created attachment 176179 --> https://bugs.documentfoundation.org/attachment.cgi?id=176179=edit Writer Document with embedded images Simple LibO Document with two images embedded, one in RGB and one in Grayscale -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145616] New: PRINTING: unable to print or generate PostScript from Writer Document with embedded grayscale images
https://bugs.documentfoundation.org/show_bug.cgi?id=145616 Bug ID: 145616 Summary: PRINTING: unable to print or generate PostScript from Writer Document with embedded grayscale images Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: wisch...@bfw-online.de Description: It seems as if the wrong color space is being used for generation of the Post Script code for grayscale images. Trying to view it with GhostView leads to an error. Also trying to print the document directly from LibO does not result on any output on the printer. Steps to Reproduce: 1. Create a new LibreOffice Writer Document 2. Insert > Image... > Select an image that is saved in grayscale 3. File > Print... > select Printer: Print to File... 4. Click on Properties... > Device > select Printer language type: PostScript Actual Results: PostScript file contains 'DeviceRGB' for that image Expected Results: should be a 'DeviceGray' instead Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.2.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 96; OS: Linux 4.14; UI render: default; VCL: x11 Locale: en-US (C); UI: en-US Debian package version: 1:7.2.2-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145108] Read-only documents can still be changed by drag-and-droping text
https://bugs.documentfoundation.org/show_bug.cgi?id=145108 yellowplane <1yellowpl...@gmail.com> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||1yellowpl...@gmail.com --- Comment #1 from yellowplane <1yellowpl...@gmail.com> --- I can reproduce in Version: 7.3.0.0.alpha1+ (x86) / LibreOffice Community Build ID: ccf3d9140a24d767003c08cd0247e6ee6fd12fe0 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_US); UI: en-US Calc: threaded In addition to dragging and dropping, I realized that you can move the text using the space bar. Other text manipulations remained unusable as expected, and I confirmed that ctrl+s is disabled and the file itself is not changed once you close out of the document and open it again. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 53027] EDITING: dBase-Import-Wizard fails when trying to append DECIMAL(NUMERIC) and BOOLEAN data types
https://bugs.documentfoundation.org/show_bug.cgi?id=53027 chief changed: What|Removed |Added URL||https://careersngr.com --- Comment #52 from chief --- When I open LO there is a welcomescreen with all the sub-programms of LO. There you have to click on "Database". When you have started LO directly, for example with the sub-program writer, you could find the same with file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121546] CRASH undoing table paste
https://bugs.documentfoundation.org/show_bug.cgi?id=121546 --- Comment #13 from Caolán McNamara --- Created attachment 176178 --> https://bugs.documentfoundation.org/attachment.cgi?id=176178=edit much smaller document that can reproduce the assert -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145606] feature request: be able to set "always recover and always finish"
https://bugs.documentfoundation.org/show_bug.cgi?id=145606 Michael Warner changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||2176 --- Comment #2 from Michael Warner --- While I think what you suggest is a reasonable feature, I can say that it may be some time before it is implemented. A more immediate way of dealing with the inconvenience of the recovery dialog box would be to create a Sikuli script to click the buttons for you, and have that launch on startup. Or you could just get in the habit of always closing all applications before shutting down, that's what I do. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142176] No prompt during logout/restart/shutdown when there's unsaved documents
https://bugs.documentfoundation.org/show_bug.cgi?id=142176 Michael Warner changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5606 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90486] [META] Chart bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=90486 Bug 90486 depends on bug 136111, which changed state. Bug 136111 Summary: Scaling problem on chart driven by a macro. https://bugs.documentfoundation.org/show_bug.cgi?id=136111 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136111] Scaling problem on chart driven by a macro.
https://bugs.documentfoundation.org/show_bug.cgi?id=136111 Collabora Productivity Ltd changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145607] Very slow startup when network drive is mounted in Windows 10 Pro
https://bugs.documentfoundation.org/show_bug.cgi?id=145607 Michael Warner changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||1302 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 101302] Deleted files visible as recent documents in menu and start center
https://bugs.documentfoundation.org/show_bug.cgi?id=101302 Michael Warner changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5607 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144566] LibreOffice won't start when there is an unreachable file in "recent documents" list
https://bugs.documentfoundation.org/show_bug.cgi?id=144566 Michael Warner changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5607 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145607] Very slow startup when network drive is mounted in Windows 10 Pro
https://bugs.documentfoundation.org/show_bug.cgi?id=145607 Michael Warner changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4566 Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Michael Warner --- (In reply to Julien Pierre from comment #0) Have you saved documents to the network drive? It may be hanging up waiting to check on them for the recent files list in the start center when it detects the drive is mounted (or will be mounted once all the networking stack has started). There were some other recent bugs similar to this. Bug 144566 is the one I can find at the moment. Bug 101302 has a different summary but seems related or similar with more description and tracing in it. > I have tried doing a fresh OS install of Windows 11 on a spare SATA SSD, and > booting it from a SATA dock in order to test this behavior, and can't > reproduce the issue there. In this case, when you boot from the spare drive and start LO you would have a clean user profile, so your recent files list would be empty. > I'm guessing that there is some interaction between LibreOffice and one of > the dozens of programs installed on my main Windows 10 partition. > Reinstalling the OS from scratch and all the apps would take weeks of setup, > There are so many things, from monitor profiles, printer profiles, UI > customization, etc. I don't want to start over with the OS to make this > problem go away. And it might come back anyway, if it's a conflict with some > other application. I don't think it's a conflict with any of your other applications, and just blindly re-installing everything probably wouldn't solve the problem. > So, I'd like to get to the bottom of this issue. I'm willing to run a debug > build of LbireOffice if there is one for me to try and collect any data that > might help resolve it. > > User Profile Reset: No Try backing up and resetting you user profile as described here: https://wiki.documentfoundation.org/UserProfile Then see if the problem still occurs and what happens if you have recent files on the network drive. Let us know what you find out. -- You are receiving this mail because: You are the assignee for the bug.
