[Libreoffice-bugs] [Bug 153131] Copy causes Calc to Freeze on Windows 11

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

--- Comment #56 from Buovjaga  ---
(In reply to Barry L. Kramer from comment #54)
> (In reply to Mike Kaganski from comment #52)
> > 
> > Is that your own build? I haven't found it in our dailies
> 
> 
> No, I don't know how to build it yet. I used the link in one of the comments
> (https://dev-builds.libreoffice.org/daily/master/current.html) and chose
> "Win-x86_64@tb77-TDF  2023-09-15 05:28:33".  I'll try to find a debug
> version.  Do you have a link I should follow?  I would be happy to run it
> again

That's a version *without* debug symbols. The one with debug symbols is
Win-x86@39. It can be used with Windbg per
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg#First_Time_Setup

"Alternatively if you wish to also debug both the standard build and master
build (Win-x86@39 tinderbox), paste the following instead" etc.

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

[Libreoffice-bugs] [Bug 157296] [DESIGN] [WRITER] Icons for unordered and ordered list are not different enough

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

Buovjaga  changed:

   What|Removed |Added

Summary|[DESIGN] [WRITER] unordered |[DESIGN] [WRITER] Icons for
   |and ordered list are not to |unordered and ordered list
   |differentiate   |are not different enough

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

[Libreoffice-bugs] [Bug 157296] [DESIGN] [WRITER] unordered and ordered list are not to differentiate

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

--- Comment #1 from Rizal Muttaqin  ---
Could you please put any capture (please provide with built-in screenshoter not
from another device. :D)

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

[Libreoffice-bugs] [Bug 153131] Copy causes Calc to Freeze on Windows 11

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

--- Comment #55 from Mike Kaganski  ---
(In reply to Barry L. Kramer from comment #54)
> Do you have a link I should follow?  I would be happy to run it again

I would be clad if you create a minidump using any release version - the normal
one, like 7.5.4.2 that you used in comment 44.

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

[Libreoffice-bugs] [Bug 157059] Styles: Spaces are not respected when resizing an image

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

Dieter  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|

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

[Libreoffice-bugs] [Bug 157061] Background of merged paragraphs among styles that share the background

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

Dieter  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|

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

[Libreoffice-bugs] [Bug 157298] Yellow background color overlaps the red color

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

--- Comment #1 from guardao  ---
Created attachment 189661
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189661=edit
Yellow over red

EXAMPLE

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

[Libreoffice-bugs] [Bug 157298] New: Yellow background color overlaps the red color

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

Bug ID: 157298
   Summary: Yellow background color overlaps the red color
   Product: LibreOffice
   Version: 7.5.5.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: guar...@hotmail.com

Description:
The yellow background color goes beyond the left limit of the column and
overlaps the red color

Steps to Reproduce:
1. Fill the bottom of the line with red
2. Fill the bottom of the next column of the same row with yellow
3. BUG - Yellow on Red

Actual Results:
Yellow surpasses column left limit over Red.

Expected Results:
The yellow color must respect the beginning of the column.


Reproducible: Always


User Profile Reset: No

Additional Info:
Yellow background.

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

[Libreoffice-bugs] [Bug 157297] New: LO crashes when start the first time after reboot, or system suspend

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

Bug ID: 157297
   Summary: LO crashes when start the first time after reboot, or
system suspend
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rob...@iafrica.com

Description:
Cal (and Writer) want to send crash report when I open a file first time, but
continues quite happily. Does not happen again until next time.

Steps to Reproduce:
1.start laptop from suspend or reboot
2.open a document
3.dialog to send crash report appears
4.send or cancel


Actual Results:
work continues as normal

Expected Results:
do not understand why crash report dialog appears


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-GB
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes

Version: 7.6.2.0.0+ (X86_64) / LibreOffice Community
Build ID: 235ebd321bb89f0c1c103c4c7ae88f9ddf291a7f
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Calc: threaded

there is no option for this in the version list above

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

[Libreoffice-bugs] [Bug 157064] Allow customization of the bibliographic entry text

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

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 157071] Calc - Hyperlink to hidden sheet bringing to closest un-hidden sheet

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

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 153149] LibreOffice Writer and Calc buttons group is mixed in taskbar of Debian 11.6 KDE

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

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

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 157059] Styles: Spaces are not respected when resizing an image

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

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 157061] Background of merged paragraphs among styles that share the background

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

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 154291] I'm editing a doc. then sudenly the pgm freeze, then quit, no saving of the work pending

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

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

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 153139] Incorrect calculation of times

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

--- Comment #7 from QA Administrators  ---
Dear apprendista.programmatore+Bugzilla,

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 152856] Problem in editing Hindi Text in Writer.

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

--- Comment #9 from QA Administrators  ---
Dear Premdayal Gupta,

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 48814] MAILMERGE to email: Transmission Logfile Output required

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 144296] Under-engineered and inconsistent overflow/extension direction choice incl. with cell edit mode

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

--- Comment #16 from QA Administrators  ---
Dear Eyal Rozenberg,

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 142947] Make menu expander triangles configurable for icon design

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

--- Comment #14 from QA Administrators  ---
Dear Jérôme,

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 134115] "Allow overlap" in current state is not usable in regard to interoperability with Word

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 123263] Array with an element type should not be assignable to a variable of Array with another element type

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

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

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 112418] Calling ImageMagick COM object from macro with more than two parameters results in exception

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 157038] Auto Spell Checker Prevents Cell Selection Right Click

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

ady  changed:

   What|Removed |Added

 CC||jl...@mail.com

--- Comment #13 from ady  ---
(In reply to Kira Tubo from comment #12)
> Bibisected repository win64-7.4. 
> 
> Regression occurring at:
> https://git.libreoffice.org/core/+/cf18038c66075f7a18d89e47f3a2ab1a5bf7c4fd
> 
> Note that the commit was made to fix Bug 81894.

CC'ing Justin.

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

[Libreoffice-bugs] [Bug 150048] [PPTX] Table shadows not imported by Impress for a specific table

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

Gerald Pfeifer  changed:

   What|Removed |Added

 CC||ger...@pfeifer.com

--- Comment #8 from Gerald Pfeifer  ---
FWIW still the case with

  Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
  Build ID: a4522ef5ce6a625054d83ec907aee07c156e94ed
  CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3
  Locale: en-US (en_US.UTF-8); UI: en-US

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

[Libreoffice-bugs] [Bug 152714] Exporting Selected Range in JPG, Position of the Shape is out of place.

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

nobu  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 157293] When exporting cells + shapes in libreoffice calc into a png or jpg, shapes moves and are not aligned anymore

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

