[Libreoffice-bugs] [Bug 155905] New: Has been crashing on and off for 2 weeks. Randomized, no trigger as far as I can tell. It freezes up, then closes all libre office windows compeltely

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155905

Bug ID: 155905
   Summary: Has been crashing on and off for 2 weeks. Randomized,
no trigger as far as I can tell. It freezes up, then
closes all libre office windows compeltely
   Product: LibreOffice
   Version: 7.5.4.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: imj3jenni...@gmail.com

Description:
The program has been crashing on and off for two weeks. Has been worse this
week. There is no trigger as far as I can tell, it is not consistent, it is
random. Nothing i do seems to trigger it. The window works fine, then, freezes
up. Then all open Libre Office Documents close down suddenly. There is no
spinning circle, no option of, this program has frozen up do you want to force
stop, or wait. 
It froze up before last software update, and after the last software update.
I set the settings to auto save work every minute, so if it crashes before I
can click save i don't lose much work, but it has been very frustrating. I'm
sorry I don't have more details for you than that. 
I am writing a book, so I have libreOffice Open for long periods of time, I
frequently manually save, I'm not sure if it's the fact that the program is
open for a long period of time?  

Steps to Reproduce:
1.Open Libre Office 
2.Use for a long time, Save work, continue happily along way, 
3.Save work final time, close down, go to bed. 

Actual Results:
Use libre office, usually for a longer period of time. The program freezes up,
the mouse moves, but it won't recognize buttons, or any clicks, whether I click
anything or not, it shuts down regardless. So I know I'm not overloading the
program...

Expected Results:
Not frozen up and then promptly shut down after about a minute of frozen time
thus being stupid. 
Expected results? Idk, Worked correctly? 


Reproducible: Sometimes


User Profile Reset: No

Additional Info:
I'm sorry. I don't have good information for a software bug, I am just having
issues and have had issues for a few weeks now, and it seems to be getting
worse. I updated the software, that didn't help. And, don't know what else to
do but file a bug report. It's not consistent, I can't get it to reproduce the
problem at will, it's not something that I can figure out if there's a trigger
or not.
I'm hoping there's something that can be done to fix it. 
I also, have not reset my user profile, I have no idea how to do that... I
googled it to see if it was something I could do, and I can't figure it out.
So, I'm just gonna send it. 
I'm sorry. 
have a good day.

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

[Libreoffice-bugs] [Bug 155812] Open file with many page numbers spend too much time

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155812

--- Comment #5 from Xiaoc <3118049...@qq.com> ---
Anyone who can help?

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

[Libreoffice-bugs] [Bug 155656] Quattro Pro files show textual & column rendering problems, slanted, and overrunning text

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155656

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 155634] Announcement by Orca screen reader 'Contains formula' disappeared in calc 7.5.3 on a cell including a formula.

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155634

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 151616] Text tearing in Writer

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151616

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 151616] Text tearing in Writer

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151616

--- Comment #12 from QA Administrators  ---
Dear Carole Rousseaux,

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 145598] The display of sublevels of chapters in LibreOffice Writer

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145598

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

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 145699] UI: Expanding effects deck puts a the vertical scrollbar above spinboxes and such in draw

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145699

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 145699] UI: Expanding effects deck puts a the vertical scrollbar above spinboxes and such in draw

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145699

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

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 145390] Calc - Planilha não está ordenando por data(Date) corretamente

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145390

--- Comment #5 from QA Administrators  ---
Dear Jacó da Silva,

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 145373] LibreOffice locks up when loading a spreadsheet

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145373

--- Comment #3 from QA Administrators  ---
Dear Earl Dingman,

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 145962] [META] Bugs related to kerning/font spacing (cramped/to width/wiggling)

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145962
Bug 145962 depends on bug 141749, which changed state.

Bug 141749 Summary: Text Tearing, Font Shrinkage, and Line Shifting bug related 
to use of Sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=141749

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 141749] Text Tearing, Font Shrinkage, and Line Shifting bug related to use of Sidebar

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141749

--- Comment #9 from QA Administrators  ---
Dear Eek! A Bug. Kill it!,

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 145962] [META] Bugs related to kerning/font spacing (cramped/to width/wiggling)

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145962
Bug 145962 depends on bug 139296, which changed state.

Bug 139296 Summary: scrolling document canvas down & up can cause a line of 
text to "tear" with loss of registration, it clears when the line moves out of 
view far enough or view passes to a new page
https://bugs.documentfoundation.org/show_bug.cgi?id=139296

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 139296] scrolling document canvas down & up can cause a line of text to "tear" with loss of registration, it clears when the line moves out of view far enough or view passes to

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139296

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 139296] scrolling document canvas down & up can cause a line of text to "tear" with loss of registration, it clears when the line moves out of view far enough or view passes to

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=139296

