[Bug 160275] LibreOffice Calc crashes immediately when trying to use fcitx in the input line under Wayland

[bugzilla-daemon]

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

--- Comment #16 from Michael Weghorn  ---
(In reply to Huanyu Liu from comment #14)
> I opened a new issue for fcitx5-qt:
> https://github.com/fcitx/fcitx5-qt/issues/60

Thanks a lot for the excellent analysis and even suggesting how to fix the
cause of the crash, which I see has been applied upstream now!

And thanks for moving the remaining issue to a separate bug, that's helpful.

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

[Bug 160839] "Recent Documents" file open menu items filenames from remote sources have %20 instead of spaces (URI entities not unquoted)

[bugzilla-daemon]

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

--- Comment #1 from Jeff Fortin Tam  ---
Created attachment 193875
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193875=edit
Screenshot

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

[Bug 160839] New: "Recent Documents" file open menu items filenames from remote sources have %20 instead of spaces (URI entities not unquoted)

[bugzilla-daemon]

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

Bug ID: 160839
   Summary: "Recent Documents" file open menu items filenames from
remote sources have %20 instead of spaces (URI
entities not unquoted)
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nekoh...@gmail.com

Description:
Recently opened documents from remote folders will show up urlencoded/quoted in
the recent documents files list, with a bunch of "%20" instead of spaces,
unlike local files. See attached screenshot.

Steps to Reproduce:
1. With the Nautilus file manager on Linux / GNOME, visit a SFTP GVFS mount
(i.e. you visited a sftp://someserver/some/folder/ and then opened whatever.ods
from that folder)
2. Look at the File > "Recent Documents" menu entries

Actual Results:
Lots of %20 in the filename, as per attached screenshot with the "sftp: "
prefixed item.

Expected Results:
Unquote/decode the filenames so that they show up human-readable like local
files.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 8; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: en-CA (en_US.UTF-8); UI: en-US
Flatpak
Calc: threaded

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

[Bug 160275] LibreOffice Calc crashes immediately when trying to use fcitx in the input line under Wayland

[bugzilla-daemon]

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

Huanyu Liu <1293660...@qq.com> changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|UNCONFIRMED |RESOLVED

--- Comment #15 from Huanyu Liu <1293660...@qq.com> ---
(Moved to tdf#160838, as the description is no longer accurate.)

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

[Bug 160838] New: LibreOffice does not report the correct cursor position for IME at certain places unless using gtk3 VCL plugin

[bugzilla-daemon]

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

Bug ID: 160838
   Summary: LibreOffice does not report the correct cursor
position for IME at certain places unless using gtk3
VCL plugin
   Product: LibreOffice
   Version: 24.2.1.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: 1293660...@qq.com

Description:
This bug is move from tdf#160275 to make the description more accurate.

Background information: For a few non-Latin scripts (especially Chinese and
Japanese), an IME (input method engine/editor) is needed for inputting. When an
IME is enabled, the keystrokes on the keyboard is first sent to the IME. The
IME will do the transcription and show a candidate box for you to select the
intended character sequence, as the transcription process is not one-to-one
(e.g. in Chinese Pinyin, shizi → 狮子, 十字, 师资, ...). After you select the
intended candidate, the corresponding character sequence will be inputted. For
ease of inputting, the candidate box is usually shown near the cursor of the
"host" program.

The problem is that LO does not report the correct cursor position at certain
places, so the candidate box will be shown at the wrong position (usually at
the top-left corner of the window). "Certain places" includes:
- Input line of Calc;
- Comment region (Ctrl+Alt+C) of Writer, Impress and Draw (but not Calc);
- Input region of Math.
This only happens at these certain places, and everything works well at other
places.

Furthermore, the IME has different behaviors when using different VCL plugins:
- gtk3: Everything works well (even at the places mentioned above);
- kf5, qt5, kf6, qt6, gen: The candidate box is shown at the wrong position,
but IME is still usable;
- gtk4: IME is not usable at all; every keystroke is directly sent to LO.
Again, this only happens at the places mentioned above.

I noticed that all these places have one thing in common: The cursor does not
blink. I think this should be related to the bug.

Currently, I am using the fcitx5 IME. The 5.1.4 version of fcitx5-qt had a bug
that would cause LO to crash (see tdf#160275) under Wayland, but it was fixed
in the 5.1.6 version. The current bug happens under both Wayland and X11.

Steps to Reproduce:
1. Install the fcitx5 framework and setup it according to the instructions on
the official website;
2. Launch LO (optionally with environment variable SAL_USE_VCLPLUGIN) and
navigate to any one of the above-mentioned places (e.g. comment region of
Writer);
3. Toggle the IME with keyboard shortcut (Ctrl+Space by default);
4. (Optionally) try typing something if you have installed any "usable" IMEs
(see other information below). 

Actual Results:
The candidate box is not shown at the correct position.

Expected Results:
The candidate box should appear around the cursor.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Please bear in mind that fcitx5 itself does not ship with any "usable" IMEs;
only keyboard layouts (which do not use a candidate box actually) are provided.
However, toggling the IME with keyboard shortcut will show an indicator near
the cursor, which shares the same code with the "actual" candidate box and also
fails at the above-mentioned places. You can install a "usable" IME (e.g. Rime
for Chinese, Mozc for Japanese) to summon the "actual" candidate box.

Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: 420(Build:2)
CPU threads: 16; OS: Linux 6.8; UI render: default; VCL: kf6 (cairo+wayland)
Locale: zh-CN (zh_CN.UTF-8); UI: zh-CN
24.2.2-2
Calc: threaded

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

[Bug 103370] [META] Heading Numbering bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103370
Bug 103370 depends on bug 160253, which changed state.

Bug 160253 Summary: Heading numbering wrong on file reload
https://bugs.documentfoundation.org/show_bug.cgi?id=160253

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

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

[Bug 103370] [META] Heading Numbering bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103370
Bug 103370 depends on bug 160253, which changed state.

Bug 160253 Summary: Heading numbering wrong on file reload
https://bugs.documentfoundation.org/show_bug.cgi?id=160253

   What|Removed |Added

 Status|VERIFIED|UNCONFIRMED
 Resolution|FIXED   |---

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

[Bug 160586] LibreOffice 7.6 does not load under Windows 10 64 bit.

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard| QA:needsComment|

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

[Bug 160646] GIF don't animate in edit mode; are rendered as still images

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 160641] [LOCALHELP] Explain what is multithread setting in Calc option help page

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 160639] GIF draws over itself in presentation mode

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 160634] Alternate substitution feature does not work when AAT tables are present in font

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 160636] Allow 3+ words in spelling and italicise words, using LanguageTool

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 160619] Create Separate Print Jobs for collated output fails

