[Libreoffice-bugs] [Bug 152550] Drop the "Basic Fonts" option dialogs

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

--- Comment #6 from Mike Kaganski  ---
(In reply to Eyal Rozenberg from comment #3)
> > I agree that the settings discussed here are very problematic. These
> > settings control these things:
> > 
> > 1. User defaults stored in registrymodifications.xcu, used for new documents
> > created when no default template is set:
> >
> > 2.  element in
> > the current document;
> > 3. Properties of *some* user-visible pre-defined styles, like "Default
> > Paragraph Style" (which has internal name of "Standard").
> 
> Can you clarify the difference between (2.) and (3.)? Is (3.) outside of the
> current document? Is it in the default template, if one exists?

Let me try once more (sorry, the following is TL;DR).
I suppose that it could look more confusing than it actually is, just because
of this confusing dialog.

Please start from the file format / document in mind.
The document has a set of defaults for *any* paragraphs (in ODF, these are
stored in the ). These defaults
are used when any given setting is not set in a given style inheritance
hierarchy, so the  may be
considered an implicit root of all  inheritance trees.

Remove any given property from a given ODF, and the program would need to use
some default. If there is a configurable setting for it, the default value
could (?) be obtained from there (tdf#150377). Or a hardcoded default should be
used. Use of hardcoded default instead of a configurable setting has its own
pros, like making documents more predictable even with some settings missing
from them - *if* the hardcoded default is not likely to change across versions
and locales and such.

A document may be created from a template. A template is a document; and
creating from a document basically copies everything (just a little bit
simplifying), so *everything defined in the template* is used instead of any
default or configuration - so defaults/settings are not relevant for template
case.

There is an option to not use any template (and this is the default); it has
some own advantages (already mentioned flexibility). People may want to keep
using it (e.g., because they simply don't want to bother with setting up a
template; or because of some other considerations), and at the same time, they
might want to define some custom properties for newly created documents
(basically, they need something like partial "templates"). This is implemented
by having some configurable user settings like '' in
registrymodifications.xcu, used only when creating new documents, and only when
no template is used for that.



With all that (I hope the description is reasonable complete), the behavior is
flexible and defined. But the problem arises when one, for some completely
weird reason, decides to merge three things in one control in a strange place.
The place choice is the least of the problems here - because it's easy to move
it anywhere; but no matter where you move it, it will be not less confusing,
unless it's split into three (and there is already a place for one of the
three).

The specific controls there are font names and sizes:

* Default
* Heading
* List
* Caption
* Index

First, let's skip the most problematic "Default", and look at the rest. They
all control only *two* things each:
- the respective properties of respective paragraph styles in the current
document;
- the user settings under  in
registrymodifications.xcu.

What a user will *see* in the controls when they open this dialog? They will
see the values from the current document (you can't have the dialog when Writer
document is not current). There's no way to get the values from
registrymodifications.xcu - only if they happen to be the same, e.g. because
the current document is just created without a template, and the styles are not
changed from the defaults...

What will be saved when you press OK? Both. Previously, there was a "[ ]
Current document only" checkbox in the bottom of that page, allowing only store
that in the styles in current document, but without updating the user defaults
in registrymodifications.xcu ... but I don't see it there anymore at least in
7.4.3.2 (I am sure there was some misguided decision to "simplify" the UI
related to this).

Now let's look at the most problematic "Default" entry.

1. What does it control?

- The respective properties of 
(i.e., the root of *all* paragraph hierarchies);
- the user settings under  in
registrymodifications.xcu.

Is this all? No. When setting the  properties, it *also* resets respective properties in
 (i.e., the font
properties of the "Default Paragraph Style").

So, there are *three* things that it controls.

2. What do you see in the controls when opening the dialog?

You see the value of the respective properties in the "Default Paragraph
Style". Not what is stored in style:default-style, nor what is set in
registrymodifications.xcu.

Given all that, I wonder how on earth a user could figure all the
interrelations of 

[Libreoffice-bugs] [Bug 150377] ODF without font information uses hardcoded defaults, should use settings from Options->Writer->Basic Fonts

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

Mike Kaganski  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |NOTABUG

--- Comment #3 from Mike Kaganski  ---
An advantage of using hardcoded defaults in the absence of an information in
the document is having "partial" documents more predictable, less dependent on
custom settings (in case when the hardcoded defaults never change across
program versions). Another reason to WONTFIX (possibly the most important), or
even NOTABUG (works as intended), which I will assume here.

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

[Libreoffice-bugs] [Bug 152566] Smooth vertical scroll in spreadsheets please

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from V Stuart Foote  ---


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

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

[Libreoffice-bugs] [Bug 40917] UI: Calc currently scrolling only by full row height

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||rm.pa...@freenet.de

--- Comment #22 from V Stuart Foote  ---
*** Bug 152566 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 152550] Drop the "Basic Fonts" option dialogs

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

--- Comment #5 from Mike Kaganski  ---
(In reply to Eyal Rozenberg from comment #3)
> Is (3.) ... in the default template, if one exists?

Yes, these styles indeed are stored in any document, including any template;
and when they are in the template, they are used to create new documents, not
the setting here. Same for #2, BTW.

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

[Libreoffice-bugs] [Bug 152550] Drop the "Basic Fonts" option dialogs

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

Mike Kaganski  changed:

   What|Removed |Added

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

--- Comment #4 from Mike Kaganski  ---
(In reply to Eyal Rozenberg from comment #3)
> the template named "Default" isn't the default?

Exactly. And it should be renamed because of the confusion the name creates.

> And - can I select one of the templates as the default, then? I don't see
> any UI for that.

File->Templates->Manage Templates (also available from the "Templates" split
button in the Start Center), and right-click them there.

> > When no template is made
> > the default, LibreOffice uses some settings set in user preferences (like
> > the "Basic Fonts" discussed here, *one of* the functions of which is setting
> > this global user preference, or the user's locale, which defines the page
> > size). If those settings are not set (or even are impossible to set without
> > templates, which is true for most of the numerous document settings), some
> > hard-coded program defaults are used.
> 
> So, what's your opinion about this state of affairs? As opposed to, say,
> there _always_ being a default template in the user's profile (and if it's
> missing, one is generated when the module comes up, from hard-code values or
> from a default-of-default-templates that's not in the user's profile)

I don't see a problem in the status quo, specifically in this regard. As I
mention in bug 152551, not being forced to have a default template file makes
it possible to have some dynamic behavior, like page size dependent on the
locale. And allowing to set any template as default gives maximum flexibility.
IMO, it could only seem confusing because (1) the name of one of the templates
(#1 above), and (2) MS Office background.

> > These settings control these things:
> > ...
> > 2.  element in
> > the current document;
> > 3. Properties of *some* user-visible pre-defined styles, like "Default
> > Paragraph Style" (which has internal name of "Standard").
> 
> Can you clarify the difference between (2.) and (3.)? Is (3.) outside of the
> current document? Is it in the default template, if one exists?

No, (3) is about several  in the current document. The only thing outside the
document is #1 (User defaults stored in registrymodifications.xcu).

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

[Libreoffice-bugs] [Bug 152308] Crop Dialog is unavailable in Writer and Calc

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

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 142971] LibreOffice crashes if I click or mouseover on the toolbar

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

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

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

[Libreoffice-bugs] [Bug 142971] LibreOffice crashes if I click or mouseover on the toolbar

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

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 152362] the global menu is often not shown

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

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 149136] MAILMERGE : Database not updating for email mailmerge

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

