[Bug 107905] [META] Cross-references bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107905 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||160700 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160700 [Bug 160700] Regression: broken cross-reference to empty element of numbered list after saving -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160700] Regression: broken cross-reference to empty element of numbered list after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=160700 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Keywords||bibisectRequest, regression Blocks||107905 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107905 [Bug 107905] [META] Cross-references bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
core.git: static/source
static/source/unoembindhelpers/PrimaryBindings.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit d304fdb3369235ff4916463687b5e625c7fa3650
Author: Stephan Bergmann
AuthorDate: Tue Apr 16 20:37:25 2024 +0200
Commit: Stephan Bergmann
CommitDate: Wed Apr 17 07:56:09 2024 +0200
Embind: css::uno::Type should probably use sharing_policy::NONE
Given the reasoning in 0957ee9f5d379c80fca4027c187b471118d0490d "Embind: No
need
for $query", those sharing_policies appear to be (solely) about upcasting of
those smart pointers, and css::uno::Type doesn't involve any class
hierarchies,
so NONE ("no upcasting", in genericPointerToWireType in Emscripten's
src/embind/embind.js) appears to be the best match here.
Change-Id: I74b74d3c31cc17a7fd0a6d072160316e60884557
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166160
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann
diff --git a/static/source/unoembindhelpers/PrimaryBindings.cxx
b/static/source/unoembindhelpers/PrimaryBindings.cxx
index c8d4717aa347..d74b63ab8402 100644
--- a/static/source/unoembindhelpers/PrimaryBindings.cxx
+++ b/static/source/unoembindhelpers/PrimaryBindings.cxx
@@ -45,7 +45,7 @@ template <> struct emscripten::smart_ptr_trait
{
return ptr.getTypeLibType();
}
-static sharing_policy get_sharing_policy() { return
sharing_policy::INTRUSIVE; }
+static sharing_policy get_sharing_policy() { return sharing_policy::NONE; }
static css::uno::Type* share(typelib_TypeDescriptionReference* v)
{
return new css::uno::Type(v);
[Bug 156273] Add a "Navigate by" Help page for .uno:NavElement
https://bugs.documentfoundation.org/show_bug.cgi?id=156273 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6332 Assignee|libreoffice-b...@lists.free |stephane.guillou@libreoffic |desktop.org |e.org --- Comment #5 from Stéphane Guillou (stragu) --- I am looking into it now. See also my bug 115673 comment 1. (In reply to sdc.blanco from comment #4) > 1. I guess this page is supposed to be the help for the Navigation toolbar > (was hard to tell). (fwiw, I opened that toolbar and tried with F1, but no > luck, so filed bug 156332). The Navigation toolbar holds different commands, namely .uno:NavigateBack and .uno:NavigateForward to navigate the cursor position history, and its corresponding help page is /text/swriter/navigate_toolbar.xhp I have reopened bug 156332 so we can correct that link. > 2. I can follow your idea that the various options in the "Navigate By" > combobox could be explained on the Navigation page (given that they are > already mentioned there). There's enough quirks to it to have that dedicated separate page, e.g. the Repeat Search tool (documented) and the addition of Recency for bug 115817 (not documented). > Alternatively, the "Navigation" toolbar does not have "Navigate by", see above > while > it does appear (hidden) in the "Find" toolbar. since 7.1 with your commit for bug 129471 > "Navigate by" is not > mentioned in the help for Find, but maybe that material should be moved > there? As it's hidden by default, I wouldn't prioritise that. > 3. In either case, it seems like a "Navigate By" heading should appear > explicitly, because that is the name used in the Tools - Customize (for > .uno:NavElement). Agreed, I am changing it in the help page. > 4. The list of objects that can be navigated needs to be updated (and > explained better in some cases). Agreed. Might need a follow-up commit to the one I'm working on. > 5. The first sentence (on the Navigation page) refers to an icon (but it is > not clear where it is located, probably this icon should be added to this > help page). It was changed from an icon to a listbox (and relabelled from "Navigation" to "Navigate By") in 7.0. > 6. Maybe additional improvements are appropriate on the "Navigation" page, > have not inspected closely. Certainly, e.g. the mention of the button in "lower right of the document window" - that scrollbar button is long gone. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103030] [META] Navigator sidebar deck and floating window (also "Target in Document")
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||115673 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=115673 [Bug 115673] [META] Navigate By toolbar control bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115673] [META] Navigate By toolbar control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=115673 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Blocks||103030 Version|unspecified |Inherited From OOo --- Comment #1 from Stéphane Guillou (stragu) --- (In reply to Yousuf Philips (jay) (retired) from comment #0) > Navigate By (.uno:NavElement) toolbar control was added in bug 79167 to the > Find Toolbar in LibreOffice 6.0. ... along with the companion navigation arrows Previous Element (.uno:ScrollToPrevious) and Next Element (.uno:ScrollToNext). However, all three were by default hidden from the Find Toolbar in 7.1. (See e70069fb72d52c20b28166708a217bf674dcb61b for bug 129471) We still have these three controls in the Navigator (since OOo times). Note that we also have a "Navigation" toolbar that has the Back (.uno:NavigateBack) and Forward (.uno:NavigateForward) arrows to navigate a history of cursor positions; however, it's mostly made obsolete since LO 7.2 by the fix for bug 115817, superseding it with the "Recency" element in the Navigate By dropdown, + use of .uno:ScrollToPrevious and .uno:ScrollToNext arrows. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103030 [Bug 103030] [META] Navigator sidebar deck and floating window (also "Target in Document") -- You are receiving this mail because: You are the assignee for the bug.
core.git: include/tools tools/source
include/tools/XmlWriter.hxx|7 +--
tools/source/xml/XmlWriter.cxx | 13 -
2 files changed, 5 insertions(+), 15 deletions(-)
New commits:
commit 96f62b48b4425f0bc2b6d8497782694078d968fc
Author: Mike Kaganski
AuthorDate: Mon Apr 15 08:19:25 2024 +0100
Commit: Mike Kaganski
CommitDate: Wed Apr 17 06:40:40 2024 +0200
Simplify a bit
Change-Id: Iadfa442f762aa3caf3a8de7f3633be4e73bfd91a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166091
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/include/tools/XmlWriter.hxx b/include/tools/XmlWriter.hxx
index 03cc151b2624..9c8f82a86f42 100644
--- a/include/tools/XmlWriter.hxx
+++ b/include/tools/XmlWriter.hxx
@@ -48,12 +48,15 @@ public:
void endDocument();
void startElement(const char* sName);
-void startElement(const OString& sName);
+void startElement(const OString& sName) { startElement(sName.getStr()); }
void startElement(const OString& sPrefix, const OString& sName, const
OString& sNamespaceUri);
void endElement();
void attribute(const char* sTagName, const OString& aValue);
-void attribute(const OString& sTagName, const OString& aValue);
+void attribute(const OString& sTagName, const OString& aValue)
+{
+attribute(sTagName.getStr(), aValue);
+}
void attribute(const char* sTagName, std::u16string_view aValue);
void attribute(const char* sTagName, sal_Int64 aNumber);
template
diff --git a/tools/source/xml/XmlWriter.cxx b/tools/source/xml/XmlWriter.cxx
index f49c312bd133..8bbd7951a3b8 100644
--- a/tools/source/xml/XmlWriter.cxx
+++ b/tools/source/xml/XmlWriter.cxx
@@ -99,12 +99,6 @@ void XmlWriter::startElement(const char* pName)
(void)xmlTextWriterStartElement(mpImpl->mpWriter, xmlName);
}
-void XmlWriter::startElement(const OString& rName)
-{
-xmlChar* xmlName = BAD_CAST(rName.getStr());
-(void)xmlTextWriterStartElement(mpImpl->mpWriter, xmlName);
-}
-
void XmlWriter::endElement() {
(void)xmlTextWriterEndElement(mpImpl->mpWriter); }
void XmlWriter::attributeBase64(const char* pName, std::vector
const& rValueInBytes)
@@ -128,13 +122,6 @@ void XmlWriter::attribute(const char* name, const OString&
value)
(void)xmlTextWriterWriteAttribute(mpImpl->mpWriter, xmlName, xmlValue);
}
-void XmlWriter::attribute(const OString& name, const OString& value)
-{
-xmlChar* xmlName = BAD_CAST(name.getStr());
-xmlChar* xmlValue = BAD_CAST(value.getStr());
-(void)xmlTextWriterWriteAttribute(mpImpl->mpWriter, xmlName, xmlValue);
-}
-
void XmlWriter::attribute(const char* name, std::u16string_view value)
{
attribute(name, OUStringToOString(value, RTL_TEXTENCODING_UTF8));
[Bug 160702] Wrong and unstable positioning of text parts in SVG
https://bugs.documentfoundation.org/show_bug.cgi?id=160702 Mike Kaganski changed: What|Removed |Added Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | Status|UNCONFIRMED |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
core.git: sc/source
sc/source/ui/view/output3.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 0340a52ef0b9da9861f912c56550e685621a59f1
Author: Andrea Gelmini
AuthorDate: Tue Apr 16 23:08:33 2024 +0200
Commit: Taichi Haradaguchi <20001...@ymail.ne.jp>
CommitDate: Wed Apr 17 06:11:36 2024 +0200
Fix typo
Change-Id: Idee34a2b522f69a0fcea9595c62b68f74628c299
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166164
Tested-by: Jenkins
Reviewed-by: Taichi Haradaguchi <20001...@ymail.ne.jp>
diff --git a/sc/source/ui/view/output3.cxx b/sc/source/ui/view/output3.cxx
index 760a62a12d1d..a54718076857 100644
--- a/sc/source/ui/view/output3.cxx
+++ b/sc/source/ui/view/output3.cxx
@@ -207,7 +207,7 @@ void ScOutputData::DrawSelectiveObjects(SdrLayerID nLayer)
if(pPageView)
{
// tdf#160589 need to check for registered PaintWindow using
the
-// 'original' TragetDevice, mpDev might have been changed by a
+// 'original' TargetDevice, mpDev might have been changed by a
// call to ::SetContentDevice. That again might patch in a
// pre-render device fetched from
SdrPaintWindow::GetTargetOutputDevice
// and thus the test if target is aregistered PageWindow would
fail
[Bug 120201] [META] Update or add link to help page
https://bugs.documentfoundation.org/show_bug.cgi?id=120201 Bug 120201 depends on bug 156332, which changed state. Bug 156332 Summary: F1 on View - Navigation does not find a relevant help page https://bugs.documentfoundation.org/show_bug.cgi?id=156332 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159395] LanguageTool Server: use correct default URL, when username/API key set
https://bugs.documentfoundation.org/show_bug.cgi?id=159395 --- Comment #2 from Commit Notification --- Leonid Ryzhov committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/155a6af93a8ac90cab15968f5dd499ab77ad9f72 tdf#159395-LanguageTool use correct default URL when username/APIkey set It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159395] LanguageTool Server: use correct default URL, when username/API key set
https://bugs.documentfoundation.org/show_bug.cgi?id=159395 Commit Notification changed: What|Removed |Added Whiteboard||target:24.8.0 -- You are receiving this mail because: You are the assignee for the bug.
core.git: cui/source
cui/source/options/optlanguagetool.cxx | 35 -
1 file changed, 22 insertions(+), 13 deletions(-)
New commits:
commit 155a6af93a8ac90cab15968f5dd499ab77ad9f72
Author: Leonid Ryzhov
AuthorDate: Wed Mar 20 23:21:18 2024 +0300
Commit: Mike Kaganski
CommitDate: Wed Apr 17 06:00:47 2024 +0200
tdf#159395-LanguageTool use correct default URL when username/APIkey set
Change-Id: I31e1c2f1dfd96d87f60b6be1e5abce4837827a76
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165079
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/cui/source/options/optlanguagetool.cxx
b/cui/source/options/optlanguagetool.cxx
index 8c56a40e728f..3979b42c0521 100644
--- a/cui/source/options/optlanguagetool.cxx
+++ b/cui/source/options/optlanguagetool.cxx
@@ -25,6 +25,7 @@
using LanguageToolCfg =
officecfg::Office::Linguistic::GrammarChecking::LanguageTool;
constexpr OUString LANGUAGETOOL_DEFAULT_URL =
u"https://api.languagetool.org/v2"_ustr;
+constexpr OUString LANGUAGETOOLPLUS_DEFAULT_URL =
u"https://api.languagetoolplus.com/v2"_ustr;
OptLanguageToolTabPage::OptLanguageToolTabPage(weld::Container* pPage,
weld::DialogController*
pController,
@@ -81,20 +82,21 @@ IMPL_LINK_NOARG(OptLanguageToolTabPage, CheckHdl,
weld::Toggleable&, void)
void OptLanguageToolTabPage::Reset(const SfxItemSet*)
{
// tdf#150494 If no URL has been set, use the default URL
-OUString aBaseURL = LanguageToolCfg::BaseURL::get().value_or("");
-if (aBaseURL.isEmpty())
-m_xBaseURLED->set_text(LANGUAGETOOL_DEFAULT_URL);
-else
-m_xBaseURLED->set_text(aBaseURL);
+OUString aUsername = LanguageToolCfg::Username::get().value_or("");
+OUString aApiKey = LanguageToolCfg::ApiKey::get().value_or("");
+OUString aBaseURL = LanguageToolCfg::BaseURL::get().value_or(
+(aUsername.isEmpty() && aApiKey.isEmpty()) ? LANGUAGETOOL_DEFAULT_URL
+ :
LANGUAGETOOLPLUS_DEFAULT_URL);
+m_xBaseURLED->set_text(aBaseURL);
m_xBaseURLED->set_sensitive(!LanguageToolCfg::BaseURL::isReadOnly());
m_xBaseURLImg->set_visible(LanguageToolCfg::BaseURL::isReadOnly());
-m_xUsernameED->set_text(LanguageToolCfg::Username::get().value_or(""));
+m_xUsernameED->set_text(aUsername);
m_xUsernameED->set_sensitive(!LanguageToolCfg::Username::isReadOnly());
m_xUsernameImg->set_visible(LanguageToolCfg::Username::isReadOnly());
-m_xApiKeyED->set_text(LanguageToolCfg::ApiKey::get().value_or(""));
+m_xApiKeyED->set_text(aApiKey);
m_xApiKeyED->set_sensitive(!LanguageToolCfg::ApiKey::isReadOnly());
m_xApiKeyImg->set_visible(LanguageToolCfg::ApiKey::isReadOnly());
@@ -139,14 +141,21 @@ bool OptLanguageToolTabPage::FillItemSet(SfxItemSet*)
auto batch(comphelper::ConfigurationChanges::create());
// tdf#150494 If no URL has been set, then save the default URL
+// tdf#159395 If Username and ApiKey are set, then save the default URL
for paid service
OUString aBaseURL = m_xBaseURLED->get_text();
-if (aBaseURL.isEmpty())
-LanguageToolCfg::BaseURL::set(LANGUAGETOOL_DEFAULT_URL, batch);
-else
-LanguageToolCfg::BaseURL::set(aBaseURL, batch);
+OUString aUsername = m_xUsernameED->get_text();
+OUString aApiKey = m_xApiKeyED->get_text();
-LanguageToolCfg::Username::set(m_xUsernameED->get_text(), batch);
-LanguageToolCfg::ApiKey::set(m_xApiKeyED->get_text(), batch);
+if (aBaseURL.isEmpty()
+|| (aUsername.isEmpty() && aApiKey.isEmpty() && aBaseURL ==
LANGUAGETOOLPLUS_DEFAULT_URL))
+aBaseURL = LANGUAGETOOL_DEFAULT_URL;
+
+if (!aUsername.isEmpty() && !aApiKey.isEmpty() && aBaseURL ==
LANGUAGETOOL_DEFAULT_URL)
+aBaseURL = LANGUAGETOOLPLUS_DEFAULT_URL;
+
+LanguageToolCfg::BaseURL::set(aBaseURL, batch);
+LanguageToolCfg::Username::set(aUsername, batch);
+LanguageToolCfg::ApiKey::set(aApiKey, batch);
LanguageToolCfg::RestProtocol::set(m_xRestProtocol->get_text(), batch);
LanguageToolCfg::SSLCertVerify::set(!m_xSSLDisableVerificationBox->get_active(),
batch);
batch->commit();
[Bug 88278] [META] SVG import image filter (all modules)
https://bugs.documentfoundation.org/show_bug.cgi?id=88278 Mike Kaganski changed: What|Removed |Added Depends on||160702 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160702 [Bug 160702] Wrong and unstable positioning of text parts in SVG -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160702] New: Wrong and unstable positioning of text parts in SVG
https://bugs.documentfoundation.org/show_bug.cgi?id=160702 Bug ID: 160702 Summary: Wrong and unstable positioning of text parts in SVG Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: filters and storage Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com Blocks: 88278 Created attachment 193717 --> https://bugs.documentfoundation.org/attachment.cgi?id=193717=edit A sample with colon after a tspan The attached SVG has this markup: Tititititititititit: Note that the colon is outside of the tspan containing the most of the text, not separated by anu spaces. It is expected that the colon is drawn as a natural continuation of the text, as if there weren't a tspan element around the preceding "Tititititititititit". Opening it in different versions of LibreOffice gives different, but consistently poor, result. In versions prior to 7.5 (e.g., in 7.0), the colon is "merged" to the preceding "t" in most of zoom levels (e.g., 200%, 250%); but sometimes, it is separated by a large space (in 180% and 280%); and sometimes, it "jumps" somewhere between i and t (160%). In fact, this is not the colon that jumps; zooming between 250, 280, and 310 percent zoom using the mouse wheel allows to see that it's the size of "Tititititititititit" that changes inconsistently, becoming relatively larger or smaller compared to the whole page size in different zoom levels. Starting with version 7.5 (and in current master), the size of the "Tititititititititit" and the position of the ":" is different, but still wrong; the picture similar to older versions' 250-280-310% jumping is now visible in 140-160-180% zoom. Two commits resulted in this change: 1fa731d03ba0f22cb9392a578124ea977eaab2e9 and a42f5faac7c6d4590e632cf40e3ba9eb618e6f56. Note how this seems to answer the "I don't know in which context such blank is needed" in bug 103888 - the blank between different pieces was likely added as a hack to increase chances that the pieces won't overlap (at the cost of adding unexpected gaps). Note that the effect depends on display DPI; all the abovementioned zoom levels were tested using 100% display scale on Windows; and when using 150% scaling, the 140-160-180% looks different, but 90% zoom shows the jump. The essence of the problem is generally inconsistent scaling of the text, which makes the absolutely positioned pieces of text to look bad. That same issue may result in a bad absolute positioning of the colon here, when its position is calculated using some screen font size, with unclear correctness of the calculation. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=88278 [Bug 88278] [META] SVG import image filter (all modules) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160698] Crash after opening Print dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=160698 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160675] UI: Sidebar doesn't show width and height (nor X/Y coordinates) of object in certain context
https://bugs.documentfoundation.org/show_bug.cgi?id=160675 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159939] Calc print dialog showing metric page size when system set to imperial sizes
https://bugs.documentfoundation.org/show_bug.cgi?id=159939 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160487] FILESAVE PPTX "Fit height to text" attribute of drawing objects (placeholders)
https://bugs.documentfoundation.org/show_bug.cgi?id=160487 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160489] libmspub: pub2xhtml doesn't preserve text and other issues
https://bugs.documentfoundation.org/show_bug.cgi?id=160489 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 132087] FORMATTING: Image-width shows maximum writeable area when set anchor > as character
https://bugs.documentfoundation.org/show_bug.cgi?id=132087 --- Comment #5 from QA Administrators --- Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160477] DIRE UPDATE
https://bugs.documentfoundation.org/show_bug.cgi?id=160477 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160484] LibreOffice can not store modified document, when file is on network drive
https://bugs.documentfoundation.org/show_bug.cgi?id=160484 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 124561] jumping ui in calc (pastespecial drop down menu with/without arrow)
https://bugs.documentfoundation.org/show_bug.cgi?id=124561 --- Comment #7 from QA Administrators --- Dear andreas_k, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158740] Crash at undo after pasting table in footnote
https://bugs.documentfoundation.org/show_bug.cgi?id=158740 --- Comment #25 from Telesto --- (In reply to Stéphane Guillou (stragu) from comment #24) > Telesto, can you still reproduce with comment 0 steps? If not, let's put > this one to rest and open fresh reports for crashes that are still current. Yes/No. Only the first attempt; argh. The crash reporter stack was different from attached backtraces. I have to re-investigate to improve the STR Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: aef28c23adc87b8e26eacb56c7dbcf652e907fb9 CPU threads: 8; OS: macOS 14.3; UI render: Skia/Raster; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 35595] Application.Wait = invalid procedure call
https://bugs.documentfoundation.org/show_bug.cgi?id=35595 --- Comment #6 from Trevor Gross --- Before the changes to Bugzilla on October 16, 2011, this Bug was discovered. starting right from NEW without ever being explicitly confirmed. The error is changed to NEEDINFO status for this reason. To move this error from NEEDINFO back to NEW, please check if the bug still exists with the release before 3.5.0 beta1 or beta2. https://doodlebaseball.io/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115846] “Navigate By” Function in Find Toolbar does not Work with Documents in Read-only Mode
https://bugs.documentfoundation.org/show_bug.cgi?id=115846 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard||target:6.1.0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160291] Sampling dialog should be able to run without closing the dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=160291 --- Comment #4 from Stéphane Guillou (stragu) --- (In reply to Heiko Tietze from comment #3) > I am thinking about to remember the settings as we do in other dialogs too. > This may, however, end in a situation where the result in $A1 is some sample > and $B1 some other, and what you actual what to get is the setting on this > result cell (plus the latest to apply it again). Not sure I understand this. Remembering the settings would be OK (although making sure we still use the current range selection to populate the "Input range" field, as currently), but I still think we need a simple Apply button so we don't have to repeatedly go into "Data > Statistics > Sampling" to do a handful of sampling events. Rafael, what's you opinion? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 142585] Flashing toolbar for Navigator and Styles (when at least one of them is docked)
https://bugs.documentfoundation.org/show_bug.cgi?id=142585 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #23 from Stéphane Guillou (stragu) --- (In reply to Adalbert Hanßen from comment #20) > In this case the problem persists: despite > "Headings" is the category selected in the Navigator, the Navigator view > shows the finding in the category "Tables" if I click on any of the words > "HERE" which are in a table. (In reply to Adalbert Hanßen from comment #21) > Excuse me, I looked for the wrong error: The flashing toolbar does not > happen in this installation (but the other bug of the Navigator not working > as expected showed up again). Yes, let's please stick to just the flickering here. The comments are already overwhelming in this report. So can you confirm that the flickering does _not_ happen with gen VCL but it _does_ happen with gtk3? Any chance you could record a video of the flickering issue when it happens? (In reply to Adalbert Hanßen from comment #22) > The button "Navigate By" was pressed (correct) but the other button > "ContentNavigation View" was not pressed. How do these relate to the bug? What settings need to be on or off to see the flickering? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 65028] RTF: RTF sections and write protection
https://bugs.documentfoundation.org/show_bug.cgi?id=65028 Aron Budea changed: What|Removed |Added Blocks||107738 CC||aron.bu...@gmail.com Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107738 [Bug 107738] [META] Section bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107738] [META] Section bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107738 Aron Budea changed: What|Removed |Added Depends on||65028 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=65028 [Bug 65028] RTF: RTF sections and write protection -- You are receiving this mail because: You are the assignee for the bug.
core.git: cui/source filter/source include/basegfx include/svx include/tools include/vcl sc/source sd/source sfx2/source slideshow/source svx/source sw/source tools/CppunitTest_tools_test.mk tools/qa
cui/source/dialogs/cuigrfflt.cxx |8 - filter/source/svg/svgwriter.cxx | 22 ++--- include/basegfx/numeric/ftools.hxx | 34 ++-- include/svx/svdtrans.hxx | 12 +- include/tools/helpers.hxx|8 - include/vcl/bitmap.hxx |5 - sc/source/core/data/drwlayer.cxx |8 - sd/source/ui/app/optsitem.cxx|4 sd/source/ui/dlg/vectdlg.cxx |6 - sd/source/ui/func/fuoaprms.cxx |3 sd/source/ui/view/drviews8.cxx |4 sfx2/source/doc/objcont.cxx |4 slideshow/source/engine/shapes/drawinglayeranimation.cxx |6 - svx/source/customshapes/EnhancedCustomShape2d.cxx|4 svx/source/dialog/_contdlg.cxx |4 svx/source/gallery2/galobj.cxx |4 svx/source/svdraw/gradtrns.cxx | 24 ++--- svx/source/svdraw/sdrpagewindow.cxx |7 + svx/source/svdraw/svdedtv1.cxx |4 svx/source/svdraw/svdfmtf.cxx|7 - svx/source/svdraw/svdhdl.cxx | 12 +- svx/source/svdraw/svdoashp.cxx | 18 ++-- svx/source/svdraw/svdobj.cxx |6 - svx/source/svdraw/svdocapt.cxx |6 - svx/source/svdraw/svdocirc.cxx | 11 +- svx/source/svdraw/svdoedge.cxx |4 svx/source/svdraw/svdograf.cxx |2 svx/source/svdraw/svdomeas.cxx | 16 +-- svx/source/svdraw/svdopath.cxx | 37 +--- svx/source/svdraw/svdorect.cxx |2 svx/source/svdraw/svdotext.cxx | 10 +- svx/source/svdraw/svdotextdecomposition.cxx | 12 +- svx/source/svdraw/svdpdf.cxx | 12 +- svx/source/svdraw/svdpoev.cxx|9 +- svx/source/svdraw/svdtrans.cxx | 24 ++--- svx/source/xoutdev/_xpoly.cxx|7 - sw/source/core/graphic/ndgrf.cxx |3 sw/source/core/layout/fly.cxx|2 tools/CppunitTest_tools_test.mk |1 tools/qa/cppunit/test_fround.cxx | 62 --- tools/source/generic/color.cxx |7 - tools/source/generic/line.cxx|7 + tools/source/generic/poly.cxx| 37 +--- vcl/osx/salframeview.mm |3 vcl/skia/salbmp.cxx |3 vcl/source/animate/AnimationRenderer.cxx |8 - vcl/source/bitmap/BitmapEmbossGreyFilter.cxx |4 vcl/source/bitmap/BitmapFastScaleFilter.cxx |4 vcl/source/bitmap/BitmapInterpolateScaleFilter.cxx |4 vcl/source/bitmap/BitmapScaleConvolutionFilter.cxx |8 - vcl/source/bitmap/BitmapScaleSuperFilter.cxx |4 vcl/source/bitmap/BitmapTools.cxx|8 - vcl/source/bitmap/Vectorizer.cxx |6 - vcl/source/bitmap/bitmap.cxx | 16 +-- vcl/source/filter/eps/eps.cxx|4 vcl/source/filter/wmf/emfwr.cxx |6 - vcl/source/filter/wmf/wmfwr.cxx |4 vcl/source/gdi/gdimtf.cxx| 28 +++--- vcl/source/gdi/metaact.cxx | 30 +++ vcl/source/gdi/pdfwriter_impl.cxx|8 - vcl/source/gdi/pdfwriter_impl2.cxx |8 - vcl/source/gdi/print.cxx | 10 +- vcl/source/gdi/regband.cxx |7 + vcl/source/graphic/GraphicObject.cxx | 16 +-- vcl/source/helper/canvastools.cxx|4 vcl/source/outdev/hatch.cxx | 19 ++-- vcl/source/outdev/rect.cxx | 16 +-- vcl/source/outdev/textline.cxx |4 vcl/source/outdev/transparent.cxx|2 vcl/source/window/window2.cxx|6 - vcl/unx/gtk3/gtkinst.cxx |3 xmloff/source/draw/shapeexport.cxx | 17 ++-- 72 files changed, 356 insertions(+), 389 deletions(-) New commits: commit ea9904c89608d561f6bde3379408208bbb24fe35
[Bug 62366] SLIDESHOW: Pen on the presenter console
https://bugs.documentfoundation.org/show_bug.cgi?id=62366 Stéphane Guillou (stragu) changed: What|Removed |Added URL||https://ask.libreoffice.org ||/t/ink-annotations-with-pen ||-while-presenting-in-presen ||ter-mode/90976 -- You are receiving this mail because: You are the assignee for the bug.
core.git: Branch 'feature/cib_contract49' - desktop/qa include/sfx2 sc/qa sfx2/source
desktop/qa/desktop_lib/test_desktop_lib.cxx |5 +
include/sfx2/sidebar/SidebarController.hxx |3
sc/qa/uitest/calc_tests/printRange.py | 95
sc/qa/uitest/manual_tests/calc.py |8 +-
sfx2/source/sidebar/SidebarController.cxx | 24 +--
5 files changed, 30 insertions(+), 105 deletions(-)
New commits:
commit 6cac6107d644c73a0c0fb913401039fc416487e9
Author: Oliver Specht
AuthorDate: Wed Apr 10 12:36:00 2024 +0200
Commit: Thorsten Behrens
CommitDate: Wed Apr 17 02:21:17 2024 +0200
Bundle sidebar updates via Timer
When a selection changes (text/table/shape) the framework
notifies the sidebar about each step which results in three
visible updates. This is reduced into one now.
Disable Calc printRange.py ui test for the moment, inducing
timer-based issues not affecting functionality.
Change-Id: I48ed987971cf6c711af31d552e8d64fa9982a416
diff --git a/desktop/qa/desktop_lib/test_desktop_lib.cxx
b/desktop/qa/desktop_lib/test_desktop_lib.cxx
index b698cc5976b7..019fcc76ada4 100644
--- a/desktop/qa/desktop_lib/test_desktop_lib.cxx
+++ b/desktop/qa/desktop_lib/test_desktop_lib.cxx
@@ -66,6 +66,7 @@
#include
#include
#include
+#include
#if USE_TLS_NSS
#include
@@ -3280,7 +3281,9 @@ void DesktopLOKTest::testControlState()
{
LibLODocument_Impl* pDocument = loadDoc("search.ods");
pDocument->pClass->postUnoCommand(pDocument, ".uno:StarShapes", nullptr,
false);
+Scheduler::ProcessEventsToIdle();
lcl_initializeSidebar();
+std::this_thread::sleep_for(std::chrono::milliseconds(300));
Scheduler::ProcessEventsToIdle();
boost::property_tree::ptree aState;
@@ -3294,7 +3297,9 @@ void DesktopLOKTest::testMetricField()
{
LibLODocument_Impl* pDocument = loadDoc("search.ods");
pDocument->pClass->postUnoCommand(pDocument, ".uno:StarShapes", nullptr,
false);
+Scheduler::ProcessEventsToIdle();
SfxChildWindow* pSideBar = lcl_initializeSidebar();
+std::this_thread::sleep_for(std::chrono::milliseconds(300));
Scheduler::ProcessEventsToIdle();
vcl::Window* pWin = pSideBar->GetWindow();
diff --git a/include/sfx2/sidebar/SidebarController.hxx
b/include/sfx2/sidebar/SidebarController.hxx
index 06e092bceec8..3f7b79aa2041 100644
--- a/include/sfx2/sidebar/SidebarController.hxx
+++ b/include/sfx2/sidebar/SidebarController.hxx
@@ -226,6 +226,9 @@ private:
*/
VclPtr mpCloseIndicator;
+Timer maChangeEventTimer;
+
+DECL_DLLPRIVATE_LINK(TimeoutHdl, Timer*, void);
DECL_DLLPRIVATE_LINK(WindowEventHandler, VclWindowEvent&, void);
/** Make maRequestedContext the current context.
*/
diff --git a/sc/qa/uitest/calc_tests/printRange.py
b/sc/qa/uitest/calc_tests/printRange.py
deleted file mode 100644
index b2253055c129..
--- a/sc/qa/uitest/calc_tests/printRange.py
+++ /dev/null
@@ -1,95 +0,0 @@
-# -*- tab-width: 4; indent-tabs-mode: nil; py-indent-offset: 4 -*-
-#
-# This file is part of the LibreOffice project.
-#
-# This Source Code Form is subject to the terms of the Mozilla Public
-# License, v. 2.0. If a copy of the MPL was not distributed with this
-# file, You can obtain one at http://mozilla.org/MPL/2.0/.
-#
-from uitest.framework import UITestCase
-from uitest.uihelper.common import get_state_as_dict
-from libreoffice.uno.propertyvalue import mkPropertyValues
-
-class printRange(UITestCase):
-def test_printRange(self):
-with self.ui_test.create_doc_in_start_center("calc"):
-xCalcDoc = self.xUITest.getTopFocusWindow()
-gridwin = xCalcDoc.getChild("grid_window")
-
-gridwin.executeAction("SELECT", mkPropertyValues({"RANGE":
"A1:F20"}))
-#Set print range
-self.xUITest.executeCommand(".uno:DefinePrintArea")
-# Print Range dialog
-with
self.ui_test.execute_modeless_dialog_through_command(".uno:EditPrintArea") as
xDialog:
-xlbprintarea = xDialog.getChild("lbprintarea")
-xedprintarea = xDialog.getChild("edprintarea")
-#verify range
-
self.assertEqual(get_state_as_dict(xlbprintarea)["SelectEntryText"], "-
selection -")
-self.assertEqual(get_state_as_dict(xedprintarea)["Text"],
"$A$1:$F$20")
-#set Row
-xedrepeatrow = xDialog.getChild("edrepeatrow")
-xedrepeatrow.executeAction("TYPE",
mkPropertyValues({"TEXT":"$1"}))
-#set Column
-xedrepeatcol = xDialog.getChild("edrepeatcol")
-xedrepeatcol.executeAction("TYPE",
mkPropertyValues({"TEXT":"$A"}))
-# Click Ok
-
-#Verify Print Range dialog
-with
self.ui_test.execute_modeless_dialog_through_command(".uno:EditPrintArea",
close_button="cancel") as xDialog:
-xedprintarea = xDialog.getChild("edprintarea")
-xedrepeatrow =
[Bug 158740] Crash at undo after pasting table in footnote
https://bugs.documentfoundation.org/show_bug.cgi?id=158740 --- Comment #24 from Stéphane Guillou (stragu) --- It's true this report has gotten messy, partly my fault. Reviewing the different steps to reproduce, with a current daily build (not debug): - comment 0: can't reproduce with original steps, but it does crash with one extra Redo step - comment 3: crash at paste (no need to undo, which Miklos confirmed in comment 5) - comment 6 and comment 16 (no floating table): crashing on paste step (no need to undo either) Telesto, can you still reproduce with comment 0 steps? If not, let's put this one to rest and open fresh reports for crashes that are still current. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bdf3b5ce49b0e4ee1b4525d344cfb037ef473059 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 120200] [META] Update or correct help for features
https://bugs.documentfoundation.org/show_bug.cgi?id=120200 Bug 120200 depends on bug 147898, which changed state. Bug 147898 Summary: instructions about paint can in "Font Color" section of "Font Effects" help page appears to be incorrect https://bugs.documentfoundation.org/show_bug.cgi?id=147898 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 80430] [META] Documentation gap for new features
https://bugs.documentfoundation.org/show_bug.cgi?id=80430 Bug 80430 depends on bug 86637, which changed state. Bug 86637 Summary: LOCALHELP: write help page for Calc OpenCL implementation https://bugs.documentfoundation.org/show_bug.cgi?id=86637 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 86637] LOCALHELP: write help page for Calc OpenCL implementation
https://bugs.documentfoundation.org/show_bug.cgi?id=86637 Olivier Hallot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 120200] [META] Update or correct help for features
https://bugs.documentfoundation.org/show_bug.cgi?id=120200 Bug 120200 depends on bug 135360, which changed state. Bug 135360 Summary: LO HELP: Update informations for View Dialog in Options => LibreOffice Writer https://bugs.documentfoundation.org/show_bug.cgi?id=135360 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 120200] [META] Update or correct help for features
https://bugs.documentfoundation.org/show_bug.cgi?id=120200 Bug 120200 depends on bug 107081, which changed state. Bug 107081 Summary: LOCALHELP: Index: backgrounds;inserting form Gallery https://bugs.documentfoundation.org/show_bug.cgi?id=107081 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 99671] [META] Gallery bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=99671 Bug 99671 depends on bug 107081, which changed state. Bug 107081 Summary: LOCALHELP: Index: backgrounds;inserting form Gallery https://bugs.documentfoundation.org/show_bug.cgi?id=107081 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 120200] [META] Update or correct help for features
https://bugs.documentfoundation.org/show_bug.cgi?id=120200 Bug 120200 depends on bug 120179, which changed state. Bug 120179 Summary: [LOCALHELP] rewrite SUMIF Help page https://bugs.documentfoundation.org/show_bug.cgi?id=120179 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 150027] Turn on "Range contains column labels" (for sorting) by default
https://bugs.documentfoundation.org/show_bug.cgi?id=150027 --- Comment #3 from Eyal Rozenberg --- I sometimes sort ranges with column headers/labels and sometimes columns which don't have them. Long story short: I OPPOSE option A, since IMHO it's more difficult to notice that non-column-headers have been misplaced, than to notice the column headers have been misplaced. I SUPPORT option B, i.e. a persistent default choice. I OPPOSE option C, but not on principle, just as exceeding the scope of this bug. I would expect a separate bug about other contexts, unless you can demonstrate that it's the same issue in specific other contexts. I WEAKLY OPPOSE option D, since I don't want to go look for preferences to choose my sort options. But I don't mind if that existed _also_ in the preferences. As for Brian's suggestion, of applying an intelligent heuristic instead of a fixed preference - that would be nice, if someone were to implement it; but perhaps that merits a separate bug, or at least - let option B be implemented as soon as possible, and a heuristic could be a potential extra. Perhaps a project for new developers? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 150027] Turn on "Range contains column labels" (for sorting) by default
https://bugs.documentfoundation.org/show_bug.cgi?id=150027 --- Comment #3 from Eyal Rozenberg --- I sometimes sort ranges with column headers/labels and sometimes columns which don't have them. Long story short: I OPPOSE option A, since IMHO it's more difficult to notice that non-column-headers have been misplaced, than to notice the column headers have been misplaced. I SUPPORT option B, i.e. a persistent default choice. I OPPOSE option C, but not on principle, just as exceeding the scope of this bug. I would expect a separate bug about other contexts, unless you can demonstrate that it's the same issue in specific other contexts. I WEAKLY OPPOSE option D, since I don't want to go look for preferences to choose my sort options. But I don't mind if that existed _also_ in the preferences. As for Brian's suggestion, of applying an intelligent heuristic instead of a fixed preference - that would be nice, if someone were to implement it; but perhaps that merits a separate bug, or at least - let option B be implemented as soon as possible, and a heuristic could be a potential extra. Perhaps a project for new developers? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160701] OpenPGP warning when encrypting with an untrusted public key: rename from "Error" to "Warning"
https://bugs.documentfoundation.org/show_bug.cgi?id=160701 steve changed: What|Removed |Added Priority|medium |low -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160701] OpenPGP warning when encrypting with an untrusted public key: rename from "Error" to "Warning"
https://bugs.documentfoundation.org/show_bug.cgi?id=160701 steve changed: What|Removed |Added CC||guibomac...@gmail.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0184 Blocks||158839 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158839 [Bug 158839] [META] OpenPGP bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158839] [META] OpenPGP bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=158839 steve changed: What|Removed |Added Depends on||160701 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160701 [Bug 160701] OpenPGP warning when encrypting with an untrusted public key: rename from "Error" to "Warning" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160701] OpenPGP warning when encrypting with an untrusted public key: rename from "Error" to "Warning"
https://bugs.documentfoundation.org/show_bug.cgi?id=160701 --- Comment #1 from steve --- Created attachment 193716 --> https://bugs.documentfoundation.org/attachment.cgi?id=193716=edit Screenshot info message about encrypting with an untrusted public OpenPGP key -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160701] New: OpenPGP warning when encrypting with an untrusted public key: rename from "Error" to "Warning"
https://bugs.documentfoundation.org/show_bug.cgi?id=160701 Bug ID: 160701 Summary: OpenPGP warning when encrypting with an untrusted public key: rename from "Error" to "Warning" Product: LibreOffice Version: 24.8.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: trivial Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: l...@disr.it Description: Gladly https://bugs.documentfoundation.org/show_bug.cgi?id=160184 got resolved and OpenPGP encryption with untrusted keys is now possible. A warning is shown beforehand. Currently that warning is labled "Error" which I find misleading and confusing. An error suggests that something is wrong with the software. That is not the case here. Would it be possible to re-label the dialog as "Warning" which better suits the nature of the context in this case? Steps to Reproduce: 1. open writer and write test 2. save document 3. in save dialog tick option "Encrypt with GPG key" and click "save" button 4. make sure you have an untrusted public OpenPGP key in your keyring and select that from the "Select Certificate" dialog Actual Results: Dialog with title "Error" is shown. Expected Results: Dialog title could be "Warning" instead. There is a side-problem that the dialog gives no advice how to resolve the situation the warning is about, i.e. trust a key. But that is a complex problem and probably out of scope for LibreOffice at that point. Reproducible: Always User Profile Reset: No Additional Info: Version: 24.8.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 38ed8100872913c64941927bba665e4bd1a44c12 CPU threads: 12; OS: macOS 14.4.1; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160700] Regression: broken cross-reference to empty element of numbered list after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=160700 --- Comment #3 from Serg Bormant --- Another Steps to Reproduce: 1. Open attached test_crossref.odt (crossref saved with 24.2.1.2 (valid)) with 24.2.2.2. 2. Save file 3. Reopen file -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160700] Regression: broken cross-reference to empty element of numbered list after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=160700 Serg Bormant changed: What|Removed |Added Attachment #193715|crossref saved with 2.4.2.2 |crossref saved with description|(invalid) |24.2.2.2 (invalid) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160700] Regression: broken cross-reference to empty element of numbered list after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=160700 --- Comment #2 from Serg Bormant --- Created attachment 193715 --> https://bugs.documentfoundation.org/attachment.cgi?id=193715=edit crossref saved with 2.4.2.2 (invalid) This is test_crossref.odt, opened and saved with Writer 24.2.2.2 with invalid crossref. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160700] Regression: broken cross-reference to empty element of numbered list after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=160700 --- Comment #1 from Serg Bormant --- Created attachment 193714 --> https://bugs.documentfoundation.org/attachment.cgi?id=193714=edit crossref saved with 24.2.1.2 (valid) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160700] New: Regression: broken cross-reference to empty element of numbered list after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=160700 Bug ID: 160700 Summary: Regression: broken cross-reference to empty element of numbered list after saving Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: borm...@mail.ru Description: Writer in 24.2.2.2 breaks cross-references to empty elements of numbered lists. Writer in 24.2.1.2 works. Steps to Reproduce: 1. Create new Writer document 2. Press Enter, Up, F12, Down 3. Select menu Insert - Cross-reference Type: Numbered paragraphs Refer using: Number Selection: 1 Click [ Insert ], click [ Close ] 4. Select menu File - Save, give name, for ex. test1.odt 5. Select menu File - Reload Actual Results: Error: Reference source not found instead of cross-reference "1" as at steps 3 and 4. Expected Results: Cross-referense "1" to list item as at step 3 and 4. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 24.2.2.2 (x86) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160699] Performance: delay loading OpenPGP key details until needed for an operation
https://bugs.documentfoundation.org/show_bug.cgi?id=160699 --- Comment #3 from Patrick Luby (volunteer) --- (In reply to steve from comment #2) > Created attachment 193713 [details] > 2024-04-16 Sample of LibreOfficeDev while hanging Interestingly, your sample shows LibreOffice is loading all of fonts for the Font combobox in the toolbar. I don't see any GPG code in your sample so I wonder if one or more fonts are loading very slowly. If you validate all your fonts using the steps in the following comment, are there any fonts with warnings or errors? If yes, does deactivating or removing them stop or reduce the hang?: https://bugs.documentfoundation.org/show_bug.cgi?id=160644#c7 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146852] Opening Tools-Options slow because it checks GnuPG port at local computer
https://bugs.documentfoundation.org/show_bug.cgi?id=146852 steve changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0699 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160699] Performance: delay loading OpenPGP key details until needed for an operation
https://bugs.documentfoundation.org/show_bug.cgi?id=160699 steve changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6852 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160699] Performance: delay loading OpenPGP key details until needed for an operation
https://bugs.documentfoundation.org/show_bug.cgi?id=160699 --- Comment #2 from steve --- Created attachment 193713 --> https://bugs.documentfoundation.org/attachment.cgi?id=193713=edit 2024-04-16 Sample of LibreOfficeDev while hanging -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160699] Performance: delay loading OpenPGP key details until needed for an operation
https://bugs.documentfoundation.org/show_bug.cgi?id=160699 steve changed: What|Removed |Added Keywords||perf --- Comment #1 from steve --- This is the mac where reproducing the delay is possible: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 71efd6046488b952f679936ea1c4a415f4989b18 CPU threads: 8; OS: macOS 13.6.6; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153306] Cursor leftovers keep being displayed when using Skia Vulkan/Metal
https://bugs.documentfoundation.org/show_bug.cgi?id=153306 --- Comment #32 from Patrick Luby (volunteer) --- Forgot to post my LibreOffice About dialog details: Version: 24.8.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 1d5630c5deeec5dca724c29ec8c886bfa71a2099 CPU threads: 8; OS: macOS 14.4.1; UI render: Skia/Metal; VCL: osx Locale: en-CA (en_CA.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159708] High CPU usage UI ribbon/menu
https://bugs.documentfoundation.org/show_bug.cgi?id=159708 --- Comment #12 from je...@jgilmore.com --- (In reply to m_a_riosv from comment #11) > Have you tested with other app, doing the same? I performed tests amoung a few applications as listed below. The only thing I noticed was a brief CPU spike as I switch window from one screen to the other. After that, the CPU settled down. LibreOffice Calc Exhibits the same behavior as LibreOffice Writer with the difference that if you stop interacting with LibreCalc, the CPU settles down. Fascinating behavior. If you move it in the external monitor and don't touch it for a while. The CPU will start to idle. Then you can interact with it OK. If you slightly move the window around on the external monitor, it will then start maxing out the CPU. At some point, the interface freezes. Moving the main window back to the built in monitor unfreezes everything. The Skia is enabled. The other odd behavior with Calc is it seems to heavily use 2 cores, where Writer seemed to use only a single core. CyberLink PowerDirector 14. This is multicore capable. I use it to render videos. This has a different bug: it doesn't re-render its interface, so it starts on my high res built in monitor and looks fine. After I drag it to my external monitor, it looks ugly because the interface was scaled up. It stays that way :( But it also does not exhibit high CPU usage when I shift monitors. Notepad++ no noticable change Arduino IDE no noticable change Visual Studio 2023 no noticable change GIMP no noticable change Paint.net no noticable change FileZilla no noticable change Putty no noticable change Fiddler proxy debugger no noticable change RealVNC viewer no noticable change That's about all I ever use. I hope this helps. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160699] Performance: delay loading OpenPGP key details until needed for an operation
https://bugs.documentfoundation.org/show_bug.cgi?id=160699 steve changed: What|Removed |Added Blocks||158839 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158839 [Bug 158839] [META] OpenPGP bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158839] [META] OpenPGP bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=158839 steve changed: What|Removed |Added Depends on||160699 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160699 [Bug 160699] Performance: delay loading OpenPGP key details until needed for an operation -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153306] Cursor leftovers keep being displayed when using Skia Vulkan/Metal
https://bugs.documentfoundation.org/show_bug.cgi?id=153306 --- Comment #31 from Patrick Luby (volunteer) --- (In reply to bintoro from comment #27) > When using the external display, the horizontal point in which the artifacts > appear has in the nightly build moved so far to the right that the trails > won’t show up until the zoom level is increased. But for some reason, this > improvement hasn’t carried over to the internal display. > > Also, please see attachment 190367 [details] (posted in a duplicate bug) > exhibiting partial cursor trails to the left of the horizontal cutoff point. > This only happened with certain fonts, but right now I’m unable to reproduce > it at all. Anyway, perhaps some of this can provide clues as to what’s going > on. I can now reproduce this bug with the latest LibreOffice code using the document in comment #2 if I set the document zoom to 350% or more. Then, I need to right arrow to the least few letters in a line to see the bug: https://bugs.documentfoundation.org/attachment.cgi?id=193712 Since Skia/Raster is fine, maybe Skia/Metal (and maybe Skia/Vulkan on Windows?) is mishandling upscaling? Not sure how we would debug this though. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160699] Performance: delay loading OpenPGP key details until needed for an operation
https://bugs.documentfoundation.org/show_bug.cgi?id=160699 steve changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2524 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160699] New: Performance: delay loading OpenPGP key details until needed for an operation
https://bugs.documentfoundation.org/show_bug.cgi?id=160699 Bug ID: 160699 Summary: Performance: delay loading OpenPGP key details until needed for an operation Product: LibreOffice Version: 7.6.0.0 alpha0+ Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: l...@disr.it Description: Follow-up to https://bugs.documentfoundation.org/show_bug.cgi?id=152524 (macOS: LibreOffice crashes (gpgme / gpgmeio) on macOS 13 Ventura) While Patrick investigated that highly problematic crash it came to light that, at least on intel macs on macOS 13 Ventura, having many OpenPGP keys can lead to delays of up to a minute when opening LibreOffice. Apparently OpenPGP key details are being processed / loaded already when LibreOffice is opened as described in https://bugs.documentfoundation.org/show_bug.cgi?id=152524#c89: "I know LibreOffice loads all of your certificates sequentially so maybe I can see if we can delay loading each certificate's details until it is selected in the certificate selection dialog." If processing of OpenPGP key details can be delayed until required for an action that uses OpenPGP that would be a win for users. I set this to Minor, since on Apple Silicon with macOS 14.4.1 I am not seeing the beachball / delay when opening LibreOffice. I am unsure if that is because the problem does not occur on macOS Sonoma or if Apple Silicon has much better performance. Will have to test this some more on an old 2012 mac on which I run macOS Sonoma via OpenCoreLegacyPatcher but I am not near that mac currently. Steps to Reproduce: 1. have a few hundred key in GPG Keychain on your macOS 13 Ventura mac (unsure if intel mac is a requirement for this performance problem to show) Actual Results: Beachball / delay when opening LibreOffice. Expected Results: If the delay can be delayed (scnr) until the user interacts with OpenPGP functionality, that would improve the overall user experience. Reproducible: Sometimes User Profile Reset: No Additional Info: This is an edge case, and further investigation is needed to see if the issue is limited to macOS 13. If that is the case, spending time on this problem is probably not worth it. But that is to be discussed. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160684] The Landscape style is nonsensical while we have neither hierarchical nor composable page styles
https://bugs.documentfoundation.org/show_bug.cgi?id=160684 --- Comment #4 from Eyal Rozenberg --- (In reply to Cor Nouws from comment #2) > (Not sure what I should understand that 'incompatible page styles' means, > but..) To make my argument in the reply to Heiko more concrete: Scenario 1: Suppose I've spent a while tweaking my Default Page Style - working on margins, arranging the background, choosing a gradient transparency, set up a 3-column layout with fancy borders etc. Now, after having created a few pages, I want a landscape-oriented page. Since I'm a good boy who learned he should use styles, I double-click the "Landscape" PS and... what is this? It's the plain old boring white page! That's not what I wanted; I just wanted a landscape page! I will now have to copy style features from Default PS to Landscape :-( Scenario 2: I started out with the plain vanilla Default and Landscape PS'es and used them both. Now I want to, say, make my pages be green. So, I change the Default PS to green, and - darn it, the Landscape pages stay white :-( -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160684] The Landscape style is nonsensical while we have neither hierarchical nor composable page styles
https://bugs.documentfoundation.org/show_bug.cgi?id=160684 --- Comment #3 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #1) > How do you insert a landscape page in a typical portrait style document? The > supposed procedure is Insert > More Breaks > Manual Break... > Page break + > Page Style = Landscape. That's incorrect, because you get a style that, in principle, is completely different from Default PS. The only guarantee (assuming you haven't modified it) is that the page orientation is landscape. What's worse - if you then change the Default PS - the Landscape pages will not change, although you reasonably expect them to. When page styles inherit each other (bug 41316), and Landscape = "Default + orientation:landscape" - then that would be an appropriate procedure. Until that time, the procedure is: 1. Insert > Page Break 2. Set Format > Page Style > Page > Orientation to Landscape and while this is DF - it at least preserves all of the Default Page Style's other properties. > But we should remove page styles because of this shortcoming. Ah, so, that's a different question. If you accept what I said above, let's talk about what should be done in the mean time. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153306] Cursor leftovers keep being displayed when using Skia Vulkan/Metal
https://bugs.documentfoundation.org/show_bug.cgi?id=153306 --- Comment #30 from Patrick Luby (volunteer) --- Created attachment 193712 --> https://bugs.documentfoundation.org/attachment.cgi?id=193712=edit High zoomed document with Skia/Metal -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160644] Upon opening, LibreOffice sometimes crashes (perhaps once a week)
https://bugs.documentfoundation.org/show_bug.cgi?id=160644 --- Comment #9 from Patrick Luby (volunteer) --- (In reply to Sam from comment #8) > Thanks! I've followed your steps, and Font Validation found 9 fonts with > minor problems (warnings). I've now removed/deleted these fonts. Hopefully that stops the crashing, but if not please post the crash log and I will look for any differences from the previous logs. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108576] [META] Writer page style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108576 Bug 108576 depends on bug 160684, which changed state. Bug 160684 Summary: The Landscape style is nonsensical while we have neither hierarchical nor composable page styles https://bugs.documentfoundation.org/show_bug.cgi?id=160684 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160684] The Landscape style is nonsensical while we have neither hierarchical nor composable page styles
https://bugs.documentfoundation.org/show_bug.cgi?id=160684 Eyal Rozenberg changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160682] HTML "page style" is not a page style - move this functionality elsewhere
https://bugs.documentfoundation.org/show_bug.cgi?id=160682 --- Comment #3 from Eyal Rozenberg --- (In reply to Cor Nouws from comment #2) > Still it allows the user to do start a new Writer doc, and change to a HTML > version. I'm not sure I understand what you mean. How can you do this? Do you mean Web View? Well, that doesn't apply the HTML page style IIANM. > > 3. Converse of (2.) - when editing an HTML document, we _can't_ edit the > > HTML page style. > After starting a new HTML document, one can just edit the page style..? Ok, true, but only from the Format menu and not through the Styles sidebar. So, my point (3.) is a bit weak. > I do not object per see. What is the solution you suggest to use in stead? I think it should be "per se" https://www.grammar-monster.com/Latin_terms/per_se.htm Anyway, I am not _sure_ about what the solution should be. But one option I was thinking of is for HTML documents to use their own template. When you start a regular document, you open the default Writer template. If we had a default template for HTML documents, or even simply a template named HTML (more crude, but easier to implement UI-wise) - we could take its default page style. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160682] HTML "page style" is not a page style - move this functionality elsewhere
https://bugs.documentfoundation.org/show_bug.cgi?id=160682 --- Comment #3 from Eyal Rozenberg --- (In reply to Cor Nouws from comment #2) > Still it allows the user to do start a new Writer doc, and change to a HTML > version. I'm not sure I understand what you mean. How can you do this? Do you mean Web View? Well, that doesn't apply the HTML page style IIANM. > > 3. Converse of (2.) - when editing an HTML document, we _can't_ edit the > > HTML page style. > After starting a new HTML document, one can just edit the page style..? Ok, true, but only from the Format menu and not through the Styles sidebar. So, my point (3.) is a bit weak. > I do not object per see. What is the solution you suggest to use in stead? I think it should be "per se" https://www.grammar-monster.com/Latin_terms/per_se.htm Anyway, I am not _sure_ about what the solution should be. But one option I was thinking of is for HTML documents to use their own template. When you start a regular document, you open the default Writer template. If we had a default template for HTML documents, or even simply a template named HTML (more crude, but easier to implement UI-wise) - we could take its default page style. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160644] Upon opening, LibreOffice sometimes crashes (perhaps once a week)
https://bugs.documentfoundation.org/show_bug.cgi?id=160644 --- Comment #8 from Sam --- (In reply to Patrick Luby (volunteer) from comment #7) > (In reply to Sam from comment #6) > > There was another system crash today which occurred as soon as I asked > > LibreOffice to print to PDF a Writer document. > > > > I now remember these crashes not only occur unpredictably when starting LO > > but also when trying to print something from LO. > > > > Two more reports were generated after today's crash. I hope they give some > > useful information. > > Still looks like Apple "fontd" background process is crashing macOS. I > believe that fontd handles font loading so I wonder if you have a corrupted > or unloadable font installed on your Mac. > > If you validate all of the fonts using the following steps, are there any > fonts with warnings or errors?: > > 1. Launch the /Applications/Font Book application from the Finder > > 2. Select "All Fonts" in the sidebar on the left > > 3. Select one of the fonts and then select the Edit > Select All menu item > to select all of the fonts > > 4. Select the File > Validate Selection menu item to start the validation > process Thanks! I've followed your steps, and Font Validation found 9 fonts with minor problems (warnings). I've now removed/deleted these fonts. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160686] "Left Page" and "Right Page" are nonsensical and should be removed
https://bugs.documentfoundation.org/show_bug.cgi?id=160686 --- Comment #3 from Eyal Rozenberg --- (In reply to Eyal Rozenberg from comment #2) Apparently, I already _have_ commented there before, to oppose :-( -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160686] "Left Page" and "Right Page" are nonsensical and should be removed
https://bugs.documentfoundation.org/show_bug.cgi?id=160686 --- Comment #3 from Eyal Rozenberg --- (In reply to Eyal Rozenberg from comment #2) Apparently, I already _have_ commented there before, to oppose :-( -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160686] "Left Page" and "Right Page" are nonsensical and should be removed
https://bugs.documentfoundation.org/show_bug.cgi?id=160686 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0655 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Eyal Rozenberg changed: What|Removed |Added Depends on||140655 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140655 [Bug 140655] Page naming "right" and "left" is wrong for right-to-to left documents should be "odd" and "even" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160686] "Left Page" and "Right Page" are nonsensical and should be removed
https://bugs.documentfoundation.org/show_bug.cgi?id=160686 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0655 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 140655] Page naming "right" and "left" is wrong for right-to-to left documents should be "odd" and "even"
https://bugs.documentfoundation.org/show_bug.cgi?id=140655 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0686 Blocks||43808 --- Comment #11 from Eyal Rozenberg --- I now believe this bug should be marked INVALID, and have opened bug 160686 to promote the removal of these styles. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=43808 [Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160681] White background comment box drop down button in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=160681 Telesto changed: What|Removed |Added Keywords||bibisectRequest, regression -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160690] Animated GIF completely invisible in Edit mode (GIF has alpha-transparency)
https://bugs.documentfoundation.org/show_bug.cgi?id=160690 m_a_riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m_a_riosv --- Reproducible Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded and Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: faadf7c15593521c0ebceb043f82f916ee5ccf9d CPU threads: 16; OS: Windows 10.0 Build 22631; 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.
[Bug 160644] Upon opening, LibreOffice sometimes crashes (perhaps once a week)
https://bugs.documentfoundation.org/show_bug.cgi?id=160644 --- Comment #7 from Patrick Luby (volunteer) --- (In reply to Sam from comment #6) > There was another system crash today which occurred as soon as I asked > LibreOffice to print to PDF a Writer document. > > I now remember these crashes not only occur unpredictably when starting LO > but also when trying to print something from LO. > > Two more reports were generated after today's crash. I hope they give some > useful information. Still looks like Apple "fontd" background process is crashing macOS. I believe that fontd handles font loading so I wonder if you have a corrupted or unloadable font installed on your Mac. If you validate all of the fonts using the following steps, are there any fonts with warnings or errors?: 1. Launch the /Applications/Font Book application from the Finder 2. Select "All Fonts" in the sidebar on the left 3. Select one of the fonts and then select the Edit > Select All menu item to select all of the fonts 4. Select the File > Validate Selection menu item to start the validation process -- You are receiving this mail because: You are the assignee for the bug.
core.git: Branch 'feature/cib_contract49' - 3 commits - drawinglayer/source include/drawinglayer svx/source sw/uiconfig
drawinglayer/source/geometry/viewinformation2d.cxx| 21 drawinglayer/source/primitive2d/texthierarchyprimitive2d.cxx |3 drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx| 14 drawinglayer/source/processor2d/vclpixelprocessor2d.cxx | 11 include/drawinglayer/geometry/viewinformation2d.hxx |3 include/drawinglayer/primitive2d/texthierarchyprimitive2d.hxx | 23 svx/source/sdr/contact/objectcontactofpageview.cxx|2 svx/source/sdr/primitive2d/sdrattributecreator.cxx| 53 sw/uiconfig/swriter/ui/fldvarpage.ui | 647 -- 9 files changed, 362 insertions(+), 415 deletions(-) New commits: commit f9aa7d95ac68c39166342aff91a5777a565f2c1d Author: Oliver Specht AuthorDate: Wed Apr 10 17:11:10 2024 +0200 Commit: Thorsten Behrens CommitDate: Tue Apr 16 22:17:15 2024 +0200 tdf#160621 Redesign name and value fields in variabe fields dialog page The space available in the bottom of the dialog page is now used to make the input fields longer Change-Id: If936decbcc44ff356095fc291ff8306084c248ef diff --git a/sw/uiconfig/swriter/ui/fldvarpage.ui b/sw/uiconfig/swriter/ui/fldvarpage.ui index 4c6be9736980..9fd8c8f8a306 100644 --- a/sw/uiconfig/swriter/ui/fldvarpage.ui +++ b/sw/uiconfig/swriter/ui/fldvarpage.ui @@ -55,162 +55,273 @@ 12 True - + + True False -True -True -vertical -12 +6 +6 + + +True +False +start +Na_me: +True +name +0 + + +0 +0 + + + + +True +True +True +True + + +Type the name of the user-defined field to create. + + + + +1 +0 +2 + + - + True False +start +start +_Value: +True +value +0 + + +0 +1 + + + + +True +True True True -0 -none +in - + True True -6 True True -in - - -True -True -True -True -liststore1 -False -False -0 -False - - - - - - - - -0 - - - - - - -Lists the available field types. To add a field to your document, click a field type, click a field in the Select list, and then click Insert. - - + + +Enter the contents to add to a user-defined field. - - + + +1 +1 +2 + + + + + +True +False +end +6 + + True -False -_Type -True -0 - - - +True +True +Apply +center +image2 +True + + +Adds the user-defined field to the Select list. + + + + +0 +0 + + + + +True +True +True +Delete +center +image1 +True + + +Removes the user-defined field from the select list. You can only remove fields that are not used in the current document. + + + +1 +0 +
[Bug 142999] Problems with filter of rows and images after the file is saved with filter activated
https://bugs.documentfoundation.org/show_bug.cgi?id=142999 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #8 from Regina Henschel --- I get the error only if I open the xls file, which is attached to the mentioned Ask, and save it back as xls. When I save to ods, the images are all present. Tested with Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160681] White background comment box drop down button in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=160681 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from m_a_riosv --- Reproducible Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: faadf7c15593521c0ebceb043f82f916ee5ccf9d CPU threads: 16; OS: Windows 10.0 Build 22631; 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.
[Bug 160674] Paste on the position where context menu opened, instead of the original position
https://bugs.documentfoundation.org/show_bug.cgi?id=160674 --- Comment #5 from Telesto --- (In reply to Heiko Tietze from comment #3) > Maybe because most users copy/paste with shortcuts? I would use CTRL+C/ CTRL+V. But I have hard time to predict the outcome. The context menu part is actually something I use as fails safe. If CTRL+V doesn't deliver, maybe context menu does. I lack of clear idea how CTRL+V should function. Paste is defined by caret in Writer. By a cell in Calc. But where the paste on empty canvas? Right Click context menu has clear coordinates (in my mental model). In case of CTRL+V I have no idea what should be used. Nothing (current behaviour). The current mouse position? Or should a double left click on page add some temporal anchor which can be used reference: paste here [however again a gimmick/ requiring documentation. Not some natural state] * In a A3 page with zoom level 250% copy an image of the top right corner to the clipboasrd (CTRL+C).. Scroll to right bottom of the page CTRL+V nothing happens. I use context menu -> Paste. Agh... [Confusing feedback] * Say I want to replace an image. I copy ImageA. Select ImageB. Press CTRL+V. ImageB gets deselected. ImageA selected. ImageB being unchanged. There is Context Menu -> Replace. However that requires a external file (not possible from clipboard). I still have no clue how to replace an image using the clipboard. Spoken about: internal consistency within same the suite :-). Makes the learning curve rather bumpy ride. Accompanied with lots of frustration * In writer select object a + CTRL+C + CTRL+V results in no change (so say: source image overwritten by copy). Draw has different view on the matter, actually stacking copy's on top of source object. I likely unintendedly created duplicates which did go unnoticed. * With CTRL+V creating a duplicate, I still have to drag the object to the proper place. The copy is surely not intended to be on the same spot as the source. I can't control where CTRL+V pastes. It would nice if LEFT+MOUSE CLICK + CTRL+V or something like that would mean: paste here. --- >But no objection from my > side to take the position information, if available. I guess you expect the > source object's center to be on the target position - easy for simple > objects but quickly a challenge. So perhaps just top/left? I have quite a hard time understanding this. Do you mean to say: the right click x/y coordinates should be interpreted as the the top/left of the to be pasted object (shape/image). In that case, I tend to say yes. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160428] LibreOffice Draw Properties Position and Size often do not display
https://bugs.documentfoundation.org/show_bug.cgi?id=160428 m_a_riosv changed: What|Removed |Added Summary|LiberyOffice Draw |LibreOffice Draw Properties |Properties Position and |Position and Size often do |Size often do not display |not display Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #6 from m_a_riosv --- Thanks @Rober, I can reproduce now. It's curious that blank fields, are not the same with different shapes. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: faadf7c15593521c0ebceb043f82f916ee5ccf9d CPU threads: 16; OS: Windows 10.0 Build 22631; 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.
[Bug 131274] When opening a CSV file with Calc, the default template is ignored.
https://bugs.documentfoundation.org/show_bug.cgi?id=131274 --- Comment #4 from wpeat...@gmail.com --- I strongly disagree that this is not a bug. When you import a CSV file, Calc is clearly using some kind of template to determine styles, page settings, etc. But it's not using the user defined template. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 131274] When opening a CSV file with Calc, the default template is ignored.
https://bugs.documentfoundation.org/show_bug.cgi?id=131274 --- Comment #4 from wpeat...@gmail.com --- I strongly disagree that this is not a bug. When you import a CSV file, Calc is clearly using some kind of template to determine styles, page settings, etc. But it's not using the user defined template. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160644] Upon opening, LibreOffice sometimes crashes (perhaps once a week)
https://bugs.documentfoundation.org/show_bug.cgi?id=160644 --- Comment #6 from Sam --- There was another system crash today which occurred as soon as I asked LibreOffice to print to PDF a Writer document. I now remember these crashes not only occur unpredictably when starting LO but also when trying to print something from LO. Two more reports were generated after today's crash. I hope they give some useful information. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160644] Upon opening, LibreOffice sometimes crashes (perhaps once a week)
https://bugs.documentfoundation.org/show_bug.cgi?id=160644 --- Comment #5 from Sam --- Created attachment 193711 --> https://bugs.documentfoundation.org/attachment.cgi?id=193711=edit the report no. 3 generated by macOS -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160644] Upon opening, LibreOffice sometimes crashes (perhaps once a week)
https://bugs.documentfoundation.org/show_bug.cgi?id=160644 --- Comment #4 from Sam --- Created attachment 193710 --> https://bugs.documentfoundation.org/attachment.cgi?id=193710=edit the report no. 2 generated by macOS -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160693] Top borders of merged cells are not painted when the merged cell is partially visible
https://bugs.documentfoundation.org/show_bug.cgi?id=160693 --- Comment #2 from ady --- Although I don't repro this on Windows with a recent 24.8 alpha (or, alternatively, I am not understanding the STR), there is a similar issue in tdf#160654 (scrolling horizontally instead of vertically), which I can repro on Windows. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160696] CALC: Rounding for Time Value does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=160696 --- Comment #3 from Robert Großkopf --- (In reply to Eike Rathke from comment #2) > HH:MM:SS is a clock format, it does not round into seconds. If it did, then > 23:59:59.9 would result in 00:00:00 (24:00:00 but wrapped around), and along > with a date (like -MM-DD HH:MM:SS) it even would display 00:00:00 of the > next day. And what would be wrong if it does? The date has to show the next day, if rounded… -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159708] High CPU usage UI ribbon/menu
https://bugs.documentfoundation.org/show_bug.cgi?id=159708 --- Comment #11 from m_a_riosv --- Have you tested with other app, doing the same? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160428] LiberyOffice Draw Properties Position and Size often do not display
https://bugs.documentfoundation.org/show_bug.cgi?id=160428 --- Comment #5 from Robert Großkopf --- (In reply to m_a_riosv from comment #4) > I can't reproduce Please try with https://bugs.documentfoundation.org/attachment.cgi?id=193691 Description: https://bugs.documentfoundation.org/show_bug.cgi?id=160675#c0 Produces here the buggy behavior in every version since LO 7.5. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159598] Merging a whole column increases file size unnecessarily (comment 8)
https://bugs.documentfoundation.org/show_bug.cgi?id=159598 --- Comment #11 from ady --- (In reply to Stéphane Guillou (stragu) from comment #10) > Results for me: > - pre-merge ODS: 7.9 kb > - post-merge ODS (merged cell is C1:D1048576): 736.5 kb > > Even for a single merged column, I get 592.3 kb. The counterpart of the report (as in comment 8) is the time to open each of these, which is directly related to the initial problem in comment 0. Even if the size could be somehow reduced, if one consequence of such reduction would be additional time (to open, or to some other relevant action on the file), then the problem presented in comment 0 would remain (i.e. opening would take such a long time in certain systems that users would assume some crash/hang/corruption). -- You are receiving this mail because: You are the assignee for the bug.
core.git: Branch 'distro/collabora/co-24.04' - desktop/source
desktop/source/lib/init.cxx |8
1 file changed, 8 insertions(+)
New commits:
commit 83c5571bc6991749aa80aa87127dd56f53f9dee9
Author: Noel Grandin
AuthorDate: Mon Apr 15 16:10:54 2024 +0200
Commit: Caolán McNamara
CommitDate: Tue Apr 16 20:53:03 2024 +0200
preload BreakIterator for LOK
Change-Id: I22bea46d224f4020bb18d2826f23985fc2d8e492
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166129
Tested-by: Noel Grandin
Reviewed-by: Noel Grandin
(cherry picked from commit 42e175060c28ef339e3c96b51baa9a8d84ef2c82)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166095
Tested-by: Jenkins CollaboraOffice
Reviewed-by: Caolán McNamara
diff --git a/desktop/source/lib/init.cxx b/desktop/source/lib/init.cxx
index 04c46306f12e..fdf25b4cfeac 100644
--- a/desktop/source/lib/init.cxx
+++ b/desktop/source/lib/init.cxx
@@ -15,6 +15,7 @@
#include
#include
#include
+#include
#include
#include
@@ -134,6 +135,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -7633,6 +7635,12 @@ static void preloadData()
}
std::cerr << "
";
+std::cerr << "Preloading breakiterator: ";
+css::uno::Reference< css::i18n::XBreakIterator > xBreakIterator =
css::i18n::BreakIterator::create(xContext);
+css::i18n::LineBreakUserOptions aUserOptions;
+css::i18n::LineBreakHyphenationOptions aHyphOptions(
LinguMgr::GetHyphenator(), css::uno::Sequence(), 1 );
+xBreakIterator->getLineBreak("", /*nMaxBreakPos*/0, aLocales[0],
/*nMinBreakPos*/0, aHyphOptions, aUserOptions);
+
css::uno::Reference< css::ui::XAcceleratorConfiguration > xGlobalCfg =
css::ui::GlobalAcceleratorConfiguration::create(
comphelper::getProcessComponentContext());
xGlobalCfg->getAllKeyEvents();
