[Libreoffice-bugs] [Bug 144396] page layout footnotes and images / frame conflict

[bugzilla-daemon]

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

--- Comment #2 from Elmar  ---
Created attachment 174914
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174914=edit
pdf of he doc

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

[Libreoffice-bugs] [Bug 144396] page layout footnotes and images / frame conflict

[bugzilla-daemon]

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

--- Comment #1 from Elmar  ---
Created attachment 174913
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174913=edit
example doc see page 5 figure 5

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

[Libreoffice-bugs] [Bug 144396] New: page layout footnotes and images / frame conflict

[bugzilla-daemon]

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

Bug ID: 144396
   Summary: page layout footnotes and images / frame conflict
   Product: LibreOffice
   Version: 7.3.0.0 alpha0+ Master
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rob...@iafrica.com

Description:
If an image / frame will still fit within page boundaries, it can overlay
footnotes

get same result in 
Version: 6.4.7.2
Build ID: 1:6.4.7-0ubuntu0.20.04.1

Steps to Reproduce:
1.created document
2.frame/image just fits into a page, but there are footnotes
3.

Actual Results:
frame overlays footnotes

Expected Results:
image/frame should move to next page


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-GB
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: 4cd3ce9848aa039b8d443a1257d1298231680b01
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-GB
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time:
2021-09-06_04:39:11
Calc: threaded

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

[Libreoffice-bugs] [Bug 144377] Dates are not correctly auto-extrapolated if exclude days

[bugzilla-daemon]

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

Mike Kaganski  changed:

   What|Removed |Added

 Resolution|--- |NOTABUG
 Status|REOPENED|RESOLVED

--- Comment #6 from Mike Kaganski  ---
(In reply to buggymcbug from comment #5)
> > LOL. It does not depend on "my" definition; it is what standard say, and 
> > what is implemented in software.
> 
> I'm afraid the standard agrees with me. This part of the spec:
> https://datatracker.ietf.org/doc/html/rfc6350#section-4.3.1

The only standard that is discussed here is ODF; you constantly try to bring
unrelated matters into discussion; you started mentioning ISO 8601 etc. I
mentioned the *implemented* standard - and it is ODF 1.3 currently.

The relevant part there is ODF 1.3 part 4 Formula sect. 4.3.3 Date [1]:

> Date is a subtype of Number.
> Date is represented by an integer value.
> A serial date is the expression of a date as the number of days elapsed from
> a start date called the epoch.

This definition explicitly says that dates, as a data sub-type in spreadsheets
implementing ODF, are measured in *days*. They are *not* measured in months, in
ISO strings, or in any other unit of your choice. Whenever you enter *anything*
that Calc should convert to a date, it *must* convert it to "the number of
*days* elapsed from a start date called the epoch". It means that your second
argument about false precision is wrong premise, too.

Closing NOTABUG. Please don't reopen based on arbitrary citations from
unrelated places. Thanks.

[1]
https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part4-formula/OpenDocument-v1.3-os-part4-formula.html#__RefHeading__1017888_715980110

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

[Libreoffice-bugs] [Bug 144378] Calc: Characters rotated when printed in Asian layout mode of vertical writing

[bugzilla-daemon]

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

--- Comment #12 from JO3EMC  ---
(In reply to Ming Hua from comment #11)
> Bug 144222 looks very similar to this, would the kind people here take a
> look at that one as well?  Thanks.

It's certainly a problem that's happening in close position, but the phenomenon
is a bit different and it seems difficult to tell if it's related at this
point.

This issue points to character rotation, and Bug 144222 points to character
placement.
Also, this issue occurs when printing, not PDF export.

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

[Libreoffice-bugs] [Bug 144088] SpreadSheetML (Excel 2003 XML) mixed up styles

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 144087] Finder screen is "blocked" on Mac - Unable to see my desktop

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 144086] Custom List Styles associated with Paragraph Styles have no effect.

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 144082] Stylist: Make styles family selection a dropdown (and remove the CS)

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 144081] Stylist: CS filter moves below canvas on resizing via the splitter (only gtk3)

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 144080] Stylist: Fill-mode button reverts to the actual PS in new Text Styles view

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 144079] Stylist: New Text Styles view misses interactions for CS

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 144071] Some bugs during export pages to pdf

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

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

[Libreoffice-bugs] [Bug 140287] Bar chart user-defined data range colour not retained between instances of opening the document

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 140287] Bar chart user-defined data range colour not retained between instances of opening the document

[bugzilla-daemon]

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

--- Comment #3 from QA Administrators  ---
Dear step...@swabey.co,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 140204] This software crashed when I was opening Libreoffice base.

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 140204] This software crashed when I was opening Libreoffice base.

[bugzilla-daemon]

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

--- Comment #3 from QA Administrators  ---
Dear 2005gouravsoni,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 140092] CRASH when trying to reformat table

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 140092] CRASH when trying to reformat table

[bugzilla-daemon]

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

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 138677] LO Writer crashes when length of Table of Contents reaches a Page Break

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 138677] LO Writer crashes when length of Table of Contents reaches a Page Break

[bugzilla-daemon]

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

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 134580] Problem with the incorrect display of lists in all LibreOffice programs on 4k displays

[bugzilla-daemon]

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

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 134580] Problem with the incorrect display of lists in all LibreOffice programs on 4k displays

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 134086] can't delete is using cell style. can't select and click is delete menu.

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 134086] can't delete is using cell style. can't select and click is delete menu.

[bugzilla-daemon]

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

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 113117] [META] Windows installer/uninstaller bugs and enhancements

[bugzilla-daemon]

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

Bug 130771 Summary: Uninstalling LibreOffice corrupts Windows Office 2016 
installation
https://bugs.documentfoundation.org/show_bug.cgi?id=130771

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 130771] Uninstalling LibreOffice corrupts Windows Office 2016 installation

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 130771] Uninstalling LibreOffice corrupts Windows Office 2016 installation

[bugzilla-daemon]

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

--- Comment #20 from QA Administrators  ---
Dear Shimon Shore,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 126831] UI: The bitmap previews in Area dialog Bitmap have a different shape (rectangle) compared to gradient/hatch/pattern (square)

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 126831] UI: The bitmap previews in Area dialog Bitmap have a different shape (rectangle) compared to gradient/hatch/pattern (square)

[bugzilla-daemon]

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

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 114300] [META] Bugs and enhancements involving lock files or file locking

[bugzilla-daemon]

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

Bug 124887 Summary: Libreoffice cannot open files from Google Drive file shared 
with Linux due to lockfiles
https://bugs.documentfoundation.org/show_bug.cgi?id=124887

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 124887] Libreoffice cannot open files from Google Drive file shared with Linux due to lockfiles

[bugzilla-daemon]

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

--- Comment #11 from QA Administrators  ---
Dear tywin77,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 124887] Libreoffice cannot open files from Google Drive file shared with Linux due to lockfiles

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 103182] [META] GTK3-specific bugs

[bugzilla-daemon]

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

Bug 122161 Summary: UI: Bright screen flashing when starting Impress 
presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=122161

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 122161] UI: Bright screen flashing when starting Impress presentation

[bugzilla-daemon]

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

QA Administrators  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 122161] UI: Bright screen flashing when starting Impress presentation

[bugzilla-daemon]

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

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

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

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

[Libreoffice-bugs] [Bug 99818] EDITING: unformatted paste incorrectly grayed (no steps)

[bugzilla-daemon]

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

--- Comment #29 from QA Administrators  ---
Dear yolo,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

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

[Libreoffice-bugs] [Bug 92159] Can't add text box formatting toolbar

[bugzilla-daemon]

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

--- Comment #18 from QA Administrators  ---
Dear Jonathan Underwood,

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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 86602] Float Frame should require real filename in Content

[bugzilla-daemon]

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

--- Comment #6 from QA Administrators  ---
Dear Maxim Britov,

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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 40218] FILEOPEN: Calc confused by unclosed HTML tags