--- Comment #11 from QA Administrators  ---
Dear Thierry Munoz,

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 148919] [FORMATTING] Changing paragraph style tab option does not take or save

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

--- Comment #4 from QA Administrators  ---
Dear Emily Bowman,

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 149177] Formatting (I want an option clearly stated: "Turn off formatting")

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

--- Comment #4 from QA Administrators  ---
Dear Anthony Judge,

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 149177] Formatting (I want an option clearly stated: "Turn off formatting")

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

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 148919] [FORMATTING] Changing paragraph style tab option does not take or save

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

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 144233] something(row-height above 2.00 ?) prevents embedded objects from being re-positioned properly on sheet

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

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

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 144233] something(row-height above 2.00 ?) prevents embedded objects from being re-positioned properly on sheet

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

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 143986] In slideshow mode, when we go to the next slide, horizontal bands flicker across the screen

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

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 143986] In slideshow mode, when we go to the next slide, horizontal bands flicker across the screen

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

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

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 144015] In Calc secondary X axis position is referring to primary Y axis

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

--- Comment #3 from QA Administrators  ---
Dear Greg,

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 144015] In Calc secondary X axis position is referring to primary Y axis

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

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 140493] The Contents of the Combo Box or List Field could not be determined

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

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 138984] Information missing due to footnote and line spacing in LibreOffice

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

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

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 140493] The Contents of the Combo Box or List Field could not be determined

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

--- Comment #4 from QA Administrators  ---
Dear Veridical Angel,

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 149634] Unable to open .vsdx drawing

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

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

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 106952] Update cell style can bypass cell protection

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

--- Comment #7 from QA Administrators  ---
Dear Jean-Sebastien Bevilacqua,

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 112687] Presentation annotations are saved with way too many points

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

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

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 88484] Sample text in font name combobox doesn't display

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

Rajasekaran Karunanithi  changed:

   What|Removed |Added

 CC||rajasekara...@gmail.com

--- Comment #6 from Rajasekaran Karunanithi  ---
Still presents in LO 7.5 Dev under Windows 10(x64).

Version: 7.5.0.0.alpha1 (X86_64) / LibreOffice Community
Build ID: 2b4d136b65bc79a1248876160e85fab79d52d5d6
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-IN (en_IN); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 124603] Automatic spell check of edited word is made after another word edit starts

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

--- Comment #15 from László Németh  ---
(In reply to Gabriel Masei from comment #12)
> Thanks Laszlo for your fix! I've tested it by building the master branch and
> running locally and it works.
> 
> However, I think that the solution is incomplete. The state of the word is
> changed only if the user presses the up or down keys. This is good but not
> enough. The issue still manifests if the user performs any other actions
> (like left/right keys or mouse to change the cursor position or perform a
> different action, Ctrl + S to save the document, mouse to navigate through
> menu for choosing an option, ...). I think that the update of the word state
> should be done after any other action beside editing the word. Maybe we
> should update the state at "leave the current word" event, if this event is
> available. Or to update the word after any action from the user. I don't
> know if the last suggestion is feasible as it could slow the editing but, on
> the other hand, this will include all cases.

@Gabriel: you are right, this solves only the most annoying part of the
problem: replacing the mandatory editing with a more comfortable solution. The
other part of the problem was filed in Bug 136294. (Likely it's worth to
separate the online task (where we don't like the false alarms, which could
cause extra network load) from the desktop functionality.) Many thanks for your
bug report and feedback!

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

[Libreoffice-bugs] [Bug 145988] macOS skia: colors not displayed correctly for all document previews e.g. start center or impress templates

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

--- Comment #52 from خالد حسني  ---
(In reply to Patrick Luby from comment #51)
> I have another possible fix. Would anyone be able to try building
> LibreOffice with the following patch?:
> 
> https://gerrit.libreoffice.org/c/core/+/144387
> 
> Does the above patch change anything? Even if it does not fix this bug, is
> the color shift different in any way? Any details are much appreciated.
> 
> This patch enables 32 bit Skia bitmaps. Internally, LibreOffice uses 24 bit
> bitmaps (I think it is an old Windows limitation) but on macOS, 32 bit
> bitmaps are well supported. Switching to 32 bit Skia bitmaps may cause other
> problems (Luboš Luňák has left many comments about why 24 bit Skia bitmaps
> are used instead of 32 bits), but at least this patch will tell us if
> 24-to-32 bit or 32-to-24 bit conversions are the cause of this bug.

It makes no difference for me.

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

[Libreoffice-bugs] [Bug 95315] Add in preset styles for essays/papers such as MLA (writer)

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

--- Comment #8 from Bertha  ---
I have difficulties with the writing part of any project. For example, when the
time comes to create a text, I am stressed about its correctness, structure,
and compliance with the required parameters. Fortunately, a help service saves
my success. I am about http://essaypapers.reviews/ because this is the source I
trust the most. Their academic experts are reliable. So, I ask them to buy
dissertation and receive support when I get any writing assignment because
pupils and students need such encouragement for doing their best for their
studies.

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

[Libreoffice-bugs] [Bug 152550] Drop the "Basic Fonts" option dialogs

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

--- Comment #3 from Eyal Rozenberg  ---
(In reply to Mike Kaganski from comment #1)
> There is no "default document template" at all, until you define it manually
> - e.g. in Templates section of the Start Center.

Really? So, the template named "Default" isn't the default? And - can I select
one of the templates as the default, then? I don't see any UI for that.

> When no template is made
> the default, LibreOffice uses some settings set in user preferences (like
> the "Basic Fonts" discussed here, *one of* the functions of which is setting
> this global user preference, or the user's locale, which defines the page
> size). If those settings are not set (or even are impossible to set without
> templates, which is true for most of the numerous document settings), some
> hard-coded program defaults are used.

So, what's your opinion about this state of affairs? As opposed to, say, there
_always_ being a default template in the user's profile (and if it's missing,
one is generated when the module comes up, from hard-code values or from a
default-of-default-templates that's not in the user's profile)

> I agree that the settings discussed here are very problematic. These
> settings control these things:
> 
> 1. User defaults stored in registrymodifications.xcu, used for new documents
> created when no default template is set:
>
> 2.  element in
> the current document;
> 3. Properties of *some* user-visible pre-defined styles, like "Default
> Paragraph Style" (which has internal name of "Standard").

Can you clarify the difference between (2.) and (3.)? Is (3.) outside of the
current document? Is it in the default template, if one exists?

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

[Libreoffice-bugs] [Bug 138587] Using the navigator upsets optimal zoom setting

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

--- Comment #3 from Jim Raykowski  ---
@Matt and Dieter, Nice attention to detail catch and explanation of what works
and doesn't.

I couldn't repro the shift right for Frames and Footnotes. Maybe the document
tested with has these in a right to left paragraph?

Effort to fix the issue for Headings and Drawing objects is here:
https://gerrit.libreoffice.org/c/core/+/144392

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

[Libreoffice-bugs] [Bug 139322] [UI] Can not change the focus to Manage Names dialog with the keyboard

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

--- Comment #8 from Tammy  ---
This is reproducible with:

Version: 7.4.2.3 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

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

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

[Libreoffice-bugs] [Bug 137010] Calc autocorrect capitalizes first letter when adding punctuation to a word followed by a number

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

--- Comment #8 from Tammy  ---
- Verified that this is still happening when typing city#1 in the cell, and it
capitalizes City#1. 
- Verified by using various symbols such as: !, &, or -. 
-Verified that this is still happening when pressing enter, selecting the tab
key, or even selecting the up or down arrow, it still capitalizes. 
-Verified by selecting 
-Verified by navigating to Tools > AutoCorrect Options > Options and unchecking
the option "Capitalize the first letter of every sentence" which seems to stop
it

It appears that it capitalizes on complete words. When I tried c#ity#1, it
stays in lowercase even if the user presses enter, selects the tab key, or uses
the up or down arrow. 


Version: 7.4.2.3 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

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

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

[Libreoffice-bugs] [Bug 152572] fall of writer

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

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Please 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 152560] Consistent appearance of dropdowns and Application Colors background

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

Buovjaga  changed:

   What|Removed |Added

   Keywords||needsUXEval
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Libreoffice-bugs] [Bug 145988] macOS skia: colors not displayed correctly for all document previews e.g. start center or impress templates

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