--- Comment #62 from QA Administrators  ---
Dear Bob,

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 147743] Crash on start

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147743

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

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

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152348

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

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 151747] Libreoffice crashes when selecting menu option

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151747

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

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 145325] Weird behaviour when using custom cell height

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=145325

--- Comment #10 from QA Administrators  ---
Dear Perico Palotes,

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 92064] LO unusable with Tibetan super long paragraphs

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92064

--- Comment #14 from QA Administrators  ---
Dear Elie Roux,

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 89773] Text Boxes based on cells with formulas do not update after pasting new data in cells the formula uses (hard recalc needed)

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=89773

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

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 147554] Changing fonts within an app makes cursor disappear and app won't accept input

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147554

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

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 89621] DOCX margin or paragraph width with tab and space (and with Verdana font?) isn't the same in Word and in Writer (comment 14)

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=89621

--- Comment #16 from QA Administrators  ---
Dear Tom Williams,

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 72079] Adding Fonts for Lao, Thai, and Khmer

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=72079

--- Comment #11 from QA Administrators  ---
Dear Robert M Campbell,

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 142604] FILESAVE DOCX Writer line callouts customization points are incorrect

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142604

--- Comment #4 from QA Administrators  ---
Dear NISZ LibreOffice Team,

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 34538] Writer wraps words wrong on banner size paper

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34538

--- Comment #16 from QA Administrators  ---
Dear rknasc,

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 142898] Roundtrip DOCX: file size increase from 430 KB to 5500 because of font embedding

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142898

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 142238] VIEWING Presentation range influences slideshow playback incorrectly

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=142238

--- Comment #2 from QA Administrators  ---
Dear NISZ LibreOffice Team,

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 135444] FILEOPEN: DOCX: altName from fontTable.xml not applied so font wrong

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135444

--- Comment #6 from QA Administrators  ---
Dear Rhys Young,

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 107476] FILEOPEN: DOC: DOCX: TAB_OVER_MARGIN paragraphs should never wrap

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107476

--- Comment #13 from QA Administrators  ---
Dear Xisco Faulí,

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 155904] docx file is not available in file open?

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155904

--- Comment #2 from jindam, vani  ---
Created attachment 187970
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187970=edit
screenshot libreoffice viewer android docx file is listed file open option

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

[Libreoffice-bugs] [Bug 155904] docx file is not available in file open?

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155904

jindam, vani  changed:

   What|Removed |Added

 CC||jindam.v...@disroot.org

--- Comment #1 from jindam, vani  ---
Created attachment 187969
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187969=edit
screenshot mc [ midnightcommander ] linux docx file is listed

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

[Libreoffice-bugs] [Bug 155904] New: docx file is not available in file open?

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155904

Bug ID: 155904
   Summary: docx file is not available in file open?
   Product: LibreOffice
   Version: 7.5.4.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jindam.v...@disroot.org

Created attachment 187968
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187968=edit
screenshot libreoffice linux docx file is not listed file open option

* .docx filename:
=_UTF-8_Q_=D8=A2=D8=AF=D8=A7=D8=A8_=D8=B1=D8=A7=D8=B2_=D9=88=D9=86=D9=8A_=
=_UTF-8_Q_=D8=A7=D8=B2_=D8=A8=D9=87_=D8=AF=D8=B1.docx

* File is not listed
libreoffice [ linux ] _file open

* File is listed
** libreoffice viewer [ android ]_ select file 
to open
** mc [ linux ]

* Completly lost about how to write 
this issue, please find attached screenshots

* repro
libreoffice: Version: 7.5.4.2 (ARM_EABI) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: x11
Locale: en-US (C); UI: en-US
Calc: threaded
OS: NAME="openSUSE Tumbleweed", VERSION_ID="20230604"

* no repro
libreoffice: f-droid: Version: 7.6.0.0.alpha1+, Build ID: 5c1c768e128d
OS: Android

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

[Libreoffice-bugs] [Bug 155634] Announcement by Orca screen reader 'Contains formula' disappeared in calc 7.5.3 on a cell including a formula.

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155634

ady  changed:

   What|Removed |Added

 Whiteboard||QA:needsComment

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

[Libreoffice-bugs] [Bug 155881] Saving causes consolidate dialog to fill up with garbage ranges

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155881

ady  changed:

   What|Removed |Added

 Blocks||115775


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 115775] [META] Database Range and Consolidate bugs and enhancements

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115775

ady  changed:

   What|Removed |Added

 Depends on||155881


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=155881
[Bug 155881] Saving causes consolidate dialog to fill up with garbage ranges
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155881] Saving causes consolidate dialog to fill up with garbage ranges

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155881

--- Comment #6 from ady  ---
Using a recent Dev version and a file from scratch (taking data from attachment
187945 from comment 2), I am still able to replicate the behavior reported in
this bug 155881. The difference in this case is that, when re-opening the
already-saved file, the additional lines are not 4 but 3 (i.e. offset of -1).
The next times (after each save and reload) the values are similar: 11 lines
instead of 12, 27 lines instead of 28...