[bugzilla-daemon]

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

--- Comment #17 from QA Administrators  ---
Dear Tristan Miller,

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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 118913] FILESAVE: convert-to html creates html file with default charset

[bugzilla-daemon]

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

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

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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 102057] charts in duplicated sheet point to original sheet rather than to duplicated one

[bugzilla-daemon]

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

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

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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

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

[Libreoffice-bugs] [Bug 144222] Vertical Japanese character strings are misaligned when exporting PDF.

[bugzilla-daemon]

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

JO3EMC  changed:

   What|Removed |Added

 CC||jo3...@jarl.com

--- Comment #3 from JO3EMC  ---
Reproduced.

Version: 7.2.0.4 (x64) / LibreOffice Community
Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: default; VCL: win
Locale: ja-JP (ja_JP); UI: ja-JP
Calc: CL

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

[Libreoffice-bugs] [Bug 144395] LibreOffice hangs on opening large .docx file

[bugzilla-daemon]

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

--- Comment #2 from wokeness  ---
Created attachment 174912
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174912=edit
The htop's view on Writer.

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

[Libreoffice-bugs] [Bug 144393] Libre converted all my NotePad.txt notes to its own without asking me. It is not reversible.

[bugzilla-daemon]

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

--- Comment #2 from V Stuart Foote  ---
Nothing actionable here.

LibreOffice will not be a default application for .txt documents unless you set
it to be. Either from Windows Setting -> "Choose default apps by file type" or
from File Explorer and context menu "Open With" and "Chose another app..."
dialog.

Yes if you open a .txt text document with LibreOffice Writer and save it, you
will clobber any formatting that may have existed.  So don't!  Rather, use the
Save as and use the native ODF Text document format.

Quit the edit of the .txt and nothing will have been changed in the original
Text file.

And if *you* have set LibreOffice Writer as default for .TXT format--just
revert the App to Notepad.exe. Choosing as described above...

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

[Libreoffice-bugs] [Bug 144395] LibreOffice hangs on opening large .docx file

[bugzilla-daemon]

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

--- Comment #1 from wokeness  ---
Created attachment 174911
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174911=edit
The problematic large .docx file.

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

[Libreoffice-bugs] [Bug 144395] New: LibreOffice hangs on opening large .docx file

[bugzilla-daemon]

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

Bug ID: 144395
   Summary: LibreOffice hangs on opening large .docx file
   Product: LibreOffice
   Version: 7.2.0.4 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: wowli...@126.com

Description:
The .docx file's size is 5.3MB, with chinese characters inside.
Writer hangs on opening the file, 100% CPU, growing MEM.
I run htop to watch the status of Writer, it took about 6min to display the
file content, with long lasting 100% CPU and 1G MEM.

Steps to Reproduce:
1. open the large .docx file
2. run htop command and watch the writer's status

Actual Results:
about 6min later, the Writer is operational, but with lasting 100% CPU and 1G+
MEM.

Expected Results:
open the file within 1min, and consume normal cpu and mem.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 7.2.0.4 / LibreOffice Community
Build ID: 20(Build:4)
CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: zh-CN (zh_CN.UTF-8); UI: zh-CN
7.2.0-2
Calc: threaded

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

[Libreoffice-bugs] [Bug 144393] Libre converted all my NotePad.txt notes to its own without asking me. It is not reversible.

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

 CC||vstuart.fo...@utsa.edu
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INSUFFICIENTDATA

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

[Libreoffice-bugs] [Bug 144222] Vertical Japanese character strings are misaligned when exporting PDF.

[bugzilla-daemon]

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

Junichi Matsukawa  changed:

   What|Removed |Added

 CC||jr4...@kagaku.xii.jp
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #2 from Junichi Matsukawa  ---
reproduced.

Version: 7.2.0.4 (x64) / LibreOffice Community
Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: ja-JP (ja_JP); UI: ja-JP
Calc: CL

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

[Libreoffice-bugs] [Bug 144379] Implement OAuth2 support to use email accounts requiring such authentication in Mail Merge

[bugzilla-daemon]

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

--- Comment #1 from prrv...@gmail.com ---
Hi stragu,

I confirm that this problem exists and that I have known about it for a long
time.

I tried to correct this problem and I just finished writing smtpServerOOo which
will soon replace smtpMailerOOo since everything has been integrated into a
single extension... 

So now if you install:
- OAuth2OOo for authorizations
- gContactOOo for a data source (your phone contacts)
- smtpServerOOo (smtpMailerOOo soon) for:
- mailing list creation (because merging emails without a mailing list is
really nonsense...)
- merging email body in html format.
- merging attached files also in pdf format.
- HsqlDBDriverOOo to have a functional and up to date database under the UNO
API.

then you will be able to get rid of this problem quickly...

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

[Libreoffice-bugs] [Bug 144394] New: Toolbar help has to be updated or not present

[bugzilla-daemon]

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

Bug ID: 144394
   Summary: Toolbar help has to be updated or not present
   Product: LibreOffice
   Version: 7.2.0.4 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: UI
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: s.zosgor...@libreoffice.org

My most beloved feature on LibreOffice is that it allows me to change all
shortcuts on-the-fly<3.
No other office suite offers me this comfort of customization and it's the main
keep I keep LO.

But the toolbar help text is hard coded and that does slaps into my face!

So I ask you to update the toolbar-items help items to the latest user
interaction or complete remove!

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

[Libreoffice-bugs] [Bug 144393] Libre converted all my NotePad.txt notes to its own without asking me. It is not reversible.

[bugzilla-daemon]

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

Walter  changed:

   What|Removed |Added

 CC||walterlace...@yahoo.com

--- Comment #1 from Walter  ---
Also:
I can no longer open any .txt with NotePad. I f I "cut'n'paste" it shows only
garbage. All my notes have been destroyed an a micro second. SHAME! SHAME!
SHAME!

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

[Libreoffice-bugs] [Bug 144393] New: Libre converted all my NotePad.txt notes to its own without asking me. It is not reversible.

[bugzilla-daemon]

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

Bug ID: 144393
   Summary: Libre converted all my NotePad.txt notes to its own
without asking me. It is not reversible.
   Product: LibreOffice
   Version: 7.2.0.4 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Documentation
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: walterlace...@yahoo.com
CC: olivier.hal...@libreoffice.org

Description:
It would take a most assuming, inconsiderate and UN-caring programmer to do
this wholesale without asking or even warning in time to stop.
As long as you have contributors like that, you should hang up any hopes of a
good system.
And yes, I prefer my quick notes in NotePad.txt far more than Libre.

Steps to Reproduce:
1.completed redesign
2.
3.

Actual Results:
open any *.txt and open it using libre

Expected Results:
it changed all my *.txt file formats and made Libre the default to open it.
Shame!


Reproducible: Always


User Profile Reset: No



Additional Info:
pop-up warning/choice of OK to do such or not or never

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

[Libreoffice-bugs] [Bug 144075] Fonts in interface and preferences are too small.

[bugzilla-daemon]

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

--- Comment #12 from MarjaE  ---
If I leave the monitor at the default resolution, the LibreOffice preferences,
etc. are unreadable or painfully hard to read. Maybe they're "perfectly
readable" for you, but not for me.

Some other apps have similar text sizes, but LibreOffice seems uniquely hard to
read. Maybe it's the fonts, text rendering, etc.

If I set a lower resolution, and auto-resize application windows, they start to
overlap the Dock, etc. I'm not sure why. I think rounding errors may be
involved. Apps where I'd set my preferred text sizes get giant but blurry text.
The Menu Bar runs out of space.

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

[Libreoffice-bugs] [Bug 144222] Vertical Japanese character strings are misaligned when exporting PDF.

[bugzilla-daemon]

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

Ming Hua  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 144378] Calc: Characters rotated when printed in Asian layout mode of vertical writing

[bugzilla-daemon]

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

Ming Hua  changed:

   What|Removed |Added

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

