[Bug 160503] File Open/Save dialog box icon size in Places too large

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160503

Haris  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #1 from Haris  ---
For the open or save dialog box, which icons are you talking about? When I get
to the save dialog box with the steps provided, I don't see any icons. This
might be because I'm on MacOS, but in any case, can you please provide a
screenshot of what you're specifically referring to?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160330] Images, text boxes, and shapes are sent up

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160330

Buovjaga  changed:

   What|Removed |Added

 CC||ilmari.lauhakangas@libreoff
   ||ice.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #5 from Buovjaga  ---
On Linux, I can reproduce with 7.3, but no longer in 7.4.

If you want to try without adding a PPA or upgrading your entire Ubuntu, you
can use an appimage: https://www.libreoffice.org/download/appimage/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160485] FILESAVE: Some Cells Text missing in EXPORT.png with highresolution.

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160485

Rainer Bielefeld Retired  changed:

   What|Removed |Added

 CC||LibreOffice@bielefeldundbus
   ||s.de

--- Comment #2 from Rainer Bielefeld Retired  
---
(In reply to Armondo Lopez from comment #1)
What kind of corruption?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160316] Distorted tabs on Mac

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160316

Buovjaga  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||ilmari.lauhakangas@libreoff
   ||ice.org
 Status|UNCONFIRMED |NEW

--- Comment #4 from Buovjaga  ---
Nothing controversial here about the status, so let's set to NEW.

-- 
You are receiving this mail because:
You are the assignee for the bug.

core.git: connectivity/source hwpfilter/source vcl/source

2024-04-03 Thread Stephan Bergmann (via logerrit)
 connectivity/source/manager/mdrivermanager.cxx |4 ++--
 hwpfilter/source/hstyle.cxx|4 ++--
 vcl/source/window/layout.cxx   |   12 ++--
 3 files changed, 10 insertions(+), 10 deletions(-)

New commits:
commit 6b7245f51274424a6c634424161e8766f8827033
Author: Stephan Bergmann 
AuthorDate: Wed Apr 3 23:58:18 2024 +0200
Commit: Stephan Bergmann 
CommitDate: Thu Apr 4 07:06:17 2024 +0200

A number of bogus GCC 13 warnings still hit with recent GCC 14 trunk

Change-Id: I0ec7743cd79429591fcfc3eb9715ff36d06fc00b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165765
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 

