[Libreoffice-bugs] [Bug 112805] Support for "size" (optical size) OpenType table

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

Volga  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153368] Support optical size for OpenType variable fonts

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

Volga  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153369] New: dpkg: erreur: archive 'LibreOffice_7.5.0.3_Linux_x86-64_deb/' is not a regular file

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

Bug ID: 153369
   Summary: dpkg: erreur: archive
'LibreOffice_7.5.0.3_Linux_x86-64_deb/' is not a
regular file
   Product: LibreOffice
   Version: 7.5.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: m.se...@proximus.be

Hello,
I have  download the new version of LibreOffice, Unzip the donwloaded files,
an try to install the the pakage,
michel@I7:~/Logiciel$ sudo dpkg -i LibreOffice_7.5.0.3_Linux_x86-64_deb/
the response is :
dpkg: erreur: archive 'LibreOffice_7.5.0.3_Linux_x86-64_deb/' is not a regular
file
my home system;

Nom OS :   GNU/Linux
Noyau  :   #1 SMP Debian 4.19.269-1 (2022-12-20)
Relase :   4.19.0-23-amd64
Debian :   10.13   buster
Nom PC :   I7
Machine :  x86_64

Thank you
michel

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

[Libreoffice-bugs] [Bug 153368] New: Support optical size for OpenType variable fonts

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

Bug ID: 153368
   Summary: Support optical size for OpenType variable fonts
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: shanshandehongx...@outlook.com

Description:
OpenType font variation have the 'size' axis for optical fonts. In LibreOffice
this should be activated by default for variable fonts so they would be able to
produce proper rendition on documents.

If a font have both 'size' axis and 'size' feature tag, the 'size' axis should
override 'size' feature tag.

Steps to Reproduce:
-

Actual Results:
-

Expected Results:
-


Reproducible: Always


User Profile Reset: No

Additional Info:
-

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

[Libreoffice-bugs] [Bug 143344] [META] Linux Dark Mode bugs and enhancements

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

Bug 153353 Summary: When switching between freedesktop light and dark mode, 
Calc's formula bar text entry has leftover colors from the previous theme
https://bugs.documentfoundation.org/show_bug.cgi?id=153353

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 76131] Existing pinned icon on Win7/8/10/11 is taskbar invalid after re-installation/update and start menu icons are swapped (W10/W11)

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

Fridrich Strba  changed:

   What|Removed |Added

 CC|fridrich.st...@bluewin.ch   |

--- Comment #77 from Fridrich Strba  ---
.

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

[Libreoffice-bugs] [Bug 76131] Existing pinned icon on Win7/8/10/11 is taskbar invalid after re-installation/update and start menu icons are swapped (W10/W11)

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

--- Comment #76 from Kumāra  ---
(In reply to Dietmar from comment #75)
> In the context of Mike's correct remarks, I would like to extend this bug
> with a part of my bug 153337, so that I can mark it as duplicate.
> 
> In my bug I addressed on the one hand the problem of icons in the taskbar
> discussed here, however I also addressed a similar problem in the start menu
> :
> 
> If I pin links to several LibreOffice programs in the Start menu, e.g.
> LibreOffice, LibreOffice Writer and LibreOffice Calc in exactly this order,
> then these are still present and active after an update in contrast to the
> icons in the TaskBar, but the order is swapped, e.g. LibreOffice Calc,
> LibreOffice and LibreOffice Writer. So after each update I have to fix the
> icons in the taskbar and also the order of the icons in the start menu. This
> is not a big issue for single devices, but extremely annoying if you have to
> do it several hundred times a year.

I think you may rightly put the two together only if the fix is sure to address
both issues. Otherwise, you should report this (new) issue separately.

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

[Libreoffice-bugs] [Bug 153367] New: Allow numbered font weight

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

Bug ID: 153367
   Summary: Allow numbered font weight
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: shanshandehongx...@outlook.com

Description:
Currently LibreOffice could handle multiple font weights, however there are
some variable fonts required to set font weight by number, thus it's necessary
to allow users to input number to set font weight from the wght axis.

Steps to Reproduce:
-

Actual Results:
-

Expected Results:
-


Reproducible: Always


User Profile Reset: No

Additional Info:

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

[Libreoffice-bugs] [Bug 135871] Highlighting no fill is not the same as no fill; there is still direct formatting present according to paragraph style

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

Dieter  changed:

   What|Removed |Added

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

--- Comment #60 from Dieter  ---
I don't want to read the whole "book", but just want to ask you, Telesto, if
the situation is still the same with LO 7.5. And perhaps it is possible for you
to summarize previous discussion.

=> NEEDINFO

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

[Libreoffice-bugs] [Bug 153366] New: New Main LibreOffice Icons Are a Complete Failure!

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

Bug ID: 153366
   Summary: New Main LibreOffice Icons Are a Complete Failure!
   Product: LibreOffice
   Version: 7.5.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: brendieel...@brenda-make.com

Description:
The main Libreoffice icons do not function. They are broken. The Writer icon
used to look like a document. The new one? I can't tell. What the hell was it
supposed to be?

When was the last time, you wrote a document on dark blue paper?
The icons do not need to be novel or fun; they should depict what the program
should look like.

This is beyond change for change's sake--they icons don't even work.
To be nit-picky, the icons cannot even decide if there is rounded corners or
folded.

Please, put the old ones back until you come up with something that looks like
something in this world.

Did Microsoft make them for you?


Steps to Reproduce:
1. Icon should convey usage.


Actual Results:
Icon doesn't look like paper or text, or a document.


Expected Results:
Icon should look like a document, perhaps a word processor document.


Reproducible: Always


User Profile Reset: No

Additional Info:
Seriously, it bears examination on just how the icons were ever approved. I am
sorry, but if the designer cannot design a usable icon, then they shouldn't be
making them.

It doesn't matter if it's someone's first attempt, or that they are your
friend; you have to think of the project, in large.

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

[Libreoffice-bugs] [Bug 145565] (Enhancement) In Writer, make it easier to align forms to text

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

Dieter  changed:

   What|Removed |Added

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

--- Comment #3 from Dieter  ---
Marja, a new major release is available at
https://www.libreoffice.org/download/download-libreoffice/ Could you please
retest ith LO 7.5? If problem ist still present there, I will try to reproduce
it, but I must admit that steps are unclear to me.

=> NEEDINFO

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

[Libreoffice-bugs] [Bug 153330] The XFilePickerControlAccess.setLabel method does not change the name of the "Open" button (when LO Open/Save dialogs are not used).

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

Mike Kaganski  changed:

   What|Removed |Added

 OS|All |Windows (All)

--- Comment #4 from Mike Kaganski  ---
(In reply to Caolán McNamara from comment #3)

Thanks - I must had been tested with an older version (even though I thought I
checked that, but likely I confused myself). Yes, I see this in current master.

Let's mark it Windows-only; any other VCL plugin, if it happens to not
implement this, would need to have a separate bug, preferably with this in See
Also.

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

[Libreoffice-bugs] [Bug 152976] Print preview should start with right page, if document is in book view mode

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

--- Comment #6 from Dieter  ---
Having a look at bug 153127, I realized print preview toolbar for the first
time. So using this toolbar, it is of course possible to have book view as
preview. But some users (at least I) might be focused on icons in status bar.
So I'd like to suggest

1. Remove view mode icons in status bar, because you can't change them and the
selected multi-page-view indicates something wrong, if you change view mode in
toolbar

2. Change current behaviour

a) Document is in single view
Actual: Two-pages-preview and Book Preview off
Expected: Single-Page preview and Book Preview off

b) Document is in Multi-page view
Actual and expected result: Two-pages-preview and Book Preview off