--- Comment #11 from Ming Hua  ---
Bug 144222 looks very similar to this, would the kind people here take a look
at that one as well?  Thanks.

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

[Libreoffice-bugs] [Bug 144378] Calc: Characters rotated when printed in Asian layout mode of vertical writing

[bugzilla-daemon]

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

Junichi Matsukawa  changed:

   What|Removed |Added

 CC||jr4...@kagaku.xii.jp

--- Comment #10 from Junichi Matsukawa  ---
reproduced.

Version: 7.2.0.4 (x64) / LibreOffice Community
Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: ja-JP (ja_JP); UI: ja-JP
Calc: CL

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

[Libreoffice-bugs] [Bug 144392] New: Current point after "close path" command Z is the initial point of the closed path

[bugzilla-daemon]

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

Bug ID: 144392
   Summary: Current point after "close path" command Z is the
initial point of the closed path
   Product: LibreOffice
   Version: 7.3.0.0 alpha0+ Master
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rb.hensc...@t-online.de

Created attachment 174910
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174910=edit
Command sequences Z L L and Z M L

Open attached document. It has two custom shapes. The used enhanced-path is
cited on the right side.

The "close path" command Z makes the "current point" not invalid, but sets it
to the initial point of the closed path. And following commands uses this as
"current point" as long as they do not set themselves a "current point".

In the examples the closed path is the triangle. Its initial point has the
coordinates (0|0). Therefore in shape A there should be a line from point (0|0)
to point (80|60) which is the parameter of the first L (lineto) command.
Shape B does not have such line, because the command M (moveto) sets a "current
point".

I think, there should be no concerns to fix it. This bug-report is not about
the path object and its svg:d attribute, where users have a UI to manipulate
points. But it is about the enhanced-path attribute of custom-shapes. The
reported situation does not exists in import or export with predefined shapes.
It happens only, if someone creates own custom-shapes by editing the markup in
file or using macros.

Current ODF 1.3 is not explicit about current point after Z. But SVG, from
which the path commands were inspired, has this rule and ODF 1.4 will have it
explicitly too.

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

[Libreoffice-bugs] [Bug 144391] Calc: link to files management.

[bugzilla-daemon]

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

--- Comment #2 from Arnaldo  ---
Created attachment 174909
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174909=edit
Screenshot 02

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

[Libreoffice-bugs] [Bug 144391] Calc: link to files management.

[bugzilla-daemon]

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

--- Comment #1 from Arnaldo  ---
Created attachment 174908
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174908=edit
Screenshot 01

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

[Libreoffice-bugs] [Bug 144390] Marker (arrow head) on enhanced-path in custom shape is wrong

[bugzilla-daemon]

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

Regina Henschel  changed:

   What|Removed |Added

 Attachment #174906|0   |1
is obsolete||

--- Comment #1 from Regina Henschel  ---
Created attachment 174907
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174907=edit
Example file with five non-primitive custom-shapes

Correction: C is OK
E is wrong, because a closed path should not have markers regardless of other
sub-paths in the same set.

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

[Libreoffice-bugs] [Bug 144391] New: Calc: link to files management.

[bugzilla-daemon]

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

Bug ID: 144391
   Summary: Calc: link to files management.
   Product: LibreOffice
   Version: 7.1.5.2 release
  Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: argas...@argasoft.it

Description:
In link management pop-up:
Before updating: clicking on a file name (highlighted) shows the correct link.
After updating: updated file name still highlighted, BUT wrong link is given.

Actual Results:
See description.

Expected Results:
Correct link after updating


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.5.2 (x64) / LibreOffice Community
Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render:
Skia/Raster; VCL: win
Locale: it-IT (it_IT); UI: it-IT
Calc: threaded

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

[Libreoffice-bugs] [Bug 144390] New: Marker (arrow head) on enhanced-path in custom shape is wrong

[bugzilla-daemon]

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

Bug ID: 144390
   Summary: Marker (arrow head) on enhanced-path in custom shape
is wrong
   Product: LibreOffice
   Version: 7.3.0.0 alpha0+ Master
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rb.hensc...@t-online.de

Created attachment 174906
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174906=edit
Example file with four non-primitive custom-shapes

Open attached file. It contains four shapes and next to it the markup of the
enhanced-path attribute.

A is correct. The path is closed by command Z and therefore has no markers.

B is wrong. The path is not closed but has only accidentally same coordinates
in start and end point. It should show markers. This is a custom shape with an
enhanced-path. The handling of polyline and polygon does not apply.

C is wrong. The path is closed by command Z and therefore should show no
markers. Difference to A is, that here exists a second sub-paths set (starting
after the N command) that has a line.

D is wrong. The path is not closed and therefore should show markers. It is the
same as B but with an addition second sub-paths set with a line.

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

[Libreoffice-bugs] [Bug 144377] Dates are not correctly auto-extrapolated if exclude days

[bugzilla-daemon]

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

buggymc...@bobmail.info changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|NOTABUG |---

--- Comment #5 from buggymc...@bobmail.info ---
> LOL. It does not depend on "my" definition; it is what standard say, and what 
> is implemented in software.

I'm afraid the standard agrees with me. This part of the spec:
https://datatracker.ietf.org/doc/html/rfc6350#section-4.3.1

"Reduced accuracy, as specified in [ISO.8601.2004], Sections 4.1.2.3
   a) and b), but not c), is permitted."

So the ISO8601 specification explicitly says that a date of 1985-04 is valid
(it uses that as an example).