nobu  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 157295] SVG Image Export from Calc places X-axis values in random places

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

ady  changed:

   What|Removed |Added

   Keywords||bibisectRequest

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

[Libreoffice-bugs] [Bug 157295] SVG Image Export from Calc places X-axis values in random places

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

ady  changed:

   What|Removed |Added

Version|7.5.6.2 release |7.5.3.2 release
 Ever confirmed|0   |1
   Keywords||filter:svg, regression
 Status|UNCONFIRMED |NEW
   Hardware|x86-64 (AMD64)  |All
 OS|Linux (All) |All

--- Comment #4 from ady  ---
Repro on MS Windows > NEW, regression.

I'm not sure I would say the x-axis is placed at "random" places, but rather
roughly centered on the exported SVG image; it is true that it is not placed at
the same location as the original chart shows.

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

[Libreoffice-bugs] [Bug 156900] Delete row with track changes ON and show OFF doesn't hide the deleted row

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

Kira Tubo  changed:

   What|Removed |Added

Version|24.2.0.0 alpha0+ Master |7.6.1.2 release
   Keywords|bibisectRequest |bibisected, bisected
 CC||nem...@numbertext.org,
   ||nem...@openoffice.org

--- Comment #3 from Kira Tubo  ---
Bibisected repository win64-7.6. Added László Németh to cc.

Regression occurring at:
https://git.libreoffice.org/core/+/aff269c18b9029fec992135a406dc5031927c401


commit  aff269c18b9029fec992135a406dc5031927c401[log]
author  László NémethMon May 15 19:11:11 2023 +0200
committer   László NémethWed May 17 19:45:01
2023 +0200
treed5280591723728d4570275c7093d9090ab7bc397
parent  247738a9afeeb2f0644fa0307b7023fe115fae83 [diff]


f5161c82b52ed9b741186343facea1a1795755dd is the first bad commit
commit f5161c82b52ed9b741186343facea1a1795755dd
Author: Norbert Thiebaud 
Date:   Wed May 17 12:03:41 2023 -0700

source sha:aff269c18b9029fec992135a406dc5031927c401

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

[Libreoffice-bugs] [Bug 157038] Auto Spell Checker Prevents Cell Selection Right Click

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

Kira Tubo  changed:

   What|Removed |Added

   Keywords|bibisectRequest |bibisected, bisected

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

[Libreoffice-bugs] [Bug 157038] Auto Spell Checker Prevents Cell Selection Right Click

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

--- Comment #12 from Kira Tubo  ---
Bibisected repository win64-7.4. 

Regression occurring at:
https://git.libreoffice.org/core/+/cf18038c66075f7a18d89e47f3a2ab1a5bf7c4fd

Note that the commit was made to fix Bug 81894.


commit  cf18038c66075f7a18d89e47f3a2ab1a5bf7c4fd[log]
author  Justin LuthSat Feb 19 20:22:23 2022 +0200
committer   Eike Rathke   Fri Feb 25 15:22:32 2022 +0100
tree2032074d415fd06b060f1e4f41be3aa99d49c92a
parent  6c49b4290955ef1b3a502b4e5e223a4fd5573683 [diff]


c87abe4ee3766a65a553ba1ea513f0b5bf774c92 is the first bad commit
commit c87abe4ee3766a65a553ba1ea513f0b5bf774c92
Author: Norbert Thiebaud 
Date:   Fri Feb 25 06:58:41 2022 -0800

source sha:cf18038c66075f7a18d89e47f3a2ab1a5bf7c4fd

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

[Libreoffice-bugs] [Bug 157064] Allow customization of the bibliographic entry text

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

--- Comment #2 from Lucas  ---
Exactly. I want several entries in the text pointing to the same entry in the
bibliography, like that:
+-+
| ... |
|  word words words words |
|  (SOUSA-BRITO, 2023, p.22)  | <- Entry1 
| ... |
|According to Sousa-Brito (2023, p.10), words | <- Entry2
| words words words words words words words words.|
| ... |
| According to Sousa-Brito (2023, p.50), words| <- Entry3
| words words words words words words words.  | 
| ... |
| BIBLIOGRAPHY|
| |
|Sousa-Brito, 2023; Example Publication; ...  | <- Bibliography 
+-+

* Zotero allow this (the entry label can be edited). 

* LaTeX allow this thought the natbib package.

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

[Libreoffice-bugs] [Bug 157296] New: [DESIGN] [WRITER] unordered and ordered list are not to differentiate

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

Bug ID: 157296
   Summary: [DESIGN] [WRITER] unordered and ordered list are not
to differentiate
   Product: LibreOffice
   Version: 7.6.1.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: dennisroc...@libreoffice.org

Description:
As described in the design telegram channel: these two icons (hopefully correct
naming, here on german ui) dark mode standard theme are too crowdy plus  with
not enough contrast - depending on the screen (here old macbook pro 2015)



Steps to Reproduce:
see description

Actual Results:
see description

Expected Results:
see description


Reproducible: Always


User Profile Reset: Yes

Additional Info:
see chat

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

[Libreoffice-bugs] [Bug 153131] Copy causes Calc to Freeze on Windows 11

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