c) Document is in Book view
Actual: Two-pages-preview and Book Preview off
Expected: Two-pages-preview and Book Preview on

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

[Libreoffice-bugs] [Bug 153127] "Book preview" should be separate from other page preview buttons in Print Preview toolbar

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

Dieter  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|
 CC||dgp-m...@gmx.de
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||2976

--- Comment #1 from Dieter  ---
I support that idea. I must admit, that it's the first time I've recognized
print preview toolbar. I would also recommend to remove view options in status
bar in print preview (but I will comment this in bug 152976).

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

[Libreoffice-bugs] [Bug 152976] Print preview should start with right page, if document is in book view mode

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

Dieter  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 137942] pyuno package for linux contains windows executable files

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

--- Comment #9 from lvm  ---
Still repeatable in 

Version: 7.4.4.2 / LibreOffice Community
Build ID: 85569322deea74ec9134968a29af2df5663baa21
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Calc: threaded


$ find -name *.exe
./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-9.0-amd64.exe
./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-10.0.exe
./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-14.0-amd64.exe
./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-6.0.exe
./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-10.0-amd64.exe
./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-7.1.exe
./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-9.0.exe
./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-14.0.exe
./libreoffice7.4/program/python-core-3.8.16/lib/distutils/command/wininst-8.0.exe

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

[Libreoffice-bugs] [Bug 123004] EDITING: Sheet/Named ranges/Insert - Paste all, only pastes named ranges with global scope

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

--- Comment #7 from m.a.riosv  ---
Still
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: fa1f2b7f5c65d66eaa5887acc9da5eb526570b18
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo

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

[Libreoffice-bugs] [Bug 153365] Invoking font list freezes program and after long delay crashes LibreOffice

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

--- Comment #1 from John Hale  ---
Error occurs from 7.4.2 onward through to including current 7.5

As noted, works fine on 7.3.7

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

[Libreoffice-bugs] [Bug 153365] New: Invoking font list freezes program and after long delay crashes LibreOffice

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

Bug ID: 153365
   Summary: Invoking font list freezes program and after long
delay crashes LibreOffice
   Product: LibreOffice
   Version: 4.2.0.4 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: hal...@gmail.com

Description:
Windows 64. With text program and slide program, invoking font list freezes
program and after long delay crashes LibreOffice. Have tried repeatedly with
all 7.4 releases and 7.5. One user online said that this problem did not exist
with 7.3.7. I installed 7.3.7, and it pulled up my font list immediately
without problem. The text used to experiment was very short, so file size is
not the issue. My laptop has a modern CPU and 8mb of RAM. It has handled
multiple graphics programs simultaneously with problem. The user scenario is
that many users, such as I am, need to access multiple fonts for document
design. Inability to access such a basic capability as fonts is a deal breaker.
I am willing to use the deprecated 7.3 for a reasonable time to fix this bug.
Otherwise, users needing more than basic text design will have to look
elsewhere. Thanks for your help.

