[Libreoffice-bugs] [Bug 141578] Libreoffice unusable with fractional scaling on multimonitor (on kf5/qt5/qt6 vcl + wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=141578 --- Comment #23 from Callegar --- Is the issue related to fractional scaling only? I.e. does integer scaling (i.e. 200%) work correctly? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141578] Libreoffice unusable with fractional scaling on multimonitor (on kf5/qt5/qt6 vcl + wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=141578 Callegar changed: What|Removed |Added Summary|Libreoffice unusable with |Libreoffice unusable with |fractional scaling on |fractional scaling on |multimonitor (on|multimonitor (on |plasma+wayland) |kf5/qt5/qt6 vcl + wayland) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/inc
sc/inc/conditio.hxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 211c4df7656bc81617e98ec89466c12f998a6130
Author: Andrea Gelmini
AuthorDate: Mon Sep 18 19:25:18 2023 +0200
Commit: Julien Nabet
CommitDate: Wed Sep 20 07:28:23 2023 +0200
Fix typo
Change-Id: I1d248f2980292cdbb9f2c3275c4f371b75f1a2f8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157028
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git a/sc/inc/conditio.hxx b/sc/inc/conditio.hxx
index 8e5af1dd3c3c..c3ef00e5cf93 100644
--- a/sc/inc/conditio.hxx
+++ b/sc/inc/conditio.hxx
@@ -614,7 +614,7 @@ class RepaintInIdle final : public Idle
public:
RepaintInIdle(ScConditionalFormat* pCondFormat)
-: Idle("Contitional Format Repaint Idle")
+: Idle("Conditional Format Repaint Idle")
, mpCondFormat(pCondFormat)
{}
[Libreoffice-commits] core.git: 2 commits - sw/qa vcl/jsdialog
vcl/jsdialog/jsdialogbuilder.cxx | 19 --- 1 file changed, 19 deletions(-) New commits: commit 41208b2c46f082814faf721eb84baaf4fc7e9e78 Author: Andrea Gelmini AuthorDate: Mon Sep 18 22:50:57 2023 +0200 Commit: Julien Nabet CommitDate: Wed Sep 20 07:28:07 2023 +0200 Remove duplicated includes Change-Id: Ia76c2a83f5c5e0ea31260dace7bd32763eb4d0e2 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157035 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/vcl/jsdialog/jsdialogbuilder.cxx b/vcl/jsdialog/jsdialogbuilder.cxx index fcabfc67bbbc..ec0c4fec1573 100644 --- a/vcl/jsdialog/jsdialogbuilder.cxx +++ b/vcl/jsdialog/jsdialogbuilder.cxx @@ -29,29 +29,10 @@ #include #include -#include -#include -#include -#include -#include -#include - -#include #include -#include - #include -#include -#include -#include -#include -#include -#include -#include -#include -#include #include static std::map& GetLOKPopupsMap() commit db41fbf7224d1d1dd1ef2d7f2ac0dd005d6367be Author: Andrea Gelmini AuthorDate: Tue Sep 19 23:42:58 2023 +0200 Commit: Julien Nabet CommitDate: Wed Sep 20 07:27:55 2023 +0200 Remove executable bits on odt file Change-Id: Ie7ee5bc7586835f65eae7275f2cfc1d86a2cbbdc Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157091 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/sw/qa/extras/uiwriter/data/testTdf106663.odt b/sw/qa/extras/uiwriter/data/testTdf106663.odt old mode 100755 new mode 100644
[Libreoffice-bugs] [Bug 157074] Program freeze when editing graphics, saving file
https://bugs.documentfoundation.org/show_bug.cgi?id=157074 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #10 from Buovjaga --- Do you happen to use Windows Speech Recognition? It recently came up that it can cause severe performance problems. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88388] CALC is not exporting ODS graphs to XLS, XLT and UOS correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=88388 --- Comment #17 from Carlos Roberto --- Hello QA team, I am back. Yes, It still persist on XLS, XLT and UOS. Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: pt-BR (pt_BR); UI: pt-BR Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157222] The info texts of EndGluePointIndex and EndPosition are exchanged
https://bugs.documentfoundation.org/show_bug.cgi?id=157222 --- Comment #1 from taniyuki --- The fishing game is simple, easy to play and very entertaining https://tinyfishing.co -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157100] FILEOPEN DOC Group object is placed in horizontally incorrect position
https://bugs.documentfoundation.org/show_bug.cgi?id=157100 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 157108] "New Style From Selection" for Frames does not seem to copy properties
https://bugs.documentfoundation.org/show_bug.cgi?id=157108 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 157095] Content control opens "Review fields" dialog box instead of inline editing
https://bugs.documentfoundation.org/show_bug.cgi?id=157095 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 157071] Calc - Hyperlink to hidden sheet bringing to closest un-hidden sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=157071 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 153734] Writer freezes on enabling new adobe font
https://bugs.documentfoundation.org/show_bug.cgi?id=153734 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 153734] Writer freezes on enabling new adobe font
https://bugs.documentfoundation.org/show_bug.cgi?id=153734 --- Comment #3 from QA Administrators --- Dear johann-nikolaus, 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 153723] spell check
https://bugs.documentfoundation.org/show_bug.cgi?id=153723 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 153723] spell check
https://bugs.documentfoundation.org/show_bug.cgi?id=153723 --- Comment #3 from QA Administrators --- Dear Neil, 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 153715] Calc:Formatting, Insert comment makes font toolbar disappear.
https://bugs.documentfoundation.org/show_bug.cgi?id=153715 --- Comment #4 from QA Administrators --- Dear irontopp18, 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 153715] Calc:Formatting, Insert comment makes font toolbar disappear.
https://bugs.documentfoundation.org/show_bug.cgi?id=153715 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 153697] Suddenly close
https://bugs.documentfoundation.org/show_bug.cgi?id=153697 --- Comment #3 from QA Administrators --- Dear taekue.dragon, 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 153697] Suddenly close
https://bugs.documentfoundation.org/show_bug.cgi?id=153697 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 109239] [META] CSV / TSV / Text Import and export / Text to Columns dialogs bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109239 Bug 109239 depends on bug 153072, which changed state. Bug 153072 Summary: LibreOffice calc Text import does not display imported data preview: QPainter error "painter not active" https://bugs.documentfoundation.org/show_bug.cgi?id=153072 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE (kf5) VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Bug 102495 depends on bug 153072, which changed state. Bug 153072 Summary: LibreOffice calc Text import does not display imported data preview: QPainter error "painter not active" https://bugs.documentfoundation.org/show_bug.cgi?id=153072 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153072] LibreOffice calc Text import does not display imported data preview: QPainter error "painter not active"
https://bugs.documentfoundation.org/show_bug.cgi?id=153072 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 153072] LibreOffice calc Text import does not display imported data preview: QPainter error "painter not active"
https://bugs.documentfoundation.org/show_bug.cgi?id=153072 --- Comment #12 from QA Administrators --- Dear Jiří Rohlíček, 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 151200] LibreOffice freezes when opening the SAVE dialog in a Text Document in Mac
https://bugs.documentfoundation.org/show_bug.cgi?id=151200 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 151200] LibreOffice freezes when opening the SAVE dialog in a Text Document in Mac
https://bugs.documentfoundation.org/show_bug.cgi?id=151200 --- Comment #8 from QA Administrators --- Dear Steve Wilson, 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 147274] Listboxes corners don't update with dark and lightmode
https://bugs.documentfoundation.org/show_bug.cgi?id=147274 --- Comment #8 from QA Administrators --- Dear jr.om, 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 154336] libvisio: Traditional Chinese characters in text box displayed unproperly
https://bugs.documentfoundation.org/show_bug.cgi?id=154336 --- Comment #4 from QA Administrators --- Dear Hsiao, 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 154325] In Calc forgots the diferent fontsize of empty paragraphs inside the same cell.
https://bugs.documentfoundation.org/show_bug.cgi?id=154325 --- Comment #2 from QA Administrators --- Dear Luís Mendes, 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 153303] Window flickers (content shifts) on every key press when having opened multiple windows of a document
https://bugs.documentfoundation.org/show_bug.cgi?id=153303 --- Comment #4 from QA Administrators --- Dear Ulrich Windl, 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 154207] Application crash
https://bugs.documentfoundation.org/show_bug.cgi?id=154207 --- Comment #2 from QA Administrators --- Dear Eduardo, 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 152946] when sidebar is wider that some value, most of the final row of widgets is lost below the sidebar border, and is unreadable (but not necessarily unusable)
https://bugs.documentfoundation.org/show_bug.cgi?id=152946 --- Comment #3 from QA Administrators --- Dear xaxazak, 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 89863] Calc: Long captions in chart are out of background - option should choose just the beginning or break text
https://bugs.documentfoundation.org/show_bug.cgi?id=89863 --- Comment #14 from QA Administrators --- Dear Andy, 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 150663] Crash in: google_breakpad::ExceptionHandler::HandlePureVirtualCall()
https://bugs.documentfoundation.org/show_bug.cgi?id=150663 --- Comment #4 from QA Administrators --- Dear Faisal, 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 88388] CALC is not exporting ODS graphs to XLS, XLT and UOS correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=88388 --- Comment #16 from QA Administrators --- Dear Carlos Roberto, 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 67116] Macros: RemoveByName with IDE Code Window open cause program flow termination
https://bugs.documentfoundation.org/show_bug.cgi?id=67116 --- Comment #11 from QA Administrators --- Dear irs, 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 51925] [BASIC] Writer Table getColumns().getByIndex(i) returns null, where it should not
https://bugs.documentfoundation.org/show_bug.cgi?id=51925 --- Comment #14 from QA Administrators --- Dear Olivier Hallot, 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 47214] LINE INPUT is not recognized after a colon
https://bugs.documentfoundation.org/show_bug.cgi?id=47214 --- Comment #16 from QA Administrators --- Dear rifford, 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 49994] TABLES : jumps on selecting text in table in big cell on neighboring pages
https://bugs.documentfoundation.org/show_bug.cgi?id=49994 --- Comment #11 from QA Administrators --- Dear Palagichev, 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 47876] Macro error when loading spreadsheet (works in MSoffice)
https://bugs.documentfoundation.org/show_bug.cgi?id=47876 --- Comment #11 from QA Administrators --- Dear Chris Martin, 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 42796] Macro assigned to dataform Before Unload or While Unloading events are not called when form container is closed
https://bugs.documentfoundation.org/show_bug.cgi?id=42796 --- Comment #8 from QA Administrators --- Dear Jurgen, 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 38450] XMouseClickHandler Fails To Fire Event When a Sheet Has been "Frozen"
https://bugs.documentfoundation.org/show_bug.cgi?id=38450 --- Comment #13 from QA Administrators --- Dear gn_phelps, 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 36210] disable "Insert" command impossible through dispatch framework
https://bugs.documentfoundation.org/show_bug.cgi?id=36210 --- Comment #17 from QA Administrators --- Dear Laurent Godard, 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 142947] Make menu expander triangles configurable for icon design
https://bugs.documentfoundation.org/show_bug.cgi?id=142947 --- Comment #18 from QA Administrators --- Dear Jérôme, 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 134115] "Allow overlap" in current state is not usable in regard to interoperability with Word
https://bugs.documentfoundation.org/show_bug.cgi?id=134115 --- Comment #9 from QA Administrators --- Dear Regina Henschel, 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 103113] IDE: JavaScript macros is not removed purely from Spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=103113 --- Comment #17 from QA Administrators --- Dear nvyush, 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 119175] Laggy behavior pressing paste (CTRL+V) repeatedly in a document containing a large amount of comments
https://bugs.documentfoundation.org/show_bug.cgi?id=119175 --- Comment #7 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 119446] Form controls Design Mode impacts speed
https://bugs.documentfoundation.org/show_bug.cgi?id=119446 --- Comment #4 from QA Administrators --- Dear matti.jaatinen, 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 112038] when importing docx, formula are created at default font size
https://bugs.documentfoundation.org/show_bug.cgi?id=112038 --- Comment #6 from QA Administrators --- Dear john, 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 103610] [META] Slide show (presentation mode) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103610 Bug 103610 depends on bug 150102, which changed state. Bug 150102 Summary: LibreOffice Impress has white line on bottom and right edge of projection monitor https://bugs.documentfoundation.org/show_bug.cgi?id=150102 What|Removed |Added Status|VERIFIED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152245] Crash with copy-paste from Calc to Writer table with tracked changes
https://bugs.documentfoundation.org/show_bug.cgi?id=152245 --- Comment #8 from noblekeon --- László Németh pushed a fix for this problem. It's now on the "libreoffice-7-5" release train: https://git.libreoffice.org/core/commit/61312cb3ec89730e23ae90a86381e71a94c7d297 https://wordletoday.io/ Tracking changes from Calc to Writer (tdf#152245) In version 7.5.0.2, it will be accessible. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157089] Support mixed column/row references like in Google Sheets like =SUM(A1:3)
https://bugs.documentfoundation.org/show_bug.cgi?id=157089 --- Comment #9 from ady --- (In reply to Eike Rathke from comment #8) > Note that definition is in the global schema definition. That definition to > me is ambiguous and quite certainly did not want to say that one could mix > the notations of cell range addresses and entire column or row range > addresses. It likely is wrong worded and instead of > "a row address is the same as a cell address" > should read > "a row address is the same as a cell range address" > and then "except the alphabetic values that indicate the column are omitted" > actually would make sense. Similar for column address. @Regina, I guess that if the current wording needs a revision, then it would be wise to propose an improvement (be)for(e) the future ODF 1.4. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157342] Delete menu item in Master Navigator popup menu should be disabled when no entry is selected
https://bugs.documentfoundation.org/show_bug.cgi?id=157342 --- Comment #1 from Jim Raykowski --- (In reply to Jim Raykowski from comment #0) > Steps to repro: > > 1. Open a new Master document. (Menu->File->New->Master Document or Ctrl+N) > 2. Right-click in the Navigator content area. > > Result: A popup menu is displayed showing Update and Delete menu items. > > Expected result: The Delete menu item is disabled when there are no entries > selected. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 80a24870491385ba145757bf517c5f1cf7939017 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148959] Calc: Transparency of axis font not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=148959 Kira Tubo changed: What|Removed |Added CC||vmik...@collabora.com Keywords|bibisectRequest |bibisected, bisected --- Comment #5 from Kira Tubo --- Bibisected win64-7.0 repository. Added Miklos Vajna to cc. Regression occurring at: https://git.libreoffice.org/core/+/b4554b8eddd048532269df610e89ae739c46fab7 Seems that this occurred when Transparency was implemented into the UI for the X/Y Axis menu. I was able to reproduce consistently following OP's steps. In relation to Comment 2, it seems consistently reproducible with the following: 1. Create new calc doc 2. Add sample data 3. Insert chart 4. Edit x-axis 5. Set Font Color = Automatic (this is the default) 6. Set Transparency = 100% 7. Click OK OR 1. Repeat steps 1-4 above 2. Change Font Color to any color other than Automatic or White 3. Set Transparency = 100% 4. Click OK 5. Edit x-axis 6. Change Font Color to any color other than Automatic or White (Transparency should already be at 100%) 7. Click OK. -- commit b4554b8eddd048532269df610e89ae739c46fab7[log] author Miklos Vajna Fri Nov 22 17:12:04 2019 +0100 committer Miklos Vajna Fri Nov 22 18:33:39 2019 +0100 treec373507b685e09ae4f2253274f9175f291650c0d parent e227d96bbc500afd810064eee64175b800bfc11f [diff] commit 6da9a6f9bb1b6d95becb71de7d68d326136562f2 Author: Norbert Thiebaud Date: Tue Nov 26 15:54:19 2019 -0800 source sha:b4554b8eddd048532269df610e89ae739c46fab7 - Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 36163d269bd8f77a86605e4c5ff5adce17b4c66c CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; 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 157342] New: Delete menu item in Master Navigator popup menu should be disabled when no entry is selected
https://bugs.documentfoundation.org/show_bug.cgi?id=157342 Bug ID: 157342 Summary: Delete menu item in Master Navigator popup menu should be disabled when no entry is selected Product: LibreOffice Version: 4.0.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rayk...@gmail.com Steps to repro: 1. Open a new Master document. (Menu->File->New->Master Document or Ctrl+N) 2. Right-click in the Navigator content area. Result: A popup menu is displayed showing Update and Delete menu items. Expected result: The Delete menu item is disabled when there are no entries selected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156383] enhancement: customized height of cells
https://bugs.documentfoundation.org/show_bug.cgi?id=156383 --- Comment #4 from ksso --- now, if you select a row and check "no borders", the row changes its height, and this change cannot be undone, neither by removing the style, nor by copying the style of another row into the altered row, (only Ctrl Z, but then if it isn't consecutive commands you need to delete rows in order to make an acceptable table) nor by changing the paragraph style by the way, where is located or the route to "Fit to Size" command? Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156383] enhancement: customized height of cells
https://bugs.documentfoundation.org/show_bug.cgi?id=156383 --- Comment #3 from ksso --- Created attachment 189708 --> https://bugs.documentfoundation.org/attachment.cgi?id=189708=edit can not undo the change on the row height can not undo the change on the row height (even with no border selection) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157341] various lines with character style 90° degrees
https://bugs.documentfoundation.org/show_bug.cgi?id=157341 --- Comment #2 from ksso --- Created attachment 189707 --> https://bugs.documentfoundation.org/attachment.cgi?id=189707=edit command command selected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157341] various lines with character style 90° degrees
https://bugs.documentfoundation.org/show_bug.cgi?id=157341 --- Comment #1 from ksso --- Created attachment 189706 --> https://bugs.documentfoundation.org/attachment.cgi?id=189706=edit example of result different format when rotating text -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157341] New: various lines with character style 90° degrees
https://bugs.documentfoundation.org/show_bug.cgi?id=157341 Bug ID: 157341 Summary: various lines with character style 90° degrees Product: LibreOffice Version: 7.6.1.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kep...@gmail.com Description: when I use character style, 90° degrees rotation, it does not allow to have multiple lines (all text is forced to a single line), and it is difficult to write new text with that character style (see screenshot). Steps to Reproduce: 1.write several lines (horizontal) 2.now apply character style to read it (vertical 90° degrees) 3.all are flattened in one line Actual Results: text flattened in one line Expected Results: same number of lines when text is rotated Reproducible: Always User Profile Reset: No Additional Info: see pictures -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148959] Calc: Transparency of axis font not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=148959 Kira Tubo changed: What|Removed |Added Version|7.3.2.2 release |7.0.3.1 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148959] Calc: Transparency of axis font not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=148959 Kira Tubo changed: What|Removed |Added Keywords||bibisectRequest, regression -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139923] Unwanted motion for objects during animation
https://bugs.documentfoundation.org/show_bug.cgi?id=139923 Commit Notification changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/source
sw/source/uibase/utlui/glbltree.cxx |9 +
1 file changed, 5 insertions(+), 4 deletions(-)
New commits:
commit 91ca15e3f8ae13b22531745a634459a2d9b4596a
Author: Jim Raykowski
AuthorDate: Sat Sep 16 15:12:42 2023 -0800
Commit: Jim Raykowski
CommitDate: Wed Sep 20 02:35:53 2023 +0200
tdf#139923 Part A: Master Navigator: Fix Insert popup menu
Makes Master Navigator content tree popup menu item 'Insert' submenu
items set sensitivity settings work for SalInstanceMenu.
GtkInstanceMenu doesn't seem to require additional menu declarations
for submenu items to be able to set sensitivity.
Change-Id: Ifec28429927591f80859e3b20765c59374a64faa
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/156980
Tested-by: Jenkins
Reviewed-by: Jim Raykowski
diff --git a/sw/source/uibase/utlui/glbltree.cxx
b/sw/source/uibase/utlui/glbltree.cxx
index 9ce80bf0f3fe..367f9a65dd2a 100644
--- a/sw/source/uibase/utlui/glbltree.cxx
+++ b/sw/source/uibase/utlui/glbltree.cxx
@@ -272,6 +272,7 @@ IMPL_LINK(SwGlobalTree, CommandHdl, const CommandEvent&,
rCEvt, bool)
{
std::unique_ptr
xBuilder(Application::CreateBuilder(m_xTreeView.get(),
"modules/swriter/ui/mastercontextmenu.ui"));
std::unique_ptr xPopup = xBuilder->weld_menu("navmenu");
+std::unique_ptr xSubPopup =
xBuilder->weld_menu("insertmenu");
const MenuEnableFlags nEnableFlags = GetEnableFlags();
@@ -280,10 +281,10 @@ IMPL_LINK(SwGlobalTree, CommandHdl, const CommandEvent&,
rCEvt, bool)
xPopup->set_sensitive("editlink", bool(nEnableFlags &
MenuEnableFlags::EditLink));
//disabling if applicable
-xPopup->set_sensitive("insertindex", bool(nEnableFlags &
MenuEnableFlags::InsertIdx ));
-xPopup->set_sensitive("insertfile", bool(nEnableFlags &
MenuEnableFlags::InsertFile));
-xPopup->set_sensitive("insertnewfile", bool(nEnableFlags &
MenuEnableFlags::InsertFile));
-xPopup->set_sensitive("inserttext", bool(nEnableFlags &
MenuEnableFlags::InsertText));
+xSubPopup->set_sensitive("insertindex", bool(nEnableFlags &
MenuEnableFlags::InsertIdx ));
+xSubPopup->set_sensitive("insertfile", bool(nEnableFlags &
MenuEnableFlags::InsertFile));
+xSubPopup->set_sensitive("insertnewfile", bool(nEnableFlags &
MenuEnableFlags::InsertFile));
+xSubPopup->set_sensitive("inserttext", bool(nEnableFlags &
MenuEnableFlags::InsertText));
xPopup->set_sensitive("update", bool(nEnableFlags &
MenuEnableFlags::Update));
xPopup->set_sensitive("insert", bool(nEnableFlags &
MenuEnableFlags::InsertIdx));
[Libreoffice-bugs] [Bug 151628] Report Builder; The Report Header it's placed below Page Header. Should be above
https://bugs.documentfoundation.org/show_bug.cgi?id=151628 Stéphane Guillou (stragu) changed: What|Removed |Added Component|Extensions |Base CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #3 from Stéphane Guillou (stragu) --- Thank you for the report. Page headers and footers that are repeated on all pages are respectively above and below all page content, and their position is the same on all page – which couldn't be done properly if it was placed below the report header. This is a norm and expected in Writer, so I don't see why it should be different header. If need be, once created, the report can be edited, and the first page given the "First page" style, which will remove the page header and footer while the rest of the report still has them. My take is is "not a bug" but others can confirm. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e472b5b557d2b43b41e488c83db2b188de499610 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149780] Writer pdf serial mail includes data sentences
https://bugs.documentfoundation.org/show_bug.cgi?id=149780 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Stéphane Guillou (stragu) --- Thank you Andreas. Could you please provide an example database and document for others to test? And possibly also a resulting PDF? Please also test in a recent version (7.5 or 7.6) to see if the issue persists. Much appreciated! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155671] Allow edit of F1 keystroke
https://bugs.documentfoundation.org/show_bug.cgi?id=155671 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Summary|E. Request: Allow edit of |Allow edit of F1 keystroke |F1 keystroke| Version|7.0.0.3 release |Inherited From OOo Ever confirmed|0 |1 --- Comment #5 from Stéphane Guillou (stragu) --- Was already the case in OOo 3.3, so inherited. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92416] SIDEBAR: Functions pane improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=92416 Stéphane Guillou (stragu) changed: What|Removed |Added Hardware|Other |All See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||2718 --- Comment #7 from Stéphane Guillou (stragu) --- Just mentioning that bug 122718 was fixed for the upcoming version 24.2, adding a search field to the deck. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157340] On Calc disfonction with keys numbers on keyboard. It's correct only with keypad numbers. I checked with 2 cumputers and it's same problem
https://bugs.documentfoundation.org/show_bug.cgi?id=157340 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Please detail a bit. What is the disfonction meaning? If dysfunction, what is it? What do you do and what do you get? And please don't set up your own reports as new, someone else must test and confirm it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154994] Functions sidebar should be searchable as soon as it is focused
https://bugs.documentfoundation.org/show_bug.cgi?id=154994 --- Comment #3 from Stéphane Guillou (stragu) --- With your implementation in bug 122718, you workflow works exactly as described. Please go ahead and close this one as fixed too! :) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157332] EDITING: Cannot save a Page Style correctly in a template
https://bugs.documentfoundation.org/show_bug.cgi?id=157332 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- No problem here with Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Please test in safe mode, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157329] .docx header field is getting distorted
https://bugs.documentfoundation.org/show_bug.cgi?id=157329 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from m.a.riosv --- Reproducible Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133026] [META] Tight integration of extensions
https://bugs.documentfoundation.org/show_bug.cgi?id=133026 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||157324 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157324 [Bug 157324] Extensions Gallery dialog does not show some gallery extensions -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157324] Extensions Gallery dialog does not show some gallery extensions
https://bugs.documentfoundation.org/show_bug.cgi?id=157324 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Blocks||133026 CC||heiko.tietze@documentfounda ||tion.org, ||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 --- Comment #1 from Stéphane Guillou (stragu) --- Reproduced with gallery extension "Computer science symbols for BTS SIO classroom", which at the time of writing had an update 5 months before. https://extensions.libreoffice.org/en/extensions/show/27721 I checked that the downloaded OXT extension could be installed manually without problem. The extensions has the "Gallery" tag on the website. Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e472b5b557d2b43b41e488c83db2b188de499610 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Heiko, you are my go-to extensions specialist, any idea why that might be? How is that list populated? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=133026 [Bug 133026] [META] Tight integration of extensions -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157322] When underlining a paragraph, the line goes beyond the last characters to the right.
https://bugs.documentfoundation.org/show_bug.cgi?id=157322 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 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 157318] Named ranges defined at the sheet level are not exported to XLSX
https://bugs.documentfoundation.org/show_bug.cgi?id=157318 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Reproducible with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5416c9183384d46f9eb347871541c6ee1e30c28b CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127232] [META] QR/barcode generator's problems and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=127232 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||157323 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157323 [Bug 157323] QR codes generated in Calc and exported to SVG or pasted elsewhere are too small -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157323] QR codes generated in Calc and exported to SVG or pasted elsewhere are too small
https://bugs.documentfoundation.org/show_bug.cgi?id=157323 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Blocks||127232 Version|7.6.1.2 release |6.4.0.3 release Ever confirmed|0 |1 Summary|Generated QR codes in Calc |QR codes generated in Calc |do not retain high |and exported to SVG or |definition when saved |pasted elsewhere are too ||small CC||stephane.guillou@libreoffic ||e.org --- Comment #3 from Stéphane Guillou (stragu) --- Thank you for the report! I can not reproduce the issue as described: after inserting a QR code, saving and reopening or reloading, the OLE object still looks sharp in Calc. However, I see that using "right-click > Save" on the QR code saves an SVG file that by default is 0.04 × 0.04 cm (if encoding the URL to this bug report), regardless of how big it is on canvas. This is way too small and should either be based on the size on the document, or use a more sensible default that would straight away be usable when printed as-is. This can also be shown when copy-pasting the object onto a Writer or Draw document. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e472b5b557d2b43b41e488c83db2b188de499610 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Same in 6.4.0.3, the branch in which the feature first appeared. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=127232 [Bug 127232] [META] QR/barcode generator's problems and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157317] FILESAVE, FILEOPEN: Formulas don't show database or column labels after save/reload
https://bugs.documentfoundation.org/show_bug.cgi?id=157317 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #2 from m.a.riosv --- Please take a looke into https://wiki.documentfoundation.org/ReleaseNotes/5.1#Table_structured_references Only possible to save in xlsx format. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157337] Writer Keyboard Shortcut for Data and Time fields request revert default to Fixed Value
https://bugs.documentfoundation.org/show_bug.cgi?id=157337 --- Comment #2 from Mike Kaganski --- I believe we should not revert, because the fix of old UNO would likely be in different files / functions. The new UNO for non-fixed date/time should IMO be discussed first. Let us limit this to the regression part, and not introduce anything new here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157327] Incorrect display scaling on kf5 VCL (linux/wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=157327 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- This issue is tracked in bug 141578, see e.g. bug 141578 comment 21. Thank you! *** This bug has been marked as a duplicate of bug 141578 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141578] Libreoffice unusable with fractional scaling on multimonitor (on plasma+wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=141578 Stéphane Guillou (stragu) changed: What|Removed |Added CC||sergio.calleg...@gmail.com --- Comment #22 from Stéphane Guillou (stragu) --- *** Bug 157327 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120201] [META] Update or add link to help page
https://bugs.documentfoundation.org/show_bug.cgi?id=120201 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||157020 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157020 [Bug 157020] help opens always the same page (overview/home page) when pressing F1 on a function -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157020] help opens always the same page (overview/home page) when pressing F1 on a function
https://bugs.documentfoundation.org/show_bug.cgi?id=157020 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||120201 Status|UNCONFIRMED |NEW Version|7.6.0.3 release |Inherited From OOo Ever confirmed|0 |1 CC||olivier.hallot@libreoffice. ||org, ||stephane.guillou@libreoffic ||e.org OS|Windows (All) |All Severity|normal |enhancement Summary|Offline help opens always |help opens always the same |the same page |page (overview/home page) |(overview/home page)|when pressing F1 on a ||function Whiteboard| QA:needsComment| --- Comment #1 from Stéphane Guillou (stragu) --- This is an interesting use of F1, and i agree it should work as you expect. - If the cursor is in the function name SUM in the cell, I get HID=SC_HID_SC_WIN_GRIDWIN#bm_id3155335 - If the cursor is in the function name SUM in the input line (aka formula bar), I get a 404 with HID=modules/scalc/ui/inputbar/sc_input_window Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e472b5b557d2b43b41e488c83db2b188de499610 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded The behaviour in cell is inherited, but at least OOo 3.3 would lead to the Input Line help page if F1 was pressed in the input line. Olivier, what do you think? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120201 [Bug 120201] [META] Update or add link to help page -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157336] Spreadsheet Function AVERAGE Doesn't accept more than 30 arguments
https://bugs.documentfoundation.org/show_bug.cgi?id=157336 Werner Tietz changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #1 from Werner Tietz --- Hallo AVERAGE accepts Range-addresses aka: »A2:A2« which counts as ONE Argument but includes 1 Numbers, that should solve your issue! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142947] Make menu expander triangles configurable for icon design
https://bugs.documentfoundation.org/show_bug.cgi?id=142947 --- Comment #17 from Jérôme --- This bug is fixed in most cases but not all. Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: 4412c0006c0cfe5a5d40cae25a00da8a194aa4c0 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded See comment comment 11, comment 12 and comment 13 for details. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157309] Crash in: SwContentFrame::MakeAll(OutputDevice *) after loading document
https://bugs.documentfoundation.org/show_bug.cgi?id=157309 --- Comment #4 from Yves Poissant --- I just tried loading the document in version 24.2.0.0.alpha0+ and it didn't crash. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104444] [META] DOCX (OOXML) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=10 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||157328 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157328 [Bug 157328] The save icon in .docx file suggests change when there were none (move out of cell with number) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157328] The save icon in .docx file suggests change when there were none (move out of cell with number)
https://bugs.documentfoundation.org/show_bug.cgi?id=157328 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||10 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=10 [Bug 10] [META] DOCX (OOXML) table-related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157328] The save icon in .docx file suggests change when there were none (move out of cell with number)
https://bugs.documentfoundation.org/show_bug.cgi?id=157328 Stéphane Guillou (stragu) changed: What|Removed |Added Version|7.5.6.2 release |3.3.0 release Status|UNCONFIRMED |NEW Summary|The save icon in .docx file |The save icon in .docx file |suggests changes when there |suggests change when there |were none |were none (move out of cell ||with number) CC||stephane.guillou@libreoffic ||e.org Blocks||116625 Ever confirmed|0 |1 Severity|normal |minor Priority|medium |low --- Comment #1 from Stéphane Guillou (stragu) --- Reproduced for DOCX but not ODT in: Version: 7.5.6.2 (X86_64) / LibreOffice Community Build ID: f654817fb68d6d4600d7d2f6b647e47729f55f15 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded And a recent master build: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e472b5b557d2b43b41e488c83db2b188de499610 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded But also in 7.4.7.2 and 5.4.0.3 and 3.3.0, when saving as DOCX started. The change is visible in the undo history, it's a format change. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=116625 [Bug 116625] [META] Bugs where document modification status is wrong -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116625] [META] Bugs where document modification status is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=116625 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||157328 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157328 [Bug 157328] The save icon in .docx file suggests change when there were none (move out of cell with number) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156842] Export to PDF that includes PDF images are incorrect in size (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=156842 Patrick Luby changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |plub...@neooffice.org |desktop.org | --- Comment #15 from Patrick Luby --- (In reply to Patrick Luby from comment #14) > Created attachment 189705 [details] > Another sample file that reproduces the bug I have submitted a fix in the following patch: https://gerrit.libreoffice.org/c/core/+/157090 It still needs to be reviewed, but I think the above patch fixes this bug without causing non-external PDF XObjects to be incorrectly resized that occurred in my debug patch in https://bugs.documentfoundation.org/show_bug.cgi?id=156842#c12. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157135] LibreOffice 7.6 stalls under Windows 11
https://bugs.documentfoundation.org/show_bug.cgi?id=157135 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #8 from m.a.riosv --- Please test disabling Skia options in Menu/Tools/LibreOffice/View. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157074] Program freeze when editing graphics, saving file
https://bugs.documentfoundation.org/show_bug.cgi?id=157074 Stéphane Guillou (stragu) changed: What|Removed |Added Version|7.6.1.2 release |7.6.0.3 release Keywords||regression --- Comment #9 from Stéphane Guillou (stragu) --- Marking as regression as you can't reproduce in 7.5. I'm not holding my breath but can you please see if the problem persists with forced Skia/Raster? Turn "Force Skia software rendering" on in Tools ▸ Options ▸ LibreOffice ▸ View. Please also share the version information with Help > About LibreOffice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36729] an alternate way to view comparison results: simply highlight modified sections
https://bugs.documentfoundation.org/show_bug.cgi?id=36729 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|an alternate way to view|an alternate way to view |comparison results |comparison results: simply ||highlight modified sections Version|3.3.2 release |Inherited From OOo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa
sw/qa/extras/uiwriter/data/testTdf106663.odt |binary
sw/qa/extras/uiwriter/uiwriter6.cxx | 20
2 files changed, 20 insertions(+)
New commits:
commit 486ae5db6987411d5e394de94b2b077099d03856
Author: Andreas Heinisch
AuthorDate: Tue Sep 19 21:20:40 2023 +0200
Commit: Andreas Heinisch
CommitDate: Tue Sep 19 22:44:05 2023 +0200
tdf#106663 - Test GoToNextPlacemarker in header's fly frame
Change-Id: I3a2d63c0a1f07460db4aeabd1df289090c5f013b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/157070
Tested-by: Jenkins
Reviewed-by: Andreas Heinisch
diff --git a/sw/qa/extras/uiwriter/data/testTdf106663.odt
b/sw/qa/extras/uiwriter/data/testTdf106663.odt
new file mode 100755
index ..eee462406bb0
Binary files /dev/null and b/sw/qa/extras/uiwriter/data/testTdf106663.odt differ
diff --git a/sw/qa/extras/uiwriter/uiwriter6.cxx
b/sw/qa/extras/uiwriter/uiwriter6.cxx
index 80eecbaa5edd..f1f349779dac 100644
--- a/sw/qa/extras/uiwriter/uiwriter6.cxx
+++ b/sw/qa/extras/uiwriter/uiwriter6.cxx
@@ -2522,6 +2522,26 @@ CPPUNIT_TEST_FIXTURE(SwUiWriterTest6, testTdf146178)
CPPUNIT_ASSERT_EQUAL(sal_Int32(0), pCursor->GetPoint()->GetContentIndex());
}
+CPPUNIT_TEST_FIXTURE(SwUiWriterTest6,
testTdf106663HeaderTextFrameGoToNextPlacemarker)
+{
+createSwDoc("testTdf106663.odt");
+
+SwDoc* pDoc = getSwDoc();
+SwPaM* pCursor = pDoc->GetEditShell()->GetCursor();
+SwWrtShell* pWrtShell = pDoc->GetDocShell()->GetWrtShell();
+
+// Move the cursor into the fly frame of the document's header
+pWrtShell->GotoFly("FrameInHeader", FLYCNTTYPE_FRM, false);
+
+// Check that GoToNextPlacemarker highlights the first field instead of
the second one
+dispatchCommand(mxComponent, ".uno:GoToNextPlacemarker", {});
+// Without the fix in place, this test would have failed with
+// - Expected: Heading
+// - Actual : Some other marker
+// i.e. the GoToNextPlacemarker command skipped the first field
+
CPPUNIT_ASSERT(pCursor->GetPoint()->GetNode().GetTextNode()->GetText().startsWith("Heading"));
+}
+
CPPUNIT_TEST_FIXTURE(SwUiWriterTest6, testTdf155407)
{
createSwDoc();
[Libreoffice-bugs] [Bug 119605] Document comparison is missing an option not to take into account (or show) style (or formatting) changes
https://bugs.documentfoundation.org/show_bug.cgi?id=119605 Stéphane Guillou (stragu) changed: What|Removed |Added Version|unspecified |Inherited From OOo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119605] Document comparison is missing an option not to take into account (or show) style (or formatting) changes
https://bugs.documentfoundation.org/show_bug.cgi?id=119605 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7338 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 31481] [RFE] Split pane in same window for side-by-side proof reading/ translating of 2 different files
https://bugs.documentfoundation.org/show_bug.cgi?id=31481 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7338 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 36729] an alternate way to view comparison results
https://bugs.documentfoundation.org/show_bug.cgi?id=36729 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||7338 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157338] Need side-by-side comparison in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=157338 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||stephane.guillou@libreoffic ||e.org Version|7.4.7.2 release |Inherited From OOo Ever confirmed|0 |1 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||9605, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=36 ||729, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=31 ||481 Blocks||125674 --- Comment #2 from Stéphane Guillou (stragu) --- I can see how this would improve the readability in comparing two versions of the same document. Somewhat linked to the split view requested in bug 31481. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125674 [Bug 125674] [META] Document Comparison bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