--- Comment #54 from Barry L. Kramer  ---
(In reply to Mike Kaganski from comment #52)
> 
> Is that your own build? I haven't found it in our dailies


No, I don't know how to build it yet. I used the link in one of the comments
(https://dev-builds.libreoffice.org/daily/master/current.html) and chose
"Win-x86_64@tb77-TDF  2023-09-15 05:28:33".  I'll try to find a debug version. 
Do you have a link I should follow?  I would be happy to run it again

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

[Libreoffice-bugs] [Bug 157059] Styles: Spaces are not respected when resizing an image

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

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 CC||sdc.bla...@youmail.dk

--- Comment #5 from sdc.bla...@youmail.dk ---
(In reply to MasterGone from comment #3)
> Simply resize the photo with lower dimensions. 
Isn't the issue really only when image height is reduced?
Image width changes do not give a problem, because both image (as character)
and caption are in centered paragraphs. Also, when image height is increased,
no problem. But when image height is decreased, it looks like the canvas is not
repainted/updated.

Two different workarounds.

Workaround 1:
1. Right-click image, select Anchor -> To Character.
2. Right-click image, select Anchor -> As Character.

Workaround 2:
1. Place cursor before or after the image, press Spacebar.
2. Delete inserted space.

I think either method will give you want you want, but I agree that the
"updating"/"repainting" should happen when the height is reduced, without
having to use a workaround.

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

[Libreoffice-bugs] [Bug 157279] EDITING : ReportBuilder : Can't change the Application-BackGround of preview report

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

--- Comment #4 from TISSENDIER Pierre  ---
I experimented : 
1-Change application-background in menu Tools>options>Interface colors>
application background, choice any color
2-Execute routine "openreport"
Result :
First the background container writer is ok
When report is include background is set blank (automatic)
if you want, you can reset the right background color with
Tools>options>Interface colors> application background :o((

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

[Libreoffice-bugs] [Bug 157059] Styles: Spaces are not respected when resizing an image

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

--- Comment #4 from MasterGone  ---
(In reply to Dieter from comment #2)
> A second thing: It seems to me, that you don't
> use the caption feature of LO: Click in image -> context menu -> insert
> caption (or you use presettings in tools -> options -> LibreOffice Writer ->
> AutoCaption. Can you explain why?
> => NEEDINFO

I find that formatting the legend is not intuitive this way, even using the
styles. This is especially true when the caption is larger than the photo.

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

[Libreoffice-bugs] [Bug 157194] Tables don't keep size configuration as per manually input

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

LeroyG  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEEDINFO

--- Comment #1 from LeroyG  ---
How do you created the table for it to "exceeds page margins"?

The table alignment is set to Automatic or to Manual?

How do you change the column's width? With the mouse pointer over the
horizontal ruler? In the Columns tab of the Table Properties dialog? Have you
checked there [x] Adapt table width?

If I understood well the question, I see no problems here:
Version: 7.4.3.2 / LibreOffice Community
Build ID: 40(Build:2)
CPU threads: 1; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: es-MX (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 157059] Styles: Spaces are not respected when resizing an image

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

MasterGone  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

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

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

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

https://git.libreoffice.org/core/commit/80a24870491385ba145757bf517c5f1cf7939017

tdf#152029 Don't include frame area top margin in the bring headings to

It will be available in 24.2.0.

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

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

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

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

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

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:7.5.0 target:7.6.0   |target:7.5.0 target:7.6.0
   |target:7.5.0.0.beta2|target:7.5.0.0.beta2
   |target:7.5.0.2  |target:7.5.0.2
   |inReleaseNotes:7.5  |inReleaseNotes:7.5
   ||target:24.2.0

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

[Libreoffice-bugs] [Bug 157279] EDITING : ReportBuilder : Can't change the Application-BackGround of preview report

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

--- Comment #3 from TISSENDIER Pierre  ---
(In reply to Alex Thurgood from comment #2)
> @Pierre: shouldn't you be using :
> 
> https://wiki.documentfoundation.org/Documentation/DevGuide/
> Office_Development#Window_Interfaces
> 
> in particular, something like :
> 
> xPeer.setBackground(0x)

thank you. @alex
It's very hard for me, i'm not very experimented LO's API. In xray i see
com.sun.star.awt.xWindowPeer only in ContainerWindow.Toolkit.DesktopWindow but
this property is  

Really, i thing, it is not possible. It is LO who create the container "writer"
before include the report, so I don't see how to intervene on the container,
before.

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

[Libreoffice-bugs] [Bug 156980] "Delete chapter" error message and action in relation to folded headings is inverted in Navigator context menu

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

--- Comment #2 from sdc.bla...@youmail.dk ---
(In reply to Dieter from comment #1)
Just to be sure. The issue here is outline folding, not whether headings are
collapsed or expanded in Navigator. I do not think the issue is affected by
whether headings are collapsed or expanded in Navigator.

When I opened the attached document, I noticed that "Heading Level 2 - folded"
was not "outline folded".  Make sure it is folded.  Then try the tests.

When "Heading Level 2 - folded" was outline folded, then I reproduced both Test
1 and Test 2, now with a later version.

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 218a7650a5cf03f895bed19c68d6f02daec536e9
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win

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

[Libreoffice-bugs] [Bug 157288] During Table editing, right click on a field doesn't show "Primary Key" for other fields than those already primary key

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

Julien Nabet  changed:

   What|Removed |Added

   Priority|medium  |high
   Severity|normal  |major
   Keywords||regression

--- Comment #6 from Julien Nabet  ---
Not a crash but:
- expected to happen on all envs considering the bug
- regression
- not a corner case

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

[Libreoffice-bugs] [Bug 157295] SVG Image Export from Calc places X-axis values in random places

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

--- Comment #3 from Jabari  ---
Created attachment 189660
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189660=edit
Correct svg done with 7.4.7.2

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

[Libreoffice-bugs] [Bug 157295] SVG Image Export from Calc places X-axis values in random places

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

--- Comment #2 from Jabari  ---
Created attachment 189659
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189659=edit
Test data

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

[Libreoffice-bugs] [Bug 157295] SVG Image Export from Calc places X-axis values in random places

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

--- Comment #1 from Jabari  ---
Created attachment 189658
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189658=edit
Example of bad svg image.

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

[Libreoffice-bugs] [Bug 157295] New: SVG Image Export from Calc places X-axis values in random places

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

Bug ID: 157295
   Summary: SVG Image Export from Calc places X-axis values in
random places
   Product: LibreOffice
   Version: 7.5.6.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jzak...@gmail.com

Description:
This problem occurred after 7.4.7.2 and exists in 7.5 and 7.6 series.

I have calc graphs with numerical x|y-axis data.
When I "export image" to svg, the x-axis values are moved from the x-axis and
are placed in seemingly random places, in a line, within the graph. Y-axis data
values, title, and legend are unaffected.

I used AppImgs of LO back to 7.2 and found exporting to svg worked fine up
through 7.4.7.2.  Starting with 7.5 thru current 7.6, the problem exists.

Steps to Reproduce:
1.Create in Calc 2 columns of numerical data
2.Use chart helper and create x|y-axis graph with numerical values along each
axis
3.Export image to svg from the graph

Actual Results:
The data values along the x-axis are placed in a line within the graph body

Expected Results:
The x-axis data values should appear along the bottom of the x-axis


Reproducible: Always


User Profile Reset: No

Additional Info:
This occurs with line graphs, histographs, step graphs, et al I tried.

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

[Libreoffice-bugs] [Bug 154443] UI: Page corners rendered incorrectly (grey squares)

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

Mike Kaganski  changed:

   What|Removed |Added

 CC||achaplea5...@oakton.edu

--- Comment #18 from Mike Kaganski  ---
*** Bug 157294 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 157294] UI- Windows 10- Grey boxes in corner of document when using dark mode

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

Mike Kaganski  changed:

   What|Removed |Added

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

--- Comment #3 from Mike Kaganski  ---


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

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

[Libreoffice-bugs] [Bug 157288] During Table editing, right click on a field doesn't show "Primary Key" for other fields than those already primary key

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

--- Comment #5 from Julien Nabet  ---
Thank you Robert for the confirmation.

For the record, I don't reproduce this with odb with Firebird embedded.

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

[Libreoffice-bugs] [Bug 157294] UI- Windows 10- Grey boxes in corner of document when using dark mode

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

--- Comment #2 from achaplea5...@oakton.edu  ---
Created attachment 189657
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189657=edit
An image in light mode where no grey boxes are in the corner of the document
area

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

[Libreoffice-bugs] [Bug 157294] UI- Windows 10- Grey boxes in corner of document when using dark mode

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

--- Comment #1 from achaplea5...@oakton.edu  ---
Created attachment 189656
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189656=edit
An image of the boxes in the corners of the document area

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

[Libreoffice-bugs] [Bug 157294] New: UI- Windows 10- Grey boxes in corner of document when using dark mode

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

Bug ID: 157294
   Summary: UI- Windows 10- Grey boxes in corner of document when
using dark mode
   Product: LibreOffice
   Version: 7.6.1.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: achaplea5...@oakton.edu

Description:
Only when using dark mode in LibreOffice Writer do I see small grey boxes in
the corners of the document area. Light mode is unaffected Per
https://ask.libreoffice.org/t/writer-grey-squares-in-far-page-corners/93227/4
this is a bug: "This is a drawing artifact, not a part of your document. It is
seen regularly in development builds, but I didn’t see it in releases. The
artifacts represent “rounding” of the shadow behind the sheet." The post
suggests filing a bug report. I have tried a new user profile, repairing the
installation and a clean uninstall and reinstall and I still have the same
issue.

Steps to Reproduce:
1. Open LibreOffice Writer
2. Choose Dark Mode in Tools > Options > View > Appearance = Dark

Actual Results:
Grey boxes shown in corner of document area

Expected Results:
No grey boxes in corner of document area


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.6.1.2 (X86_64) / LibreOffice Community
Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

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

[Libreoffice-bugs] [Bug 157288] During Table editing, right click on a field doesn't show "Primary Key" for other fields than those already primary key

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

Robert Großkopf  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #4 from Robert Großkopf  ---
Could confirm the buggy behavior in
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a2b6be8af9be3237efc3ed1244302cf899680e97
CPU threads: 6; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded

Works well in LO 7.6.1.2 on the same system (OpenSUSE 15.4 64bit rpm Linux.

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

[Libreoffice-bugs] [Bug 109272] Wrong cursor position when deleting a selection in Show Changes mode

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

Aron Budea  changed:

   What|Removed |Added

Summary|Worm, But A Caterpillar |Wrong cursor position when
   ||deleting a selection in
   ||Show Changes mode

--- Comment #29 from Aron Budea  ---
Please refrain from changing the summary to some nonsense.

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

[Libreoffice-bugs] [Bug 147834] When 'next' style is different, clear DF numbering and bulleting

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

--- Comment #12 from Eyal Rozenberg  ---
(In reply to Dieter from comment #11)
> You think it should be changed
> in the case of a style with different next style.

I don't just think that as a personal preference. I claim it's what users
_expect_, and it is what's useful to do.


> I also don't agree with this proposal, because it would lead to
> inconsistency and I'm sure, that somebody will report this as a bug and
> discussion would start again.

On the contrary, it would maintain consistency and increase coherence.

Consistency is maintained because when you press Enter and continue in the same
style, DF remains in effect; but when you are editing a paragraph with a Next
style, and the style changes, you are now writing a different part of your
document. And you expect to now have the formatting appropriate for this new
part of the document you're writing; while the DF is something you wanted to
apply to the part you were working on before. So you expect the font to change,
the spacing to change, the numbering/bulleting to change - already today. What
do you expect them to change to? The non-DF settings of the Paragraph style you
have now moved to. 

Coherence will be improved, since the way things are now, when a bunch of DF is
carried along from the previous paragraph to a Next-PS, the formatting becomes
a mess of irrelevant DF over the new PS.

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

[Libreoffice-bugs] [Bug 156980] "Delete chapter" error message and action in relation to folded headings is inverted in Navigator context menu

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

Dieter  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|
 CC||dgp-m...@gmx.de

--- Comment #1 from Dieter  ---
(In reply to sdc.blanco from comment #0)
> Test 1: 
>   1. Place cursor in ”Heading Level 2 – folded”
>   2. Use Navigator, right-click on ”Heading Level 1 – open”, choose ”Delete
> Heading”
> 
> Actual: Dialog box appears, with ”You are trying to delete folded (hidden)
> content.”

Actual result:
- No dialog box appears
- If heading level 2 is folded in navigator, heading level 2 within sublevel
(instructions) is deleted
- If heading level 2 is open in navigator, sublevel "instructions" remains.

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a4522ef5ce6a625054d83ec907aee07c156e94ed
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (de_DE); UI: en-US
Calc: CL threaded

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

[Libreoffice-bugs] [Bug 148189] Autocorrect hyphen/minus sign into Hebrew Maqaf when appropriate

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

--- Comment #7 from Shai Berger  ---
Hi, 

I want to support Eyal's suggestion here. Some background: I was involved with
the Hebrew keyboard layout standardization effort which led to the inclusion of
Maqaf in the layout; in fact, I authored that part of the "il" XKB symbols
file.  AFAIK, the alt+- key combination produces a Maqaf on Windows too, since
Windows 10.

I think the suggestion to use an emoji-like construct (":+-:"), is missing the
point: Because of decades of this character not being available on keyboards;
and the fact that it's a 3rd-level key, meaning it is still not engraved on
most physical keyboards, people have been taught not look out for it. However,
since it is still used in newspapers and books, its use will make texts look
better, and people will be happy to see it offered to them.

I think it is comparable, culturally and technically, to the fixing of ordinal
numbers (where 4th is changed to 4^th):
- It is something which makes text look much nicer; most users would just not
bother to find the option to do it themselves, but would be happy to see the
computer do it for them;
- There are contextual constraints on the transformations -- th is transformed
in "4th" and "1234th", but not in "a4th" (not pure number before) nor "4thd"
(not end-of-word after). 

Considering your question if this belongs in localized options -- I'm not sure.
The number suffixes are localized, as they change from language to language.
"Capitalize first letter of every sentence" isn't, as it is apparently relevant
to all users of Latin, Greek and and Cyrillic scripts. I think this feature is
closer to the latter -- relevant to all users of the Hebrew script (the two
most significant languages are Hebrew and Yiddish, you can see some uses in
Yiddish at https://yi.wikipedia.org/), but I'll accept the argument that the
whole script is fringe enough to put the option in "localized".

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

[Libreoffice-bugs] [Bug 157279] EDITING : ReportBuilder : Can't change the Application-BackGround of preview report

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

--- Comment #2 from Alex Thurgood  ---
@Pierre: shouldn't you be using :

https://wiki.documentfoundation.org/Documentation/DevGuide/Office_Development#Window_Interfaces

in particular, something like :

xPeer.setBackground(0x)

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

[Libreoffice-bugs] [Bug 157038] Auto Spell Checker Prevents Cell Selection Right Click

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

--- Comment #11 from ady  ---
(In reply to Heiko Tietze from comment #9)
> Interestingly, for RTL sheets it happens on the opposite side but clicking
> jumps into the cell.

That might be a separate issue. See comment 4 as an example of different
results depending on where exactly the user clicks within a cell. I could be
wrong, as I have not tested this report in RTL cases.

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

[Libreoffice-bugs] [Bug 157209] Keyboard shortcuts with CTRL (copy/cut/paste/undo/redo...) not working in Linux Hebrew keyboard layout

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

Shai Berger  changed:

   What|Removed |Added

 CC||s...@platonix.com

--- Comment #6 from Shai Berger  ---
I noted a difference between Amiad's setting and Eyal's -- Amiad was using a
Hebrew (he-IL) UI, while Eyal's is en-US.

I tried both, and the bug did not reproduce.

Version: 7.5.6.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 16; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-IL (en_IL.UTF-8); UI: en-US
Debian package version: 4:7.5.6-1
Calc: threaded

Version: 7.5.6.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 16; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-IL (en_IL.UTF-8); UI: he-IL
Debian package version: 4:7.5.6-1
Calc: threaded

I tried even with Hebrew locale:

Version: 7.5.6.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 16; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb)
Locale: he-IL (he_IL); UI: he-IL
Debian package version: 4:7.5.6-1
Calc: threaded

Nada.

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

[Libreoffice-bugs] [Bug 157291] Ctrl-v to paste does not work in file dialogues

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

steve  changed:

   What|Removed |Added

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

--- Comment #1 from steve  ---
This is a duplicated of
https://bugs.documentfoundation.org/show_bug.cgi?id=126638 which sadly is a
long-standing bug with LibreOffice on macOS and so far unresolved.

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

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

[Libreoffice-bugs] [Bug 126638] macOS: Can't paste, copy, cut or ⌘A (select all) using keyboard shortcuts in Save-As field (workaround: comment 38)

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

steve  changed:

   What|Removed |Added

 CC||lionte...@cogweb.net

--- Comment #45 from steve  ---
*** Bug 157291 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 157290] Link to Release Notes 7.6 is dead

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

steve  changed:

   What|Removed |Added

 CC||l...@disr.it
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #1 from steve  ---
Hi David,
clicking your link
https://hub.libreoffice.org/ReleaseNotes/?LOvers=7.6=en-US on Firefox
desktop takes me to https://wiki.documentfoundation.org/ReleaseNotes/7.6

Checking from my local 7.6.1.2 install the release notes also open as expected.

It seems that forwarding has been addressed in the meantime. Can you confirm?

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

[Libreoffice-bugs] [Bug 157291] Ctrl-v to paste does not work in file dialogues

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

David Liontooth  changed:

   What|Removed |Added

Version|7.6.1.2 release |3.3.0 release
  Component|LibreOffice |filters and storage

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

[Libreoffice-bugs] [Bug 157293] New: When exporting cells + shapes in libreoffice calc into a png or jpg, shapes moves and are not aligned anymore

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

Bug ID: 157293
   Summary: When exporting cells + shapes in libreoffice calc into
a png or jpg, shapes moves and are not aligned anymore
   Product: LibreOffice
   Version: 7.6.1.2 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: thurston.m...@laposte.net

Description:
if i export a sheet (calc) in png or jpg, where some shapes are used, aligned
with cells, these shapes will always be shifted vertically in the resulting
image, not let aligned with the cells they refer to. (It can be seen in the
image joined). All the losenges should be aligned with their corresponding
text. bottom losenge should be located and aligned to the left of “earliest
date…”

Steps to Reproduce:
i put / upload some files here
https://ask.libreoffice.org/t/png-jpg-export-of-calc-sheet-with-shapes-shapes-shifted-vertically/95928

Actual Results:
Take an empty sheet (ods).
Put some text in a cell (in the middle of the sheet) It could start be like "-
test".
Place a lozenge from shape and align it with the "-" of your test.
export the selection of cells around, including test + shape, into png or jpg.
the lozenge will not stay in place, being shifted to the bottom (and a bit to
the left).
Whatever it is locked with cell or page will give the issue.
Note that exporting in pdf seems to work fine, it is when exporting into png or
jpg the issue comes.

Expected Results:
The software should have kept the shape aligned with the text (or with the
cell) as it is shown in the spreadsheet under calc.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Please have a look here
https://ask.libreoffice.org/t/png-jpg-export-of-calc-sheet-with-shapes-shapes-shifted-vertically/95928

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

[Libreoffice-bugs] [Bug 120294] "Combine single line paragraphs" autocorrect option does not work

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

Dieter  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #13 from Dieter  ---
Having again a look at this bug report:

Help [1] is about line break and this works, if you follow stepf from help. But
example in video of comment 3 is about paragraph breaks. So AFAIK LO doesn't
offer such a feature for paragraph breaks. So for me NAB or perhaps an
enhancement request.
Tonyab, what do you think?

=> NEEDINFO


[1]
https://help.libreoffice.org/7.6/en-US/text/swriter/guide/removing_line_breaks.html?=SHARED=WIN

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

[Libreoffice-bugs] [Bug 157256] Beim Abspeichern in docx wird der Neubeginn der Zeilennummerierung nicht gespeichert

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

--- Comment #4 from hendrik.gas...@gmail.com ---
Hello,

you'll find two examples attached. In the docx-file I defined the first row
with the "NZZ" as a new paragraph. When I reopened it, the start of the
paragraph numbering was gone. In the odt-file everything works as expected.

Thanks for your time and help!

Best regards

Hendrik

PS: First I save the file as docx and then created the odt-file from the
docx-file.

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

[Libreoffice-bugs] [Bug 148189] Autocorrect hyphen/minus sign into Hebrew Maqaf when appropriate

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

Eyal Rozenberg  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

--- Comment #6 from Eyal Rozenberg  ---
(In reply to Dieter from comment #5)
> AFAIK the idea of context sensible AutoCorrect is, that a unique key
> combination (like :-+:) is replaced by Maqaf

While that could be defined, it's would be ineffective, as few people will use
it, and one would always have to remember to type that combination in. Plus, if
you work with existing text, it can't be applied. 

No, I specifically asked for heuristic replacement of minus characters between
words with Maqaf, with no special key combination.

> Let's see, if design-team has a solution
> 
> cc: Design-Team

I don't mind the CC, but there's not much of a design issue here IMHO. The
design part is all there - same as for minus-to-en-dash, or replacement of <<
>> with guillemets. Just needs a checkbox in the AutoCorrect options dialog and
implementation of the heuristic.

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

[Libreoffice-bugs] [Bug 157256] Beim Abspeichern in docx wird der Neubeginn der Zeilennummerierung nicht gespeichert

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

--- Comment #3 from hendrik.gas...@gmail.com ---
Created attachment 189655
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189655=edit
odt-file with working paragraph numbering

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

[Libreoffice-bugs] [Bug 157256] Beim Abspeichern in docx wird der Neubeginn der Zeilennummerierung nicht gespeichert

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

--- Comment #2 from hendrik.gas...@gmail.com ---
Created attachment 189654
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189654=edit
docx-file with not working paragraph numbering

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

[Libreoffice-bugs] [Bug 157292] Consolidate Text should maintain vertical placement of lines after consolidation

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

Eyal Rozenberg  changed:

   What|Removed |Added

  Component|Impress |Draw

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

[Libreoffice-bugs] [Bug 148159] Please check if you get error reports which are assigned to the wrong version of LibreOfficeWriter

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

--- Comment #6 from Dieter  ---
(In reply to Adalbert Hanßen from comment #4)
> Created attachment 189305 [details]
> the file which crashed LO Writer when double-clicked upon in the file browser

I could open it without any problems

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

Perhaps somebody else can help.

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

[Libreoffice-bugs] [Bug 157292] Consolidate Text should maintain vertical placement of lines after consolidation

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

--- Comment #2 from Eyal Rozenberg  ---
Created attachment 189653
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189653=edit
A simple LibreOffice Draw file for reproduction

For a simpler reproduction:

1. Create a new drawing in LO.
2. Insert two textboxes with some text at a non-trivial vertical distance from
each other.
3. Select both textboxes.
4. In the context menu, select Consolidate Text.

The attachment lets you skip steps (1.) - (2.).

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

[Libreoffice-bugs] [Bug 148189] Autocorrect hyphen/minus sign into Hebrew Maqaf when appropriate

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

Dieter  changed:

   What|Removed |Added

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

--- Comment #5 from Dieter  ---
(In reply to Eyal Rozenberg from comment #4)
> 1. You don't want to always replace minus sign (-) with Maqaf (־). It's
> context-dependent. There are no Maqaf's after or before spaces (AFAIK), for
> example. You also want to make sure it's not a hyphen between numbers. etc.

AFAIK the idea of context sensible AutoCorrect is, that a unique key
combination (like :-+:) is replaced by Maqaf
> 
> 2. The replacement is not defined by default. I'm asking for something that
> will be defined and enabled once AutoCorrect is enabled and the user is
> writing Hebrew text.

Let's see, if design-team has a solution

cc: Design-Team

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

[Libreoffice-bugs] [Bug 157292] Consolidate Text should maintain vertical placement of lines after consolidation

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

--- Comment #1 from Eyal Rozenberg  ---
Created attachment 189652
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189652=edit
PDF to import into draw for reproducing the bug

PDF for use with the reproduction instructions.

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

[Libreoffice-bugs] [Bug 157292] New: Consolidate Text should maintain vertical placement of lines after consolidation

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

Bug ID: 157292
   Summary: Consolidate Text should maintain vertical placement of
lines after consolidation
   Product: LibreOffice
   Version: 7.6.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com

Reproduction instructions:

1. Open the attached PDF in Draw
2. Consider the two-line title on the first page, and specifically the vertical
placement of the second line, at a (relatively high) vertical distance from the
fir
3. Select the two textboxes of the title text
4. In the context menu for the selected boxes, choose "Consolidate Text"
5. Consider again the vertical placement of the second line of the title text
and its distance from the first line

Expected results:

The second line of title text does not move. The space between the two lines is
set (either via space-after the first line or space-before the second line,
preferably the latter) so as to maintain the vertical position of the second
title line.

Actual results:

The second line of the title moves up




Note that preserving the position is of significance when the origin of the two
lines is in a document you did not create, and whose text you wish to edit, but
whose layout, especially vertical layout, must be maintained. Specifically
important when editing imported PDF files.

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

[Libreoffice-bugs] [Bug 157291] New: Ctrl-v to paste does not work in file dialogues

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

Bug ID: 157291
   Summary: Ctrl-v to paste does not work in file dialogues
   Product: LibreOffice
   Version: 7.6.1.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: lionte...@cogweb.net

Description:
When selecting "File Save" or "File Save As", ctrl-v does not work in the file
name field. Instead you have to use right-click mouse.

I don't know which LibreOffice component is responsible for this functionality
-- maybe Filters and storage? MS Word and any other programs allow ctrl-v for
paste in file dialogues, so it's clearly possible.

Steps to Reproduce:
1. Open a Save dialog
2. In the file name field, press ctrl-v to paste a file name


Actual Results:
Nothing happens -- you have you right-click and select Paste

Expected Results:
Ctrl-v should paste whatever is in the paste buffer


Reproducible: Always


User Profile Reset: Yes

Additional Info:
I have used LibreOffice for a decade or more and this has never worked.

Version: 7.6.1.2 (AARCH64) / LibreOffice Community
Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674
CPU threads: 8; OS: Mac OS X 13.1; UI render: Skia/Raster; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 156999] Writer splitting words or changing them

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

Dieter  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|
 Status|UNCONFIRMED |NEEDINFO
 CC||dgp-m...@gmx.de
 Ever confirmed|0   |1

--- Comment #2 from Dieter  ---
Rod, thank you for reporting the bug. It seems, you are using an old version of
LO. Could you please retest with acutal version LO 7.6? If the bug is still
present, please also try in safe mode (Help -> Restart in SafeMode).

=> NEEDINFO

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

[Libreoffice-bugs] [Bug 147834] When 'next' style is different, clear DF numbering and bulleting

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

Dieter  changed:

   What|Removed |Added

Summary|When 'next' style is|When 'next' style is
   |different, clear numbering  |different, clear DF
   |and bulleting   |numbering and bulleting

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

[Libreoffice-bugs] [Bug 147834] When 'next' style is different, clear numbering and bulleting

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

Dieter  changed:

   What|Removed |Added

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

--- Comment #11 from Dieter  ---
(In reply to Eyal Rozenberg from comment #10)
> The whole point I'm making is that we're not talking about _always_ here,
> we're talking the niche case of styles with a different Next style. That's
> the case you have a contra-indication of your wanting DF to continue. Not
> the default case.

As Heiko explained in comment 6 actual rule is: "If you DF until the end of the
paragraph this formatting will be kept." You think it should be changed in the
case of a style with different next style.

I also don't agree with this proposal, because it would lead to inconsistency
and I'm sure, that somebody will report this as a bug and discussion would
start again.

Heiko, is it possible to discuss this topic in a design meeting and come to a
final decision?

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

[Libreoffice-bugs] [Bug 157290] New: Link to Release Notes 7.6 is dead

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

Bug ID: 157290
   Summary: Link to Release Notes 7.6 is dead
   Product: LibreOffice
   Version: 7.6.1.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Documentation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: lionte...@cogweb.net
CC: olivier.hal...@libreoffice.org

Description:
When I first open Libreoffice 7.6.1.2, I'm prompted to read the Release Notes.
Clicking that link takes me to
https://hub.libreoffice.org/ReleaseNotes/?LOvers=7.6=en-US, which is a
dead link -- page does not load. The same link is used in the "About
LibreOffice" screen. I use the AARCH64 architecture, but suspect this is the
same in all releases.

The release notes appear to have moved and I find them here:
https://wiki.documentfoundation.org/ReleaseNotes/7.6
It looks to me like this link should be updated. 

Steps to Reproduce:
1. Click on "LibreOffice", "About LibreOffice" and then  "Release Notes"
2.
3.

Actual Results:
Web page no longer exists

Expected Results:
Release Notes


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Change the link to the current location of the Release Notes,
https://wiki.documentfoundation.org/ReleaseNotes/7.6

Note that the instructions for this field in the bug report system prompts
users to "Please copy here the information from menu Help - About LibreOffice."
This is incorrect; the "About LibreOffice" screen is no longer accessible from
the Help menu, at least on a Mac. Instead it's located under LibreOffice |
About LibreOffice.

Version: 7.6.1.2 (AARCH64) / LibreOffice Community
Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674
CPU threads: 8; OS: Mac OS X 13.1; UI render: Skia/Raster; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 153131] Copy causes Calc to Freeze on Windows 11

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

--- Comment #53 from Mike Kaganski  ---
I believe that the best would be a minidump for some *release* version -
because we have symbols for them on our symbol server. Any local or daily build
would have a symbols missing problem...

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

[Libreoffice-bugs] [Bug 157289] FILESAVE DOCX: Saving curved arrow shape works all right in 7.2 but not in 24.2

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

sdc.bla...@youmail.dk changed:

   What|Removed |Added

Summary|Saving curved arrow shape   |FILESAVE DOCX: Saving
   |as DOCX works all right in  |curved arrow shape works
   |7.2 but not in 24.2 |all right in 7.2 but not in
   ||24.2
  Component|Writer  |filters and storage
 Blocks||104442


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=104442
[Bug 104442] [META] OOXML shape (DrawingML and VML) related issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 104442] [META] OOXML shape (DrawingML and VML) related issues

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

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 Depends on||157289


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=157289
[Bug 157289] FILESAVE DOCX: Saving curved arrow shape works all right in 7.2
but not in 24.2
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157289] New: Saving curved arrow shape as DOCX works all right in 7.2 but not in 24.2

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

Bug ID: 157289
   Summary: Saving curved arrow shape as DOCX works all right in
7.2 but not in 24.2
   Product: LibreOffice
   Version: 24.2.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sdc.bla...@youmail.dk

Created attachment 189651
  --> https://bugs.documentfoundation.org/attachment.cgi?id=189651=edit
test file with screenshots that show differential behavior

The attached file gives a test document and includes screenshots of the
problem.

1. Insert some curved arrows into a new document.
2. Save as .docx and open in Word.

3. If saved with Version: 7.2.7.2 (x64) / LibreOffice Community
Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2
then arrows appear the same (as expected) when opened in Word.

4. If saved with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 218a7650a5cf03f895bed19c68d6f02daec536e9
the curved arrows are NOT reproduced as expected.  

Screenshots in attached document show the obtained results.

Possible regression?

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

[Libreoffice-bugs] [Bug 119617] FILEOPEN PPTX Text box setting "Resize shape to fit text" not imported correctly ( steps in comment 8 )

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

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 157285] FILEOPEN PPTX: Textbox too tall - import needs to look at the shape on the slide instead of the master page

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

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 CC||kelem...@ubuntu.com
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=11
   ||9617

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

[Libreoffice-bugs] [Bug 157285] FILEOPEN PPTX: Textbox too tall - import needs to look at the shape on the slide instead of the master page

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

Gerald Pfeifer  changed:

   What|Removed |Added

Summary|FILEOPEN PPTX: Textbox too  |FILEOPEN PPTX: Textbox too
   |high - import needs to look |tall - import needs to look
   |at the shape on the slide   |at the shape on the slide
   |instead of the master page  |instead of the master page

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

[Libreoffice-bugs] [Bug 153131] Copy causes Calc to Freeze on Windows 11

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

--- Comment #52 from Mike Kaganski  ---
(In reply to Barry L. Kramer from comment #46)
> I am using the following version of Dev 24:
> 
> Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
> Build ID: b3fdd999f87312447d03915585812b3a5cd48141

Is that your own build? I haven't found it in our dailies (the one from Sep 14
there is 4942aa1533af25cf102da7516bd5e521c553aa07, i.e. several commits later,
and its binaries aren't accepted to debug this minidump)

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

[Libreoffice-bugs] [Bug 108600] Paragraph format: Inconsistent display in space between paragraphs for area fill

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

Dieter  changed:

   What|Removed |Added

 CC||sanipache...@outlook.com.ar

--- Comment #15 from Dieter  ---
*** Bug 157061 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 157061] Background of merged paragraphs among styles that share the background

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

Dieter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||dgp-m...@gmx.de
 Resolution|--- |DUPLICATE
 Whiteboard| QA:needsComment|

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

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

bit I also think it is a duplicate of bug 108600. leandro feel free to change
it back to NEW with a short reasoning, if you disagree.

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

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

[Libreoffice-bugs] [Bug 148189] Autocorrect hyphen/minus sign into Hebrew Maqaf when appropriate

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

--- Comment #4 from Eyal Rozenberg  ---
(In reply to Dieter from comment #3)
> Eyal, does this solve your problem?

No, for two reasons:

1. You don't want to always replace minus sign (-) with Maqaf (־). It's
context-dependent. There are no Maqaf's after or before spaces (AFAIK), for
example. You also want to make sure it's not a hyphen between numbers. etc.

2. The replacement is not defined by default. I'm asking for something that
will be defined and enabled once AutoCorrect is enabled and the user is writing
Hebrew text.

> I know it is not your idea for 100%, but more general your option is "Make it
> possible, that defined replacement only happens in a specific context". If
> this is possible it would need a lot of effort

This effort has already been expended for replacement of minus signs by
en-dashes, which also happens in specific contexts. 

> and why should we only have
> such a feature for Maquaf and not for other characters also?

I'm not sure what you mean by other characters, but: We have AutoCorrect for
double quotes, single quotes, and dashes. Maqaf is a kind of dash, so it is, in
principle, covered by the current scope of AutoCorrect.

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

[Libreoffice-bugs] [Bug 101258] [META] Bibliography bugs and enhancements

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

Dieter  changed:

   What|Removed |Added

 Depends on||157064


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=157064
[Bug 157064] Allow customization of the bibliographic entry text
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157064] Allow customization of the bibliographic entry text

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

Dieter  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|
 CC||dgp-m...@gmx.de,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org
   Keywords||needsUXEval
 Blocks||101258

--- Comment #1 from Dieter  ---
I'm not very familiar with bibliography in LO, because I use Zotero Plugin. I
understand your idea, but does it mean you have to add a new entry everytime
you refer to a different page?

cc: Design-Team for further input and decision.


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 101258] [META] Bibliography bugs and enhancements

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

Dieter  changed:

   What|Removed |Added

 Blocks||129434


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=129434
[Bug 129434] [META] Writer (EDITING) Suggested bug fixes, enhancements and
features for authors.
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 129434] [META] Writer (EDITING) Suggested bug fixes, enhancements and features for authors.

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

Dieter  changed:

   What|Removed |Added

 Depends on||101258


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 148644] Bug within paragraph constraints (keep with next / do not split paragraph)

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

Dieter  changed:

   What|Removed |Added

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

--- Comment #10 from Dieter  ---
(In reply to Timur from comment #6)
> I don't see a bug . 
> Help says:
> "Keep with next paragraph
> Keeps the current paragraph and the following paragraph together when a
> break or column break is inserted."
> 
>  "Keep with next" should be for the whole para, for comment 4 just turn it
> off. 

I'm not sure for 100%, because in this case widow and orphan control makes no
sense and should be greyed out, but they are still active.

Heiko, what do you think?

Anyway, help [1] should be improved here.

[1]
https://help.libreoffice.org/7.6/en-GB/text/swriter/01/05030200.html?System=WIN=WRITER=cui/ui/textflowpage/TextFlowPage#bm_id3147406

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

  1   2   >