[Libreoffice-bugs] [Bug 149506] Slow start-up and opening of files since 7.3 release

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149506

--- Comment #24 from Buovjaga  ---
(In reply to bunkem from comment #22)
> (In reply to Buovjaga from comment #17)
> > bunkem: just to be clear, before starting a bisecting session, you check
> > both the master commit and the oldest commit in the repository. If the bug
> > is not seen in the oldest, but is in master, you can start.
> > 
> > Now, if you have doubts about the result, you can double-check by doing
> > 
> > git checkout 846a5c424a6c16dc07eefb6827b362efed5075b1
> > 
> > Test, if the slowness is there. Then, do
> > 
> > git checkout HEAD^
> > 
> > to go to the preceding commit and test again. If the slowness is still
> > there, your result is wrong.
> 
> Hi again.  Sorry I've tried to follow the instructions on the QA website
> link. THis is the first time I use git so I'm a bit lost.
> 
> I followed the instructions and did: 
> 
> > git checkout 846a5c424a6c16dc07eefb6827b362efed5075b1
> 
> > open Libreoffice.app/
> 
> It takes about 9-10 sec to start.  So this is a slow one.
> 
> > git checkout HEAD^ gives
> 
> > Previous HEAD position was 846a5c424 source 
> > ce69f71983a09416514f0569c6cdfbcde87d4b99
> > HEAD is now at a5a14a421 source b8f067dae3424c9cc2373e84c8a3465d477f9adc
> 
> I don't know how to identify the last version.  I presume it is 846a5c424
> but that is the first 9 characters of the version checked out.
> 
> I'm embarrassed for my lack of knowledge and the git bisect man page isn't
> helping me. :-(

So to put it briefly, I'm interested in if you saw the slowness or not after
running LibreOffice after doing git checkout HEAD^

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

[Libreoffice-bugs] [Bug 153534] Most bundled page styles are nonsensical and/or redundant

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153534

--- Comment #17 from Heiko Tietze  ---
And how do you make the margin appear left/right depending on odd/even pages?

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

[Libreoffice-bugs] [Bug 153606] macOS app icon is not properly integrated

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153606

--- Comment #5 from Heiko Tietze  ---
Created attachment 185424
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185424=edit
macOS start center

You are free to always reopen tickets. 

That's how it looks for me, pretty nice. And this is likely what Galdam makes
think it is fixed aka notabug. Now we need to figure out why your icon is
smaller.

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

[Libreoffice-bugs] [Bug 153678] Better integration of JDBC in Base

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153678

Julien Nabet  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #1 from Julien Nabet  ---
There must some other way but to have max info, I'd suggest to build yourself
LO by following https://wiki.documentfoundation.org/Development/BuildingOnLinux
+ adding --enable-dbgutil in autogen.input

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

[Libreoffice-bugs] [Bug 153683] New: CLI: Show the module which is used in --convert-to

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153683

Bug ID: 153683
   Summary: CLI: Show the module which is used in --convert-to
   Product: LibreOffice
   Version: unspecified
  Hardware: All
   URL: https://ask.libreoffice.org/t/convert-to-txt-text-enco
ded-utf8-fails/88123
OS: All
Status: UNCONFIRMED
  Keywords: difficultyMedium, easyHack, skillCpp
  Severity: enhancement
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mikekagan...@hotmail.com

In command-line interface, --convert-to prints some diagnostics. E.g., this
command:

> soffice --convert-to "txt:Text (encoded):UTF8" myfile

would produce this diagnostic:

> convert /path/to/myfile -> /path/to/myfile.txt using filter : Text 
> (encoded):UTF8

If 'myfile' happens to be opened in a module other than Writer (say, it's a PDF
or ODS), then conversion would fail like this:

> Error: Please verify input parameters... (SfxBaseModel::impl_store
>  failed: 0xc10(Error Area:Io Class:Write Code:16))

And there is no hint to user, what the problem was. See e.g.
https://ask.libreoffice.org/t/convert-to-txt-text-encoded-utf8-fails/88123.

The proposal is to print the module that is used to import the source document,
which defines which export filters are available. This could look like:

> convert /path/to/myfile -> /path/to/myfile.txt as a Draw document
> using filter : Text (encoded):UTF8

and should be done in desktop/source/app/dispatchwatcher.cxx [1] by examining
the implemented service of xModel.

[1]
https://opengrok.libreoffice.org/xref/core/desktop/source/app/dispatchwatcher.cxx?r=1f59cbe6=29729=667#667

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

[Libreoffice-bugs] [Bug 153676] Page styles should include a default paragraph style like paragraph styles include a character styles

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153676

--- Comment #2 from Mike Kaganski  ---
Conceptually, text document is a text with attributes applied to parts of the
text defining the end result. The text consists of the main entities, which are
paragraphs. Then, paragraphs consist of text runs. These are the real
constituents of the documents. *There is no pages*. The pages are the artifacts
of the dynamic layout process (i.e., they emerge in WYSIWYG and at print). But
each paragraph, by definition, has a paragraph style. If a paragraph has a DF,
it is also an (auto) paragraph style, based on another real paragraph style.
There is no way to define an "automatically assigned" paragraph style.

Automatically assigning paragraph styles based on page styles could happen in
one of two ways. First would be like the "next paragraph style" mechanism: the
editor would hard-assign it at the next paragraph creation time. This requires
knowing which page style is current at the time of the paragraph creation.
Which means that the layout must be known at creation time (ruling out any
automated creation, e.g. macros and manual markup generation). And changing
page style would make it inconsistent, where already assigned styles would not
match the current page style in the changed layout.

Another way would be a dynamic assignment of paragraph style at layout time,
and would require a conception of paragraphs without otherwise assigned para
styles. Which is a nonsense in the ODT model.

Consider this situation. You type something on the first page. Its style A is
decided in some way; and now you are near the bottom of it. You start a new
paragraph. Its style depends on the active page style. Let's say, the automatic
paragraph style X has spacing-before, or widow/orphan setting, to not fit on
this page. The next page gets created automatically, to accommodate the
content. Its style is defined by the previous page style's "next style". And
this new page with its new style B defines another automatic paragraph style Y.
And this paragraph style Y could, e.g., define that it has a
page-break-with-page-style C. So instead of page style B, this next page much
become style C. But style C could define yet another automatic paragraph style
Z, and our new paragraph needs to be it (because its style is just being
defined). But it could have new properties that allow it to fit to page 1 ...

All in all, I consider this proposal to be incompatible with text flow-oriented
paradigm of Writer. It is more like page-oriented approach. If Draw/Impress had
paragraph styles (which they should one day), it could be applicable there; and
then, it would be the one difference between similar features in different
modules.

For now, as in Writer, I consider this not only WONTFIX (i.e., "acknowledge the
problem, but have reasons to not do it"), but even INVALID (as in "there is no
such problem in the first place").

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

[Libreoffice-bugs] [Bug 116222] [META] Edit conditional formatting dialog bugs and enhancements

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116222

ady  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 116221] [META] Manage conditional formatting dialog bugs and enhancements

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116221

ady  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 87351] [META] Conditional formatting bugs and enhancements

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87351

ady  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153506] Conditional format not preserved in copied sheet. See comment 19

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153506

ady  changed:

   What|Removed |Added

   Keywords||regression
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=87
   ||351,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=11
   ||6221,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=11
   ||6222

--- Comment #20 from ady  ---
Also repro (as steps in comment 19) in:

Version: 7.0.0.3 (x86)
Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e

and in:

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


whereas with:

_ LibreOffice 3.3.0 
_ Version: 5.4.7.2
_ Version: 6.0.0.3
Build ID: 64a0f66915f38c6217de274f0aa8e15618924765

I repeated the steps in comment 19 and worksheet _2 behaves the same as
, thus it's a regression that started somewhere between version 6 and
6.1.5.2.


See also META bug 87351 bug 116221 bug 116222.

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

[Libreoffice-bugs] [Bug 153682] FORMATTING: Objects are moved in LibreOffice Draw even if I group them

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153682

--- Comment #2 from Wilhelm Erth  ---
Created attachment 185423
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185423=edit
A screenshot of the PDF viewer of the slide when it was exported to PDF. It
shows how the slide actually should look like.

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

[Libreoffice-bugs] [Bug 153682] FORMATTING: Objects are moved in LibreOffice Draw even if I group them

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153682

--- Comment #1 from Wilhelm Erth  ---
Created attachment 185422
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185422=edit
A screenshot of a slide after I've reopened the file. All the objects are
moved. The writing, however, should be covered by white rectangles.

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

[Libreoffice-bugs] [Bug 153682] New: FORMATTING: Objects are moved in LibreOffice Draw even if I group them

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153682

Bug ID: 153682
   Summary: FORMATTING: Objects are moved in LibreOffice Draw even
if I group them
   Product: LibreOffice
   Version: 3.6.7.2 release
  Hardware: Other
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: wilhelm.e...@web.de

Description:
I used LibreOffice Draw to create some structures. Therefore I pasted a
screenshot into a new slide and added some rectangles to the slide and placed
them over parts of the screenshot. To avoid moving some objects, I grouped them
for each slide and saved all. After opening the file again, the screenshot is
looking different (it's larger than the area I cut and chose) and all the
objects on the slide were moved so the slide doesn't look like I made it.

Steps to Reproduce:
1. Paste a screenshot or an other image file into LibreOffice Draw.
2. Right-click on the object and choose "Cut".
3. Cut the image. 
4. Choose some rectangles from the toolbar and add them onto the image.
5. Mark all objects on a slide using Ctrl+A and right-click choosing "Group".
6. Save the file.
7. Close the file.
8. Reopen the file again. 

Actual Results:
The rectangles aren't at the position where I have placed them the last time I
have worked with the file. Furthermore, the images are cut in another way than
I cut them.

Expected Results:
The slide looks the same as it looked when I saved it the day before. All the
objects are on the position where they should be.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: de
Module: DrawingDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
[Information added manually]
Version: 7.3.6.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 4; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

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

[Libreoffice-bugs] [Bug 153681] Conversion from docx and odt format to rtf produces incorrect document

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153681

--- Comment #1 from Sunil  ---
Created attachment 185421
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185421=edit
ODT example file where the issue is present

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

[Libreoffice-bugs] [Bug 153681] New: Conversion from docx and odt format to rtf produces incorrect document

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153681

Bug ID: 153681
   Summary: Conversion from docx and odt format to rtf produces
incorrect document
   Product: LibreOffice
   Version: 6.4.7.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sunil+bugzi...@tandan.me

Description:
When a docx document or odt document with table inside table is saved as rtf,
the resulting file is incorrect and the layout is messed up.

When the same document is converted to PDF, the resulting document is as
expected.

Steps to Reproduce:
1. Create a new document using Writer
2. Insert a 3x3 table 
3. Insert 2x2 table in the middle column of the original table
4. Save it as rtf file
5. Close the document and reopen the rtf file

Actual Results:
The whole table layout is messed up. 
If the content is inside the table, the content is also missing. 

Expected Results:
The table layout should be the same as on the original document. 


Reproducible: Always


User Profile Reset: Yes

Additional Info:
If exported as PDF, the layout is correct. Saving as docx file also results in
correct docx file.

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

[Libreoffice-bugs] [Bug 153676] Page styles should include a default paragraph style like paragraph styles include a character styles

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153676

--- Comment #1 from Mike Kaganski  ---
This is IMO wrong, since page style is an *attribute* of paragraph (style). And
this would introduce a possible circular problem.

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

[Libreoffice-bugs] [Bug 153672] sm formula text nodes of OLE Math equation from a pasted OLE Calc sheet cell are not displayed

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153672

V Stuart Foote  changed:

   What|Removed |Added

Summary|Text of pasted OLE Calc |sm formula text nodes of
   |sheet with cell holding OLE |OLE Math equation from a
   |Math equations not  |pasted OLE Calc sheet cell
   |displayed   |are not displayed

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

[Libreoffice-bugs] [Bug 153672] Text of pasted OLE Calc sheet with cell holding OLE Math equations not displayed

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153672

QA Administrators  changed:

   What|Removed |Added

   Keywords||bibisectRequest

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

[Libreoffice-bugs] [Bug 150960] Use platform look and feel (plaf) and scaling for Java windows

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150960

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 133274] Signing a document with x.509 soft certificate not possible when DATEV Middleware is installed (Germany)

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133274

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

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 150503] Libre Calc Paste Special

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150503

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

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 153333] Plasma Wayland: Invisible or wrong cursor when inserting geometric shapes etc.

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=15

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 137040] Writing in Persian and English Simultaneously in one line make libreoffice writer too slow

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=137040