diff --git a/connectivity/source/manager/mdrivermanager.cxx 
b/connectivity/source/manager/mdrivermanager.cxx
index 5c5b4f60a017..ed09cc3c816e 100644
--- a/connectivity/source/manager/mdrivermanager.cxx
+++ b/connectivity/source/manager/mdrivermanager.cxx
@@ -601,12 +601,12 @@ Reference< XDriver > 
OSDBCDriverManager::implGetDriverForURL(const OUString& _rU
 m_aDriversBS.end(), // end of search range
 [&_rURL, this] (const DriverAccessArray::value_type& 
driverAccess) {
 // extract the driver from the access, then ask the 
resulting driver for acceptance
-#if defined __GNUC__ && !defined __clang__ && __GNUC__ == 13
+#if defined __GNUC__ && !defined __clang__ && __GNUC__ >= 13 && __GNUC__ <= 14
 #pragma GCC diagnostic push
 #pragma GCC diagnostic ignored "-Wdangling-reference"
 #endif
 const DriverAccess& ensuredAccess = 
EnsureDriver(m_xContext)(driverAccess);
-#if defined __GNUC__ && !defined __clang__ && __GNUC__ == 13
+#if defined __GNUC__ && !defined __clang__ && __GNUC__ >= 13 && __GNUC__ <= 14
 #pragma GCC diagnostic pop
 #endif
 const Reference driver = 
ExtractDriverFromAccess()(ensuredAccess);
diff --git a/hwpfilter/source/hstyle.cxx b/hwpfilter/source/hstyle.cxx
index 013f755496a5..9a0040edcf08 100644
--- a/hwpfilter/source/hstyle.cxx
+++ b/hwpfilter/source/hstyle.cxx
@@ -68,14 +68,14 @@ void HWPStyle::SetName(int n, char const* name)
 
 if (name)
 {
-#if defined __GNUC__ && (__GNUC__ >= 8 && __GNUC__ <= 13) && !defined __clang__
+#if defined __GNUC__ && (__GNUC__ >= 8 && __GNUC__ <= 14) && !defined __clang__
 #pragma GCC diagnostic push
 #pragma GCC diagnostic ignored "-Wstringop-truncation"
 #endif
 auto const p = style[n].name;
 strncpy(p, name, MAXSTYLENAME);
 p[MAXSTYLENAME] = '
-#if defined __GNUC__ && (__GNUC__ >= 8 && __GNUC__ <= 13) && !defined __clang__
+#if defined __GNUC__ && (__GNUC__ >= 8 && __GNUC__ <= 14) && !defined __clang__
 #pragma GCC diagnostic pop
 #endif
 }
diff --git a/vcl/source/window/layout.cxx b/vcl/source/window/layout.cxx
index 9e47d6d8f347..c4729a1e1abb 100644
--- a/vcl/source/window/layout.cxx
+++ b/vcl/source/window/layout.cxx
@@ -964,12 +964,12 @@ static array_type assembleGrid(const VclGrid )
 {
 for (sal_Int32 y = 0; y < nMaxY; ++y)
 {
-#if defined __GNUC__ && !defined __clang__ && __GNUC__ == 13
+#if defined __GNUC__ && !defined __clang__ && __GNUC__ >= 13 && __GNUC__ <= 14
 #pragma GCC diagnostic push
 #pragma GCC diagnostic ignored "-Wdangling-reference"
 #endif
 const GridEntry  = A[x][y];
-#if defined __GNUC__ && !defined __clang__ && __GNUC__ == 13
+#if defined __GNUC__ && !defined __clang__ && __GNUC__ >= 13 && __GNUC__ <= 14
 #pragma GCC diagnostic pop
 #endif
 const vcl::Window *pChild = rEntry.pChild;
@@ -1101,7 +1101,7 @@ static void calcMaxs(const array_type , 
std::vector ,
 {
 for (sal_Int32 y = 0; y < nMaxY; ++y)
 {
-#if defined __GNUC__ && !defined __clang__ && __GNUC__ == 13
+#if defined __GNUC__ && !defined __clang__ && __GNUC__ >= 13 && __GNUC__ <= 14
 #pragma GCC diagnostic push
 #pragma GCC diagnostic ignored "-Wdangling-reference"
 #elif defined _MSC_VER
@@ -1109,7 +1109,7 @@ static void calcMaxs(const array_type , 
std::vector ,
 #pragma warning(disable : 4459)
 #endif
 const GridEntry  = A[x][y];
-#if defined __GNUC__ && !defined __clang__ && __GNUC__ == 13
+#if defined __GNUC__ && !defined __clang__ && __GNUC__ >= 13 && __GNUC__ <= 14
 #pragma GCC diagnostic pop
 #elif defined _MSC_VER
 #pragma warning(pop)
@@ -1144,12 +1144,12 @@ static void calcMaxs(const array_type , 
std::vector ,
 {
 for (sal_Int32 y = 0; y < nMaxY; ++y)
 {
-#if defined __GNUC__ && !defined __clang__ && __GNUC__ == 13
+#if defined __GNUC__ && !defined __clang__ && __GNUC__ >= 13 && __GNUC__ <= 14
 #pragma GCC diagnostic push
 #pragma GCC diagnostic ignored "-Wdangling-reference"
 #endif
 const GridEntry  = A[x][y];
-#if defined __GNUC__ && !defined __clang__ && __GNUC__ == 13
+#if defined __GNUC__ && !defined __clang__ && __GNUC__ >= 13 && __GNUC__ <= 14
 #pragma GCC diagnostic pop
 #endif
 const vcl::Window *pChild = 

core.git: linguistic/source

2024-04-03 Thread Stephan Bergmann (via logerrit)
 linguistic/source/gciterator.cxx |   90 ++-
 linguistic/source/gciterator.hxx |   16 +++---
 2 files changed, 50 insertions(+), 56 deletions(-)

New commits:
commit b23019c566f2cbf50dfbec71d258b3e1a9ead312
Author: Stephan Bergmann 
AuthorDate: Wed Apr 3 23:32:51 2024 +0200
Commit: Stephan Bergmann 
CommitDate: Thu Apr 4 07:06:00 2024 +0200

Revert "osl::Mutex->std::mutex in GrammarCheckingIterator"

This reverts commit 829fa53fe877d0f0fc33d634fa7fbfbed23b7676, which started 
all
sorts of `make check` tests to hang for me due to a recursive locking 
attempt in

> #5  std::mutex::lock (this=0x7f6af81e62c0) at 
~/gcc/inst/include/c++/14.0.1/bits/std_mutex.h:113
> #6  std::unique_lock::lock (this=) at 
~/gcc/inst/include/c++/14.0.1/bits/unique_lock.h:147
> #7  std::unique_lock::unique_lock (this=, 
__m=...) at ~/gcc/inst/include/c++/14.0.1/bits/unique_lock.h:73
> #8  GrammarCheckingIterator::NextDocId (this=0x7f6af81e6260) at 
linguistic/source/gciterator.cxx:317
> #9  GrammarCheckingIterator::GetOrCreateDocId 
(this=this@entry=0x7f6af81e6260, xComponent=uno::Reference to (SwXTextDocument 
*) 0x7f6af8430ec8) at linguistic/source/gciterator.cxx:339
> #10 0x7f6b3b9e9da9 in GrammarCheckingIterator::startProofreading 
(this=0x7f6af81e6260, xDoc=, xIteratorProvider=) 
at linguistic/source/gciterator.cxx:773
> #11 0x7f6b16441ec3 in SwDoc::StartGrammarChecking (this=, bSkipStart=bSkipStart@entry=false) at sw/source/core/doc/docnew.cxx:180
> #12 0x7f6b164c4eae in sw::DocumentTimerManager::DoIdleJobs 
(this=0x7f6afad005a0) at sw/source/core/doc/DocumentTimerManager.cxx:169
> #13 0x7f6b3e83a68b in Scheduler::CallbackTaskScheduling () at 
vcl/source/app/scheduler.cxx:509
> #14 0x7f6b3eb1725f in SalTimer::CallCallback (this=) 
at vcl/inc/saltimer.hxx:54
> #15 SvpSalInstance::CheckTimeout (this=this@entry=0xffebe0, 
bExecuteTimers=bExecuteTimers@entry=true) at vcl/headless/svpinst.cxx:157
> #16 0x7f6b3eb1761d in SvpSalInstance::ImplYield 
(this=this@entry=0xffebe0, bWait=bWait@entry=true, 
bHandleAllCurrentEvents=bHandleAllCurrentEvents@entry=false) at 
vcl/headless/svpinst.cxx:395
> #17 0x7f6b3eb17cd5 in SvpSalInstance::DoYield (this=0xffebe0, 
bWait=, bHandleAllCurrentEvents=) at 
vcl/headless/svpinst.cxx:467
> #18 0x7f6b3e86aa44 in ImplYield (i_bWait=true, i_bAllEvents=false) at 
vcl/source/app/svapp.cxx:394
> #19 0x7f6b3e86b13b in Application::Execute () at 
vcl/source/app/svapp.cxx:369
> #20 0x7f6b3c8e715f in desktop::Desktop::Main (this=0x7ffe5e22fcb0) at 
desktop/source/app/app.cxx:1615
> #21 0x7f6b3e87e6fb in ImplSVMain () at vcl/source/app/svmain.cxx:229
> #22 0x7f6b3e87e9c5 in SVMain () at vcl/source/app/svmain.cxx:261
> #23 0x7f6b3c91de37 in soffice_main () at 
desktop/source/app/sofficemain.cxx:93
> #24 0x0040078b in sal_main () at desktop/source/app/main.c:51
> #25 main (argc=argc@entry=8, argv=argv@entry=0x7ffe5e22feb8) at 
desktop/source/app/main.c:49

Change-Id: I60b8b0ba00cae691d6089325e4379a86221dc95b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165764
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann 

diff --git a/linguistic/source/gciterator.cxx b/linguistic/source/gciterator.cxx
index bf37df637f4b..ad85bab95953 100644
--- a/linguistic/source/gciterator.cxx
+++ b/linguistic/source/gciterator.cxx
@@ -273,11 +273,19 @@ css::uno::Any SAL_CALL 
LngXStringKeyMap::getValueByIndex(::sal_Int32 nIndex)
 }
 
 
+osl::Mutex& GrammarCheckingIterator::MyMutex()
+{
+static osl::Mutex SINGLETON;
+return SINGLETON;
+}
+
 GrammarCheckingIterator::GrammarCheckingIterator() :
 m_bEnd( false ),
 m_bGCServicesChecked( false ),
 m_nDocIdCounter( 0 ),
-m_thread(nullptr)
+m_thread(nullptr),
+m_aEventListeners( MyMutex() ),
+m_aNotifyListeners( MyMutex() )
 {
 }
 
@@ -291,7 +299,7 @@ void GrammarCheckingIterator::TerminateThread()
 {
 oslThread t;
 {
-std::unique_lock aGuard( m_aMutex );
+::osl::Guard< ::osl::Mutex > aGuard( MyMutex() );
 t = m_thread;
 m_thread = nullptr;
 m_bEnd = true;
@@ -314,14 +322,13 @@ bool GrammarCheckingIterator::joinThreads()
 
 sal_Int32 GrammarCheckingIterator::NextDocId()
 {
-std::unique_lock aGuard( m_aMutex );
+::osl::Guard< ::osl::Mutex > aGuard( MyMutex() );
 m_nDocIdCounter += 1;
 return m_nDocIdCounter;
 }
 
 
 OUString GrammarCheckingIterator::GetOrCreateDocId(
-std::unique_lock& /*rGuard*/,
 const uno::Reference< lang::XComponent >  )
 {
 // internal method; will always be called with locked mutex
@@ -347,7 +354,6 @@ OUString GrammarCheckingIterator::GetOrCreateDocId(
 
 
 void GrammarCheckingIterator::AddEntry(
-std::unique_lock& /*rGuard*/,
 const uno::Reference< text::XFlatParagraphIterator >& xFlatParaIterator,
 const 

[Bug 160332] Bug when trying to use dark mode with Mac.

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160332

Buovjaga  changed:

   What|Removed |Added

Version|3.3.0 release   |24.2.0.3 release

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158181] (LibreOffice Math) black text in dark background (dark theme) makes text "invisible" in formula editor

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158181

--- Comment #4 from Haris  ---
Thank you for reporting the bug. I can not reproduce the bug in

Stable Build
Version: 24.2.2.2 (AARCH64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 10; OS: macOS 14.1.2; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Master/Daily Build
Version: 24.8.0.0.alpha0+ (AARCH64) / LibreOffice Community
Build ID: c4023d3ec604abfff38be2053e2989c7ec2ba8c1
CPU threads: 10; OS: macOS 14.1.2; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157936] Calc EDITING: pressing context menu key in a cell causes context menus of calc as well as the cell to popup at same time with focus on calc context menu

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157936

--- Comment #3 from Haris  ---
Thank you for reporting the bug, it is no longer present in the following two
builds:

Stable Build
Version: 24.2.2.2 (AARCH64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 10; OS: macOS 14.1.2; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Master/Daily Build
Version: 24.8.0.0.alpha0+ (AARCH64) / LibreOffice Community
Build ID: c4023d3ec604abfff38be2053e2989c7ec2ba8c1
CPU threads: 10; OS: macOS 14.1.2; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160391] Font color of the menu bar stays black when changing win10/11 from light to dark mode

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160391

Kira Tubo  changed:

   What|Removed |Added

   Keywords|bibisectRequest |bibisected, bisected

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157420] Allow setting a default Date and Time format for fields (see comment 12)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157420

--- Comment #17 from Mike Kaganski  ---
I believe, that instead of such a specific setting, a way to define
/program-wide/ default date/time format would be anough and much better, i.e.
fixing Bug 46448 would fix this as well. But implementing this separately would
introduce a fragmentation (this part of program uses this, that part of the
program uses that), and so is not good.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 107326] [META] Writer style bugs and enhancements

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107326

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||145518


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=145518
[Bug 145518] Add Comment / Annotation field to Writer Styles' Organizer tab
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 145518] Add Comment / Annotation field to Writer Styles' Organizer tab

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145518

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
Summary|Feature suggestion -- add   |Add Comment / Annotation
   |Comments field to Styles|field to Writer Styles'
   ||Organizer tab
 Blocks|106179  |107326
Version|7.2.2.2 release |Inherited From OOo

--- Comment #12 from Stéphane Guillou (stragu) 
 ---
(Not really about "Writer comments", changing to "Writer styles" meta bug
107326.)


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=106179
[Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107326
[Bug 107326] [META] Writer style bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 106179] [META] Writer comment bugs and enhancements

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106179

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on|145518  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=145518
[Bug 145518] Add Comment / Annotation field to Writer Styles' Organizer tab
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160276] Writer comment: Author and Date info should use same padding as is used for comment text

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160276

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
Created attachment 193477
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193477=edit
screenshot with "reply to" header, and "resolved" status

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160276] Writer comment: Author and Date info should use same padding as is used for comment text

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160276

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
Created attachment 193477
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193477=edit
screenshot with "reply to" header, and "resolved" status

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160276] Writer comment: Author and Date info should use same padding as is used for comment text

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160276

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||106179


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=106179
[Bug 106179] [META] Writer comment bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160276] Writer comment: Author and Date info should use same padding as is used for comment text

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160276

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||106179


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=106179
[Bug 106179] [META] Writer comment bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 106179] [META] Writer comment bugs and enhancements

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106179

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||160276


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160276
[Bug 160276] Writer comment: Author and Date info should use same padding as is
used for comment text
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160276] Writer comment: Author and Date info should use same padding as is used for comment text

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160276

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
Version|3.3.0 release   |24.8.0.0 alpha0+ Master
   Keywords||bibisected, bisected,
   ||needsUXEval

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
OOo 3.3 and 24.2.2.2 have both flush to the left border.
Padding was added by 1dc0c8c8304ebbce0a2e05e89a3b5458d88f3630 for bug 159531 
(should have looked at the "see also" before bibisecting, but I was mislead by
the 3.3 as earliest version affected )

Heiko says in bug 159531 comment 9:
> Different code, probably not easy to find. Having the author information 
> drawn differently to the content is not bad (although spacing is our friend).

Note that the "Reply to" header has the same padding as the comment.

I agree that the spacing of the authorship info could be improved, it feels too
close to the edge now that everything else is spaced. And there is no extra
space between text and authorship info.

More opinion from other UX/Design contributors?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160276] Writer comment: Author and Date info should use same padding as is used for comment text

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160276

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
Version|3.3.0 release   |24.8.0.0 alpha0+ Master
   Keywords||bibisected, bisected,
   ||needsUXEval

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
OOo 3.3 and 24.2.2.2 have both flush to the left border.
Padding was added by 1dc0c8c8304ebbce0a2e05e89a3b5458d88f3630 for bug 159531 
(should have looked at the "see also" before bibisecting, but I was mislead by
the 3.3 as earliest version affected )

Heiko says in bug 159531 comment 9:
> Different code, probably not easy to find. Having the author information 
> drawn differently to the content is not bad (although spacing is our friend).

Note that the "Reply to" header has the same padding as the comment.

I agree that the spacing of the authorship info could be improved, it feels too
close to the edge now that everything else is spaced. And there is no extra
space between text and authorship info.

More opinion from other UX/Design contributors?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 160468] Alt+F4 is marked reserved, but doesn't do anything

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160468