Steps to Reproduce:
1.open Writer or Impress on Windows
2.type in a sentence
3.call up font list (I have, like other designers, a long list of fonts, which
however works quickly and smoothly on 7.3.7.

Actual Results:
The new versions freeze the system including other applications, then at least
80% of the time completely crashes.

Expected Results:
Font list should invoke immediately to use in modifying text.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
All as above

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

[Libreoffice-bugs] [Bug 140147] position of cursor not saved

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

--- Comment #43 from Peter  ---
I would like to add my experience to this thread.
Note: I have tried the suggested solutions to this problem, without effect.

• 19 Aug 2022 upgraded Libre Office 7.3.5.2 (x64) to 7.4.0.3 (x64)
21 Aug 2022 Noticed that this version does not properly remember where in the
document the file was closed, so that when opened, the cursor is positioned
somewhere quite remote from where it should be. Libre Office also opens in a
fixed wide and shallow height window (that is, it does not remember the window
size from the last close).

• 18 Sep 2022 Upgraded Libre Office 7.4.0.3 (x64) to 7.4.1.2 (x64). This has
fixed the opening size of the Libre Office window which was a problem from the
19 Aug 2022 7.4.0.3 (x64) upgrade. That is, the size when last closed is
remembered again, but the position in the document is still not recalled. 

• 22 Oct 2022  Upgraded Libre Office 7.4.1.1 (x64) to 7.4.2.2 (x64). This has
NOT FIXED the correct saving of the position in the document which has been a
problem from the 19 Aug 2022 7.4.0.3 (x64) upgrade.

• 15 Dec 2022 Upgraded Libre Office 7.4.2.3 to 7.4.3.2 (x64). 
This has NOT FIXED the correct saving of the position in the document which has
been a problem from the 19 Aug 2022 7.4.0.3 (x64) upgrade.

• 28 Jan 2023 Upgraded Libre Office 7.4.3.2 (x64) to:
Version: 7.4.5.1 (x64) / LibreOffice Community
Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-NZ (en_NZ); UI: en-US
Calc: threaded
This has still NOT FIXED the correct saving of the position in the document
which has been a problem from the 19 Aug 2022 7.4.0.3 (x64) upgrade.

• 04 Feb 2023 Upgraded Libre Office Version: 7.4.5.1 (x64) to:
Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-NZ (en_NZ); UI: en-US
Calc: threaded
This has still NOT FIXED the correct saving of the position in the document
which has been a problem from the 19 Aug 2022 7.4.0.3 (x64) upgrade.


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

[Libreoffice-bugs] [Bug 153127] "Book preview" should be separate from other page preview buttons in Print Preview toolbar

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

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 153297] A complex formula does not work in Calc 7.4.x; (MATCH function)

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

QA Administrators  changed:

   What|Removed |Added

   Keywords||bibisectRequest

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

[Libreoffice-bugs] [Bug 147519] 7.3.0.3 broken just crashes. 7.3.1 will work with --safe-mode.

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

--- Comment #8 from QA Administrators  ---
Dear Michael Setzer II,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 95239] Wrong ToC in Navigator and PDF when using frames

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

--- Comment #7 from QA Administrators  ---
Dear Joaquim Pedro França Simão,

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 60814] Colors of shapes change after copy+paste from one drawing to another

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

--- Comment #16 from QA Administrators  ---
Dear Clemens Eisserer,

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 77778] Writer thinly displays hidden column on Paste Special RTF paste from Calc table

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

--- Comment #17 from QA Administrators  ---
Dear Roman Kuznetsov,

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 140114] Line spacing partly lost after copy/paste

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 137942] pyuno package for linux contains windows executable files

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

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

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 123004] EDITING: Sheet/Named ranges/Insert - Paste all, only pastes named ranges with global scope

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

--- Comment #6 from QA Administrators  ---
Dear m.a.riosv,

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 122545] FILEOPEN: Error on creating script provider for Python script from location=document

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

--- Comment #13 from QA Administrators  ---
Dear spinnau,

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 117498] Ctrl+[ decreases only first cell in table

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

--- Comment #6 from QA Administrators  ---
Dear Bastien Nocera,

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 120134] Page rendering: missing pages when pasting a large table

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 108318] Copying a hyperlink into a textbox messes up its frame target

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

--- Comment #10 from QA Administrators  ---
Dear Bernd Brinker,

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 117190] Formatting is applied to outer table when Embedding a formatted table (using a table style) into a table cell

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 148872] Right-Click at the right end of Selected Text, the selection will be released

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

nobu  changed:

   What|Removed |Added

Version|7.3.0.0 beta1+  |7.3.0.0 alpha0+

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

[Libreoffice-bugs] [Bug 152430] Libreoffice hangs when cycling through open documents

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

Telesto  changed:

   What|Removed |Added

 CC||solomonchar...@me.com

--- Comment #9 from Telesto  ---
*** Bug 153348 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 153348] If I use Command-Tab on mac to change windows in LibreOffice the app freezes and I lose my work

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

Telesto  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEEDINFO|RESOLVED

--- Comment #2 from Telesto  ---


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

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

