[Libreoffice-bugs] [Bug 147450] Line end point moving not possible

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147450

Buovjaga  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||ilmari.lauhakangas@libreoff
   ||ice.org
 Ever confirmed|0   |1
 Whiteboard| QA:needsComment|

--- Comment #2 from Buovjaga  ---
No problem here. Can you retest with the latest version?

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED
WORKSFORME, if the problem went away.

Version: 7.4.3.2 / LibreOffice Community
Build ID: 40(Build:2)
CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: kf5 (cairo+wayland)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
7.4.3-3
Calc: threaded

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

[Libreoffice-bugs] [Bug 152560] Consistent appearance of dropdowns and Application Colors background

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152560

Buovjaga  changed:

   What|Removed |Added

  Component|LibreOffice |UI
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO
 CC||ilmari.lauhakangas@libreoff
   ||ice.org
Summary|Consisgtent appearance of   |Consistent appearance of
   |pop-ups and Appearance  |dropdowns and Application
   |background  |Colors background

--- Comment #2 from Buovjaga  ---
Just to make the use case clear, you are using a non-dark theme in your
operating system, but you want LibreOffice to look like it does in dark mode?

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.

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

[Libreoffice-bugs] [Bug 152561] Consistent appearance of pop-ups and Appearance background

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152561

Buovjaga  changed:

   What|Removed |Added

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

--- Comment #1 from Buovjaga  ---


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

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

[Libreoffice-bugs] [Bug 152560] Consisgtent appearance of pop-ups and Appearance background

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152560

--- Comment #1 from Buovjaga  ---
*** Bug 152561 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 152537] No obvious UI to set the document default font used e.g. in Line Numbering

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152537

--- Comment #13 from Mike Kaganski  ---
(In reply to Seán Ó Séaghdha from comment #12)
> I’m curious now about how this situation came about.  What is the use case
> for having separate styles ('style:default-style style:family="paragraph"'
> and 'style:style style:name="Standard" style:family="paragraph"')?

'style:style style:name="Standard" style:family="paragraph"' is a normal
paragraph style. It may be used as an ancestor in inheritance hierarchy; but it
is not a required hierarchy root. Any paragraph style may be set to not inherit
from *any style*, and become a root of own inheritance hierarchy (creating a
"forest" of paragraph style hierarchy trees).

>From the file format point of view, the need to store the defaults applicable
to *any* style of a given family (paragraph/text/...) that does not define a
property in its inheritance tree requires such 'style:default-style' elements.
They *allow* (but do not force) to create files that do not depend on user
settings and/or program versions (which may change the defaults).

The documentation for style:default-style is at
https://docs.oasis-open.org/office/OpenDocument/v1.3/OpenDocument-v1.3-part3-schema.html#element-style_default-style.

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

[Libreoffice-bugs] [Bug 152562] New: Crash Report Upload Missing on LibreOffice (Portable)

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152562

Bug ID: 152562
   Summary: Crash Report Upload Missing on LibreOffice (Portable)
   Product: LibreOffice
   Version: 7.4.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ktop...@gmail.com

Description:
I have used both the standard LibreOffice and Portable version on Windows.

With the standard version, I get a prompt to upload a crash report whenever I
have a crash to assist development team in fixing that bug.

However, I donot get any prompts to upload crash reports on the Portable
version of LibreOffice. I know many people use the Portable version and the
crash report upload feature is already available in the standard version of
LibreOffice.

I believe the crash upload feature should be restored on the Portable version
so all crash reports on the Portable version can be uploaded for debugging.

Workaround is to run standard version of LibreOffice (instead of portable) to
get the crash report upload prompts. Manually filing crash reports are too
time-consuming because they happen often when I work with complex spreadsheet.

Actual Results:
No prompts to upload crash report on LibreOffice (Portable)

Expected Results:
Prompt to upload crash report


Reproducible: Always


User Profile Reset: No

Additional Info:

Workaround is to run standard version of LibreOffice (instead of portable) to
get the crash report upload prompts. Manually filing crash reports are too
time-consuming because they happen often when I work with complex spreadsheet.

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

[Libreoffice-bugs] [Bug 152551] "Templates and Styles" help claims incorrectly that "Unless you specify otherwise, every new LibreOffice text document is based on the default template"

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152551

--- Comment #2 from Mike Kaganski  ---
(In reply to BogdanB from comment #1)
> my default template is 2 cm all margins. All new documents are the
> same. So, could be correct that all new documents are based on a template.

The latter does not follow from the former. "I have set a default template, and
my new documents are being created from it" is *not* equal to "all new
documents are based on a template".

> But only IF LibreOffice is taking default template when creating a new
> document.

LibreOffice *does* take a default template when creating a new document, *if
and only if* the default template is set. When it's not set, no template is
taken into account.

> But also, if the default template is created based on hardcoded numbers and
> a new document is created based on the same default hardcoded numbers that
> could also mean that it is based on the template, because we have the same
> settings in hardcoded code, template and new document created from code
> (default template).

This is playing words. The term "template" is used in a very specific sense in
the technical documentation, which is LibreOffice help. It is about a kind of
*files* (ODF) that have names, are placed somewhere in the filesystem, and so
on. The term "default template" also has a very specific meaning in the
documentation, namely "a template (see above) that is configured in LibreOffice
(either in shared configuration, or user configuration) to be used by default".
The philosophical/linguistical question "what one could call a template" is not
relevant to our documentation. And the current situation is confusing. And that
is especially important since MS Word, for instance, has a true "default
template" (normal.dot(m)), and so people tend to expect something similar in LO
*by default*.

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

[Libreoffice-bugs] [Bug 152228] Inconsistent "Show Boundaries" behavior based on document creation method

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152228

--- Comment #7 from BogdanB  ---
I confirm the behaviour with the doc "FromDesktop.odt".
When toogled "Show Text Boundaries" the table bounderies are gone.

But I can NOT reproduce with a new file in the same version.

So, it seems that there is a problem in the structure of the new created file.

Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: ad085990b8073a122ac5222e5220f8f1d6826dcf
CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152228] Inconsistent "Show Boundaries" behavior based on document creation method

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152228

BogdanB  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #6 from BogdanB  ---
I confirm the behaviour with the doc "FromDesktop.odt".
When toogled "Show Text Boundaries" the table bounderies are gone.

But I can reproduce with a new file in the same version.

So, it seems is a problem in the structure of the new created file.

Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: ad085990b8073a122ac5222e5220f8f1d6826dcf
CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 144814] Options dialog has some settings specific to current document & stored within it

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144814