BogdanB  changed:

   What|Removed |Added

 Resolution|FIXED   |WORKSFORME
 CC||buzea.bog...@libreoffice.or
   ||g

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157420] Allow setting a default Date and Time format for fields (see comment 12)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157420

--- Comment #16 from QA Administrators  ---
[Automated Action] NeedInfo-To-Unconfirmed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 159464] Short text in sections combined with long endnotes makes parts of text hidden under red arrow

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159464

--- Comment #6 from QA Administrators  ---
[Automated Action] NeedInfo-To-Unconfirmed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 154977] Changing the paragraph area of a style makes LO crash

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154977

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.

[Bug 154977] Changing the paragraph area of a style makes LO crash

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154977

--- Comment #22 from QA Administrators  ---
[Automated Action] NeedInfo-To-Unconfirmed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 155270] [ Calc - 7.5.3.2 (X86_64) / LibreOffice Community ] [ 3x issues identified while using Pivot table, 2x EDITING / FORMATTING and 1x UI ]

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155270

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 156426] Gregorian Date before 1582

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156426

--- Comment #5 from QA Administrators  ---
Dear rwk,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 156316] Position and Size command is not working properly in Writer RC1.

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156316

--- Comment #5 from QA Administrators  ---
Dear TseRigs,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 155270] [ Calc - 7.5.3.2 (X86_64) / LibreOffice Community ] [ 3x issues identified while using Pivot table, 2x EDITING / FORMATTING and 1x UI ]

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155270

--- Comment #9 from QA Administrators  ---
Dear James,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 146528] not recognizing scroll from logitech trackball marble (T-BC21) viewing

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146528

--- Comment #3 from QA Administrators  ---
Dear Rich Little,

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.

[Bug 147845] Copying an entire cell in Libre Office Calc and pasting it into Adobe InDesign breaks the clipboard

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147845

--- Comment #2 from QA Administrators  ---
Dear Raúl Mesa,

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.

[Bug 121210] IMPORT: No possibility to set Auto Value to a Integer Primary Key when importing Calc range

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121210

--- Comment #18 from QA Administrators  ---
Dear Robert Großkopf,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 105429] Names of new default set of cell styles not localized

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=105429