[Libreoffice-bugs] [Bug 153323] Assertion `(nLen == TextFrameIndex(COMPLETE_STRING)) ? (nIdx.get() < rText.getLength()) : (nIdx + nLen).get() <= rText.getLength()' failed

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

--- Comment #8 from Telesto  ---
(In reply to Buovjaga from comment #2)
Incremental builds on macOS tend to produce spurious asserts (and other
quirkiness) once in a while (at least for me). A make clean build might solve
the problem

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

[Libreoffice-bugs] [Bug 153364] New: libreoffice writer dont open odt document

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

Bug ID: 153364
   Summary: libreoffice writer dont open odt document
   Product: LibreOffice
   Version: 7.5.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: elias__0...@yahoo.com

Created attachment 185100
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185100=edit
pspp created document

libreoffice writer dont open odt document  in linux bullseye 11.

The writer is running and only its title bar appears and nothing else. 

No document is opened. 

document was created by pspp. I have opened many other odt pspp-saved documents
from writer normally.

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

[Libreoffice-bugs] [Bug 153363] FILEOPEN on mail attachments gives an invisible alert

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

Michael Poisson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

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

[Libreoffice-bugs] [Bug 153363] New: FILEOPEN on mail attachments gives an invisible alert

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

Bug ID: 153363
   Summary: FILEOPEN on mail attachments  gives an invisible alert
   Product: LibreOffice
   Version: unspecified
  Hardware: ARM
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mikedaf...@mpoisson.fr

Created attachment 185099
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185099=edit
Example of Alert window when problem occurs

OS is MAC OS Monterey version 12.5.1
Libre Office is version 7.2.7.2

Context : Libre Office running with at least one file open and window
displayed.

Trigger: DoubleClick on a mail attachment .ods file results in a fullscreen
empty window.`

Actually a 'file lock cannot be created Alert' is raised BEHIND the empty
window (see attachment). The Alert is normal and to be expected as attachments
are held in protected directories. The fact that it stays behind is not,
however.

The empty window cannot be closed with close button at top left because it is
waiting for the alert to be responded

Workaround : use the minimise button instead of close...

Solution: force Alert window to front.

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

[Libreoffice-bugs] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.

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

--- Comment #4 from John Mills  ---
Sorry, I should say the photo compares, Writer, Word and TextMaker.

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

[Libreoffice-bugs] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.

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

John Mills  changed:

   What|Removed |Added

 Attachment #185098|Comparison of Status bar|Comparison of Status bar
description|Icons, LibreOffice, |Icons, LibreOffice,
   |MicrosoftOffice 365,|MicrosoftOffice 365,
   |Kingsoft Office 2021|Softmaker Office 2021

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

[Libreoffice-bugs] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.

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

--- Comment #3 from John Mills  ---
This shows the difference by default of the icons in LibreOffice, Microsoft
Office and Kingsoft Office. Notice how much smaller the icons are in
LibreOffice compared to the other two.

>From Top to bottom:

LibreOffice
Microsoft Office
Softmaker Office

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

[Libreoffice-bugs] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.

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

--- Comment #2 from John Mills  ---
Created attachment 185098
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185098=edit
Comparison of Status bar Icons, LibreOffice, MicrosoftOffice 365, Kingsoft
Office 2021

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

[Libreoffice-bugs] [Bug 153360] Languagetool 7.4 not working with languages different from default language (Languagetool installed from Preferences)

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

--- Comment #2 from m.a.riosv  ---
Maybe in Mac, Menu/Edit/Preferences

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

[Libreoffice-bugs] [Bug 153360] Languagetool 7.4 not working with languages different from default language (Languagetool installed from Preferences)

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

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
It works for me, except for a few single words, like 'lkjafljks'.

Version: 7.4.5.1 (x64) / LibreOffice Community
Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: threaded
and
Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL threaded

Please test if you have the languages available with options enable,
Menu/Tools/Options/Language Settings/Writing Aids - Available Language Modules
- Edit

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

[Libreoffice-bugs] [Bug 142018] [EMF] Few Arcs with different pens: wrong line width for the 3rd arc

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

Bartosz  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |gan...@poczta.onet.pl
   |desktop.org |

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

[Libreoffice-bugs] [Bug 153355] Merging vertically adjacent cells turns a formula into data if the formula is the lower cell in the merge

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

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #3 from m.a.riosv  ---
Reproducible, the problem occurs by merging the cells vertically, not
horizontally.

Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

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

[Libreoffice-bugs] [Bug 153349] Missing Write lines

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

m.a.riosv  changed:

   What|Removed |Added

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

--- Comment #1 from m.a.riosv  ---
Please attach a sample file.

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

[Libreoffice-bugs] [Bug 153297] A complex formula does not work in Calc 7.4.x; (MATCH function)

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

m.a.riosv  changed:

   What|Removed |Added

   Keywords||regression
   Severity|normal  |critical

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

[Libreoffice-bugs] [Bug 153362] New: Dead link in ooxml-export-notes.txt

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

Bug ID: 153362
   Summary: Dead link in ooxml-export-notes.txt
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
   URL: https://opengrok.libreoffice.org/xref/core/oox/source/
export/ooxml-export-notes.txt?r=c7008197#23
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rb.hensc...@t-online.de

The link [1] in line 23 of
https://opengrok.libreoffice.org/xref/core/oox/source/export/ooxml-export-notes.txt?r=c7008197#23
is dead.

[1] http://www.asahi-net.or.jp/~eb2m-mrt/ooxml/dependencies.html