In the Consolidate dialog, there are other features that are not working
correctly:
* The field info for Source data cannot be deleted; meaning that after
deletion, closing the dialog and reopening it, the source data lines remain as
before deletion.

* Trying to select an area for Source Data, I cannot use typical keyboard
shortcuts to select an area (e.g. [CTRL]+[HOME], [SHIFT]+[CTRL]+[END],
[SHIFT]+[CTRL]+[arrow keys]); the focus of the cursor remains in the field of
the dialog, so the area can be selected by using the mouse and scrolling).

* Not all the (Row) Head Labels are actually used/seen in the resulting
consolidation area (i.e. "Copy results to:" field).


(In reply to m.a.riosv from comment #5)
> bug 45862

I tried using attachment 56839 from bug 45862, but it doesn't make sense when I
open it: the dialog is set up in order to consolidate data by a SUM of _text_
values. Starting from such situation, I decided not to use it for testing the
Data Consolidation feature.

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

[Libreoffice-bugs] [Bug 154933] Rename "Text body" to "Body text"

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154933

--- Comment #13 from Commit Notification 
 ---
Seth Chaiklin committed a patch related to this issue.
It has been pushed to "libreoffice-7-6":

https://git.libreoffice.org/help/commit/dc45fbe8e459de068be8370757affb486b4aafad

Related tdf#154933  update "Text Body" -> "Body Text"

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

[Libreoffice-bugs] [Bug 122970] Direct cursor leaves screen trail with mouse pointer movement and no text

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=122970

Hossein  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 155902] writer crashes regularly after updating to dark mode

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155902

--- Comment #2 from jim hamilton  ---
My OS is Windows 10 - basically always updated.
Note: I get the crash unexpectedly. It might be two days before it crashes.
I've updated to LibreOffice_7.5.4_Win_x86-64 since filing this bug report and
will see if there is any change.. PS I run a pretty strong computer i7 with
32gb of memory, etc. but I run it pretty hard :)

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

[Libreoffice-bugs] [Bug 146976] Writer Crashes After Opening A Large File of 2000 text pages

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146976

Caolán McNamara  changed:

   What|Removed |Added

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

--- Comment #15 from Caolán McNamara  ---
sounds like the same problem them, running out of windows resource handles

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

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

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092
Bug 133092 depends on bug 146976, which changed state.

Bug 146976 Summary: Writer Crashes After Opening A Large File of 2000 text pages
https://bugs.documentfoundation.org/show_bug.cgi?id=146976

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 155903] Writer: Error opening a .docx file containing audio inserted files

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155903

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #3 from m.a.riosv  ---
Created attachment 187967
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187967=edit
Screenshot error with word.

The file shows an error window opening with word.

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

[Libreoffice-bugs] [Bug 155894] column sum problem left below

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155894

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Maybe a more detailed information, and a step by step with a sample file could
help.

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

[Libreoffice-bugs] [Bug 155881] Saving causes consolidate dialog to fill up with garbage ranges

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155881

m.a.riosv  changed:

   What|Removed |Added

 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #5 from m.a.riosv  ---
But it doesn't happen to me with a file from scratch.
In that case, second ranges are lost.

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

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

[Libreoffice-bugs] [Bug 155903] Writer: Error opening a .docx file containing audio inserted files

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155903

--- Comment #2 from FLS  ---
The same file saved in the native ODF fprmat is OK. It has NO PROBLEM AT ALL.
That means the problem arises when converting the file to the .docx format.
The bug is inside the converter.

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

[Libreoffice-bugs] [Bug 155903] Writer: Error opening a .docx file containing audio inserted files

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155903

--- Comment #1 from FLS  ---
Created attachment 187966
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187966=edit
Sample of a corrupted file

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

[Libreoffice-bugs] [Bug 155903] New: Writer: Error opening a .docx file containing audio inserted files

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155903

Bug ID: 155903
   Summary: Writer: Error opening a .docx file containing audio
inserted files
   Product: LibreOffice
   Version: 7.5.4.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: francois.sal...@laposte.net

Description:
When creating a doc file and saving it in the .docx format, there is no
reported problem to save it.

BUT, after closing the file normally, an error occcurs when attempting to open
it again. The following error message appears:

Detalles del error:
SAXException: [word/document.xml line 2]: Namespace prefix p14 on media is not
defined

Si continúa con la importación, podrían producirse pérdidas o daños de datos y
la aplicación podría volverse inestable o cerrarse inesperadamente.

Going ahead, it imports only the data previous to the first audio embedded
file. The rest is lost.

Steps to Reproduce:
1.Open the file submitted in the attachment
2. Observe the error report
3.

Actual Results:
Always the same error when aopening the file occurs.