--- Comment #16 from QA Administrators  ---
Dear Leif Lodahl,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160228] Online Update always offers an update when starting LibreOffice, even if it is up to date

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160228

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Summary|Online Update never |Online Update always offers
   |finishes proposing the  |an update when starting
   |update when starting|LibreOffice, even if it is
   |LibreOffice, even if it is  |up to date
   |up to date. |

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
Right, so:
1. in 24.2.1, turn on online updates
2. download the update to 24.2.2 when prompted, install the update
3. restart the newly updated 24.2.2
Result: LO still prompts to update
Workaround: delete update temp file

Is that correct?
Not able to test right now as I am not offered the update on 24.2.1.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158456] FILEOPEN, FILESAVE. Corrupted ODS file opens slowly and increases in size after saving

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158456

--- Comment #7 from Armondo Lopez  ---
In both of these versions:

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
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

and

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
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

The size of the file went from 1.02 MB to 11.2 MB.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 146014] [META] Poor Scrolling Performance

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146014

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||153111


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153111
[Bug 153111] Terrible performance when scrolling on Wayland
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 153111] Terrible performance when scrolling on Wayland

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153111

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Keywords||perf
 Blocks||146014


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=146014
[Bug 146014] [META] Poor Scrolling Performance
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 152911] VIEWING - High CPU and lag when scrolling on Wayland with modified display scale (KF5)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152911

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||matej.st...@protonmail.com

--- Comment #16 from Stéphane Guillou (stragu) 
 ---
*** Bug 160235 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160235] Scroll lag with kf5 (cairo+wayland) VCL plugin, no lag with gtk3 (libreoffice-qt5 uninstalled)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160235

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEEDINFO|RESOLVED
Summary|Libreoffice lags if not |Scroll lag with kf5
   |using skia as a renderer|(cairo+wayland) VCL plugin,
   ||no lag with gtk3
   ||(libreoffice-qt5
   ||uninstalled)

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
I think the best match is bug 152911 (kf5 cairo+wayland, scaling on, large
display).
Thank you!

*** This bug has been marked as a duplicate of bug 152911 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 147639] Incorrect zoom (except for menubar) on enabling fractional scaling on KDE Wayland

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147639

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=14 |
   |1578|

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 141578] Libreoffice unusable with different scale factors used for different screens in multimonitor setup (on kf5/qt5/qt6 vcl + wayland)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141578

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also|https://bugs.documentfounda |https://bugs.documentfounda
   |tion.org/show_bug.cgi?id=14 |tion.org/show_bug.cgi?id=15
   |7639|9915

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160391] Font color of the menu bar stays black when changing win10/11 from light to dark mode

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160391

Kira Tubo  changed:

   What|Removed |Added

 CC||caolan.mcnamara@collabora.c
   ||om, kira.t...@gmail.com
  Regression By||Caolán McNamara

--- Comment #5 from Kira Tubo  ---
Bibisected win64-7.6. Added Caolán McNamara to cc. 

Regression first occurs at:
https://git.libreoffice.org/core/+/f7c03364e24da285ea95cea0cc688a7a120fc163%5E%21



commit  f7c03364e24da285ea95cea0cc688a7a120fc163[log]
author  Caolán McNamara Mon Feb 06 20:53:55 2023 +
committer   Caolán McNamara Wed Feb 08 16:11:25
2023 +
treeb6dc20e02654f5144daea807303dbdd71a72bba0
parent  68ab2e109edf8b81c48e953f7c8d43841e07365a [diff]

-

Reproduced on:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: f7c03364e24da285ea95cea0cc688a7a120fc163
CPU threads: 6; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160249] Support marking text as having an arbitrary language

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160249

--- Comment #7 from Stéphane Guillou (stragu) 
 ---
(In reply to Eyal Rozenberg from comment #6)
> (In reply to Stéphane Guillou (stragu) from comment #2)
> > We already have "no language"
> 
> Do we have "no language"? Where?
Isn't that what "[None]" is?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157403] UI: Navigator in Sidebar does not show new slide/page or objects after file reload (Impress/Draw)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157403

--- Comment #5 from Jim Raykowski  ---
I've been poking around the Draw/Impress Navigator code lately trying to
improve some things. Here is a link to a patch that appears to make this bug go
away:
https://gerrit.libreoffice.org/c/core/+/165767

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 155012] Same Help page used for Sign Document and Encrypt Document dialogs

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155012

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
Thanks for looking into it, Dione! For the X.509 title, this issue is relevant:
bug 155049.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160228] Online Update never finishes proposing the update when starting LibreOffice, even if it is up to date.

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160228

m_a_riosv  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160228] Online Update never finishes proposing the update when starting LibreOffice, even if it is up to date.

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160228

--- Comment #2 from m_a_riosv  ---
I delete the temp files created to online update when detects a new version,
and the issue has disappeared.

Every time I start LibreOffice, it presents the automatic update window even if
it was already updated.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160496] Viewport jumps after moving cursor to different style

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160496

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||106773
 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
Hm I understand a jump is expected to have a full view of the page, but the
delay is jarring. Try this:
- place cursor at bottom of page
- press arrow down to go to the next page
Results: viewport jumps to next page to show half the page, then updates after
the delay to show the whole page.
In my opinion, if the Zoom settings means "single entire page that has the
cursor is shown", it should do it straight away and not have that delay that
makes it a two-step jump.

For some reason, I reproduce very inconsistently, I am missing something in the
steps to always get the same result. At least, I have see the jump in:

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: f2482fd96eff00b806fae385096531f63f5f2bf5
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded

But now I can't reproduce in any version.

Tyler, any chance you can provide more precise steps? The document doesn't have
the line "put cursor here".


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=106773
[Bug 106773] [META] Writer document canvas view / viewport jump issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 106773] [META] Writer document canvas view / viewport jump issues

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106773

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||160496


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160496
[Bug 160496] Viewport jumps after moving cursor to different style
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157420] Allow setting a default Date and Time format for fields (see comment 12)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157420

