[Libreoffice-bugs] [Bug 133092] [META] Crash bugs

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=133092
Bug 133092 depends on bug 155017, which changed state.

Bug 155017 Summary: Crash when closing an HTML in a debug build
https://bugs.documentfoundation.org/show_bug.cgi?id=155017

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

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

[Libreoffice-commits] core.git: sfx2/source

[Mike Kaganski (via logerrit)]

 sfx2/source/control/dispatch.cxx |   20 
 1 file changed, 16 insertions(+), 4 deletions(-)

New commits:
commit 271f17a6022c64cbbe9befbc66a9eaaa0567d569
Author: Mike Kaganski 
AuthorDate: Tue Apr 25 20:58:30 2023 +0300
Commit: Mike Kaganski 
CommitDate: Wed Apr 26 06:40:50 2023 +0200

tdf#155017: make sure that the correct shell is popped from SfxDispatcher

Honestly, I don't quite understand the idea of using the stack of shells
in SfxDispatcher, when the order of addition of shells there does not
match the order of removal.

After opening the bugdoc, SfxDispatcher has these shells in xImp->aStack
(from top to bottom):

  [8] SwWebView
  [7] SwWebTableShell
  [6] SwWebTextShell
  [5] SwWebListShell
  [4] FmFormShell
  [3] SwWebDocShell
  [2] SfxViewFrame
  [1] SwModule
  [0] SfxApplication

SfxViewFrame dtor calls ReleaseObjectShell_Impl.
 * First of all, it calls PopShellAndSubShells_Impl for SfxViewShell;
 * Then it calls SfxDispatcher::Pop for SfxObjectShell;
 * Then it calls SfxDispatcher::RemoveShell_Impl for SfxModule;
 * Then SfxObjectShell is destroyed;
 * And finally, SfxDispatcher::SetDisableFlags is called.

PopShellAndSubShells_Impl (for SfxViewShell) finds the passed SwWebView
at the top of the stack (pos. 8), and removes it.

SfxDispatcher::Pop for SfxObjectShell queues removal of the passed
SwWebDocShell *without* SfxDispatcherPopFlags::POP_UNTIL mode.

SfxDispatcher::RemoveShell_Impl first calls Flush, which actually
executes the queued actions. At this point, an SwWebTableShell (pos. 7)
is the top of the stack; SfxDispatcher::FlushImpl will pop it, and stop
(because there was no SfxDispatcherPopFlags::POP_UNTIL at the previous
step), so the intended removal of SwWebDocShell (which is at pos. 3)
will not happen. Then RemoveShell_Impl will proceed searching for the
specific shell (SwModule), and removing specifically that (at pos. 1).

At the moment of destruction of object shell, the dispatcher's stack
looks like this:

  [5] SwWebTextShell
  [4] SwWebListShell
  [3] FmFormShell
  [2] SwWebDocShell <-- The problem is here
  [1] SfxViewFrame
  [0] SfxApplication

and pos.2 points to a destructed object.

Finally, SetDisableFlags iterates all the shells still in the stack,
setting their flags - and obviously accessing already destroyed object.
In debug builds, this crashes reliably; in release builds, where dtors
do not fill memory, the access of the just-destroyed objects likely
often goes unnoticed.

In different documents, the order and the set of shells there is
different, e.g. an empty Writer document would have view shell just
above object shell, resulting in correct removal of the object shell.

I don't know what strategy is intended here. I decided to implement a
small change, that makes sure that without POP_UNTIL, popping a shell
removes exactly that shell that was requested for removal.

Change-Id: I670d024056a5b32d5485f00a4799a8b0bacb6485
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151003
Tested-by: Mike Kaganski 
Reviewed-by: Mike Kaganski 

diff --git a/sfx2/source/control/dispatch.cxx b/sfx2/source/control/dispatch.cxx
index b1bb3c7aed27..e78789e56271 100644
--- a/sfx2/source/control/dispatch.cxx
+++ b/sfx2/source/control/dispatch.cxx
@@ -1321,12 +1321,25 @@ void SfxDispatcher::FlushImpl()
 else
 {
 // Actually pop
-SfxShell* pPopped = nullptr;
 bool bFound = false;
-do
+if (!i->bUntil)
+{
+// pop exactly the requested shell
+if (auto it = std::find(xImp->aStack.begin(), 
xImp->aStack.end(), i->pCluster);
+it != xImp->aStack.end())
+{
+xImp->aStack.erase(it);
+i->pCluster->SetDisableFlags(SfxDisableFlags::NONE);
+bFound = true;
+
+// Mark the moved Shell
+aToDoCopy.push_front(SfxToDo_Impl(false, i->bDelete, 
false, *i->pCluster));
+}
+}
+while (!bFound)
 {
 DBG_ASSERT( !xImp->aStack.empty(), "popping from empty stack" 
);
-pPopped = xImp->aStack.back();
+SfxShell* pPopped = xImp->aStack.back();
 xImp->aStack.pop_back();
 pPopped->SetDisableFlags( SfxDisableFlags::NONE );
 bFound = (pPopped == i->pCluster);
@@ -1334,7 +1347,6 @@ void SfxDispatcher::FlushImpl()
 // Mark the moved Shell
 aToDoCopy.push_front(SfxToDo_Impl(false, i->bDelete, false, 
*pPopped));
 }
-while(i->bUntil && !bFound);
 DBG_ASSERT( 

[Libreoffice-bugs] [Bug 113499] [META] AutoFill bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=113499

BogdanB  changed:

   What|Removed |Added

 Depends on||153517


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153517
[Bug 153517] CALC - wrong time value when using the autofill function and
minutes are entered (not for 00 min)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153517] CALC - wrong time value when using the autofill function and minutes are entered (not for 00 min)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153517

BogdanB  changed:

   What|Removed |Added

 Blocks||113499
 CC||buzea.bog...@libreoffice.or
   ||g


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 155019] Strikethroughs don't copy from Calc to Writer

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155019

BogdanB  changed:

   What|Removed |Added

 Blocks||108844
 CC||buzea.bog...@libreoffice.or
   ||g


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 108844] [META] Cut/copy bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108844

BogdanB  changed:

   What|Removed |Added

 Depends on||155019


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=155019
[Bug 155019] Strikethroughs don't copy from Calc to Writer
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 88173] [META] DOCX (OOXML) format limitations

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=88173

BogdanB  changed:

   What|Removed |Added

 Depends on||155010


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=155010
[Bug 155010] LibreOffice writer coredumps when opening malformed docx file
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155010] LibreOffice writer coredumps when opening malformed docx file

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155010

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||88173


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=88173
[Bug 88173] [META] DOCX (OOXML) format limitations
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-commits] core.git: sw/qa sw/source

[Mike Kaganski (via logerrit)]

 sw/qa/extras/htmlimport/data/tdf155011.html |   31 
 sw/qa/extras/htmlimport/htmlimport.cxx  |6 +
 sw/source/core/layout/sectfrm.cxx   |4 +--
 3 files changed, 39 insertions(+), 2 deletions(-)

New commits:
commit 9ca317ff313958706c63b132113d3f706813587d
Author: Mike Kaganski 
AuthorDate: Tue Apr 25 14:08:32 2023 +0300
Commit: Mike Kaganski 
CommitDate: Wed Apr 26 05:58:58 2023 +0200

tdf#155011: Fix assert/check

pFrameStartAfter may be a section frame itself, thus its FindSctFrame
would not return this. Same for pSav.

Change-Id: Ib592965b30eb47f37ba54fe7f39af0b8689b3175
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150981
Tested-by: Jenkins
Reviewed-by: Mike Kaganski 