[bugzilla-daemon]

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

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

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

[Bug 160587] Crash in: salhelper::Thread::launch()

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 160605] Calc Sort via AU3, VBA/VBS external script doesn't sort.

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Bug 160619] Create Separate Print Jobs for collated output fails

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Bug 98077] When files are embedded (OLE) and associated with Excel, internally associate them with Calc instead

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Bug 103303] [META] Desktop integration bugs and enhancements

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=103303
Bug 103303 depends on bug 98077, which changed state.

Bug 98077 Summary: When files are embedded (OLE) and associated with Excel, 
internally associate them with Calc instead
https://bugs.documentfoundation.org/show_bug.cgi?id=98077

   What|Removed |Added

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

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

[Bug 98077] When files are embedded (OLE) and associated with Excel, internally associate them with Calc instead

[bugzilla-daemon]

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

--- Comment #20 from QA Administrators  ---
Dear chrissc.humbert,

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.

[Bug 157464] Cells formatted as percentage no longer function as numbers, and cannot even be reverted to numbers

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Bug 157464] Cells formatted as percentage no longer function as numbers, and cannot even be reverted to numbers

[bugzilla-daemon]

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

--- Comment #7 from QA Administrators  ---
Dear nats.nmr,

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.

[Bug 70289] Extension update progress bar does not work

[bugzilla-daemon]

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

--- Comment #22 from QA Administrators  ---
Dear Emir Sarı,

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.

[Bug 43275] Tooltips leave elements behind when dismissed; tooltips don't dismiss when application switch occurs

[bugzilla-daemon]

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

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

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.

[Bug 148478] FILESAVE PPTX: Audio used in slide transition has gone lost as transition sound if the audio file name contains Chinese Characters (but still exists in sound list)

[bugzilla-daemon]

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

--- Comment #13 from QA Administrators  ---
Dear Kevin Suo,

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.

[Bug 142754] Different page layout file-open ODT (from DOC) across LibO versions and causing changes on DOCX export

[bugzilla-daemon]

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

--- Comment #11 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.

[Bug 140466] Animation repeat option "Until end of slide" is the same as "Until next click"

[bugzilla-daemon]

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

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

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.

[Bug 139975] FILESAVE PPTX Slide containing mpg video generates invalid file error in PP

[bugzilla-daemon]

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

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

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Bug 107422] Buttons related to colors in the contextual groups variant of the Notebookbar

[bugzilla-daemon]

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

--- Comment #6 from QA Administrators  ---
Dear Heiko Tietze,

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.

[Bug 107419] Remove function to modify cell appearance from contextual groups Notebookbar

[bugzilla-daemon]

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

--- Comment #5 from QA Administrators  ---
Dear Heiko Tietze,

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.

[Bug 105870] EDITING: start and end buttons in navigator do the wrong thing

[bugzilla-daemon]

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

--- Comment #5 from QA Administrators  ---
Dear Gilward Kukel,

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.

[Bug 104389] Direct formatting instead of styles is used for text on table autoformat/styles

[bugzilla-daemon]

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

--- Comment #15 from QA Administrators  ---
Dear RGB,

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.

[Bug 150495] New release with fixes from osnola needed

[bugzilla-daemon]

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

--- Comment #4 from Aron Budea  ---
@David, do you think you could prepare a new libetonyek release?

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

[Bug 140541] Apple Numbers spreadsheet mangled on loading

[bugzilla-daemon]

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

Aron Budea  changed:

   What|Removed |Added

   Hardware|x86-64 (AMD64)  |All
 OS|macOS (All) |All

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

[Bug 124107] [META] Problem with Apple iWork Office Suite files

[bugzilla-daemon]

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

Aron Budea  changed:

   What|Removed |Added

 Depends on|139175  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=139175
[Bug 139175] Import from Apple Pages
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 123571] Apple Pages totally blank

[bugzilla-daemon]

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

Aron Budea  changed:

   What|Removed |Added

   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=13 |
   |9175|
 CC||sratcliffjo...@mac.com

--- Comment #12 from Aron Budea  ---
*** Bug 139175 has been marked as a duplicate of this bug. ***

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

[Bug 139175] Import from Apple Pages

[bugzilla-daemon]

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

Aron Budea  changed:

   What|Removed |Added

   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=12 |
   |3571|
 CC||aron.bu...@gmail.com
 Status|REOPENED|RESOLVED
 OS|macOS (All) |All
 Resolution|--- |DUPLICATE
 Blocks|124107  |

--- Comment #10 from Aron Budea  ---
(In reply to linus.sturm.github from comment #9)
> Therefore, I re-open this as this issue obviously hasn't been fixed.
I opened attachment 168504 in recent LibreOffice, and it showed the content, so
this seems fixed, and a duplicate of bug 123571. If you can reproduce a similar
issue, please open a new bug report.

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


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=124107
[Bug 124107] [META] Problem with Apple iWork Office Suite files
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 123571] Apple Pages totally blank

[bugzilla-daemon]

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

Aron Budea  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #11 from Aron Budea  ---
Noting here that libetonyek was updated to version 0.1.10 in LibreOffice 7.2
with the following commit:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=5471dc3238e8005fa146cfa0a81c5784ea018e95

And indeed the bug is gone since then.

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

[Bug 124107] [META] Problem with Apple iWork Office Suite files

[bugzilla-daemon]

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

Aron Budea  changed:

   What|Removed |Added

 Depends on||123571


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=123571
[Bug 123571] Apple Pages totally blank
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 123571] Apple Pages totally blank

[bugzilla-daemon]

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

Aron Budea  changed:

   What|Removed |Added

   Hardware|x86 (IA32)  |All
 Blocks||124107
 OS|Windows (All)   |All
 CC||aron.bu...@gmail.com


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=124107
[Bug 124107] [META] Problem with Apple iWork Office Suite files
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160431] Inverts webp file image when inserted

[bugzilla-daemon]

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

Adolfo Jayme Barrientos  changed:

   What|Removed |Added

 Whiteboard|target:24.8.0 target:24.2.4 |target:24.8.0
   |target:24.2.3   |target:24.2.3.2

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