--- Comment #15 from FaithfulScuff  ---
(In reply to Stéphane Guillou (stragu) from comment #14)
> (let's stick to the earliest version affected; it is consistent with when
> you reported the issue)
> Can you please confirm that the remaining issue is that you'd like to be
> able to define a default format for inserted date and time fields?

Yes, I can confirm that being able to define a default format for date and time
would be wonderful.

Thank you for the consideration.

-- 
You are receiving this mail because:
You are the assignee for the bug.

core.git: editeng/source

2024-04-03 Thread Tomaž Vajngerl (via logerrit)
 editeng/source/editeng/ContentNode.cxx |   32 
 1 file changed, 24 insertions(+), 8 deletions(-)

New commits:
commit 5ebe81f068dba0c141ebe92f64731d0c95179dae
Author: Tomaž Vajngerl 
AuthorDate: Mon Mar 25 16:28:39 2024 +0900
Commit: Tomaž Vajngerl 
CommitDate: Thu Apr 4 04:06:40 2024 +0200

editeng: make it ContentNode::FindFeature clearer

Change-Id: Ia3498df3cb11b06ac71e3c75839cc98cc0f3d88c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165337
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl 

diff --git a/editeng/source/editeng/ContentNode.cxx 
b/editeng/source/editeng/ContentNode.cxx
index a02a3fde0d39..08bf250b6c86 100644
--- a/editeng/source/editeng/ContentNode.cxx
+++ b/editeng/source/editeng/ContentNode.cxx
@@ -947,16 +947,20 @@ EditCharAttrib* CharAttribList::FindEmptyAttrib( 
sal_uInt16 nWhich, sal_Int32 nP
 return nullptr;
 }
 
-namespace {
+namespace
+{
 
 class FindByStartPos
 {
 sal_Int32 mnPos;
 public:
-explicit FindByStartPos(sal_Int32 nPos) : mnPos(nPos) {}
-bool operator() (const std::unique_ptr& r) const
+explicit FindByStartPos(sal_Int32 nPos)
+: mnPos(nPos)
+{}
+
+bool operator() (std::unique_ptr const& pCharAttrib) const
 {
-return r->GetStart() >= mnPos;
+return pCharAttrib->GetStart() >= mnPos;
 }
 };
 
@@ -965,16 +969,28 @@ public:
 const EditCharAttrib* CharAttribList::FindFeature( sal_Int32 nPos ) const
 {
 // First, find the first attribute that starts at or after specified 
position.
-AttribsType::const_iterator it =
+AttribsType::const_iterator iterator =
 std::find_if(maAttribs.begin(), maAttribs.end(), FindByStartPos(nPos));
 
-if (it == maAttribs.end())
+if (iterator == maAttribs.end())
+{
 // All attributes are before the specified position.
 return nullptr;
+}
 
 // And find the first attribute with feature.
-it = std::find_if(it, maAttribs.end(), [](const 
std::unique_ptr& aAttrib) { return aAttrib->IsFeature(); } );
-return it == maAttribs.end() ? nullptr : it->get();
+iterator = std::find_if(iterator, maAttribs.end(), [](const 
std::unique_ptr& aAttrib) {
+return aAttrib->IsFeature();
+});
+
+if (iterator == maAttribs.end())
+{
+// Couldn't find the feature
+return nullptr;
+}
+
+// Found
+return iterator->get();
 }
 
 void CharAttribList::DeleteEmptyAttribs()


core.git: editeng/inc editeng/source

2024-04-03 Thread Tomaž Vajngerl (via logerrit)
 editeng/inc/EditLine.hxx|  130 ++--
 editeng/source/editeng/EditLine.cxx |   75 +++-
 2 files changed, 106 insertions(+), 99 deletions(-)

New commits:
commit 7f4d31f2d6f37d280ae3e65c86077a7423dff0cc
Author: Tomaž Vajngerl 
AuthorDate: Wed Mar 20 14:15:23 2024 +0900
Commit: Tomaž Vajngerl 
CommitDate: Thu Apr 4 04:06:20 2024 +0200

editeng: prefix EditLine members, clean-up

Change-Id: Ie8c8ee86f139854137ba95875f51ddaf64cc5848
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165336
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl 

diff --git a/editeng/inc/EditLine.hxx b/editeng/inc/EditLine.hxx
index 7d4a43e0e639..46a2379853e6 100644
--- a/editeng/inc/EditLine.hxx
+++ b/editeng/inc/EditLine.hxx
@@ -31,105 +31,107 @@ public:
 typedef std::vector CharPosArrayType;
 
 private:
-CharPosArrayType aPositions;
-std::vector aKashidaPositions;
-sal_Int32 nTxtWidth = 0;
-sal_Int32 nStartPosX = 0;
-sal_Int32 nNextLinePosXDiff = 0;
-sal_Int32 nStart = 0; // could be replaced by nStartPortion
-sal_Int32 nEnd = 0; // could be replaced by nEndPortion
-sal_Int32 nStartPortion = 0;
-sal_Int32 nEndPortion = 0;
-sal_uInt16 nHeight = 0; //  Total height of the line
-sal_uInt16 nTxtHeight = 0; // Pure Text height
-sal_uInt16 nMaxAscent = 0;
-bool bHangingPunctuation : 1 = false;
-bool bInvalid : 1 = true; // for skillful formatting
+CharPosArrayType maPositions;
+std::vector maKashidaPositions;
+sal_Int32 mnTextWidth = 0;
+sal_Int32 mnStartPosX = 0;
+sal_Int32 mnNextLinePosXDiff = 0;
+sal_Int32 mnStart = 0; // could be replaced by nStartPortion
+sal_Int32 mnEnd = 0; // could be replaced by nEndPortion
+sal_Int32 mnStartPortion = 0;
+sal_Int32 mnEndPortion = 0;
+sal_uInt16 mnHeight = 0; //  Total height of the line
+sal_uInt16 mnTextHeight = 0; // Pure Text height
+sal_uInt16 mnMaxAscent = 0;
+bool mbHangingPunctuation : 1 = false;
+bool mbInvalid : 1 = true; // for skillful formatting
 
 public:
 EditLine() = default;
 EditLine(const EditLine& rEditLine)
-: nStart(rEditLine.nStart)
-, nEnd(rEditLine.nEnd)
-, nStartPortion(rEditLine.nStartPortion)
-, nEndPortion(rEditLine.nEndPortion)
-, bHangingPunctuation(rEditLine.bHangingPunctuation)
-, bInvalid(true)
+: mnStart(rEditLine.mnStart)
+, mnEnd(rEditLine.mnEnd)
+, mnStartPortion(rEditLine.mnStartPortion)
+, mnEndPortion(rEditLine.mnEndPortion)
+, mbHangingPunctuation(rEditLine.mbHangingPunctuation)
 {
 }
 
-bool IsIn(sal_Int32 nIndex) const { return ((nIndex >= nStart) && (nIndex 
< nEnd)); }
+bool IsIn(sal_Int32 nIndex) const { return nIndex >= mnStart && nIndex < 
mnEnd; }
 
-bool IsIn(sal_Int32 nIndex, bool bInclEnd) const
+bool IsIn(sal_Int32 nIndex, bool bIncludeEnd) const
 {
-return ((nIndex >= nStart) && (bInclEnd ? (nIndex <= nEnd) : (nIndex < 
nEnd)));
+return nIndex >= mnStart && (bIncludeEnd ? nIndex <= mnEnd : nIndex < 
mnEnd);
 }
 
-void SetStart(sal_Int32 n) { nStart = n; }
-sal_Int32 GetStart() const { return nStart; }
-sal_Int32& GetStart() { return nStart; }
+void SetStart(sal_Int32 nStart) { mnStart = nStart; }
+sal_Int32 GetStart() const { return mnStart; }
+sal_Int32& GetStart() { return mnStart; }
 
-void SetEnd(sal_Int32 n) { nEnd = n; }
-sal_Int32 GetEnd() const { return nEnd; }
-sal_Int32& GetEnd() { return nEnd; }
+void SetEnd(sal_Int32 nEnd) { mnEnd = nEnd; }
+sal_Int32 GetEnd() const { return mnEnd; }
+sal_Int32& GetEnd() { return mnEnd; }
 
-void SetStartPortion(sal_Int32 n) { nStartPortion = n; }
-sal_Int32 GetStartPortion() const { return nStartPortion; }
-sal_Int32& GetStartPortion() { return nStartPortion; }
+void SetStartPortion(sal_Int32 nStartPortion) { mnStartPortion = 
nStartPortion; }
+sal_Int32 GetStartPortion() const { return mnStartPortion; }
+sal_Int32& GetStartPortion() { return mnStartPortion; }
 
-void SetEndPortion(sal_Int32 n) { nEndPortion = n; }
-sal_Int32 GetEndPortion() const { return nEndPortion; }
-sal_Int32& GetEndPortion() { return nEndPortion; }
+void SetEndPortion(sal_Int32 nEndPortion) { mnEndPortion = nEndPortion; }
+sal_Int32 GetEndPortion() const { return mnEndPortion; }
+sal_Int32& GetEndPortion() { return mnEndPortion; }
 
-void SetHeight(sal_uInt16 nH, sal_uInt16 nTxtH = 0);
-sal_uInt16 GetHeight() const { return nHeight; }
-sal_uInt16 GetTxtHeight() const { return nTxtHeight; }
+void SetHeight(sal_uInt16 nHeight, sal_uInt16 nTextHeight = 0);
+sal_uInt16 GetHeight() const { return mnHeight; }
+sal_uInt16 GetTxtHeight() const { return mnTextHeight; }
 
-void SetTextWidth(sal_Int32 n) { nTxtWidth = n; }
-sal_Int32 GetTextWidth() const { 

[Bug 160512] CRASH Writer Hangs completely when copying complete file, even small file

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160512

--- Comment #3 from m_a_riosv  ---
No matter, with 24.8 if Skia is enabled or not.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160512] CRASH Writer Hangs completely when copying complete file, even small file

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160512

m_a_riosv  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160467] [NEWHELP] CSS issue with Help pages for prism code colorize

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160467

Juan José  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

--- Comment #2 from Juan José  ---
Change to fix it:

https://gerrit.libreoffice.org/c/help/+/165768

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160512] CRASH Writer Hangs completely when copying complete file, even small file

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160512

m_a_riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg
   Keywords||bibisectRequest, regression

--- Comment #2 from m_a_riosv  ---
Not reproducible with
Version: 7.5.9.2 (X86_64) / LibreOffice Community
Build ID: cdeefe45c17511d326101eed8008ac4092f278a9
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded

I can reproduce with attached file, but deleting the empty paragraph at the
end, seems to avoid the issue.
Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded

With
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: b0edb1909b9deb1a170497f935a528f8118c8308
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: threaded
just crash after opening the file just in the tip box, even in Safe Mode.
Without LO detect the crash at reopening.

Attached the result of odf validator.
https://odfvalidator.org/

ODF Validator Result Page
Result for kopjes boven volledige code.odt

The document is NOT conformant ODF1.3!
Details:
kopjes boven volledige code.odt: Info: ODF version of root document: 1.3
internal:/schema/odf1.3/OpenDocument-v1.3-manifest-schema.rng: Info: parsed.
kopjes boven volledige code.odt/META-INF/manifest.xml: Info: no errors, no
warnings
kopjes boven volledige code.odt/mimetype: Info: no errors, no warnings
kopjes boven volledige code.odt: Info: Media Type:
application/vnd.oasis.opendocument.text
internal:/schema/odf1.3/OpenDocument-v1.3-schema.rng: Info: parsed.
kopjes boven volledige code.odt/meta.xml: Info: Generator:
LibreOffice/24.2.2.2$Linux_X86_64 LibreOffice_project/420$Build-2
kopjes boven volledige code.odt/meta.xml: Info: no errors, no warnings
kopjes boven volledige code.odt/settings.xml: Info: no errors, no warnings
kopjes boven volledige code.odt/styles.xml[2,3149]: Error: element
"loext:gradient-stop" was found where no element may occur
ype="rgb" 

[Bug 157420] Allow setting a default Date and Time format for fields (see comment 12)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157420

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Version|24.2.1.2 release|7.6.1.2 release

--- Comment #14 from Stéphane Guillou (stragu) 
 ---
(let's stick to the earliest version affected; it is consistent with when you
reported the issue)
Can you please confirm that the remaining issue is that you'd like to be able
to define a default format for inserted date and time fields?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158663] LibreOffice 7.6.4.1 hangs on startup after opening initial window and showing splash screen on Arch Linux

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158663

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Resolution|FIXED   |WORKSFORME