diff --git a/sw/qa/extras/htmlimport/data/tdf155011.html 
b/sw/qa/extras/htmlimport/data/tdf155011.html
new file mode 100644
index ..b3bc7845b56a
--- /dev/null
+++ b/sw/qa/extras/htmlimport/data/tdf155011.html
@@ -0,0 +1,31 @@
+
+ 
+  
+   
+
+ 
+  
+   
+
+ 
+  
+   
+
+ 
+  
+ 
+
+   
+  
+  
+  
+ 
+
+   
+  
+ 
+
+   
+  
+ 
+
\ No newline at end of file
diff --git a/sw/qa/extras/htmlimport/htmlimport.cxx 
b/sw/qa/extras/htmlimport/htmlimport.cxx
index d39d651560d6..34900529ada9 100644
--- a/sw/qa/extras/htmlimport/htmlimport.cxx
+++ b/sw/qa/extras/htmlimport/htmlimport.cxx
@@ -605,6 +605,12 @@ CPPUNIT_TEST_FIXTURE(HtmlImportTest, testTdf153341)
 CPPUNIT_ASSERT_EQUAL(Color(ColorTransparency, 0xB3, 0xFF, 0x00, 0x00), 
getProperty(xRun3, "CharColor"));
 }
 
+CPPUNIT_TEST_FIXTURE(HtmlImportTest, testTdf155011)
+{
+createSwWebDoc("tdf155011.html");
+// Must not crash / fail asserts
+}
+
 CPPUNIT_PLUGIN_IMPLEMENT();
 
 /* vim:set shiftwidth=4 softtabstop=4 expandtab: */
diff --git a/sw/source/core/layout/sectfrm.cxx 
b/sw/source/core/layout/sectfrm.cxx
index cc6c3982d3a4..0b1ac612bfd9 100644
--- a/sw/source/core/layout/sectfrm.cxx
+++ b/sw/source/core/layout/sectfrm.cxx
@@ -522,9 +522,9 @@ void SwSectionFrame::MergeNext( SwSectionFrame* pNxt )
 |*/
 SwSectionFrame* SwSectionFrame::SplitSect( SwFrame* pFrameStartAfter, SwFrame* 
pFramePutAfter )
 {
-assert(!pFrameStartAfter || pFrameStartAfter->FindSctFrame() == this);
+assert(!pFrameStartAfter || IsAnLower(pFrameStartAfter));
 SwFrame* pSav = pFrameStartAfter ? pFrameStartAfter->FindNext() : 
ContainsAny();
-if (pSav && pSav->FindSctFrame() != this)
+if (pSav && !IsAnLower(pSav))
 pSav = nullptr; // we are at the very end
 
 // Put the content aside

[Libreoffice-bugs] [Bug 154764] LibreOffice opens Apple Numbers documents with formatting but without text in cells

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154764

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 154999] Icon auf der Taskleiste fehlt / Icon on the taskbar is missing

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154999

--- 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 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154978

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 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154978

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

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

[Libreoffice-ux-advise] [Bug 154687] Add a way to reset toolbar button colors to default (see comment 4)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154687

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Libreoffice-bugs] [Bug 154687] Add a way to reset toolbar button colors to default (see comment 4)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154687

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

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

[Libreoffice-ux-advise] [Bug 154687] Add a way to reset toolbar button colors to default (see comment 4)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154687

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

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

[Libreoffice-bugs] [Bug 154687] Add a way to reset toolbar button colors to default (see comment 4)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154687

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

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

[Libreoffice-bugs] [Bug 129223] EDITING: Crash if I copy big amount of data and [Windows]+[V] copy history enabled.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=129223

--- Comment #9 from QA Administrators  ---
Dear jorge.alfe.512,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 108843] [META] Clipboard bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108843
Bug 108843 depends on bug 129223, which changed state.

Bug 129223 Summary: EDITING: Crash if I copy big amount of data and 
[Windows]+[V] copy history enabled.
https://bugs.documentfoundation.org/show_bug.cgi?id=129223

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 133092] [META] Crash bugs

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=133092
Bug 133092 depends on bug 129223, which changed state.

Bug 129223 Summary: EDITING: Crash if I copy big amount of data and 
[Windows]+[V] copy history enabled.
https://bugs.documentfoundation.org/show_bug.cgi?id=129223

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151777] Crash in: .LTHUNK688.lto_priv.20293

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151777

--- Comment #4 from QA Administrators  ---
Dear opensuse.lietuviu.kalba,

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 89065] Text in Fade In animations is not antialiased

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=89065

--- Comment #12 from QA Administrators  ---
Dear Chris King,

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 77752] FILESAVE PPTX Saving a PPT file to PPTX changes font family

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=77752

--- Comment #12 from QA Administrators  ---
Dear Ofir,

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 36419] EDITING: + does not work reliable as expected.

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=36419

--- Comment #19 from QA Administrators  ---
Dear Rainer Bielefeld Retired,

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 141369] Unexpected toolbars are visible in Tabbed NB mode when switching in another app

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=141369

--- Comment #2 from QA Administrators  ---
Dear Aron Budea,

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 141005] Bottom and descent values ignored for vertical writing

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=141005

--- Comment #8 from QA Administrators  ---
Dear Y. Kawara,

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 124419] Memory usage for 4 documents containing a table of 10 columns 1500 cells

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=124419

--- Comment #12 from QA Administrators  ---
Dear Telesto,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 122929] High memory usage & OOM x86 when using find & replace on a specific document

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=122929

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 114708] Error installing extension with a space in the filename; installing in a folder with a space in the name fails too

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=114708

--- Comment #8 from QA Administrators  ---
Dear Mark,

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 106996] Unsaved changes not indicated, if character style upon opening changed from custom one to Default Style

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=106996

--- Comment #6 from QA Administrators  ---
Dear Kruno,

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 153451] LO Input line switched from white to gray (as rest of the toolbar) making it harder to find

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153451

--- Comment #19 from Wojtek  ---
Created attachment 186929
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186929=edit
libre.office.7.6.gray.png

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

[Libreoffice-bugs] [Bug 153451] LO Input line switched from white to gray (as rest of the toolbar) making it harder to find

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153451

--- Comment #18 from Wojtek  ---
Thanks ady.

ad rem - the issue is still there.

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

[Libreoffice-bugs] [Bug 155022] New: Tabbed UI: Reference tab in Writer has a command with the wrong layout

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155022

Bug ID: 155022
   Summary: Tabbed UI: Reference tab in Writer has a command with
the wrong layout
   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: rafael.palma.l...@gmail.com

Created attachment 186928
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186928=edit
Screenshot showing the problem

The Reference tab in Writer (using the Tabbed UI) has the button "Bibliography
Database" in the wrong layout. It should be a large image with text at the
bottom.

See attached image for more details.

System info

Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Ubuntu package version: 4:7.5.2~rc2-0ubuntu0.22.10.1~lo1
Calc: threaded

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

[Libreoffice-bugs] [Bug 146790] Problème avec la fonction NB.SI() COUNTIF()

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=146790

--- Comment #6 from ady  ---
Repro in

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 5cd9de202765e243e41416802f3e4486b8a96f16
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (es_AR); UI: en-US
Calc: CL threaded
Built on 2023-04-21

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

[Libreoffice-bugs] [Bug 146790] Problème avec la fonction NB.SI() COUNTIF()

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=146790

ady  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 151958] The COUNTIF function mis-counts, Recalculate Hard does not work

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151958

ady  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||6790
 CC||er...@redhat.com

--- Comment #9 from ady  ---
(In reply to ady from comment #8)
> Recalculate Hard is failing, not the countif() function itself.

OTOH, bug 146790 is also about COUNTIF() and it fails in a similar way as this
bug 151958, in the same versions for me.

CC'ing Eike.

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

[Libreoffice-bugs] [Bug 155021] New: Tabbed UI: Tools tab layout can be improved

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155021

Bug ID: 155021
   Summary: Tabbed UI: Tools tab layout can be improved
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rafael.palma.l...@gmail.com

Created attachment 186927
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186927=edit
Screenshot showing the problem

When using the Tabbed UI, the Tools tab (available in all apps) does not use
well the space to distribute the tools. There are two main problems:

1) The "Group box" command is alone at the bottom of a stack where 2 tools were
supposed to be placed, but the top slot is empty.

2) The controls are misaligned, leaving empty spaces. For instance, the "Image
Control" could be placed below the "Image Button".

See attached image for more details.

System info

Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Ubuntu package version: 4:7.5.2~rc2-0ubuntu0.22.10.1~lo1
Calc: threaded

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

[Libreoffice-bugs] [Bug 154997] macOS: infinite spinning wheel when saving file

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154997