--- Comment #51 from Patrick Luby  ---
I have another possible fix. Would anyone be able to try building LibreOffice
with the following patch?:

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

Does the above patch change anything? Even if it does not fix this bug, is the
color shift different in any way? Any details are much appreciated.

This patch enables 32 bit Skia bitmaps. Internally, LibreOffice uses 24 bit
bitmaps (I think it is an old Windows limitation) but on macOS, 32 bit bitmaps
are well supported. Switching to 32 bit Skia bitmaps may cause other problems
(Luboš Luňák has left many comments about why 24 bit Skia bitmaps are used
instead of 32 bits), but at least this patch will tell us if 24-to-32 bit or
32-to-24 bit conversions are the cause of this bug.

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

[Libreoffice-bugs] [Bug 152516] Crash pressing edit table in Base

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

Telesto  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEEDINFO|RESOLVED

--- Comment #5 from Telesto  ---
> It might be already fixed with
> https://cgit.freedesktop.org/libreoffice/core/commit/
> ?id=0390479ccf454cd87997fe97d640caf9f8c45a13
> 
> Could you try with a build including this patch?

Indeed
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 8635c9aa8c6f1078a9e220076d5a08daf30077e8
CPU threads: 8; OS: Mac OS X 12.3.1; UI render: default; 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 152538] Content of tables isn't shown

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

--- Comment #7 from Telesto  ---
Looking OK now, ..
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 8635c9aa8c6f1078a9e220076d5a08daf30077e8
CPU threads: 8; OS: Mac OS X 12.3.1; UI render: default; 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 106179] [META] Writer comment bugs and enhancements

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||152573


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152573
[Bug 152573] "Comments in margin" for PDF export results in blank PDF if cursor
is inside a comment
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||152573


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152573
[Bug 152573] "Comments in margin" for PDF export results in blank PDF if cursor
is inside a comment
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152573] New: "Comments in margin" for PDF export results in blank PDF if cursor is inside a comment

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

Bug ID: 152573
   Summary: "Comments in margin" for PDF export results in blank
PDF if cursor is inside a comment
   Product: LibreOffice
   Version: 7.5.0.0 beta1+
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Keywords: filter:pdf
  Severity: normal
  Priority: high
 Component: Printing and PDF export
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: stephane.guil...@libreoffice.org
Blocks: 103378, 106179

Since LO 7.5, we can include comments in the margin of a PDF export using the
GUI (see bug 77650). If the cursor is in a comment, and the PDF export dialog
is used, the resulting PDF is one single blank page.

Steps:
1. Open attachment 184179
2. Click inside one of the comments
3. File > Export as > Export as PDF
4. Tick option "Comments in margin"
5. Click "Export"

Result:
PDF is one blank page.

Interestingly, using "Export directly as PDF" (or the PDF toolbar button) uses
the same settings (I think?) but does export the PDF properly.

High priority as PDF export is a very central feature of Writer, and the
resulting PDF is useless.

Version: 7.5.0.0.beta1 (X86_64) / LibreOffice Community
Build ID: 3aca23eec42e9d6fbe57071d7633ae1fc4bc5fcc
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs

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

Bug 151627 Summary: Skia rendering (both Vulkan and raster) artifacts in the sd 
slidesorter, crashes with Vulkan
https://bugs.documentfoundation.org/show_bug.cgi?id=151627

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|NOTOURBUG   |---

-- 
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-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152560

--- Comment #5 from lostbits  ---
that's correct:
[1] In dark mode the default for dropdowns should be in dark mode.
[2] In light mode the default for dropdowns should be in light mode.
[3] In any mode an option should be available for dropdowns.
[4] For customized appplication colors an option should be available to
colorize the dropdowns.