--- Comment #6 from Stéphane Guillou (stragu) 
 ---
Thanks for reporting back!
Let's close as "works for me", as "fixed" is for when a patch has been
identified.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160508] The overall interface is very very slow on Windows 11

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160508

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||stephane.guillou@libreoffic
   ||e.org
 Ever confirmed|0   |1

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
Please also check if:
- restarting LO in safe mode helps
- version 24.2.2 is out, might be worth giving it a try

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157547] FILEOPEN "Write error. The file could not be written"

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157547

Kira Tubo  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Kira Tubo  ---
(In reply to Michael Dewsbury from comment #5)
> Issue no longer occurs.
> Previously, when trying to open a document, I received th error: "Write
> error. the file could not be written."

Thanks for confirming, Michael. I'll go ahead and close this ticket.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 145698] UI: Sidebar is showing horizontal scrollbar in Writer

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145698

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=16
   ||0513

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160513] Table guides not visible after upgrade from 7.5.9 to 7.6.6

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160513

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Summary|Incompatibilities and   |Table guides not visible
   |regressions (7.5.9 ->   |after upgrade from 7.5.9 to
   |7.6.6)  |7.6.6
 CC||stephane.guillou@libreoffic
   ||e.org
 Ever confirmed|0   |1
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||5698
 Status|UNCONFIRMED |NEEDINFO

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
Thanks for the report. Please note that we try to only have one issue per
report, so it is more likely it will get actioned.

(In reply to Ulrich Windl from comment #0)
> 1) The selector for the styles (like "All styles", "Used styles", etc.) was
> almost unreadable due to a scrollbar issue. The issue vanished when
> horizontally resizing the frame (making it wider), and it could not be
> reproduced when making the frame more narrow again.
This is already tracked in bug 145698.

> 2) The guide showing the text area does not appear any more, and I found no
> setting to make it appear.
I tested in 7.6.6 and could not reproduce. I tested inserting a table with
borders (via the toolbar, shows the borders) and without (via Table > Insert
table, shows the cell boundaries).

Version: 7.6.6.3 (X86_64) / LibreOffice Community
Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7
CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

Visibility of table borders and boundaries depend on a few settings:
- display of tables with Tools > Options > LibreOffice Writer > View > Display
> Tables (on by default)
- automatic borders when table inserted via toolbar widget with Tools > Options
> LibreOffice Writer > Table > New Table Defaults (on by default)
- when the table has no border (for example when inserting one with Table >
Insert Table), display (and colour) of boundaries controlled by Tools > Options
> LibreOffice > Application Colors > General Table Boundaries (on by default)

Can you please:
- test in safe mode / with a new profile (after backing it up if you don't want
to lose your settings): https://wiki.documentfoundation.org/UserProfile
- paste here the full version information copied from Help > About LibreOffice
- check the settings I listed above
- give precise steps to reproduce the issue with the table

Thank you!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 137303] "This PDF file is encrypted and can't be opened. " when opening any pdf file from Draw

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137303

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Stéphane Guillou (stragu) 
 ---
Thank you. The fact that you said "this behaviour is restricted to a single
Windows Session" makes it seem like the same issue as bug 160260, which is now
resolved. Let's mark as duplicate.
Cheers! :)

*** This bug has been marked as a duplicate of bug 160260 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160514] Usability of accessibility check (Alt+7)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160514

Ulrich Windl  changed:

   What|Removed |Added

 CC||u20230...@gmail.com

--- Comment #1 from Ulrich Windl  ---
Created attachment 193475
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193475=edit
Screenshot showing the results of accessibility checking

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160514] New: Usability of accessibility check (Alt+7)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160514