Does someone know, what kind of information it had?

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

[Libreoffice-bugs] [Bug 146988] Opening at cursor position doesn't work in large documents (User Data must be entered)

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

--- Comment #19 from MR Zenwiz  ---
This remains unfixed in LO 7.5:

Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 32; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Last I saw this was supposed to be fixed in 7.5 and it is not.

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

[Libreoffice-bugs] [Bug 107158] [META] Notebookbar Groupedbar

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

Bug 153358 Summary: Wrong redimensioning of Groupedbar compact toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=153358

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153358] Wrong redimensioning of Groupedbar compact toolbar

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

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org
 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED

--- Comment #5 from Stéphane Guillou (stragu) 
 ---
I am pretty sure this is a duplicate of the regression described in bug 153078.
Marking as such, but please set back to New if a master build that include
bcf9e47791d5b3e1d6a75c73f3b8c9940abda8eb still reproduces it. (Stuart's version
did not have that commit.)

Fix will be available in 7.5.1 too.

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

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

[Libreoffice-bugs] [Bug 153317] MySQL/MariaDB direct connection: Content of field type 'Bit' isn't shown in Tools → SQL

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

--- Comment #3 from jcs...@libreoffice.org ---
I can reproduce this also in Windows 11

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

MariaDB 10.10 (x64)

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

[Libreoffice-bugs] [Bug 153229] [RFE] Please provide a user preference to disable inheriting the system UI theme

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

--- Comment #17 from derei  ---
I've been having trouble with this behavior of LO picking from W10 theme for
the past 2 or 3 releases.
So, yes... Please be considerate and mindful towards the user by offering an
option to select theme. Most apps have system/light/dark, so then user can
decide.

I prefer the light version of LO, even if i'm using the dark mode for Windows.

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

[Libreoffice-bugs] [Bug 75331] FILEOPEN: DOCX - floating table with text wrapping 'around' and vertical position relative to 'page' position is wrong (see Comment 15)

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

--- Comment #29 from Ari Latvala  ---
Created attachment 185097
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185097=edit
LO 7.5 vs Word two page view comparison

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

[Libreoffice-bugs] [Bug 75331] FILEOPEN: DOCX - floating table with text wrapping 'around' and vertical position relative to 'page' position is wrong (see Comment 15)

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

--- Comment #28 from Ari Latvala  ---
Layout of the example document still very different on LO 7.5 when compared
outlook on Word. Screenshot added to the case showing both side by side.

Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: c21113d003cd3efa8c53188764377a8272d9d6de
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: fi-FI (fi_FI); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 75331] FILEOPEN: DOCX - floating table with text wrapping 'around' and vertical position relative to 'page' position is wrong (see Comment 15)

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

--- Comment #27 from Ari Latvala  ---
Created attachment 185096
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185096=edit
Layout LO 7.5 vs Word, still very wrong on LO 7.5

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

[Libreoffice-bugs] [Bug 153361] New: Theme color set has unsuitable lighten for background colors

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

Bug ID: 153361
   Summary: Theme color set has unsuitable lighten for background
colors
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rb.hensc...@t-online.de

Open attachment 185094 from bug 153359.

The slide shows a screenshot of the theme color set in PowerPoint. The left
shape uses the first from left theme color, a text color; the right shape uses
the third from left theme color, a background color.

Look at the light/darken values for the theme color of the right shape.
PowerPoint provides the light/darken values
darken 10%
darken 25%
darken 50%
darken 75%
darken 90%

LibreOffice provides the light/darken values
lighten 80%
lighten 60%
lighten 40%
darken 25%
darken 50%

Problems:
A) The theme color background colors in MS Office are light and therefore it
makes no sense to lighten them even more.

B) If LibreOffice uses different value than MS Office, the chosen color is not
contained in the set shown to the user.

[There is no problem with the colors themselves, because lighten and darken is
not part of the theme but described by separate attributes. Besides ±1 off
sometimes the colors are correct.]

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

[Libreoffice-bugs] [Bug 94911] Autocorrect: em dash doesn't form after closing parenthesis

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

--- Comment #9 from spikeo...@gmail.com ---
Just started using new Writer version. This feature stopped working. I believe
the troggering event was an ending quotation mark. Once the auto-em flipped
off, I can't get it flipped back on! And the two -- looks very weird now, too.

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

[Libreoffice-bugs] [Bug 153360] New: Languagetool 7.4 not working with languages different from default language (Languagetool installed from Preferences)

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

Bug ID: 153360
   Summary: Languagetool 7.4 not working with languages different
from default language (Languagetool installed from
Preferences)
   Product: LibreOffice
   Version: 7.4.4.2 release
  Hardware: ARM
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: grass...@gmail.com

Created attachment 185095
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185095=edit
Various text showing the bug

Hi, since the integration of LT in LO there is new bug which makes the use of
LT in LO very difficult.

When I am using strings of text in Latin, French, Italian and German within a
paragraph in Spanish for ex. LT struggles to proof the text and sometimes does
not specify what mistake it is underlining, sometimes it suggests corrections
in Spanish.

Sometimes if the text in the Foreign language starts in a new paragraph the bug
is gone, others it persists (such as in the case of Latin tex).