--- Comment #10 from QA Administrators  ---
Dear omid,

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 63965] CONFIGURATION: two identical functions

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=63965

--- Comment #9 from QA Administrators  ---
Dear Kranthi Katikala,

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 135034] Bbox should rotate with rotated groups (like it does for single objects)

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=135034

--- Comment #7 from QA Administrators  ---
Dear Jim Avera,

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 120569] Custom Animation Sound Effect Not Played After ODP File Moved To Another Location

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120569

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

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 116418] FILEOPEN: Incorrect text size when using TextFitToSize / "Do not Autofit"

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=116418

--- Comment #10 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 115205] FILESAVE HTMLEXPORT images are overlapped when spreadsheet exported as HTML

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115205

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

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 115154] Exported html contains unvalid links (target in document)

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115154

--- Comment #7 from QA Administrators  ---
Dear board.bugs.documentfoundation,

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 101002] Comments in Impress are not accessible (adding/reading)

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101002

--- Comment #11 from QA Administrators  ---
Dear Alex ARNAUD,

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 100288] first line after inserted picture is not justified

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=100288

--- Comment #7 from QA Administrators  ---
Dear Heinrich Hartl,

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 153562] Pasting Selected Range to Sheet as BMP Image, It will be a Chart Image without content.

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153562

nobu  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153467] Charts created by Calc are damaged when copied as Metafile (GDI)

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153467