--- Comment #20 from Seán Ó Séaghdha  ---
Just adding my support for removing any document-specific settings from
Tools|Options.  It’s just too confusing and adding indicators or colours would
be a poor fix.

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

[Libreoffice-bugs] [Bug 152228] Inconsistent "Show Boundaries" behavior based on document creation method

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152228

BogdanB  changed:

   What|Removed |Added

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

--- Comment #5 from BogdanB  ---
No problem in
Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: ad085990b8073a122ac5222e5220f8f1d6826dcf
CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

when I toogled "Show Text Boundaries" the corner of the page became
visible/invisible.

when I toogled "Show Table Boundaries" the invisible borders of the table
became visible/invisible.

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

[Libreoffice-bugs] [Bug 152551] "Templates and Styles" help claims incorrectly that "Unless you specify otherwise, every new LibreOffice text document is based on the default template"

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152551

BogdanB  changed:

   What|Removed |Added

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

--- Comment #1 from BogdanB  ---
Mike, my default template is 2 cm all margins. All new documents are the same.
So, could be correct that all new documents are based on a template. But only
IF LibreOffice is taking default template when creating a new document.

But also, if the default template is created based on hardcoded numbers and a
new document is created based on the same default hardcoded numbers that could
also mean that it is based on the template, because we have the same settings
in hardcoded code, template and new document created from code (default
template).

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

[Libreoffice-bugs] [Bug 152537] No obvious UI to set the document default font used e.g. in Line Numbering

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152537

--- Comment #12 from Seán Ó Séaghdha  ---
I’m curious now about how this situation came about.  What is the use case for
having separate styles ('style:default-style style:family="paragraph"' and
'style:style style:name="Standard" style:family="paragraph"')?

Is this just because styles in the interface require a name?  But since it’s
not the name that’s shown anyway...

How is having these separate styles actually useful? (ignoring for the moment
the complexity of collapsing them)

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

[Libreoffice-bugs] [Bug 152029] Visually draw attention to in-view bookmark or hyperlink when selecting/hovering it in the Navigator

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152029

--- Comment #39 from Commit Notification 
 ---
Jim Raykowski committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/1c6410fc51a89464898622ae3859931f81178a01

tdf#152029 cleanup: Bring content to attention in document view

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-bugs] [Bug 152517] Navigator: Ctrl+Minus collapses the whole Headings tree, not the selected node

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152517

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-bugs] [Bug 86209] MENUS: Reorganize the View menu

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=86209

--- Comment #11 from Mathew Aderson  ---
Each action (add, edit, remove, or move) when updating your menus counts as a
change. When you reach 200 changes, you are unable to take any more action
until you save your menu changes. https://wordhurdle.co

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

[Libreoffice-bugs] [Bug 147565] Browsing comments in the navigation pane also browses hidden solved comments

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147565

--- Comment #19 from Mathew Aderson  ---
I'm glad the problem is solved, thank you for sharing this information!
https://fnfonline.co/

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

[Libreoffice-bugs] [Bug 152507] Database table content not read or displayed in UI with an existing connection to ODB file

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152507

QA Administrators  changed:

   What|Removed |Added

   Keywords||bibisectRequest

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

[Libreoffice-bugs] [Bug 152514] Save icon in old high contrast theme extension disappears after any changes

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152514

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

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

[Libreoffice-bugs] [Bug 152356] Show indication when clicking on a template in canvas

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152356

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 149183] difficulté utilisation calc suite migration en 7.2

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149183

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 152514] Save icon in old high contrast theme extension disappears after any changes

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152514

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-bugs] [Bug 152348] LibreOffice Writer crash after installing Help on 4GB memory RAM

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152348

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 149183] difficulté utilisation calc suite migration en 7.2

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149183