Version: 7.4.4.2 / LibreOffice Community
Build ID: 85569322deea74ec9134968a29af2df5663baa21
CPU threads: 8; OS: Mac OS X 13.2; UI render: default; VCL: osx
Locale: it-IT (en_IT.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 153344] The size of icons in the status bar should be increased to at least 16px and the height of the status bar adjusted to allow this.

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

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #1 from V Stuart Foote  ---
The icons are of course not 10px they are 16px with padding.

But, it could be helpful to provide an Icon Size option for the status
bar--similar to the Tools -> Options -> View selectors for Toolbar, Notebookbar
and Sidebar-- where UI responds to icons size of: Small (16px), Large (24px) or
Extra Large (32px), or as scaled for HiDPI.

On Large icon selection, text size should probably increase and more data
elements would be hidden from view on the Status bar, continuing to use current
element collapse sequence.

So reasonable.

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

[Libreoffice-bugs] [Bug 153359] New: Theme color UI mess with background <-> text labels

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

Bug ID: 153359
   Summary: Theme color UI mess with background <-> text labels
   Product: LibreOffice
   Version: 7.6.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rb.hensc...@t-online.de

Created attachment 185094
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185094=edit
Shapes using theme colors

Open attached file. It contains two shapes. The text in the shape is a quote of
the label I see in PowerPoint.

Now go to the area fill dialog and look at the labels you get in LibreOffice.

"Text 1"   becomes  "Background - Dark 1"
"Background 2" becomes "Text - Light 2".

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

[Libreoffice-bugs] [Bug 150932] FILESAVE DOCX Underlined trailing spaces not drawn

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

raal  changed:

   What|Removed |Added

 CC||r...@post.cz

--- Comment #5 from raal  ---
Created attachment 185093
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185093=edit
test file

test file created in LO 7.6.
This file is without underlined trailing spaces in word 2010, but with
Underlined trailing spaces in office.com => looks like word's problem.

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

[Libreoffice-bugs] [Bug 153352] Promote/Demote level list should be in the Tabbed interface

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

V Stuart Foote  changed:

   What|Removed |Added

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

--- Comment #1 from V Stuart Foote  ---
+1, for lists in a textbox we do a layout adjustment rather than an outline
adjustment now.

So, would replace the Tabbed NB use of

.uno:DecrementIndent
.uno:IncrementIndent

to instead use

.uno:OutlineLeft
.uno:OutlineRight

to match usage in the SB Properties "Lists" panel.

But do we still need the layout adjustment (e.g. for graphical bullets)?

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

[Libreoffice-bugs] [Bug 153339] Feature request: Add option to NOT round up very large numbers or any numbers

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

--- Comment #2 from NRL  ---
Created attachment 185092
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185092=edit
Difference between a number and text


Hi,

I still cannot get the number.

as a number I get:
5254615415121512155
5461154115994554615
---
(206,538,700,873,042,000.00)

as plain text I get:
5254615415121512155
5461154115994554615
---
-2.06538700873042E+17

In plain text I cannot increase the number of decimal places.
How do I get the exact number this way?
What am I doing wrong?
I don't understand?
I'm sorry that I'm stupid.


Thanks for getting back to me so quickly.

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

[Libreoffice-bugs] [Bug 149728] LibreOffice 7.3.3 and above: Locally Integrated Menu (LIM) disappears with kf5 and material-decoration theme

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

--- Comment #12 from rom1...@gmail.com ---
This looks like a related bug in the LO flatpak repo:
https://github.com/flathub/org.libreoffice.LibreOffice/issues/63

As I understand it:
- appmenu doesn't work with Gtk apps under KDE+Wayland¹ in general
- using the kf5 VCL backend could work around the issue (but this backend seems
absent from/broken in the flatpak distribution)
- (at least on my machine) the Gtk VCL backend doesn't ensure that the menu bar
is displayed in-app under KDE+Wayland, which is unlike every other Gtk apps
(AFAICT)

Perhaps this last point could be improved upon, if LO could detect that it's
running under wayland, and make sure that an in-app menu is shown in this case?



¹: https://bugs.kde.org/show_bug.cgi?id=424485

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

[Libreoffice-bugs] [Bug 153357] Can't Type or See Characters in New LibreOffice Writer

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

Julien Nabet  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #2 from Julien Nabet  ---
Some info here:
https://wiki.documentfoundation.org/QA/FirstSteps

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

[Libreoffice-bugs] [Bug 153341] Copied HTML text which uses the alpha channel is pasted either without it (when rgb(r g b / a) notation is used) or without any color (when rgba(r, g, b, a) notation is

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

Julien Nabet  changed:

   What|Removed |Added

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

--- Comment #1 from Julien Nabet  ---
On pc Debian x86-64 with master sources updated today, I could reproduce this.

I gave a try with https://gerrit.libreoffice.org/c/core/+/146546

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

[Libreoffice-bugs] [Bug 107575] [META] Number format bugs and enhancements

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

Bug 153023 Summary: NatNum12 number format (spell out): thousand separator 
should be disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=153023

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153357] Can't Type or See Characters in New LibreOffice Writer

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

V Stuart Foote  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||vsfo...@libreoffice.org
 Status|UNCONFIRMED |NEEDINFO

--- Comment #1 from V Stuart Foote  ---
Please reset your user profile and retest.

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