Bug ID: 160514
   Summary: Usability of accessibility check (Alt+7)
   Product: LibreOffice
   Version: 7.6.6.3 release
  Hardware: x86 (IA32)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: u20230...@gmail.com

Description:
The usability of the accessibility check is terrible IMHO:
In the separate frame where the issues are listen one has to press the RIGHT
mouse button on the links to see the targets in the text area; using the normal
left mouse button seems to do nothing!

* The check complains if a hyperlink is rendered as the hyperlinks itself;
however specifically for printed media that makes a lot of sense.

* The check complains about "empty lines", but the links seem to address no
target; *where are those empty lines?*

* For a formula object it complains about the lack of "alt text"; shouldn't the
formula editor create that automatically? Having an "alt text" like "Formula 2"
would not be helpful.

Steps to Reproduce:
1. Have some "normal" text document
2. Open the  accessibility check (Alt+7) window


Actual Results:
Most messages are useless or not helpful.

Expected Results:
The checks should help the user to fix real problems.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.6.3 (x86) / LibreOffice Community
Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160513] Incompatibilities and regressions (7.5.9 -> 7.6.6)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160513

--- Comment #3 from Ulrich Windl  ---
You can see the guides for text area in attachment #193469.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160513] Incompatibilities and regressions (7.5.9 -> 7.6.6)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160513

--- Comment #2 from Ulrich Windl  ---
Created attachment 193474
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193474=edit
Screenshot showing the lack of guides for text area (table)

When inserting a table the lack of guidelines for the text area is most
obvious!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160513] Incompatibilities and regressions (7.5.9 -> 7.6.6)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160513

Ulrich Windl  changed:

   What|Removed |Added

 CC||u20230...@gmail.com

--- Comment #1 from Ulrich Windl  ---
Created attachment 193473
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193473=edit
Frame showing the styles after having resized it

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160513] New: Incompatibilities and regressions (7.5.9 -> 7.6.6)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160513

Bug ID: 160513
   Summary: Incompatibilities and regressions (7.5.9 -> 7.6.6)
   Product: LibreOffice
   Version: 7.6.6.3 release
  Hardware: x86 (IA32)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: u20230...@gmail.com

Created attachment 193472
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193472=edit
Frame showing the styles after having upgraded Writer

After upgrading from LibreOffice 7.5.9 to 7.6.6 I immediately noticed two
incompatibilities (regressions):

1) The selector for the styles (like "All styles", "Used styles", etc.) was
almost unreadable due to a scrollbar issue. The issue vanished when
horizontally resizing the frame (making it wider), and it could not be
reproduced when making the frame more narrow again.

2) The guide showing the text area does not appear any more, and I found no
setting to make it appear.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160235] Libreoffice lags if not using skia as a renderer

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160235

--- Comment #3 from Matej Starc  ---
It seems it runs smoothly when using x11. If you need someone to test or to
provide certain logs, I can do that.

This can now be flagged as a duplicate, I think.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 133092] [META] Crash bugs

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092
Bug 133092 depends on bug 157203, which changed state.

Bug 157203 Summary: CRASH when reset drawing object area fill to NONE
https://bugs.documentfoundation.org/show_bug.cgi?id=157203

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 103223] [META] Area fill tab bugs and enhancements

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103223
Bug 103223 depends on bug 157203, which changed state.

Bug 157203 Summary: CRASH when reset drawing object area fill to NONE
https://bugs.documentfoundation.org/show_bug.cgi?id=157203

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157203] CRASH when reset drawing object area fill to NONE

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157203

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Priority|medium  |high
 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #27 from Stéphane Guillou (stragu) 
 ---
Matt, I understand you never reproduce this crash, even in earlier versions?
There is something inconsistent, some testers say it only happens with the
tabbed UI, others can reproduce with the toolbars.

Bug 160453 reporter also says it is fixed in 24.2, as in comment 18, so let's
mark as "works for me". Other users affected: please double-check that it is
indeed fixed for you in 24.2. If not, please provide precise steps again.

If anyone can give it a go, a bibisect for the cause and/or the fix would still
be really appreciated: https://bibisect.libreoffice.org/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160235] Libreoffice lags if not using skia as a renderer

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160235

--- Comment #2 from Matej Starc  ---
I'd like to correct myself as well. I does not run smoothly on my pc. Not at
all actually. It runs worse than on my laptop (sadly i cannot get you logs from
my pc right now because I nowhere near it).

Here is the information. I have a 90hz 2880x1800 screen on my laptop and I use
135% scaling in plasma settings (but this does not affect the programs
performance).

Libreoffice
Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: 420(Build:2)
CPU threads: 16; OS: Linux 6.8; UI render: default; VCL: kf5 (cairo+wayland)
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 157203] CRASH when reset drawing object area fill to NONE

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157203

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=16 |
   |0453|
 CC||thomascarr...@gmail.com

--- Comment #26 from Stéphane Guillou (stragu) 
 ---
*** Bug 160453 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160453] LibreOffice Calc crashes when you change the background of the cells to "none".

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160453

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |DUPLICATE
   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=15 |
   |7203|

--- Comment #9 from Stéphane Guillou (stragu) 
 ---
Thanks Thomas. Let's consolidate into bug 157203.

*** This bug has been marked as a duplicate of bug 157203 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158957] Keyboard inputs handled incorrectly on "end of slide" screen (Wayland)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158957

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #9 from Stéphane Guillou (stragu) 
 ---
Not reproduced on Ubuntu 22.04 with Wayland and:

Version: 7.6.6.3 (X86_64) / LibreOffice Community
Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded

I tried the steps in comment 0 as well as in the slideshow.

Do you test with a multi-monitor setup or single display?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 133092] [META] Crash bugs

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||160493


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160493
[Bug 160493] Crash with floating table when changing to specific font size
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160493] Crash with floating table when changing to specific font size

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160493

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||133092
Crash report or|https://crashreport.libreof |
crash signature|fice.org/stats/crash_detail |
   |s/2aae081f-3599-4d36-9506-8 |
   |365850dac7b |
   Severity|normal  |critical
 CC||stephane.guillou@libreoffic
   ||e.org,
   ||vmik...@collabora.com
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||8801

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
Regarding the fileopen crash:

(m_a_riosv, your crash report
https://crashreport.libreoffice.org/stats/crash_details/2aae081f-3599-4d36-9506-8365850dac7b
doesn't lead to anything, not sure why.)

I also get a crash on open in 7.6.6.3 and 24.2.2.2:
https://crashreport.libreoffice.org/stats/crash_details/209449ce-fa0d-4f03-98cb-05e6716f9a7c
(same signature ["SwTabFrame::MakeAll(OutputDevice*)"] as for bug 158344)
...but it is fixed in master. In linux-64-24.8, it stopped crashing at build
[ba26d9d81765ca45f3e8383714cf2b8eb077c07f] which is:

commit  186de7178c6065e1de13fd216b46ac9b716e44c5
author  Miklos VajnaThu Feb 29 08:17:41 2024 +0100
committer   Miklos VajnaThu Feb 29 11:39:54 2024 +0100
tdf#158801 sw floattable: fix crash with headers and interactive editing
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/164136

The cherrypick to 24.2 hasn't been merged yet:
https://gerrit.libreoffice.org/c/core/+/164119

@miklos, you'd rather not get that in 7.6 because
https://gerrit.libreoffice.org/c/core/+/163805 is not cherrypicked to that
branch, correct?

---

Regarding the font size crash:

I reproduce in a recent trunk build too. It already crashes at the above quoted
commit.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=133092
[Bug 133092] [META] Crash bugs
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160493] Crash with floating table when changing to specific font size

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160493