--- Comment #6 from Bruce  ---
This bug appears to be the same as previously reported in bug reports 128233
and 139679 so this is not a new issue.

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

[Libreoffice-bugs] [Bug 151958] The COUNTIF function mis-counts, Recalculate Hard does not work

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151958

ady  changed:

   What|Removed |Added

Summary|The COUNTIF function|The COUNTIF function
   |mis-counts  |mis-counts, Recalculate
   ||Hard does not work

--- Comment #8 from ady  ---
Recalculate Hard is failing, not the countif() function itself.

This works OK in 7.6.alpha, and also in older 7.4.3.2 (this is not a typo,
despite the current Version field set to a prior version), but fails in current
7.4.6.2.

I have not tested 7.5.

This "must" be resolved for the next 7.4.7 before its release (I can only
hope).

This should be set to "Major".

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

[Libreoffice-bugs] [Bug 153789] Icons needed for new Uno commands WatchWindow and StackWindow in the Basic IDE

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153789

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.6.0

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

[Libreoffice-commits] core.git: icon-themes/karasa_jaga icon-themes/karasa_jaga_svg

[Rizal Muttaqin (via logerrit)]

 icon-themes/karasa_jaga/cmd/32/stackwindow.png |binary
 icon-themes/karasa_jaga/cmd/32/watchwindow.png |binary
 icon-themes/karasa_jaga/cmd/lc_stackwindow.png |binary
 icon-themes/karasa_jaga/cmd/lc_watchwindow.png |binary
 icon-themes/karasa_jaga/cmd/sc_stackwindow.png |binary
 icon-themes/karasa_jaga/cmd/sc_watchwindow.png |binary
 icon-themes/karasa_jaga_svg/cmd/32/stackwindow.svg |1 +
 icon-themes/karasa_jaga_svg/cmd/32/watchwindow.svg |1 +
 icon-themes/karasa_jaga_svg/cmd/lc_stackwindow.svg |1 +
 icon-themes/karasa_jaga_svg/cmd/lc_watchwindow.svg |1 +
 icon-themes/karasa_jaga_svg/cmd/sc_stackwindow.svg |1 +
 icon-themes/karasa_jaga_svg/cmd/sc_watchwindow.svg |1 +
 12 files changed, 6 insertions(+)

New commits:
commit d91dc9ffd57d749946dd6062a3d961fab47ec607
Author: Rizal Muttaqin 
AuthorDate: Wed Apr 26 06:08:12 2023 +0700
Commit: Rizal Muttaqin 
CommitDate: Wed Apr 26 02:11:28 2023 +0200

tdf#153789 KJ: icons for Watched Expressions and Call Stack

Change-Id: I9a989e039ae726e413c0a54ab805a0ee7d09c94e
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151007
Tested-by: Jenkins
Reviewed-by: Rizal Muttaqin 

diff --git a/icon-themes/karasa_jaga/cmd/32/stackwindow.png 
b/icon-themes/karasa_jaga/cmd/32/stackwindow.png
new file mode 100644
index ..59490b7276da
Binary files /dev/null and b/icon-themes/karasa_jaga/cmd/32/stackwindow.png 
differ
diff --git a/icon-themes/karasa_jaga/cmd/32/watchwindow.png 
b/icon-themes/karasa_jaga/cmd/32/watchwindow.png
new file mode 100644
index ..2186dc15a84d
Binary files /dev/null and b/icon-themes/karasa_jaga/cmd/32/watchwindow.png 
differ
diff --git a/icon-themes/karasa_jaga/cmd/lc_stackwindow.png 
b/icon-themes/karasa_jaga/cmd/lc_stackwindow.png
new file mode 100644
index ..9510fa52388c
Binary files /dev/null and b/icon-themes/karasa_jaga/cmd/lc_stackwindow.png 
differ
diff --git a/icon-themes/karasa_jaga/cmd/lc_watchwindow.png 
b/icon-themes/karasa_jaga/cmd/lc_watchwindow.png
new file mode 100644
index ..e578e4bccaa6
Binary files /dev/null and b/icon-themes/karasa_jaga/cmd/lc_watchwindow.png 
differ
diff --git a/icon-themes/karasa_jaga/cmd/sc_stackwindow.png 
b/icon-themes/karasa_jaga/cmd/sc_stackwindow.png
new file mode 100644
index ..802874460201
Binary files /dev/null and b/icon-themes/karasa_jaga/cmd/sc_stackwindow.png 
differ
diff --git a/icon-themes/karasa_jaga/cmd/sc_watchwindow.png 
b/icon-themes/karasa_jaga/cmd/sc_watchwindow.png
new file mode 100644
index ..4d2b6bbccb13
Binary files /dev/null and b/icon-themes/karasa_jaga/cmd/sc_watchwindow.png 
differ
diff --git a/icon-themes/karasa_jaga_svg/cmd/32/stackwindow.svg 
b/icon-themes/karasa_jaga_svg/cmd/32/stackwindow.svg
new file mode 100644
index ..75a1c3feea8a
--- /dev/null
+++ b/icon-themes/karasa_jaga_svg/cmd/32/stackwindow.svg
@@ -0,0 +1 @@
+http://www.w3.org/2000/svg; 
xmlns:xlink="http://www.w3.org/1999/xlink;>
\ No newline at end of file
diff --git a/icon-themes/karasa_jaga_svg/cmd/32/watchwindow.svg 
b/icon-themes/karasa_jaga_svg/cmd/32/watchwindow.svg
new file mode 100644
index ..eb28440880d2
--- /dev/null
+++ b/icon-themes/karasa_jaga_svg/cmd/32/watchwindow.svg
@@ -0,0 +1 @@
+http://www.w3.org/2000/svg; 
xmlns:xlink="http://www.w3.org/1999/xlink;>
\ No newline at end of file
diff --git a/icon-themes/karasa_jaga_svg/cmd/lc_stackwindow.svg 
b/icon-themes/karasa_jaga_svg/cmd/lc_stackwindow.svg
new file mode 100644
index ..22a92164772f
--- /dev/null
+++ b/icon-themes/karasa_jaga_svg/cmd/lc_stackwindow.svg
@@ -0,0 +1 @@
+http://www.w3.org/2000/svg; 
xmlns:xlink="http://www.w3.org/1999/xlink;>
\ No newline at end of file
diff --git a/icon-themes/karasa_jaga_svg/cmd/lc_watchwindow.svg 
b/icon-themes/karasa_jaga_svg/cmd/lc_watchwindow.svg
new file mode 100644
index ..f93258b1cd8e
--- /dev/null
+++ b/icon-themes/karasa_jaga_svg/cmd/lc_watchwindow.svg
@@ -0,0 +1 @@
+http://www.w3.org/2000/svg; 
xmlns:xlink="http://www.w3.org/1999/xlink;>
\ No newline at end of file
diff --git a/icon-themes/karasa_jaga_svg/cmd/sc_stackwindow.svg 
b/icon-themes/karasa_jaga_svg/cmd/sc_stackwindow.svg
new file mode 100644
index ..3cac12337f8d
--- /dev/null
+++ b/icon-themes/karasa_jaga_svg/cmd/sc_stackwindow.svg
@@ -0,0 +1 @@
+http://www.w3.org/2000/svg; 
xmlns:xlink="http://www.w3.org/1999/xlink;>
\ No newline at end of file
diff --git a/icon-themes/karasa_jaga_svg/cmd/sc_watchwindow.svg 
b/icon-themes/karasa_jaga_svg/cmd/sc_watchwindow.svg
new file mode 100644
index ..1973b489ec0b
--- /dev/null
+++ b/icon-themes/karasa_jaga_svg/cmd/sc_watchwindow.svg
@@ -0,0 +1 @@
+http://www.w3.org/2000/svg; 
xmlns:xlink="http://www.w3.org/1999/xlink;>
\ No newline at end of file

[Libreoffice-bugs] [Bug 95520] Sort column by color (Extension?)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=95520

--- Comment #9 from Crusader  ---
As a big LO fan, I am disappointed to see this important issue languishing for
>7 years.  This is a commonly used feature in other spreadsheets - and must be
part of all respected spreadsheets.