[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing

[bugzilla-daemon]

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

--- Comment #16 from V Stuart Foote  ---
(In reply to Julien Nabet from comment #15)

>...
> why driverVersion appears only with GR_GL_DRIVER_VER except for
> include/third_party/vulkan/vulkan/vulkan_core.h ?

I think those are mostly leftovers from migration from OpenGL to Vulkan that
Luboš had handled. OpenGL removed from VCL, but retained some of the OpenGL
driver version used in the DENYLIST handling?

https://gerrit.libreoffice.org/c/core/+/107290
https://gerrit.libreoffice.org/c/core/+/107362
https://gerrit.libreoffice.org/c/core/+/107398
https://gerrit.libreoffice.org/c/core/+/107399

And, I'm not sure but seems like the version and os handling for the DENYLIST
will need some attention. No Windows 11 and especially if we implement testing
as uint32_t against the returned VkPhysicalDeviceProperties prop.driverVersion

vcl/source/helper/driverblocklist.cxx
vcl/inc/driverblocklist.hxx

For Vulkan, Luboš had tweaked the version string conversion there with

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

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

[Bug 132998] macOS: can't change the shape of data points in "points and lines" chart

[bugzilla-daemon]

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

--- Comment #13 from Lane Jancy  ---
Works correctly in 
Version: 6.2.8.3
Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee
Threads CPU : 8; OS : Mac OS X 10.15.4; UI Render : par défaut; VCL: osx; 
Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR
Calc: threaded
https://io-games.onl

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

[Bug 132999] Crash on macOS Catalina while scrolling and using magnification (from OS accessibility settings)

[bugzilla-daemon]

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

Lane Jancy  changed:

   What|Removed |Added

URL||https://io-games.onl/

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

[Bug 41360] FORMATTING Problem with fontsize in style when expressed in percentage

[bugzilla-daemon]

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

--- Comment #30 from Paolo Benvenuto  ---
confirmed inç

Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: 420(Build:2)
CPU threads: 16; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: en-US (C.UTF-8); UI: en-US
Ubuntu package version: 4:24.2.2-0ubuntu1
Calc: threaded

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

[Bug 160814] DOCX comments (replies) are in the wrong order

[bugzilla-daemon]

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

--- Comment #3 from Justin L  ---
A wild attempt at a fix is at https://gerrit.libreoffice.org/c/core/+/166765

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

[Bug 160822] Writer hangs on copying text with Ctrl+C

[bugzilla-daemon]

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

--- Comment #13 from Oleksandr Natalenko  ---
Thank you for checking this.

I'm not sure how this document can fail validation as it was not modified
outside of Writer.

Regarding the footnote, I think she did not enter the text of the footnote by
herself but instead copy-pasted it from a site that generates formatted
bibliography string (Grafiati). I shortened the string of course to the point
of a minimal reproducer.

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

[Bug 160837] ACCESSIBILITY: toolbar positions are incorrectly reported to AT-SPI2

[bugzilla-daemon]

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

m_a_riosv  changed:

   What|Removed |Added

   Keywords||accessibility

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

[Bug 160832] Writer and Impress don't show #ArrowWideRounded in svg

[bugzilla-daemon]

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

m_a_riosv  changed:

   What|Removed |Added

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

--- Comment #2 from m_a_riosv  ---
Reproducible
Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded
and
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ea43cbbb7371a743f470d949762a0e92f196e652
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

even worse with:
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ea43cbbb7371a743f470d949762a0e92f196e652
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; 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.

[Bug 160831] some contour lines appears in images

[bugzilla-daemon]

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

m_a_riosv  changed:

   What|Removed |Added

   Keywords||bibisectRequest, regression
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
 CC||miguelangelrv@libreoffice.o
   ||rg

--- Comment #3 from m_a_riosv  ---
Reproducible with:
Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded
and


Even the graphics have no line, in the export as PDF it looks like the line is
applied, barely visible because it is applied very thinly and with a blue
color.
Changing DPI for export doesn't help.

Not reproducible with:
Version: 7.6.6.3 (X86_64) / LibreOffice Community
Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: es-ES
Calc: CL threaded

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

[Bug 160835] Unclear meaning of "a basic total population"

[bugzilla-daemon]

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

--- Comment #4 from ady  ---
IMHO, it would help if you could link to the actual Help content (i.e.
function) we are talking about. I mean that "Value 1; value 2; ... are
arguments representing a sample taken from a basic total population" sounds as
the description of a "ValueN" argument of some specific Calc function, probably
part of the Statistical Category of functions.

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

[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing

[bugzilla-daemon]

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

--- Comment #15 from Julien Nabet  ---
(In reply to Mike Kaganski from comment #5)
> The Vulkan API documents VkPhysicalDeviceProperties and its driverVersion
> this way [1]:
> 
> > uint32_tdriverVersion;
> ...

BTW, I had read this too but when looking at source code in
workdir/UnpackedTarball/skia, by just typing:
fgrep -nR driverVersion *
here what I got:
include/third_party/vulkan/vulkan/vulkan_core.h:2775:uint32_t  
 driverVersion;
src/gpu/ganesh/gl/GrGLContext.h.orig:65:GrGLDriverVersion driverVersion()
const { return fDriverInfo.fDriverVersion; }
src/gpu/ganesh/gl/GrGLUtil.cpp:416:GrGLDriverVersion driverVersion =
GR_GL_DRIVER_UNKNOWN_VER;
src/gpu/ganesh/gl/GrGLUtil.cpp:434:driverVersion =
GR_GL_DRIVER_VER(driverMajor, driverMinor, 0);
src/gpu/ganesh/gl/GrGLUtil.cpp:453:driverVersion =
GR_GL_DRIVER_VER(driverMajor, driverMinor, 0);
src/gpu/ganesh/gl/GrGLUtil.cpp:467:driverVersion =
GR_GL_DRIVER_VER(driverMajor, driverMinor, 0);
src/gpu/ganesh/gl/GrGLUtil.cpp:480:driverVersion =
GR_GL_DRIVER_VER(driverMajor, driverMinor, 0);
src/gpu/ganesh/gl/GrGLUtil.cpp:491:driverVersion =
GR_GL_DRIVER_VER(driverMajor, driverMinor, 0);
src/gpu/ganesh/gl/GrGLUtil.cpp:512:driverVersion =
GR_GL_DRIVER_VER(driverMajor, driverMinor, driverPoint);
src/gpu/ganesh/gl/GrGLUtil.cpp:523:driverVersion =
GR_GL_DRIVER_VER(driverMajor, driverMinor, 0);
src/gpu/ganesh/gl/GrGLUtil.cpp:537:driverVersion =
GR_GL_DRIVER_VER(driverMajor, driverMinor, 0);
src/gpu/ganesh/gl/GrGLUtil.cpp:556:driverVersion =
GR_GL_DRIVER_VER(driverMajor, driverMinor, 0);
src/gpu/ganesh/gl/GrGLUtil.cpp:565:return {driver, driverVersion};
src/gpu/ganesh/gl/GrGLContext.h:65:GrGLDriverVersion driverVersion() const
{ return fDriverInfo.fDriverVersion; }
src/gpu/ganesh/gl/GrGLCaps.cpp:3747:ctxInfo.driverVersion() <
GR_GL_DRIVER_VER(367, 57, 0)) {
src/gpu/ganesh/gl/GrGLCaps.cpp:3801:ctxInfo.driverVersion() >
GR_GL_DRIVER_VER(127, 0, 0)) {
src/gpu/ganesh/gl/GrGLCaps.cpp:3889:(ctxInfo.driverVersion() <
GR_GL_DRIVER_VER(10, 30, 12) ||
src/gpu/ganesh/gl/GrGLCaps.cpp:3912:if (ctxInfo.driverVersion() <=
GR_GL_DRIVER_VER(219, 0, 0)) {
src/gpu/ganesh/gl/GrGLCaps.cpp:3919:if (ctxInfo.driverVersion() <
GR_GL_DRIVER_VER(145, 0, 0)) {
src/gpu/ganesh/gl/GrGLCaps.cpp:3951:ctxInfo.driverVersion() >
GR_GL_DRIVER_VER(53, 0, 0)) {
src/gpu/ganesh/gl/GrGLCaps.cpp:4209:ctxInfo.driverVersion() <
GR_GL_DRIVER_VER(337, 00, 0) &&
src/gpu/ganesh/gl/GrGLCaps.cpp:4222:ctxInfo.driverVersion() <
GR_GL_DRIVER_VER(355, 00, 0)) {
src/gpu/ganesh/gl/GrGLCaps.cpp:4291:ctxInfo.driverVersion() <
GR_GL_DRIVER_VER(1, 15, 0)) {
src/gpu/ganesh/gl/GrGLCaps.cpp:4455:ctxInfo.driverVersion() <
GR_GL_DRIVER_VER(571, 0, 0)) {
src/gpu/ganesh/gl/GrGLCaps.cpp:4465:ctxInfo.driverVersion() < 
GR_GL_DRIVER_VER(1, 16, 0)) {
src/gpu/ganesh/gl/GrGLCaps.cpp:4517:ctxInfo.driverVersion()  <
GR_GL_DRIVER_VER(1, 26, 0)) {
src/gpu/ganesh/gl/GrGLCaps.cpp:4547:ctxInfo.driverVersion()  <
GR_GL_DRIVER_VER(1, 19, 0)) {
src/gpu/ganesh/gl/GrGLCaps.cpp:4578:ctxInfo.driverVersion() >=
GR_GL_DRIVER_VER(2, 1, 19900)) {

why driverVersion appears only with GR_GL_DRIVER_VER except for
include/third_party/vulkan/vulkan/vulkan_core.h ?

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

[Bug 160822] Writer hangs on copying text with Ctrl+C

[bugzilla-daemon]

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

m_a_riosv  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #12 from m_a_riosv  ---
Reproducible with:
Version: 24.2.2.2 (X86_64) / LibreOffice Community
Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

It seems that the problem originates in the footnote, with the removal of the
footnote, the problem disappears. Recreating the footnote, the issue, is not
reproduced.

The file doesn't pass well the validator.
https://odfvalidator.org/


But not reproducible with:
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: ea43cbbb7371a743f470d949762a0e92f196e652
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; 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.

[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing

[bugzilla-daemon]

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

--- Comment #14 from Julien Nabet  ---
(In reply to Mike Kaganski from comment #13)
> (In reply to Julien Nabet from comment #7)
> > I've submitted https://gerrit.libreoffice.org/c/core/+/166736
> 
> Continuing the topic that we touched there: I believe, that we need to use
> the formatted string for user, and for use in the denylist file (as human
> readable); but for comparison, we should convert the formatted string back
> into the uint32_t. This would automatically resolve the problem of Intel
> having different encodings on Windows - the conversion of the string will do
> different things on Windows vs. Linux, so the same version string will turn
> into respective proper numbers.
> 
> Also, this conversion from the string into uint32_t will allow to easily
> convert current strings into their numbers (using Vulkan encoding), and then
> turn back into the proper new numbers (using NVidia or Intel encoding).

Sorry, it's confused for me. If you got a clear idea of what to do, please go
ahead. Abandoning my patch again.

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

[Bug 160827] Crash on opening certain .docx files

[bugzilla-daemon]

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

--- Comment #5 from Julien Nabet  ---
Patch on review here:
https://gerrit.libreoffice.org/c/core/+/166763

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

[Bug 124107] [META] Problem with Apple iWork Office Suite files

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=124107
Bug 124107 depends on bug 139175, which changed state.

Bug 139175 Summary: Import from Apple Pages
https://bugs.documentfoundation.org/show_bug.cgi?id=139175

   What|Removed |Added

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

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

[Bug 139175] Import from Apple Pages

[bugzilla-daemon]

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

linus.sturm.git...@hotmail.com changed:

   What|Removed |Added

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

--- Comment #9 from linus.sturm.git...@hotmail.com ---
It seems that this problem is related to an old version of a package called
'libetonyek'. See bug 123571. Therefore, I re-open this as this issue obviously
hasn't been fixed. Correct me if I've done it wrong, as I'm not very familiar
with bug reports.

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

[Bug 123571] Apple Pages totally blank

[bugzilla-daemon]

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

linus.sturm.git...@hotmail.com changed:

   What|Removed |Added

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

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

[Bug 139175] Import from Apple Pages

[bugzilla-daemon]

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

linus.sturm.git...@hotmail.com changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=12
   ||3571

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

[Bug 160837] New: ACCESSIBILITY: toolbar positions are incorrectly reported to AT-SPI2

[bugzilla-daemon]

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

Bug ID: 160837
   Summary: ACCESSIBILITY: toolbar positions are incorrectly
reported to AT-SPI2
   Product: LibreOffice
   Version: 7.6.5.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: madewokh...@gmail.com

To reproduce:
1. Open a LibreOffice application (I tested Writer and Calc).
2. Open Accerciser.
3. Browse to a toolbar button in Accerciser.

Expected behavior: Accerciser draws a rectangle over the selected button.

Actual behavior: Accerciser draws a rectangle vertically offset from the button
position.

This will draw a rectangle over the reported position of the button. The
rectangle should be in the same position as the button on screen, but it's
actually vertically offset (might be by the height of the menu bar?).

Using 7.6.5-1 binary package in Manjaro.

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

[Bug 160827] Crash on opening certain .docx files

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

 CC||nem...@numbertext.org,
   ||serval2...@yahoo.fr

--- Comment #4 from Julien Nabet  ---
The pb is precisely on this line:
2744 if (xPropertySet->getPropertyValue("_MarkAsFinal").get())

#1  0x7f209d0388c6 in com::sun::star::uno::Any::get() const
(this=0x7ffca817d5f0) at include/com/sun/star/uno/Any.hxx:687
#2  0x7f209d5ee7d5 in SfxObjectShell::ImportFrom(SfxMedium&,
com::sun::star::uno::Reference const&)
(this=0x559694cfc470, rMedium=..., xInsertPosition=empty uno::Reference)
at sfx2/source/doc/objstor.cxx:2744
#3  0x7f209d5dba75 in SfxObjectShell::DoLoad(SfxMedium*)
(this=0x559694cfc470, pMed=0x559694d151e0) at sfx2/source/doc/objstor.cxx:762
#4  0x7f209d666846 in
SfxBaseModel::load(com::sun::star::uno::Sequence
const&) (this=0x559694d02c10, seqArguments=uno::Sequence of length 15 = {...})
at sfx2/source/doc/sfxbasemodel.cxx:1980
#5  0x7f209d82a76e in (anonymous
namespace)::SfxFrameLoader_Impl::load(com::sun::star::uno::Sequence
const&, com::sun::star::uno::Reference const&)
(this=0x559691eabf70, rArgs=uno::Sequence of length 12 = {...},
_rTargetFrame=uno::Reference to ((anonymous namespace)::XFrameImpl *)
0x55969195f4b0) at sfx2/source/view/frmload.cxx:720
#6  0x7f209e5e0898 in framework::LoadEnv::impl_loadContent()
(this=0x559691ae7988) at framework/source/loadenv/loadenv.cxx:1176

László: thought you might be interested in this one since it's related to
9a5c56a9c4e04589b0a6bb710573922e459d9685
tdf#107690 OOXML import/export of setting "Open as read-only"

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

[Bug 160835] Unclear meaning of "a basic total population"

[bugzilla-daemon]

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

--- Comment #3 from Tuomas Hietala  ---
(In reply to ady from comment #2)
> 

Yes, I know what "population" means in statistics. What I don't know is what
"basic total population" is supposed to mean.

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

[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing

[bugzilla-daemon]

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

--- Comment #13 from Mike Kaganski  ---
(In reply to Julien Nabet from comment #7)
> I've submitted https://gerrit.libreoffice.org/c/core/+/166736

Continuing the topic that we touched there: I believe, that we need to use the
formatted string for user, and for use in the denylist file (as human
readable); but for comparison, we should convert the formatted string back into
the uint32_t. This would automatically resolve the problem of Intel having
different encodings on Windows - the conversion of the string will do different
things on Windows vs. Linux, so the same version string will turn into
respective proper numbers.

Also, this conversion from the string into uint32_t will allow to easily
convert current strings into their numbers (using Vulkan encoding), and then
turn back into the proper new numbers (using NVidia or Intel encoding).

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

[Bug 160835] Unclear meaning of "a basic total population"

[bugzilla-daemon]

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

--- Comment #2 from ady  ---


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

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

[bugzilla-daemon]

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

László Németh  changed:

   What|Removed |Added

 Depends on||160836


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160836
[Bug 160836] unable to resize table row height with mouse, if contains an image
which cropped by the fixed row height
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 108364] [META] Table/Row/Column/Cell management function bugs and enhancements

[bugzilla-daemon]

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

László Németh  changed:

   What|Removed |Added

 Depends on||160836


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160836
[Bug 160836] unable to resize table row height with mouse, if contains an image
which cropped by the fixed row height
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 103100] [META] Writer table bugs

[bugzilla-daemon]

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

László Németh  changed:

   What|Removed |Added

 Depends on||160836


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160836
[Bug 160836] unable to resize table row height with mouse, if contains an image
which cropped by the fixed row height
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 160836] unable to resize table row height with mouse, if contains an image which cropped by the fixed row height

[bugzilla-daemon]

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

László Németh  changed:

   What|Removed |Added

 CC||nem...@numbertext.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED
   Assignee|libreoffice-b...@lists.free |nem...@numbertext.org
   |desktop.org |

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

[Bug 160836] New: unable to resize table row height with mouse, if contains an image which cropped by the fixed row height

[bugzilla-daemon]

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

Bug ID: 160836
   Summary: unable to resize table row height with mouse, if
contains an image which cropped by the fixed row
height
   Product: LibreOffice
   Version: Inherited From OOo
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nem...@numbertext.org

Description:
Fixed row height can crop cell content, including images anchored as character.
Resizing the row height with mouse is not possible there, because the cropped
image avoids to select the horizontal border.

Steps to Reproduce:
1. open the attached document with a floating table.
2. Try to resize the bottom border of the first cell (containing an image
cropped by the fixed row height) with the mouse.

Actual Results:
It's not possible: the pointer doesn't change to double arrow indicating the
selectable cell border, also it's not possible to drag the border.

Expected Results:
Possible to drag & drop the bottom border with the mouse, resizing row height.


Reproducible: Always


User Profile Reset: No

Additional Info:
Possible workaround:

1. select the table row with the mouse by clicking in front of the cell, and
modify Size->Row Height in the context menu.

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

[Bug 56266] FILESAVE: "Track/record changes": interdependentant revision marks not correctly saved to ODT file

[bugzilla-daemon]

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

--- Comment #17 from Mike Kaganski  ---
(In reply to Commit Notification from comment #14)
> László Németh committed a patch related to this issue.
> It has been pushed to "master":
> 
> https://git.libreoffice.org/core/commit/
> 2682828f73a6c759735613ec924357424baeae24
> 
> tdf#56266 sw xmloff: fix tracked deletions in insertions

Any attempt to use this in a unit test in CppunitTest_sw_odfexport results in:

> Error: element "text:insertion" was found where no element may occur
> text:p>John 
> Doe
>  ^

So this obviously missed to add respective changes to (our extended) schema.
ODF [1] tells clearly, that text:changed-region contains a *single* element.
Currently we produce invalid ODF.


[1]
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.html#__RefHeading__1415172_253892949

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

[Bug 160686] "Left Page" and "Right Page" are nonsensical and should be removed

[bugzilla-daemon]

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

--- Comment #44 from David  ---
(In reply to Eyal Rozenberg from comment #43)
> None of that is relevant to this bug. If you believe the default styles
> should cater to this set of assumptions, please open a bug about that.

So the only explanation is that a different use of these styles (even though an
only right-hand or only left-hand page is wanted) isn't relevant and therefore
they should still be removed.

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

[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #12 from V Stuart Foote  ---
(In reply to Julien Nabet from comment #11)
> I had submitted https://gerrit.libreoffice.org/c/core/+/166736 but your idea
> seems better so I abandoned my patch/

No, your patch of skiahelper.cxx is the way to go. I don't think we should
integrate the gpuinfo.org project stuff, its just out there to get a better
handle on the driver strings and device IDs we need.

> However, I suppose using this requires more work than a simple patch
> (dealing with gbuild, make the app work for all OSes, removing parts in LO,
> adding other ones which call the external code, etc.)

Think we just need to decide if we want to test the uint32_t returned by
prop.driverVersion, or the suggested Vendor masking to render to string as in
comment 6.

> I can't help here => uncc myself.

With so much effort as you've invested in the Vulkan denylist handling, you
deserve a say in how it could be refactored--if at all.

=-=-=
another sidebar, regards the bitwise mask for extracting the Vulkan
driverVersion for Intel GPUs. So I guess we're doing the correct thing with
them?

On a Win11 laptop with Intel Iris Plus graphics that needed a driver update.
Ran the Vulkan Caps viewer, and vulkaninfo.exe, and compared to the skia.log
(of our handling of the Vulkan driver conversion

For the 27.20.100.8853 Intel driver

*Vulkan HW Capability 1.2.151 and 0.402.661 (and in DB as 100.8853)

*vulkaninfo.exe
Device Properties and Extensions:
=
GPU0:
VkPhysicalDeviceProperties:
---
apiVersion = 4202647 (1.2.151)
driverVersion  = 1647253 (0x192295)
vendorID   = 0x8086
deviceID   = 0x8a52
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = Intel(R) Iris(R) Plus Graphics

skia.log
RenderMethod: vulkan
Vendor: 0x8086
Device: 0x8a52
API: 1.2.151
Driver: 0.402.661
DeviceType: integrated
DeviceName: Intel(R) Iris(R) Plus Graphics
Denylisted: no


=-=-=-=

For the 31.0.101.2115 Intel driver

*Vulkan HW Capability 1.3.215 and 0.404.2115 (and in DB as 101.2115)

*vulkaninfo.exe
GPU0:
VkPhysicalDeviceProperties:
---
apiVersion= 4206807 (1.3.215)
driverVersion = 1656899 (0x194843)
vendorID  = 0x8086
deviceID  = 0x8a52
deviceType= PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName= Intel(R) Iris(R) Plus Graphics
pipelineCacheUUID = 7232703e-7731-4532-7a3f-79317e357c03

skia.log
RenderMethod: vulkan
Vendor: 0x8086
Device: 0x8a52
API: 1.3.215
Driver: 0.404.2115
DeviceType: integrated
DeviceName: Intel(R) Iris(R) Plus Graphics
Denylisted: noion).

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

[Bug 160835] Unclear meaning of "a basic total population"

[bugzilla-daemon]

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

--- Comment #1 from Tuomas Hietala  ---
Correction: the same string appears in two other places, too:
https://translations.documentfoundation.org/translate/libo_ui-master/scmessages/en/?q=a+basic+total+population_by=-priority%2Cposition=

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

[Bug 160835] New: Unclear meaning of "a basic total population"

[bugzilla-daemon]

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

Bug ID: 160835
   Summary: Unclear meaning of "a basic total population"
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tuomas.hiet...@iki.fi

Description:
In Calc, there's the following UI string: "Value 1; value 2; ... are arguments
representing a sample taken from a basic total population."

I have no idea what the expression "a basic total population" means. Nothing
seems to come up on a web or Wikipedia search. I assume this is a mistake of
some kind, perhaps a mistranslation from another language?

Steps to Reproduce:
1. The string on Weblate:
https://translations.documentfoundation.org/translate/libo_ui-master/scmessages/en/?checksum=56d94ade7c12a99c


Actual Results:
The string is confusing.

Expected Results:
The string is using generally accepted English statistics terminology.


Reproducible: Always


User Profile Reset: No

Additional Info:
n/a

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

[Bug 160686] "Left Page" and "Right Page" are nonsensical and should be removed

[bugzilla-daemon]

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

--- Comment #43 from Eyal Rozenberg  ---
(In reply to David from comment #42)
> OK. Then please attach ... assume ... assume ... assume..

None of that is relevant to this bug. If you believe the default styles should
cater to this set of assumptions, please open a bug about that.

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

[Bug 160834] New: Unclear meaning of "Ignore pieces of length"

[bugzilla-daemon]

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

Bug ID: 160834
   Summary: Unclear meaning of "Ignore pieces of length"
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: tuomas.hiet...@iki.fi

Description:
The UI string "Ignore _pieces of length:" is somewhat confusing and
contradictory. The following explanation is given in Help: "Set the minimum
number of characters to trigger a valid comparison."

The UI and Help are at odds here, because it's not clear whether the selected
number of characters is to be ignored (as indicated by the UI string) or if
it's the minimum amount to be taken into account (as indicated by Help)

"Pieces of length" should IMO also be reworded for clarity. I'd suggest
replacing the string with something like "Minimum number of characters to
compare" (if Help is correct) or "Maximum number of characters to ignore" (if
Help is not).

Steps to Reproduce:
1. Go to Tools -> Options -> LibreOffice Writer -> Comparison


Actual Results:
The UI string is confusing and contradicts Help.

Expected Results:
The UI string and Help are in agreement and are easy to understand.


Reproducible: Always


User Profile Reset: No

Additional Info:
n/a

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

[Bug 160827] Crash on opening certain .docx files

[bugzilla-daemon]

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

--- Comment #3 from Julien Nabet  ---
Created attachment 193870
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193870=edit
gdb bt

On pc Debian x86-64 with master sources updated today, I could reproduce this.

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

[Bug 160827] Crash on opening certain .docx files

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

   Keywords||haveBacktrace

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

[Bug 120200] [META] Update or correct help for features

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=120200
Bug 120200 depends on bug 86427, which changed state.

Bug 86427 Summary: automatic label detection needs explanation
https://bugs.documentfoundation.org/show_bug.cgi?id=86427

   What|Removed |Added

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

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

[Bug 86427] automatic label detection needs explanation

[bugzilla-daemon]

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

Olivier Hallot  changed:

   What|Removed |Added

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

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

[Bug 160686] "Left Page" and "Right Page" are nonsensical and should be removed

[bugzilla-daemon]

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

--- Comment #42 from David  ---
(In reply to Eyal Rozenberg from comment #41)
> Different margins = different page style.
Maybe the top margin is to be changed on the first page. The spacing on a
heading could be changed, but so could the page margin.

> No, you couldn't. That's the style for the first page in a sequence of
> Default-Page-Style documents. Its other uses in your document would be
> messed up.
And if you notice in my example document that the next style is set for a
default page style, which I usually set as mirrored.

> "If I want XYZ" - Define your own custom style to do more specific things
> which you want.
Why are you demanding what I do?

> 1. Again, you're suggesting a different and contradictory use for "Right
> Page". If you actually want that - open a bug about it.
> 2. No, it really couldn't, because what you described is not the style of
> "Right Page"'s, whatever that means.

OK. Then please attach a sample document so that we can all learn what a better
(i.e. simpler) procedure would be than what I have attached and so I don't run
afoul of the page style police.
   -Assume multiple chapters or sections.
   -Assume that no direct configuration is to be done by the user.
   -Assume that any header/footer information is changed only by fields.
   -Assume that each chapter or section is to begin only on a right-hand page.
   -Assume that a heading will be used to initiate a page break with the
specified style and only as a right-hand page.
   -Assume that other options may also want to be re-configured for only that
right-hand page.

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

[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

 CC|serval2...@yahoo.fr |

--- Comment #11 from Julien Nabet  ---
(In reply to V Stuart Foote from comment #10)
> As a sidebar, worth noting...
> 
> Poking around the gpuinfo.org web portal, they offer handy "capability"
> checkers for Vulkan, OpenGL, and OpenCL--each linked to optionally upload
> report to the appropriate repository.  Also host db and Android app for
> OpenGL ES (Embedded Systems).  
> 
> All seem a useful resource to recommend during QA for us to obtain reliable
> GPU device and driver info.
> 
> The gpuinfo.org Vulkan utility is here, simple unzip or appimage. 
> 
> https://vulkan.gpuinfo.org/download.php
> ...

I had submitted https://gerrit.libreoffice.org/c/core/+/166736 but your idea
seems better so I abandoned my patch/
However, I suppose using this requires more work than a simple patch (dealing
with gbuild, make the app work for all OSes, removing parts in LO, adding other
ones which call the external code, etc.)
I can't help here => uncc myself.

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

[Bug 104878] Impress works very slow with large sized GIF

[bugzilla-daemon]

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

--- Comment #63 from f...@gmx.us ---
I can confirm this bug still exists. I am using LibreOffice 24.2 with Ubuntu
24.04 LTS and putting gifs in the presentation freezes the application.

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

[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing

[bugzilla-daemon]

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

--- Comment #10 from V Stuart Foote  ---
As a sidebar, worth noting...

Poking around the gpuinfo.org web portal, they offer handy "capability"
checkers for Vulkan, OpenGL, and OpenCL--each linked to optionally upload
report to the appropriate repository.  Also host db and Android app for OpenGL
ES (Embedded Systems).  

All seem a useful resource to recommend during QA for us to obtain reliable GPU
device and driver info.

The gpuinfo.org Vulkan utility is here, simple unzip or appimage. 

https://vulkan.gpuinfo.org/download.php

They offer for macOS but not too much use as Apple Metal API are not Khronos
Vulkan API based, and few macOS installs would switch to Vulkan. Also, Patrick
L. has been handling Metal devices directly in quartz/cgutils.mm, so no
separate denylist implementation for macOS.

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

[Bug 160586] LibreOffice 7.6 does not load under Windows 10 64 bit.

[bugzilla-daemon]

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

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||r...@post.cz
 Resolution|--- |WORKSFORME

--- Comment #3 from raal  ---
Thanks for reporting. I installed LO 7.6 on ~20 of win10 machines without
problems, so I assume it's local problem and I'm closing the bug. Also see
https://wiki.documentfoundation.org/Faq/General/General_Installation_Issues_(Windows)

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

[Bug 160828] Links contained within text in XLSX spreadsheets not ctrl-clickable

[bugzilla-daemon]

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

raal  changed:

   What|Removed |Added

Version|24.2.2.2 release|4.1.0.4 release
 Ever confirmed|0   |1
 Blocks||107733
 CC||r...@post.cz
 Status|UNCONFIRMED |NEW

--- Comment #5 from raal  ---
confirm with Version 4.1.0.0.alpha0+ (Build ID:
efca6f15609322f62a35619619a6d5fe5c9bd5a)
And Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 5740d3fa83e9725a2771e5f00ba4aaf9965f0be2
CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded Jumbo


Referenced Bugs:

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

[Bug 107733] [META] Hyperlink bugs and enhancements

[bugzilla-daemon]

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

raal  changed:

   What|Removed |Added

 Depends on||160828


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=160828
[Bug 160828] Links contained within text in XLSX spreadsheets not
ctrl-clickable
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 44773] Unable to resize table row height with mouse if cursor outside of table

[bugzilla-daemon]

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

László Németh  changed:

   What|Removed |Added

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

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

[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing

[bugzilla-daemon]

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

--- Comment #9 from V Stuart Foote  ---
Regards nVidia driver versioning: this from  Sascha Willems, the Vulkan
community's maintainer of the vulkan.gpuinfo.org repository--as sourced from
nVidia [1]

   
   This is the information I got from NVIDIA :

   Starting with MSB :
   10 bits = major version (up to r1023)
   8 bits = minor version (up to 255)
   8 bits = secondary branch version/build version (up to 255)
   6 bits = tertiary branch/build version (up to 63)
   

So nVidia intends encoding of a 4-part driver version string into uint32_t of
props.driverVersion. 

I recall Lubos being particular about difference between vendor's "marketing"
driver version and the actual Vulkan driver version that we needed for the
denylist, I guess some of that is at play here since we've got to
convert/extract the version string to test.

=-ref-=
[1] https://github.com/SaschaWillems/VulkanCapsViewer/issues/2

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

[Bug 160833] FILEOPEN DOCX: Mirrored positioning of circle on the margins

[bugzilla-daemon]

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

Miklos Vajna  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
 Ever confirmed|0   |1
   Assignee|libreoffice-b...@lists.free |vmik...@collabora.com
   |desktop.org |

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

[Bug 160833] New: FILEOPEN DOCX: Mirrored positioning of circle on the margins

[bugzilla-daemon]

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

Bug ID: 160833
   Summary: FILEOPEN DOCX: Mirrored positioning of circle on the
margins
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: vmik...@collabora.com

Created attachment 193869
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193869=edit
Reproducer document

Steps to reproduce:

1) Open the attached document.

2) Look at the position of the circle shape.

Expected result: it's on the right edge of the page, like in Word.

Actual result: it's on the left edge of the page.

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

[Bug 160686] "Left Page" and "Right Page" are nonsensical and should be removed

[bugzilla-daemon]

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

--- Comment #41 from Eyal Rozenberg  ---
(In reply to David from comment #40)
> How are multiple consecutive chapters or sections to automatically be
> accounted for? 

I actually don't quite have a good grasp of the interplay of sections and page
styles in LO, considering that sections can start in the middle of a page and
can be nested.

As for chapters - that was your second question.

> The header was just an example of one possible element. What
> if margins or page layout or any other option is also wanted changed for
> only the first page for multiple chapters or sections?

Different margins = different page style.

Basically, you're just describing why custom page styles are important and
necessary.

> Yes, I could make a new style or even pick the First Page style to
> re-configure.

No, you couldn't. That's the style for the first page in a sequence of
Default-Page-Style documents. Its other uses in your document would be messed
up.

> But let's see... What might possibly be a good built-in choice
> for a name if I want to put the first page of a chapter or section on only
> the right-hand side?

"If I want XYZ" - Define your own custom style to do more specific things which
you want. When you start with a common use case and keep adding specificity, it
becomes a not-common-enough use case.

> Hmmm Could be "First Page" if that style isn't in
> use for something else in a complex document, or maybe something like "Right
> Page" might be a good description for an only right page style? 

1. Again, you're suggesting a different and contradictory use for "Right Page".
If you actually want that - open a bug about it.
2. No, it really couldn't, because what you described is not the style of
"Right Page"'s, whatever that means.

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

[Bug 136524] [META] Performance/hang/lag/high CPU issues

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=136524
Bug 136524 depends on bug 146852, which changed state.

Bug 146852 Summary: Opening Tools-Options slow because it checks GnuPG port at 
local computer
https://bugs.documentfoundation.org/show_bug.cgi?id=146852

   What|Removed |Added

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

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

[Bug 146852] Opening Tools-Options slow because it checks GnuPG port at local computer

[bugzilla-daemon]

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

kolAflash  changed:

   What|Removed |Added

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

--- Comment #6 from kolAflash  ---
Looks like the GnuPG problem was fixed between libreoffice-7.0 and
libreoffice-7.1.0.0.alpha1.

Fixed by:
https://git.libreoffice.org/core/+/d49e7c74d13f01fda923d7399eac11b83b66

But between libreoffice-7.6 and libreoffice-24.2 there's a new "search" feature
in the Options menu. And that slowed down the Options loading again. But that's
a new topic, so I'm closing this bug.

bug 49895: Add a "search" field in (non-advanced) Options dialog
https://git.libreoffice.org/core/+/a4633dadb4233ad5587bd238449671d610540c81

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

[Bug 160686] "Left Page" and "Right Page" are nonsensical and should be removed

[bugzilla-daemon]

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

--- Comment #40 from David  ---
(In reply to Eyal Rozenberg from comment #39)
> (In reply to David from comment #36)
> > And how do you propose to remove headers, for instance, on just the first
> > page?
> 
> At the same dialog, there is also an option for having a different header on
> the first page (which could be empty).
How are multiple consecutive chapters or sections to automatically be accounted
for? The header was just an example of one possible element. What if margins or
page layout or any other option is also wanted changed for only the first page
for multiple chapters or sections?

> I suggest you add a "Book Chapter First Page" style, whose Next Style is the
> "Book Page" I suggested above. It would not be one of the two alternating
> "Left Page" - "Right Page" pair.
Yes, I could make a new style or even pick the First Page style to
re-configure. But let's see... What might possibly be a good built-in choice
for a name if I want to put the first page of a chapter or section on only the
right-hand side? Hmmm Could be "First Page" if that style isn't in use for
something else in a complex document, or maybe something like "Right Page"
might be a good description for an only right page style? 

Just because the Right/Left Page styles as an alternating pair might be
considered  of little value, is that a sufficient reason to just eliminate the
pair as built-in styles when those descriptions might also fit uses other than
as an alternating pair?

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

[Bug 153306] Cursor leftovers keep being displayed when using Skia Vulkan/Metal

[bugzilla-daemon]

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

--- Comment #35 from Patrick Luby (volunteer)  ---
(In reply to lupurus from comment #34)
> For me it also happens when using zoom 100 %. The best way to reproduce the
> bug I found out, is, when you type in the text (or a lot of space
> characters), at least until the middle of the line. Then, when the cursor is
> at the end of this line, press the left arrow key several times.

I can reproduce what you see with LibreOffice 7.6.6. However, the problem is
that in the newer LibreOffice 24.2.2, I cannot reproduce what you see.

With LibreOffice 24.2.2, the only way I can reproduce the bug is by zooming a
Writer document more than 300%.

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

[Bug 160828] Links contained within text in XLSX spreadsheets not ctrl-clickable

[bugzilla-daemon]

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

ady  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

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

[Bug 160832] Writer and Impress don't show #ArrowWideRounded in svg

[bugzilla-daemon]

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

--- Comment #1 from Karl  ---
Created attachment 193868
  --> https://bugs.documentfoundation.org/attachment.cgi?id=193868=edit
The .svg file where the top arrow doesn't get displayed correctly

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

[Bug 160832] New: Writer and Impress don't show #ArrowWideRounded in svg

[bugzilla-daemon]

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

Bug ID: 160832
   Summary: Writer and Impress don't show #ArrowWideRounded in svg
   Product: LibreOffice
   Version: 24.2.2.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: karl.hoffm...@2ho.de

Description:
I created an svg in Inkscape. It is a path with an end marker. This end marker
is #ArrowWideRounded. So in total I have made an arrow in svg. When copying the
file to Writer or Impress the Arrow-End (in svg-slang: marker-end) doesn't show
up. When using a different marker-end such as #ArrowTriangleStylized it shows
up and works.
The #ArrowWideRounded also doesn't work at marker-start or marker-mid.
#ArrowTriangleStylized works in all of them

Here is a link to my svg and also the odt and odp. I have also exported pdfs
because that also doesn't work:
https://drive.google.com/drive/folders/1jjlRmzWWS9VXb6HgAV3w0mulLXd3QmVQ

The svg is called "bug.svg"

Steps to Reproduce:
1. Copy the svg into Writer/Impress
2. See that the arrow-ends on the top should-be-arrow don't show up
3. Export a pdf
4. See that the arrow-ends on the top should-be-arrow don't show up

Actual Results:
The top arrow is only a line. The bottom arrow has three arrow-ends.

Expected Results:
The three arrow ends of the top arrow should show up like on the bottom arrow,
but with a different design, like how they do in Inkscape.


Reproducible: Always


User Profile Reset: No

Additional Info:
I have also opened the .odt and .odp files with an Archive Manager. When
looking at the internally stored .svg file and opening it with Inkscape the top
arrow is correct. That suggest only the rendering of LibreOffice is wrong.

But when opening the exported PDFs in Inkscape the top arrow is just a line,
that suggest that on export the marker-ends of the top arrow get lost.

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

[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing

[bugzilla-daemon]

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

--- Comment #8 from Julien Nabet  ---
(In reply to Julien Nabet from comment #7)
> Thank you Mike for your feedback, I've submitted
> https://gerrit.libreoffice.org/c/core/+/166736 as you m

"...as you may have seen"

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