[Libreoffice-bugs] [Bug 107158] [META] Notebookbar Groupedbar

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

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||153358


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153358
[Bug 153358] Wrong redimensioning of Groupedbar compact toolbar
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153358] Wrong redimensioning of Groupedbar compact toolbar

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

V Stuart Foote  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 OS|macOS (All) |All
 Blocks||107158
 CC||heiko.tietze@documentfounda
   ||tion.org,
   ||kain...@gmail.com,
   ||vsfo...@libreoffice.org
 Ever confirmed|0   |1

--- Comment #4 from V Stuart Foote  ---
Confirmed 
Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: d8e6b488ceaff7c88856ebcfcfec14d2d8cd7652
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

The vcl canvas looks to be mispositioned on redraw. Screen draw overwrites the
MUFFIN Groupedbar Comact UI elements aligned with the left margin of the
document.

I can force it to redraw the Notebook Bar simply expanding the Styles listbox
which is still showing.

@Heiko, Andreas can you think of who'd be able to look at this?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107158
[Bug 107158] [META] Notebookbar Groupedbar
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 146468] Use same border preset tooltips between toolbar and sidebar

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

Radhey Parekh  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

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

[Libreoffice-bugs] [Bug 146468] Use same border preset tooltips between toolbar and sidebar

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

--- Comment #4 from Radhey Parekh  ---
I would like to look into this. One doubt, till what index, do we need to
assign the RID_SVXSTR to the code line? Like you have started from (0,...) then
'(1,)', so till which index we need to assign this? Thanks :)

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

[Libreoffice-bugs] [Bug 153335] Establishing a keyboard shortcut is doubly counter-intuitive

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

--- Comment #8 from V Stuart Foote  ---
While here a duplicate of bug 115527 (and its dupes), please note the UI
function of the Customize dialog's Keyboard panel is equally to make shortcut
assignments, but also to inspect assignments already in place.

The listing of Keys (those available to Shortcut assign) is sequential and
logically grouped. While filtering might be useful, a search against the Keys
would be of limited use.

Actions/Functions can be filtered by the Category a function is
assigned/performs, and at the 5.4 release actions/functions can be searched by
name.  

Where a function has an shortcut key assignment made that assignment is
indicated in the lower right Keys panel following search--to help (along with
the pop-up description) to identify the correct function.

So in practice the Shortcut Keys panel on top makes the most sense: both to
visually review existing assignments, and to select the shortcut that would be
modified/assigned.

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

[Libreoffice-bugs] [Bug 153358] Wrong redimensioning of Groupedbar compact toolbar

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

--- Comment #3 from Vincent Boudry  ---
Created attachment 185091
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185091=edit
Screenshot of the standard toolbar

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

[Libreoffice-bugs] [Bug 153358] Wrong redimensioning of Groupedbar compact toolbar

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

--- Comment #2 from Vincent Boudry  ---
Created attachment 185090
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185090=edit
Screenshot of compressed toolbar

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

[Libreoffice-bugs] [Bug 153358] Wrong redimensioning of Groupedbar compact toolbar

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

--- Comment #1 from Vincent Boudry  ---
Created attachment 185089
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185089=edit
Document model

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

[Libreoffice-bugs] [Bug 153358] New: Wrong redimensioning of Groupedbar compact toolbar

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

Bug ID: 153358
   Summary: Wrong redimensioning of Groupedbar compact toolbar
   Product: LibreOffice
   Version: 7.5.0.0 beta1+
  Hardware: x86-64 (AMD64)
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: vincent.bou...@in2p3.fr

Description:
In Writer, unsing the attached model, the Groupedbar Compact toolbar is
resized, as is the window was too small after the cursor is moved to a place
with a different style.

Steps to Reproduce:
1.Select View > User Interface > Groupedbar Compact; then apply to all.
2.Create a new Writer document using the attached 
3.Go at the end of the docuement. Type Cmd-0 to have text in the Text Body
style. 
4.Input any text
5.Type return
6.Input any text and press cmd-1 to switch to "Heading 1"



Actual Results:
The toolbar was spanning the full window.
After step 6, it is squeezed (see screen shot).
The toolbar size and span can be restored by resizing the window.


Expected Results:
Not change in the size of the toolbar


Reproducible: Always


User Profile Reset: Yes

Additional Info:
This might be related to the fonts, as this doesn't seem to occur with the
default document model.

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

[Libreoffice-bugs] [Bug 107351] Search on the dialog Shortcut

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

V Stuart Foote  changed:

   What|Removed |Added

 Whiteboard||target:5.4.0

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

[Libreoffice-bugs] [Bug 85976] Feature Request - Add "Remove Duplicates" button to LibreOffice / filtering showing duplicates is too complicated

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

Rafael Lima  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 150936] CALC MENU>DATA>More FILTER s> Advanced FILTER >options>No duplicates Duplicates the first item in the selection

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

Rafael Lima  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 153357] New: Can't Type or See Characters in New LibreOffice Writer

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

Bug ID: 153357
   Summary: Can't Type or See Characters in New LibreOffice Writer
   Product: LibreOffice
   Version: 7.5.0.3 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: will.kaufh...@gmail.com

Description:
When I try to type in a new document no characters apear

Steps to Reproduce:
1.Open a new document
2.Go to type and nothing appears
3.characters are counted at the bottom

Actual Results:
open a new document and I can't type and nothing apears

Expected Results:
should be able to see characters


Reproducible: Always