--- Comment #3 from QA Administrators  ---
Dear air...@neuf.fr,

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 145336] Crash on setting table borders in LibreOffice Writer

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145336

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 145336] Crash on setting table borders in LibreOffice Writer

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145336

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

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 144023] Special character window not usable on Ubuntu 20.04 LTS

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144023

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 144023] Special character window not usable on Ubuntu 20.04 LTS

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144023

--- Comment #4 from QA Administrators  ---
Dear JaK,

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 142707] PDF: Export to PDF of relative hyperlinks created by function HYPERLINK() not plausible

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142707

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 127593] [META] Python Macro bugs

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127593
Bug 127593 depends on bug 141337, which changed state.

Bug 141337 Summary: Python doc.Sheets.copyByName(existingname, newname, 
position) does not update references in chart when copying sheets
https://bugs.documentfoundation.org/show_bug.cgi?id=141337

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 142707] PDF: Export to PDF of relative hyperlinks created by function HYPERLINK() not plausible

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142707

--- Comment #5 from QA Administrators  ---
Dear Norbert Scheibner,

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 141337] Python doc.Sheets.copyByName(existingname, newname, position) does not update references in chart when copying sheets

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141337

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 141337] Python doc.Sheets.copyByName(existingname, newname, position) does not update references in chart when copying sheets

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141337

--- Comment #4 from QA Administrators  ---
Dear nib70776,

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 140238] LibreOffice Base - Table Control - navigating using tab and / keys not working as it used to

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=140238

--- Comment #4 from QA Administrators  ---
Dear Tony,

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 84032] Intersection of some polygons produces wrong result

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=84032

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

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 138980] CTRL+A cut doesn't include image frame/ with image if record changes being enabled

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138980

--- Comment #3 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 138765] set the displayed size of an image inserted in Writer by changing its DPI

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138765

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

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 115270] LibreOffice Impress export *.SVG = fail. Usage of "javascript:window" in a TEXT Link results in fundamentally flawed behavior in the web browser.

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115270

--- Comment #7 from QA Administrators  ---
Dear UbunLibOffImp,

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 138588] it is can not make duplication (copy&paste) Zotero citation.

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138588

--- Comment #2 from QA Administrators  ---
Dear SergeiD,

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 118054] Writer doesn't show the initial image before cropping in the background (like Calc/Impress/Draw)

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=118054

--- Comment #6 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 117953] VIEWING: Default text position in form text box changes with scale (zoom) when aligned to right in Writer

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117953

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

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 115590] Image position is wrong, if svg:x and svg:y does not exist

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115590

--- Comment #11 from QA Administrators  ---
Dear Regina Henschel,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 152521] Thick ugly black border around boolean tickbox in database table grid view

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152521

--- Comment #7 from m.a.riosv  ---
Created attachment 184203
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184203&action=edit
Screnshoot

You are right, hope this is the one.

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

[Libreoffice-bugs] [Bug 152228] Inconsistent "Show Boundaries" behavior based on document creation method

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152228

altasilvap...@gmail.com  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #4 from altasilvap...@gmail.com  ---
Sorry for the delay; I was finally able to get back to this.  I am now updated
to 7.4.3.2, and can confirm the described behavior persists.

I've also uploaded two test documents that I used to confirm the error:

"FromDesktop.odt"
1. Right-click on desktop
2. Context menu "New"
3. Select "Open Document Text"

"FromFileNew.odt"
1. Open LibreOffice
2. File menu
3. New -> Text Document

Then in each file, I inserted a table of a random size, set the properties of
said table to have no boundary, and then tried toggling "Show Text Boundaries"
and "Show Table Boundaries".

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

[Libreoffice-bugs] [Bug 152228] Inconsistent "Show Boundaries" behavior based on document creation method

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152228

--- Comment #3 from altasilvap...@gmail.com  ---
Created attachment 184202
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184202&action=edit
Test file created from Windows Right-Click Context->New->Open Document Text

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

[Libreoffice-bugs] [Bug 152228] Inconsistent "Show Boundaries" behavior based on document creation method

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152228

--- Comment #2 from altasilvap...@gmail.com  ---
Created attachment 184201
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184201&action=edit
Test file created from LibreOffice File->New->Text Document

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

[Libreoffice-bugs] [Bug 152561] New: Consistent appearance of pop-ups and Appearance background

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152561

Bug ID: 152561
   Summary: Consistent appearance of pop-ups and Appearance
background
   Product: LibreOffice
   Version: 7.4.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: aschw...@acm.org

Description:
ENHANCEMENT: Would it be possible to have the
Tools->Options->LIbreOffice->Appearance setting effect pop-ups? I have selected
LibreOffice Dark for appearance, and would like the pop-ups to reflect this
selection.

Steps to Reproduce:
1. Point and Click and option in the option bar
2. Observe pop-up

Actual Results:
Pop-up appears in Libre Office default Appearance

Expected Results:
Same result


Reproducible: Always


User Profile Reset: No