I am respectfully requesting developers (I am not a developer) to work on this
issue and bring this feature to LO.  I know of at least one case where lack of
this feature resulted in the loss of a "convert."

LO does have the ability to "FILTER" by font color/background color, but there
is no way to "SORT" by font color/background color.  Given the extensive usage
of the sort function in spreadsheets, implementation of the sort feature will
significantly increase respect for Calc and promote it as a valuable and
respected spreadsheet.

Thanks in advance to everyone working to bring this feature to fruition.

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

[Libreoffice-bugs] [Bug 153451] LO Input line switched from white to gray (as rest of the toolbar) making it harder to find

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=153451

--- Comment #17 from ady  ---
https://wiki.documentfoundation.org/QA/Testing_Daily_Builds#Daily_builds_install_and_run_in_parallel_to_a_normal_release_version

Quote (but it's even better to read the wiki page directly):
"
To run an installed macOS daily build, you either need to open it twice or run
this command against the application in a terminal:

xattr -d com.apple.quarantine /path/to/LibreOfficeDev.app

"

HTH.

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

[Libreoffice-bugs] [Bug 150453] [EDITING] Select all in formula bar only selects partially for URLs

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=150453

--- Comment #10 from ady  ---
(In reply to LeroyG from comment #2)

> Step 4 must be done with mouse, not with keyboard.

The focus on the relevant cell by means of keyboard will show the url
highlighted, whereas the focus by means of mouse will not. This is the reason
for the steps to reproduce the problem are meant with the mouse but not with
the keyboard.

Additionally, by performing the focus by mouse, we can select part of the
content of the cell, whereas focusing on the cell by keyboard we can see the
complete content highlighted and it is not clear how to select only part of it.

I wonder whether this is (at least in part) a UX issue.

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

[Libreoffice-bugs] [Bug 155014] Arrow head varies with same settings

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155014

--- Comment #2 from Don Matschull  ---
Created attachment 186926
  --> https://bugs.documentfoundation.org/attachment.cgi?id=186926=edit
Lines with arrowheads that differ

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

[Libreoffice-bugs] [Bug 90507] Tools - AutoCorrect - Apply converts non-empty "Default Paragraph Style" paragraphs to "Text Body" PS --even when no [M] options are selected

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=90507

Baole Fang  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=12
   ||8192
   Assignee|libreoffice-b...@lists.free |baole.f...@gmail.com
   |desktop.org |
 Status|NEW |ASSIGNED

--- Comment #23 from Baole Fang  ---
Start working on this together with bug 128192. I'll prevent AutoCorrect from
changing the style if it is expected.

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

[Libreoffice-bugs] [Bug 128192] Tools > AutoCorrect > Apply only applies AutoCorrect Options on "Default paragraph style" - but should apply for all paragraph styles

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=128192

Baole Fang  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |baole.f...@gmail.com
   |desktop.org |
 Status|NEW |ASSIGNED

--- Comment #9 from Baole Fang  ---
I've taken a look into this bug, and here is the current AutoCorrect logic for
non default paragraph style:

If the current style is user defined, then AutoCorrect is applied according to
whether "Replace Custom Styles" is checked.

Else, if the style is not default paragraph style, then it is assumed that
everything is well formatted. It will get into HAS_FMTCOLL state, where
BuildText() is not correctly run.

I can fix it by calling BuildText() properly. In the same fix, I'll prevent
AutoCorrect from changing the style to "Text Body" mentioned in bug 90507.

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

[Libreoffice-bugs] [Bug 155020] Cursor is almost invisible

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155020

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #2 from m.a.riosv  ---
And I think cursor, usually it's set up at OS level.

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

[Libreoffice-ux-advise] [Bug 155016] New feature: set the source/scope of AutoComplete search

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155016

m.a.riosv  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO
 CC||miguelangelrv@libreoffice.o
   ||rg
   Severity|normal  |enhancement

--- Comment #1 from m.a.riosv  ---
We already have a lot of options.

Maybe the use of Menu/Data/Validity, could help.

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

[Libreoffice-bugs] [Bug 155016] New feature: set the source/scope of AutoComplete search

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155016

m.a.riosv  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO
 CC||miguelangelrv@libreoffice.o
   ||rg
   Severity|normal  |enhancement

--- Comment #1 from m.a.riosv  ---
We already have a lot of options.

Maybe the use of Menu/Data/Validity, could help.

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

[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154978

--- Comment #4 from agap...@hotmail.com ---
(In reply to Julien Nabet from comment #2)
> What's your LO version?
> Could you check you use recent LO version, 7.4.6 or even brand new 7.5.2?
> Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps to
> exclude things like corrupted LO profile.
> 
> Then how do you use Languagetool? I mean, until recently Languagetool was an
> extension to install on LO, now it's an api to call from
> Tools/Options/Language Settings/LanguageTool Server
> and here you must check "Enable LanguageTool" option then put the Base URL.
> By default the free one (because there's also premium one), it's
> https://api.languagetool.org/v2.
> 
> Finally, would it be possible you attach a backtrace by following
> https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU/Linux:
> _How_to_get_a_backtrace ?

>LO version:

Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-US (en_US.UTf-8); UI: en-US
7.5.2-1
Calc: threaded

> Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps to
> exclude things like corrupted LO profile.

I have tried deleting the profile in /home//.config/libreoffice/4/user/
The moment I reinstall LanguageTool the issue appears again.


>Then how do you use Languagetool? I mean, until recently Languagetool was an
> extension to install on LO, now it's an api to call from

I use it as an extension from the official site. I have also tried the latest
SNAPSHOT versions as well from https://internal1.languagetool.org/snapshots/

>> extension to install on LO, now it's an api to call from
> Tools/Options/Language Settings/LanguageTool Server
> and here you must check "Enable LanguageTool" option then put the Base URL.
> By default the free one (because there's also premium one), it's
> https://api.languagetool.org/v2.

I have the Server also enabled and the issue persists


>Finally, would it be possible you attach a backtrace by following 

Here is the backtrace

warning: Currently logging to gdbtrace.log.  Turn the logging off and on to
make the new setting effective.
Downloading separate debug info for /lib64/ld-linux-x86-64.so.2...
Downloading separate debug info for system-supplied DSO at 0x77fc8000...
Downloading separate debug info for
/usr/lib/libreoffice/program/libuno_sal.so.3...
Downloading separate debug info for
/usr/lib/libreoffice/program/libsofficeapp.so...
Downloading separate debug info for /usr/lib/libc.so.6...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Downloading separate debug info for /usr/lib/libz.so.1...
Downloading separate debug info for /usr/lib/libm.so.6...
Downloading separate debug info for /usr/lib/libdbus-1.so.3...
Downloading separate debug info for /usr/lib/libicuuc.so.72...
Downloading separate debug info for
/usr/lib/libreoffice/program/libclewlo.so...
Downloading separate debug info for
/usr/lib/libreoffice/program/libcomphelper.so...
Downloading separate debug info for
/usr/lib/libreoffice/program/libuno_cppu.so.3...
Downloading separate debug info for
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3...
Downloading separate debug info for
/usr/lib/libreoffice/program/libdeploymentmisclo.so...
Downloading separate debug info for
/usr/lib/libreoffice/program/libeditenglo.so...
Downloading separate debug info for /usr/lib/libreoffice/program/libfwklo.so...
Downloading separate debug info for
/usr/lib/libreoffice/program/libi18nlangtag.so...
Downloading separate debug info for
/usr/lib/libreoffice/program/libopencllo.so...
Downloading separate debug info for
/usr/lib/libreoffice/program/libuno_salhelpergcc3.so.3...
Downloading separate debug info for /usr/lib/libreoffice/program/libsblo.so...
Downloading separate debug info for /usr/lib/libreoffice/program/libsfxlo.so...
Downloading separate debug info for /usr/lib/libreoffice/program/libsvllo.so...
Downloading separate debug info for /usr/lib/libreoffice/program/libsvxlo.so...
Downloading separate debug info for
/usr/lib/libreoffice/program/libsvxcorelo.so...
Downloading separate debug info for /usr/lib/libreoffice/program/libsvtlo.so...
Downloading separate debug info for /usr/lib/libreoffice/program/libtklo.so...
Downloading separate debug info for /usr/lib/libreoffice/program/libtllo.so...
Downloading separate debug info for
/usr/lib/libreoffice/program/libucbhelper.so...
Downloading separate debug info for /usr/lib/libreoffice/program/libutllo.so...
Downloading separate debug info for /usr/lib/libreoffice/program/libvcllo.so...
Downloading separate debug info for /usr/lib/libsystemd.so.0...
Downloading separate debug info for /usr/lib/libicudata.so.72...
Downloading separate debug info for /usr/lib/libgpgmepp.so.6...
Downloading separate debug info for /usr/lib/libnss3.so...
Downloading separate 

[Libreoffice-bugs] [Bug 86630] MENU: Easily insert page number into header/footer with extended menu Insert

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=86630

--- Comment #31 from Commit Notification 
 ---
Justin Luth committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/bc6c5356c5cfa5c09145b54b87ad7be4d8f40ca2

tdf#86630 sw page number wizard: default to center of page

It will be available in 7.6.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

[Libreoffice-ux-advise] [Bug 155007] FILESAVE XLS Excessive number of rows or columns warning

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155007

ady  changed:

   What|Removed |Added

 CC|libreoffice-ux-advise@lists |
   |.freedesktop.org|

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

[Libreoffice-commits] core.git: sw/source

[Justin Luth (via logerrit)]

 sw/source/ui/misc/pagenumberdlg.cxx |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

New commits:
commit bc6c5356c5cfa5c09145b54b87ad7be4d8f40ca2
Author: Justin Luth 
AuthorDate: Tue Apr 25 12:58:29 2023 -0400
Commit: Justin Luth 
CommitDate: Wed Apr 26 00:43:01 2023 +0200

tdf#86630 sw page number wizard: default to center of page

Defaulting to one side of the page only makes sense
if the footer is mirrored.
[Well, mirrored isn't the best word here
because it only refers to margin spacing.]

The only way to get mirrored footers is to have
separate left and right pages.

It would be nice to add mirroring to the wizard,
but that can be done separately.

First, lets just get a better default value in place.

Change-Id: I314c6a34414a696c6f2e27bb2b0747fdb86f3b22
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150998
Tested-by: Jenkins
Reviewed-by: Justin Luth 
Reviewed-by: Paris Oplopoios 

diff --git a/sw/source/ui/misc/pagenumberdlg.cxx 
b/sw/source/ui/misc/pagenumberdlg.cxx
index 19402d5a69a7..ed889a277852 100644
--- a/sw/source/ui/misc/pagenumberdlg.cxx
+++ b/sw/source/ui/misc/pagenumberdlg.cxx
@@ -30,8 +30,8 @@ SwPageNumberDlg::SwPageNumberDlg(weld::Window* pParent)
 , m_xPageNumberPosition(m_xBuilder->weld_combo_box("positionCombo"))
 , m_xPageNumberAlignment(m_xBuilder->weld_combo_box("alignmentCombo"))
 , m_xPreviewImage(m_xBuilder->weld_image("previewImage"))
-, m_aPageNumberPosition(1)
-, m_aPageNumberAlignment(0)
+, m_aPageNumberPosition(1) // bottom
+, m_aPageNumberAlignment(1) // center
 {
 m_xOk->connect_clicked(LINK(this, SwPageNumberDlg, OkHdl));
 m_xPageNumberPosition->connect_changed(LINK(this, SwPageNumberDlg, 
PositionSelectHdl));

[Libreoffice-bugs] [Bug 155015] Impress shows window title bar in display mode (not true full screen)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155015

m.a.riosv  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||miguelangelrv@libreoffice.o
   ||rg
 Status|UNCONFIRMED |NEEDINFO

--- Comment #1 from m.a.riosv  ---
I can't repro with
Version: 7.5.3.1 (X86_64) / LibreOffice Community
Build ID: d29ee673721b12c92b3de9b9663473211414f0db
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded

Please what Menu/View/Toolbars do you have enabled.

Test with a clean profile, Menu/Help/Restart in Safe Mode

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

[Libreoffice-bugs] [Bug 154998] CALC: print selected cells

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154998

--- Comment #4 from Gianfranco L'Abbate  ---
Other info on this issue:
1) the bug is not present in the previous version (I don't remind what version
is, sorry) on Windows I use at work, and the firs cell is the same of actual, a
merged cell.
2) This bug is not present in the Linux version 7.3.7.2 i have on my pc home
(with Kubuntu 22.04)

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

[Libreoffice-bugs] [Bug 154997] macOS: infinite spinning wheel when saving file

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154997

Bruce  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #5 from Bruce  ---
I have updated the Mac to OS Ventura 3.3.1 and the bug still exists in exactly
the same form.

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

[Libreoffice-bugs] [Bug 155014] Arrow head varies with same settings

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155014

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #1 from m.a.riosv  ---
Please attach a sample file.

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

[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154978

--- Comment #3 from agap...@hotmail.com ---
(In reply to Robert Großkopf from comment #1)
> Do you close the whole LO or is there anything opened of LO and crashes?
> 
> I'm also using KDE (OpenSuSE 15.4). For some apps it will report every time
> a crash when closing this apps through the special closing cross of the
> window. But I have only closed the app …

In the github thread I linked in the OP, there is a screen capture posted of
what happens when closing LO Writer. 

But yes, I usually get a crash when clicking on the X "close window" button in
the titlebar

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

[Libreoffice-bugs] [Bug 154428] FILESAVE Shapes vanish from a Writer Frame after grouping and anchoring operation (gtk3 and kf5)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154428

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #8 from Stéphane Guillou (stragu) 
 ---
Repro in 7.5.3.1, verified as fixed in:

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

Thank you all!

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

[Libreoffice-bugs] [Bug 154827] Regression in 7.5.x: Graphics anchored in Writer as character become anchored at paragraph when reopening the document

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154827

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #12 from Stéphane Guillou (stragu) 
 ---
Fix verified in:

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

Thank you all!

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

[Libreoffice-bugs] [Bug 128192] Tools > AutoCorrect > Apply only applies AutoCorrect Options on "Default paragraph style" - but should apply for all paragraph styles

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=128192

Baole Fang  changed:

   What|Removed |Added

 CC||baole.f...@gmail.com

--- Comment #8 from Baole Fang  ---
*** Bug 155018 has been marked as a duplicate of this bug. ***

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

[Libreoffice-bugs] [Bug 155018] Manual auto correct failure in Writer

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155018

Baole Fang  changed:

   What|Removed |Added

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

--- Comment #4 from Baole Fang  ---


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

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

[Libreoffice-bugs] [Bug 155018] Manual auto correct failure in Writer

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155018

--- Comment #3 from Baole Fang  ---
Thank you for your comment.

It is indeed true that this bug happens because the style becomes "Text Body"
instead of "Default Paragraph Style", so this bug should be a duplicate of bug
128192.

It is also true that the logic behind Tools/AutoCorrect/Apply is complicated,
and I'm happy to work on it in bug 128192. But it will take some time :(

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

[Libreoffice-bugs] [Bug 137542] SIGSEGV on tab cycling focus to input field in a table cell

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=137542

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
Crash report or||["SwFieldInputDlg::SwFieldI
crash signature||nputDlg(weld::Widget*,
   ||SwWrtShell&, SwField*,
   ||bool, bool)"]
 Status|RESOLVED|VERIFIED

--- Comment #12 from Stéphane Guillou (stragu) 
 ---
Crash reproduced in 7.3.7.2, report in
https://crashreport.libreoffice.org/stats/crash_details/7a386ea6-7d3a-4cd9-b0a9-4f01661ce1bb
Fix verified in:

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

Could not crash when navigating with tab.

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

[Libreoffice-bugs] [Bug 155020] Cursor is almost invisible

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155020

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Hi there
Please provide more information to help us test and troubleshoot:
- Information from Help > About LibreOffice
- Operating System
- Screen resolution and any scaling factor applied
- A screenshot so we can compare to what we see

We have bug 101379 already, maybe that matches your description?

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

[Libreoffice-bugs] [Bug 133092] [META] Crash bugs

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=133092

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||155017


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=155017
[Bug 155017] Crash when closing an HTML in a debug build
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-ux-advise] [Bug 155007] FILESAVE XLS Excessive number of rows or columns warning

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155007

Telesto  changed:

   What|Removed |Added

 CC||tele...@surfxs.nl
   Keywords|needsUXEval |

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

[Libreoffice-bugs] [Bug 155007] FILESAVE XLS Excessive number of rows or columns warning

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155007

Telesto  changed:

   What|Removed |Added

 CC||tele...@surfxs.nl
   Keywords|needsUXEval |

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

[Libreoffice-ux-advise] [Bug 155007] FILESAVE XLS Excessive number of rows or columns warning

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155007

Telesto  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
   Keywords||needsUXEval

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

[Libreoffice-bugs] [Bug 155007] FILESAVE XLS Excessive number of rows or columns warning

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155007

Telesto  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
   Keywords||needsUXEval

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

[Libreoffice-bugs] [Bug 155016] New feature: set the source/scope of AutoComplete search

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155016

Telesto  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||tele...@surfxs.nl

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

[Libreoffice-ux-advise] [Bug 155016] New feature: set the source/scope of AutoComplete search

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155016

Telesto  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||tele...@surfxs.nl

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

[Libreoffice-bugs] [Bug 155018] Manual auto correct failure in Writer

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155018

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
Thanks Baole.

I think this is already covered by bug 90507 and bug 128192:
applying the autocorrect rule changes the style from Default Paragraph Style to
Text Body, and because autocorrect doesn't ever (?)[1] apply to other paragraph
styles, it does not work on subsequent strings.
Wondering if you can decide on which bug this is a duplicate of, and maybe
continue the conversation there?
It would be wonderful if you could work on some patches on this issues, as many
reports are linked to this limitation:
https://bugs.documentfoundation.org/showdependencytree.cgi?id=103341_resolved=1

[1] question mark because I am still unsure of the intricacies of how
autocorrect and styles interact.

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

[Libreoffice-bugs] [Bug 155010] LibreOffice writer coredumps when opening malformed docx file

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155010

Telesto  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 155010] LibreOffice writer coredumps when opening malformed docx file

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155010

Telesto  changed:

   What|Removed |Added

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

--- Comment #1 from Telesto  ---
Confirm
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 066b23115c2a360507e306a88da572554daefab7
CPU threads: 8; OS: Mac OS X 12.6.3; UI render: Skia/Raster; VCL: osx
Locale: nl-NL (nl_NL.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 155020] New: Cursor is almost invisible

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155020

Bug ID: 155020
   Summary: Cursor is almost invisible
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: leocdo...@comcast.net

Description:
Cursor is almost invisible in document

Actual Results:
Cursor not wide enought to been seen readily

Expected Results:
Cursor should be made thicker.


Reproducible: Always


User Profile Reset: No

Additional Info:
Can't you just change one of the bits in the byte that control the appearance
of the cursor?

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

[Libreoffice-bugs] [Bug 154997] macOS: infinite spinning wheel when saving file

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154997

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
Bruce, any chance you could update macOS to the latest version of Ventura and
see if the issue persists?

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

[Libreoffice-bugs] [Bug 155019] Strikethroughs don't copy from Calc to Writer

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155019

Eike Rathke  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 OS|Windows (All)   |All
Version|7.4.6.2 release |Inherited From OOo
 Ever confirmed|0   |1

--- Comment #1 from Eike Rathke  ---
Clarification: this when copying more than one entire cells; copying
strikethrough-attributed content from within cells and a single cell and
pasting to Writer (without cell border) works.

Cells are pasted using the clipboard's RTF (Rich Text Format) text/rtf target.
For two cells with the first having content CellContent and strikethrough that
results in (xclip -selection clipboard -o -target text/rtf)

{\rtf\ansi
{
\trowd\trgaph30\trleft-30\trrh256\clvertalb\cellx1280\clvertalb\cellx2560\pard\plain\intbl
\ql CellContent\cell\ql \cell\row
}
}

Using bold text attribute that is copied along:

{\rtf\ansi
{
\trowd\trgaph30\trleft-30\trrh256\clvertalb\cellx1280\clvertalb\cellx2560\pard\plain\intbl
\ql\b CellContent\cell\plain\ql \cell\row
}
}

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

[Libreoffice-bugs] [Bug 108253] [META] Calc cell formula bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108253
Bug 108253 depends on bug 41304, which changed state.

Bug 41304 Summary: EDITING: Cell formula shown without colors, colored frames 
missing around referenced cells (see comment 17)
https://bugs.documentfoundation.org/show_bug.cgi?id=41304

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

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

[Libreoffice-bugs] [Bug 108917] [META] Cell references bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108917
Bug 108917 depends on bug 41304, which changed state.

Bug 41304 Summary: EDITING: Cell formula shown without colors, colored frames 
missing around referenced cells (see comment 17)
https://bugs.documentfoundation.org/show_bug.cgi?id=41304

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

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

[Libreoffice-bugs] [Bug 41304] EDITING: Cell formula shown without colors, colored frames missing around referenced cells (see comment 17)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=41304

Eike Rathke  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

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

[Libreoffice-bugs] [Bug 154745] Basic Dialogs: Runtime Appearance differs from Editor (spin buttons, dropdown list) on Linux

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=154745

Buovjaga  changed:

   What|Removed |Added

Summary|Basic Dialogues: Runtime|Basic Dialogs: Runtime
   |Appearance differs from |Appearance differs from
   |Editor (spin buttons,   |Editor (spin buttons,
   |dropdown list) on Linux |dropdown list) on Linux

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

[Libreoffice-bugs] [Bug 41304] EDITING: Cell formula shown without colors, colored frames missing around referenced cells (see comment 17)

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=41304

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.6.0

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

Re: A search engine of libreoffice code would be useful.

[Ilmari Lauhakangas]

On 25.4.2023 16.22, nicholas ferguson wrote:

Hi,
I did a project over six years ago, writing C++ code on a Windows platform
to access libreoffice calc spreadsheets.  This code extracted, indexed and
catalogued info on entries in very complex spreadsheets.

These spreadsheets had embedded Reuters market data macros.  Market data
macros had 'Rt' in front of their names.  This clashed with 'RT' in
libreoffice code that also used 'RT' as a prefix. Reuters Ex:
RtGet("IDN","EURO=","BID)

New releases of Reuters API no longer use that 'Rt' prefix.

A fully functioning search engine of Libreoffice code would have helped.
Yes of course, I grepped.


The search engine is OpenGrok: https://opengrok.libreoffice.org/

Ilmari

[Libreoffice-commits] core.git: sc/source

[Eike Rathke (via logerrit)]

 sc/source/ui/app/inputhdl.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 2ff1830207d69ddd8aa6637e8ccc586ecabf1567
Author: Eike Rathke 
AuthorDate: Tue Apr 25 19:46:45 2023 +0200
Commit: Eike Rathke 
CommitDate: Tue Apr 25 22:08:07 2023 +0200

Resolves: tdf#41304 Add percent operator % to reference delimiters

Change-Id: I094fcb800a29de424db28e1b58f1239381a3b4a3
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151001
Reviewed-by: Eike Rathke 
Tested-by: Jenkins

diff --git a/sc/source/ui/app/inputhdl.cxx b/sc/source/ui/app/inputhdl.cxx
index 00fc7e429eb4..d60b10378ffa 100644
--- a/sc/source/ui/app/inputhdl.cxx
+++ b/sc/source/ui/app/inputhdl.cxx
@@ -364,7 +364,7 @@ void ScInputHandler::InitRangeFinder( const OUString& 
rFormula )
 ScDocument& rDoc = pDocSh->GetDocument();
 const sal_Unicode cSheetSep = rDoc.GetSheetSeparator();
 
-OUString aDelimiters = ScEditUtil::ModifyDelimiters(" !~\"\t\n");
+OUString aDelimiters = ScEditUtil::ModifyDelimiters(" !~%\"\t\n");
 // delimiters (in addition to ScEditUtil): only characters that are
 // allowed in formulas next to references and the quotation mark (so
 // string constants can be skipped)

Re: written in german: Want to use Libre office to draw Diagrams (UML, Function Blocks) with semantic content, but I am frustrated about details

[Ilmari Lauhakangas]

On 25.4.2023 19.01, 9...@vishia.de wrote:

Hello

I have checked in the last year the possibility of using libre office 
for technical diagrams, the XML format (odg) is understanable, good 
readable and seems to be also stable. I have read out and convert some 
informations (Java programming), its proper. As base for semanitc 
content I have used style sheets in draw. Then, in the last year, I have 
written an article in german language: 
https://www.embedded-software-engineering.de/low-code-oder-no-code-in-der-anwenderprogrammierung-a-67f62846379fecb2dadf22e568c9ecdc/   but after them I havn't more time, have done other stuff.


Now, because the topic is currently, I have start with some more 
experience. But, really less details (have used the version 7.5.2.2 but 
also 6.4.x, same) makes the live very hard to stay :-((


One Detail: I have small connection points with a proper graphic, the 
connection points have the size 0.15 * 0.3 cm. It is large enough to 
select with the mouse to drag. The size is fixed. But, if I select it, 
suddenly the ... sorry should write in german furthermore, less time


If you don't have time to write in English, then write to some German 
mailing list. Besides, it seems you are making requests about something, 
which is not what this list is about. Rather create reports for those 
and in English: https://wiki.documentfoundation.org/QA/BugReport


Ilmari

A search engine of libreoffice code would be useful.

[nicholas ferguson]

Hi,
I did a project over six years ago, writing C++ code on a Windows platform
to access libreoffice calc spreadsheets.  This code extracted, indexed and
catalogued info on entries in very complex spreadsheets.

These spreadsheets had embedded Reuters market data macros.  Market data
macros had 'Rt' in front of their names.  This clashed with 'RT' in
libreoffice code that also used 'RT' as a prefix. Reuters Ex:
RtGet("IDN","EURO=","BID)

New releases of Reuters API no longer use that 'Rt' prefix.

A fully functioning search engine of Libreoffice code would have helped.
Yes of course, I grepped.

Of course I signed all kinds of non disclosures on that project.

Regards

Nicholas

Add: written in german: Want to use Libre office to draw Diagrams (UML, Function Blocks) with semantic content, but I am frustrated about details

[9876]

Hello
mir ist noch ein wichtiger Gedanke gekommen. Es ist natürlich vollkommen richtig, dass Libre Office die dragpunkte zur Größenveränderung anzeigt, und dann aber mit einem Symbol anzeigt, dass das in diesem konkreten Fall nicht geht. Das ist ein wichtiges Usability-Prinzip, alle Funktionen immer anzubieten und auszugrauen bzw. klar anzuzeigen dass sie hier nicht gehen, anstatt einfach was nicht anzeigen. Man versetze sich in denjenigen, der nicht daran denkt oder nicht weiß, das die Size eben grad mal gefreezed ist, und sich ärgert warum die Größenänderung nicht angeboten wird.
Die Lösung für das moven kleiner (size-freezed) Objekte kann also nicht sein, das sizen nicht anzuzeigen. Eine brauchbare allgemein verwendbare Lösung ist, die dragpunkte zum sizen nicht symmetrisch auf die kanten zu legen sondern etwas außerhalb. Intuitiv will man ja auch von leicht außen an das Objekt heran. Dann ergibt sich von selbst, dass auch bei kleinen Objekten in der Mitte ein genügend großer Bereich zum moven verbleibt. Diese allgemeine Lösung benötigt nur die Änderung von ein paar Zahlen im Program. Kein if().

Eine zweite Möglichkeit wäre auch die dragpunkte in ihrer Größe einstellbar zu haben. Aber das ist nix für den ottonormalbediener, denn er findet die Einstellung nicht und ärgert sich dass er das Objekt bzw. die Punkte nicht trifft mit seiner Grobmaus. das muss man halt auch beachten.
mfG Hartmut best regards from Hartmut
9...@vishia.de schrieb am 25.04.2023 12:01 (GMT -04:00):

Hello
I have checked in the last year the possibility of using libre office for technical diagrams, the XML format (odg) is understanable, good readable and seems to be also stable. I have read out and convert some informations (Java programming), its proper. As base for semanitc content I have used style sheets in draw. Then, in the last year, I have written an article in german language: https://www.embedded-software-engineering.de/low-code-oder-no-code-in-der-anwenderprogrammierung-a-67f62846379fecb2dadf22e568c9ecdc/  but after them I havn't more time, have done other stuff.
Now, because the topic is currently, I have start with some more experience. But, really less details (have used the version 7.5.2.2 but also 6.4.x, same) makes the live very hard to stay :-((
One Detail: I have small connection points with a proper graphic, the connection points have the size 0.15 * 0.3 cm. It is large enough to select with the mouse to drag. The size is fixed. But, if I select it, suddenly the ... sorry should write in german furthermore, less time
 ... die Ziehpunkte für die Größe des Objekts werden angezeigt. Obwohl die Größe fix ist, vollkommen unnötig. Weil dann die Mouseposition offensichtlich innerhalb des fangbreiches dieser Größe-Ziehpunkte liegt, wird ein "verboten"-Symbol angezeigt (weil die Größe ja nicht änderbar ist), und ich kann das Objekt auch nicht mehr moven. Ab einer Größe von ca. 0.2 * 0.2 cm ist genug Platz, um in der Mitte einen Punkt zum moven zu finden aber bei 0.15 mm ist es zu klein. Die kleine Größe brauche ich aber, weil auf einem Diagramm ja auch was darzustellen sein soll, die Größe von 1.5 mm ist locker zu bearbeiten in "Seitenbreite" Auflösung eines 1920-Monitors, da ist also gar nix dagegen zu haben. Aber die "verboten" Ziehpunkte für die Größe drängeln sich vor, ohne benötigt zu werden, und nix geht. 
Vorher habe ich schon einiges probiert. Eine gute Idee war auch ein Textbox, in der der Name des Konnektors steht, diese ist durchsichtig, weil nur der Text sichtbar sein soll. Der ist dann mit dem notwendigen Symbol (filled or non filled diamond etc. wie in UML üblich) als Group verbunden - funktioniert super. Nur: Wenn ich das notwendige Stylesheet dem gesamten Objekt zuweise (weil ich das auch in der Anzeige sehen will) dann setzt sich die indirekte Formatiierung über die direkt vorgegebene (Raute oder Diamond muss eine Linienbreite haben, das Textfeld nicht...) und die Route wird unsichtbar, oder das Textfeld hat eine unwerwünschte Linie, je nachdem ich das Stylesheet einrichte. Diese Idee hatte ich dann aufgegeben, weil ich festgestellt habe, dass ein zugehöriger Text zu einem Objekt (der Raute als ConnectionPoint) auch so einstellbar ist, dass er links daneben erscheint. Super geht juchhe. Und dann dieses Sache mit der nicht-movebarkeit, siehe oberen Absatz.
In der Draw-Software dürfte die Korrektur der Movebarkeit fast ziemlich einfach sein, weil man nur ein if() braucht um bei gesperrter size diese unnötigen Größeziehpunkte erst gar nicht anzuzeigen. Der Rest wird dann so wie gehabt gehen. Doch ich weiß wie es mit den RFCs läuft. Sie werden einsortiert, nach priorität sortiert, und dann (zumindestens bei den kommerziellen Tools) wird das realisiert was der dümmste aber meist zahlende Kunde will. Bei den nichtkommerziellen Tools ist es ggf. nicht der zahlende, sondern der Mengenmößig überlegene, also die vielen Kunden die hübsche verspielte Grafiken haben wollen. Damit habe ich nur geringe chancen.
Wenn 

written in german: Want to use Libre office to draw Diagrams (UML, Function Blocks) with semantic content, but I am frustrated about details

[9876]

Hello
I have checked in the last year the possibility of using libre office for technical diagrams, the XML format (odg) is understanable, good readable and seems to be also stable. I have read out and convert some informations (Java programming), its proper. As base for semanitc content I have used style sheets in draw. Then, in the last year, I have written an article in german language: https://www.embedded-software-engineering.de/low-code-oder-no-code-in-der-anwenderprogrammierung-a-67f62846379fecb2dadf22e568c9ecdc/  but after them I havn't more time, have done other stuff.
Now, because the topic is currently, I have start with some more experience. But, really less details (have used the version 7.5.2.2 but also 6.4.x, same) makes the live very hard to stay :-((
One Detail: I have small connection points with a proper graphic, the connection points have the size 0.15 * 0.3 cm. It is large enough to select with the mouse to drag. The size is fixed. But, if I select it, suddenly the ... sorry should write in german furthermore, less time
 ... die Ziehpunkte für die Größe des Objekts werden angezeigt. Obwohl die Größe fix ist, vollkommen unnötig. Weil dann die Mouseposition offensichtlich innerhalb des fangbreiches dieser Größe-Ziehpunkte liegt, wird ein "verboten"-Symbol angezeigt (weil die Größe ja nicht änderbar ist), und ich kann das Objekt auch nicht mehr moven. Ab einer Größe von ca. 0.2 * 0.2 cm ist genug Platz, um in der Mitte einen Punkt zum moven zu finden aber bei 0.15 mm ist es zu klein. Die kleine Größe brauche ich aber, weil auf einem Diagramm ja auch was darzustellen sein soll, die Größe von 1.5 mm ist locker zu bearbeiten in "Seitenbreite" Auflösung eines 1920-Monitors, da ist also gar nix dagegen zu haben. Aber die "verboten" Ziehpunkte für die Größe drängeln sich vor, ohne benötigt zu werden, und nix geht. 
Vorher habe ich schon einiges probiert. Eine gute Idee war auch ein Textbox, in der der Name des Konnektors steht, diese ist durchsichtig, weil nur der Text sichtbar sein soll. Der ist dann mit dem notwendigen Symbol (filled or non filled diamond etc. wie in UML üblich) als Group verbunden - funktioniert super. Nur: Wenn ich das notwendige Stylesheet dem gesamten Objekt zuweise (weil ich das auch in der Anzeige sehen will) dann setzt sich die indirekte Formatiierung über die direkt vorgegebene (Raute oder Diamond muss eine Linienbreite haben, das Textfeld nicht...) und die Route wird unsichtbar, oder das Textfeld hat eine unwerwünschte Linie, je nachdem ich das Stylesheet einrichte. Diese Idee hatte ich dann aufgegeben, weil ich festgestellt habe, dass ein zugehöriger Text zu einem Objekt (der Raute als ConnectionPoint) auch so einstellbar ist, dass er links daneben erscheint. Super geht juchhe. Und dann dieses Sache mit der nicht-movebarkeit, siehe oberen Absatz.
In der Draw-Software dürfte die Korrektur der Movebarkeit fast ziemlich einfach sein, weil man nur ein if() braucht um bei gesperrter size diese unnötigen Größeziehpunkte erst gar nicht anzuzeigen. Der Rest wird dann so wie gehabt gehen. Doch ich weiß wie es mit den RFCs läuft. Sie werden einsortiert, nach priorität sortiert, und dann (zumindestens bei den kommerziellen Tools) wird das realisiert was der dümmste aber meist zahlende Kunde will. Bei den nichtkommerziellen Tools ist es ggf. nicht der zahlende, sondern der Mengenmößig überlegene, also die vielen Kunden die hübsche verspielte Grafiken haben wollen. Damit habe ich nur geringe chancen.
Wenn ich das selbst programmiere, hätte ich die Lösung, aber niemand sonst.
Ich bin jetzt beim Überlegen ob ich mir doch eine Visio-Lizenz anschaffe und Libre Office sein lasse, Aber Libre Office hat den charme, das es jeder leicht nutzen kann.
Die Entwicklung hin zu einem Grafikeditor für Grafische Programmierung könnte für Libre Office ein sehr interessantes Feld sein. Kurz zum Vergleich, ich verwende häufig auch Simulink, und dessen Grafikeditor ist teils Sch... sorry auch nicht so sehr gut, Die Basis-Grafikfähigkeiten von Libre Office mit seinen Connector - Verbindungen funktionieren besser !!!
Wenn ich auf die Mail eine Antwort bekomme und eine Chance sehe Gehör zu finden, dann melde ich mich in der Community an, spende einen Startbeitrag und formuliere meine Anforderungen RFC-mäßig. Im Moment bin ich noch frustriert, habe keine Zeit weil ich gleich zu einer Chorprobe weg muss (Kirchenmusik) man muss ja auch noch was anderes sinnvolles machen. 
Mit freundlichen Grüßen, Hartmut Schorrig
 

[Libreoffice-bugs] [Bug 155013] LibreOffice crashed

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155013

--- Comment #2 from BogdanB  ---
I was using the program, I go to chrome and when I return click on the sheet,
automatically the program closes. Didn't show up in the "no answer" window, it
just closed. When he opened, when he tried to recover the document, nothing was
recovered, he remained at first.

Actual Results:
I already added that information to the report

Expected Results:
I already added that information to Description 


Reproducible: Sometimes


User Profile Reset: Yes

Additional Info:
I already added that information to Description

Translated using LibreTranslate

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

[Libreoffice-bugs] [Bug 155013] LibreOffice crashed

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155013

Julien Nabet  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||serval2...@yahoo.fr
 Ever confirmed|0   |1

--- Comment #1 from Julien Nabet  ---
2 things you can try:
- upgrade to LO 7.5.2
- give a try at https://wiki.documentfoundation.org/QA/FirstSteps

Please provide some feedback in English about the result of all this.

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

[Libreoffice-bugs] [Bug 148712] Show the count of hidden sheets in the Calc spreadsheets statusbar

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=148712

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||86066


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=86066
[Bug 86066] [META] Bugs and improvements to the status bar
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 86066] [META] Bugs and improvements to the status bar

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=86066

BogdanB  changed:

   What|Removed |Added

 Depends on||148712


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=148712
[Bug 148712] Show the count of hidden sheets in the Calc spreadsheets statusbar
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108253] [META] Calc cell formula bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108253

BogdanB  changed:

   What|Removed |Added

 Depends on||146790


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=146790
[Bug 146790] Problème avec la fonction NB.SI() COUNTIF()
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 146790] Problème avec la fonction NB.SI() COUNTIF()

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=146790

BogdanB  changed:

   What|Removed |Added

 Blocks||108253
 CC||buzea.bog...@libreoffice.or
   ||g


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 151958] The COUNTIF function mis-counts

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=151958

BogdanB  changed:

   What|Removed |Added

 Blocks||108253
 CC||buzea.bog...@libreoffice.or
   ||g


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 108253] [META] Calc cell formula bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=108253

BogdanB  changed:

   What|Removed |Added

 Depends on||151958


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=151958
[Bug 151958] The COUNTIF function mis-counts
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155019] New: Strikethroughs don't copy from Calc to Writer

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=155019

Bug ID: 155019
   Summary: Strikethroughs don't copy from Calc to Writer
   Product: LibreOffice
   Version: 7.4.6.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rjfe...@msn.com

Description:
I created a spreadsheet that included several text entries formatted with
strikethroughs.  I copied the spreadsheet entries to the clipboard and used
Paste to add the entries to a Writer document.  The text copied correctly but
without strikethroughs.  After posting my problem, a user passed along a
solution:  Use Paste Special and choose HTML.  I am a very new user of LO and
it was suggested by the poster of the solution that this was a bug that should
be reported.

Steps to Reproduce:
1.Copy text with strikethroughs to clipboard in Calc.
2.Paste clipboard into Writer.
3.

Actual Results:
Text appears in Writer but strikethroughs are lost.

Expected Results:
Strikethroughs should be maintained between components.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.4.6.2 (x64) / LibreOffice Community
Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d
CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

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

[Libreoffice-bugs] [Bug 112125] [META] Hyperlink dialog bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=112125

BogdanB  changed:

   What|Removed |Added

 Depends on||151551


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=151551
[Bug 151551] Suggestion to drop frame target options from Link dialog
-- 
You are receiving this mail because:
You are the assignee for the bug.