nobu  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||3562

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

[Libreoffice-bugs] [Bug 153467] Charts created by Calc are damaged when copied as Metafile (GDI)

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153467

--- Comment #6 from nobu  ---
Created attachment 185420
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185420=edit
my sample file

Reproducible with Version 7.5.0.3 64bit, OS:Windows10 64bit
Reproducible with Version 7.6.0.0 alpha0 64bit, OS:Windows10 64bit

I reported the next bug the other day.
https://bugs.documentfoundation.org/show_bug.cgi?id=153562
"Paste GDI" seems to be worse.
Check my sample file.

1. Open the sample file
2. Select and Copy just the cells within the red rectangle that has the caption
"Copy Range."
3. Move to another cell.
4. From the Paste Icon dropdown in the toolbar, Select to paste using the GDI
Metafile option.

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

[Libreoffice-bugs] [Bug 153606] macOS app icon is not properly integrated

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153606

--- Comment #4 from alexandre burton  ---
hello!

in the issue trackers i'm familiar with, if the issue is marked "resolved" it
means it's closed -- in the sense that it's not open to discussion anymore.
perhaps here it works differently.

i'm not an apple guideline inspector, i'm reacting to my own experience, which
is this: https://pasteboard.co/9PKU7UdN81ze.jpg and LO is diminutive and
off-weight.

as far as my take goes, the main reason i see is the duplication of
"backgrounds" (esp white) and "outlines". the dark gray border should be the
"squircle" BG, and the iconic white LO doc be within (like the mail enveloppe
for example). and cutting the top-right corner of the squircle to have a
pointed triangle float "out" of the squircle zone would be great (perhaps even
with an alpha gap), support the consistency of the OS, and reaffirm the LO
branding. very tight shadowing will bring sharpness in line with most other
icons (even the non-squircles ones have tight shadows).

the end game is to fit in the dock and task bar as it's where the icon is seen
99% of the time. but maybe my approach is distorted (when i mentioned the "LO
community" it's because i assumed there was a collective process behind this
(perhaps iterating), but as i understand it's more of an individual-based
effort, which is fine).

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

[Libreoffice-bugs] [Bug 153680] Period [.] incorrectly formatting in cross-reference to outline numbering paragraph

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153680

--- Comment #4 from Andrew Conley  ---
Comment on attachment 185419
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185419
Example Windows

I tried it on 7.4.5.1 in a Windows VirtualBox installation. Same problem.

See second attachment: ‘Example Windows’.

Version: 7.4.5.1 (x86) / LibreOffice Community
Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render:
Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-GB
Calc: threaded

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

[Libreoffice-bugs] [Bug 153680] Period [.] incorrectly formatting in cross-reference to outline numbering paragraph

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153680

--- Comment #3 from Andrew Conley  ---
Created attachment 185419
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185419=edit
Example Windows

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