Expected Results:
To be able to save doc documents with audio embedded files in the .docx format.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: es
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no

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

[Libreoffice-bugs] [Bug 155902] writer crashes regularly after updating to dark mode

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155902

--- Comment #1 from IvoErMejo  ---
What's your OS?
I tested your bug and inside Linux openSUSE KDE Plasma and Writer 7.5.4.1. I
have no bug.

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

[Libreoffice-bugs] [Bug 155902] New: writer crashes regularly after updating to dark mode

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155902

Bug ID: 155902
   Summary: writer crashes regularly after updating to dark mode
   Product: LibreOffice
   Version: 7.5.3.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jhamil...@coreresonance.com

Description:
I was very excited to update to 7.5.3.2 to access what I believed was a robust
version of Libre Writer so that I could use dark mode.. but find that Libre
Writer crashes regularly. It can crash more than once a day but just today, it
crashed after I went back to the latest article I am writing and crashed
shortly after I started editing. Seems it might crash early in the day of first
using Writer.. Not familiar with any of the other products in Office..
Otherwise, love the software!

Steps to Reproduce:
1.seems it happens after I start my day with Writer.. but likely happens most
any time... More than once a day? Yes.
2. Screen freezes and then Writer crashes
3. restore brings back all documents with a 1min save feature

Actual Results:
This crash has been occurring regularly since updating to 7.5.3.2. I've looked
at release notes for this and later versions and see nothing about crashes
assumedly associated with dark mode.. PS Love dark mode.. Hope you find a
solution soon!

Expected Results:
?


Reproducible: Always


User Profile Reset: No

Additional Info:
did not try resetting my user profile.. Not willing to go into safe mode, etc..

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

[Libreoffice-bugs] [Bug 155901] New: MCGR: Adding gradient to user palette or setting a border changes last stop offset to 1

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155901

Bug ID: 155901
   Summary: MCGR: Adding gradient to user palette or setting a
border changes last stop offset to 1
   Product: LibreOffice
   Version: 24.2.0.0 alpha0+ Master
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rb.hensc...@t-online.de
CC: armin.le.gr...@me.com

Created attachment 187965
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187965=edit
Gradient with last stop at offset 0.69

(1) Open attached document. Select the shape and open Area-dialog from the
context menu of the shape. Click 'Add' button to add the gradient to the user
gradient palette. Enter a name. OK. Notice that the offset of the last color
stop has changed.
Or
(2) Open attached document. Select the shape and open Area-dialog from the
context menu of the shape. Change the value of the 'Transition start' field to
a different value. Click into any other field to update the setting. Notice
that the offset of the last color stop has changed.

The changed offset is already visible in the preview in the dialog.

Hi Armin, do you have a code pointer for me, where this change might happen?

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

[Libreoffice-bugs] [Bug 155900] New: Font color in pdf, created from impress ppt/odp file, is reduced to black for bold text.

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155900

Bug ID: 155900
   Summary: Font color in pdf, created from impress ppt/odp file,
is reduced to black for bold text.
   Product: LibreOffice
   Version: 7.5.3.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ki...@freenet.de

Description:
Exporting Impress slide-show to PDF changes color of bold text from any color
to black (and only for bold text).

Steps to Reproduce:
1. Start Impress
2. Select "Freshes" from Templates
3. Change font color of BOLD text (e.g. the first heading) to a color other
than black via right click → 'Character' → Tab 'Font Effects', e.g. to blue (or
keep the inital white version)
4. Press button "Export directly to PDF"
5. Check font color of the PDF file

Actual Results:
The font color changes to black in the PDF (happens ONLY for BOLD text)

Expected Results:
The PDF should adopt the font color from the impress file


Reproducible: Always


User Profile Reset: No

Additional Info:
Version 7.5.3.2 (X86_64)
CPU threads: 4; OS: Linux 6.3
UI render: default; VCL: gtk3
en-US (en_US.UTF-8); UI:en-US
Calc_threaded

Fedora 38, happens with rpm and Flatpak version

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

[Libreoffice-bugs] [Bug 155898] table in footer is missing on .doc file

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155898

Eike Rathke  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[Libreoffice-bugs] [Bug 155898] table in footer is missing on .doc file

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155898

Eike Rathke  changed:

   What|Removed |Added

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

--- Comment #2 from Eike Rathke  ---


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

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

[Libreoffice-bugs] [Bug 155899] only table in footer is missing on .doc file

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155899

--- Comment #4 from Eike Rathke  ---
*** Bug 155898 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 155896] Libre Calc does not do the PEMDAS functions correctly

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155896

