[Libreoffice-commits] core.git: 2 commits - comphelper/source include/comphelper sd/source
comphelper/source/misc/weakeventlistener.cxx |2
include/comphelper/weakeventlistener.hxx | 13 +--
sd/source/ui/slidesorter/cache/SlsBitmapCache.cxx | 82 --
sd/source/ui/slidesorter/cache/SlsBitmapCache.hxx | 12 ++-
4 files changed, 63 insertions(+), 46 deletions(-)
New commits:
commit 2767caa7958a0c98117494bf09ce5333af679c14
Author: Noel Grandin
AuthorDate: Fri Feb 17 14:00:07 2023 +0200
Commit: Noel Grandin
CommitDate: Sun Feb 19 07:33:47 2023 +
osl::Mutex->std::mutex in OWeakEventListenerAdapter
Change-Id: I3ebd6cfdb8ff76b2d1988c3c481ef4effa5c2964
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147262
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/comphelper/source/misc/weakeventlistener.cxx
b/comphelper/source/misc/weakeventlistener.cxx
index e8ce46590559..0543816d0593 100644
--- a/comphelper/source/misc/weakeventlistener.cxx
+++ b/comphelper/source/misc/weakeventlistener.cxx
@@ -55,7 +55,7 @@ namespace comphelper
}
-void SAL_CALL OWeakEventListenerAdapter::disposing( )
+void OWeakEventListenerAdapter::disposing( std::unique_lock&
/*rGuard*/ )
{
Reference< XComponent > xBroadcaster( getBroadcaster( ), UNO_QUERY );
OSL_ENSURE( xBroadcaster.is(), "OWeakEventListenerAdapter::disposing:
broadcaster is invalid in the meantime! How this?" );
diff --git a/include/comphelper/weakeventlistener.hxx
b/include/comphelper/weakeventlistener.hxx
index d64f302d8066..c4b4e79704c4 100644
--- a/include/comphelper/weakeventlistener.hxx
+++ b/include/comphelper/weakeventlistener.hxx
@@ -21,7 +21,7 @@
#define INCLUDED_COMPHELPER_WEAKEVENTLISTENER_HXX
#include
-#include
+#include
#include
#include
#include
@@ -44,7 +44,7 @@ namespace comphelper
holds it's listener hard. The adapter itself knows the real listener
as weak reference,
thus not affecting its life time.
*/
-class OWeakListenerAdapterBase : public cppu::BaseMutex
+class OWeakListenerAdapterBase
{
private:
css::uno::WeakReference< css::uno::XInterface >
@@ -98,7 +98,7 @@ namespace comphelper
as this can't be done in a generic way
*/
class OWeakListenerAdapter
-:public ::cppu::WeakComponentImplHelper< LISTENER >
+:public ::comphelper::WeakComponentImplHelper< LISTENER >
,public OWeakListenerAdapterBase
{
protected:
@@ -123,7 +123,7 @@ namespace comphelper
protected:
// OComponentHelper overridables
// to be overridden, again - the derived class should revoke the
listener from the broadcaster
-virtual void SAL_CALL disposing( ) override = 0;
+virtual void disposing( std::unique_lock& rGuard )
override = 0;
};
@@ -147,7 +147,7 @@ namespace comphelper
private:
using OWeakEventListenerAdapter_Base::disposing;
-virtual void SAL_CALL disposing( ) override;
+virtual void disposing( std::unique_lock& rGuard )
override;
};
@@ -159,8 +159,7 @@ namespace comphelper
const css::uno::Reference< css::uno::XWeak >& _rxListener,
const css::uno::Reference< BROADCASTER >& _rxBroadcaster
)
-: ::cppu::WeakComponentImplHelper< LISTENER >( m_aMutex )
-, OWeakListenerAdapterBase( _rxListener, _rxBroadcaster )
+: OWeakListenerAdapterBase( _rxListener, _rxBroadcaster )
{
}
commit 801cbe5410d44805945c2be616b284888a1e1b80
Author: Noel Grandin
AuthorDate: Fri Feb 17 15:30:58 2023 +0200
Commit: Noel Grandin
CommitDate: Sun Feb 19 07:33:34 2023 +
osl::Mutex->std::mutex in BitmapCache
Change-Id: I4ca8ac53e0d37aaf015e96963299acb5eb10f3b3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147267
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sd/source/ui/slidesorter/cache/SlsBitmapCache.cxx
b/sd/source/ui/slidesorter/cache/SlsBitmapCache.cxx
index 87c727408cfe..89acdc564bf5 100644
--- a/sd/source/ui/slidesorter/cache/SlsBitmapCache.cxx
+++ b/sd/source/ui/slidesorter/cache/SlsBitmapCache.cxx
@@ -140,7 +140,7 @@ BitmapCache::~BitmapCache()
void BitmapCache::Clear()
{
-::osl::MutexGuard aGuard (maMutex);
+std::unique_lock aGuard (maMutex);
mpBitmapContainer->clear();
mnNormalCacheSize = 0;
@@ -150,7 +150,7 @@ void BitmapCache::Clear()
bool BitmapCache::HasBitmap (const CacheKey& rKey)
{
-::osl::MutexGuard aGuard (maMutex);
+std::unique_lock aGuard (maMutex);
CacheBitmapContainer::iterator iEntry (mpBitmapContainer->find(rKey));
return (iEntry != mpBitmapContainer->end()
@@ -159,7 +159,7 @@ bool BitmapCache::HasBitmap (const CacheKey& rKey)
bool BitmapCache::BitmapIsUpToDate (const CacheKey& rKey)
{
-::osl::MutexGuard aGuard (maMutex);
+std::unique_lock aGuard (maMutex);
bool bIsUpToDate = false;
CacheBitmapContainer::iterator aIterator
[Libreoffice-bugs] [Bug 148601] Missing scrollbars in menus (interface bug since 7.0)
https://bugs.documentfoundation.org/show_bug.cgi?id=148601 BogdanB changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146076] [META] Find & Replace Regular Expressions
https://bugs.documentfoundation.org/show_bug.cgi?id=146076 Dieter changed: What|Removed |Added Depends on||34596 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=34596 [Bug 34596] Search and replace empty paragraphs in a Writer document with tables -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130480] search for regular expressions not usable any more
https://bugs.documentfoundation.org/show_bug.cgi?id=130480 Dieter changed: What|Removed |Added Depends on|34596 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=34596 [Bug 34596] Search and replace empty paragraphs in a Writer document with tables -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 34596] Search and replace empty paragraphs in a Writer document with tables
https://bugs.documentfoundation.org/show_bug.cgi?id=34596 Dieter changed: What|Removed |Added CC|dgp-m...@gmx.de | Blocks|130480 |146076 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=130480 [Bug 130480] search for regular expressions not usable any more https://bugs.documentfoundation.org/show_bug.cgi?id=146076 [Bug 146076] [META] Find & Replace Regular Expressions -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153724] New: A macro which is executed in older versions but not in newer versions.
https://bugs.documentfoundation.org/show_bug.cgi?id=153724 Bug ID: 153724 Summary: A macro which is executed in older versions but not in newer versions. Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: exodus.s...@gmail.com Description: newer versions refuses to execute almost all the macros. In my poor investigation, 6.4 is fine but 7.3 or later has this problem. sorry about my poor English. Steps to Reproduce: 1. Use 7.4 or later [maybe 7.0 or later] 2. Run the macro which quoted in "Other Information" down below. 3. 6.4 does it fine but 7.4 or newer stops it with error. Actual Results: It stops with error. Expected Results: I think this is a very big bug. I need the macro so I uninstalled 7.4 and reinstalled 6.4 because newer versions refuses to execute the macro. Reproducible: Always User Profile Reset: No Additional Info: Sub さかさことば2() Dim 選択セル As Range For Each 選択セル In Selection 選択セル.Value = StrReverse(選択セル.Value) Next 選択セル End Sub 3行マクロ～文字列をさかさに並び替える、文字列逆から読む～StrReverse 関数 https://kokodane.com/mini_macro28.htm -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153716] Comments on first page omitted during PDF export
https://bugs.documentfoundation.org/show_bug.cgi?id=153716 sdc.bla...@youmail.dk changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1 |0 --- Comment #1 from sdc.bla...@youmail.dk --- cannot confirm own bug report -- setting to UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153723] New: spell check
https://bugs.documentfoundation.org/show_bug.cgi?id=153723 Bug ID: 153723 Summary: spell check Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nlsov...@gmail.com I have had no problem with spell check until I installed version 7.5.0.3.. Now the spell check brings up a blank screen and doesn.t do any checking let alone correcting. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114278] [META] Style filter drop down list in Styles deck of Sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=114278 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||153722 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153722 [Bug 153722] Review needed of style groups "Chapter Styles" and "Text Styles" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153722] Review needed of style groups "Chapter Styles" and "Text Styles"
https://bugs.documentfoundation.org/show_bug.cgi?id=153722 sdc.bla...@youmail.dk changed: What|Removed |Added Keywords||needsUXEval Blocks||114278 CC||libreoffice-ux-advise@lists ||.freedesktop.org Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114278 [Bug 114278] [META] Style filter drop down list in Styles deck of Sidebar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153722] Review needed of style groups "Chapter Styles" and "Text Styles"
https://bugs.documentfoundation.org/show_bug.cgi?id=153722 sdc.bla...@youmail.dk changed: What|Removed |Added Keywords||needsUXEval Blocks||114278 CC||libreoffice-ux-advise@lists ||.freedesktop.org Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114278 [Bug 114278] [META] Style filter drop down list in Styles deck of Sidebar -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153722] New: Review needed of style groups "Chapter Styles" and "Text Styles"
https://bugs.documentfoundation.org/show_bug.cgi?id=153722 Bug ID: 153722 Summary: Review needed of style groups "Chapter Styles" and "Text Styles" Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sdc.bla...@youmail.dk Created attachment 185468 --> https://bugs.documentfoundation.org/attachment.cgi?id=185468=edit screenshot of "Text Styles" category Open Styles deck. Use category select dropdown box (at bottom), select 1. "Chapter Styles" Actual: Appendix Subtitle Title Expected: ?? 2. "Text Styles" Actual: see attachment. Some observations. 1. "Chapter" seems an unfortunate choice for three PS with outline level "Text Body" (could not find any mention of "chapter styles" in BZ) 2. For "Text Styles", seems unfortunate to have Heading N mixed with the other PS. 3. Maybe "Outline Styles" or "Book Styles" or "Document Styles" (as possible categories) would inspire a better selection. Initial motivation of ticket: To change the word "Chapter" in this dialog. Subsequent motivation: to ask UXEval to consider whether some improvements are needed in relation to these two categories. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153370] Language drop down menu obscured in Review panel in References screen in Collabora on iPad
https://bugs.documentfoundation.org/show_bug.cgi?id=153370 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 153694] Localized Bold/Italic/Underline icons
https://bugs.documentfoundation.org/show_bug.cgi?id=153694 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153375] Create an user profile comparator. (registrymodifications.xcu)
https://bugs.documentfoundation.org/show_bug.cgi?id=153375 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 153694] Localized Bold/Italic/Underline icons
https://bugs.documentfoundation.org/show_bug.cgi?id=153694 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153565] Minimally responsive (sluggish) and crashing almost randomly
https://bugs.documentfoundation.org/show_bug.cgi?id=153565 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153565] Minimally responsive (sluggish) and crashing almost randomly
https://bugs.documentfoundation.org/show_bug.cgi?id=153565 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150538] Spreadsheet crashes in V. 7.4.0.3 & earlier versions
https://bugs.documentfoundation.org/show_bug.cgi?id=150538 --- Comment #3 from QA Administrators --- Dear Tec, 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 144014] I cannot create a New Style for internet links, without the system Internet Link overriding my style.
https://bugs.documentfoundation.org/show_bug.cgi?id=144014 --- Comment #4 from QA Administrators --- Dear nirodhaha, 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 142919] Can't open Google Drive documents from nautilus on with Flatpak LibreOffice on Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=142919 --- Comment #5 from QA Administrators --- Dear Finley Turner-Hall, 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 34596] Search and replace empty paragraphs in a Writer document with tables
https://bugs.documentfoundation.org/show_bug.cgi?id=34596 --- Comment #15 from QA Administrators --- Dear Antanas, 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 140105] The TAB character is removed under certain conditions (see comment 6)
https://bugs.documentfoundation.org/show_bug.cgi?id=140105 --- Comment #7 from QA Administrators --- Dear Dan Sczygelski, 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 140496] EOL character is not processed correctly when opening xlsx-files with cells containing multi-line text and hyperlinks
https://bugs.documentfoundation.org/show_bug.cgi?id=140496 --- Comment #5 from QA Administrators --- Dear Sergey Nemna, 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 140472] hyperlink does not reach target with line break
https://bugs.documentfoundation.org/show_bug.cgi?id=140472 --- Comment #5 from QA Administrators --- Dear TorrAB, 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 127524] TAB STOPS: Tab stop gets lost in a line that starts with "- ", "* " or "+ " after pressing return
https://bugs.documentfoundation.org/show_bug.cgi?id=127524 --- Comment #2 from QA Administrators --- Dear Gozo Gozoso, 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 123069] No Fly Through Transition in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=123069 --- Comment #4 from QA Administrators --- Dear Daniel, 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 123995] [EDITING] index entry: impossible to add 1st and/or 2nd key in user-defined entry (field greyed out)
https://bugs.documentfoundation.org/show_bug.cgi?id=123995 --- Comment #6 from QA Administrators --- Dear soffioalcuore, 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 116343] picture zoom using mouse does not work sometimes
https://bugs.documentfoundation.org/show_bug.cgi?id=116343 --- Comment #11 from QA Administrators --- Dear Dr. Matthias Weisser, 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 120284] Autocorrection wrong at word tail - looks it loose first char of pattern when no space before
https://bugs.documentfoundation.org/show_bug.cgi?id=120284 --- Comment #7 from QA Administrators --- Dear alexrayne, 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 150164] PDF exporter's "Export outlines as named destinations" does not export outlines, but bookmarks
https://bugs.documentfoundation.org/show_bug.cgi?id=150164 sdc.bla...@youmail.dk changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #11 from sdc.bla...@youmail.dk --- (In reply to gabriel.crabbe from comment #9) > The phrasing "names of objects" is overly broad: only LibreOffice bookmarks > are exported (just tested with LibreOffice 7.5.0). This phrase appears in the following sentence in the help page [1]. "Enable the checkbox to export the names of objects in your document as valid bookmark targets." This raises the following question -- which I will ask to UXEval -- Is the intended behavior of this option: (a) to only export LO bookmarks, or (b) should "names of objects" be interpreted as referring to the "Name" property of images, tables, frames, and OLE objects, which could plausibly be exported as named destinations. If (a), then the needed corrections are being addressed here. If (b), then (maybe) a bug report must be filed. [1] https://help.libreoffice.org/7.6/en-US/text/shared/01/ref_pdf_export_links.html -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 150164] PDF exporter's "Export outlines as named destinations" does not export outlines, but bookmarks
https://bugs.documentfoundation.org/show_bug.cgi?id=150164 sdc.bla...@youmail.dk changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #11 from sdc.bla...@youmail.dk --- (In reply to gabriel.crabbe from comment #9) > The phrasing "names of objects" is overly broad: only LibreOffice bookmarks > are exported (just tested with LibreOffice 7.5.0). This phrase appears in the following sentence in the help page [1]. "Enable the checkbox to export the names of objects in your document as valid bookmark targets." This raises the following question -- which I will ask to UXEval -- Is the intended behavior of this option: (a) to only export LO bookmarks, or (b) should "names of objects" be interpreted as referring to the "Name" property of images, tables, frames, and OLE objects, which could plausibly be exported as named destinations. If (a), then the needed corrections are being addressed here. If (b), then (maybe) a bug report must be filed. [1] https://help.libreoffice.org/7.6/en-US/text/shared/01/ref_pdf_export_links.html -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 150164] PDF exporter's "Export outlines as named destinations" does not export outlines, but bookmarks
https://bugs.documentfoundation.org/show_bug.cgi?id=150164 --- Comment #10 from sdc.bla...@youmail.dk --- (In reply to gabriel.crabbe from comment #9) Many thanks for helpful detailed answers. > I propose the following text for both the extended tip and the help page: Excellent proposal. > Enable the checkbox to export the bookmarks (targets of references) in your > document as PDF named destinations. This allows you to create links to > specific locations in your document. Three followup questions. 1. The first sentence ends with "PDF named destinations", which makes me wonder if the checkbox label should be: [] Export bookmarks as PDF named destinations not: [] Export bookmarks as named destinations Do you have any intuition/opinion about which might be a preferred choice? For example, would the first be less ambiguous than the second? 2. First sentence: Is "targets of references" needed? seems like it is included as a way to explain what "bookmarks" means -- but if that is the reason, it does not seem like a good use of extended tip. 3. Alternative proposal for second sentence: "You can then create URL links to these locations in the PDF document." (reasons can be supplied) > I've also taken the liberty ... You are welcome to change the summary, but nothing appears to have changed. > an "outline export" new feature (hypothetical new issue). If you think the idea deserves consideration, then please file a new bug report. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 044aefc0231d0d066a67600ca5419da51194858b Author: Seth Chaiklin AuthorDate: Sun Feb 19 01:45:39 2023 + Commit: Gerrit Code Review CommitDate: Sun Feb 19 01:45:39 2023 + Update git submodules * Update helpcontent2 from branch 'master' to bdf9af4c8847ac03d1a836f6cfc9f49053ddd95d - tdf#144493 (related) command name changes require updating also icons for "Move Chapter Up" and "Move Chapter Down" corrected Change-Id: I09671ba5431ce969757f64c5d1892f6f6f0f399d Reviewed-on: https://gerrit.libreoffice.org/c/help/+/147253 Reviewed-by: Seth Chaiklin Tested-by: Jenkins diff --git a/helpcontent2 b/helpcontent2 index 72dcc8952e24..bdf9af4c8847 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 72dcc8952e242a86c3e328ca285cd17424008c77 +Subproject commit bdf9af4c8847ac03d1a836f6cfc9f49053ddd95d
[Libreoffice-commits] help.git: source/text
source/text/swriter/01/0211.xhp | 28 ++-- 1 file changed, 14 insertions(+), 14 deletions(-) New commits: commit bdf9af4c8847ac03d1a836f6cfc9f49053ddd95d Author: Seth Chaiklin AuthorDate: Sun Feb 19 01:06:23 2023 + Commit: Seth Chaiklin CommitDate: Sun Feb 19 01:45:38 2023 + tdf#144493 (related) command name changes require updating also icons for "Move Chapter Up" and "Move Chapter Down" corrected Change-Id: I09671ba5431ce969757f64c5d1892f6f6f0f399d Reviewed-on: https://gerrit.libreoffice.org/c/help/+/147253 Reviewed-by: Seth Chaiklin Tested-by: Jenkins diff --git a/source/text/swriter/01/0211.xhp b/source/text/swriter/01/0211.xhp index 1d5d528381..c6660201d0 100644 --- a/source/text/swriter/01/0211.xhp +++ b/source/text/swriter/01/0211.xhp @@ -130,7 +130,7 @@ Heading item -Collapse/Expand All, Go to, Select, Delete, Promote Chapter, Demote Chapter, Promote Level, Demote Level, Outline Content Visibility, Outline Tracking, Outline Level +Collapse/Expand All, Go to, Select, Delete, Move Chapter Up, Move Chapter Down, Promote Outline Level, Demote Outline Level, Outline Content Visibility, Outline Tracking, Outline Level @@ -316,7 +316,7 @@ A hidden section in a document appears gray in the Navigator, and displays the text "hidden" when you rest the mouse pointer over it. The same applies to header and footer contents of Page Styles that are not used in a document, and hidden contents in tables, frames, graphics, OLE objects, and indexes. - Toggle Master View +Toggle Master View Switches between master view and normal view if a master document is open. Switches between master view and normal view if a master document is open. @@ -433,64 +433,64 @@ -Promote Level +Promote Outline Level Increases the outline level of the selected heading, and the headings that occur below the heading, by one. To only increase the outline level of the selected heading, hold down CommandCtrl, and then click this icon. - Icon Promote level + Icon Promote Outline Level - Promote level + Promote Outline Level -Demote Level +Demote Outline Level Decreases the outline level of the selected heading, and the headings that occur below the heading, by one. To only decrease the outline level of the selected heading, hold down CommandCtrl, and then click this icon. - Icon Demote level + Icon Demote Outline Level - Demote level + Demote Outline Level -Promote Chapter +Move Chapter Up Moves the selected heading, and the text below the heading, up one heading position in the Navigator and in the document. To move only the selected heading and not the text associated with the heading, hold down CommandCtrl, and then click this icon. - Icon Chapter Up + Icon Move Chapter Up - Chapter Up + Move Chapter Up -Demote Chapter +Move Chapter Down Moves the selected heading, and the text below the heading, down one heading position in the Navigator and in the document. To move only the selected heading and not the text associated with the heading, hold down CommandCtrl, and then click this icon. - Icon Chapter down + Icon Move Chapter Down - Chapter down + Move Chapter Down
[Libreoffice-bugs] [Bug 105628] Creating a ToC with page numbering by chapter (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=105628 --- Comment #19 from sdc.bla...@youmail.dk --- (In reply to sdc.blanco from comment #14) > There is an additional problem -- > there is a blank space between the Heading (Chapter No.) and the page > number. Bug 114773 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 105628] Creating a ToC with page numbering by chapter (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=105628 --- Comment #19 from sdc.bla...@youmail.dk --- (In reply to sdc.blanco from comment #14) > There is an additional problem -- > there is a blank space between the Heading (Chapter No.) and the page > number. Bug 114773 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153721] Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=153721 --- Comment #1 from sdc.bla...@youmail.dk --- Same problem with “Delete Chapter” Maybe: “Delete Heading and Text” or “Delete: Heading and Text” -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||153721 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153721 [Bug 153721] Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153721] Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=153721 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||103030 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103030 [Bug 103030] [META] Navigator sidebar deck and floating window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153721] New: Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=153721 Bug ID: 153721 Summary: Rename "Move Chapter Up/Down" to "Move Heading+Text Up/Down" in Navigator Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sdc.bla...@youmail.dk "Move Chapter Up/Down" commands in Navigator move "headings with the immediately following text until the next heading". Main problem is that "chapter" is wrong/misleading about action of command. Proposal: "Move Chapter Up" -> "Move Heading and Text Up" "Move Chapter Down" -> "Move Heading and Text Down" Variations: 1. If length is a problem, maybe drop "Move" 2. Put important action first: Up: Heading and Text Down: Heading and Text -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 139302] [UI] Demote Chapter in navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=139302 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4493 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 139302] [UI] Demote Chapter in navigator
https://bugs.documentfoundation.org/show_bug.cgi?id=139302 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4493 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121626] When copying sheets or objects (checkboxes/charts) references in the objects are not updated
https://bugs.documentfoundation.org/show_bug.cgi?id=121626 --- Comment #8 from m.a.riosv --- Created attachment 185467 --> https://bugs.documentfoundation.org/attachment.cgi?id=185467=edit Chart sample to test copy. On the sample file copying chart in H2, anywhere, always refers to the range of the copied chart, no way to change it. Maybe the easy way could be asking when copying. I don't know if it would be possible to have the chars with relative addresses instead of absolute, so when copying it can change to adapt the new chart relative to their position. Still with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9788a565b3241d1bd62394b9e29c322361d05f80 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153720] New: Bar chart: data stacks are showed in reverse order.
https://bugs.documentfoundation.org/show_bug.cgi?id=153720 Bug ID: 153720 Summary: Bar chart: data stacks are showed in reverse order. Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Chart Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: miguelange...@libreoffice.org See attached file, Name 'j' it's at the top Name 'a' it's at the bottom. BTW, there is not an option to reverse order. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 9788a565b3241d1bd62394b9e29c322361d05f80 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153719] New: 7.5 BASIC shell function fails (flatpak and snap versions)
https://bugs.documentfoundation.org/show_bug.cgi?id=153719
Bug ID: 153719
Summary: 7.5 BASIC shell function fails (flatpak and snap
versions)
Product: LibreOffice
Version: 7.5.0.3 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: BASIC
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: s...@hevanet.com
Description:
BASIC Macros that invoke executuables via the shell function throw a "BASIC
runtime error. File not found." Same macros work fine in the current (K)Ubuntu
7.3.7.2 package.
(I haven't previously run LibreOffice as a snap or flatpak.)
Steps to Reproduce:
1. Execute a macro with this shell command: shell("/usr/bin/konsole",2)
2.
3.
Actual Results:
Macro editor launches, highlighting the "shell" line of the macro, and a box
shows the error message: BASIC runtime error. File not found.
Expected Results:
The software should have launched the desired application, in this case konsole
(but, in my use case, a LibreOffice program).
Reproducible: Always
User Profile Reset: Yes
Additional Info:
I hope that, when Ubuntu ships 7.5, this will be gone. Maybe it's an artifact
of using snap or flatpak -- something I haven't done with LibreOffice before.
Best of luck, and thanks for all you do to make LibreOffice great!
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153565] Minimally responsive (sluggish) and crashing almost randomly
https://bugs.documentfoundation.org/show_bug.cgi?id=153565 --- Comment #3 from fpecq...@comcast.net --- I did have "UI Render: Skia/Vulkan" in the about help window so I disabled Sika. I will let you know how it turns out. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153718] EDITING In a Calc table, the default document language setting is not honored throughout the table. Instead, some cells are set to English(USA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153718 --- Comment #2 from ben@eml.cc --- Created attachment 185466 --> https://bugs.documentfoundation.org/attachment.cgi?id=185466=edit Context menu in offending cell, option to mark as German word, English suggestions -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153718] EDITING In a Calc table, the default document language setting is not honored throughout the table. Instead, some cells are set to English(USA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153718 ben@eml.cc changed: What|Removed |Added CC||ben@eml.cc --- Comment #1 from ben@eml.cc --- Created attachment 185465 --> https://bugs.documentfoundation.org/attachment.cgi?id=185465=edit Spreadsheet with German Document language, individual cells makred as wrong -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153718] New: EDITING In a Calc table, the default document language setting is not honored throughout the table. Instead, some cells are set to English(USA)
https://bugs.documentfoundation.org/show_bug.cgi?id=153718 Bug ID: 153718 Summary: EDITING In a Calc table, the default document language setting is not honored throughout the table. Instead, some cells are set to English(USA) Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ben@eml.cc Description: My default language as per settings is German(Austria). In a table I typed, where each word contains one word, a (seemingly random) handful of - correctly spelled - German words are marked as incorrect. When double-clicking in the cell and right-clicking on the underlined word, English words are suggested instead and the option "this word is German" appears. I take it that Calc seems to think this word is English. I selected the entire table and clicked the language setting in the center of bottom panel to confirm the German(Austria) language, but nothing changed, several individual cells are still marked as wrong (English). I don't use Calc a lot, trying to reproduce it, I opened several existing .ods files and found one more that had an English cell in the middle of a German document. Steps to Reproduce: 1. Set LO default document language to German(Austria) 2. open a spreadsheet containing German language and set spellchecker language to German(Austria) for entire document 3. Check if some correctly spelled words are marked as wrong. 4. Check if suggestions are English or German Actual Results: Re-applying the default language manually, some random cells to not pick up the setting and remain in English Expected Results: When setting the document language to X (German(Austria) in my case), this should apply to the entire document without exception. Reproducible: Sometimes User Profile Reset: Yes Additional Info: I cannot tell if this is language-specific. I copied some cells from a table in an .odt document over into the offending spreadsheet. I thought maybe they are the ones seen as English, but a) some other cells I had manually typed are also marked wrong and b) the original .odt doc is also set to German(Austria). However, if cells copied over from another document were the offenders, manually setting the document language should still turn them all to default. It shouldn't be necessary to tell Calc for each cell individually that it's not English. But how that English snuck in there in the first place is also a mystery. German(Austria) is the default setting for my OS (Manjaro) which Lo came preinstalled on. I did not manually adjust the language setting in LO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150164] PDF exporter's "Export outlines as named destinations" does not export outlines, but bookmarks
https://bugs.documentfoundation.org/show_bug.cgi?id=150164 gabriel.cra...@outlook.com changed: What|Removed |Added Status|NEEDINFO|NEW Summary|PDF exporter's "Export |PDF exporter's "Export |outlines as named |outlines as named |destinations" should export |destinations" does not |outlines, not bookmarks |export outlines, but ||bookmarks --- Comment #9 from gabriel.cra...@outlook.com --- > 1. Just to be sure: the place where you want a change is found by: > > File > Export as > Export as PDF > Links tab > > and on the tab: [] "Export outlines as named destinations" Correct. > 2. The patch should change the word "outlines" in that label to "bookmarks" Correct. > 3. There is an extended tip for this control. If you do not have extended > tips > enabled, then press Shift+F1 (the mouse cursor gets a question mark > beside it), > and hover over the line with the checkbox. My understanding is that the tip is inaccurate. The phrasing "names of objects" is overly broad: only LibreOffice bookmarks are exported (just tested with LibreOffice 7.5.0). Moreover, they are not exported as "valid bookmark targets" (presumably PDF bookmarks, which is incorrect), but as "named destinations". > 4. Similarly, could you kindly look at the help page for this control: In addition to the inaccuracies reported above, the sentence "The bookmarks [...] in PDF files can be defined as rectangular areas." is incorrect. PDF bookmarks are another name for outline items. Even substituting "named destinations" for "bookmarks" does not fix the inaccuracy, as neither are "rectangular areas". The PDF Reference version 1.6, section 8.2.1, defines "destination" as: A destination defines a particular view of a document, consisting of the following items: • The page of the document to be displayed • The location of the document window on that page • The magnification (zoom) factor to use when displaying the page Of which "named destinations" are destinations referenced by a string (their name). I do not think it's useful to delve down into the specifics of what is a named destination, however, which is why I propose the following text for both the extended tip and the help page: Enable the checkbox to export the bookmarks (targets of references) in your document as PDF named destinations. This allows you to create links to specific locations in your document. I've also taken the liberty to revert @Buovjaga's edit, as it adds to the confusion between a mislabeled "bookmark export" feature (this issue) and an "outline export" new feature (hypothetical new issue). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153707] NPV function error with big number
https://bugs.documentfoundation.org/show_bug.cgi?id=153707 --- Comment #4 from Xaxa --- Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153707] NPV function error with big number
https://bugs.documentfoundation.org/show_bug.cgi?id=153707 Xaxa changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153707] NPV function error with big number
https://bugs.documentfoundation.org/show_bug.cgi?id=153707 --- Comment #3 from ady --- (In reply to Xaxa from comment #2) > It is not intuitive to know to expand the width of the column. Could we > please display the result however long it is? Other platform (Google > spreadsheet, MS Excel) still displays the number even if it is long. > > How much effort does it need to always display the number if it is long? If > it is too much effort, we should display a message "number is too long, > please expand the column". Being able to display X amount of characters in one column depends on several factors: _ column width _ font type _ font size _ amount of characters to be displayed _ zoom factor _ other attributes of the relevant cell As for the last one, you could select the cell (or the entire column) and go to menu format > cell > alignment > shrink to fit cell size. This is only one of several alternatives. FYI, Excel uses the same exact method, whenever the combination of the aforementioned factors results in not enough physical width. There is no physical way to display any-and-all possible results of an unknown width within a limited column width. You have to modify at least one of the listed elements. The only exception is when the adjacent cell is absolutely blank empty, so the content text "spills" on to the neighboring cell. Now, for future reference, you could first go to ask.libreoffice.org and try to solve your doubts there. In many cases your question would be already answered. A web search could also help (e.g. "Calc ### error" or "Excel ### error" or whatever). There is also help.libreoffice.org . I already closed this report as NAB before, and you re-opened it. I provided more than enough details. I'll leave the report in the same status as you left it, but IMO it should be closed as NOTABUG again. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153717] New: Working directory of recovered file is assumed to be the one of newly opened file
https://bugs.documentfoundation.org/show_bug.cgi?id=153717 Bug ID: 153717 Summary: Working directory of recovered file is assumed to be the one of newly opened file Product: LibreOffice Version: 7.3.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m...@protonmail.ch So.. it's a bit hard to explain the issue in a single sentence, so I'll just list the step that lead me there: * make a new document (it was in calc for me, but I don't think this matters) * write anything to it (but still keep it temporary, i.e. don't save anything) * force the pc off (or I guess killing the soffice processes could do it as well) * open a pre-existing document (it was a .doc for me, but again I don't think it matters) * the document recovery window should pop up and ask you if you want to try saving the old work * say yes and after it has opened for good, close the other document * you will still be unable to delete the folder the later is in, because the rescued document has an handle opened on that completely foreign folder -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153527] LibreOffice 7.5 Calc: unable to apply formatting to all cells in spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=153527
--- Comment #11 from ady ---
(In reply to V Stuart Foote from comment #10)
> As to some edit engine cyclic application of the +A selection--seems
> overly complex, and you'd never be sure what you'd selected (you can't see
> the last cell selected).
FWIW, having "steps" for +A is what Excel already does (see bug 131916
comment 14 regarding [CTRL]+[A]). Such behavior does not contradict whichever
other decision about which action is applied to which ranges. In fact, by
imitating Excel in this regard the "mistake" of users applying some attribute
to the entire worksheet is reduced, while letting users _know_ that they are
applying it just to the selected area. IOW, it brings mostly pros, especially
in comparison to the current behavior.
Regarding not seeing the last cell, I don't understand why that is relevant in
any case. At any rate, users get "surprised" by the result. In some cases, it
is a welcome result, whereas in others, it might be an eventual "why is this
cell not formatted as I expected?".
I understand the performance issue. I happen to disagree that _forcing_
unexpected results on users is the best that can be done. When users complain
about unexpected results, they receive some explanation, or at least a hint,
and NAB. I think that allowing "steps" in +A behavior would reduce the
amount of "surprises". If then a user complains about performance when
selecting the entire worksheet (which would replace the other complains), the
response would also be about a UX decision, with a relevant comment about
workarounds ("modify the default cell style").
I am not a developer. My comments come from a user's POV only. It seems strange
to _silently force_ users (against the behavior they are used to and expect,
from prior experience), when there might be alternatives, especially when the
product is named _libre_ :p).
IDK whether having an option to "allow" applying attributes to an entire
worksheet is an adequate solution. I do know that having "steps" for +A
should be welcome (because, in comparison to the current status, it brings more
freedom and efficiency). Whichever the case, until users are _somehow_
"allowed" to see their actions applied to the selected range of cells (with
whichever pros and cons, as with anything), these types of bug reports will
keep showing up, simply because the behavior is unexpected by users,
independently of whichever logical and justified reasoning developers could
present.
Let me put it this way. Current answer: "You cannot do that, even when you
expected that result". Alternative answer: "You pressed +A three times in
order to select the entire worksheet and the reaction from Calc is not
absolutely immediate? Well, you have the choice to select only the relevant
areas of your worksheet, and work faster; or you could change the default cell
style; but if you anyway decide to select the entire worksheet with 10^6
columns (or whatever), please be patient".
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153527] LibreOffice 7.5 Calc: unable to apply formatting to all cells in spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=153527
--- Comment #11 from ady ---
(In reply to V Stuart Foote from comment #10)
> As to some edit engine cyclic application of the +A selection--seems
> overly complex, and you'd never be sure what you'd selected (you can't see
> the last cell selected).
FWIW, having "steps" for +A is what Excel already does (see bug 131916
comment 14 regarding [CTRL]+[A]). Such behavior does not contradict whichever
other decision about which action is applied to which ranges. In fact, by
imitating Excel in this regard the "mistake" of users applying some attribute
to the entire worksheet is reduced, while letting users _know_ that they are
applying it just to the selected area. IOW, it brings mostly pros, especially
in comparison to the current behavior.
Regarding not seeing the last cell, I don't understand why that is relevant in
any case. At any rate, users get "surprised" by the result. In some cases, it
is a welcome result, whereas in others, it might be an eventual "why is this
cell not formatted as I expected?".
I understand the performance issue. I happen to disagree that _forcing_
unexpected results on users is the best that can be done. When users complain
about unexpected results, they receive some explanation, or at least a hint,
and NAB. I think that allowing "steps" in +A behavior would reduce the
amount of "surprises". If then a user complains about performance when
selecting the entire worksheet (which would replace the other complains), the
response would also be about a UX decision, with a relevant comment about
workarounds ("modify the default cell style").
I am not a developer. My comments come from a user's POV only. It seems strange
to _silently force_ users (against the behavior they are used to and expect,
from prior experience), when there might be alternatives, especially when the
product is named _libre_ :p).
IDK whether having an option to "allow" applying attributes to an entire
worksheet is an adequate solution. I do know that having "steps" for +A
should be welcome (because, in comparison to the current status, it brings more
freedom and efficiency). Whichever the case, until users are _somehow_
"allowed" to see their actions applied to the selected range of cells (with
whichever pros and cons, as with anything), these types of bug reports will
keep showing up, simply because the behavior is unexpected by users,
independently of whichever logical and justified reasoning developers could
present.
Let me put it this way. Current answer: "You cannot do that, even when you
expected that result". Alternative answer: "You pressed +A three times in
order to select the entire worksheet and the reaction from Calc is not
absolutely immediate? Well, you have the choice to select only the relevant
areas of your worksheet, and work faster; or you could change the default cell
style; but if you anyway decide to select the entire worksheet with 10^6
columns (or whatever), please be patient".
--
You are receiving this mail because:
You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 120131] Include font substitutions for fonts commonly used in MS Office for which we bundle alternatives
https://bugs.documentfoundation.org/show_bug.cgi?id=120131 Eyal Rozenberg changed: What|Removed |Added Keywords||needsDevEval --- Comment #12 from Eyal Rozenberg --- This should not be difficult, since it's just adding some table entries. As for the discussion on bug 64509 - it did not progress to an adoption of the suggestions here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145936] FORMATTING: Changing text page size changes the page style for endnotes, and hides part of the endnotes
https://bugs.documentfoundation.org/show_bug.cgi?id=145936 Caolán McNamara changed: What|Removed |Added Regression By|Caolán McNamara | --- Comment #8 from Caolán McNamara --- caolanm->raal: I think that bisect doesn't really help. In the version without that fix add an initial set of adding a single character to the document before following the other steps (this sets the document to "modified"). Then after that, format page, and set height to 5cm, and ok and the same behavior is seen without that commit which just faithfully recognized that there was a modification done to the document by changing a page style. If I bisect with that extra step then I get the result of: commit c927ea4c5d8a9ede979e17c09c2303854ccdebec Author: Muhammet Kara Date: Mon Jun 24 01:46:42 2019 +0300 Sync page orientation of Endnote page Description: When changing the default page style to have a different orientation, end-notes are placed on a page with a custom ‘Endnote’ page style. This style does not inherit its orientation from the default style. Repro: Create a blank document, insert→End Note, Format→Page in the first page, select the Page tab, and alter the Orientation to Landscape, ‘Ok’. The End-note page should update its orientation too. NB. If the Endnote page style is manually set to a different value in a document template it will remain in the selected orientation. After this patch, Default style and the Endnote style have their orientations synced after each run of the Format > Page dialog. Ideally, this should be solved by resolving tdf#41316 on master: Page styles should support hierarchical parent-child relationships (like paragraph or character styles) Change-Id: I255b470d1aebb897f50a4a74b8678b771ffbab28 Reviewed-on: https://gerrit.libreoffice.org/79869 Tested-by: Jenkins CollaboraOffice Reviewed-by: Andras Timar Reviewed-on: https://gerrit.libreoffice.org/82173 Tested-by: Jenkins Reviewed-by: Muhammet Kara If I go back to the oldest version I have, and manually toggle the "endnote" page style from portrait to landscape then I think I get the odd behavior too. So the change of the endnote orientation along with the default page style orientation was deliberate, and not in itself a bad idea, but the result is unsatisfactory I guess. One possible tweak might be to only do the "syncEndnoteOrientation" if the default page style paper size matches the endnote page style paper size? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140314] Extensions button in Start Center should not point to localised extensions site URLs
https://bugs.documentfoundation.org/show_bug.cgi?id=140314 Hossein changed: What|Removed |Added Whiteboard||reviewed:2023 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153703] FILESAVE Emojis are not shown when exporting document to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=153703 خالد حسني changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from خالد حسني --- EmojiOne Color is an OpenType-SVG font, we don't currently support such fonts in PDF export. I suggest you use other fonts like Noto Color Emoji, which are supported starting from LibreOffice 7.5.0. *** This bug has been marked as a duplicate of bug 105488 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105488] Support multi-colored fonts using SVG table
https://bugs.documentfoundation.org/show_bug.cgi?id=105488 خالد حسني changed: What|Removed |Added CC||ben@eml.cc --- Comment #9 from خالد حسني --- *** Bug 153703 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: include/comphelper toolkit/source
include/comphelper/compbase.hxx |5
toolkit/source/controls/grid/defaultgridcolumnmodel.cxx | 130
2 files changed, 70 insertions(+), 65 deletions(-)
New commits:
commit 76bdc40cc3157a8ac98332047f8edbc4008f5392
Author: Noel Grandin
AuthorDate: Fri Feb 17 14:23:52 2023 +0200
Commit: Noel Grandin
CommitDate: Sat Feb 18 20:40:37 2023 +
osl::Mutex->std::mutex in DefaultGridColumnModel
Change-Id: Ie3df092b013f10b36c85028fe3b9966d58b22005
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147264
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/include/comphelper/compbase.hxx b/include/comphelper/compbase.hxx
index 38380ede20d0..ad34ed7007ea 100644
--- a/include/comphelper/compbase.hxx
+++ b/include/comphelper/compbase.hxx
@@ -50,6 +50,11 @@ public:
virtual void disposing(std::unique_lock&);
protected:
+void throwIfDisposed(std::unique_lock&)
+{
+if (m_bDisposed)
+throw css::lang::DisposedException(OUString(),
static_cast(this));
+}
comphelper::OInterfaceContainerHelper4
maEventListeners;
mutable std::mutex m_aMutex;
bool m_bDisposed = false;
diff --git a/toolkit/source/controls/grid/defaultgridcolumnmodel.cxx
b/toolkit/source/controls/grid/defaultgridcolumnmodel.cxx
index 64cf2a61b3e2..f498001d1173 100644
--- a/toolkit/source/controls/grid/defaultgridcolumnmodel.cxx
+++ b/toolkit/source/controls/grid/defaultgridcolumnmodel.cxx
@@ -29,9 +29,8 @@
#include
#include
#include
-#include
-#include
-#include
+#include
+#include
#include
#include
#include
@@ -49,12 +48,11 @@ using namespace toolkit;
namespace {
-typedef ::cppu::WeakComponentImplHelper< css::awt::grid::XGridColumnModel
+typedef ::comphelper::WeakComponentImplHelper<
css::awt::grid::XGridColumnModel
, css::lang::XServiceInfo
> DefaultGridColumnModel_Base;
-class DefaultGridColumnModel:public ::cppu::BaseMutex
-,public DefaultGridColumnModel_Base
+class DefaultGridColumnModel : public DefaultGridColumnModel_Base
{
public:
DefaultGridColumnModel();
@@ -82,25 +80,20 @@ public:
virtual css::uno::Reference< css::util::XCloneable > SAL_CALL createClone(
) override;
// OComponentHelper
-virtual void SAL_CALL disposing() override;
+virtual void disposing( std::unique_lock& ) override;
private:
typedef ::std::vector< rtl::Reference< GridColumn > > Columns;
-::comphelper::OInterfaceContainerHelper3
m_aContainerListeners;
+::comphelper::OInterfaceContainerHelper4
m_aContainerListeners;
Columns m_aColumns;
};
DefaultGridColumnModel::DefaultGridColumnModel()
-:DefaultGridColumnModel_Base( m_aMutex )
-,m_aContainerListeners( m_aMutex )
{
}
DefaultGridColumnModel::DefaultGridColumnModel( DefaultGridColumnModel
const & i_copySource )
-:cppu::BaseMutex()
-,DefaultGridColumnModel_Base( m_aMutex )
-,m_aContainerListeners( m_aMutex )
{
Columns aColumns;
aColumns.reserve( i_copySource.m_aColumns.size() );
@@ -134,14 +127,16 @@ private:
Reference< XGridColumn > SAL_CALL DefaultGridColumnModel::createColumn( )
{
-::comphelper::ComponentGuard aGuard( *this, rBHelper );
+std::unique_lock aGuard(m_aMutex);
+throwIfDisposed(aGuard);
return new GridColumn();
}
::sal_Int32 SAL_CALL DefaultGridColumnModel::addColumn( const Reference<
XGridColumn > & i_column )
{
-::comphelper::ComponentGuard aGuard( *this, rBHelper );
+std::unique_lock aGuard(m_aMutex);
+throwIfDisposed(aGuard);
GridColumn* const pGridColumn = dynamic_cast(
i_column.get() );
if ( pGridColumn == nullptr )
@@ -157,8 +152,7 @@ private:
aEvent.Accessor <<= index;
aEvent.Element <<= i_column;
-aGuard.clear();
-m_aContainerListeners.notifyEach(
::elementInserted, aEvent );
+m_aContainerListeners.notifyEach( aGuard,
::elementInserted, aEvent );
return index;
}
@@ -166,7 +160,8 @@ private:
void SAL_CALL DefaultGridColumnModel::removeColumn( ::sal_Int32
i_columnIndex )
{
-::comphelper::ComponentGuard aGuard( *this, rBHelper );
+std::unique_lock aGuard(m_aMutex);
+throwIfDisposed(aGuard);
if ( ( i_columnIndex < 0 ) || ( o3tl::make_unsigned( i_columnIndex )
>= m_aColumns.size() ) )
throw css::lang::IndexOutOfBoundsException( OUString(), *this );
@@ -192,8 +187,9 @@ private:
aEvent.Accessor <<= i_columnIndex;
aEvent.Element <<= xColumn;
-aGuard.clear();
-m_aContainerListeners.notifyEach( ::elementRemoved,
aEvent );
+m_aContainerListeners.notifyEach( aGuard,
[Libreoffice-commits] core.git: 2 commits - dbaccess/source include/dbaccess sd/source
dbaccess/source/ui/browser/genericcontroller.cxx | 12 ++--
include/dbaccess/genericcontroller.hxx |3 ++-
sd/source/ui/tools/SdGlobalResourceContainer.cxx | 11 ++-
3 files changed, 14 insertions(+), 12 deletions(-)
New commits:
commit a979535eeb1630334b60eea98be2c2fabec56c23
Author: Noel Grandin
AuthorDate: Fri Feb 17 13:25:39 2023 +0200
Commit: Noel Grandin
CommitDate: Sat Feb 18 20:40:17 2023 +
osl::Mutex->std::mutex in OGenericUnoController
Change-Id: If49864f3127b185bb0212be02abd0f92e14c3908
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147261
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/dbaccess/source/ui/browser/genericcontroller.cxx
b/dbaccess/source/ui/browser/genericcontroller.cxx
index 5c4423227784..a5c8afbb306b 100644
--- a/dbaccess/source/ui/browser/genericcontroller.cxx
+++ b/dbaccess/source/ui/browser/genericcontroller.cxx
@@ -459,7 +459,7 @@ void OGenericUnoController::InvalidateFeature_Impl()
bool bEmpty = true;
FeatureListener aNextFeature;
{
-::osl::MutexGuard aGuard( m_aFeatureMutex);
+std::unique_lock aGuard( m_aFeatureMutex);
bEmpty = m_aFeaturesToInvalidate.empty();
if (!bEmpty)
aNextFeature = m_aFeaturesToInvalidate.front();
@@ -492,7 +492,7 @@ void OGenericUnoController::InvalidateFeature_Impl()
ImplBroadcastFeatureState( aFeaturePos->first,
aNextFeature.xListener, aNextFeature.bForceBroadcast );
}
-::osl::MutexGuard aGuard( m_aFeatureMutex);
+std::unique_lock aGuard( m_aFeatureMutex);
m_aFeaturesToInvalidate.pop_front();
bEmpty = m_aFeaturesToInvalidate.empty();
if (!bEmpty)
@@ -521,7 +521,7 @@ void OGenericUnoController::ImplInvalidateFeature(
sal_Int32 _nId, const Referen
bool bWasEmpty;
{
-::osl::MutexGuard aGuard( m_aFeatureMutex );
+std::unique_lock aGuard( m_aFeatureMutex );
bWasEmpty = m_aFeaturesToInvalidate.empty();
m_aFeaturesToInvalidate.push_back( aListener );
}
@@ -547,7 +547,7 @@ void OGenericUnoController::InvalidateAll_Impl()
ImplBroadcastFeatureState( supportedFeature.first, nullptr, true );
{
-::osl::MutexGuard aGuard( m_aFeatureMutex);
+std::unique_lock aGuard( m_aFeatureMutex);
OSL_ENSURE(m_aFeaturesToInvalidate.size(),
"OGenericUnoController::InvalidateAll_Impl: to be called from within
InvalidateFeature_Impl only!");
m_aFeaturesToInvalidate.pop_front();
if(!m_aFeaturesToInvalidate.empty())
@@ -680,7 +680,7 @@ void OGenericUnoController::removeStatusListener(const
Reference< XStatusListene
}
// now remove the listener from the deque
-::osl::MutexGuard aGuard( m_aFeatureMutex );
+std::unique_lock aGuard( m_aFeatureMutex );
m_aFeaturesToInvalidate.erase(
std::remove_if( m_aFeaturesToInvalidate.begin(),
m_aFeaturesToInvalidate.end(),
@@ -717,7 +717,7 @@ void OGenericUnoController::disposing()
m_xDatabaseContext = nullptr;
{
-::osl::MutexGuard aGuard( m_aFeatureMutex);
+std::unique_lock aGuard( m_aFeatureMutex);
m_aAsyncInvalidateAll.CancelCall();
m_aFeaturesToInvalidate.clear();
}
diff --git a/include/dbaccess/genericcontroller.hxx
b/include/dbaccess/genericcontroller.hxx
index 0eb6a94ad703..6ef9393c2f9a 100644
--- a/include/dbaccess/genericcontroller.hxx
+++ b/include/dbaccess/genericcontroller.hxx
@@ -25,6 +25,7 @@
#include
#include
#include
+#include
#include
#include
@@ -233,7 +234,7 @@ namespace dbaui
::std::deque< FeatureListener >
m_aFeaturesToInvalidate;
-::osl::Mutexm_aFeatureMutex;// locked when
features are append to or remove from deque
+std::mutex m_aFeatureMutex;// locked when
features are append to or remove from deque
StateCache m_aStateCache; // save the current
status of feature state
Dispatchm_arrStatusListener;// all our listeners
where we dispatch status changes
OAsynchronousLink m_aAsyncInvalidateAll;
commit 4a4223f924d4ec49b023a85ce37f3788bc699723
Author: Noel Grandin
AuthorDate: Fri Feb 17 15:05:54 2023 +0200
Commit: Noel Grandin
CommitDate: Sat Feb 18 20:40:05 2023 +
osl::Mutex->std::mutex in SdGlobalResourceContainer
Change-Id: I521ec7397e9ac54547bc82be6579cbb4fb4fc5a8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147266
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/sd/source/ui/tools/SdGlobalResourceContainer.cxx
b/sd/source/ui/tools/SdGlobalResourceContainer.cxx
index a7dbc5f25920..7f692caa157c 100644
--- a/sd/source/ui/tools/SdGlobalResourceContainer.cxx
+++ b/sd/source/ui/tools/SdGlobalResourceContainer.cxx
@@ -31,6 +31,7 @@
[Libreoffice-bugs] [Bug 148601] Missing scrollbars in menus (interface bug since 7.0)
https://bugs.documentfoundation.org/show_bug.cgi?id=148601 Michael FA changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105957] [META] Scrollbar-related bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105957 Bug 105957 depends on bug 148601, which changed state. Bug 148601 Summary: Missing scrollbars in menus (interface bug since 7.0) https://bugs.documentfoundation.org/show_bug.cgi?id=148601 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148601] Missing scrollbars in menus (interface bug since 7.0)
https://bugs.documentfoundation.org/show_bug.cgi?id=148601 Michael FA changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/qa sc/source
sc/qa/unit/data/csv/testTdf82254-csv-bom.csv |3 +++
sc/qa/unit/subsequent_filters_test.cxx | 21 +
sc/source/ui/dbgui/asciiopt.cxx |8 +++-
sc/source/ui/dbgui/imoptdlg.cxx |7 ++-
sc/source/ui/docshell/docsh.cxx | 13 +
sc/source/ui/docshell/impex.cxx | 11 +++
sc/source/ui/inc/asciiopt.hxx|3 +++
sc/source/ui/inc/imoptdlg.hxx|3 ++-
sc/source/ui/inc/impex.hxx |4
sc/source/ui/unoobj/filtuno.cxx |6 ++
10 files changed, 72 insertions(+), 7 deletions(-)
New commits:
commit 509ab788baf54285b4e38f2560326657d97510fd
Author: Andreas Heinisch
AuthorDate: Fri Jan 20 12:08:13 2023 +0100
Commit: Eike Rathke
CommitDate: Sat Feb 18 20:05:49 2023 +
tdf#82254 - Don't remove UTF-8 BOM from CSV when saving file
Don't remove the byte-order-mark in the resulting CSV file
when it was present in the CSV source file.
Change-Id: Id26abad2686917f320f2ace85441621bcf57ea9e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/145879
Tested-by: Jenkins
Reviewed-by: Eike Rathke
diff --git a/sc/qa/unit/data/csv/testTdf82254-csv-bom.csv
b/sc/qa/unit/data/csv/testTdf82254-csv-bom.csv
new file mode 100755
index ..eabb18da0bf0
--- /dev/null
+++ b/sc/qa/unit/data/csv/testTdf82254-csv-bom.csv
@@ -0,0 +1,3 @@
+col1 col2col3
+row1-1 row1-2 row1-3
+row2-1 row2-2 row2-3
diff --git a/sc/qa/unit/subsequent_filters_test.cxx
b/sc/qa/unit/subsequent_filters_test.cxx
index 10cf129c0412..6af0460170be 100644
--- a/sc/qa/unit/subsequent_filters_test.cxx
+++ b/sc/qa/unit/subsequent_filters_test.cxx
@@ -54,6 +54,8 @@
#include
#include
+#include
+
#include
#include
@@ -196,6 +198,7 @@ public:
void testImportCrashes();
void testTdf129681();
void testTdf149484();
+void testTdf82254_csv_bom();
void testEscapedUnicodeXLSX();
void testTdf144758_DBDataDefaultOrientation();
void testSharedFormulaXLS();
@@ -321,6 +324,7 @@ public:
CPPUNIT_TEST(testImportCrashes);
CPPUNIT_TEST(testTdf129681);
CPPUNIT_TEST(testTdf149484);
+CPPUNIT_TEST(testTdf82254_csv_bom);
CPPUNIT_TEST(testEscapedUnicodeXLSX);
CPPUNIT_TEST(testTdf144758_DBDataDefaultOrientation);
CPPUNIT_TEST(testSharedFormulaXLS);
@@ -3203,6 +3207,23 @@ void ScFiltersTest::testTdf149484()
CPPUNIT_ASSERT_EQUAL(OUString("-TRUE-"), pDoc->GetString(0, 2, 0));
}
+void ScFiltersTest::testTdf82254_csv_bom()
+{
+setImportFilterName(SC_TEXT_CSV_FILTER_NAME);
+createScDoc("csv/testTdf82254-csv-bom.csv");
+saveAndReload(SC_TEXT_CSV_FILTER_NAME);
+ScDocShell* pDocSh = getScDocShell();
+SvStream* pStream = pDocSh->GetMedium()->GetInStream();
+
+pStream->Seek(0);
+CPPUNIT_ASSERT_EQUAL(sal_uInt64(0), pStream->Tell());
+pStream->StartReadingUnicodeText(RTL_TEXTENCODING_UTF8);
+// Without the fix in place, this test would have failed with
+// - Expected: 3
+// - Actual : 0 (no byte order mark was read)
+CPPUNIT_ASSERT_EQUAL(sal_uInt64(3), pStream->Tell());
+}
+
void ScFiltersTest::testEscapedUnicodeXLSX()
{
createScDoc("xlsx/escape-unicode.xlsx");
diff --git a/sc/source/ui/dbgui/asciiopt.cxx b/sc/source/ui/dbgui/asciiopt.cxx
index 933491efbbe5..4234794ea279 100644
--- a/sc/source/ui/dbgui/asciiopt.cxx
+++ b/sc/source/ui/dbgui/asciiopt.cxx
@@ -37,6 +37,7 @@ ScAsciiOptions::ScAsciiOptions() :
bSkipEmptyCells(false),
bSaveAsShown(true),
bSaveFormulas(false),
+bIncludeBOM(false),
cTextSep( cDefaultTextSep ),
eCharSet( osl_getThreadTextEncoding() ),
eLang ( LANGUAGE_SYSTEM ),
@@ -192,6 +193,9 @@ void ScAsciiOptions::ReadFromString( std::u16string_view
rString )
}
else
bEvaluateFormulas = true; // default of versions that didn't add the
parameter
+
+// Token 13: include BOM.
+bIncludeBOM = nPos >= 0 && o3tl::getToken(rString, 0, ',', nPos) ==
u"true";
}
OUString ScAsciiOptions::WriteToString() const
@@ -261,7 +265,9 @@ OUString ScAsciiOptions::WriteToString() const
// Token 11: sheet to export, always 0 for current sheet
",0," +
// Token 12: evaluate formulas in import
- OUString::boolean( bEvaluateFormulas )
+ OUString::boolean( bEvaluateFormulas ) + "," +
+ // Token 13: include BOM
+ OUString::boolean(bIncludeBOM)
);
return aOutStr.makeStringAndClear();
}
diff --git a/sc/source/ui/dbgui/imoptdlg.cxx b/sc/source/ui/dbgui/imoptdlg.cxx
index b285c6ae968e..2777eb9e450b 100644
--- a/sc/source/ui/dbgui/imoptdlg.cxx
+++ b/sc/source/ui/dbgui/imoptdlg.cxx
@@ -47,6 +47,7 @@ ScImportOptions::ScImportOptions( std::u16string_view rStr )
bRemoveSpace = false;
nSheetToExport = 0;
[Libreoffice-bugs] [Bug 153716] Comments on first page omitted during PDF export
https://bugs.documentfoundation.org/show_bug.cgi?id=153716 N Murthy changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153716] New: Comments on first page omitted during PDF export
https://bugs.documentfoundation.org/show_bug.cgi?id=153716 Bug ID: 153716 Summary: Comments on first page omitted during PDF export Product: LibreOffice Version: 7.5.0.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nmurth...@gmail.com Description: In writer document, though the comments are set to be placed within page margin under libreoffice writer tab of print command, the comments in first page are omitted in the exported PDF file. The comments in pages after that i.e page no 2 onward appear as intended. The first page is exported in the normal size as well without shrinking the data for comments to be placed within margins Steps to Reproduce: 1.Create or open libreoffice writer file 2. Add comments on first and other pages as required 3. Goto file>print, select libreoffice writer tab 4. Set place in margins for comments 5. Then goto file>export as>export as PDF and export the file as PDF Actual Results: Comments in the first page are omitted Expected Results: Comments should appear on all pages Reproducible: Always User Profile Reset: No Additional Info: Prior to installing 7.5 version, 7.45 version was installed. Windows version is 21H2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123792] [NEWHELP] The new SVG icons/images for math elements don't seem to make it to correct location in offline help
https://bugs.documentfoundation.org/show_bug.cgi?id=123792 V Stuart Foote changed: What|Removed |Added Resolution|MOVED |WORKSFORME --- Comment #6 from V Stuart Foote --- checked recent TB77 build of trunk against 7.6.0 (2023-02-16 c3bd52f) with its corresponding Helppack (en-US) installed to local system The SVG versions of the help article icons are present now in the @ORIGIN/../help/media/helpimg/starmath and the icons Help pages are well rendered in browser without pixelation at an enlarged readable size. Likewise rendering remains good as the os/DE UI is scaled above 225% -- so scaling is nicely progressive. So while bug 125178 is resolved => WF, this facet for use the SVG in the local/offline Help install is good. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c3bd52f81bf733a0b9b0560794a54b2ac1e0f444 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139112] libreoffice does not remember the dimensions of the settings window
https://bugs.documentfoundation.org/show_bug.cgi?id=139112 --- Comment #14 from Łukasz --- in 7.5.0.3 there is also a problem. it's been going on for a long time and you probably won't fix it -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139993] Extreme lagging with SVG's containing gradients
https://bugs.documentfoundation.org/show_bug.cgi?id=139993 --- Comment #6 from Gellért Gyuris --- The bug is still present: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153715] New: Calc:Formatting, Insert comment makes font toolbar disappear.
https://bugs.documentfoundation.org/show_bug.cgi?id=153715 Bug ID: 153715 Summary: Calc:Formatting, Insert comment makes font toolbar disappear. Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: irontop...@gmail.com Description: Toolbar with font adjustments disappears when creating a cell comment. Cannot modify font size or type in 7.5.0.3. Actual Results: highlight cell, insert comment command Expected Results: toolbar disappears Reproducible: Always User Profile Reset: Yes Additional Info: leave the toolbar in place. Previous versions did not have this problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sc/qa
dev/null|binary
sc/qa/extras/vba-macro-test.cxx | 37 ++---
2 files changed, 34 insertions(+), 3 deletions(-)
New commits:
commit 0a27403bbc36c89efa321fb3c5061fe4ee7095fb
Author: Balazs Varga
AuthorDate: Thu Feb 16 20:06:02 2023 +0100
Commit: Balazs Varga
CommitDate: Sat Feb 18 18:23:51 2023 +
Related tdf#149786: add better unit test for vba pdf export macro
Better unit test for vba pdf export.
Change-Id: Ifa3dff79c457e21ca24b8d99c024bd59917bc990
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147171
Tested-by: Jenkins
Reviewed-by: Balazs Varga
diff --git a/sc/qa/extras/testdocuments/ExportAsPDF.xlsm
b/sc/qa/extras/testdocuments/ExportAsPDF.xlsm
deleted file mode 100644
index 6cb410beec21..
Binary files a/sc/qa/extras/testdocuments/ExportAsPDF.xlsm and /dev/null differ
diff --git a/sc/qa/extras/vba-macro-test.cxx b/sc/qa/extras/vba-macro-test.cxx
index 268b35ee33fe..29fdf213f8e7 100644
--- a/sc/qa/extras/vba-macro-test.cxx
+++ b/sc/qa/extras/vba-macro-test.cxx
@@ -11,6 +11,8 @@
#include
#include
#include
+#include
+#include
#include
#include
#include
@@ -834,10 +836,39 @@ void VBAMacroTest::testTdf126457()
void VBAMacroTest::testVbaPDFExport()
{
-loadFromURL(u"ExportAsPDF.xlsm");
+mxComponent = loadFromDesktop("private:factory/scalc");
+
+// Save a copy of the file to get its URL
+uno::Reference xDocStorable(mxComponent, uno::UNO_QUERY);
+utl::TempFileNamed aTempFile(u"testVBA_PDF_Export", true, u".ods");
+aTempFile.EnableKillingFile();
+uno::Sequence descSaveAs(
+comphelper::InitPropertySequence({ { "FilterName",
uno::Any(OUString("calc8")) } }));
+xDocStorable->storeAsURL(aTempFile.GetURL(), descSaveAs);
+
+utl::TempFileNamed aTempPdfFile(u"exportedfile", true, u".pdf");
+aTempPdfFile.EnableKillingFile();
+
+css::uno::Reference xDocScr(mxComponent,
uno::UNO_QUERY_THROW);
+auto xLibs = xDocScr->getBasicLibraries();
+auto xLibrary = xLibs->createLibrary("TestLibrary");
+OUString sMacro = "Option VBASupport 1\n"
+ "Sub ExportAsPDF\n"
+ " fileName = \""
+ + aTempPdfFile.GetFileName()
+ + "\"\n ActiveSheet.ExportAsFixedFormat
Type:=xlTypePDF, "
+"FileName:=fileName, Quality:=xlQualityStandard, "
+"IncludeDocProperties:=True, OpenAfterPublish:=False\n"
+"End Sub\n";
+xLibrary->insertByName("TestModule", uno::Any(sMacro));
+
+
executeMacro("vnd.sun.Star.script:TestLibrary.TestModule.ExportAsPDF?language=Basic="
+ "document");
-executeMacro("vnd.sun.Star.script:VBAProject.Module1.ExportAsPDF?"
- "language=Basic=document");
+// Parse the export result.
+vcl::filter::PDFDocument aDocument;
+SvFileStream aStream(aTempPdfFile.GetURL(), StreamMode::READ);
+CPPUNIT_ASSERT_MESSAGE("Failed to get the pdf document",
aDocument.Read(aStream));
}
CPPUNIT_TEST_SUITE_REGISTRATION(VBAMacroTest);
[Libreoffice-bugs] [Bug 153714] New: Silent failure to encrypt with password when libnssckbi.so fails to be dynamically loaded
https://bugs.documentfoundation.org/show_bug.cgi?id=153714 Bug ID: 153714 Summary: Silent failure to encrypt with password when libnssckbi.so fails to be dynamically loaded Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: filters and storage Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: maxim.courno...@gmail.com Hi, Using LibreOffice 7.5.0.3 on Guix System, which is built using system libraries, and which doesn't use the File Hierarchy Standard (FHS) layout, it was discovered that the encrypt with password feature (in the Save dialog box) did not work [0]. [0] https://issues.guix.gnu.org/59292 Instead, what happens is that the file is saved unencrypted, without any indication of a problem to the user (!). Debugging the cause when as follow: 1. Using strace, I found that libnssckbi.so was not resolved: ``` [pid 2594] openat(AT_FDCWD, "/home/maxim/.thunderbird/sjp3hftb.default/libnssckbi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD, "/proc/sys/crypto/fips_enabled", O_RDONLY) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD, "/gnu/store/rrid5nx9cbrq0flkhc1rv4b5hk4w70ib-nspr-4.34/lib/libnssckbi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD, "/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33/lib/libnssckbi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/libnssckbi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../tls/x86_64/x86_64/libnssckbi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [pid 2594] newfstatat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../tls/x86_64/x86_64", 0x7ffead11c5b0, 0) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../tls/x86_64/libnssckbi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [pid 2594] newfstatat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../tls/x86_64", 0x7ffead11c5b0, 0) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../tls/x86_64/libnssckbi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [pid 2594] newfstatat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../tls/x86_64", 0x7ffead11c5b0, 0) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../tls/libnssckbi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [pid 2594] newfstatat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../tls", 0x7ffead11c5b0, 0) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../x86_64/x86_64/libnssckbi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [pid 2594] newfstatat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../x86_64/x86_64", 0x7ffead11c5b0, 0) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../x86_64/libnssckbi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [pid 2594] newfstatat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../x86_64", 0x7ffead11c5b0, 0) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../x86_64/libnssckbi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) [pid 2594] newfstatat(AT_FDCWD, "/gnu/store/094bbaq6glba86h1d4cj16xhdi6fk2jl-gcc-10.3.0-lib/lib/gcc/x86_64-unknown-linux-gnu/10.3.0/../../../x86_64", 0x7ffead11c5b0, 0) = -1 ENOENT (No such file or directory) [pid 2594] openat(AT_FDCWD,
[Libreoffice-bugs] [Bug 126008] TABLES STYLES: Inserting a row/column changes entire table's formatting (see comment 5)
https://bugs.documentfoundation.org/show_bug.cgi?id=126008 N Murthy changed: What|Removed |Added CC||nmurth...@gmail.com --- Comment #75 from N Murthy --- The problem persists in libreoffice version 7.5 also -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153713] New: Feldbefehl - Verweis einfügen
https://bugs.documentfoundation.org/show_bug.cgi?id=153713 Bug ID: 153713 Summary: Feldbefehl - Verweis einfügen Product: LibreOffice Version: 7.5.0.3 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: klauspeter.die...@arcor.de Created attachment 185464 --> https://bugs.documentfoundation.org/attachment.cgi?id=185464=edit Document after saving. Mit "Feldbefehl" und "Verweis einfügen" neuen Feldbefehl eingefügt. Feldbefehlname "ruhrwoge_Datum". Dann mit "Feldbefehl" und "Verweistext" in die Kopfzeile die Referenz auf den Text eingefügt. Mit Ansicht -> Feldnamen eintrag geprüft. OK. Dokument als .docx gespeichert und geschlossen. Nach erneutem Öffnen ist die Referenz vorhanden, aber nach weiteren Operationen nicht mehr, z.B. Dokument als PDF exportieren. Mit Ansicht -> Feldnamen die Referenz geprüft, es wurde aus "ruhrwoge_Datum" "Ref_ruhrwoge_Datum". Tritt nur mit Dokumenten .docx auf, bei .odt nicht. Inserted new field command with "Feldbefehl" and "Verweis einfügen". Field command name "ruhrwoge_Datum". Then inserted the reference to the text in the header with "Feldbefehl" and "Verweistext". Check entry with Ansicht -> Feldnamen. OK. Document saved as .docx and closed. After reopening, the reference is available, but not after further operations, e.g. export document as PDF. Checked the reference with Ansicht -> Feldnamen, "ruhrwoge_Datum" became "Ref_ruhrwoge_Datum". Only occurs with .docx documents, not with .odt. Reproduzierbar in nachfolgenden Versionen bzw. Umgebungen: Reproducible in subsequent versions or environments: Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.1 Calc: threaded Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL threaded Version: 6.0.7.3 Build-ID: 1:6.0.7-0ubuntu0.18.04.12 CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=122497 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||153712 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153712 [Bug 153712] "Chapter Info" should be named "Heading Info" (or "Heading") and "chapter entry" and its buddy dropdown box labels should be changed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153712] "Chapter Info" should be named "Heading Info" (or "Heading") and "chapter entry" and its buddy dropdown box labels should be changed
https://bugs.documentfoundation.org/show_bug.cgi?id=153712 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||122497 Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122497 [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 153712] "Chapter Info" should be named "Heading Info" (or "Heading") and "chapter entry" and its buddy dropdown box labels should be changed
https://bugs.documentfoundation.org/show_bug.cgi?id=153712 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||122497 Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122497 [Bug 122497] [META] Table of Contents and Indexes dialog bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 153712] New: "Chapter Info" should be named "Heading Info" (or "Heading") and "chapter entry" and its buddy dropdown box labels should be changed
https://bugs.documentfoundation.org/show_bug.cgi?id=153712 Bug ID: 153712 Summary: "Chapter Info" should be named "Heading Info" (or "Heading") and "chapter entry" and its buddy dropdown box labels should be changed Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sdc.bla...@youmail.dk Created attachment 185463 --> https://bugs.documentfoundation.org/attachment.cgi?id=185463=edit screenshot of Chapter Info Entries dialog 1. Insert - Table of Contents and Index - Table of Contents, Index, or Bibliography 2. Select "Type" tab, then select any Type (except for "Table of Contents" or "Bibliography") 3. Select "Entries" tab 4. Insert "Chapter Info" to Structure, then click on "Chapter Info" New options are displayed (screenshot attached). Proposals: 1. "Chapter Info" should be named "Heading Info" (or "Heading" might be sufficient): because this control is providing information from headings, not from chapters (outline level 1 paragraphs) alone. 2. If proposal 1 is accepted, then of course the "CI" should change to "HI" (or "H"). 3. "chapter entry" label should be improved, with "chapter" -> "heading" and "entry" does not sound right. Could not think of a suitable alternative. Maybe "entry" can be dropped -- given that the dropdown box contents quickly explains its meaning. 4. "number range" in dropdown box for "Chapter entry" sounds wrong. probably "heading number" is accurate. 5. "description" also sounds wrong. Perhaps "heading contents" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153711] New: FILESAVE DOCX. Character theme color is not exported as theme color
https://bugs.documentfoundation.org/show_bug.cgi?id=153711 Bug ID: 153711 Summary: FILESAVE DOCX. Character theme color is not exported as theme color Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Created attachment 185462 --> https://bugs.documentfoundation.org/attachment.cgi?id=185462=edit document with color theme Open attached document. It a theme in styles.xml. The characters in the file are direct formatted to use a theme color. You can verify in the file markup, that this is indeed contained in the file markup. Save the file to docx. Open the file in Word and change the theme of Word (that is in tab 'Design'). The colors of the characters do not change, which means, that they do not have theme colors. Inspect the markup of the docx file. You will find that the needed attributes "w:themeColor" and "w:themeTint" or "w:themeShade" of the element are missing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153710] "Evaluate up to level" for Chapter Info for User-Defined Index shows only top level or all levels
https://bugs.documentfoundation.org/show_bug.cgi?id=153710 sdc.bla...@youmail.dk changed: What|Removed |Added Blocks||89606 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=89606 [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=89606 sdc.bla...@youmail.dk changed: What|Removed |Added Depends on||153710 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153710 [Bug 153710] "Evaluate up to level" for Chapter Info for User-Defined Index shows only top level or all levels -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153710] New: "Evaluate up to level" for Chapter Info for User-Defined Index shows only top level or all levels
https://bugs.documentfoundation.org/show_bug.cgi?id=153710 Bug ID: 153710 Summary: "Evaluate up to level" for Chapter Info for User-Defined Index shows only top level or all levels Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sdc.bla...@youmail.dk Created attachment 185461 --> https://bugs.documentfoundation.org/attachment.cgi?id=185461=edit Document for testing levels with user-defined index Problem: There does not seem to be any way to control how many levels are shown in a "Chapter Info" number range To see issue: 0. Attached document has a User-Defined Index at the end. 1. Edit the Index. See in the "Type" tab that it is created from Tables, Frames, and Graphics (using "Use level from source chapter"). 2. Select Entries tab and level 5. 3. Select CI icon (which introduces new options in the dialog window). 4. Note that "Evaluate up to level" is set to 6. Change to "5" 5. OK. ACTUAL: The number in front of "Second Table" changes from "1.1.1.1.1" to "1" EXPECTED: Number changes to "1.1.1.1" Any value for "Evaluate up to..." from 1-5 only shows "1", while any value greater than 5 shows "1.1.1.1.1" -- In short: Cannot control the number of levels shown. Additional Information: 1. Bug 153636 reports that levels do not work for Graphics and Frames, so if you use the attached file, then only Tables will change levels. 2. Have not tested other Indexes that use Chapter Info. 3. It is possible to control the number of levels shown in a ToC Index (using the "Evaluate up to..." option in the Entries tab). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153709] "Delete Sheet" command should indicate the number of selected sheets that will be deleted
https://bugs.documentfoundation.org/show_bug.cgi?id=153709 --- Comment #1 from Laurent Balland --- The place where message should be updated: https://opengrok.libreoffice.org/xref/core/sc/source/ui/view/tabvwshf.cxx?r=0908c7c1#679 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/qa
sw/qa/inc/swmodeltestbase.hxx | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
New commits:
commit 02512bbfe9bc8f21b82eaf0cbf7135693ea12ced
Author: Stephan Bergmann
AuthorDate: Sat Feb 18 10:44:52 2023 +0100
Commit: Stephan Bergmann
CommitDate: Sat Feb 18 16:23:46 2023 +
Remove redundant (and wrong!) explicit template arguments
At least the last one, for css::table::BorderLine2::LineWidth, should have
been
sal_uInt32 instead of sal_Int32.
Change-Id: Iab375988432b6a69172625af86cc25b813f60446
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147268
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann
diff --git a/sw/qa/inc/swmodeltestbase.hxx b/sw/qa/inc/swmodeltestbase.hxx
index 4c5ba58103d5..c64a3ab13f47 100644
--- a/sw/qa/inc/swmodeltestbase.hxx
+++ b/sw/qa/inc/swmodeltestbase.hxx
@@ -369,12 +369,12 @@ inline void assertBorderEqual(
const css::table::BorderLine2& rExpected, const css::table::BorderLine2&
rActual,
const CppUnit::SourceLine& rSourceLine )
{
-CPPUNIT_NS::assertEquals( rExpected.Color,
rActual.Color, rSourceLine, "different Color" );
-CPPUNIT_NS::assertEquals( rExpected.InnerLineWidth,
rActual.InnerLineWidth, rSourceLine, "different InnerLineWidth" );
-CPPUNIT_NS::assertEquals( rExpected.OuterLineWidth,
rActual.OuterLineWidth, rSourceLine, "different OuterLineWidth" );
-CPPUNIT_NS::assertEquals( rExpected.LineDistance,
rActual.LineDistance, rSourceLine, "different LineDistance" );
-CPPUNIT_NS::assertEquals( rExpected.LineStyle,
rActual.LineStyle, rSourceLine, "different LineStyle" );
-CPPUNIT_NS::assertEquals( rExpected.LineWidth,
rActual.LineWidth, rSourceLine, "different LineWidth" );
+CPPUNIT_NS::assertEquals( rExpected.Color, rActual.Color, rSourceLine,
"different Color" );
+CPPUNIT_NS::assertEquals( rExpected.InnerLineWidth,
rActual.InnerLineWidth, rSourceLine, "different InnerLineWidth" );
+CPPUNIT_NS::assertEquals( rExpected.OuterLineWidth,
rActual.OuterLineWidth, rSourceLine, "different OuterLineWidth" );
+CPPUNIT_NS::assertEquals( rExpected.LineDistance, rActual.LineDistance,
rSourceLine, "different LineDistance" );
+CPPUNIT_NS::assertEquals( rExpected.LineStyle, rActual.LineStyle,
rSourceLine, "different LineStyle" );
+CPPUNIT_NS::assertEquals( rExpected.LineWidth, rActual.LineWidth,
rSourceLine, "different LineWidth" );
}
#define CPPUNIT_ASSERT_BORDER_EQUAL(aExpected, aActual) \
[Libreoffice-bugs] [Bug 153709] New: "Delete Sheet" command should indicate the number of selected sheets that will be deleted
https://bugs.documentfoundation.org/show_bug.cgi?id=153709 Bug ID: 153709 Summary: "Delete Sheet" command should indicate the number of selected sheets that will be deleted Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jumbo4...@yahoo.fr Description: in a file with many sheets, you may have accidentally select several sheets (or intentionally but forget). When deleting sheets, the confirmation message does not specify the exact number of sheets which are selected and will be deleted Steps to reproduce: 1. Open a spreadsheet with several sheets 2. Select some sheets (or not) but not all 3. Select menu Sheet > Delete Sheet Actual behavior Whatever the number of selected sheets, a confirmation message ask: "Are you sure you want to delete the selected sheet(s)?" Expected behavior Confirmation message should be adapted to the number of selected sheet: For 1 sheet: "Are you sure you want to delete the selected sheet?" For x sheets: "Are you sure you want to delete the x selected sheets?" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145936] FORMATTING: Changing text page size changes the page style for endnotes, and hides part of the endnotes
https://bugs.documentfoundation.org/show_bug.cgi?id=145936 raal changed: What|Removed |Added Regression By||Caolán McNamara CC||caol...@redhat.com, ||r...@post.cz Keywords|bibisectRequest |bibisected, bisected --- Comment #7 from raal --- This seems to have begun at the below commit. Adding Cc: to Caolán McNamara ; Could you possibly take a look at this one? Thanks a8461899f33e3a07713239130aeea1b29786f075 is the first bad commit commit a8461899f33e3a07713239130aeea1b29786f075 Author: Jenkins Build User Date: Mon Dec 14 21:34:13 2020 +0100 source sha:ccd89a02f8b5f0e7c542353c5bf0a774dbf781d2 https://git.libreoffice.org/core/+/ccd89a02f8b5f0e7c542353c5bf0a774dbf781d2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139112] libreoffice does not remember the dimensions of the settings window
https://bugs.documentfoundation.org/show_bug.cgi?id=139112 Dieter changed: What|Removed |Added Version|7.5.0.3 release |7.0.4.2 release --- Comment #13 from Dieter --- Don't understand, why you've changed version of earliest affected version from 7.0.4.2 to 7.5.0.3 So I've changed it back. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123792] [NEWHELP] The new SVG icons/images for math elements don't seem to make it to correct location in offline help
https://bugs.documentfoundation.org/show_bug.cgi?id=123792 Bug 123792 depends on bug 125178, which changed state. Bug 125178 Summary: [NEWHELP] enlarge SVG icons in help pages https://bugs.documentfoundation.org/show_bug.cgi?id=125178 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97629] [META] Help Content Modernization
https://bugs.documentfoundation.org/show_bug.cgi?id=97629 Bug 97629 depends on bug 125178, which changed state. Bug 125178 Summary: [NEWHELP] enlarge SVG icons in help pages https://bugs.documentfoundation.org/show_bug.cgi?id=125178 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125178] [NEWHELP] enlarge SVG icons in help pages
https://bugs.documentfoundation.org/show_bug.cgi?id=125178 Olivier Hallot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Olivier Hallot --- Icons in tags are progressively updated to SVG and with 1cm x 1cm size. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97629] [META] Help Content Modernization
https://bugs.documentfoundation.org/show_bug.cgi?id=97629 Bug 97629 depends on bug 125117, which changed state. Bug 125117 Summary: EDIT: Table of Contens (TOC) spanning more than page: Only the first page of the TOC can successfully be assigned to the page style using default „Index Page Style“, solution is confusing for new users and the documentation should be enhanced to show how. https://bugs.documentfoundation.org/show_bug.cgi?id=125117 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125117] EDIT: Table of Contens (TOC) spanning more than page: Only the first page of the TOC can successfully be assigned to the page style using default „Index Page Style“, so
https://bugs.documentfoundation.org/show_bug.cgi?id=125117 Olivier Hallot changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #16 from Olivier Hallot --- Solution to this issue is given in comment #3 by Dieter. Proper management of page styles solves the issue. Tip: to change the page style from "Index" to "Default", format the first heading paragraph adding a page break in the Text Flow tab with "Default paragraph Style" in "With Paragraph Style". Tip 2: Format the TOC page style with proper age break in the Index Heading style => Worksforme -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153683] CLI: Show the module which is used in --convert-to
https://bugs.documentfoundation.org/show_bug.cgi?id=153683 Hossein changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153707] NPV function error with big number
https://bugs.documentfoundation.org/show_bug.cgi?id=153707 Xaxa changed: What|Removed |Added Resolution|NOTABUG |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #2 from Xaxa --- It is not intuitive to know to expand the width of the column. Could we please display the result however long it is? Other platform (Google spreadsheet, MS Excel) still displays the number even if it is long. How much effort does it need to always display the number if it is long? If it is too much effort, we should display a message "number is too long, please expand the column". -- 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 Bug 120201 depends on bug 149286, which changed state. Bug 149286 Summary: Problems with links to help from Tools > Customize > Toolbars tab https://bugs.documentfoundation.org/show_bug.cgi?id=149286 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit e676c585f316b649c06c73711013abe32fce72e6 Author: Olivier Hallot AuthorDate: Sat Feb 18 11:41:38 2023 -0300 Commit: Gerrit Code Review CommitDate: Sat Feb 18 14:41:38 2023 + Update git submodules * Update helpcontent2 from branch 'master' to 72dcc8952e242a86c3e328ca285cd17424008c77 - tdf#149286 Missing Help links for Customize toolbars Change-Id: I702b2ab1759decee9c283e2f2abb09b1a282ab52 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/147090 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index 02ca13ee438e..72dcc8952e24 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 02ca13ee438eac0be0a811f86ffd43c2366eecfa +Subproject commit 72dcc8952e242a86c3e328ca285cd17424008c77