[Libreoffice-bugs] [Bug 153680] Period [.] incorrectly formatting in cross-reference to outline numbering paragraph

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153680

--- Comment #2 from Andrew Conley  ---
I tried it on 7.4.5.1 in a Windows VirtualBox installation. Same problem.

See second attachment: ‘Example Windows’.

Version: 7.4.5.1 (x86) / LibreOffice Community
Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render:
Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-GB
Calc: threaded

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

[Libreoffice-bugs] [Bug 153680] Period [.] incorrectly formatting in cross-reference to outline numbering paragraph

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153680

--- Comment #1 from Andrew Conley  ---
Created attachment 185418
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185418=edit
Example

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

[Libreoffice-bugs] [Bug 153680] New: Period [.] incorrectly formatting in cross-reference to outline numbering paragraph

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153680

Bug ID: 153680
   Summary: Period [.] incorrectly formatting in cross-reference
to outline numbering paragraph
   Product: LibreOffice
   Version: 7.3.7.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: main.spot5...@fastmail.com

Description:
Previously, if I had the following outline numbering paras:

1.
   (a)

— and then inserted a cross-reference to (a) using ‘Number (full context)’,
Writer would insert:

1(a)

Since upgrading to 7.3.7.2, it now inserts:

1.(a)

Steps to Reproduce:
1. Insert two levels of outline numbered paragraphs where the first level has a
period [.] following the paragraph number.
2. Insert a cross-reference to the second level using ‘Number (full context)’.

NOTE: The unwanted behaviour does not occur if you insert a cross-reference to
the first level. I.e. it will insert just ‘1’ without a period [.] following.

Actual Results:
1.(a)

Expected Results:
1(a)


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.3.7.2 / LibreOffice Community
Build ID: 30(Build:2)
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11
Locale: en-AU (en_AU.UTF-8); UI: en-US
Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.1
Calc: threaded

This behaviour started after I upgraded from 6.[?] to 7.3.7.2.

I posted about this here:
https://ask.libreoffice.org/t/unwanted-change-to-cross-referencing-numbering-convention/87797

One comment said: This is the result of
https://gerrit.libreoffice.org/c/core/+/117156. And please file this as a bug
(about broken backward compatibility). It is related to
https://bugs.documentfoundation.org/show_bug.cgi?id=144563.

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

[Libreoffice-bugs] [Bug 153534] Most bundled page styles are nonsensical and/or redundant

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153534

--- Comment #16 from David  ---
(In reply to Eyal Rozenberg from comment #15)
> Then you're assuming the style will do something it does not, because
> specifying "Right page" will not affect the page numbering; nor will it
> insert an extra page before your section begins (nor at section start).

I can configure a heading paragraph style at the beginning of a chapter (and
yes, that chapter may be within a document "section") to insert a page break
with a particular page style before the heading. If I tell it to insert a page
with the Right page style, then I can set that page style to not include a
header. I can also set the Right page style to use my normal page style as the
next page, which does have headings on it. Please provide a document template
that demonstrates a better way to do this so that we all may learn.

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

[Libreoffice-bugs] [Bug 105948] [META] Undo/Redo bugs and enhancements

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=105948

Aron Budea  changed:

   What|Removed |Added

 Depends on||153644


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153644
[Bug 153644] Calc: Undo doesn't remove cell's borders
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 133619] [META] Regressions from increasing column limit in Calc (mainly bug 50916)

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=133619

Aron Budea  changed:

   What|Removed |Added

 Depends on||153644


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153644
[Bug 153644] Calc: Undo doesn't remove cell's borders
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153644] Calc: Undo doesn't remove cell's borders

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153644

Aron Budea  changed:

   What|Removed |Added

 Blocks||105948, 133619
 CC||aron.bu...@gmail.com


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=105948
[Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=133619
[Bug 133619] [META] Regressions from increasing column limit in Calc (mainly
bug 50916)
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153679] Texts on PPTX files are intertwined

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153679

--- Comment #1 from kerems...@gmail.com ---
Created attachment 185417
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185417=edit
An example presentation file that have this issue.

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

[Libreoffice-bugs] [Bug 153679] New: Texts on PPTX files are intertwined

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153679

Bug ID: 153679
   Summary: Texts on PPTX files are intertwined
   Product: LibreOffice
   Version: 7.4.5.1 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: kerems...@gmail.com

Description:
I'm using LibreOffice 7.4.5.1 on my Debian stable. However, when I open MS
Office presentation files, the texts always appear intertwined with each other.
As far as I can see, there is no transition or effect. At first, I wasn't sure
what could be causing it, but then I noticed that when I scaled up the fonts,
they got better. This is happening with all the PPTXs I've opened so far. I
think it's a font related thing because I also tried exporting the PPTX file
using strict XML from Microsoft PowerPoint, but it gave the same result.


Steps to Reproduce:
1. Open a PPTX file made with Microsoft Office.

Actual Results:
The letters appear to overlap and are impossible to read.

Expected Results:
They should be looked like a normal readable text.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.4.5.1 / LibreOffice Community
Build ID: 40(Build:1)
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: qt5 (qfont+xcb)
Locale: en-CA (en_CA.UTF-8); UI: en-US
Debian package version: 4:7.4.5-1~bpo11+1
Calc: threaded

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

[Libreoffice-bugs] [Bug 153677] It is not possible to select two or more images simultaneously

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153677

V Stuart Foote  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 34438] [feature request, FORMATTING] group selection does not work with raster images

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34438

V Stuart Foote  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 150678] [EDITING] Not possible to select multiple raster images after some text is added to the document

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150678

V Stuart Foote  changed:

   What|Removed |Added

   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=34 |
   |438,|
   |https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=15 |
   |3677|

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

