[Libreoffice-bugs] [Bug 152406] macOS Calc: Scrolling: scrollbar showing wrong position resulting in unscrollable document
https://bugs.documentfoundation.org/show_bug.cgi?id=152406 Buovjaga changed: What|Removed |Added Keywords||bibisectRequest, regression -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96372] Filters do not work on Hsqldb subquery result when subquery has alias.
https://bugs.documentfoundation.org/show_bug.cgi?id=96372 --- Comment #19 from Robert Großkopf --- Bug is still the same in LO 7.4.3.2 on OpenSUSE 15.3 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147982] On macOS Monterey LibreOffice 7.3 crashes about every day. This was also with previous versions of LibreOffice.
https://bugs.documentfoundation.org/show_bug.cgi?id=147982 --- Comment #25 from Alex Thurgood --- (In reply to Alexander Van den Panhuysen from comment #24) > Excuse me, do you still need more info? I'm sure everything is explained in > detail, I can not imagine what can be explained more. > Meanwhile I'm using fore some months LibreOffice 7.4, stil not working > properly. > When will this be solved? As we don't have a crash trace, we still don't know what is happening when it crashes. That said, a possibly similar problem was recently fixed in master branch 7.5 alpha, and this seems to have removed most of the deadlocking issues that were being seen. You could try a daily developer build, and report back. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147982] On macOS Monterey LibreOffice 7.3 crashes about every day. This was also with previous versions of LibreOffice.
https://bugs.documentfoundation.org/show_bug.cgi?id=147982 Alexander Van den Panhuysen changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #24 from Alexander Van den Panhuysen --- Excuse me, do you still need more info? I'm sure everything is explained in detail, I can not imagine what can be explained more. Meanwhile I'm using fore some months LibreOffice 7.4, stil not working properly. When will this be solved? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133122] Using a shape mask with a bitmap Shapes | Subtract alters aspect ratio of bitmap
https://bugs.documentfoundation.org/show_bug.cgi?id=133122 --- Comment #5 from Derek Keats --- This bug is still present, and is now also present in Impress. Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: en-ZA (en_ZA.UTF-8); UI: en-ZA Ubuntu package version: 1:7.4.2~rc3-0ubuntu1 Calc: threaded The behaviour is exactly as I documented initially, and it still forces the use of a third tool to do this one thing. It would be really awesome if it could be fixed as I use Libreoffice for everything otherwise, and it is a fantastic suite. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152160] Printed label's field content mismatch for spreadsheet data source if field added afterwards in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152160 Petri H changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #2 from Petri H --- Thanks for looking into this Stéphane. You need to walkthrough the specified procedure to reproduce the bug. details from my LibreOffice Version: 7.4.2.3 (x86) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (sv_SE); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137955] Browse Mode in LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=137955 --- Comment #9 from Quentin Christensen --- (In reply to V Stuart Foote from comment #4) > > > If NVDA 'Browse mode' is dependent on any UIA, pretty clearly > > > unsupportable > > > in LibreOffice where we support only accessible event triggers--as mapped > > > back to IA2. I can answer this (all speaking generally at least, since I haven't looked at the code on either side here) - while NVDA now uses UIA by default in recent builds of Word, because the experience there has improved to where it is better and more responsive than iA2 *in that situation* in general for the majority of users, we have otherwise (and still offer) iA2 support. So that should be possible in LO as well. I know one of our developers, Reef, commented previously that we weren't in a position to take on the whole project - https://github.com/nvaccess/nvda/issues/8148#issuecomment-744228528 - At the time he suggested looking at how NVDA handles browse mode using iA2 in browsers. I don't think we're currently in a better position to own the endeavour, but I'm happy to keep the dialog open. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152402] Prints dark background instead of white with custom dark settings
https://bugs.documentfoundation.org/show_bug.cgi?id=152402 --- Comment #3 from nopainenogai...@hushmail.com --- (In reply to nopainenogain12 from comment #2) > Created attachment 184028 [details] > sample document in print preview Not sure where to put this: I found a solution after messing with it all day. I hit the reset button. LibreOffice > Options > Applications Colorsbottom reset button changed the page to how it should have displayed in print preview and when being printed...white. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137955] Browse Mode in LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=137955 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||dgp-m...@gmx.de --- Comment #8 from Dieter --- (In reply to juergenkohler23 from comment #6) > I have tried again to contact the NVDA developers; without their help the > necessary information will probably not be available... Jürgen, any news? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143700] Libreoffice All Modules Bug Reporting
https://bugs.documentfoundation.org/show_bug.cgi?id=143700 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 143480] Writer: In Navigator, promotion or demotion of a level should change heading level in document
https://bugs.documentfoundation.org/show_bug.cgi?id=143480 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143480] Writer: In Navigator, promotion or demotion of a level should change heading level in document
https://bugs.documentfoundation.org/show_bug.cgi?id=143480 --- Comment #10 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148579] Print Preview jumps to a different page upon zooming in/out
https://bugs.documentfoundation.org/show_bug.cgi?id=148579 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148579] Print Preview jumps to a different page upon zooming in/out
https://bugs.documentfoundation.org/show_bug.cgi?id=148579 --- Comment #3 from QA Administrators --- Dear Ben, 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 146430] Cannot apply edited master slide to selected/all slides
https://bugs.documentfoundation.org/show_bug.cgi?id=146430 --- Comment #3 from QA Administrators --- Dear NarayanAras, 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 144529] Double ListBox dlg:selected attribute corrupts xdl dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=144529 --- Comment #3 from QA Administrators --- Dear bughugger, 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 146430] Cannot apply edited master slide to selected/all slides
https://bugs.documentfoundation.org/show_bug.cgi?id=146430 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149075] Windows 10 Skia: Writer closes after startup
https://bugs.documentfoundation.org/show_bug.cgi?id=149075 --- Comment #16 from QA Administrators --- Dear 2sas, 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 96372] Filters do not work on Hsqldb subquery result when subquery has alias.
https://bugs.documentfoundation.org/show_bug.cgi?id=96372 --- Comment #18 from QA Administrators --- Dear Saren Tasciyan, 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 99222] While typing, some characters appear out of order from how they are typed.
https://bugs.documentfoundation.org/show_bug.cgi?id=99222 --- Comment #10 from QA Administrators --- Dear Joseph, 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 66772] EDITING: LibO not allows input methods and IME to use some "Ctrl+XXX" hotkeys
https://bugs.documentfoundation.org/show_bug.cgi?id=66772 --- Comment #14 from QA Administrators --- Dear minhsien0330, 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 138591] Using Unicode conversion on a combined emoji results in only partial conversion
https://bugs.documentfoundation.org/show_bug.cgi?id=138591 --- Comment #10 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 138615] Insure Windows wildcards work properly with long paths
https://bugs.documentfoundation.org/show_bug.cgi?id=138615 --- Comment #3 from QA Administrators --- Dear Deb, 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 137042] SQL Error -607, when changing Field type of a table (Firebird)
https://bugs.documentfoundation.org/show_bug.cgi?id=137042 --- Comment #15 from QA Administrators --- Dear Richard Demattio, 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 136068] Certain formula get corrupted after DOC export (and get lost when converting to DOCX)
https://bugs.documentfoundation.org/show_bug.cgi?id=136068 --- Comment #5 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135941] Frame has no border after DOCX export (depending on line style)
https://bugs.documentfoundation.org/show_bug.cgi?id=135941 --- Comment #2 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114116] Dialog "assign datasource" in Writer doesn't display the source name in the list
https://bugs.documentfoundation.org/show_bug.cgi?id=114116 --- Comment #8 from QA Administrators --- Dear Thomas Krumbein, 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 112472] "Number" number format listbox entry should toggle the format as number uno command
https://bugs.documentfoundation.org/show_bug.cgi?id=112472 --- Comment #7 from QA Administrators --- Dear Emil Tanev, 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 152265] UI: tip of the day: placeholder "PRODUCTNAME" in text of the tip
https://bugs.documentfoundation.org/show_bug.cgi?id=152265
--- Comment #3 from Andika Triwidada ---
found some typos: %(space)PRODUCTNAME or (probably missing %)PRODUCTNAME
andika@libre:~/libreoffice/translations/source/nl$ git status
HEAD detached at libreoffice-7.3.7.2
Untracked files:
(use "git add ..." to include in what will be committed)
../id/helpcontent2/source/text/simpress/guide.po.bak
nothing added to commit but untracked files present (use "git add" to track)
andika@libre:~/libreoffice/translations/source/nl$ grep -nR PRODUCTNAME *|grep
-v \%PRODUCTNAME|grep -v '${PRODUCTNAME}'|grep -v '\[PRODUCTNAME\]'|grep -v
'\[FULLPRODUCTNAME\]'
cui/messages.po:2614:msgstr "U kunt het uiterlijk van PRODUCTNAME wijzigen via
Extra > Opties > Beeld > Gebruikersinterface."
cui/messages.po:2626:msgstr "U kunt formules tonen in plaats van resultaten met
Beeld > Formule weergeven (of Extra > Opties > PRODUCTNAME Calc > Beeld >
Weergave > Formules."
helpcontent2/source/text/sbasic/shared.po:3221:msgstr "De variabele is geldig
zolang de% PRODUCTNAME-sessie duurt."
helpcontent2/source/text/sbasic/shared.po:4040:msgstr "% PRODUCTNAME
Standaardbibliotheken kunnen in 3 verschillende containers worden opgeslagen:"
helpcontent2/source/text/shared/01.po:6281:msgstr "Opent een nieuw venster in uw
standaard e-mailprogramma met het huidige document als bijlage. De huidige
bestandsindeling wordt gebruikt. Als het document nieuw en
niet-opgeslagen is, wordt de indeling gespecificeerd in % PRODUCTNAME -
VoorkeurenExtra -
Opties - Laden / Opslaan -
Algemeen wordt gebruikt."
helpcontent2/source/text/shared/01.po:47852:msgstr "De huidige implementatie (%
PRODUCTNAME% PRODUCTVERSION) van de enkelvoudige werkbalk is gemeenschappelijk
voor de modules Writer, Calc, Draw en Impress. Een wijziging in de enkelvoudige
werkbalk in de ene module heeft invloed op de enkelvoudige werkbalk van de
andere modules."
helpcontent2/source/text/shared/01.po:49841:msgstr "De te gebruiken
sleutelopslag kan worden geselecteerd onder % PRODUCTNAME -
Voorkeuren Extra -
Opties -% PRODUCTNAAM -
Beveiliging - Certificeringspad."
helpcontent2/source/text/shared/01.po:50642:msgstr "Indien
ingeschakeld, worden automatisch ingevoegde blanco pagina's geëxporteerd naar
het pdf-bestand. Dit is het beste als u het pdf-bestand dubbelzijdig afdrukt.
Voorbeeld: in een boek is een alinea-opmaakprofiel voor hoofdstukken ingesteld
om altijd te beginnen met een oneven genummerde pagina. Als het vorige
hoofdstuk op een oneven pagina eindigt, voegt % PRODUCTNAME een even genummerde
blanco pagina in. Deze optie bepaalt of die even genummerde pagina moet worden
geëxporteerd of niet."
helpcontent2/source/text/shared/01.po:52163:msgstr "Met % PRODUCTNAME kunt u
een ondertekeningsregel in uw document digitaal ondertekenen."
helpcontent2/source/text/shared/01.po:52172:msgstr "Bij het ondertekenen van
een ondertekening-regel vult % PRODUCTNAME de regel met de naam van de
ondertekenaar, voegt de informatie van de uitgever van het digitale certificaat
toe en voegt optioneel de datum van ondertekening in."
helpcontent2/source/text/shared/optionen.po:6533:msgstr "Dit besturingselement
wordt alleen weergegeven als Complexe tekstlay-out is ingesteld in
% PRODUCTNAME
- VoorkeurenExtra -
Opties - Taalinstellingen -
Talen."
helpcontent2/source/text/smath/01.po:13832:msgstr "Het primaire doel van%
PRODUCTNAME Math is om wiskundige formules te maken, maar het kan ook worden
gebruikt om chemische formules te schrijven. In chemische formules worden de
chemische symbolen normaal gesproken in hoofdletters geschreven met
rechtopstaande in plaats van cursieve tekens."
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42082] [META] Make LibreOffice shine and glow on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=42082 Sierk Bornemann changed: What|Removed |Added Depends on||82115 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=82115 [Bug 82115] Repeatable crash/hang entering Japanese into a Writer comment on OSX ( see comment 4 ) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152402] Prints dark background instead of white with custom dark settings
https://bugs.documentfoundation.org/show_bug.cgi?id=152402 --- Comment #2 from nopainenogai...@hushmail.com --- Created attachment 184028 --> https://bugs.documentfoundation.org/attachment.cgi?id=184028&action=edit sample document in print preview -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152406] macOS Calc: Scrolling: scrollbar showing wrong position resulting in unscrollable document
https://bugs.documentfoundation.org/show_bug.cgi?id=152406 --- Comment #1 from steve --- Created attachment 184027 --> https://bugs.documentfoundation.org/attachment.cgi?id=184027&action=edit scrollbar has wrong position resulting in stuck document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152406] New: macOS Calc: Scrolling: scrollbar showing wrong position resulting in unscrollable document
https://bugs.documentfoundation.org/show_bug.cgi?id=152406 Bug ID: 152406 Summary: macOS Calc: Scrolling: scrollbar showing wrong position resulting in unscrollable document Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: l...@disr.it Description: Sadly no clear repro steps but for me it happens after scrolling around in a blank document for a while. Issue: scrollbar is stuck at the top most (y) or left most (x) position despite the document not been on the first row or first column. Once this happens scrolling in the axis showing the wrong scrollbar position is locked e.g. when y scrollbar is affected document can no longer be scrolled to top. LibreOffice seems to assume the scrollbar position (at the very top) to be correct (it actually is not, since the document is not scrolled to the top). This issue can be worked around by scrolling up and down (or sideways) for a while into the sidebar snaps into correct position which then results in a correctly scrollable document again. The issue can affect both horizontal and verital scrollbar. I have not observed both scrollbars misbehaving at the same time, although both are affected by this issue and have misbehaved in described way. Steps to Reproduce: If only I knew. Scrolling around for a while in a new calc document should be sufficient to trigger the issue after under 1 minute. Actual Results: Unscrollable document Expected Results: Scrollbars should never show wrong position and by that prevent document getting stuck on wrong position. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: c08e5db055c9d34d3f0b0b9d2a192d7ebdcd9576 CPU threads: 8; OS: Mac OS X 13.0.1; UI render: default; VCL: osx Locale: de-DE (en_DE.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118017] [META] macOS Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=118017 steve changed: What|Removed |Added Depends on||152405 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152405 [Bug 152405] macOS Dark Mode: white text on while background in various UI elements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152405] macOS Dark Mode: white text on while background in various UI elements
https://bugs.documentfoundation.org/show_bug.cgi?id=152405 steve changed: What|Removed |Added Blocks||118017 CC||caol...@redhat.com, ||mikekagan...@hotmail.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=118017 [Bug 118017] [META] macOS Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152405] macOS Dark Mode: white text on while background in various UI elements
https://bugs.documentfoundation.org/show_bug.cgi?id=152405 --- Comment #2 from steve --- Created attachment 184026 --> https://bugs.documentfoundation.org/attachment.cgi?id=184026&action=edit fontname size and cellname - white text on white background -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152405] macOS Dark Mode: white text on while background in various UI elements
https://bugs.documentfoundation.org/show_bug.cgi?id=152405 --- Comment #1 from steve --- Created attachment 184025 --> https://bugs.documentfoundation.org/attachment.cgi?id=184025&action=edit buttons white text on white background -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152405] New: macOS Dark Mode: white text on while background in various UI elements
https://bugs.documentfoundation.org/show_bug.cgi?id=152405 Bug ID: 152405 Summary: macOS Dark Mode: white text on while background in various UI elements Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: l...@disr.it Description: Sadly I have no clear repro steps for this and it happens infrequently but often enough that I now file this issue. Once the issue hits, several UI elements change to white text on white background which before were displayed as expected. Find attached screenshots shows the issue happen in Calc for Fontname, Fontsize and Cellname dropdown. And a second screenshot showing the save dialog buttons misbehaving in the same way. Steps to Reproduce: If only I knew :( Actual Results: Fields and buttons become hard to use and unreadable. Expected Results: Buttons and fields should not switch to white text on white background. Reproducible: Couldn't Reproduce User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: c08e5db055c9d34d3f0b0b9d2a192d7ebdcd9576 CPU threads: 8; OS: Mac OS X 13.0.1; UI render: default; VCL: osx Locale: de-DE (en_DE.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152404] Crash in Writer when inserting a new comment while there is uncommitted text
https://bugs.documentfoundation.org/show_bug.cgi?id=152404 --- Comment #1 from Patrick Luby --- One more detail: if, in step 4, you select the Insert > Comment menu item, the crash does not occur and uncommitted text is committed and the cursor moves to the new comment. So, it appears that selecting a menu item commits the text before the new comment is created but pressing a shortcut that contains the Control key bypasses the commit process. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152404] New: Crash in Writer when inserting a new comment while there is uncommitted text
https://bugs.documentfoundation.org/show_bug.cgi?id=152404 Bug ID: 152404 Summary: Crash in Writer when inserting a new comment while there is uncommitted text Product: LibreOffice Version: 7.5.0.0 alpha1+ Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: plub...@neooffice.org Description: After some debugging, I found that the crash occurs when the new comment grabs focus, it invokes WinSalFrame::EndExtTextInput() which is supposed to commit the uncommitted text. Unfortunately, Writer's input method handler commits the text in two steps: first it deletes the uncommitted text, then it inserts the committed text. The crash occurs in the first step: when Writer deletes the uncommitted text, it triggers Writer to remove the newly added comment and the comment's vcl objects are all deleted. Steps to Reproduce: Steps to reproduce. Note: this crash occurs in Windows but not macOS since macOS has not yet implemented SalFrame::EndExtTextInput(): 1. Open a new Writer document 2. Change your keyboard entry to a Chinese, Japanese, or Korean input method (I used Japanese Hiragana) 3. Type a few characters so that the text is in an uncommitted state (I typed "aaa" on a US English physical keyboard which get converted to "あああ" by the Japanese Hiragana input method) 4. Press the Control-Alt-C keys to create a new comment 5. Crash Actual Results: Application crashes due to use of a deleted pointer. Expected Results: Uncommitted text should be committed and the cursor moved to the new comment. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: c08e5db055c9d34d3f0b0b9d2a192d7ebdcd9576 CPU threads: 1; OS: Windows 10.0 Build 19045; 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 55571] [META] ACCESSIBILITY: Tracking bug for issues related to the macOS Accessibility API
https://bugs.documentfoundation.org/show_bug.cgi?id=55571 steve changed: What|Removed |Added Severity|critical|normal --- Comment #29 from steve --- Lowering importance to normal. This is a meta bug. If there is a critical bug, it should be the individual bug, not this meta bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152402] Prints dark background instead of white with custom dark settings
https://bugs.documentfoundation.org/show_bug.cgi?id=152402 --- Comment #1 from steve --- Unable to reproduce on macOS with daily build. Are you seeing the dark area you are referring to in print preview? If yes, could you attach a screenshot of that please. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152397] The explanation of the help page about Calc Input settings is not appropriate.
https://bugs.documentfoundation.org/show_bug.cgi?id=152397 --- Comment #2 from nobu --- (In reply to Olivier Hallot from comment #1) > Does this makes it clearer? > > "If a range of cells is selected, each time Enter is > pressed will select the next cell inside the range, according to the > direction selected in Press Enter to move selection. Hence, > enabling both options is useful when entering values into a range of cells > sequentially." I rely on Google's automatic translation to post and read, so it's difficult to judge whether this sentence is easy to understand, but I think it's a correct description. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 82115] Repeatable crash/hang entering Japanese into a Writer comment on OSX ( see comment 4 )
https://bugs.documentfoundation.org/show_bug.cgi?id=82115 Patrick Luby changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |plub...@neooffice.org |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 82115] Repeatable crash/hang entering Japanese into a Writer comment on OSX ( see comment 4 )
https://bugs.documentfoundation.org/show_bug.cgi?id=82115 --- Comment #21 from Patrick Luby --- I have posted a patch that fixes this bug: https://gerrit.libreoffice.org/c/core/+/143619 The patch needs still needs to be reviewed and tested before it appears in a nightly build. Are there any people who have a macOS LibreOffice build that can test the patch? Overall, the patch commits any uncommitted text when one or more of the following events occur: - The focused window changes - A menu item is selected - Text is entered with the Command key pressed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143480] Writer: In Navigator, promotion or demotion of a level should change heading level in document
https://bugs.documentfoundation.org/show_bug.cgi?id=143480 --- Comment #9 from Paul --- Created attachment 184024 --> https://bugs.documentfoundation.org/attachment.cgi?id=184024&action=edit File with Navigator promotion problem Here is the sanitized file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143480] Writer: In Navigator, promotion or demotion of a level should change heading level in document
https://bugs.documentfoundation.org/show_bug.cgi?id=143480 --- Comment #8 from Paul --- (In reply to Dieter from comment #7) > (In reply to Buovjaga from comment #6) > > Paul: you closed this as insufficientdata. Does this mean you have not been > > able to sanitize the document? If so, you can send it to me via email and I > > can give it a shot (confirming with you before attaching it to the report). > > => NEEDINFO Thanks guys, I appreciate your attention greatly. I have made a screencast of the problem, using the actual problem file. In doing so, I have narrowed down the extent of the problem. In Navigator, using the toolbar arrows to promote a heading up or demote it down works fine. However, using the toolbar arrows to promote left or demote right, while it works in that it affects a Table of Contents refresh, never is reflected in the LO toolbar Style combo box item. That is, if I take an H4 heading down to H5, it shows as H5 in a refreshed ToC, but stays as H4 in the toolbar box. Here is the video: https://videy.co/v?id=H6Lde88p I will try to sanitize the file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152134] Customize: assign user macro to menu fails and hangs LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=152134 --- Comment #22 from wzpd...@gmail.com --- Stephane, thanks for the help. Have moved to v7.3.7.2 and can confirm that version works. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152134] Customize: assign user macro to menu fails and hangs LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=152134 --- Comment #21 from wzpd...@gmail.com --- Sorry, names are similar and I was asleep at the switch. Thanks for the help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143480] Writer: In Navigator, promotion or demotion of a level should change heading level in document
https://bugs.documentfoundation.org/show_bug.cgi?id=143480 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #7 from Dieter --- (In reply to Buovjaga from comment #6) > Paul: you closed this as insufficientdata. Does this mean you have not been > able to sanitize the document? If so, you can send it to me via email and I > can give it a shot (confirming with you before attaching it to the report). => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152029] Visually draw attention to in-view bookmark or hyperlink when selecting/hovering it in the Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=152029 --- Comment #24 from Commit Notification --- Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/3cb654972ba204efb5dd35a44f95c7d509414400 tdf#152029 Visually draw attention to in-view bookmark It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152029] Visually draw attention to in-view bookmark or hyperlink when selecting/hovering it in the Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=152029 Commit Notification changed: What|Removed |Added Whiteboard||target:7.5.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152381] sal_Int32 comphelper::date::YearToDays(sal_Int16): Assertion `nYear != 0' failed.
https://bugs.documentfoundation.org/show_bug.cgi?id=152381 Eike Rathke changed: What|Removed |Added Status|NEW |ASSIGNED OS|Linux (All) |All Assignee|libreoffice-b...@lists.free |er...@redhat.com |desktop.org | Hardware|x86-64 (AMD64) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103378 خالد حسني changed: What|Removed |Added Depends on|152396 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152396 [Bug 152396] Font width (expanded, condensed, etc.) is not supported -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152396] Font width (expanded, condensed, etc.) is not supported
https://bugs.documentfoundation.org/show_bug.cgi?id=152396 خالد حسني changed: What|Removed |Added Blocks|103378 | Summary|Variable font: variants are |Font width (expanded, |not correctly selected |condensed, etc.) is not ||supported Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103378 [Bug 103378] [META] PDF export bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152403] New: Missing space on credits list of video *LibreOffice 7.4: New Features*
https://bugs.documentfoundation.org/show_bug.cgi?id=152403 Bug ID: 152403 Summary: Missing space on credits list of video *LibreOffice 7.4: New Features* Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: pmenzel+bugs.documentfoundation@molgen.mpg.de CC: olivier.hal...@libreoffice.org In the video [*LibreOffice 7.4: New Features*](https://www.youtube.com/watch?v=PC8M4UzqpqE) – also on https://www.libreoffice.org/discover/new-features/ (with PeerTube). On the credits “slide” a space is missing before Attila Bakos. It’d be great, if you rerendered the video and uploaded the improved version. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152396] Variable font: variants are not correctly selected
https://bugs.documentfoundation.org/show_bug.cgi?id=152396 --- Comment #4 from خالد حسني --- I tried to debug this and now I’m very skeptical that font width ever worked, it seems to be ignored left and right. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94524] Add option to remove trailing spaces in the Basic IDE
https://bugs.documentfoundation.org/show_bug.cgi?id=94524 Rafael Lima changed: What|Removed |Added Summary|IDE (Integrated Development |Add option to remove |Environment) Removing |trailing spaces in the |tailing spaces/tabs |Basic IDE Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94524] IDE (Integrated Development Environment) Removing tailing spaces/tabs
https://bugs.documentfoundation.org/show_bug.cgi?id=94524 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #3 from Rafael Lima --- We could have an option in the Edit menu named "Remove all trailing spaces". When the user clicks this command, it will remove all trailing spaces in the currently open module. This way, we wouldn't need to create a new setting. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113108] [META] Dialog UI/UX bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113108 Bug 113108 depends on bug 62948, which changed state. Bug 62948 Summary: IDE Object catalog: Enter does not openen a selected module/function https://bugs.documentfoundation.org/show_bug.cgi?id=62948 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 62948] IDE Object catalog: Enter does not openen a selected module/function
https://bugs.documentfoundation.org/show_bug.cgi?id=62948 Rafael Lima changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME CC||rafael.palma.l...@gmail.com --- Comment #4 from Rafael Lima --- I just tried this today and Enter opens the selected module in the Object Catalog. Tested with Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 1:7.4.2~rc3-0ubuntu1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152381] sal_Int32 comphelper::date::YearToDays(sal_Int16): Assertion `nYear != 0' failed.
https://bugs.documentfoundation.org/show_bug.cgi?id=152381 --- Comment #2 from Eike Rathke --- Sure, if code sets/uses a date with year 0 (or even day=0,month=0,year=0 in this case) for the proleptic Gregorian calendar then that code is wrong ;-) That so far didn't matter because the Base code had its own and wrong conversion. Problem here seems to be a NULL value of the database that is *not* a date to be converted to relative days, entering connectivity/source/commontools/dbconversion.cxx dbtools::DBTypeConversion::toDouble() with _rVal all 0 then via dbtools::DBTypeConversion::toDays() dbtools::implRelativeToAbsoluteNull() calls the now new comphelper::date::convertDateToDaysNormalizing() that via its calls asserts. The old dbtools::implRelativeToAbsoluteNull() implementation for day=0,month=0,year=0 returned -365 for that "date", which is completely off. Whatever the old now eliminated dbtools::implBuildFromRelative() did for such.. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152392] Elements sidebar font in system dark mode lacks contrast: black on grey
https://bugs.documentfoundation.org/show_bug.cgi?id=152392 Caolán McNamara changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #4 from Caolán McNamara --- I can reproduce -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152402] New: Prints dark background instead of white with custom dark settings
https://bugs.documentfoundation.org/show_bug.cgi?id=152402 Bug ID: 152402 Summary: Prints dark background instead of white with custom dark settings Product: LibreOffice Version: 7.3.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nopainenogai...@hushmail.com Description: The same settings in version 7 do not work as in version 6 of Libreoffice Writer. Dark settings while typing are a must but the printer prints the page dark instead of it remaining white. Not usable this way. Steps to Reproduce: 1.The steps to create dark mode--only affects top part of document 2.changing the doc to dark 3.I uninstalled LO, hoping to reinstall version 6 and find that not possible. I cannot be more specific. Actual Results: The printer prints the dark background instead of a white background, as in version 6. Expected Results: I expected to see a white paper printed with black type. Reproducible: Always User Profile Reset: No Additional Info: I already uninstalled LO, hoping to reinstall version 6. Don't have that now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152396] Variable font: variants are not correctly selected
https://bugs.documentfoundation.org/show_bug.cgi?id=152396 خالد حسني changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from خالد حسني --- It does not seem to be a variable font issue, rather it seems that LibreOffice is failing to use the width variants at all, i.e. the width is always ignored. If you install the static fonts you get the same issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152393] configmgr and vcl warnings in Math since version 7.5
https://bugs.documentfoundation.org/show_bug.cgi?id=152393 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- @stragu, any chance it is related to recent 9939ffb9b87e536b3217232b732218e82126ad6c for bug 151842? Reverting a chunk of work around https://gerrit.libreoffice.org/c/core/+/120753 Quick to tell by simply checking if it is throwing the errors on nightlys from before 2022-12-01? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102019] [META] Dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102019 Bug 102019 depends on bug 122254, which changed state. Bug 122254 Summary: LO Impress Presentation minimizer: Text at the 3rd line is cut in the final message https://bugs.documentfoundation.org/show_bug.cgi?id=122254 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122254] LO Impress Presentation minimizer: Text at the 3rd line is cut in the final message
https://bugs.documentfoundation.org/show_bug.cgi?id=122254 Caolán McNamara changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152392] Elements sidebar font in system dark mode lacks contrast: black on grey
https://bugs.documentfoundation.org/show_bug.cgi?id=152392 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #3 from V Stuart Foote --- No issue with Elements deck on Windows builds in os/DE 'Dark' color theme. fg of each element/example is the White of the formula canvas, good contrast to the bg. Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: c50cf1883af26daebdfc9d796ced3c20c222f43b CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103182 Bug 103182 depends on bug 121297, which changed state. Bug 121297 Summary: LO Impress: "JPG Quality" overlapping with "Reduce image resolution" in Presentation Minimizer Wizard in some GTK3 https://bugs.documentfoundation.org/show_bug.cgi?id=121297 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- 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||152397 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152397 [Bug 152397] The explanation of the help page about Calc Input settings is not appropriate. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152397] The explanation of the help page about Calc Input settings is not appropriate.
https://bugs.documentfoundation.org/show_bug.cgi?id=152397 Olivier Hallot changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Blocks||80430 --- Comment #1 from Olivier Hallot --- Does this makes it clearer? "If a range of cells is selected, each time Enter is pressed will select the next cell inside the range, according to the direction selected in Press Enter to move selection. Hence, enabling both options is useful when entering values into a range of cells sequentially." 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 102985] [META] Font bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102985 V Stuart Foote changed: What|Removed |Added Depends on||152396 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152396 [Bug 152396] Variable font: variants are not correctly selected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103378 V Stuart Foote changed: What|Removed |Added Depends on||152396 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152396 [Bug 152396] Variable font: variants are not correctly selected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152396] Variable font: variants are not correctly selected
https://bugs.documentfoundation.org/show_bug.cgi?id=152396 V Stuart Foote changed: What|Removed |Added Blocks||103378, 102985 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102985 [Bug 102985] [META] Font bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=103378 [Bug 103378] [META] PDF export bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152396] Variable font: variants are not correctly selected
https://bugs.documentfoundation.org/show_bug.cgi?id=152396 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=10 ||8497 CC||kha...@aliftype.com, ||vsfo...@libreoffice.org --- Comment #2 from V Stuart Foote --- I'm sure خالد will comment, but I think https://gerrit.libreoffice.org/c/core/+/142028 was an incremental handling of variable fonts until (or even if) more work on HB based instantiation in PDF provides better glyph stamping. The mangled PS font names are there in the PDF, but I don't think we can expect the bitmap glyps to match appearance on VCL canvas yet. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152278] "Unimplemented mac encoding 18432 to unicode conversion"
https://bugs.documentfoundation.org/show_bug.cgi?id=152278 --- Comment #2 from Eyal Rozenberg --- (In reply to Dieter from comment #1) > Eyal, for me your comment doens't look like a bug report Then let me clarify for you: That message should not be printed. Either such conversion needs to happen, in which case the bug is that it's not implemented; or it doesn't need to happen, in which case the bug is that this message is printed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120190] Data "Formula to Value" don't preserve line break with multi-line text value
https://bugs.documentfoundation.org/show_bug.cgi?id=120190 --- Comment #8 from Mike Kaganski --- Repro using Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152343] FORMATTING:
https://bugs.documentfoundation.org/show_bug.cgi?id=152343 jean...@gmail.com changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |NOTABUG --- Comment #2 from jean...@gmail.com --- I swear to god that I spent more than an hour fighting this last Thursday, but after re-installing 7.4.3.2 this morning, it is working the same as 7.3.4.2 did. I apologize for adding to your workload. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152134] Customize: assign user macro to menu fails and hangs LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=152134 Adolfo Jayme Barrientos changed: What|Removed |Added Whiteboard||target:7.5.0 target:7.4.4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147839] Slide View toolbar visible in Tabbed UI in Impress when changing view to Slide Sorter
https://bugs.documentfoundation.org/show_bug.cgi?id=147839 --- Comment #2 from Pedro --- Still present in: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: c50cf1883af26daebdfc9d796ced3c20c222f43b CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: pt-PT (pt_PT); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121076] Can't select/pick multiples lines or items in tables with CTRL key
https://bugs.documentfoundation.org/show_bug.cgi?id=121076 --- Comment #11 from Pedro --- Still present in: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: c50cf1883af26daebdfc9d796ced3c20c222f43b CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: pt-PT (pt_PT); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152277] window/ filter state of styles does not save
https://bugs.documentfoundation.org/show_bug.cgi?id=152277 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||dgp-m...@gmx.de --- Comment #1 from Dieter --- I can't confirm it with Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121967] Can't select/pick multiples shapes or images in Writer/Calc/Impress/Draw with CTRL key
https://bugs.documentfoundation.org/show_bug.cgi?id=121967 --- Comment #42 from Pedro --- Can confirm this still happens in 7.5: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: c50cf1883af26daebdfc9d796ced3c20c222f43b CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: pt-PT (pt_PT); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152278] "Unimplemented mac encoding 18432 to unicode conversion"
https://bugs.documentfoundation.org/show_bug.cgi?id=152278 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de --- Comment #1 from Dieter --- Eyal, for me your comment doens't look like a bug report but like a question for advice. Please use ask.libreoffice.org in such a case. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 53300] Chart: Impossible to choose non-contiguous range when, editing data range with use of the Expand button
https://bugs.documentfoundation.org/show_bug.cgi?id=53300 --- Comment #37 from Pedro --- This was the version I tested: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: c50cf1883af26daebdfc9d796ced3c20c222f43b CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: pt-PT (pt_PT); UI: en-US Calc: threaded Also, could we maybe bump importance of this and the multiple related bugs that involve the use of the Ctrl key? I know this might not be a super-glamorous new feature that excites devs but this a batch of multiple bugs inherited from Open Office that affect UX... -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152395] [Accessibility] LibreOffice Writer immediately crashes when entering characters and VoiceOver is running.
https://bugs.documentfoundation.org/show_bug.cgi?id=152395 --- Comment #7 from Stéphane Guillou (stragu) --- I couldn't reproduce a crash with: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fe845e40ab23a3fa9fd401498edf925b7b00776f CPU threads: 2; OS: Mac OS X 12.6.1; UI render: Skia/Raster; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 2; OS: Mac OS X 12.6.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I also tried with DE locale and UI: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 2; OS: Mac OS X 12.6.1; UI render: default; VCL: osx Locale: de-DE (en_US.UTF-8); UI: de-DE Calc: threaded Marco, do you know what was the latest version you could use without a crash? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152352] Sidebar weird behavior
https://bugs.documentfoundation.org/show_bug.cgi?id=152352 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #3 from Dieter --- I can't confirm it with Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Emu, thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and re-test? => NEEDINFO You can also try it with Skia disabled (Tools -> Options -> LibreOffice -> View) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149110] LibreOffice Base slows down if there is an unsaved change to the databse
https://bugs.documentfoundation.org/show_bug.cgi?id=149110 --- Comment #5 from Robert Großkopf --- (In reply to Dr. Martinus from comment #4) > > And they will tell me to report to LO. I had this problem already long > before I switched to Manjaro. So I don't think it's related to the > distribution. If you couldn't try with original packages and nobody could see the same buggy behavior with original packages it will be impossible to help here. I couldn't confirm the behavior while closing a Base file with an unsaved query. There will appear a message the query hasn't been saved. I will press "Yes". Then another message appears if I want to save the changed database file. I press "Yes" and the database has been closed without any delay. I don't know what other distributions will do while creating packages. But there are Base bugs in openSUSE version (rpm) and identical in Ubuntu version (deb) but this bugs won't appear in the original, which is available as *.deb or *.rpm and could be installed parallel to this versions on the same system. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147800] Master View toolbar visible in Tabbed UI in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=147800 --- Comment #3 from Pedro --- Can confirm it happens still in 7.5: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: c50cf1883af26daebdfc9d796ced3c20c222f43b CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: pt-PT (pt_PT); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 53300] Chart: Impossible to choose non-contiguous range when, editing data range with use of the Expand button
https://bugs.documentfoundation.org/show_bug.cgi?id=53300 --- Comment #36 from Pedro --- Can confirm this still happens in development version for 7.5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81880] Ability to search Gallery for graphics by description
https://bugs.documentfoundation.org/show_bug.cgi?id=81880 --- Comment #13 from Heiko Tietze --- (In reply to V Stuart Foote from comment #12) > Don't see translation of core gallery content as an immediate issue... I mean that as a consequence of the naming. If we assign a variable name to the Gallery objects we could also provide translations. OTOH, if the Gallery comes from the extension all work needs to be done externally, which is rather unlikely. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152396] Variable font: variants are not correctly selected
https://bugs.documentfoundation.org/show_bug.cgi?id=152396 --- Comment #1 from RGB --- Created attachment 184021 --> https://bugs.documentfoundation.org/attachment.cgi?id=184021&action=edit PDF output of a sample documnet using both, the variable and the standard version of Junicode Two Beta In the attached PDF you can see the behavior described in the report. The first three lines show the static versions of Junicode Two Beta in its Condensed, Regular and SemiExpanded variants. The following line show the variable version which LibreOffice label as condensed, independently of which style you select from those indicated between parenthesis. As you can see, the "condensed" from the variable font matches with the SemiExpanded static variant, not with the condensed. The embedded variable font don't show its name in the exported PDF. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152184] macOS: dark mode: Application Colors > Color Scheme should automatically follow System Settings > Appearance
https://bugs.documentfoundation.org/show_bug.cgi?id=152184 --- Comment #10 from Heiko Tietze --- AC consists of ~50 colors while SC is limited to 10. There is no way to completely get rid of it. My take is to follow with AC the SC but allow to edit it. Ideally per extension. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152387] Calc Auto-Filter: duplicate filtering items
https://bugs.documentfoundation.org/show_bug.cgi?id=152387 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #2 from m.a.riosv --- Maybe because some of them have a space at the end of the word. Select the column, Menu/Edit/Find & Replace [Ctrl+H] Search for a space Replace with nothing. Replace All. Now filter looks fine. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152395] [Accessibility] LibreOffice Writer immediately crashes when entering characters and VoiceOver is running.
https://bugs.documentfoundation.org/show_bug.cgi?id=152395 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||needsDevAdvice CC||stephane.guillou@libreoffic ||e.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152388] Librecalc freezes when searching for non-existent text
https://bugs.documentfoundation.org/show_bug.cgi?id=152388 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO --- Comment #1 from m.a.riosv --- I have tested with a 5 rows sheet, and not issue with Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL On one side, 6.4 it's EOL, so no new revisions. Please try with a newer version. https://www.libreoffice.org/download/download-libreoffice/ Or if the issue is only with one file, please attach it here after depersonalizing it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131722] FILEOPEN DOCX Date picker control placeholder texts first character goes out of the control
https://bugs.documentfoundation.org/show_bug.cgi?id=131722 --- Comment #6 from Justin L --- Repro 7.5 master with Date entry-example.docx for the first in-table date, which is a BlockSdt (i.e. the paragraph is inside the contents as opposed to a RunSdt which is inside a paragraph). The second in-table date (which is a RunSdt) was fixed in LO 7.4 with commit 5ee8670f18cb8b1913a23d04590d6a31ac9730de Author: Miklos Vajna on Mon May 30 09:00:25 2022 +0200 sw content controls, date: add DOCX import -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149110] LibreOffice Base slows down if there is an unsaved change to the databse
https://bugs.documentfoundation.org/show_bug.cgi?id=149110 --- Comment #4 from Dr. Martinus --- (In reply to Robert Großkopf from comment #3) > I have never worked with this system. Is it possible to install a *.deb or > *.rpm package on this system? You should try to install the original > packages from LO so we could see if it is a bug from LO. In other Linux > distributions you could install packaged from LO parallel to the version > from the distribution. Have installed here many different *.rpm-versions > (OpenSUSE). rpm or deb can be installed on Manjaro/Arch systems, but that would only go with a workaround, and I don't really feel confident to do that. Installing LO directly from the LO-website has always become trying for me (because it's split in multiple packages and one depends on another and I get always errors because of that). And as far as I know, there are no packages for Arch/Manjaro distribution available, so it would become even more difficult. > If it is impossible to install a package direct from LO: File a bug to > Manjaro. And they will tell me to report to LO. I had this problem already long before I switched to Manjaro. So I don't think it's related to the distribution. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152345] Pivot table - visual FORMATTING mistake after sorting by descending order
https://bugs.documentfoundation.org/show_bug.cgi?id=152345 --- Comment #7 from m.a.riosv --- I guess you are trying to sort with the general sort of calc, not with the pivot table properties. Maybe it doesn't work exactly the same in calc and excel, because calc always restart the format of the PT every time it is updated. But you have an option to update the PT based on result. While in PT, Right-click - Properties - Double-click on Row field 'Description' - Options - Sort by 'Sum Amount' - Descending - Ok - Ok - Ok. -- You are receiving this mail because: You are the assignee for the bug.