Eike Rathke  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #2 from Eike Rathke  ---
2(7-2) is *NOT* a valid spreadsheet formula expression because it lacks an
operator between 2 and (7-2). Specifically, 20/2(7-2) would never be evaluated
as 20/(2*(7-2)) or 20/2/(7-2) what you seem to expect, not even by a TI
calculator.
Even WolframAlpha agrees that 20/2(7-2) is evaluated as 20/2*(7-2)
https://www.wolframalpha.com/input?i=20%2F2%287-2%29

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

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

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133092
Bug 133092 depends on bug 146626, which changed state.

Bug 146626 Summary: Crash in macOS Calc on font size operation on multi-monitor 
setup
https://bugs.documentfoundation.org/show_bug.cgi?id=146626

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 104160] [META] Bugs and features related to multiple monitor setups

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104160
Bug 104160 depends on bug 146626, which changed state.

Bug 146626 Summary: Crash in macOS Calc on font size operation on multi-monitor 
setup
https://bugs.documentfoundation.org/show_bug.cgi?id=146626

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 155886] Hash marks that indicate "cell too narrow" should expand according to the cell width

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155886

ady  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
   Severity|normal  |enhancement

--- Comment #1 from ady  ---
> Hash marks should expand fill the cell width.

FWIW, I agree... but with a minimum of three # marks, even when the width of
the cell is not enough for all three marks.