[Libreoffice-bugs] [Bug 34438] [feature request, FORMATTING] group selection does not work with raster images

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34438

V Stuart Foote  changed:

   What|Removed |Added

 CC||iavs.le...@gmail.com

--- Comment #55 from V Stuart Foote  ---
*** Bug 150678 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 150678] [EDITING] Not possible to select multiple raster images after some text is added to the document

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150678

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #3 from V Stuart Foote  ---


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

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

[Libreoffice-bugs] [Bug 34438] [feature request, FORMATTING] group selection does not work with raster images

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34438

V Stuart Foote  changed:

   What|Removed |Added

 CC||jcs...@libreoffice.org

--- Comment #54 from V Stuart Foote  ---
*** Bug 153677 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 153677] It is not possible to select two or more images simultaneously

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153677

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #2 from V Stuart Foote  ---


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

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

[Libreoffice-bugs] [Bug 153653] Styles tab help page needs revision, and Assign command in Styles dialog should have a tooltip with the command name

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153653

--- Comment #5 from Commit Notification 
 ---
Seth Chaiklin committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/620bad283446c635febcdf0b4b1c60f17c2abdf8

tdf#153653 add tooltip and correct extended tip for Assign icon

It will be available in 7.6.0.

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

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

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

[Libreoffice-bugs] [Bug 153653] Styles tab help page needs revision, and Assign command in Styles dialog should have a tooltip with the command name

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153653

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:7.6.0

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

[Libreoffice-bugs] [Bug 153678] New: Better integration of JDBC in Base

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153678

Bug ID: 153678
   Summary: Better integration of JDBC in Base
   Product: LibreOffice
   Version: 7.3.7.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Base
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: prrv...@gmail.com

Description:
Hi all,

I try to integrate more JDBC driver in my jdbcDriverOOo extension:
- H2 database
- JDBC SQLite

To achieve this, is it possible to launch LibreOffice Base in debug mode so
that it displays any error when opening the database as well as when opening
and/or editing tables?

Thanks for your advices.

Actual Results:
Hi all,

I try to integrate more JDBC driver in my jdbcDriverOOo extension:
- H2 database
- JDBC SQLite

To achieve this, is it possible to launch LibreOffice Base in debug mode so
that it displays any error when opening the database as well as when opening
and/or editing tables?

Thanks for your advices.

Expected Results:
Hi all,

I try to integrate more JDBC driver in my jdbcDriverOOo extension:
- H2 database
- JDBC SQLite

To achieve this, is it possible to launch LibreOffice Base in debug mode so
that it displays any error when opening the database as well as when opening
and/or editing tables?

Thanks for your advices.


Reproducible: Always


User Profile Reset: No

Additional Info:
Hi all,

I try to integrate more JDBC driver in my jdbcDriverOOo extension:
- H2 database
- JDBC SQLite

To achieve this, is it possible to launch LibreOffice Base in debug mode so
that it displays any error when opening the database as well as when opening
and/or editing tables?

Thanks for your advices.

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

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

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103378

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

   What|Removed |Added

 Depends on||141992


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=141992
[Bug 141992] When we export pdf from Writer, we should be able to specify how
many levels of outline should be included in the bookmarks panel
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 141992] When we export pdf from Writer, we should be able to specify how many levels of outline should be included in the bookmarks panel

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141992

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

   What|Removed |Added

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


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 141858] [META] Cross-references dialog issues

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141858
Bug 141858 depends on bug 141869, which changed state.

Bug 141869 Summary: Rephrase "Insert Reference To" items
https://bugs.documentfoundation.org/show_bug.cgi?id=141869

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

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

[Libreoffice-bugs] [Bug 141869] Rephrase "Insert Reference To" items

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141869

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

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #14 from sdc.bla...@youmail.dk ---
(In reply to Jean-Baptiste Faure from comment #7)
> If I am not wrong the code is at line 356 of
You were not wrong.  Your analysis was correct. 

The patch in comment 13 addresses this issue, and adds a tooltip to the "Refer
using" window.  Closing as FIXED.

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

[Libreoffice-bugs] [Bug 141869] Rephrase "Insert Reference To" items

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141869

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

https://git.libreoffice.org/core/commit/14a065a812c8c2176b56b2baaf08ba25a2f9fa60

tdf#141869  update extended tip to reflect UI label change

It will be available in 7.6.0.

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

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

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

[Libreoffice-bugs] [Bug 141869] Rephrase "Insert Reference To" items

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=141869

Commit Notification  changed:

   What|Removed |Added

 Whiteboard|target:7.3.0|target:7.3.0 target:7.6.0

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

[Libreoffice-bugs] [Bug 104804] Help on "Export Bookmarks" and help on "Export bookmarks as named destinations" is not clear enough

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104804

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

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 150164] PDF exporter's "Export outlines as named destinations" should export outlines, not bookmarks

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150164

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

   What|Removed |Added

 Status|NEW |NEEDINFO

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

[Libreoffice-bugs] [Bug 104804] Help on "Export Bookmarks" and help on "Export bookmarks as named destinations" is not clear enough

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104804

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

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 150164] PDF exporter's "Export outlines as named destinations" should export outlines, not bookmarks

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150164

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

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=10
   ||4804,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=13
   ||3403
 Blocks||108694

--- Comment #7 from sdc.bla...@youmail.dk ---
The issue of "named destinations" was raised in bug 104804.
The control label was changed from "bookmarks" to "outline" in bug 133403.