Telesto  changed:

   What|Removed |Added

   Keywords||wantBacktrace
 CC||serval2...@yahoo.fr

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 139532] [META] DOCX Floating table related issues

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139532

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158801


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158801
[Bug 158801] CRASH: after pressing return a few times
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 133092] [META] Crash bugs

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||158801


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=158801
[Bug 158801] CRASH: after pressing return a few times
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160512] CRASH Writer Hangs completely when copying complete file, even small file

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160512

--- Comment #1 from Armondo Lopez  ---
I wasn't able to reproduce the bug in 

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
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

or

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
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.

[Bug 160485] FILESAVE: Some Cells Text missing in EXPORT.png with highresolution.

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160485

--- Comment #1 from Armondo Lopez  ---
I wasn't able to reproduce the same behavior in 

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
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

or

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
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

Attempting to reproduce the bug results in a PNG file that is corrupted.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160511] "box around character" uses too much padding above (matter of taste)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160511

m_a_riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #3 from m_a_riosv  ---
Please attach a sample file, reduce the size as much as possible without
private information, and paste the information in Menu/Help/About LibreOffice,
there is a copy icon.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160486] Visual corruption when using display scaling of 125%

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160486

--- Comment #3 from Armondo Lopez  ---
I was unable to reproduce the bug in

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
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

or

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
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.

[Bug 160510] When pasting text styled with character format to a new document that style isn't edit-able

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160510

m_a_riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #2 from m_a_riosv  ---
Works for me with
Version: 7.5.9.2 (X86_64) / LibreOffice Community
Build ID: cdeefe45c17511d326101eed8008ac4092f278a9
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: es-ES
Calc: CL threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160491] In Calc "text to columns" produces two rows out of one row of data

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160491

Armondo Lopez  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

--- Comment #3 from Armondo Lopez  ---
Thank you for reporting the bug. Please attach a sample document, as this makes
it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'.
Please change it back to 'UNCONFIRMED' once the requested document is provided. 

(Note that the attachment will be public. Please remove any sensitive
information before attaching it. See

for further detail.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160508] The overall interface is very very slow on Windows 11

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160508

m_a_riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m_a_riosv  ---
Have you tested with Skia enable.
Menu/Tools/Options/LibreOffice/View

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 154525] [sample] Calc is extremely slow (3+ minutes) to open Lenovo's Accessories "Options Compatibility Matrix" spreadsheet

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154525

--- Comment #24 from Armondo Lopez  ---
I don't experience any extensive period of load time in 

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
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

or

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
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.

[Bug 158056] Connect to MS Access *.mdb files by mean of Microsoft.ACE.OLEDB.12.0 provider

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158056

--- Comment #6 from jcs...@libreoffice.org ---
Comment on attachment 193471
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193471
Test database format .accdb

Test database in Access 2007 format

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158056] Connect to MS Access *.mdb files by mean of Microsoft.ACE.OLEDB.12.0 provider

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158056

--- Comment #5 from jcs...@libreoffice.org ---
Created attachment 193471
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193471=edit
Test database format .accdb

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160512] New: CRASH Writer Hangs completely when copying complete file, even small file

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160512

Bug ID: 160512
   Summary: CRASH Writer Hangs completely when copying complete
file, even small file
   Product: LibreOffice
   Version: 24.2.2.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: f.zwit...@upcmail.nl

Created attachment 193470
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193470=edit
This small file makes writer hang every time when copied completely

Short description:

1) Open attached file
2) Copy complete file with ^A ^C
   (or: select all by dragging, followed by ^C, makes no difference)
3) writer stops responding.
4) After a few seconds the OS suggests to kill writer, because it doesn't
respond.
5) kill writer
6) Sometimes I can restart writer, but sometimes I have to restart the system.

Additional info:

This started happening after last update of LibreOffice.

System:
   KDE neon 6.0
   KDE Plasma 6.0.3
   KDE Frameworks 6.0.0
   Qt version 6.6.3
   Kernel 6.5.0-26-generic (64-bits)
   Graphic platform X11

It only happens in writer, so I guess it's not something with memory or Xpad
(the memory app I use).

If I start writer in safe-mode it happens too.

If I start writer in the konsole, there's no error message at all. The starting
command 'libreoffice --writer' just stays on the screen. (Normally you get some
error message in the konsole, when something goes wrong.)

In the attached file it happens always. If I only copy part of that file, it
happens sometimes. Couldn't find any pattern in it.

Package source: https://ppa.launchpadcontent.net/libreoffice/ppa/ubuntu/
Installed version: 4:24.2.2~rc2-0ubuntu0.22.04.1~lo1
 (Actually no idea what the installed version means. Help

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 144552] Right click then format on a cell could be a little faster?

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144552

--- Comment #7 from Armondo Lopez  ---
It doesn't seem slow when attempting to reproduce in

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
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

or

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
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.

[Bug 143381] Calc hangs if properties panel is resized

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143381

--- Comment #9 from Armondo Lopez  ---
I am unable to reproduce this bug in

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
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

or

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
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.

[Bug 160249] Support marking text as having an arbitrary language

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160249

--- Comment #6 from Eyal Rozenberg  ---
(In reply to Eyal Rozenberg from comment #4)

Sorry, I messed up that reply by confusing arbitrary and undetermined. Let me
take that back and reply again.

(In reply to Stéphane Guillou (stragu) from comment #2)
> Seems to me like very niche use case.

It is a somewhat a niche case, but then - there quite a lot of highly-obscure,
probably-not-spoken languages that we support. I mean, this would have wildly
more usage than runic ancient Hungraian...

> We already have "no language"

Do we have "no language"? Where?

And - it's important to have "arbitrary"; but I agree it's not as important as
having "no language" or "undetermined language".

> It's not a label that you assign to some text 

Why not? And remember, we're mostly focused on a post-151920 situation.

> Ultimately there is no use case that you solve.

Like with any language code, the use case is telling the app/the reader what is
known and not known about the language of a piece of text. That's both a use
case for automated tools and for manual editing.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 141047] FORMATTING: Calc render 11 pt Calibri font as 10,5 pt when cell contains NBSP at 90% zoom

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141047

--- Comment #10 from Armondo Lopez  ---
I was unable to reproduce the bug in

Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac
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

or

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb
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.

[Bug 160256] Support marking text as having an undetermined language (ISO 639-2 "und" code)

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=160256

--- Comment #4 from Eyal Rozenberg  ---
(In reply to Eike Rathke from comment #3)

Interesting... that's better than what I knew was implemented right now.

Regardless of that point,

* This suggestion would only be relevant before bug 151290 (after which,
language is no longer an aspect of formatting).
* There are 3 language boxes: Western, Complex, Asian. Why should the user do
this in the Western language selection box? And - should be any of them? all of
them?
* There's no list item to choose this with the mouse
* There's no completion for it
* ...and it's easy to mistake with Udmurt, which does have completion

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 158056] Connect to MS Access *.mdb files by mean of Microsoft.ACE.OLEDB.12.0 provider

2024-04-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=158056

jcs...@libreoffice.org changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

-- 
You are receiving this mail because:
You are the assignee for the bug.

  1   2   3   4   >