(Wikipedia says the same thing (with the standard as a ref):
https://en.wikipedia.org/wiki/ISO8601#Calendar_dates
"The standard also allows for calendar dates to be written with reduced
precision. For example, one may write "1981-04" to mean "1981 April". "

So hope you don't mind but given the spec itself explicitly says this is a
valid date, I'm going to re-open.


> There you may specify a Y-M pattern, and then when you enter 2019-01, Calc 
> will convert it to 2019-01-01

Thanks, but that's false precision
(https://en.wikipedia.org/wiki/False_precision) and is exactly the behaviour I
do not want (and indeed is probably why the spec does allow reduced precision).

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

[Libreoffice-bugs] [Bug 144372] Y Axis label changes when copy/pasting a chart from calc to impress

[bugzilla-daemon]

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

--- Comment #2 from buggymc...@bobmail.info ---
Thanks for the explanation but I fail to see how that's not a bug from the
user's perspective?
I don't have to fiddle with any other settings when shifting charts between
applications to get something that's otherwise identical, and from a user
perspective there's nothing at all that's special about this particular
setting. 

It's certainly non-obvious behaviour to a user, and when I saw it my first
thought was "I don't feel like spending the next 10 minutes fiddling around
trying to find the one setting that might fix this". Instead I simply took a
screenshot of it from calc and used that, completly bypassing this entire
feature.

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

[Libreoffice-bugs] [Bug 120129] EDITING: LIST function in query creates additional characters in Windows10

[bugzilla-daemon]

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

--- Comment #13 from Mike Kaganski  ---
(In reply to Mike Kaganski from comment #12)
> I couldn't repro with the attachment here.

I meant, I couldn't repro with attachment 145186 from comment 1.

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

[Libreoffice-bugs] [Bug 131758] Consistent polygon tool behavior in Draw.

[bugzilla-daemon]

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

--- Comment #20 from Regina Henschel  ---
(In reply to Heiko Tietze from comment #19)
> Don't see how the design group can help here. According comment 12 it's a
> bunch of issues and you discuss several solutions. Sounds as splitting the
> ticket into several bugs might be helpful.

I think no split is needed. A tool is missing in the UI to create
PolyPolylines. The current PolyPoly-modus always generates PolyPolygons.

It is a problem for the design group, because suggestions are needed:
* How should a PolyPoly-modus work from point of view of users?
* How should it work without mouse, or is it only usable with mouse?
* What in the workflow of users distinguishes creating a PolyPolygon from
creating a PolyPolyline?
* Which steps should be equal for creating PolyPolyline and PolyPolygon?
* Is a separate tool in the UI needed, or can the current PolyPoly-modus be
changed to allow users to choose between creating PolyPolylines and
PolyPolygons?
* Should a PolyPoly-modus for other purpose than creating shapes (e.g. Writer
contour wrap) have the same workflow?

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

Re: LibreOffice 7.2.0.4 : bug report

[Jean-Baptiste Faure]

Bonjour Lydie,

Cette liste de discussion est dédiée aux échanges concernant le développement de 
LibreOffice. Ces échanges doivent être conduits en anglais. Quant aux rapports de bug il 
faut les faire sur le site dédié pour qu'ils puissent être traités efficacement : 
https://bugs.documentfoundation.org/


Vous avez certainement un problème avec votre installation de LibreOffice. Pour obtenir de 
l'aide, la bonne méthode est de vous adresser, en français, soit à la liste de discussion 
francophone us...@fr.libreoffice.org soit au forum AskLibo : 
https://ask.libreoffice.org/c/french/7. Pensez à donner le maximum d'information sur la 
machine utilisée, le système d'exploitation utilisé, la procédure d'installation réalisée.


English translation from deepl.com :

Hello Lydie,

This discussion list is dedicated to exchanges concerning the development of LibreOffice. 
These exchanges must be conducted in English. As for bug reports, they should be made  on 
the dedicated site so that they can be processed efficiently: 
https://bugs.documentfoundation.org/


You certainly have a problem with your LibreOffice installation. To get help, the best 
method is to contact, in French, either the French-speaking discussion list 
us...@fr.libreoffice.org or the AskLibo forum : https://ask.libreoffice.org/c/french/7. 
Remember to give as much information as possible about the machine you are using, the 
operating system you are using and the installation procedure you have followed.


Best regards.
JBF

Le 07/09/2021 à 18:08, Lydie TREBUCHON a écrit :

Bonjour,

Voici le bug que j’ai malheureusement sur mon ordinateur lorsque j’ouvre Calc, je saisis 
des chiffres dans une cellule et je fais Entrée.


Rapport en pièce jointe.

Ça fait peur pour un logiciel à peine installé et dont le code a soit disant était revu et 
dépoussiéré. C’est à vous dégoûter du libre.


Microsoft a encore de beau jours devant lui !

Cordialement,

Pierre




--
Seuls des formats ouverts peuvent assurer la pérennité de vos documents.

[Libreoffice-bugs] [Bug 143868] Mac Fonts are too large on non-retina display - UI

[bugzilla-daemon]

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

--- Comment #4 from W Sanders  ---
Well I really think you didn't understand the problem. The font size is only
messy in LibreOffice and not in other apps. Scaling the display is not the
solution.

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

[Libreoffice-commits] mso-dumper.git: msodumper/emfrecord.py msodumper/wmfrecord.py wmf-dump.py

[Libreoffice Gerrit user]

 msodumper/emfrecord.py |   11 +-
 msodumper/wmfrecord.py |  237 -
 wmf-dump.py|   31 ++
 3 files changed, 275 insertions(+), 4 deletions(-)

New commits:
commit 77a03bd26e4076553ad3ea0972c64488baa467da
Author: Hossein 
AuthorDate: Wed Sep 8 23:13:17 2021 +0200
Commit: Hossein 
CommitDate: Wed Sep 8 23:27:41 2021 +0200

Add preliminary wmf support and minor cleanups

* Added "wmf-dump.py" and preliminary support for dumping header/data
  from wmf files in msodumper/wmfrecord.py
* Most of the records have data shown as  for now. Should be
  completed later
* Changed msodumper/wmfrecord.py and msodumper/emfrecord.py to
  handle wmf and emf files with unexpected end of file
* Changed msodumper/wmfrecord.py and msodumper/emfrecord.py to
  handle invalid values for the fields
* Tested to work (at least do not cause exception) for all the wmf
  and most of the emf files found inside LibreOffice core repository

Change-Id: Ia067961d006c9dc543e521ad64509b03b8454a80
Reviewed-on: https://gerrit.libreoffice.org/c/mso-dumper/+/121833
Tested-by: Hossein 
Reviewed-by: Hossein 

diff --git a/msodumper/emfrecord.py b/msodumper/emfrecord.py
index 7d7be0a..ca4b022 100644
--- a/msodumper/emfrecord.py
+++ b/msodumper/emfrecord.py
@@ -65,7 +65,7 @@ class EMFStream(BinaryStream):
 emrHeader.dump()
 for i in range(emrHeader.header.Records):
 id = self.getuInt32()
-record = RecordType[id]
+record = RecordType.get(id, ["INVALID"])
 type = record[0]
 size = self.getuInt32(pos=self.pos + 4)
 # EmrHeader is already dumped
@@ -77,7 +77,14 @@ class EMFStream(BinaryStream):
 else:
 print('')
 print('')
-self.pos += size
+# EMR_EOF
+if type == "EMR_EOF":
+break
+if self.pos + size <= self.size:
+self.pos += size
+else:
+print('')
+break
 print('')
 
 
diff --git a/msodumper/wmfrecord.py b/msodumper/wmfrecord.py
index 1d7b1fa..2294301 100644
--- a/msodumper/wmfrecord.py
+++ b/msodumper/wmfrecord.py
@@ -7,6 +7,14 @@
 
 from .binarystream import BinaryStream
 
+PlaceableKey = {
+0x9ac6cdd7: "META_PLACEABLE",
+}
+
+FileType = {
+0x00: "Memory",
+0x01: "Disk",
+}
 
 # The BrushStyle Enumeration specifies the different possible brush types that 
can be used in graphics operations.
 BrushStyle = {
@@ -22,7 +30,6 @@ BrushStyle = {
 0x0009: "BS_MONOPATTERN"
 }
 
-
 # The HatchStyle Enumeration specifies the hatch pattern.
 HatchStyle = {
 0x: "HS_HORIZONTAL",
@@ -33,7 +40,6 @@ HatchStyle = {
 0x0005: "HS_DIAGCROSS"
 }
 
-
 # No idea what's the proper name of this thing, see
 # http://msdn.microsoft.com/en-us/library/dd145130%28VS.85%29.aspx
 RasterPolishMap = {
@@ -296,6 +302,41 @@ RasterPolishMap = {
 }
 
 
+class WMFStream(BinaryStream):
+def __init__(self, bytes):
+BinaryStream.__init__(self, bytes)
+
+def dump(self):
+print('' % self.size)
+wmfHeader = WmfHeader(self)
+wmfHeader.dump()
+
+MAXIMUM_RECORDS = 10
+for i in range(1, MAXIMUM_RECORDS):
+size = self.getuInt32()
+id = self.getuInt16(pos=self.pos + 4)
+record = RecordType.get(id, ["INVALID"])
+type = record[0]
+# WmfHeader is already dumped
+if i:
+print('' % (i, type))
+if len(record) > 1:
+handler = record[1](self)
+handler.dump()
+else:
+print('')
+print('')
+# META_EOF
+if type == "META_EOF":
+break
+if self.pos + size * 2 <= self.size:
+self.pos += size * 2
+else:
+print('')
+break
+print('')
+
+
 class WMFRecord(BinaryStream):
 def __init__(self, parent):
 BinaryStream.__init__(self, parent.bytes)
@@ -303,8 +344,28 @@ class WMFRecord(BinaryStream):
 self.pos = parent.pos
 
 
+class Rect(WMFRecord):
+"""The Rect Object defines a rectangle."""
+def __init__(self, parent, name=None):
+WMFRecord.__init__(self, parent)
+if name:
+self.name = name
+else:
+self.name = "rect"
+
+def dump(self):
+print('<%s type="Rect">' % self.name)
+self.printAndSet("Left", self.readInt16(), hexdump=False)
+self.printAndSet("Top", self.readInt16(), hexdump=False)
+self.printAndSet("Right", self.readInt16(), hexdump=False)
+self.printAndSet("Bottom", self.readInt16(), hexdump=False)
+print('' % self.name)
+self.parent.pos = self.pos
+
+
 class RectL(WMFRecord):
 

[Libreoffice-bugs] [Bug 143868] Mac Fonts are too large on non-retina display - UI

[bugzilla-daemon]

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

--- Comment #3 from W Sanders  ---
Well I really think you didn't understand the problem. The font size is only
messy in LibreOffice and not in other apps. Scaling the display is not the
solution.

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

[Libreoffice-bugs] [Bug 120129] EDITING: LIST function in query creates additional characters in Windows10

[bugzilla-daemon]

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

--- Comment #12 from Mike Kaganski  ---
Created attachment 174905
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174905=edit
A sample with LIST generating BLOB with zero bytes

Hum. Maybe my issue is different after all.

I couldn't repro with the attachment here. But this file gives me a "sluggish"
experience (using my dbgutil build, I get tens of seconds until the query
shows; trying to resize the column gives another delay; UI is unresponsive up
to the point of requiring to kill it).

Putting a breakpoint to OutputDevice::GetTextBreak shows that the rStr looks
like

> rStr = 
> L"100х100х2,0;\0\0\0\0\0\0\0\0\0\0\0\0100х100х2,5;\0\0\0\0\0\0\0\0\0\0\0\0100х100х2,8;\0\0\0\0\0\0\0\0\0\0\0\0100х100х3,0;\0\0\0\0\0\0\0\0\0\0\0\0100х100х3,5;\0\0\0\0\0\0\0\0\0\0\0\0100х100х4,0;\0\0\0\0\0\0\0\0\0\0\0\0100х100х4,5;\0\0\0\0\0\0\0\0\0\0\0\0100...

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

LibreOffice 7.1.5 : bug report

[Lydie TREBUCHON]

Suite à vos conseils, j’ai installé la version 7.1.5 de LibreOffice sur mon 
ordinateur et figurez-vous que j’ai exactement le même bug
dont vous trouverez le rapport en pièce-jointe, ainsi que ma configuration 
matérielle.
Autre remarque : j’ai l’impression que les logos des icônes n’ont pas bougés 
depuis 20 ans. Ça vaudrait peut-être le coup de faire appel
à des infographistes professionnels pour avoir quelque chose au goût du jour 
(en utilisant l’argent des dons).

Voilà, c’était ma maigre contribution à la communauté du libre.

Dans l’attente de votre retour, très bonne continuation.

Bien Cordialement,
Pierre

De : Regis Perdreau
Envoyé le :mardi 7 septembre 2021 23:54
À : Lydie TREBUCHON
Cc : libreoffice@lists.freedesktop.org
Objet :Re: LibreOffice 7.2.0.4 : bug report

Bonjour,

Je pense que vous feriez mieux de prendre la version 7.1.5 ici 
https://fr.libreoffice.org/download/telecharger-libreoffice/?type=win-x86=7.2.0=fr
version X64 probablement de nos jours ...
Vous avez pris une version qui peut etre qualifiée d'expérimentalr, des 
plantages sont possibles...c'est clairement expliqué.

Par contre effectivement, vous aideriez la communauté en explicitant comment 
vous avez réussi à obtenir le crash en question.
Les informations que vous avez récupèré ne permette pas directement d'obtenir 
la cause...



Régis Perdreau


Le mar. 7 sept. 2021 à 23:05, Lydie TREBUCHON 
mailto:lydie.trebuc...@hotmail.fr>> a écrit :
Bonjour,

Voici le bug que j’ai malheureusement sur mon ordinateur lorsque j’ouvre Calc, 
je saisis des chiffres dans une cellule et je fais Entrée.
Rapport en pièce jointe.
Ça fait peur pour un logiciel à peine installé et dont le code a soit disant 
était revu et dépoussiéré. C’est à vous dégoûter du libre.
Microsoft a encore de beau jours devant lui !

Cordialement,
Pierre


Signature du problème :
  Nom d’événement de problème:  APPCRASH
  Nom de l’application: soffice.bin
  Version de l’application: 7.1.5.2
  Horodatage de l’application:  60f30d57
  Nom du module par défaut: ucrtbase.DLL
  Version du module par défaut: 10.0.10240.16390
  Horodateur du module par défaut:  55a5b718
  Code de l’exception:  4015
  Décalage de l’exception:  00065a5f
  Version du système:   6.1.7601.2.1.0.256.48
  Identificateur de paramètres régionaux:   1036
  Information supplémentaire n° 1:  3f1b
  Information supplémentaire n° 2:  3f1bb0b42f2868ebfb1bcc83f72390aa
  Information supplémentaire n° 3:  1caa
  Information supplémentaire n° 4:  1caaa000274b7300a2c74e24ad38990a

Lire notre déclaration de confidentialité en ligne :
  http://go.microsoft.com/fwlink/?linkid=104288=0x040c

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la 
version hors connexion :
  C:\Windows\system32\fr-FR\erofflps.txt
Config PC micro ATX :

- Processeur AMD Phenom II X4 B50 3,1 Ghz (je n'ai que 3 coeurs d'actifs, le 
quatrième est HS)
- Carte mère micro ATX ASUS M4A88T-M/USB3
- Mémoire vive 4 Go DDR3 1333
- Carte graphique ATI RADEON HD 5770
- écran HP 24 pouces au format 16/10 (1920 * 1200)

avec Windows 7 pro 64 bits

Re: test testPreserveJpg::TestBody fails

[Jean-Baptiste Faure]

Hi Miklos,

Le 08/09/2021 à 08:42, Miklos Vajna a écrit :

Hi JBF,

On Tue, Sep 07, 2021 at 07:13:19PM +0200, Jean-Baptiste Faure 
 wrote:

I get the following error when I run the tests on the master:


[_RUN_] testPreserveJpg::TestBody
unknown:0:testPreserveJpg::TestBody
An uncaught exception of type com.sun.star.io.IOException
- SfxBaseModel::impl_store  failed: 0xc10(Error Area:Io 
Class:Write Code:16) [...]/libo/master/sfx2/source/doc/sfxbasemodel.cxx:3187 
[...]/libo/master/sfx2/source/doc/sfxbasemodel.cxx:1767


My C++ skills are not enough to understand the problem.

Something has changed recently because the tests passed fine 2 or 3 weaks ago.


Did you try manually performing the test? Open the preserve-jpg.odt test
document, select the image, context menu, export to SVG and see if it
fails.

If so, you could bibisect when this started in your environment.


Manualling performing the test works in master and LO 7.2.
The only problem is that the default sizes of the image in the svg export dialog is 0.06 x 
0.06 cm and I see nothing when I open the svg in Firefox. If I open the svg file with 
gedit, I can see a binary string which seems to be the original jpeg image converted in PNG.


Best regards.
JBF

--
Seuls des formats ouverts peuvent assurer la pérennité de vos documents.

[Libreoffice-commits] core.git: emfio/inc emfio/source

[Caolán McNamara (via logerrit)]

 emfio/inc/wmfreader.hxx   |2 +-
 emfio/source/reader/wmfreader.cxx |   10 ++
 2 files changed, 7 insertions(+), 5 deletions(-)

New commits:
commit 5b6fcbf4a754a2699b3b865256848238f93113a2
Author: Caolán McNamara 
AuthorDate: Wed Sep 8 20:29:41 2021 +0100
Commit: Caolán McNamara 
CommitDate: Wed Sep 8 22:28:31 2021 +0200

ofz: MemorySanitizer: use-of-uninitialized-value

sidestep the resize behaviour of SvMemoryStream by using an honest
std::vector and make it use that buffer

Change-Id: Ic5e405010ac076fc04e1ca8dc6dbb495162101ce
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/121832
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 

diff --git a/emfio/inc/wmfreader.hxx b/emfio/inc/wmfreader.hxx
index a7dff2b94d85..f7788d53651c 100644
--- a/emfio/inc/wmfreader.hxx
+++ b/emfio/inc/wmfreader.hxx
@@ -35,7 +35,7 @@ namespace emfio
 sal_uInt32  mnRecSize;
 
 // embedded EMF data
-std::unique_ptr mpEMFStream;
+std::optional> mpEMFStream;
 
 // total number of comment records containing EMF data
 sal_uInt32  mnEMFRecCount;
diff --git a/emfio/source/reader/wmfreader.cxx 
b/emfio/source/reader/wmfreader.cxx
index a32c7f100e04..d71dbf485710 100644
--- a/emfio/source/reader/wmfreader.cxx
+++ b/emfio/source/reader/wmfreader.cxx
@@ -1315,7 +1315,7 @@ namespace emfio
 mpEMFStream.reset();
 }
 else
-mpEMFStream = 
std::make_unique(mnEMFSize, 0);
+mpEMFStream = std::vector();
 }
 else if( (mnEMFRecCount != nComRecCount ) || 
(mnEMFSize != nEMFTotalSize ) ) // add additional checks here
 {
@@ -1343,7 +1343,9 @@ namespace emfio
 std::vector aBuf(nCurRecSize);
 sal_uInt32 nCount = 
mpInputStream->ReadBytes(aBuf.data(), nCurRecSize);
 if( nCount == nCurRecSize )
-mpEMFStream->WriteBytes(aBuf.data(), 
nCount);
+{
+
mpEMFStream->insert(mpEMFStream->end(), aBuf.begin(), aBuf.end());
+}
 }
 }
 }
@@ -1594,8 +1596,8 @@ namespace emfio
 if(mpEMFStream && mnEMFRecCount == mnEMFRec)
 {
 GDIMetaFile aMeta;
-mpEMFStream->Seek( 0 );
-std::unique_ptr 
pEMFReader(std::make_unique( *mpEMFStream, aMeta ));
+SvMemoryStream aStream(mpEMFStream->data(), 
mpEMFStream->size(), StreamMode::STD_READ);
+std::unique_ptr 
pEMFReader(std::make_unique(aStream, aMeta));
 pEMFReader->SetEnableEMFPlus(mbEnableEMFPlus);
 bEMFAvailable = pEMFReader->ReadEnhWMF();
 pEMFReader.reset(); // destroy first!!!

[Libreoffice-bugs] [Bug 144341] Unable to set alignment for hyperlinks in text boxes

[bugzilla-daemon]

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

--- Comment #4 from Rafael Lima  ---
Created attachment 174904
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174904=edit
Sample PPTX file

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

[Libreoffice-bugs] [Bug 144372] Y Axis label changes when copy/pasting a chart from calc to impress

[bugzilla-daemon]

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

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de
 Resolution|--- |NOTABUG
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Regina Henschel  ---
The y-axis in the chart has enabled "use Source Format" in the 'Number' tab of
the properties dialog. When you copy the chart to Impress, the relationship to
the spreadsheet is cut, so the axis does not find the format. So before you
copy the chart to Impress, uncheck this option. You can check it again,
after you have copied the chart.

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

[Libreoffice-bugs] [Bug 144341] Unable to set alignment for hyperlinks in text boxes

[bugzilla-daemon]

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

--- Comment #3 from Rafael Lima  ---
Created attachment 174903
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174903=edit
ODG file with screenshots

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

[Libreoffice-bugs] [Bug 144341] Unable to set alignment for hyperlinks in text boxes

[bugzilla-daemon]

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

--- Comment #2 from Rafael Lima  ---
Hi Xisco(In reply to Xisco Faulí from comment #1)
> Hi Rafael,
> I can't reproduce the described behaviour in

Hi Xisco, take another look at the link and notice that it is aligned to the
left, even though I set its alignment to the right.

I uploaded an ODG file to clarify the issue. On page 1 I show how adding a
hyperlink breaks alignment.

I also created a PPTX file in PowerPoint (also attached to this report) and
took some screenshots (see page 2 of the ODG file). Notice that in PowerPoint
adding a hyperlink does not break alignment.

This bug also causes a PPTX import issue, because if you open this PPTX file in
Impress the alignment will be incorrect (see page 3 of the ODG file).

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

[Libreoffice-commits] core.git: drawinglayer/source

[Noel Grandin (via logerrit)]

 drawinglayer/source/primitive2d/Tools.cxx |   14 +-
 1 file changed, 5 insertions(+), 9 deletions(-)

New commits:
commit c07f4a7d04eb44020045859d305f4510ae9acfc4
Author: Noel Grandin 
AuthorDate: Wed Sep 8 20:20:55 2021 +0200
Commit: Noel Grandin 
CommitDate: Wed Sep 8 22:20:41 2021 +0200

no need to call expand() here

we can just return the value directly

Change-Id: Ia4a79ebe668dd426edbe95baee8d8cf91d4bc3f0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/121828
Tested-by: Jenkins
Reviewed-by: Noel Grandin 

diff --git a/drawinglayer/source/primitive2d/Tools.cxx 
b/drawinglayer/source/primitive2d/Tools.cxx
index 45b2a993b3a7..7be666a2cbd0 100644
--- a/drawinglayer/source/primitive2d/Tools.cxx
+++ b/drawinglayer/source/primitive2d/Tools.cxx
@@ -32,16 +32,12 @@ basegfx::B2DRange
 getB2DRangeFromPrimitive2DReference(const Primitive2DReference& rCandidate,
 const geometry::ViewInformation2D& 
aViewInformation)
 {
-basegfx::B2DRange aRetval;
+if (!rCandidate)
+return basegfx::B2DRange();
 
-if (rCandidate.is())
-{
-// get C++ implementation base
-const BasePrimitive2D* 
pCandidate(static_cast(rCandidate.get()));
-aRetval.expand(pCandidate->getB2DRange(aViewInformation));
-}
-
-return aRetval;
+// get C++ implementation base
+const BasePrimitive2D* 
pCandidate(static_cast(rCandidate.get()));
+return pCandidate->getB2DRange(aViewInformation);
 }
 
 bool arePrimitive2DReferencesEqual(const Primitive2DReference& rxA, const 
Primitive2DReference& rxB)

[Libreoffice-commits] core.git: sc/source

[Noel Grandin (via logerrit)]

 sc/source/ui/unoobj/chart2uno.cxx |7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

New commits:
commit 993ae97e38e72e9d5dabeb0f3abafdc55c73161e
Author: Noel Grandin 
AuthorDate: Wed Sep 8 21:11:05 2021 +0200
Commit: Noel Grandin 
CommitDate: Wed Sep 8 22:17:59 2021 +0200

avoid double-lookup

this is hot when creating charts

Change-Id: Ic096d9293a48d53fc2cadfda95b5b7a13ba16f68
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/121830
Tested-by: Jenkins
Reviewed-by: Noel Grandin 

diff --git a/sc/source/ui/unoobj/chart2uno.cxx 
b/sc/source/ui/unoobj/chart2uno.cxx
index 5efa562cb352..3ee4f1cde054 100644
--- a/sc/source/ui/unoobj/chart2uno.cxx
+++ b/sc/source/ui/unoobj/chart2uno.cxx
@@ -760,12 +760,13 @@ void Chart2Positioner::createPositionMap()
 aCellData.SetAbsRow(nRow);
 aCellData.SetAbsTab(nTab);
 
-if (rCol.find(nInsRow) == rCol.end())
+auto& rCell = rCol[nInsRow];
+if (!rCell)
 {
 if (bExternal)
-rCol[ nInsRow ].reset(new 
ScExternalSingleRefToken(nFileId, aTabName, aCellData));
+rCell.reset(new ScExternalSingleRefToken(nFileId, 
aTabName, aCellData));
 else
-rCol[ nInsRow ].reset(new 
ScSingleRefToken(mpDoc->GetSheetLimits(), aCellData));
+rCell.reset(new 
ScSingleRefToken(mpDoc->GetSheetLimits(), aCellData));
 }
 }
 }

[Libreoffice-commits] core.git: chart2/source

[Noel Grandin (via logerrit)]

 chart2/source/view/main/PropertyMapper.cxx |8 
 1 file changed, 4 insertions(+), 4 deletions(-)

New commits:
commit 2cf4cf718165988e81b606be7fa0a4b02973a10a
Author: Noel Grandin 
AuthorDate: Wed Sep 8 21:19:59 2021 +0200
Commit: Noel Grandin 
CommitDate: Wed Sep 8 22:17:25 2021 +0200

avoid some ref-counting

Change-Id: I04dfa4070b2e64c4ab7cb59d4a5c4668e98dc076
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/121831
Tested-by: Jenkins
Reviewed-by: Noel Grandin 

diff --git a/chart2/source/view/main/PropertyMapper.cxx 
b/chart2/source/view/main/PropertyMapper.cxx
index c7327974249a..d9ae1fc7a925 100644
--- a/chart2/source/view/main/PropertyMapper.cxx
+++ b/chart2/source/view/main/PropertyMapper.cxx
@@ -101,13 +101,13 @@ void PropertyMapper::getValueMap(
 {
 for (auto const& elem : rNameMap)
 {
-OUString aTarget = elem.first;
-OUString aSource = elem.second;
+const OUString & rTarget = elem.first;
+const OUString & rSource = elem.second;
 try
 {
-uno::Any aAny( xSourceProp->getPropertyValue(aSource) );
+uno::Any aAny( xSourceProp->getPropertyValue(rSource) );
 if( aAny.hasValue() )
-rValueMap.emplace(  aTarget, aAny );
+rValueMap.emplace(  rTarget, aAny );
 }
 catch( const uno::Exception& )
 {

[Libreoffice-commits] core.git: forms/source oox/source sc/source sfx2/source svx/source sw/source

[Noel Grandin (via logerrit)]

 forms/source/richtext/rtattributehandler.cxx   |8 

 oox/source/export/shapes.cxx   |2 +-
 sc/source/core/data/table5.cxx |2 +-
 sc/source/ui/app/scmod.cxx |2 +-
 sc/source/ui/view/auditsh.cxx  |2 +-
 sc/source/ui/view/cellsh3.cxx  |2 +-
 sc/source/ui/view/tabvwshe.cxx |4 ++--
 sfx2/source/appl/appserv.cxx   |2 +-
 svx/source/stbctrls/zoomsliderctrl.cxx |2 +-
 sw/source/core/doc/doctxm.cxx  |9 
-
 sw/source/core/docnode/ndsect.cxx  |2 +-
 sw/source/core/edit/edglbldc.cxx   |2 +-
 sw/source/core/edit/edtox.cxx  |6 
+++---
 sw/source/core/layout/fly.cxx  |2 +-
 sw/source/core/layout/trvlfrm.cxx  |2 +-
 sw/source/core/objectpositioning/ascharanchoredobjectposition.cxx  |6 
+++---
 sw/source/core/objectpositioning/environmentofanchoredobject.cxx   |4 ++--
 sw/source/core/objectpositioning/tocntntanchoredobjectposition.cxx |2 +-
 sw/source/core/txtnode/fmtatr2.cxx |3 +--
 sw/source/core/txtnode/ndtxt.cxx   |3 +--
 sw/source/core/unocore/unorefmk.cxx|3 +--
 sw/source/core/view/vprint.cxx |2 +-
 sw/source/uibase/app/docsh2.cxx|5 ++---
 sw/source/uibase/docvw/PostItMgr.cxx   |2 +-
 sw/source/uibase/uiview/srcview.cxx|4 ++--
 sw/source/uibase/utlui/viewlayoutctrl.cxx  |2 +-
 26 files changed, 40 insertions(+), 45 deletions(-)

New commits:
commit e11386053d3c404fbeab8b66402d68f813f7dd58
Author: Noel Grandin 
AuthorDate: Wed Sep 8 15:01:33 2021 +0200
Commit: Noel Grandin 
CommitDate: Wed Sep 8 22:17:05 2021 +0200

convert some OSL_ENSURE -> assert

where we are just provide checking for a following static_cast.

I'd rather have an explicit assert failure than a random crash

Change-Id: Iab6c6b056341018deaa74b78b075e564f72c58d9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/121814
Tested-by: Jenkins
Reviewed-by: Noel Grandin 

diff --git a/forms/source/richtext/rtattributehandler.cxx 
b/forms/source/richtext/rtattributehandler.cxx
index 804d6bb2d42d..653d42e46a5f 100644
--- a/forms/source/richtext/rtattributehandler.cxx
+++ b/forms/source/richtext/rtattributehandler.cxx
@@ -183,7 +183,7 @@ namespace frm
 
 AttributeCheckState ParaAlignmentHandler::implGetCheckState( const 
SfxPoolItem& _rItem ) const
 {
-OSL_ENSURE( dynamic_cast( &_rItem) !=  nullptr, 
"ParaAlignmentHandler::implGetCheckState: invalid pool item!" );
+assert( dynamic_cast( &_rItem) && 
"ParaAlignmentHandler::implGetCheckState: invalid pool item!" );
 SvxAdjust eAdjust = static_cast< const SvxAdjustItem& >( _rItem 
).GetAdjust();
 return ( eAdjust == m_eAdjust ) ? eChecked : eUnchecked;
 }
@@ -213,7 +213,7 @@ namespace frm
 
 AttributeCheckState LineSpacingHandler::implGetCheckState( const 
SfxPoolItem& _rItem ) const
 {
-OSL_ENSURE( dynamic_cast( &_rItem) !=  
nullptr, "LineSpacingHandler::implGetCheckState: invalid pool item!" );
+assert( dynamic_cast( &_rItem) && 
"LineSpacingHandler::implGetCheckState: invalid pool item!" );
 sal_uInt16 nLineSpace = static_cast< const SvxLineSpacingItem& >( 
_rItem ).GetPropLineSpace();
 return ( nLineSpace == m_nLineSpace ) ? eChecked : eUnchecked;
 }
@@ -250,7 +250,7 @@ namespace frm
 
 AttributeCheckState EscapementHandler::implGetCheckState( const 
SfxPoolItem& _rItem ) const
 {
-OSL_ENSURE( dynamic_cast( &_rItem) !=  
nullptr, "EscapementHandler::getState: invalid pool item!" );
+assert( dynamic_cast( &_rItem) && 
"EscapementHandler::getState: invalid pool item!" );
 SvxEscapement eEscapement = static_cast< const SvxEscapementItem& >( 
_rItem ).GetEscapement();
 return ( eEscapement == m_eEscapement ) ? eChecked : eUnchecked;
 }
@@ -389,7 +389,7 @@ namespace frm
 
 AttributeCheckState ParagraphDirectionHandler::implGetCheckState( const 
SfxPoolItem& _rItem ) const
 {
-OSL_ENSURE( dynamic_cast( &_rItem) !=  
nullptr, "ParagraphDirectionHandler::implGetCheckState: invalid pool item!" );
+assert( dynamic_cast( &_rItem) && 
"ParagraphDirectionHandler::implGetCheckState: invalid pool item!" );
 SvxFrameDirection eDirection = 

[Libreoffice-bugs] [Bug 144338] UI Connected spinbox not updated when value is typed into the field

[bugzilla-daemon]

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

--- Comment #14 from Telesto  ---
Created attachment 174902
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174902=edit
Screencast PhotoScape

Gimp/ RawTherapee & DigiKam/ Avidemux behave like LibreOffice

Dynamic
* https://pixlr.com (not spinbox()
* Nomacs (QT5)

It appears that the behaviour more or less platform depended. Dynamic updating
rather common for Windows applications (with some exceptions), but only
updating after focus change appears to be the norm at Linux environments (with
Nomacs being an exception).

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

[Libreoffice-bugs] [Bug 144371] Angles when plotting lines

[bugzilla-daemon]

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

Regina Henschel  changed:

   What|Removed |Added

 CC||rb.hensc...@t-online.de
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |NOTABUG

--- Comment #2 from Regina Henschel  ---
There are some ways to avoid these small inaccuracies which you get when using
the mouse:

To draw horizontal or vertical lines press the shift-key while dragging with
the mouse.

To change the length of an existing line use the "Position and Size" dialog.

Use Ctrl+Tab and Ctrl+Shift+Tag to activate start or end point of the line.
Then use the arrow keys (combine with Shift- or Alt-Key) to move that point.

Besides the already mentioned general grid you can enable "Snap to grid guides"
and use snap lines and snap points for exact positions.

Please use Draw Guide and Help (F1) or ask on us...@global.libreoffice.org or
https://ask.libreoffice.org to get assistance in using Draw.

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

[Libreoffice-bugs] [Bug 120129] EDITING: LIST function in query creates additional characters in Windows10

[bugzilla-daemon]

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

--- Comment #11 from Julien Nabet  ---
(In reply to Mike Kaganski from comment #10)
> (In reply to Julien Nabet from comment #9)
> > It may be already be fixed with tdf#144230 (put in see also).
> 
> No, I also saw *zero bytes* added to LIST output; and given that I don't
> know much about how it should work, I thought it's how the BLOB should look
> like. Looks like I need to take a look at it deep :-)

Hehe, I noticed your recent great work on Firebird, knowing that there are very
few commits about Base part, thank you a lot!

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

[Libreoffice-bugs] [Bug 144389] Assertion when launching query design (with Orca)

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

   Keywords||haveBacktrace

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

[Libreoffice-commits] core.git: vcl/unx

[Julien Nabet (via logerrit)]

 vcl/unx/gtk3/gtkinst.cxx |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 41a55bde344f924edd36dbbeead45c426ee07e4d
Author: Julien Nabet 
AuthorDate: Wed Sep 8 20:45:55 2021 +0200
Commit: Julien Nabet 
CommitDate: Wed Sep 8 21:53:56 2021 +0200

fix copy paste in assertion message (vcl/gtk3/gtkinst)

Change-Id: I2603dcb809d2bf062f3b14f7c21583fde1da9f05
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/121829
Reviewed-by: Caolán McNamara 
Reviewed-by: Julien Nabet 
Tested-by: Jenkins

diff --git a/vcl/unx/gtk3/gtkinst.cxx b/vcl/unx/gtk3/gtkinst.cxx
index 053bf5a0d607..5a4270857919 100644
--- a/vcl/unx/gtk3/gtkinst.cxx
+++ b/vcl/unx/gtk3/gtkinst.cxx
@@ -16985,7 +16985,7 @@ public:
 {
 //get_accessible_relation_set should only be needed for the vcl 
implementation,
 //in the gtk impl the native equivalent should negate the need.
-assert(false && "get_accessible_parent should only be called on a vcl 
impl");
+assert(false && "get_accessible_relation_set should only be called on 
a vcl impl");
 return uno::Reference();
 }
 

[Libreoffice-bugs] [Bug 144389] Assertion when launching query design (with Orca)

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

 CC||caol...@redhat.com

--- Comment #2 from Julien Nabet  ---
It can also asserts with
1. Start Orca
2. Launch attached file
3. Click on Tables

Caolán: here's the bugtracker following your comment in
https://gerrit.libreoffice.org/c/core/+/121829 ! :-)

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

[Libreoffice-bugs] [Bug 144389] Assertion when launching query design (with Orca)

[bugzilla-daemon]

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

--- Comment #1 from Julien Nabet  ---
Created attachment 174901
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174901=edit
bt with debug symbols

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

[Libreoffice-bugs] [Bug 144389] New: Assertion when launching query design (with Orca)

[bugzilla-daemon]

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

Bug ID: 144389
   Summary: Assertion when launching query design (with Orca)
   Product: LibreOffice
   Version: 7.3.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Base
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: serval2...@yahoo.fr

Description:
On pc Debian x86-64 with master sources updated today + enable-dbgutil, I got
an assertion when opening the attached file then "Create Query in Design View"
with Orca started

Steps to Reproduce:
1. Start Orca
2. Launch attached file
3. Click on Queries icon at left
4. Click on "Create Query in Design View"

Actual Results:
Assertion

Expected Results:
No assertion


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: 1f2bb0a065c44fce4a85f2a223076250317de864
CPU threads: 12; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: fr-FR (fr_FR.UTF-8); UI: en-US
Calc: threaded

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

[Libreoffice-bugs] [Bug 144386] Calc doesn't start from Start Center

[bugzilla-daemon]

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

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

   Keywords||bibisected, bisected,
   ||regression

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

[Libreoffice-bugs] [Bug 120129] EDITING: LIST function in query creates additional characters in Windows10

[bugzilla-daemon]

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

--- Comment #10 from Mike Kaganski  ---
(In reply to Julien Nabet from comment #9)
> It may be already be fixed with tdf#144230 (put in see also).

No, I also saw *zero bytes* added to LIST output; and given that I don't know
much about how it should work, I thought it's how the BLOB should look like.
Looks like I need to take a look at it deep :-)

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

[Libreoffice-bugs] [Bug 144388] Libreoffice 7.2 upgrade after install the office suite won't launch

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #1 from Julien Nabet  ---
Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps ?

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

[Libreoffice-bugs] [Bug 120129] EDITING: LIST function in query creates additional characters in Windows10

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

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

--- Comment #9 from Julien Nabet  ---
It may be already be fixed with tdf#144230 (put in see also).

You can give a try to a daily build from
https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF/current/
(of course, it's just for the test since it's a dev version).

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

[Libreoffice-bugs] [Bug 144338] UI Connected spinbox not updated when value is typed into the field

[bugzilla-daemon]

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

--- Comment #13 from Telesto  ---
Created attachment 174900
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174900=edit
Screencast Faststone Image viewer

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

[Libreoffice-bugs] [Bug 143868] Mac Fonts are too large on non-retina display - UI

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

 Resolution|--- |NOTOURBUG
 Status|UNCONFIRMED |RESOLVED
 CC||vstuart.fo...@utsa.edu

--- Comment #2 from V Stuart Foote  ---
adjust your scaling for the external monitor

=-ref-=
[1]
https://apple.stackexchange.com/questions/193723/scaling-all-ui-elements-when-using-an-external-monitor

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

[Libreoffice-bugs] [Bug 101646] UI option "Scaling" was removed

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

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

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

[Libreoffice-bugs] [Bug 144075] Fonts in interface and preferences are too small.

[bugzilla-daemon]

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

V Stuart Foote  changed:

   What|Removed |Added

Version|Inherited From OOo  |7.1.4.2 release
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=10
   ||1646
 Resolution|--- |NOTOURBUG
 Status|UNCONFIRMED |RESOLVED

--- Comment #11 from V Stuart Foote  ---
(In reply to MarjaE from comment #7)
> Created attachment 174749 [details]
> LibreOffice Prefs on a 21.5" screen.

Perfectly readable, font is about 40% of the icons.

If you need larger text (and I'd assume other UI elements) configure the OS for
the external monitor [1]

LibreOffice individual UI component scaling was removed as unsupportable at
5.3.0 release, reimplementing a framework with support for HiDPI displays
(other than os/DE scaling) is what bug 101646 remains open for.

=-ref-=
[1]
https://apple.stackexchange.com/questions/193723/scaling-all-ui-elements-when-using-an-external-monitor

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

[Libreoffice-bugs] [Bug 144338] UI Connected spinbox not updated when value is typed into the field

[bugzilla-daemon]

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

--- Comment #12 from Telesto  ---
Created attachment 174899
  --> https://bugs.documentfoundation.org/attachment.cgi?id=174899=edit
Screencast XnView

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