Will leave the question to @Dieter as to whether to reopen bug 133403 and/or
mark this ticket as DUP of one of the previous bugs.


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 108694] [META] PDF export options dialog bugs and enhancements

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108694

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

   What|Removed |Added

 Depends on||150164


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=150164
[Bug 150164] PDF exporter's "Export outlines as named destinations" should
export outlines, not bookmarks
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153613] FILEOPEN DOCX: export puts page break before textbox, instead of after

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153613

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

https://git.libreoffice.org/core/commit/6515f66372afb4d2e3ec57f9c99be4c3ffb2de84

tdf#153613 DOCX: DID YOU FIX ME? unit test

It will be available in 7.6.0.

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

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

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

[Libreoffice-bugs] [Bug 108694] [META] PDF export options dialog bugs and enhancements

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108694

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

   What|Removed |Added

 Depends on||133403


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=133403
[Bug 133403] [UI] PDF export options dialog: Usage of term "bookmark" confusing
-- 
You are receiving this mail because:
You are the assignee for the bug.

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

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103378

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

   What|Removed |Added

 Depends on||104804


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=104804
[Bug 104804] Help on "Export Bookmarks" and help on "Export bookmarks as named
destinations" is not clear enough
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 104804] Help on "Export Bookmarks" and help on "Export bookmarks as named destinations" is not clear enough

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104804

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

   What|Removed |Added

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


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 150164] PDF exporter's "Export outlines as named destinations" should export outlines, not bookmarks

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150164

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

   What|Removed |Added

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

--- Comment #6 from sdc.bla...@youmail.dk ---
@Gabriel Crabbe - thanks for your report.  I might be able to address your
request, but first I want to check a few details with you.

1. Just to be sure:  the place where you want a change is found by:

File > Export as > Export as PDF > Links tab

and on the tab:  [] "Export outlines as named destinations"

2. The patch should change the word "outlines" in that label to "bookmarks"

3.  There is an extended tip for this control.  If you do not have extended
tips enabled, then press Shift+F1 (the mouse cursor gets a question mark beside
it), and hover over the line with the checkbox.

You seem to have a solid understanding of these issues.  Maybe you can evaluate
if that tip is accurate.  The tip appears to say that bookmarks are exported,
but I could not decide if the description there corresponds to the explanation
you have given here.

4. Similarly, could you kindly look at the help page for this control:

https://help.libreoffice.org/7.6/en-US/text/shared/01/ref_pdf_export_links.html

I will be happy to make corrections if specific changes can be identified.

Will set Status as NEEDINFO.  After answering these questions, then you can
change Status back to NEW.  Thanks.

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

[Libreoffice-bugs] [Bug 153534] Most bundled page styles are nonsensical and/or redundant

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153534

--- Comment #15 from Eyal Rozenberg  ---
(In reply to David from comment #13)
> But I do specify a right page if I want a section to begin only on an odd 
> number page.

Then you're assuming the style will do something it does not, because
specifying "Right page" will not affect the page numbering; nor will it insert
an extra page before your section begins (nor at section start).

... not to mention what were to happen if you need to add another page before
your existing first page of the section; or what happens if you need to make
your document RTL; etc.


Bottom line: These two styles confuse users into thinking they do something
which they do not.

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

[Libreoffice-bugs] [Bug 104468] [META] DOCX (OOXML) image-related issues

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104468
Bug 104468 depends on bug 148952, which changed state.

Bug 148952 Summary: Filesave DOCX: Alt Text field of image is lost on open in 
LO and in MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=148952

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

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

[Libreoffice-bugs] [Bug 101912] [META] Accessibility (a11y) bugs and enhancements

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=101912
Bug 101912 depends on bug 148952, which changed state.

Bug 148952 Summary: Filesave DOCX: Alt Text field of image is lost on open in 
LO and in MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=148952

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

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

[Libreoffice-bugs] [Bug 147774] CROSS REFERENCE TO HEADING: Need option to drop the final number separator in reference text

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=147774

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

   What|Removed |Added

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

--- Comment #11 from sdc.bla...@youmail.dk ---
(In reply to Eyal Rozenberg from comment #10)
> Please make that a separate ticket, 
bug 153673

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

[Libreoffice-bugs] [Bug 96039] Not possible to set shortcuts to view modes

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=96039

Gabor Kelemen (allotropia)  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |kelem...@ubuntu.com
   |desktop.org |

--- Comment #8 from Gabor Kelemen (allotropia)  ---
Checked in

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: e2d8474857e8b39efcdf21441c95ad51a8aef6e8
CPU threads: 16; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: hu-HU (hu_HU.UTF-8); UI: en-US
Calc: threaded

Now it is possible to assign shortcuts by using the search feature.

There is one problem: there are two "Normal" and "Slide Sorter" items in the
Customize - Keyboard tab, so searching for either of these gives you a 50%
chance that you assign a shortcut to the wrong one. (The second Normal and the
first Slide Sorter are the ones used in the View menu).
This should help it:
https://gerrit.libreoffice.org/c/core/+/147176

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

[Libreoffice-bugs] [Bug 151882] Theme color does not work for docx -> odt ->docx

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151882

--- Comment #4 from Regina Henschel  ---
Created attachment 185414
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185414=edit
Screenshot comparing left Writer with right Word

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

[Libreoffice-bugs] [Bug 151882] Theme color does not work for docx -> odt ->docx

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151882

--- Comment #3 from Regina Henschel  ---
Created attachment 185413
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185413=edit
File with shapes with theme color

The missing theme-folder is still a problem in Version: 7.6.0.0.alpha0+
(X86_64) / LibreOffice Community
Build ID: 9d44236a62bf59d120dda89924d0d1407b2bd52b
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

It affects not only SmartArt but ordinary shapes too. We now have loext:theme
for odt and that works for odt in the main. Exporting such file to docx
produces the correct attributes with 'schemeClr' in the markup of the shapes.
But the 'theme' folder is still missing and therefore Word uses its default
theme.

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

[Libreoffice-bugs] [Bug 153677] It is not possible to select two or more images simultaneously

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153677

--- Comment #1 from jcs...@libreoffice.org ---
May be it is similar to
https://bugs.documentfoundation.org/show_bug.cgi?id=150678

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

[Libreoffice-bugs] [Bug 150678] [EDITING] Not possible to select multiple raster images after some text is added to the document

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=150678

jcs...@libreoffice.org changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153677] It is not possible to select two or more images simultaneously

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153677

jcs...@libreoffice.org changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153677] New: It is not possible to select two or more images simultaneously

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153677