User Profile Reset: No

Additional Info:
I'm in dark mode for windows 10

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

[Libreoffice-bugs] [Bug 41560] [META] Keyboard shortcuts tab of Customization dialog

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

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||153335


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=153335
[Bug 153335] Establishing a keyboard shortcut is doubly counter-intuitive
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 41560] [META] Keyboard shortcuts tab of Customization dialog

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

Bug 153335 Summary: Establishing a keyboard shortcut is doubly counter-intuitive
https://bugs.documentfoundation.org/show_bug.cgi?id=153335

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 115527] Redesign of the keyboard tab of the Customization dialog

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||nicholasj...@mailfence.com

--- Comment #12 from V Stuart Foote  ---
*** Bug 153335 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 153335] Establishing a keyboard shortcut is doubly counter-intuitive

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

V Stuart Foote  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 Blocks||41560

--- Comment #7 from V Stuart Foote  ---


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


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=41560
[Bug 41560] [META] Keyboard shortcuts tab of Customization dialog
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 107351] Search on the dialog Shortcut

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||vsfo...@libreoffice.org
 Resolution|WORKSFORME  |FIXED

--- Comment #3 from V Stuart Foote  ---
Search for function to assign to keyboard shortcuts implemented in:

https://gerrit.libreoffice.org/39356

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

[Libreoffice-bugs] [Bug 153294] Use copy_if, find_if or remove_if to simplify loops

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

Radhey Parekh  changed:

   What|Removed |Added

 CC||radhey.par...@gmail.com

--- Comment #1 from Radhey Parekh  ---
I would like to work on this as I've implemented this in one of my patches.
Also, can you please provide me the code pointer to start on? Thanks.

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

[Libreoffice-bugs] [Bug 150734] Filter to exclude empty cells on Pivot Table still shows empty cells when deselected

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

Colin  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 153335] Establishing a keyboard shortcut is doubly counter-intuitive

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

--- Comment #6 from V Stuart Foote  ---
(In reply to nicholasjoll from comment #4)

And that is why it is documented, for when visual inspection may not be
sufficient. 

Establishing or overriding/modifying keyboard shortcut navigation is NOT an
inherently trivial or intuitive action. 

In other words we really do prefer that users RTM.

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

[Libreoffice-bugs] [Bug 153335] Establishing a keyboard shortcut is doubly counter-intuitive

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

--- Comment #5 from nicholasj...@mailfence.com ---
Here is what I suggest.

A) Move the 'Shortcut keys' section to the top of the window and rename it to:
'Keyboard shortcut to assign. (Select shortcut or type it.)'. Or something like
that.

B) Within that same section - the one currently entitled 'Shortcut keys' - have
a box labelled, 'Type key(s)'; that box should accept key combinations and
display them. (I imagine there might be some difficulty implementing this but
other software has managed it.)

C) Change the 'Modify' button to read 'Assign'. Better: have it read 'assign'
when at present no function is assigned to they key combination, and have it
read 'modify' otherwise. Or something like that.

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

[Libreoffice-bugs] [Bug 153335] Establishing a keyboard shortcut is doubly counter-intuitive

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

--- Comment #4 from nicholasj...@mailfence.com ---
@V Stuart Foote

Thank you for the links to documentation.

I take it that by, 'Select Key to target' you mean: select the key from the
list that appears under the heading, 'Shortcut Keys'.

Forgive me, but I remain unconvinced that the current procedure is intuitive.
Here is why.

i) The procedure has one start at the _the bottom_ of the window (with
'Category' and 'Function') and subsequently move to the _the top_ of the window
(to 'Shortcut Keys'. (Or such anyway was the order of actions that you
proposed.)

ii) In the 'Shortcut keys' box, one cannot _type_ a key combination. Rather one
has to scroll (and scroll some more) and then select a key.

iii) Clicking a button labelled 'Modify' in order to _create_ a keyboard
shortcut _ex nihilo_ does not seem intuitive.

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

[Libreoffice-bugs] [Bug 153353] When switching between freedesktop light and dark mode, Calc's formula bar text entry has leftover colors from the previous theme

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

Caolán McNamara  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |caol...@redhat.com
   |desktop.org |

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

[Libreoffice-bugs] [Bug 153353] When switching between freedesktop light and dark mode, Calc's formula bar text entry has leftover colors from the previous theme

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

Caolán McNamara  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

--- Comment #3 from Caolán McNamara  ---
https://gerrit.libreoffice.org/c/core/+/146545 to handle that

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

[Libreoffice-bugs] [Bug 153353] When switching between freedesktop light and dark mode, Calc's formula bar text entry has leftover colors from the previous theme

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

Caolán McNamara  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

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

[Libreoffice-bugs] [Bug 150734] Filter to exclude empty cells on Pivot Table still shows empty cells when deselected

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

Colin  changed:

   What|Removed |Added

 Attachment #182472|0   |1
is obsolete||

--- Comment #4 from Colin  ---
Created attachment 185088
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185088=edit
Sample pivot table

Try to exclude the EMPTIES with the filter on column 1 "Name"
Observe that nothing changes all the empties are still producing values in
columns 2,3 & 4
Exclude or re-include any of the other Names in column 1 and observe how the
other columns respond approriately.
I would expect a subtotal anywhere there are groups say "tender" or "Juicy"

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

  1   2   3   >