Additional Info:
SEE ABOVE

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

[Libreoffice-bugs] [Bug 152560] New: Consisgtent appearance of pop-ups and Appearance background

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152560

Bug ID: 152560
   Summary: Consisgtent appearance of pop-ups and Appearance
background
   Product: LibreOffice
   Version: 7.4.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: aschw...@acm.org

Description:
ENHANCEMENT: Would it be possible to have the
Tools->Options->LIbreOffice->Appearance setting effect pop-ups? I have selected
LibreOffice Dark for appearance, and would like the pop-ups to reflect this
selection.

Steps to Reproduce:
1. Point and Click and option in the option bar
2. Observe pop-up

Actual Results:
Pop-up appears in Libre Office default Appearance

Expected Results:
Same result


Reproducible: Always


User Profile Reset: No

Additional Info:
SEE ABOVE

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

[Libreoffice-bugs] [Bug 144906] CRASH when editing date field

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=144906

Caolán McNamara  changed:

   What|Removed |Added

 CC||caol...@redhat.com

--- Comment #7 from Caolán McNamara  ---
Seeing as the bt suggests SwContentTree is involved, is there a floating
Navigator open at the time (the one from F5) or a Navigator open in the
sidebar?

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

[Libreoffice-bugs] [Bug 152514] Save icon in old high contrast theme extension disappears after any changes

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152514

--- Comment #6 from Artur Wdo  ---
In OpenOffice is work fine. Before changes icon is dark and after any changes
icon become blue.

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

[Libreoffice-bugs] [Bug 152514] Save icon in old high contrast theme extension disappears after any changes

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152514

--- Comment #5 from Artur Wdo  ---
Created attachment 184200
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184200&action=edit
issue

In alpha version behavior is the same.

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

[Libreoffice-bugs] [Bug 152559] Skia - LibreOffice Draw crashed when I zoom in the view of a diagram

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152559

--- Comment #2 from robomurphy98  ---
It can test fine when "playing around" by resizing the panel, zooming in and
out of the drawing view, or changing the page orientation.

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

[Libreoffice-bugs] [Bug 152559] Skia - LibreOffice Draw crashed when I zoom in the view of a diagram

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152559

--- Comment #1 from robomurphy98  ---
Created attachment 184199
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184199&action=edit
When I resize the pages panel

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

[Libreoffice-bugs] [Bug 152559] New: Skia - LibreOffice Draw crashed when I zoom in the view of a diagram

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152559

Bug ID: 152559
   Summary: Skia - LibreOffice Draw crashed when I zoom in the
view of a diagram
   Product: LibreOffice
   Version: 7.4.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: pabloaria...@hotmail.com

Description:
Good evening everyone, I have Skia enabled in LibreOffice and I started to make
a small entity relationship diagram. Before starting the document I made the
pages panel smaller to have a better view and I began to draw.

Everything was going well but it was to enlarge the view of the drawing with
the mouse the view and in this... crash. It's not the first time this has
happened to me, there are other times that just changing the size of the page
panels also crashes.

Steps to Reproduce:
1.Open LibreOffice Draw
2.Change the size of pages panel
3.Zoom in the drawing

Actual Results:
Crash

Expected Results:
Not crash


Reproducible: Sometimes


User Profile Reset: Yes

Additional Info:
Sometimes just changing the page panel size crashes, in Impress it once
happened to me.

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

[Libreoffice-bugs] [Bug 152558] Calc Cell Borders are inconsistent with the drop-down graphic selector. Also, No help page for manual definitions

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152558

--- Comment #1 from Colin  ---
Created attachment 184198
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184198&action=edit
Simple .ods with examples

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

[Libreoffice-bugs] [Bug 152558] New: Calc Cell Borders are inconsistent with the drop-down graphic selector. Also, No help page for manual definitions

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152558

Bug ID: 152558
   Summary: Calc Cell Borders are inconsistent with the drop-down
graphic selector. Also, No help page for manual
definitions
   Product: LibreOffice
   Version: 7.3.7.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: that.man.co...@gmail.com

Description:
The drop-down graphic pane for selecting the cell border style presents
incorrect graphic illustrations of the anticipated results. I'm also convinced
there used to be a much thinner "default" single-line border.
The help page associated with the cell format [F1] Help function doesn't exist

Steps to Reproduce:
Refer to the attached demonstration file.
It may help to zoom the sheet


Actual Results:
Borders are inconsistent with the grsphic representations. Also, I'm convinced
there was a "default" single outline defined as soon as an outline was
selected. Now it's blank until the characteristics have been "selected" but it
was much thinner than the current Outset option which presents as the thinnest
line.

Expected Results:
Consistency. I suspect previous work on the outline function has erroneously
left the programmers' experiments as the currently delivered defaults.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.3.7.2 (x64) / LibreOffice Community
Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: sv-SE (en_GB); UI: en-GB
Calc: threaded

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

[Libreoffice-bugs] [Bug 152517] Navigator: Ctrl+Minus collapses the whole Headings tree, not the selected node

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152517