Bug ID: 153677
   Summary: It is not possible to select two or more images
simultaneously
   Product: LibreOffice
   Version: 7.4.4.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jcs...@libreoffice.org

Description:
Generally in libreoffice it is possible to select several elements by clicking
on the first one and then pressing the shift key on the other elements.
In Writer it is not possible to select two or more images simultaneously, while
in Calc, Draw or Impress it is possible.
This prevents you from being able to execute some functions, e.g. grouping or
aligning several images. 

Steps to Reproduce:
1. Insert some images in a Writer document
2. Click on one of them
3. Shift + click on any other image

Actual Results:
Only the clicked image en the step 3 is selected

Expected Results:
Both images should be selected simultaneously


Reproducible: Always


User Profile Reset: No

Additional Info:
If you perform the same steps in Calc, Draw or Impress, both images are
selected, as expected, so the incorrect behavior in Writer is not
understandable.
Some times, when try to select the images, a shadow is shown over them.
Althought it seems that both images are selected, really are not selected and
is not possible to perform any operation over them simultaneously

-
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 14a36ad49518bcb5b606b0f1640e3ca56b636e89
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: es-ES
Calc: CL threaded

-
Version: 7.4.4.2 / LibreOffice Community
Build ID: 40(Build:2)
CPU threads: 2; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: es-ES (es_ES.UTF-8); UI: es-ES
Ubuntu package version: 1:7.4.4-0ubuntu0.22.10.2
Calc: threaded

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

[Libreoffice-bugs] [Bug 153676] Page styles should include a default paragraph style like paragraph styles include a character styles

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153676

Eyal Rozenberg  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153534] Most bundled page styles are nonsensical and/or redundant

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153534

Eyal Rozenberg  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153676] Page styles should include a default paragraph style like paragraph styles include a character styles

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153676

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks||107326


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 107326] [META] Writer style bugs and enhancements

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107326

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||153676


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153676
[Bug 153676] Page styles should include a default paragraph style like
paragraph styles include a character styles
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 107833] [META] Writer paragraph style bugs and enhancements

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107833

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||153676


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153676
[Bug 153676] Page styles should include a default paragraph style like
paragraph styles include a character styles
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153676] Page styles should include a default paragraph style like paragraph styles include a character styles

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153676

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks||107833


Referenced Bugs:

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

[Libreoffice-bugs] [Bug 112703] [META] ODF (XML) bug tracker

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112703

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on|153676  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153676
[Bug 153676] Page styles should include a default paragraph style like
paragraph styles include a character styles
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108237] [META] ODF specification issues

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108237

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||153676


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153676
[Bug 153676] Page styles should include a default paragraph style like
paragraph styles include a character styles
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153676] Page styles should include a default paragraph style like paragraph styles include a character styles

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153676

Eyal Rozenberg  changed:

   What|Removed |Added

 Blocks|112703  |108237


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108237
[Bug 108237] [META] ODF specification issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112703
[Bug 112703] [META] ODF (XML) bug tracker
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 112703] [META] ODF (XML) bug tracker

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=112703

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||153676


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153676
[Bug 153676] Page styles should include a default paragraph style like
paragraph styles include a character styles
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153676] Page styles should include a default paragraph style like paragraph styles include a character styles

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153676

Eyal Rozenberg  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de
 Blocks||108576, 112703


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108576
[Bug 108576] [META] Writer page style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112703
[Bug 112703] [META] ODF (XML) bug tracker
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108576] [META] Writer page style bugs and enhancements

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108576

Eyal Rozenberg  changed:

   What|Removed |Added

 Depends on||153676


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153676
[Bug 153676] Page styles should include a default paragraph style like
paragraph styles include a character styles
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153676] New: Page styles should include a default paragraph style like paragraph styles include a character styles

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153676

Bug ID: 153676
   Summary: Page styles should include a default paragraph style
like paragraph styles include a character styles
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: eyalr...@gmx.com

Each paragraph style has an "embedded" default character style (and whether
that's implemented as specific CS features or a reference to complete CS is
immaterial as far as this bug is concerned).

Similarly, each Page Style should contain a full set of Paragraph Style
properties (or a reference to an actual Paragraph Style).

When setting a Page Style, the "Default Paragraph Style" would be that page
style's default, rather than a document-wide default.


Motivation: 

* It is customary for pages used for an Index, Table-of-Contents or Endnotes
(and no other content) to have various properties different than regular
document content pages. Some of these features are "proper" page style
features, such as the number of columns, or the use of footers or headers; but
some are aspects of the paragraph style, e.g. different font size, spacing or
margins.

* We already have this implemented for a single property, which is the text
direction. Why just that and not all other Paragraph Style properties?

* If my page style has, say, a deep/dark-color background, it stands to reason
I would want the text, by default, to have a color which contrasts with that
color. But a Page Style doesn't currently have CS properties; it could have
them if it had a default Paragraph Style (or default-paragraph-style
properties).

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