If the width of the cell is not enough for all three # marks, then the behavior
should not be modified in comparison to the current one (unless and until
tdf#129847 is implemented, if implemented).

If the width of the cell is enough for more than 3 # marks, then additional #
marks should be displayed in the cell, until the width of the cell is full of #
marks, but not over it.

I am setting this as NEW ENHANCEMENT request, even when there is still
needsUXEval.

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

[Libreoffice-bugs] [Bug 152370] MariaDB direct connection: Access through socket to separate instance of MariaDB impossible

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152370

--- Comment #4 from László Károlyi  ---
Hey,

this is a long standing bug, I can confirm this for ages now. I get the same
error when trying to connect to a local mariadb instance via a unix socket
(non-tcp).

The same error shows:

"Can't connect to server on 'localhost' (111) at
/usr/src/debug/libreoffice-fresh/libreoffice-7.5.3.2/connectivity/source/drivers/mysqlc/mysqlc_general.cxx:120"

It seems to me that using the unix socket is totally ignored, it always wants
to connect via TCP, which my mariadb instance has disabled.

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

[Libreoffice-bugs] [Bug 155896] Libre Calc does not do the PEMDAS functions correctly

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155896

ady  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |NOTABUG

--- Comment #1 from ady  ---
A formula such as:
=20/2(7-2)

...would return Err:509, Operator missing (between the 2 and the parenthesis).

In Calc, the multiplication operator has to be there.

Additionally, there are priorities that are assumed by Calc, which can be
changed by using additional parentheses; for example:
=20/(2*(7-2))

Please search for info in the online help, the user mailing lists, or use
https://ask.libreoffice.org next time before posting a bug report.

Closing as NOTABUG.

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

[Libreoffice-bugs] [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103341
Bug 103341 depends on bug 90507, which changed state.

Bug 90507 Summary: Tools - AutoCorrect - Apply converts non-empty "Default 
Paragraph Style" paragraphs to "Text Body" PS --even when no [M] options are 
selected
https://bugs.documentfoundation.org/show_bug.cgi?id=90507

   What|Removed |Added

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

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

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

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108253
Bug 108253 depends on bug 132026, which changed state.

Bug 132026 Summary: Entering "-" in a cell formatted as text puts Calc into 
formula-entering mode
https://bugs.documentfoundation.org/show_bug.cgi?id=132026

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 155891] Allow blocking cell edit mode unless explicitly allowed (ie. pressing F2) to prevent accidental data manipulation

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155891

--- Comment #1 from freew...@poczta.fm ---
tl;dr I request an option to make it so pressing F2 or ENTER (if enabled in the
general options) is REQUIRED to enter the cell edit mode to enter/modify the
content.

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

[Libreoffice-bugs] [Bug 155891] Allow blocking cell edit mode unless explicitly allowed (ie. pressing F2) to prevent accidental data manipulation

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155891

freew...@poczta.fm changed:

   What|Removed |Added

Summary|Add an option to Block data |Allow blocking cell edit
   |entry unless allowed|mode unless explicitly
   |explicitly by pressing F2   |allowed (ie. pressing F2)
   |to prevent accidental data  |to prevent accidental data
   |manipulation|manipulation

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

[Libreoffice-bugs] [Bug 155891] Add an option to Block data entry unless allowed explicitly by pressing F2 to prevent accidental data manipulation

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155891

freew...@poczta.fm changed:

   What|Removed |Added

Summary|Add an option to DISABLE|Add an option to Block data
   |direct data entry to|entry unless allowed
   |prevent accidental data |explicitly by pressing F2
   |modification|to prevent accidental data
   ||manipulation

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

[Libreoffice-bugs] [Bug 155898] table in footer is missing on .doc file

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155898

jindam, vani  changed:

   What|Removed |Added

 CC||jindam.v...@disroot.org

--- Comment #1 from jindam, vani  ---
there was some error.
i did not bothered to check if this 
issue was created.
unnecassarily created another issue
https://bugs.documentfoundation.org/show_bug.cgi?id=155899

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

[Libreoffice-bugs] [Bug 37259] FORMATTING Define Print Range across filtered rows fails

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=37259

--- Comment #21 from ady  ---
Still present in current Dev build 24.2.

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

[Libreoffice-bugs] [Bug 155899] only table in footer is missing on .doc file

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155899

--- Comment #3 from jindam, vani  ---
Created attachment 187964
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187964=edit
screenshot libreoffice linux only table in footer is missing

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

[Libreoffice-bugs] [Bug 155899] only table in footer is missing on .doc file

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155899

--- Comment #2 from jindam, vani  ---
Created attachment 187963
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187963=edit
screenshot libreoffice viewer android only table in footer is missing

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

[Libreoffice-bugs] [Bug 155899] only table in footer is missing on .doc file

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155899

jindam, vani  changed:

   What|Removed |Added

 CC||jindam.v...@disroot.org

--- Comment #1 from jindam, vani  ---
Created attachment 187962
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187962=edit
screenshot word text & table are visible on footer

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

[Libreoffice-bugs] [Bug 155899] New: only table in footer is missing on .doc file

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155899

Bug ID: 155899
   Summary: only table in footer is missing on .doc file
   Product: LibreOffice
   Version: 7.6.0.0 alpha1+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jindam.v...@disroot.org

Created attachment 187961
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187961=edit
bug doc text & table are visible on footer

* open attachment bugdoc17062023.doc
* on libreoffice viewer & writer, only 
text is visible, table is missing
* on word, both text and table are visible

* repro
libreoffice: f-droid: Version: 7.6.0.0.alpha1+, Build ID: 5c1c768e128d
OS: Android

libreoffice: Version: 7.5.4.2 (ARM_EABI) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: x11
Locale: en-US (C); UI: en-US
Calc: threaded
OS: NAME="openSUSE Tumbleweed", VERSION_ID="20230604"

* no repro
Word: Version: 1.0.1 (16.0.1.16501.20160)
OS: Android

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

[Libreoffice-bugs] [Bug 155898] New: table in footer is missing on .doc file

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155898

Bug ID: 155898
   Summary: table in footer is missing on .doc file
   Product: LibreOffice
   Version: 7.6.0.0 alpha1+
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jindam.v...@disroot.org

Created attachment 187960
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187960=edit
bug doc text & table are visible on footer

* open attachment bugdoc17062023.doc
* on libreoffice viewer & writer, only 
text is visible, table is missing
* on word, both text and table are visible

* repro
libreoffice: f-droid: Version: 7.6.0.0.alpha1+, Build ID: 5c1c768e128d
OS: Android

libreoffice: Version: 7.5.4.2 (ARM_EABI) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: x11
Locale: en-US (C); UI: en-US
Calc: threaded
OS: NAME="openSUSE Tumbleweed", VERSION_ID="20230604"

* no repro
Word: Version: 1.0.1 (16.0.1.16501.20160)
OS: Android

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

[Libreoffice-bugs] [Bug 108827] [META] Calc functions bugs and enhancements

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108827
Bug 108827 depends on bug 155402, which changed state.

Bug 155402 Summary: FILEOPEN XLSX CELL() function gives different value 
compared to Excel with filename parameter
https://bugs.documentfoundation.org/show_bug.cgi?id=155402

   What|Removed |Added

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

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

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

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113499
Bug 113499 depends on bug 153517, which changed state.

Bug 153517 Summary: CALC - wrong time value when using the autofill function 
and minutes are entered (not for 00 min)
https://bugs.documentfoundation.org/show_bug.cgi?id=153517

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 155873] Column not Shown Centered

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155873

jindam, vani  changed:

   What|Removed |Added

 CC||jindam.v...@disroot.org

--- Comment #2 from jindam, vani  ---
when i open .odt file:
* left align: r1,c1; r3,c3; r4,c4; r11,c11
* centered align: r2,c2; r5-10,c5-10

format —> align text: result
* left_ all column1 cells are aligned left
* centered_ except: r1,c1; r3,c3; r4,c4; r11,c11
* right_ except: r1,c1; r3,c3; r4,c4; r11,c11
* justified_ all column1 cells are aligned left

version & os:
libreoffice: Version: 7.5.4.2 (ARM_EABI) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: x11
Locale: en-US (C); UI: en-US
Calc: threaded
OS: NAME="openSUSE Tumbleweed", VERSION_ID="20230604"

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

[Libreoffice-bugs] [Bug 155897] New: Inconsistency concerning the deletion of single empty paragraph below TextTable

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155897

Bug ID: 155897
   Summary: Inconsistency concerning the deletion of single empty