--- Comment #7 from Jim Raykowski  ---
(In reply to Jim Raykowski from comment #6)
> Yes, very interesting. It seems the styles list uses nullptr as the parent
> for all entries[1] which makes[2] work as expected because of[3].
> 
> [1]
> https://opengrok.libreoffice.org/xref/core/sfx2/source/dialog/StyleList.
> cxx?r=ef862ba4#949
> [2]
> https://opengrok.libreoffice.org/xref/core/vcl/source/treelist/svimpbox.
> cxx?r=5f9cd841#2393
> [3]
> https://opengrok.libreoffice.org/xref/core/vcl/source/treelist/treelist.
> cxx?r=6e2bd112&mo=29042&fi=1020#1020

After further investigation, it seems there is something not right with
SvTreeList::GetRootLevelParent. The only place I could find it called from
is[2]. TreeListBox::GetRootLevelParent seems correct though[4].

[4]
https://opengrok.libreoffice.org/xref/core/dbaccess/source/ui/control/dbtreelistbox.cxx?r=5f6596bd#485

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

[Libreoffice-bugs] [Bug 138775] Hiding menubar is not permanent in Single or Standard Toolbar UIs

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=138775

--- Comment #6 from gilbertohasn...@gmail.com ---
Hi, bug is still present in current version. Information from About
LibreOffice:

Version: 7.4.2.3 / LibreOffice Community
Build ID: 40(Build:3)
CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.20.04.1~lo1
Calc: threaded


(In reply to QA Administrators from comment #5)
> Dear gilbertohasnofb,
> 
> 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 67622] UI: Add vertical alignment options for text frames in Impress to tool bar

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=67622

--- Comment #13 from Eyal Rozenberg  ---
(In reply to Tin Man from comment #8)
> UX input:
> Toolbar buttons for aligning the text vertically like those in Calc would be
> useful indeed, not just for discoverability, but also for quick access.

I think we already have these...

https://i.imgur.com/FYYKjGt.png

> A button for the Text dialog in the Formatting toolbar would be useful as
> well -- currently, the dialog is quite undiscoverable.

Do you mean "Text Attributes..." from the Format | Text Box and Shape submenu?
Also exists.

But - perhaps you're suggesting putting all of these on the toolbars by
default?

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

[Libreoffice-bugs] [Bug 152545] Connectors line spacing problem

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152545

raal  changed:

   What|Removed |Added

   Keywords||bibisected, bisected
 CC||nem...@numbertext.org
  Regression By||László Németh

--- Comment #4 from raal  ---
This seems to have begun at the below commit.
Adding Cc: to László Németh; Could you possibly take a look at this one?
Thanks

3b1e6d7cd7c153358b0793caa2da016590f607cc is the first bad commit
commit 3b1e6d7cd7c153358b0793caa2da016590f607cc
Author: Jenkins Build User 
Date:   Thu Oct 27 20:29:32 2022 +0200

source sha:eec48130271188cab63665acedbabf1ff5e850a2

https://gerrit.libreoffice.org/c/core/+/141723

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

[Libreoffice-bugs] [Bug 152545] Connectors line spacing problem

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152545

raal  changed:

   What|Removed |Added

 CC||r...@post.cz
   Keywords||regression
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #3 from raal  ---
Works in Version: 7.3.7.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: cs-CZ
Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.1
Calc: threaded

broken in Version: 7.5.0.0.beta1+ (X86_64) / LibreOffice Community
Build ID: 89188837f60d83a901b2c43f73d30e1957920f50
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152546] in Czech only! Error filtering

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152546

raal  changed:

   What|Removed |Added

 CC||kam...@post.cz,
   ||r...@post.cz
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #1 from raal  ---
Uveďte konkrétní příklad, přiložte testovací dokument. Zkuste novější verzi LO,
aktuálně podporované řady jsou 7.3 a 7.4 - https://cs.libreoffice.org/. Díky.

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

[Libreoffice-bugs] [Bug 47997] FILESAVE PPT Indent of paragraph is wrong

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=47997

--- Comment #10 from Stéphane Guillou (stragu) 
 ---
Repro in:

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

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

[Libreoffice-bugs] [Bug 42196] Automatically extend the chart data source range when adding rows at the end

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42196

Stéphane Guillou (stragu)  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 108539] [META] Chart data table bugs and enhancements

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108539
Bug 108539 depends on bug 47584, which changed state.

Bug 47584 Summary: When adding data, Calc should suggest extending the data 
range to include it in the chart
https://bugs.documentfoundation.org/show_bug.cgi?id=47584

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

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

[Libreoffice-bugs] [Bug 42196] Automatically extend the chart data source range when adding rows at the end

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=42196

--- Comment #14 from Stéphane Guillou (stragu) 
 ---
*** Bug 47584 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 47584] When adding data, Calc should suggest extending the data range to include it in the chart

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=47584

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED

--- Comment #8 from Stéphane Guillou (stragu) 
 ---


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

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

[Libreoffice-bugs] [Bug 152557] Chart data range reduces range / removes cell when adding series, shifts labels

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152557

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 152557] New: Chart data range reduces range / removes cell when adding series, shifts labels

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152557