The current dropdown application colors is light mode in all cases. That is
without regard to the Application Colors used for input, dropdowns always use
light mode, that is, the same Application Colors used when Application Colors
are LibreOffice (Light) (Tools->Options->Application Colors->LibreOffice).

I hope that this is clear. If not please indicate what I need to provide so
that you have an understanding of the intent of this request. I don't know what
additional material I can present, but I will try to present something.

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

[Libreoffice-bugs] [Bug 152572] New: fall of writer

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

Bug ID: 152572
   Summary: fall of writer
   Product: LibreOffice
   Version: 7.4.3.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ondrejn...@gmail.com

Description:
writter falls while scrolling either while using a wheel on the mouse, either
using a slider on the right side

Steps to Reproduce:
open a document
try tto scroll it
it fels

Actual Results:
falling

Expected Results:
stay open :-)


Reproducible: Sometimes


User Profile Reset: No

Additional Info:
Version: 7.3.7.2 (x64) / LibreOffice Community
Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f
CPU threads: 6; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win
Locale: cs-CZ (cs_CZ); UI: cs-CZ
Calc: threaded

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

[Libreoffice-bugs] [Bug 152539] How to speak English fluently?

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

Buovjaga  changed:

   What|Removed |Added

  Component|General |deletionRequest
Version|1.0.1   |unspecified
Product|Impress Remote  |LibreOffice

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

[Libreoffice-bugs] [Bug 152571] New: Very slow save

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

Bug ID: 152571
   Summary: Very slow save
   Product: LibreOffice
   Version: 7.5.0.0 beta1+
  Hardware: ARM
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@commonsnews.org

Description:
Noticeably slower performance while opening and saving simple Writer files.
Disk icon turns red, screen pretty much freezes. Progress wheel starts whirling
just long enough to make me think it's frozen.

Steps to Reproduce:
1. Change your file
2. Hit command-s to save.

or 1. Open file.


Actual Results:
Slow performance as described above.

Expected Results:
In previous versions of Writer, saving simple files locally on the same fast
drives was virtually instantaneous.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Mac OS 12.6.1
OS is 64bit: (I believe it is, right?)

Version: 7.5.0.0.beta1 (AARCH64) / LibreOffice Community
Build ID: 3aca23eec42e9d6fbe57071d7633ae1fc4bc5fcc
CPU threads: 8; OS: Mac OS X 12.6.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 152538] Content of tables isn't shown

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