paragraph below TextTable
   Product: LibreOffice
   Version: 3.6.5.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@psilosoph.de

Created attachment 187959
  --> https://bugs.documentfoundation.org/attachment.cgi?id=187959=edit
the little demo announced in the report

Having placed the hair cursor at the end of the last paragraph inside the last
(bottom right) call of a TextTable with empty paragraphs below, Ctrl+Shift+Del
(default shortcut) deletes the next empty paragraph. This is also the case if
the TextTable is content of the text object of a frame.

Since V 3.6.5 this does no longer work if the next empty paragraph is the last
one of the main text of the Writer document. It still works for the case of
frame text objects. 

Till V 3.5.2 the removal worked, but the new state (without a paragraph below
the table) did not persist a Save/Reload cycle. 

IMO this is only annoying if the undeletable or automatically recreated empty
paragraph causes an automatic page break. But obviously this occurs - if even
rarely.

BTW: With the help of user code the final empty paragraph can still be removed.
It will then also be automatically recreated on Reload.

Concerning my statements about the working of user code you may want to
test/play with the attached example.

(Concerning the text objects of TextTable cells containing nested tables there
are additional inconsistencies. At what time and by whom was the related part
of the "architecture" specified?)

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

[Libreoffice-bugs] [Bug 155886] Hash marks that indicate "cell too narrow" should expand according to the cell width

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155886

Buovjaga  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 155812] Open file with many page numbers spend too much time

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155812

Xiaoc <3118049...@qq.com> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

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

[Libreoffice-bugs] [Bug 137067] User interface - Inconsistent fonts in tabbed style (Remote Documents looks out-of-place)

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137067

Justin L  changed:

   What|Removed |Added

Summary|User interface -|User interface -
   |Inconsistent fonts in   |Inconsistent fonts in
   |tabbed style|tabbed style (Remote
   ||Documents looks
   ||out-of-place)

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

[Libreoffice-bugs] [Bug 155896] New: Libre Calc does not do the PEMDAS functions correctly

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155896

Bug ID: 155896
   Summary: Libre Calc does not do the PEMDAS functions correctly
   Product: LibreOffice
   Version: 7.1.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dok...@yahoo.com

Description:
When I type in the following equation "20/2(7-2)" Libre Office changes it to
"20/2X(7-2)". In THIS case, it adds another multiplication function to the
equation. That creates the WRONG answer because it changes the PEMDAS Order. In
PEMDAS, ALL of the Parenthesis's functions MUST be completed, PRIOR to
finishing the equation. 

SO, If you have:
20/2(7-2)=
20/2(5)= (MUST FINISH THE PARENTHESES!!!)
20/10=
2

You do NOT go:
20/2(7-2)=
20/2(5)=
20/2X5= NOT!
so it will NOT go
10X5= WRONG

Actual Results:
20/2(7-2)=
20/2X(7-2)= YOU DO NOT Add a multiplication step to the formula!
20/2X5=
20/2X5= NOT!
so it will NOT go
10X5= WRONG

Expected Results:
20/2(7-2)=
20/2(5)= (MUST FINISH THE PARENTHESES!!!)
20/10=
2



Reproducible: Always


User Profile Reset: No

Additional Info:
I am not sure why, but even when I use Microsoft Scientific Calculator, it puts
in the extra step.

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

[Libreoffice-bugs] [Bug 155875] [LOCALHELP] - Writer - Help pages about dialogs should provide instructions for the Tabbed UI

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155875

--- Comment #3 from Commit Notification 
 ---
Olivier Hallot committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/help/commit/fe8a94e99b738bcfe5f36ac999349f9436ef769d

tdf#155875 Tabbed UI commands Writer in Help pages

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

[Libreoffice-bugs] [Bug 155875] [LOCALHELP] - Writer - Help pages about dialogs should provide instructions for the Tabbed UI

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155875

--- Comment #2 from Commit Notification 
 ---
Olivier Hallot committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/help/commit/77b1451f125ef99c9fb1a017e27f75120d6f1842

tdf#155875 Tabbed UI commands Writer in Help pages

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

[Libreoffice-bugs] [Bug 155875] [LOCALHELP] - Writer - Help pages about dialogs should provide instructions for the Tabbed UI

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155875

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:24.2.0

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

[Libreoffice-bugs] [Bug 155875] [LOCALHELP] - Writer - Help pages about dialogs should provide instructions for the Tabbed UI

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155875

--- Comment #1 from Commit Notification 
 ---
Olivier Hallot committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/help/commit/ea5863372e39437174ea1403ef30092013248df0

tdf#155875 Tabbed UI commands Writer in Help pages

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

[Libreoffice-bugs] [Bug 155881] Saving causes consolidate dialog to fill up with garbage ranges

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155881