Bug ID: 152557
   Summary: Chart data range reduces range / removes cell when
adding series, shifts labels
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Chart
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: stephane.guil...@libreoffice.org
Blocks: 90486

When modifying a chart data range that is not entirely rectangular, the smaller
range is further reduced upon saving, ultimately losing data in the chart.

Steps:
1. Open attachment 183259
2. Open data ranges dialog
3. Add ";Table1.C1:C4" to the range to add a series
4. See that extra bar was added
5. Reopen data ranges dialog to see that range was simplified to
"Table1.A2:A4;Table1.B1:E4" (still only top-left cell excluded from range)


Result 1:
"A" label is gone, other labels are shifted to the left, even though the range
still says cell A2 is included.

6. Save, reload

Result 2:
Data range was updated to "Table1.A3:A4;Table1.B1:E4" (i.e. two top cells of
column A have been excluded), which matches the glitch witnessed in the chart.

In:

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

Also in OOo 3.3:

OpenOffice.org 3.3.0
OOO330m20(Build:9567)


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 90486] [META] Chart bugs and enhancements

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=90486

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||152557


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152557
[Bug 152557] Chart data range reduces range / removes cell when adding series,
shifts labels
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152333] Crash opening saved spreadsheet which was modified with macro

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152333

--- Comment #6 from Jim Avera  ---
Created attachment 184197
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184197&action=edit
strace.log from new hang (see comment #4)

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

[Libreoffice-bugs] [Bug 152333] Crash opening saved spreadsheet which was modified with macro

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152333

--- Comment #5 from Jim Avera  ---
Created attachment 184196
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184196&action=edit
gdbtrace.log from new hang (see comment #4)

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

[Libreoffice-bugs] [Bug 152333] Crash opening saved spreadsheet which was modified with macro

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152333

--- Comment #4 from Jim Avera  ---
I downloaded today's "master" build and it always hangs at exit, with a thread
blocked in futex_wait.  I'll attach backtrace and strace logs.  \

Until this is worked out it's hard to investigate the earlier problem.

STEPS TO REPRODUCE HANG:

$ /path/to/instdir/program/soffice   # no arguments
File->Exit
(hangs)

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

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

[Libreoffice-bugs] [Bug 128233] macOS: Can't save or open files using Finder dialog on Standard accounts

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128233

Telesto  changed:

   What|Removed |Added

 CC||plub...@neooffice.org

--- Comment #79 from Telesto  ---
@Patrick
Another lovely bug. 24 duplicates, 40 people in CC. You likely tackled this
problem before..

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

[Libreoffice-bugs] [Bug 152031] Reducing width of RTL table creates "stairway" effect

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152031

--- Comment #8 from Stéphane Guillou (stragu) 
 ---
I see it fixed in:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 4e4a31ac7d920c71e26ca4acd18c11ec2bd015bb
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 Mark! Do you have follow-up commits or can this be marked as
resolved?

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

[Libreoffice-bugs] [Bug 152085] Section with two columns do not work in East Asian vertical writing mode (TB_RL)

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152085

--- Comment #8 from Stéphane Guillou (stragu) 
 ---
I can see it fixed in:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 4e4a31ac7d920c71e26ca4acd18c11ec2bd015bb
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 Mark! Do you have follow-up commits?

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

[Libreoffice-bugs] [Bug 132657] UI: Compress Image, reducing image resolution actually increases resolution

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=132657

--- Comment #15 from Stéphane Guillou (stragu) 
 ---
Please also see some very relevant comments in Bug 145161.

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

[Libreoffice-bugs] [Bug 145161] Image compression dialog is misleadingly labelled: doesn't always "reduce image resolution" (comment 9)

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145161

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

Summary|Writer Impress : the image  |Image compression dialog is
   |compression form should |misleadingly labelled:
   |change the image resolution |doesn't always "reduce
   |only if it decreases|image resolution" (comment
   ||9)

--- Comment #10 from Stéphane Guillou (stragu) 
 ---
(In reply to Heiko Tietze from comment #9)

> This ticket kind of duplicates bug 132657, up to QA.

Seeing the UX recommendations, let's keep this ticket as the relabelling
easyHack. Changing summary accordingly.

Bug 132657 can continue the discussion around potential deeper changes,
regarding size / resolution limits, syncing of values, etc.

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

[Libreoffice-bugs] [Bug 152556] New: Right-click context menu for line numbering area should show line-numbering-related items

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152556

Bug ID: 152556
   Summary: Right-click context menu for line numbering area
should show line-numbering-related items
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com

When we right-click somewhere the line numbering area, we get the same context
menu as if we had right-clicked the paragraph with the line being counted, with
entries like "Character", "Paragraph", "List" - which apply to the paragraph,
not the LN region.

Instead, the context menu should mostly have an entry for opening the Line
Numbering dialog (accessible via Tools | Line Numbering... on the menu). This
would, in particular, allow the user to more easily get to where they can
change the LN character style than in the current state of affairs.

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

[Libreoffice-bugs] [Bug 152555] No UI for styling Line Numbering numbers

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152555

Eyal Rozenberg  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|NEEDINFO|RESOLVED

--- Comment #4 from Eyal Rozenberg  ---
(In reply to Dieter from comment #3)
> Tools -> Line Numbering -> Character Style

Wow, I must be blind. Or rather, I guess I ignored that, expecting something
which opens a style dialog rather just the combo-box.

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

[Libreoffice-bugs] [Bug 113944] [META] Options dialog's Writer settings bugs and enhancements

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113944

Dieter  changed:

   What|Removed |Added

 Depends on||152391


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152391
[Bug 152391] VIEWING, CONFIGURATION: No possibility to customize or disable the
display of the new Moved track changes
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152391] VIEWING, CONFIGURATION: No possibility to customize or disable the display of the new Moved track changes

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152391

Dieter  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de,
   ||nem...@numbertext.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
 Blocks||113944

--- Comment #2 from Dieter  ---
I confirm, that option is missing

Version: 7.4.3.2 (x64) / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

László, you've implemented the move feature. Is it possible for you to add
customisation?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=113944
[Bug 113944] [META] Options dialog's Writer settings bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152360] White line above and under page in Writer. Appears and disappears when scrolling.

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152360

Dieter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #2 from Dieter  ---
(In reply to Telesto from comment #1)
> I could reproduce it with
> Version: 7.5.0.0.alpha0+ / LibreOffice Community
> Build ID: c1c8ce3b0f1037bca4d500af2f39363cd9d38db6
> CPU threads: 8; OS: Mac OS X 12.3.1; UI render: Skia/Metal; VCL: osx
> Locale: nl-NL (nl_NL.UTF-8); UI: en-US
> Calc: threaded

=> NEW

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

[Libreoffice-bugs] [Bug 151341] Slow macOS install caused by bzip2 dmg

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151341

Patrick Luby  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |plub...@neooffice.org
   |desktop.org |

--- Comment #15 from Patrick Luby  ---
I have changed the .dmg compression from bzip2 to lzfse and I have posted a
patch at:

https://gerrit.libreoffice.org/c/core/+/144342

The patch needs still needs to be reviewed and tested before it appears in a
nightly build but my limited testing showed at least a 5x increase in copying
speed on an old MacBook Pro Intel laptop while increasing the .dmg file size by
only 4% or 5%.

If any LibreOffice release engineers can review the above patch, that would be
very much appreciated. Hopefully they can determine if the small increase in
.dmg file size won't cause an increase in TDF's bandwidth costs.

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

[Libreoffice-bugs] [Bug 152555] No UI for styling Line Numbering numbers

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152555

--- Comment #3 from Dieter  ---
(In reply to Eyal Rozenberg from comment #2)
> Where, exactly?

Tools -> Line Numbering -> Character Style

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

[Libreoffice-bugs] [Bug 152555] No UI for styling Line Numbering numbers

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152555

--- Comment #2 from Eyal Rozenberg  ---
(In reply to Dieter from comment #1)
> Eyal, I don't understand the feature request, because you can choose a
> character style for line numbering.

Where, exactly?

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

[Libreoffice-bugs] [Bug 151341] Slow macOS install caused by bzip2 dmg

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151341

--- Comment #14 from Patrick Luby  ---
(In reply to Stephan Bergmann from comment #13)
> (In reply to Patrick Luby from comment #11)
> > Can anyone tell me how to actually build the .dmg in the LibreOffice build?
> 
> that's configure option --with-package-format=dmg

@Stephan Bergmann

Thank you for the tip. It worked perfectly.

For anyone using LODE like me, here are the steps that I used to build a .dmg:

./autogen.sh --with-package-format=dmg
make

Note: "make check" appears to skip building the .dmg so you

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

[Libreoffice-bugs] [Bug 150147] Zoom problem in LO 7-4-0 in macOS (Intel hardware)

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150147

--- Comment #16 from Vincent Boudry  ---
(In reply to Vincent Boudry from comment #13)
> I have a similar problem with Impress, when using an external screen, either
> when presenting, or moving a window from one screen to another.
> 
> It looks like the screen resolution is not set correctly: on 2 different
> set-ups, I have observed opposite effects:
>  - either a blown-up display showing only the upper-left corner of the slide.
>  - or a window only occupied in the upper left corner by a miniature of the
> slide (screen copy).
> 
> This only occurs using the skia rendering.

This is using LO 7.5.0beta1
OSX Ventura 3.0.1 (22A400)

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

[Libreoffice-bugs] [Bug 150147] Zoom problem in LO 7-4-0 in macOS (Intel hardware)

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150147

--- Comment #15 from Vincent Boudry  ---
Created attachment 184195
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184195&action=edit
Screen copy of a presentation with a video,

The video is at the right place, the rest of the slide is squeezed in the
upper-left corner.

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

[Libreoffice-bugs] [Bug 150147] Zoom problem in LO 7-4-0 in macOS (Intel hardware)

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150147

--- Comment #14 from Vincent Boudry  ---
Created attachment 184194
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184194&action=edit
Screen copy of a window moved from the starting screen to a secondary one.

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

[Libreoffice-bugs] [Bug 150147] Zoom problem in LO 7-4-0 in macOS (Intel hardware)

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150147

--- Comment #13 from Vincent Boudry  ---
I have a similar problem with Impress, when using an external screen, either
when presenting, or moving a window from one screen to another.

It looks like the screen resolution is not set correctly: on 2 different
set-ups, I have observed opposite effects:
 - either a blown-up display showing only the upper-left corner of the slide.
 - or a window only occupied in the upper left corner by a miniature of the
slide (screen copy).

This only occurs using the skia rendering.

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

[Libreoffice-bugs] [Bug 152555] No UI for styling Line Numbering numbers

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152555

Dieter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1

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

[Libreoffice-bugs] [Bug 152555] No UI for styling Line Numbering numbers

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152555

Dieter  changed:

   What|Removed |Added

 CC||dgp-m...@gmx.de

--- Comment #1 from Dieter  ---
Eyal, I don't understand the feature request, because you can choose a
character style for line numbering.
=> NEEDINFO

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

[Libreoffice-bugs] [Bug 147397] Calc: Spellcheck underlines a word that is in the dictionary

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147397

--- Comment #7 from Marco A.G.Pinto  ---
Kevin Atkinson's GitHub:
https://github.com/en-wl/wordlist

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

[Libreoffice-bugs] [Bug 152555] New: No UI for styling Line Numbering numbers

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152555

Bug ID: 152555
   Summary: No UI for styling Line Numbering numbers
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com

(This is a spin-off from bug 152537)

We should be able to change many/most style aspects of Line Numbering numbers:
Font family, character width factor, inter-character spacing, font digit
variant choice (old-style: https://en.wikipedia.org/wiki/Text_figures ),
boldface, color, etc. etc.

Yet - there does not seem to be any place in the UI to do so. These aspects do
not (currently) originate in any character style, nor do they have any
sui-generis settings in the UI.

One might ask "shouldn't Line Numbering (LN) be styled based on the default PS?
Or rather that PS' default CS?" - and I would say no, because the LN of a
paragraph is not part of the paragraph, it's in a separate area of the page;
and the LN numbers overall also don't constitute a paragraph. They could
potentially have a CS, e.g. analogously to footnote references. However - one
could also argue against this, in the sense that the font size at least is set
dynamically based on the counted line's effective height etc. So maybe a CS
with some aspects of it disabled? Or ignored?

Another question to be asked regards font size. LN numbers get scaled down
automatically as you decrease the font; will we want to allow overriding this
behavior? Make it relative to the font size the user has set?

As far as where such UI should be available: I want to be able to change the LN
style (and specifically maximum font size) by right-clicking the LN area or an
actual LN number at least; and via Tools | Line Numbering. I'm not saying the
UI for this styling should be on these actual menu and dialog respectively, but
I should be able to access it via those two places.

(Right now I can't even get to the LN properties from the right-click context
menu, by the way; perhaps I should file another bug this?)

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

[Libreoffice-bugs] [Bug 152341] Page background pick-up color display is wrong

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152341

Dieter  changed:

   What|Removed |Added

 OS|All |macOS (All)

--- Comment #8 from Dieter  ---
(In reply to dhina from comment #7)
> Would it be related to the changes made on this Dev version to  support
> macOS dark Mode?

Don't know. I hope a Mac user can help.

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

[Libreoffice-bugs] [Bug 152543] TRANSPOSE: error when the number of array elements exceeds 16384

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152543

Eike Rathke  changed:

   What|Removed |Added

   Priority|medium  |low
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
   Severity|normal  |minor

--- Comment #1 from Eike Rathke  ---
Yes of course. sheet::FunctionAccess uses a temporary spreadsheet to do its
calculations. The maximum number of columns is 16384.

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

[Libreoffice-bugs] [Bug 152554] New: Spell Check Does Not Have Proper Word Recognition

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152554

Bug ID: 152554
   Summary: Spell Check Does Not Have Proper Word Recognition
   Product: LibreOffice
   Version: 7.3.2.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Linguistic
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: kit...@tutanota.com
CC: so...@libreoffice.org

Description:
When selecting to spell check, a word is not very well recognized.  It is
assumed that the algorithm and/or the dictionary depth is not sufficient to do
the job.

Steps to Reproduce:
1.Select to spell-check a word such as "disside".  (Should be "decide")
2.The return is poorly chosen and does not offer the proper word.
3.

Actual Results:
Poor choice of substitute words was returned.

Expected Results:
Should have more word choices in dictionary.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.3.2.2 / LibreOffice Community
Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0
CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Debian Bullseye with Xfce 4.16

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

[Libreoffice-bugs] [Bug 103494] [META] Textbox bugs and enhancements

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103494

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||144341


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=144341
[Bug 144341] Unable to set alignment for hyperlinks in text boxes
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 147397] Calc: Spellcheck underlines a word that is in the dictionary

2022-12-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147397

Buovjaga  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |NOTOURBUG

--- Comment #6 from Buovjaga  ---
Ok, I will close this and maybe you can share the Github as I could not find it

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

  1   2   3   >