--- Comment #6 from Julien Nabet  ---
(In reply to Robert Großkopf from comment #5)
> ...
> I don't know where to get a version, which has included the commit and won't
> be LO 7.6.

About daily build, I suppose it's because the creation of 7.5 branch is quite
recent.
Now this patch is in 7.5.0 RC1 which will be released in a few days (according
to https://wiki.documentfoundation.org/ReleasePlan/7.5) so just a bit of
patience here :-)

-- 
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-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128233

--- Comment #83 from Patrick Luby  ---
(In reply to Sierk Bornemann from comment #82)
> +1
> 
> See also the unfortunately closed (why?) bug 89657 and the comments and
> discussion there. The whole situation is still unacceptable and actually
> unreasonable, especially for the average user. We can do better.

Just to be clear, I have no special influence on this topic. I am just a
volunteer here like everybody else so I don't want to pretend that I have any
idea what technical and manpower limits TDF release engineering staff face. TDF
release engineering would likely be the people who will implement any solution
to this bug so I will trust their judgement as whether my proposal is feasible
or not for LibreOffice.

@Telesto had asked if I had any experience with this sort of problem. For
NeoOffice, even back in 2013 when we first put it in the Mac App Store, paying
the cost of increased bandwidth was a no brainer as we had limited time. Plus,
since the Mac App Store required one big, complete application, it was easier
to just do the same type of installer for our non-Mac App Store builds. Maybe
it is the same situation for LibreOffice, maybe not. I don't know.

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

[Libreoffice-bugs] [Bug 151290] A language must not be a feature of a character/paragraph style

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

BogdanB  changed:

   What|Removed |Added

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

--- Comment #5 from BogdanB  ---
(In reply to Panos Stokas from comment #4)
> I like having the ability to set language to None on certain styles.
> 
> For example, the style I'm using for programming code is set to
> Language=none because I want it to be exempt from spelling checks.
> 
> Some styles may have a decorative purpose (eg. those based on Symbol or
> Wingdings characters) which again benefit from setting language=none.
> 
> However I can't think of a scenario where I would set a specific language to
> a style. As Eyal Rozenberg points, language is really part of the content.

You CAN already to set the Language to NONE to any style you need.

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

[Libreoffice-bugs] [Bug 152539] How to speak English fluently?

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

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
 CC||79045_79...@mail.ru

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

[Libreoffice-bugs] [Bug 152564] Allow users to delete default templates

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

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from BogdanB  ---


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

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

[Libreoffice-bugs] [Bug 94461] Predefined Templates and Template Folders are not Deletable in Template Manager

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

BogdanB  changed:

   What|Removed |Added

 CC||celian.godefr...@kalytis.gg

--- Comment #16 from BogdanB  ---
*** Bug 152564 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 152569] boost 1.81 breaks building libetonyek

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

Buovjaga  changed:

   What|Removed |Added

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

--- Comment #2 from Buovjaga  ---
Build errors should go to dev list
https://lists.freedesktop.org/mailman/listinfo/libreoffice

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

[Libreoffice-bugs] [Bug 152570] Navigate instructions for using Open in LibreOffice Help

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

BogdanB  changed:

   What|Removed |Added

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

--- Comment #1 from BogdanB  ---
I was testing all of them just on Linux.

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

[Libreoffice-bugs] [Bug 152570] New: Navigate instructions for using Open in LibreOffice Help

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

Bug ID: 152570
   Summary: Navigate instructions for using Open in LibreOffice
Help
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Documentation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: buzea.bog...@libreoffice.org
CC: olivier.hal...@libreoffice.org

Description:
On this page, at subtitle "File name" point 2.

We have this text:
"Use the Right Arrow key to also display an existing subdirectory in the URL
field." but this is working with Enter, not Right Arrow. If someone can test it
to be sure that I am correct. Maybe depends of OS: Windows/Linux.

Also we have this text:
"Quick AutoComplete is available if you press the End key after entering part
of the URL." but this is working with Down Arrow, not with End. Again, if
someone can test it to be sure that I am correct. Maybe depends of OS:
Windows/Linux.

https://help.libreoffice.org/7.6/en-US/text/shared/01/0102.html?DbPAR=WRITER#bm_id3149687

Steps to Reproduce:
-

Actual Results:
See description

Expected Results:
See description


Reproducible: Always


User Profile Reset: No

Additional Info:
-

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

[Libreoffice-bugs] [Bug 152567] macOS: LibreOffice freezes 30 seconds until popup granting access to certain folder (like documents) appears

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

--- Comment #1 from Sierk Bornemann  ---
I cannot confirm the issue in question – the granting access dialog appears
instantely without a 30 seconds delay.

Version: 7.6.0.0.alpha0+ (AARCH64) / LibreOffice Community
Build ID: 8635c9aa8c6f1078a9e220076d5a08daf30077e8
CPU threads: 10; OS: Mac OS X 13.1; UI render: Skia/Metal; VCL: osx
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

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

[Libreoffice-bugs] [Bug 144548] Could not find Help page for "Add Table or Query"

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

--- Comment #8 from Alain Romedenne  ---
https://wiki.documentfoundation.org/Documentation/Understanding,_Authoring_and_Editing_Openoffice.org_Help/4#Determining_A_Help_ID
wiki content can help identify helpIDs in order to scrutinize help source for
missing pages or missing HID links

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

[Libreoffice-bugs] [Bug 152569] boost 1.81 breaks building libetonyek

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

e...@linuxmail.org changed:

   What|Removed |Added

 CC||e...@linuxmail.org

--- Comment #1 from e...@linuxmail.org ---
Created attachment 184209
  --> https://bugs.documentfoundation.org/attachment.cgi?id=184209=edit
Build errors when compiling Libreoffice against Boost 1.81

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

[Libreoffice-bugs] [Bug 99746] [META] PDF import filter in Draw

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

Bug 131022 Summary: libreoffice draw cant read or show arabic language properly
https://bugs.documentfoundation.org/show_bug.cgi?id=131022

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving

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

خالد حسني  changed:

   What|Removed |Added

 CC||te...@danwin1210.me

--- Comment #112 from خالد حسني  ---
*** Bug 131022 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 131022] libreoffice draw cant read or show arabic language properly

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

خالد حسني  changed:

   What|Removed |Added

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

--- Comment #5 from خالد حسني  ---


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

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

[Libreoffice-bugs] [Bug 152569] New: boost 1.81 breaks building libetonyek

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

Bug ID: 152569
   Summary: boost 1.81 breaks building libetonyek
   Product: LibreOffice
   Version: unspecified
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: e...@linuxmail.org

Description:
Boost 1.81 has been released, but libetonyek cannot be built against Boost
1.81.

Compilation fails with a whole bunch of duplicate symbol errors and libreoffice
compilation cannot proceed.

Steps to Reproduce:
1. Have Boost 1.81 present on the system
2. Build Libreoffice with ---with-system-boost, making sure that the
configuration script points to Boost 1.81
3. Build error about duplicate symbols occur.

Actual Results:
A whole bunch of errors about duplicate symbols appear

Expected Results:
The build process should have proceeded with no errors.


Reproducible: Always


User Profile Reset: No

Additional Info:
This does NOT happen with Boost 1.80.

OpenSUSE Tumbleweed maintainers has also confirmed that Boost 1.81 breaks
libetonyek:
https://dominique.leuenberger.net/blog/2022/12/opensuse-tumbleweed-review-of-the-week-2022-50/

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

[Libreoffice-bugs] [Bug 152568] New: Help page is using old icons for LibreOffice documents

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

Bug ID: 152568
   Summary: Help page is using old icons for LibreOffice documents
   Product: LibreOffice
   Version: 7.5.0.0 beta1+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Documentation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: buzea.bog...@libreoffice.org
CC: olivier.hal...@libreoffice.org

Description:
Icons from this page use old icons.
https://help.libreoffice.org/7.5/en-US/text/shared/01/0101.html?=WRITER=UNIX

Steps to Reproduce:
See description


Actual Results:
Old icons

Expected Results:
New nices icons


Reproducible: Always


User Profile Reset: No

Additional Info:
-

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

[Libreoffice-bugs] [Bug 89657] The lang-pack installation mechanism on OS X unacceptable -- needs refactoring for better installation UX

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

Sierk Bornemann  changed:

   What|Removed |Added

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

-- 
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-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128233

Sierk Bornemann  changed:

   What|Removed |Added

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

--- Comment #82 from Sierk Bornemann  ---
(In reply to Patrick Luby from comment #80)
> (In reply to Telesto from comment #79)
> > @Patrick
> > Another lovely bug. 24 duplicates, 40 people in CC. You likely tackled this
> > problem before..
> 
> If you want my opinion, there is one simple solution: ship all languages in
> the main download. I started doing that with NeoOffice a decade ago. It is
> how applications are normally shipped in the Mac App Store.
> 
> I assume this whole language pack was a quick hack to reduce TDF's bandwidth
> usage. I also assume this is one of the reasons that TDF doesn't ship a
> Universal installer and macOS Silicon users get the Intel version by default
> (all macOS browsers have frozen their user agent strings to macOS 10.5 Intel
> so TDF's download website is broken in its current form). 
> 
> I understand why these hacks came about. A decade ago, bandwidth was much
> more expensive than it is now and macOS didn't have any no digital signing,
> notarization, sandboxing, or hardened runtime. But times have changed, TDF
> has lots of mirrors and bandwidth is significantly cheaper than then.
> 
> So my only question about this bug is why hasn't TDF just switched macOS to
> a single installer? Is it increased bandwidth cost too much? If so, how much
> is that increased cost?

+1

See also the unfortunately closed (why?) bug 89657 and the comments and
discussion there. The whole situation is still unacceptable and actually
unreasonable, especially for the average user. We can do better.

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

[Libreoffice-bugs] [Bug 65535] Correcting a misspelled word with a comment in the middle erases the comment (see comment 38)

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

László Németh  changed:

   What|Removed |Added

 CC||nem...@numbertext.org
 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |nem...@numbertext.org
   |desktop.org |

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

[Libreoffice-bugs] [Bug 152538] Content of tables isn't shown

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

--- Comment #5 from Robert Großkopf  ---
(In reply to Julien Nabet from comment #4)
> Could you give a try with a build which includes this commit:
> https://cgit.freedesktop.org/libreoffice/core/commit/
> ?id=0390479ccf454cd87997fe97d640caf9f8c45a13
> ?

I can't test it with any version of LO 7.5, see comment 2:
Problem: Can't test it for LO 7.5, because there is no daily master available
for LO 7.5 at all …
Only daily builds for 7.6 and 7.4 are available.

I don't know where to get a version, which has included the commit and won't be
LO 7.6.

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

[Libreoffice-bugs] [Bug 152552] When placing line numbering on the right, numbers are left-aligned

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

Rainer Bielefeld Retired  changed:

   What|Removed |Added

Version|7.5.0.0 beta1+  |Inherited From OOo

--- Comment #2 from Rainer Bielefeld Retired  
---
a) Already visible in OOo 3.2.0

b) No Obvious DUPs found with query


c) Bug or Feature? SoftMaker 'TextMaker' does it the same way. Line numbers at
the right are left aligned. But I can't see any sense in that formatting.

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

[Libreoffice-bugs] [Bug 146532] Updating DDE links should dirty the document

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

Buovjaga  changed:

   What|Removed |Added

   Severity|normal  |minor
   Priority|medium  |low
 CC||ilmari.lauhakangas@libreoff
   ||ice.org
 Status|UNCONFIRMED |NEW
Summary|Linking objects from Calc   |Updating DDE links should
   |to Write in DDE mode.   |dirty the document
 Ever confirmed|0   |1

--- Comment #4 from Buovjaga  ---
(In reply to gmarco from comment #0)
> a) if the document has not been further edited (changes to the actual text),
> the closure takes place without saving (and this without even a warning)
> losing the upgrades.

Repro from scratch. Changed summary to reflect this better.

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9b46020c262045aed0beace4708565235c2523cc
CPU threads: 2; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: fi-FI (fi_FI); UI: en-US
Calc: threaded Jumbo

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

[Libreoffice-bugs] [Bug 45949] SPELL check does not work for words with hyperlink

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

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:7.6.0|target:7.6.0
   ||target:7.5.0.0.beta2

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

[Libreoffice-bugs] [Bug 152552] When placing line numbering on the right, numbers are left-aligned

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

Rainer Bielefeld Retired  changed:

   What|Removed |Added

 CC||LibreOffice@bielefeldundbus
   ||s.de

--- Comment #1 from Rainer Bielefeld Retired  
---
Not a new effect, already reproducible with Version 4.0.0.3 (Build ID:
7545bee9c2a0782548772a21bc84a9dcc583b89)

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

[Libreoffice-bugs] [Bug 124603] Automatic spell check of edited word is made after another word edit starts

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

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:7.5.0 target:7.4.3   |target:7.5.0 target:7.4.3
   |inReleaseNotes:7.5  |inReleaseNotes:7.5
   |target:7.6.0|target:7.6.0
   ||target:7.5.0.0.beta2

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

[Libreoffice-bugs] [Bug 152563] Bold text from variable fonts not transcripted in PDF or in printing

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

خالد حسني  changed:

   What|Removed |Added

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

--- Comment #1 from خالد حسني  ---


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

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

[Libreoffice-bugs] [Bug 152567] New: macOS: LibreOffice freezes 30 seconds until popup granting access to certain folder (like documents) appears

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

Bug ID: 152567
   Summary: macOS: LibreOffice freezes 30 seconds until popup
granting access to certain folder (like documents)
appears
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tele...@surfxs.nl

Description:
macOS: LibreOffice freezes 30 seconds until popup granting access to certain
folder (like documents) appears

Steps to Reproduce:
1. Download LibreOffice Master
2. Launch LibreOffice (start center)
3. Launch Writer
4. Press Save -> wait, wait.. granting access dialog appears

Actual Results:
stuck 30 seconds until a dialog appears

Expected Results:
the 30 seconds delay probably unneeded


Reproducible: Always


User Profile Reset: No

Additional Info:
.

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

[Libreoffice-bugs] [Bug 142446] In folding outlines, enable specifying, document-wide, the level to which text should be collapsed.

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

--- Comment #23 from j.a.sw...@gmail.com ---
(In reply to Jim Raykowski from comment #22)

My apologies for being slow to respond. 

> (In reply to j.a.swami from comment #20)
> > 2. When I issue a command that content should be expanded to more levels,
> > the system sometimes responds a bit slowly. The lag is long enough to create
> > uncertainty as to whether the command has been recognized or not.
> Yes, for large files there can be significant delay when a large amount of
> layout frames need to be remade. Are you testing with a full debug build or
> perhaps a container version? These will have slower layout. 

I'm testing with an appimage. The document I tested with is only a page or so,
and text only.

>  
> > 3. It seems that specifying a content level greater than 3 has an
> > inconsistent effect. Sometimes specifying "4" shows me level 4, sometimes
> > not.
> I haven't been able to repro this. Could you supply the steps to repro and
> attach a test file that this happens?  

I've been otherwise occupied, so I haven't tested further. Will try.

>  
> > 4. When content is collapsed to a certain level, I would have expected to
> > see the "no-level" content beneath that level collapsed, consistently.
> > Instead, it seems, such content is always shown, unless already collapsed
> > manually with "toggle outline folding." This seems to me a less-desirable
> > approach. 
> >
> > Imagine, for example, that I have a several-page hieararchical document,
> > with some of the "no-level content" extending for several paragraphs (or
> > even pages). Using "Show outline content to level" may or may not show me
> > the actual bare-bones outline, depending on what I've previously done.
> > 
> > If I have previously collapsed some NL content but not all, expanding or
> > contracting the outline will show me that NL content accordingly, in a
> > manner that would seem to me inconsistent. That is, it would be consistent
> > with my previous actions but inconsistent with what I'm now trying to do,
> > namely view the whole outline at a certain level.
> But doing this seems like it would make the feature just an on canvas copy
> of what the Navigator Headings already does, which is, shows the actual
> bare-bones outline.

You're right, of course. But there are those of us who hardly use the
Navigator. Either we're not used to it, or we find it confusing, or we just
prefer to work directly on the canvas and not open up another panel. On the
canvas we use "Show outline content to level. . ." So that's where we want to
continue working -- on the canvas itself. 

On the canvas we interact differently with a document than we do with Navigator
Headings. As we fold and unfold things, we see and revise text as we go along,
and so on. And we'd like to have Outline Folding work in a way consistent with
what we'd naturally expect. 

Even if folding "non-level" text were to mean we'd be duplicating something one
could do in Navigator Headers, that seems fine with me. As long as we're not
multiplying extravagantly, we can have two different ways for a user to achieve
something, according to his own preferred way of working. 

In sum: I suggest we're best off having Folding Outlines work in a completely
self-sufficient way, independent of what the Navigator may offer. 

Thank you.

-- 
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 (macOS with native rendering fine with Skia)

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

--- Comment #10 from Telesto  ---
(In reply to Alex Thurgood from comment #9)
> I'm still encountering, difficult to reproduce, black backfill ugliness with
> aarch64, even in 7.5beta, e.g, when scrolling through a Writer document, so
> I'm not getting my hopes up just yet re Skia.

Any change for a screenshot.. It's different bug, if you experiencing those
glitches with Skia Metal (Vulkan On Windows) or Raster (=Software rendering)
enabled. I haven't noticed anything unusual, but I'm limited to Intel based
systems. 

--
Note A:
Skia is already available since 7.3 on macOS, I think. Except it wasn't turned
on by default because off couple of bugs. Skia Raster was pretty much unusable
with bug 145843. 

Note B:
I haven't had much issues with Skia Metal/Vulkan. There is a inverted color
glitch on some macs with Vulkan enabled (still around). And I have seen a
painting issue with Start Center (buttons not visible until hoover over)

Note C:
The black borders you see in this bug is likely some fall-out from a different
transparency handling. Windows GDI rendering similar glitches. 

Note D
My personal preference is focusing on Skia. Same rendering means a bug fixed on
Windows likely fixing the same problem on macOS too. Now the same bug can be
present on different backends.. and well unique macOS keep lingering around :-(
There also some performance gains scrolling/zooming images.

-- 
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-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128233

--- Comment #81 from Alex Thurgood  ---
(In reply to Patrick Luby from comment #80)
> (In reply to Telesto from comment #79)

> So my only question about this bug is why hasn't TDF just switched macOS to
> a single installer? Is it increased bandwidth cost too much? If so, how much
> is that increased cost?

The Appstore version includes a selection of languages (not sure how many) and
does not include outside libs, or any working Java functions (despite the Uno
call entries still being in the menus). 

When TDF started offering LO via the Appstore, it pretty much just adapted the
build script used by Collabora, or at least, so it seems, as the same
bugs/limitations already in Collabora Productivity can be found LO Appstore
version.

For people who use databases at work everyday, the appstore versions, whether
Collabora or TDF, are a crippled disappointment, hence the need to be able to
download a separate TDF DMG version which doesn't have these limitations. I
can't say whether bandwidth considerations are still an issue for these
language "neutral" versions.

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

[Libreoffice-bugs] [Bug 124603] Automatic spell check of edited word is made after another word edit starts

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

--- Comment #13 from Commit Notification 
 ---
László Németh committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/62f0707f6ff1c0dfca67c8e3d7f6d74d1a43db87

tdf#124603 sw: test only if spelling dictionary is available

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 124603] Automatic spell check of edited word is made after another word edit starts

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

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:7.5.0 target:7.4.3   |target:7.5.0 target:7.4.3
   |inReleaseNotes:7.5  |inReleaseNotes:7.5
   ||target:7.6.0

-- 
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 (macOS with native rendering fine with Skia)

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

--- Comment #9 from Alex Thurgood  ---
(In reply to Telesto from comment #8)
>  
> no repro with Skia
> Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community
> Build ID: da3dd48eaf9086f8ab28d6a6655f9a638e51433a
> CPU threads: 8; OS: Mac OS X 12.3.1; UI render: Skia/Raster; VCL: osx
> Locale: nl-NL (nl_NL.UTF-8); UI: en-US
> Calc: threaded
> 
> Skia is set default in a new profile since 7.5; I missed the memo about
> that, but accordingly to Xisco this being the case. The problem will fade
> eventually, I guess


Good to know that the problem appears to have gone with Skia activated in 7.5
alpha and x86-64.

I'm still encountering, difficult to reproduce, black backfill ugliness with
aarch64, even in 7.5beta, e.g, when scrolling through a Writer document, so I'm
not getting my hopes up just yet re Skia.

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

[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable

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

--- Comment #16 from Mibu  ---
(In reply to Stéphane Guillou (stragu) from comment #15)
> In 7.5 beta1:
> 
> Version: 7.5.0.0.beta1 (X86_64) / LibreOffice Community
> Build ID: 3aca23eec42e9d6fbe57071d7633ae1fc4bc5fcc
> CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
> Locale: en-AU (en_AU.UTF-8); UI: en-US
> Calc: threaded
> 
> Still unreliable, slightly different results for me:
> 
> From description:
> - Step 2: cursor in last line of page 3
> - Step 3: cursor at two thirds of page 2
> - Step 4: cursor at the beginning of page 3
> 
> Back in 7.2:
> 
> Version: 7.2.7.2 / LibreOffice Community
> Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2
> CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
> Locale: en-AU (en_AU.UTF-8); UI: en-US
> Calc: threaded
> 
> From description:
> - Step 2: correct position
> - Step 3: correct position
> - Step 4: cursor at beginning of document
> 
> All over the place, but as in comment 13, 7.2.7 seemed to behave less
> erratically.
> 
> Related Bug 146988 (considered to be a regression) saw an attempt at fixing
> it in commit a3d4f7e8fb714aa987c542c8d6c8822a41818701, for version 7.4.0
> 
> Upping the priority because there's 7 duplicates, many related bugs, and it
> affects accessibility.

Thank you for upping the priority!

-- 
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-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152507

Julien Nabet  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

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

[Libreoffice-bugs] [Bug 152538] Content of tables isn't shown

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

Julien Nabet  changed:

   What|Removed |Added

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

--- Comment #4 from Julien Nabet  ---
Could you give a try with a build which includes this commit:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=0390479ccf454cd87997fe97d640caf9f8c45a13
?

-- 
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-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152507

Julien Nabet  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #13 from Julien Nabet  ---
Could you give a try with a build which includes this commit:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=0390479ccf454cd87997fe97d640caf9f8c45a13
?

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

[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs

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

Julien Nabet  changed:

   What|Removed |Added

 Depends on||152559


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=152559
[Bug 152559] Skia - LibreOffice Draw crashed when I zoom in the view of a
diagram
-- 
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-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115590

--- Comment #12 from Regina Henschel  ---
The draw:transform attribute is still ignored in Version: 7.6.0.0.alpha0+
(X86_64) / LibreOffice Community
Build ID: 9b46020c262045aed0beace4708565235c2523cc
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (en_US); UI: en-US
Calc: CL threaded

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

[Libreoffice-bugs] [Bug 129062] [META] Skia library bugs

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

Bug 151627 Summary: "Stains" on Pages Panel in Draw when I enable Skia
https://bugs.documentfoundation.org/show_bug.cgi?id=151627

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |NOTOURBUG

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

[Libreoffice-bugs] [Bug 152565] Skia rendering on macOS prints empty pages

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

Julien Nabet  changed:

   What|Removed |Added

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

--- Comment #1 from Julien Nabet  ---
It's been fixed from LO 7.4.4 which should be released in January 2023 (see
https://wiki.documentfoundation.org/ReleasePlan/7.4)

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

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

[Libreoffice-bugs] [Bug 152247] Automatic translation does not work with our own documentation guides

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

--- Comment #4 from Dieter  ---
Still not possible for me to use that feature

Steps:
1. Tools -> Translate
2. Selected "German" as target language -> OK

Actual result
Error message pops up: "Requested clipboard format is not available."

Expected result
Translation

BTW: Is api-free.deepl.com the correct URL?

-- 
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-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=128233

--- Comment #80 from Patrick Luby  ---
(In reply to Telesto from comment #79)
> @Patrick
> Another lovely bug. 24 duplicates, 40 people in CC. You likely tackled this
> problem before..

If you want my opinion, there is one simple solution: ship all languages in the
main download. I started doing that with NeoOffice a decade ago. It is how
applications are normally shipped in the Mac App Store.

I assume this whole language pack was a quick hack to reduce TDF's bandwidth
usage. I also assume this is one of the reasons that TDF doesn't ship a
Universal installer and macOS Silicon users get the Intel version by default
(all macOS browsers have frozen their user agent strings to macOS 10.5 Intel so
TDF's download website is broken in its current form). 

I understand why these hacks came about. A decade ago, bandwidth was much more
expensive than it is now and macOS didn't have any no digital signing,
notarization, sandboxing, or hardened runtime. But times have changed, TDF has
lots of mirrors and bandwidth is significantly cheaper than then.

So my only question about this bug is why hasn't TDF just switched macOS to a
single installer? Is it increased bandwidth cost too much? If so, how much is
that increased cost?

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

[Libreoffice-bugs] [Bug 146814] Crash in: ScBroadcastAreaSlotMachine::AreaBroadcast(ScRange const &, SfxHintId)

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

Buovjaga  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Buovjaga  ---
Good news: I can get it to crash in 7.2, but no more in 7.4. Closing.

Version: 7.4.3.2 (x64) / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 2; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: fi-FI (fi_FI); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 106831] Can't print #10 envelopes properly and with proper orientation

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

Buovjaga  changed:

   What|Removed |Added

 CC||iea...@ielogical.com

--- Comment #13 from Buovjaga  ---
(In reply to Ian Eales from comment #12)
> 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: en-US (en_US); UI: en-US
> Calc: threaded
> 
> #10 envelope does not print landscape. Preview shows right half of letter
> size page portrait and that it is how printed.
> 
> Brother MFC-5620DW
> 
> This is the first envelope failure ever in OO or LO. Worked fine in 7.3.6

If it worked fine in 7.3, you can pinpoint the exact code commit that caused
it.

https://wiki.documentfoundation.org/QA/Bibisect/Windows

Grab this repo for the research: https://bibisect.libreoffice.org/win64-7.3

As preview already shows it, there is no need to print. But as your issue is a
newer one, you should open a new report when you find the guilty commit.

You can email me, if you need assistance with this, such as a screensharing
session.

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

[Libreoffice-bugs] [Bug 103184] [META] UI theming bugs and enhancements

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

Bug 132398 Summary: Adopt new main application icons
https://bugs.documentfoundation.org/show_bug.cgi?id=132398

   What|Removed |Added

 Status|VERIFIED|REOPENED
 Resolution|FIXED   |---

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

[Libreoffice-bugs] [Bug 42082] [META] Make LibreOffice shine and glow on macOS

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

Bug 132398 Summary: Adopt new main application icons
https://bugs.documentfoundation.org/show_bug.cgi?id=132398

   What|Removed |Added

 Status|VERIFIED|REOPENED
 Resolution|FIXED   |---

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

[Libreoffice-bugs] [Bug 138587] Using the navigator upsets optimal zoom setting

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

Dieter  changed:

   What|Removed |Added

 CC||rayk...@gmail.com
   Priority|medium  |low

--- Comment #2 from Dieter  ---
Still happens in

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

Shift to the left with
- Headings
- Drawing objects

Shift to the right
- Frames
- Footnotes

Works as expected with
- Tables
- Images
- Bookmarks
- OLE objects
- Sections
- Hyperlinks
- References
- Indexes
- Fields

Jim, any ideas?

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

[Libreoffice-bugs] [Bug 146933] Keypress events attached to table control columns in Base no longer responded to (steps in comment 4)

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

Buovjaga  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
Version|7.2.5.2 release |7.1.0.0.alpha0+
 OS|macOS (All) |All
 CC||caol...@redhat.com
Summary|Certain Keypress events in  |Keypress events attached to
   |Base no longer responded to |table control columns in
   ||Base no longer responded to
   ||(steps in comment 4)
 Ever confirmed|0   |1
  Regression By||Caolán McNamara
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=14
   ||3023
   Keywords||bibisected, bisected,
   ||regression

--- Comment #4 from Buovjaga  ---
Ok, now I got it. The regression affects column 2. The multi-line column 1 does
not react even in versions 6.3, 6.4 or 7.0.

Bibisected with linux-64-7.1 to
https://git.libreoffice.org/core/commit/d2f1cd004310b9ea6654d17fddc11cb08e884c90
weld EditControl for browsebox

New steps:

1. Open attachment 177721
2. Double-click TBL form
3. Focus into a cell in column 2 and start typing

An alert should pop up on each key press (or mouse double-click etc.)

-- 
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-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152559

Julien Nabet  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED
   Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr
   |desktop.org |

--- Comment #7 from Julien Nabet  ---
https://gerrit.libreoffice.org/c/core/+/144377

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

[Libreoffice-bugs] [Bug 151627] "Stains" on Pages Panel in Draw when I enable Skia

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

Julien Nabet  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr
   |desktop.org |

--- Comment #9 from Julien Nabet  ---
https://gerrit.libreoffice.org/c/core/+/144377

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

  1   2   >