--- Comment #4 from dominik1...@live.com ---
Thanks ady for the confirmation of the bug. I've tried to find any reported
cases on this but there were none.

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

[Libreoffice-bugs] [Bug 155662] FILEOPEN RTF Direct formatting leaks through line break

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155662

Dieter  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
 CC||dgp-m...@gmx.de,
   ||vmik...@collabora.com

--- Comment #3 from Dieter  ---
I confirm it with

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 069c7dc4e9706b40ca12d83d83f90f41cec948f8
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 threaded

Miklos, could you have a look at it?

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

[Libreoffice-bugs] [Bug 155663] FILEOPEN RTF Image crop not imported

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155663

Dieter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||dgp-m...@gmx.de
 Ever confirmed|0   |1

--- Comment #2 from Dieter  ---
I confirm it with

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 069c7dc4e9706b40ca12d83d83f90f41cec948f8
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 threaded

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

[Libreoffice-bugs] [Bug 43848] selecting whole table with merged cells at certain position not possible with draging the mouse

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=43848

Dieter  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 107200] [META] Writer table and cell selection issues

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107200

Dieter  changed:

   What|Removed |Added

 Depends on||155670


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=155670
[Bug 155670] Inconsistent table row selection
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155670] Inconsistent table row selection

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155670

Dieter  changed:

   What|Removed |Added

   Keywords||needsUXEval
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=43
   ||848
 Blocks||107200
 CC||dgp-m...@gmx.de,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org

--- Comment #4 from Dieter  ---
Ulrich, I can confirm the behaviour with

Version: 7.5.4.2 (X86_64) / LibreOffice Community
Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6
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 threaded

Steps:
1. Open attachment 187706. Excluding the heading this table contains 12 rows
(in some columns 3 rows have been merged.
2. Place mouse cursor left from table and left from first row and click.
Result: Merged cells are selected and first row
3. Place mouse cusor left from table and left from second row and click.
Nothing happens (Unexpected; My expecation: at least second row should be
selected); same with third row
4. Place cursor left from table and left from fifth row and click. Result:
Fifth rom is selected (O. K. for me)

So I think there is a bug or at least the need for an enhancement
cc: Design-Team for further input and decision about expected result


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107200
[Bug 107200] [META] Writer table and cell selection issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 107200] [META] Writer table and cell selection issues

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107200
Bug 107200 depends on bug 106932, which changed state.

Bug 106932 Summary: Impossible to select with mouse entire table rows when 
vertical Merges are present in the last column (Workaround: Ctrl+Shift+End)
https://bugs.documentfoundation.org/show_bug.cgi?id=106932

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 43848] selecting whole table with merged cells at certain position not possible with draging the mouse

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=43848

Dieter  changed:

   What|Removed |Added

 CC||jim.av...@gmail.com

--- Comment #20 from Dieter  ---
*** Bug 106932 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 106932] Impossible to select with mouse entire table rows when vertical Merges are present in the last column (Workaround: Ctrl+Shift+End)

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106932

Dieter  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED
 CC||dgp-m...@gmx.de

--- Comment #9 from Dieter  ---
Looks like a duplicate of bug 43848.

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

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

[Libreoffice-bugs] [Bug 43848] selecting whole table with merged cells at certain position not possible with draging the mouse

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=43848

Dieter  changed:

   What|Removed |Added

 OS|Linux (All) |All

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

[Libreoffice-bugs] [Bug 43848] selecting whole table with merged cells at certain position not possible with draging the mouse

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=43848

--- Comment #19 from Dieter  ---
Still present in

Version: 7.5.4.2 (X86_64) / LibreOffice Community
Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6
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 threaded

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

[Libreoffice-bugs] [Bug 155792] Text in the cell of a table renders as multiline where as MS word renders in single line

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155792

--- Comment #8 from Justin L  ---
Probably the next step is to see if there are any other bugs affecting cell
size.
-Is it a floating table? No (LO OK).
-Is it relative width? No - 15.89 cm preferred width. (LO OK)
-Spacing left (.31cm) in LO, but not seen in MSO. Removing "fixes" bug.
-assuming this was added due to border width - emulation about positioning?
-perhaps it is irrelevant when position is centred instead of left/right?

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

[Libreoffice-bugs] [Bug 113363] [META] DOCX (OOXML) content control-related issues

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=113363
Bug 113363 depends on bug 155736, which changed state.

Bug 155736 Summary: Fileopen DOCX:Page numbers (from field of course, but 
inside a nested block SDT) are missing in the footer for a particular file
https://bugs.documentfoundation.org/show_bug.cgi?id=155736

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 108799] [META] HTML and XHTML export bugs and enhancements

2023-06-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108799

Dieter  changed:

   What|Removed |Added

 Depends on||155641


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=155641
[Bug 155641] XHTML Export: Writer does not preserve tabs
-- 
You are receiving this mail because:
You are the assignee for the bug.

  1   2   >