[Libreoffice-bugs] [Bug 115274] .desktop file magic number error

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115274

--- Comment #5 from RGB  ---
Problem still present on 

Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb)
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 151342] Animation sidebar rendering cut off in a displeasing manner

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=151342

--- Comment #15 from Eyal Rozenberg  ---
(In reply to Buovjaga from comment #14)
> There is bug 128180. Is there a need to keep this one open?

Well, I think so, because:

1. This bug can be fixed without 128180 being fixed. IIANM.
2. Even if 128180 is fixed, I'm not sure this bug will automatically go away.

(In reply to Heiko Tietze from comment #13)
> And both issues likely have been reported.

I'm perfectly ok with this being closed as a dupe if the appropriate issues are
located...

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

[Libreoffice-bugs] [Bug 149506] Slow start-up and opening of files since 7.3 release

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149506

--- Comment #23 from bunkem  ---
I tried the git bisect log.  Here for your info.

---
git bisect log
# bad: [2668193da8e1844ae0336dc59d3c93c6658f5d55] source
sha:ff2ba77f22b2e96f96f5537aec1705956b47583d
git bisect start 'oldest'
# status: waiting for good commit(s), bad commit known
# bad: [846a5c424a6c16dc07eefb6827b362efed5075b1] source
sha:ce69f71983a09416514f0569c6cdfbcde87d4b99
git bisect bad 846a5c424a6c16dc07eefb6827b362efed5075b1
# status: waiting for good commit(s), bad commit known
# good: [2668193da8e1844ae0336dc59d3c93c6658f5d55] source
sha:ff2ba77f22b2e96f96f5537aec1705956b47583d
git bisect good 2668193da8e1844ae0336dc59d3c93c6658f5d55
# good: [dfbe4cd519bc2ac68dc5983edefbe101971f0db5] source
sha:2284be4f80664c54fa2ef8652030aa14d63c13a2
git bisect good dfbe4cd519bc2ac68dc5983edefbe101971f0db5
# good: [a618a57be399fd8cef923fd9b4b67762a54523dd] source
sha:3d7fcf663ceece43b4648e6adee19dc6869729af
git bisect good a618a57be399fd8cef923fd9b4b67762a54523dd
# good: [673f2ac9ffb2a66e4c72036865f7ba14383f96df] source
sha:ce64e3feb72dbe8f14a5b22a6a02722b02b391b0
git bisect good 673f2ac9ffb2a66e4c72036865f7ba14383f96df
# good: [1e9e78204356ea7bcf442424bad2dcb309562ad5] source
sha:3c62f72d7eda7a2d377cf45490c8c67403d8d745
git bisect good 1e9e78204356ea7bcf442424bad2dcb309562ad5
# good: [8bedbddcf0d17aff8bb71116f8be67b28ae0ddfe] source
sha:965e6308522a21e77a4b19cafd018973b4097224
git bisect good 8bedbddcf0d17aff8bb71116f8be67b28ae0ddfe
# good: [e1d97ac3e129e2c5f26b55edc48ea560f4fd8c50] source
sha:b5eecfc708316c1d5603f5235b408ce9fc19156d
git bisect good e1d97ac3e129e2c5f26b55edc48ea560f4fd8c50
# good: [346775956106e07b0e62a1fa23ad07c52d18f1e1] source
sha:fd06b1b2689d4189fd94beade3983af4acc5ffc3
git bisect good 346775956106e07b0e62a1fa23ad07c52d18f1e1
# good: [e6e12dad792f4d2cbc690346b3115a8a8dc053df] source
sha:f4ba4c014c74d1735288fe356878d6a2effab21f
git bisect good e6e12dad792f4d2cbc690346b3115a8a8dc053df
# good: [6d2009e0522c58af3fa35929e2ff188c04d91e12] source
sha:7f791573ff32bfb5bdd082b9a23413da6ff26b76
git bisect good 6d2009e0522c58af3fa35929e2ff188c04d91e12
# good: [4b6d46d5288e2e83dae822744d3bf3e30ad12658] source
sha:68fdfc6013126526f5ba3908c5ad762f18f463cf
git bisect good 4b6d46d5288e2e83dae822744d3bf3e30ad12658
# good: [1f020ca63c2be31f94eda95f5ce38ffb7c157349] source
sha:dd5e7b2120898b96132ed4d330adb597991c1f6b
git bisect good 1f020ca63c2be31f94eda95f5ce38ffb7c157349
# good: [a5a14a42123e566a202fbb91103ae8c41dbb36e1] source
sha:b8f067dae3424c9cc2373e84c8a3465d477f9adc
git bisect good a5a14a42123e566a202fbb91103ae8c41dbb36e1
# first bad commit: [846a5c424a6c16dc07eefb6827b362efed5075b1] source
sha:ce69f71983a09416514f0569c6cdfbcde87d4b99
---

How would I start again to check as I've learned a bunch over the past couple
of hours?

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

[Libreoffice-bugs] [Bug 153534] Most bundled page styles are nonsensical and/or redundant

2023-02-16 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153534

--- Comment #14 from Eyal Rozenberg  ---
(In reply to David from comment #12)
> Left Page / Right Page has a very real use case. I use it a lot. Left page
> might get one header/footer and right pages might get another header/footer.

What happens when you need to insert an extra page before a large number of
pages, each pair of which is style Left Page and Right Page respectively? 

> For instance, if I want page numbers only on the outside edge of the page,
> how would you propose doing it without defining left versus right page
> styles?

There's a feature specifically for this purpose. In the Page Style dialog, on
the Footer tab, under "Footer on", you have: "Same contents on left and right
pages". If you uncheck it, you get what you asked for.

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

  1   2   3   >