[Libreoffice-bugs] [Bug 148073] Consider renaming menu item "Search Commands"
https://bugs.documentfoundation.org/show_bug.cgi?id=148073 --- Comment #4 from Adolfo Jayme Barrientos --- Neither the existing name nor the proposed one cut it for me. It should have been called Command Palette, as most other software with this feature does. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 148073] Consider renaming menu item "Search Commands"
https://bugs.documentfoundation.org/show_bug.cgi?id=148073 --- Comment #4 from Adolfo Jayme Barrientos --- Neither the existing name nor the proposed one cut it for me. It should have been called Command Palette, as most other software with this feature does. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 147553] Saving basic macro results in excessive cpu usage; freezes Calc for 20+ seconds
https://bugs.documentfoundation.org/show_bug.cgi?id=147553 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 147788] Word document containing equations is imported incorrectly/incompletely
https://bugs.documentfoundation.org/show_bug.cgi?id=147788 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 147783] Cannot undo typing in Hyperlink dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=147783 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 147777] Dropdown menus open in the middle of screen and immediately close or does not open at all
https://bugs.documentfoundation.org/show_bug.cgi?id=14 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 147771] Impress. If remove all characters in any cell in the table of attach file, save and reopen then return character
https://bugs.documentfoundation.org/show_bug.cgi?id=147771 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 147770] Need better, more intuitive, Insert Caption behavior
https://bugs.documentfoundation.org/show_bug.cgi?id=147770 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 147552] Changing the axis number, and then bar color results calc 7.4 to exit.
https://bugs.documentfoundation.org/show_bug.cgi?id=147552 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147552] Changing the axis number, and then bar color results calc 7.4 to exit.
https://bugs.documentfoundation.org/show_bug.cgi?id=147552 --- Comment #10 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61189] PDF printing mode problem: HP LaserJet + media type + no tray + user prompt (refer comment #10)
https://bugs.documentfoundation.org/show_bug.cgi?id=61189 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 108800] [META] Print related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108800 Bug 108800 depends on bug 61189, which changed state. Bug 61189 Summary: PDF printing mode problem: HP LaserJet + media type + no tray + user prompt (refer comment #10) https://bugs.documentfoundation.org/show_bug.cgi?id=61189 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61189] PDF printing mode problem: HP LaserJet + media type + no tray + user prompt (refer comment #10)
https://bugs.documentfoundation.org/show_bug.cgi?id=61189 --- Comment #74 from QA Administrators --- Dear crxssi, 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 143972] Crash in: mergedlo.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=143972 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 143972] Crash in: mergedlo.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=143972 --- Comment #3 from QA Administrators --- Dear Ketil Skipnes, 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 143948] Clone formatting tool doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=143948 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 143948] Clone formatting tool doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=143948 --- Comment #8 from QA Administrators --- Dear Bob Rich, 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 144575] Writer auto formats formula objects
https://bugs.documentfoundation.org/show_bug.cgi?id=144575 --- Comment #2 from QA Administrators --- Dear delaparra.damian, 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 38727] FILEOPEN, EDITING: Cross-reference to bookmark on DDE data does not update on file open
https://bugs.documentfoundation.org/show_bug.cgi?id=38727 --- Comment #9 from QA Administrators --- Dear trumpton9, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148092] New: LibreOffice dark theme color scheme doesn't replace the light gray background color for the comments sidebar column
https://bugs.documentfoundation.org/show_bug.cgi?id=148092 Bug ID: 148092 Summary: LibreOffice dark theme color scheme doesn't replace the light gray background color for the comments sidebar column Product: LibreOffice Version: 7.2.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nekoh...@gmail.com Created attachment 178980 --> https://bugs.documentfoundation.org/attachment.cgi?id=178980=edit screenshot In Options > LibreOffice > Application Colors > Scheme, you can tell the app to use the "LibreOffice Dark" color scheme, which is great, except that the comments in Writer look wrong as they still float on a light gray background. They should be on some color that is either slightly darker or slightly lighter than the "Document background" #33 color. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147776] a slide exported as SVG from Impress should Just Work and not require JavaScript
https://bugs.documentfoundation.org/show_bug.cgi?id=147776 --- Comment #3 from skierpage --- A slide exported from Impress as SVG also won't preview in the KDE Dolphin file manager, and the cairosvg converter converts it to a blank PNG, and you can't upload it to Wikipedia; all because it contains 450 kB of JavaScript. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147776] a slide exported as SVG from Impress should Just Work and not require JavaScript
https://bugs.documentfoundation.org/show_bug.cgi?id=147776 --- Comment #2 from skierpage --- Created attachment 178979 --> https://bugs.documentfoundation.org/attachment.cgi?id=178979=edit simple slide exported as SVG whose "TEXT ON MASTER SLIDE" doesn't appear in Inkscape and doesn't work without JavaScript This simple slide exported from Libre Office Impress has 450 kB of JavaScript in it, and won't render properly unless the SVG viewer runs the script. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148091] Tofu characters are displayed in Today's hint #34 so the hint is not readable
https://bugs.documentfoundation.org/show_bug.cgi?id=148091 --- Comment #1 from nishi2015_1...@yahoo.co.jp --- Created attachment 178978 --> https://bugs.documentfoundation.org/attachment.cgi?id=178978=edit Screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148091] New: Tofu characters are displayed in Today's hint #34 so the hint is not readable
https://bugs.documentfoundation.org/show_bug.cgi?id=148091 Bug ID: 148091 Summary: Tofu characters are displayed in Today's hint #34 so the hint is not readable Product: LibreOffice Version: 7.2.5.2 release Hardware: Other OS: macOS (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Linguistic Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nishi2015_1...@yahoo.co.jp CC: so...@libreoffice.org Description: Tofu characters are displayed in Today's hint #34 so the hint is not readable. Its screenshot will be attached later. Steps to Reproduce: 1.Start LibreOffice 2.Open a file 3.Check the today's hint #34 Actual Results: There are tofu characters in the description of the hint. So user is not be able to read the hint. Expected Results: No tofu Reproducible: Always User Profile Reset: No Additional Info: Libre Office Version:7.2.6.2 Language* Japanese -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147776] a slide exported as SVG from Impress should Just Work and not require JavaScript
https://bugs.documentfoundation.org/show_bug.cgi?id=147776 --- Comment #1 from skierpage --- Created attachment 178977 --> https://bugs.documentfoundation.org/attachment.cgi?id=178977=edit simple slide whose "TEXT ON MASTER SLIDE" doesn't appear in Inkscape when exported as SVG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147553] Saving basic macro results in excessive cpu usage; freezes Calc for 20+ seconds
https://bugs.documentfoundation.org/show_bug.cgi?id=147553 Scott Clewell changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Scott Clewell --- Hello David, Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148090] Drop-down menus do not open upon clicking them
https://bugs.documentfoundation.org/show_bug.cgi?id=148090 --- Comment #2 from Adam --- I should have encoded the video with a more ubiquitous codec to ensure people can play it. I used libx265, VLC should play it fine - along with anything else using a ffmpeg backend for decoding. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148090] Drop-down menus do not open upon clicking them
https://bugs.documentfoundation.org/show_bug.cgi?id=148090 --- Comment #1 from Adam --- Created attachment 178976 --> https://bugs.documentfoundation.org/attachment.cgi?id=178976=edit Video demonstration of reproducing the bug This is a video demonstration of reproducing the bug. You can see in the video I am using LibreOffice Writer and attempt to click the drop-downs multiple times without success. I then scroll through the options of the drop-down element using the mousewheel and it works. I select options using the enter key on the keyboard. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148090] New: Drop-down menus do not open upon clicking them
https://bugs.documentfoundation.org/show_bug.cgi?id=148090 Bug ID: 148090 Summary: Drop-down menus do not open upon clicking them Product: LibreOffice Version: 7.3.1.3 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: adampoke...@gmail.com Description: Upon clicking one of the drop-down menus in any LibreOffice application, the menu will not open. Focusing the UI element and then manually scrolling the mousewheel and pressing enter works and am able to change selection and confirm selection that way. Steps to Reproduce: 1. Open any LibreOffice suite application, Writer for example 2. Click on any of the drop-downs, for example font face or font size 3. Observe the menu not opening, or sometimes opening for a brief moment in the centre of the screen then disappearing Actual Results: the drop-down menu does not open, or sometimes opening for a brief moment it opens in the centre of the screen before disappearing Expected Results: The drop-down menu should have opened when the mouse was clicked in correct place Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.3.1.3 / LibreOffice Community Build ID: 30(Build:3) CPU threads: 16; OS: Linux 5.16; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-US 7.3.1-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100390] FILESAVE: OOXML export of cloud shape leaves cloud partially unfilled
https://bugs.documentfoundation.org/show_bug.cgi?id=100390 Regina Henschel changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |rb.hensc...@t-online.de |desktop.org | CC||rb.hensc...@t-online.de --- Comment #10 from Regina Henschel --- This overlaps with my work on bug 147978. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144597] Changes to fonts will not save
https://bugs.documentfoundation.org/show_bug.cgi?id=144597 Dutch changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |bdk...@icloud.com |desktop.org | --- Comment #3 from Dutch --- So what part of this do you not understand? Description: I have a number of .csv files. They all open with an unreadable font size. Changing the font and font size will not save. Have tried "save" from 3 locations. Always revert to original font. Steps to Reproduce: 1. Start csv file 2. change fonts to larger and other font 3. Save Actual Results: No change to fonts or font size Expected Results: new font -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147982] On macOS Monterey LibreOffice 7.3 crashes about every day. This was also with previous versions of LibreOffice.
https://bugs.documentfoundation.org/show_bug.cgi?id=147982 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #7 from Julien Nabet --- Do you use a Mac with Intel or Arm processor? If you use Arm processor, you can try "Apple Silicon" version on https://www.libreoffice.org/download/download/ if it's not already the case. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 53027] EDITING: dBase-Import-Wizard fails when trying to append DECIMAL(NUMERIC) and BOOLEAN data types
https://bugs.documentfoundation.org/show_bug.cgi?id=53027 --- Comment #54 from asdxx --- kooragoal https://www.kooragoal.live/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147432] Many backups (like 1889 in 10 minutes) automatically created while editing queries in SQL-view
https://bugs.documentfoundation.org/show_bug.cgi?id=147432 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #5 from Julien Nabet --- At which location do you see these backups, the same as the original file? /tmp? other? Do you reproduce this only with this specific file or with any odb file? (or perhaps any odb file using Firebird embedded) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148089] New: Pressing Ctrl+End while editing a slide moves slide rather than moving to end of slide's text
https://bugs.documentfoundation.org/show_bug.cgi?id=148089 Bug ID: 148089 Summary: Pressing Ctrl+End while editing a slide moves slide rather than moving to end of slide's text Product: LibreOffice Version: 7.2.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rstew...@ptd.net Description: The focus seems to stay with the slide, in the Slide Pane, rather than on the slide text, when clicking on the first bullet of an existing slide and pressing Ctrl+End. Steps to Reproduce: 1. Click at the beginning of the first bullet in an existing slide. 2. Press Ctrl+End (also Ctrl+Shift+End). Actual Results: The slide moves to the end of the presentation. Expected Results: Obviously, with focus on the text in the bullets, Ctrl+End should move to the end of the last bullet, and if Shift is also depressed, all should be selected. The slide, in the Slide Pane, should not have focus. Reproducible: Always User Profile Reset: No Additional Info: I don't know what other shortcuts might act upon the slide rather than the bullet text, but I wouldn't be surprised but what others, like Ctrl+Home, would behave similarly, since it seems like a focus issue. Version: 7.2.3.2 (x64) / LibreOffice Community Build ID: d166454616c1632304285822f9c83ce2e660fd92 CPU threads: 16; OS: Windows 10.0 Build 22000; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148025] Leading spaces lost copying from pdf
https://bugs.documentfoundation.org/show_bug.cgi?id=148025 --- Comment #3 from flywire --- Pasting the selection from https://pdf-xchange.eu/ will contain the required blank lines *if* it is written in the pdf. LibreOffice does not write blank lines in the pdf. I suggest an enhancement to tweak the format to support it. eg: stream /F1 10 Tf BT 40 763.07751 Td 0 -11.0775 Td (Lorem ipsum dolor sit amet,) Tj 0 -11.0775 Td (consectetur adipiscing ) Tj 0 -11.0775 Td () Tj 0 -11.0775 Td (elit. sed do eiusmod) Tj ET endstream Decoded LibreOffice pdf: stream 0.1 w q 0 0.028 595.275 841.861 re W* n q 0 0 0 rg BT 56.8 776.789 Td /F1 10 Tf<0102030405020606070809070A06010B0C0D>Tj ET Q q 0 0 0 rg BT 56.8 765.489 Td /F1 10 Tf<040404040E0A0F10110B1213020606070414070A060115120C04>Tj ET Q q 0 0 0 rg BT 56.8 742.789 Td /F1 10 Tf<05020606070809070A06010B0C>Tj ET Q Q endstream There is no "() Tj" for blank line (unpacking the characters within the lines is not important to demonstrate this). Indented code is a potential complication that could be overcome by formatting it left aligned. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'distro/collabora/co-2021' - vcl/source
vcl/source/app/salvtables.cxx |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) New commits: commit f9aa206a7eb4dc625567925e86024eacb2a7436a Author: Caolán McNamara AuthorDate: Sun Feb 28 19:49:52 2021 + Commit: Andras Timar CommitDate: Sat Mar 19 23:01:21 2022 +0100 add NoMouseUpClose to popup flags Conflicts: vcl/source/app/salvtables.cxx Change-Id: Ib26f258bb00456392c41ec85a1002545433839a4 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/111718 Tested-by: Jenkins Reviewed-by: Caolán McNamara (cherry picked from commit 52f9caa248ff3893c6c36c5730e0210c3ad21189) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/131740 Tested-by: Jenkins CollaboraOffice Reviewed-by: Andras Timar diff --git a/vcl/source/app/salvtables.cxx b/vcl/source/app/salvtables.cxx index 8ed59e9f3e6e..97330df96b58 100644 --- a/vcl/source/app/salvtables.cxx +++ b/vcl/source/app/salvtables.cxx @@ -6592,7 +6592,8 @@ void SalInstancePopover::popup_at_rect(weld::Widget* pParent, const tools::Recta aRect.SetRight(aPt.X()); aRect.SetBottom(aPt.Y()); -FloatWinPopupFlags nFlags = FloatWinPopupFlags::Down | FloatWinPopupFlags::GrabFocus; +FloatWinPopupFlags nFlags = FloatWinPopupFlags::Down | FloatWinPopupFlags::GrabFocus +| FloatWinPopupFlags::NoMouseUpClose; m_xPopover->EnableDocking(); DockingManager* pDockingManager = vcl::Window::GetDockingManager(); pDockingManager->SetPopupModeEndHdl(m_xPopover,
[Libreoffice-bugs] [Bug 147566] Search slot does not warn that formatting has been applied
https://bugs.documentfoundation.org/show_bug.cgi?id=147566 --- Comment #7 from Jim Raykowski --- (In reply to Anduril from comment #6) > Alternatively the search and replace window and the find tab could work > independently: the former would retain the applied changes, while the latter > would only perform simple searches, without inheriting the formatting of the > former. That's exactly what the patch does :) I've been trying to figure out why it fails a uitest on the remote build but not local :( -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: external/libfixmath include/tools solenv/clang-format tools/Library_tl.mk tools/source vcl/Library_vcl.mk vcl/source
external/libfixmath/LICENSE | 20 -
external/libfixmath/fix16.c | 511
external/libfixmath/fix16.h | 333 --
external/libfixmath/int64.h | 177 -
include/tools/fix16.hxx | 40 +++
solenv/clang-format/excludelist |3
tools/Library_tl.mk |1
tools/source/misc/fix16.cxx | 172 +
vcl/Library_vcl.mk |2
vcl/source/fontsubset/fixmath.c | 13 -
vcl/source/fontsubset/fixmath.h | 23 -
vcl/source/fontsubset/sft.cxx |2
12 files changed, 214 insertions(+), 1083 deletions(-)
New commits:
commit 59a7c40255b836ed75e64686fabb3e9938b755f0
Author: Caolán McNamara
AuthorDate: Sat Mar 19 14:48:13 2022 +
Commit: Caolán McNamara
CommitDate: Sat Mar 19 22:56:05 2022 +0100
reduce down to the part and config we are using and move to tools
Change-Id: Ifaddc59c3c7834808d368c138a5ec7c0b80db14c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/131850
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/external/libfixmath/LICENSE b/external/libfixmath/LICENSE
deleted file mode 100644
index cf0aefe08af4..
--- a/external/libfixmath/LICENSE
+++ /dev/null
@@ -1,20 +0,0 @@
-libfixmath is Copyright (c) 2011-2021 Flatmush ,
-Petteri Aimonen , & libfixmath AUTHORS
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
diff --git a/external/libfixmath/fix16.c b/external/libfixmath/fix16.c
deleted file mode 100644
index 053f6794f4b2..
--- a/external/libfixmath/fix16.c
+++ /dev/null
@@ -1,511 +0,0 @@
-#include "fix16.h"
-#include "int64.h"
-
-
-/* Subtraction and addition with overflow detection.
- * The versions without overflow detection are inlined in the header.
- */
-#ifndef FIXMATH_NO_OVERFLOW
-fix16_t fix16_add(fix16_t a, fix16_t b)
-{
-// Use unsigned integers because overflow with signed integers is
-// an undefined operation (http://www.airs.com/blog/archives/120).
-uint32_t _a = a;
-uint32_t _b = b;
-uint32_t sum = _a + _b;
-
-// Overflow can only happen if sign of a == sign of b, and then
-// it causes sign of sum != sign of a.
-if (!((_a ^ _b) & 0x8000) && ((_a ^ sum) & 0x8000))
-return fix16_overflow;
-
-return sum;
-}
-
-fix16_t fix16_sub(fix16_t a, fix16_t b)
-{
-uint32_t _a = a;
-uint32_t _b = b;
-uint32_t diff = _a - _b;
-
-// Overflow can only happen if sign of a != sign of b, and then
-// it causes sign of diff != sign of a.
-if (((_a ^ _b) & 0x8000) && ((_a ^ diff) & 0x8000))
-return fix16_overflow;
-
-return diff;
-}
-
-/* Saturating arithmetic */
-fix16_t fix16_sadd(fix16_t a, fix16_t b)
-{
-fix16_t result = fix16_add(a, b);
-
-if (result == fix16_overflow)
-return (a >= 0) ? fix16_maximum : fix16_minimum;
-
-return result;
-}
-
-fix16_t fix16_ssub(fix16_t a, fix16_t b)
-{
-fix16_t result = fix16_sub(a, b);
-
-if (result == fix16_overflow)
-return (a >= 0) ? fix16_maximum : fix16_minimum;
-
-return result;
-}
-#endif
-
-
-
-/* 64-bit implementation for fix16_mul. Fastest version for e.g. ARM Cortex M3.
- * Performs a 32*32 -> 64bit multiplication. The middle 32 bits are the result,
- * bottom 16 bits are used for rounding, and upper 16 bits are used for
overflow
- * detection.
- */
-
-#if !defined(FIXMATH_NO_64BIT) && !defined(FIXMATH_OPTIMIZE_8BIT)
-fix16_t fix16_mul(fix16_t inArg0, fix16_t inArg1)
-{
-int64_t product = (int64_t)inArg0 * inArg1;
-
-#ifndef FIXMATH_NO_OVERFLOW
-// The upper 17 bits should all be the same (the sign).
-uint32_t upper = (product >> 47);
-#endif
-
-if (product < 0)
-{
-#ifndef FIXMATH_NO_OVERFLOW
-if (~upper)
-return fix16_overflow;
-#endif
-
-#ifndef FIXMATH_NO_ROUNDING
-// This adjustment is required in order to round -1/2 correctly
-product--;
-
[Libreoffice-commits] core.git: vcl/win
vcl/win/window/salframe.cxx |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
New commits:
commit 892ef6e8b6888b3029041ab150b409f81a5c31b0
Author: Caolán McNamara
AuthorDate: Fri Mar 18 21:29:00 2022 +
Commit: Caolán McNamara
CommitDate: Sat Mar 19 22:10:42 2022 +0100
Related: tdf#118320 let windows icon theme know when a dark theme is
preferred
Change-Id: I7569814a575e3d7c216e790eb162397d312fa0e5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/131843
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/vcl/win/window/salframe.cxx b/vcl/win/window/salframe.cxx
index 5965e9225058..cd9449c1a4ae 100644
--- a/vcl/win/window/salframe.cxx
+++ b/vcl/win/window/salframe.cxx
@@ -2662,7 +2662,12 @@ void WinSalFrame::UpdateSettings( AllSettings& rSettings
)
Color aMenuBarTextColor;
Color aMenuBarRolloverTextColor;
-if (UseDarkMode())
+const bool bUseDarkMode(UseDarkMode());
+
+OUString sThemeName(!bUseDarkMode ? u"colibre" : u"colibre_dark");
+aStyleSettings.SetPreferredIconTheme(sThemeName, bUseDarkMode);
+
+if (bUseDarkMode)
{
SetWindowTheme(mhWnd, L"Explorer", nullptr);
[Libreoffice-bugs] [Bug 118320] Add support for Windows 10/11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118320 --- Comment #84 from Commit Notification --- Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/892ef6e8b6888b3029041ab150b409f81a5c31b0 Related: tdf#118320 let windows icon theme know when a dark theme is preferred It will be available in 7.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/win
vcl/win/gdi/salnativewidgets-luna.cxx | 37 +-
1 file changed, 36 insertions(+), 1 deletion(-)
New commits:
commit 348407dfdf5fd41b99f5998463eb032128799555
Author: Caolán McNamara
AuthorDate: Sat Mar 19 19:42:48 2022 +
Commit: Caolán McNamara
CommitDate: Sat Mar 19 21:52:25 2022 +0100
Related: tdf#118320 tabitems appear as light in darkmode
so use a Button theme and matching button properties for drawing those
instead as a workaround
Change-Id: I5ba0e360adc109e80ab7ecb1ff2fd5bc84028b61
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/131852
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/vcl/win/gdi/salnativewidgets-luna.cxx
b/vcl/win/gdi/salnativewidgets-luna.cxx
index 805db681a211..b58731f1db42 100644
--- a/vcl/win/gdi/salnativewidgets-luna.cxx
+++ b/vcl/win/gdi/salnativewidgets-luna.cxx
@@ -813,6 +813,32 @@ static bool ImplDrawNativeControl( HDC hDC, HTHEME hTheme,
RECT rc,
iState = TILES_FOCUSED;// may need to draw focus rect
else
iState = TILES_NORMAL;
+
+// tabitem in tabcontrols gets drawn in "darkmode" as if it was a
+// a "light" theme, so bodge this by drawing with a button instead
+if (UseDarkMode())
+{
+iPart = BP_PUSHBUTTON;
+switch (iState)
+{
+case TILES_DISABLED:
+iState = PBS_DISABLED;
+break;
+case TILES_SELECTED:
+iState = PBS_PRESSED;
+break;
+case TILES_HOT:
+iState = PBS_HOT;
+break;
+case TILES_FOCUSED:
+iState = PBS_DEFAULTED;
+break;
+default:
+iState = PBS_NORMAL;
+break;
+}
+}
+
return ImplDrawTheme( hTheme, hDC, iPart, iState, rc, aCaption);
}
@@ -1148,9 +1174,18 @@ bool WinSalGraphics::drawNativeControl( ControlType
nType,
break;
case ControlType::TabPane:
case ControlType::TabBody:
-case ControlType::TabItem:
hTheme = getThemeHandle(mhWnd, L"Tab", mpImpl.get());
break;
+case ControlType::TabItem:
+if (bUseDarkMode)
+{
+// tabitem in tabcontrols gets drawn in "darkmode" as if it
was a
+// a "light" theme, so bodge this by drawing with a button
instead
+hTheme = getThemeHandle(mhWnd, L"Button", mpImpl.get());
+}
+else
+hTheme = getThemeHandle(mhWnd, L"Tab", mpImpl.get());
+break;
case ControlType::Toolbar:
if( nPart == ControlPart::Entire || nPart == ControlPart::Button )
hTheme = getThemeHandle(mhWnd, L"Toolbar", mpImpl.get());
[Libreoffice-bugs] [Bug 118320] Add support for Windows 10/11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118320 --- Comment #83 from Commit Notification --- Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/348407dfdf5fd41b99f5998463eb032128799555 Related: tdf#118320 tabitems appear as light in darkmode It will be available in 7.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: vcl/source
vcl/source/gdi/TypeSerializer.cxx | 21 +
1 file changed, 17 insertions(+), 4 deletions(-)
New commits:
commit 32dc2d14287a4210589c33dbd62c6e36e095aa6e
Author: Caolán McNamara
AuthorDate: Fri Mar 18 19:50:12 2022 +
Commit: Caolán McNamara
CommitDate: Sat Mar 19 21:52:01 2022 +0100
ofz#45583 detect some invalid scale cases at import time
Change-Id: Iad881f09bef707897e19d402a9931a6dea88f52d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/131839
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/vcl/source/gdi/TypeSerializer.cxx
b/vcl/source/gdi/TypeSerializer.cxx
index fb054e4748ef..829bc0503e1d 100644
--- a/vcl/source/gdi/TypeSerializer.cxx
+++ b/vcl/source/gdi/TypeSerializer.cxx
@@ -425,6 +425,22 @@ void TypeSerializer::writeGraphic(const Graphic& rGraphic)
}
}
+static bool UselessScaleForMapMode(const Fraction& rScale)
+{
+if (!rScale.IsValid())
+return true;
+// ImplLogicToPixel will multiply its values by this numerator * dpi and
then double that
+// result before dividing
+constexpr sal_Int32 nTypicalDPI = 96;
+if (rScale.GetNumerator() > std::numeric_limits::max() /
nTypicalDPI / 2)
+return true;
+if (rScale.GetNumerator() < std::numeric_limits::min() /
nTypicalDPI / 2)
+return true;
+if (static_cast(rScale) < 0.0)
+return true;
+return false;
+}
+
void TypeSerializer::readMapMode(MapMode& rMapMode)
{
VersionCompatRead aCompat(mrStream);
@@ -441,10 +457,7 @@ void TypeSerializer::readMapMode(MapMode& rMapMode)
readFraction(aScaleY);
mrStream.ReadCharAsBool(bSimple);
-const bool bBogus = !aScaleX.IsValid() || !aScaleY.IsValid()
-|| aScaleX.GetNumerator() ==
std::numeric_limits::min()
-|| aScaleY.GetNumerator() ==
std::numeric_limits::min()
-|| static_cast(aScaleX) < 0.0 ||
static_cast(aScaleY) < 0.0;
+const bool bBogus = UselessScaleForMapMode(aScaleX) ||
UselessScaleForMapMode(aScaleY);
SAL_WARN_IF(bBogus, "vcl", "invalid scale");
if (bSimple || bBogus)
[Libreoffice-bugs] [Bug 147641] OPTIONS DIALOG: Configuring default font size for captions always reset to 12 points
https://bugs.documentfoundation.org/show_bug.cgi?id=147641 raal changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected CC||noelgran...@gmail.com, ||r...@post.cz --- Comment #7 from raal --- This seems to have begun at the below commit. Adding Cc: to Noel Grandin ; Could you possibly take a look at this one? Thanks 15ca471a7c629e7eb27254fbe371bd2f1ebcc2ac is the first bad commit commit 15ca471a7c629e7eb27254fbe371bd2f1ebcc2ac Author: Jenkins Build User Date: Fri Nov 9 14:52:01 2018 +0100 source sha:65d2d2647ead42e5bbb7800f14c047f383fe450b https://git.libreoffice.org/core/+/65d2d2647ead42e5bbb7800f14c047f383fe450b loplugin:singlevalfields in sw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130695] EDITING: in custom dictionary, let abbreviations have trailing periods
https://bugs.documentfoundation.org/show_bug.cgi?id=130695 Nick Levinson changed: What|Removed |Added Summary|EDITING: in custom |EDITING: in custom |dictionary, let |dictionary, let |abbreviations have periods |abbreviations have trailing ||periods -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104927] Text Import - fixed width mode not adjusting csvtablebox for multi-byte fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=104927 --- Comment #12 from Commit Notification --- Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-7-3": https://git.libreoffice.org/core/commit/1ec1e1b6f9353159376419d37ac8d8584312671e Resolves: tdf#148054 Advance offset for all columns, tdf#104927 regression It will be available in 7.3.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104927] Text Import - fixed width mode not adjusting csvtablebox for multi-byte fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=104927 Commit Notification changed: What|Removed |Added Whiteboard|target:7.2.0 target:7.4.0 |target:7.2.0 target:7.4.0 ||target:7.3.3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-3' - sc/source
sc/source/ui/docshell/impex.cxx | 73
1 file changed, 44 insertions(+), 29 deletions(-)
New commits:
commit 1ec1e1b6f9353159376419d37ac8d8584312671e
Author: Eike Rathke
AuthorDate: Thu Mar 17 22:44:26 2022 +0100
Commit: Caolán McNamara
CommitDate: Sat Mar 19 20:24:18 2022 +0100
Resolves: tdf#148054 Advance offset for all columns, tdf#104927 regression
Regression from
commit 621c189173b35ac7f5ce4c578f57045479c63ab6
CommitDate: Sat Jan 9 05:13:55 2021 +0100
tdf#104927 consider character width for CSV import
that for fixed width introduced a visual count of character widths
for CJK IVS characters but did not advance the character offset
for skipped hidden columns.
Instead of having to ask bDetermineRange three times in the loop,
split off an extra loop for bDetermineRange, advancing the offset
then is straight forward and just only non-skipped columns are
extracted and written to document.
Change-Id: Ib6ab6b68c5fc0f6ff854d629d75742c39ed6ddf5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/131722
Reviewed-by: Eike Rathke
Tested-by: Jenkins
(cherry picked from commit 6b768542ddd52573bbdb0e7b5b85ce5a9dd4551d)
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/131605
Reviewed-by: Caolán McNamara
diff --git a/sc/source/ui/docshell/impex.cxx b/sc/source/ui/docshell/impex.cxx
index 1c21a67562e2..3e257bbcfbc7 100644
--- a/sc/source/ui/docshell/impex.cxx
+++ b/sc/source/ui/docshell/impex.cxx
@@ -1616,40 +1616,55 @@ bool ScImportExport::ExtText2Doc( SvStream& rStrm )
bool bMultiLine = false;
if ( bFixed ) // Fixed line length
{
-sal_Int32 nStartIdx = 0;
-// Yes, the check is nCol<=rDoc.MaxCol()+1, +1 because it is
only an
-// overflow if there is really data following to be put behind
-// the last column, which doesn't happen if info is
-// SC_COL_SKIP.
-for ( i=0; i rDoc.MaxCol())
-bOverflowCol = true;// display warning on
import
-else if (!bDetermineRange)
+const sal_uInt8 nFmt = pColFormat[i];
+if (nFmt != SC_COL_SKIP)// otherwise don't
increment nCol either
+{
+if (nCol > rDoc.MaxCol())
+bOverflowCol = true;// display warning on
import
+++nCol;
+}
+}
+}
+else
+{
+sal_Int32 nStartIdx = 0;
+// Same maxcol+1 check reason as above.
+for (i=0; i < nInfoCount && nCol <= rDoc.MaxCol()+1; ++i)
+{
+sal_Int32 nNextIdx = nStartIdx;
+if (i + 1 < nInfoCount)
+CountVisualWidth( aLine, nNextIdx, pColStart[i+1]
- pColStart[i] );
+else
+nNextIdx = nLineLen;
+sal_uInt8 nFmt = pColFormat[i];
+if (nFmt != SC_COL_SKIP)// otherwise don't
increment nCol either
{
-sal_Int32 nNextIdx = nStartIdx;
-if ( i + 1 < nInfoCount )
-CountVisualWidth( aLine, nNextIdx,
pColStart[i+1] - pColStart[i] );
+if (nCol > rDoc.MaxCol())
+bOverflowCol = true;// display warning on
import
else
-nNextIdx = nLineLen;
-
-bool bIsQuoted = false;
-aCell = lcl_GetFixed( aLine, nStartIdx, nNextIdx,
bIsQuoted, bOverflowCell );
-if (bIsQuoted && bQuotedAsText)
-nFmt = SC_COL_TEXT;
-
-bMultiLine |= lcl_PutString(
-aDocImport, !mbOverwriting, nCol, nRow, nTab,
aCell, nFmt,
-, bDetectNumFormat,
bEvaluateFormulas, bSkipEmptyCells,
-aTransliteration, aCalendar,
-pEnglishTransliteration.get(),
pEnglishCalendar.get());
-
-nStartIdx = nNextIdx;
+{
+bool bIsQuoted = false;
+aCell = lcl_GetFixed( aLine, nStartIdx,
nNextIdx, bIsQuoted, bOverflowCell );
+if (bIsQuoted && bQuotedAsText)
+nFmt = SC_COL_TEXT;
+
+bMultiLine |= lcl_PutString(
+
[Libreoffice-bugs] [Bug 130695] EDITING: in custom dictionary, let abbreviations have periods
https://bugs.documentfoundation.org/show_bug.cgi?id=130695 --- Comment #3 from Nick Levinson --- The bug was still recently present, including in Safe Mode. The only difference in applying STR to this test is that the desired user dictionary was not preselected, and that's only because I had created an additional dictionary, which was preselected, so I selected the desired dictionary and found the new entries that lacked trailing periods. Before the latest update per Fedora Linux: LO: From Help > About: Version: 7.2.5.2.0+ Build ID: 20(Build:2) CPU threads: 2; OS: Linux 5.16; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I'm not prepared to install another LO version. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148079] Headers and Footers are being duplicated on conversion from .docx to .pdf
https://bugs.documentfoundation.org/show_bug.cgi?id=148079 --- Comment #5 from julian.garb...@gmail.com --- Created attachment 178975 --> https://bugs.documentfoundation.org/attachment.cgi?id=178975=edit example docx for reproducing the described bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: hwpfilter/source
hwpfilter/source/hwpreader.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit ef37fa084e55aa13ecebcd0ebdbc7c2bca908c11
Author: Caolán McNamara
AuthorDate: Sat Mar 19 14:39:30 2022 +
Commit: Caolán McNamara
CommitDate: Sat Mar 19 20:09:53 2022 +0100
ofz: Null-dereference READ
Change-Id: Ie42af72e321bd55e3373aca33f0bcb6884bf8836
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/131849
Tested-by: Jenkins
Reviewed-by: Caolán McNamara
diff --git a/hwpfilter/source/hwpreader.cxx b/hwpfilter/source/hwpreader.cxx
index 13e60e21590d..8c84970867ba 100644
--- a/hwpfilter/source/hwpreader.cxx
+++ b/hwpfilter/source/hwpreader.cxx
@@ -3570,7 +3570,7 @@ void HwpReader::makeFormula(TxtBox * hbox)
pPar = hbox->plists[0].empty() ? nullptr : hbox->plists[0].front().get();
while( pPar )
{
-for( n = 0; n < pPar->nch && pPar->hhstr[n]->hh;
+for( n = 0; n < pPar->nch && pPar->hhstr.count(n) &&
pPar->hhstr[n]->hh;
n += pPar->hhstr[n]->WSize() )
{
if (l >= sizeof(mybuf)-7)
[Libreoffice-bugs] [Bug 147552] Changing the axis number, and then bar color results calc 7.4 to exit.
https://bugs.documentfoundation.org/show_bug.cgi?id=147552 --- Comment #9 from elias estatistics --- for 30 days: https://ufile.io/25i4u9c2 when Experimental features ON you can see on the video posted in the link that in the 2nd try libre calc crashed. I have found that it may crashing if you do other things too about graph. Graphic Drivers: Nouveau Linux: Kubuntu/Lubuntu with Bullseye kernel. Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 566ee17c2709f9939145ddc7fbb1d61c35049321 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: el-GR (el_GR.UTF-8); UI: en-US Calc: threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148079] Headers and Footers are being duplicated on conversion from .docx to .pdf
https://bugs.documentfoundation.org/show_bug.cgi?id=148079 --- Comment #4 from René Pardon --- We have no ODT file, just a word document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118320] Add support for Windows 10/11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118320 --- Comment #82 from Pedro --- Created attachment 178974 --> https://bugs.documentfoundation.org/attachment.cgi?id=178974=edit Arrows to increase and decrease numbers The arrows highlighted in the red box do not obtain dark theme. This is minor compared to the issue with tabs in dialogs and the Tabbed UI. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148079] Headers and Footers are being duplicated on conversion from .docx to .pdf
https://bugs.documentfoundation.org/show_bug.cgi?id=148079 Timur changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #3 from Timur --- Please attach source ODT. Saving as DOCX should be tested first, then GUI and command conversion. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118320] Add support for Windows 10/11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118320 --- Comment #81 from Pedro --- --off-topic-- You don't do a great disservice in steering Windows users to a UI paradigm they are used to working with for the past 15 years and that they are confortable with. You have kids in high school that have known no other Office suite UI paradigm besides a tab-like UI. A great disservice would be to force them onto an UI paradigm they never saw in their lives using office suites if they want to use an open-source office suite. Well maybe they would just move to Only Office, which is another open source Office suite that is more agile in their development and that actually provides that familiar UI paradigm. I agree that it's a great disservice that there's always been so much outright hostility towards developing a well thought out Tabbed UI with a more appropriate code. If anyone wants to do it, they're welcome. Any talk of removing the Tabbed UI or disincentivize its use for Windows users, nor properly supporting is just downright hostility towards Windows users of LibreOffice. I welcome Caolán work towards this. If he has a Patreon account or something I would like to buy him lunch for this work. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118320] Add support for Windows 10/11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118320 --- Comment #80 from Pedro --- Created attachment 178973 --> https://bugs.documentfoundation.org/attachment.cgi?id=178973=edit Paragraph dialog Mike Kaganski screenshot in LibreOffice Design Telegram channel showing Paragraph dialog after commit https://git.libreoffice.org/core/+/c43c4a00089b1965c7ef69ef40c9e645dffc2e43 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118320] Add support for Windows 10/11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118320 --- Comment #79 from Pedro --- Created attachment 178972 --> https://bugs.documentfoundation.org/attachment.cgi?id=178972=edit Bullets and numbering dialog Apparently the issue with the Tabbed UI is not restricted to the Tabbed UI itself but with tabbed dialogs themselves. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148088] New: UI: Dialog "Load Master Slide" should name "Load Master Page"
https://bugs.documentfoundation.org/show_bug.cgi?id=148088 Bug ID: 148088 Summary: UI: Dialog "Load Master Slide" should name "Load Master Page" Product: LibreOffice Version: 7.3.1.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lob...@web.de Created attachment 178971 --> https://bugs.documentfoundation.org/attachment.cgi?id=178971=edit draw dialog load master page Steps: 1. Open Draw 2. Open the dialog via Page - Master Page... - Button load... 3. Dialog appears with the title "Load Master Slide" Version: 7.3.1.3 (x64) / LibreOffice Community Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147566] Search slot does not warn that formatting has been applied
https://bugs.documentfoundation.org/show_bug.cgi?id=147566 --- Comment #6 from Anduril --- Alternatively the search and replace window and the find tab could work independently: the former would retain the applied changes, while the latter would only perform simple searches, without inheriting the formatting of the former. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 148073] Consider renaming menu item "Search Commands"
https://bugs.documentfoundation.org/show_bug.cgi?id=148073 --- Comment #3 from lol --- (In reply to Dave Barton from comment #2) > -1 > I see no advantage in making such a change. If the user does not already > know that the facility will also execute MOST commands, they will be > pleasantly surprised to discover that it does. How is the user supposed to know this? Sure, it's in the help. But the menu items should also reflect what the user can expect when selecting a menu item. > Not only does the additional > text bloat the menu, it adds unnecessary work for translators and > documentation. Why is the menu bloated? This menu item is then the longest in help menu. But that should not be an obstacle. There are other menu items that are longer. And why is it unnecessary work for translators and documentation? Two words should be added. That's not the big deal. Of course, in the documentation the effort will perhaps be greater, as it will probably have to be changed in several places. LibreOffice is constantly evolving. It's not a good idea to say we don't change menu items because the effort is too much. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 148073] Consider renaming menu item "Search Commands"
https://bugs.documentfoundation.org/show_bug.cgi?id=148073 --- Comment #3 from lol --- (In reply to Dave Barton from comment #2) > -1 > I see no advantage in making such a change. If the user does not already > know that the facility will also execute MOST commands, they will be > pleasantly surprised to discover that it does. How is the user supposed to know this? Sure, it's in the help. But the menu items should also reflect what the user can expect when selecting a menu item. > Not only does the additional > text bloat the menu, it adds unnecessary work for translators and > documentation. Why is the menu bloated? This menu item is then the longest in help menu. But that should not be an obstacle. There are other menu items that are longer. And why is it unnecessary work for translators and documentation? Two words should be added. That's not the big deal. Of course, in the documentation the effort will perhaps be greater, as it will probably have to be changed in several places. LibreOffice is constantly evolving. It's not a good idea to say we don't change menu items because the effort is too much. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148087] New: Assertion failed when editing a cell with an OnSelectionChange macro breakpoint triggered
https://bugs.documentfoundation.org/show_bug.cgi?id=148087 Bug ID: 148087 Summary: Assertion failed when editing a cell with an OnSelectionChange macro breakpoint triggered Product: LibreOffice Version: 7.3.0.0 alpha0+ Hardware: All OS: All Status: UNCONFIRMED Keywords: bibisectNotNeeded, regression Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com CC: noelgran...@gmail.com In a debug build: 1. Create any macro, e.g., empty one like this: sub OnSelectionChange end sub and put a breakpoint in it (e.g., to the "end sub" line). 2. In a new Calc document, assign this macro to the sheet's "Selection changed" event. 3. Click on any different cell and start typing. Note that nothing gets typed in the cell. 4. Return to Basic IDE, and see that the macro has the breakpoint triggered; resume execution (may be a couple of times) => crash because of failed assertion at https://opengrok.libreoffice.org/xref/core/editeng/source/editeng/impedit2.cxx?r=673a210b=118052=3119#3121 This line became an assert in commit https://git.libreoffice.org/core/+/e1972743d692c8d8611912c31aae2cb08ae7636d Noel: could you take a look at this, if something wrong happens here in these circumstances? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127590] [META] Application Programming Interface (API), when all scripted languages are affected
https://bugs.documentfoundation.org/show_bug.cgi?id=127590 Bug 127590 depends on bug 132145, which changed state. Bug 132145 Summary: "com.sun.star.sheet.GlobalSheetSettings" properties, "org.openoffice.Office.Math" and "org.openoffice.Office.Calc/Input/" entries are not synchronized https://bugs.documentfoundation.org/show_bug.cgi?id=132145 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132145] "com.sun.star.sheet.GlobalSheetSettings" properties, "org.openoffice.Office.Math" and "org.openoffice.Office.Calc/Input/" entries are not synchronized
https://bugs.documentfoundation.org/show_bug.cgi?id=132145 Mike Kaganski changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118320] Add support for Windows 10/11 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118320 --- Comment #78 from V Stuart Foote --- As Caolán notes: "Its possible it makes more sense to not try and use the windows control drawings apis and just set some dark colors and draw with the old built-in vcl widget rendering or alternative." The uxtheme.dll ShouldAppsUseDarkMode() and SetPreferredAppMode() mechanism is functional if not the best documented API [1] for Win32 WDM development, but much better than other suggested approach of reading a DWORD value from the Windows Registry. But as the APIs are structured it means we can only provide DarkMode to Win 10 build 1904 (18362) or later (with things still settling out for changes in Win 11). It can not support Win 7.1, 8, 8.1 or earlier builds of Win 10. How much of an issue is that? And as Caolán suggests are we better served to round out the VCL based "Application Colors" dialog with the additional widgets that need UI color assignment? [1] https://github.com/microsoft/WindowsAppSDK/issues/41 =-off-topic-= Given that the vaunted "Tabbed UI" MUFFIN assemblages for the Notebook Bar are not native MS "Ribbon framework" code it remains wrong to put that forward as a work alike, especially as the standard UI toolbars, menus and dialogs supplemented with the Sidebar deck are the documented (and fully supported) LibreOffice work flows cfross-platform. Absent a major refactoring there, we do a disservice to users by steering them to the Tabbed UI--but that is off topic. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103184] [META] UI theming bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103184 Mike Kaganski changed: What|Removed |Added Depends on||148086 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148086 [Bug 148086] Automatic icon theme should take dark mode into account -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148086] New: Automatic icon theme should take dark mode into account
https://bugs.documentfoundation.org/show_bug.cgi?id=148086 Bug ID: 148086 Summary: Automatic icon theme should take dark mode into account Product: LibreOffice Version: 7.4.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com Blocks: 103184 The automatic icon theme (Options->LibreOffice->View->Icon Theme->Automatic) most not only consider OS/environment (e.g., defaulting to Colibre on Windows), but also the dark mode (so it should be Colibre (dark) when dark mode is active). Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103184 [Bug 103184] [META] UI theming bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 75471] Newly opened LibO document frames stay in background (i. e. LibO does not get focus)
https://bugs.documentfoundation.org/show_bug.cgi?id=75471 Buovjaga changed: What|Removed |Added CC||maxim.egorush...@gmail.com --- Comment #84 from Buovjaga --- (In reply to Maxim Egorushkin from comment #83) > The issue still persists in Version: 6.4.7.2 Build ID: > 1:6.4.7-0ubuntu0.20.04.4 on KDE Neon 5.24. > > No other application suffers from such a bug, only LibreOffice. 1. Test with 7.3 2. If it still persists, create a new bug report -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131035] Not possible to save "background color" with a hatch in Area tab
https://bugs.documentfoundation.org/show_bug.cgi?id=131035 --- Comment #4 from sdc.bla...@youmail.dk --- Repro in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 7ac19fbce8a35f559eebb879cd0f232bfc95e703 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148085] New: Hyperlinks look bad (invisible / have no contrast) in dark mode on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=148085 Bug ID: 148085 Summary: Hyperlinks look bad (invisible / have no contrast) in dark mode on Windows Product: LibreOffice Version: 7.4.0.0 alpha0+ Master Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com Blocks: 103184 Created attachment 178970 --> https://bugs.documentfoundation.org/attachment.cgi?id=178970=edit About dialog in Dark Mode The attachment shows that the links in About dialog are very dark. For comparison, one could look how hyperlinks look in browsers on pages that honor dark mode (e.g., https://docs.microsoft.com/en-us/office/vba/language/reference/user-interface-help/dictionary-object in Chrome on Windows shows the links in much lighter blue on the dark background, which is clearly visible). Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103184 [Bug 103184] [META] UI theming bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103184] [META] UI theming bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103184 Mike Kaganski changed: What|Removed |Added Depends on||148085 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148085 [Bug 148085] Hyperlinks look bad (invisible / have no contrast) in dark mode on Windows -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147734] KeyID on image format import/export dialog is nothing in UI.
https://bugs.documentfoundation.org/show_bug.cgi?id=147734 20001...@protonmail.com <20001...@protonmail.com> changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131034] Selected hatching in Area tab - Hatch should keep selected indication when making modifications
https://bugs.documentfoundation.org/show_bug.cgi?id=131034 --- Comment #4 from sdc.bla...@youmail.dk --- repro in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 7ac19fbce8a35f559eebb879cd0f232bfc95e703 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148081] Copyable version info (for non-releases?) should include build date
https://bugs.documentfoundation.org/show_bug.cgi?id=148081 --- Comment #7 from Mike Kaganski --- (In reply to Mike Kaganski from comment #6) Note that I mean that exactly about QA; I see the "(for non-releases?)" part in the title, and argue with that in mind. QA people have different level of knowledge about the release process; and people who test dailies are not limited to those who are seasoned contributors to the Bugzilla ;) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148081] Copyable version info (for non-releases?) should include build date
https://bugs.documentfoundation.org/show_bug.cgi?id=148081 --- Comment #6 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #5) > That's more important for developers, but less for QA The bottom line of my argument is: it is not good to add something to the information, that is potentially confusing, since it is part of multi-dimensional state, and would be only helpful in some specific narrow ramifications, but otherwise would confuse unaware people, who would simply assume that "later means more complete" (or "has everything the older has, plus extra"), which is not generally correct. I would strongly suggest to not add that, but instead make it easier to navigate to the related commit web page, which provides both date and lots more information. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148081] Copyable version info (for non-releases?) should include build date
https://bugs.documentfoundation.org/show_bug.cgi?id=148081 --- Comment #5 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #4) > Why? Why shouldn't the email include the link that Bugzilla generates, when > it sends the email? Well, that's not how bugzilla email messgaes usually work, but if you can get it to happen, then ok. > Why? You have *link* in the build. At least with TDF builds and personal > builds. I meant that if you press the copy button you don't get the date. But it's true that you can click the link in the dialog and check. It's just an inconvenience (plus, the commit "dates" are listed in relative terms). If I can get the calc threading flag, I don't see why I can't have the head commit date. > since they may be from different branches But when that's the case, isn't that indicated in the version string? > and what's important is if they include something in their history or not - > which is only possible to see if you use git tools, available when you follow > the links (you can see the commit history there). That's more important for developers, but less for QA monkeys like us, who, if we have a non-release build at all, it's a daily. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148073] Consider renaming menu item "Search Commands"
https://bugs.documentfoundation.org/show_bug.cgi?id=148073 --- Comment #2 from Dave Barton --- -1 I see no advantage in making such a change. If the user does not already know that the facility will also execute MOST commands, they will be pleasantly surprised to discover that it does. Not only does the additional text bloat the menu, it adds unnecessary work for translators and documentation. My take WF or NAB. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 148073] Consider renaming menu item "Search Commands"
https://bugs.documentfoundation.org/show_bug.cgi?id=148073 --- Comment #2 from Dave Barton --- -1 I see no advantage in making such a change. If the user does not already know that the facility will also execute MOST commands, they will be pleasantly surprised to discover that it does. Not only does the additional text bloat the menu, it adds unnecessary work for translators and documentation. My take WF or NAB. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 148081] Copyable version info (for non-releases?) should include build date
https://bugs.documentfoundation.org/show_bug.cgi?id=148081 --- Comment #4 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #3) > But the linkifier doesn't work when you get email. Why? Why shouldn't the email include the link that Bugzilla generates, when it sends the email? > Nor does it work in your own LO installation. Why? You have *link* in the build. At least with TDF builds and personal builds. And anyway, "which one is earlier than the other and by how much" makes absolutely no sense, since they may be from different branches, and what's important is if they include something in their history or not - which is only possible to see if you use git tools, available when you follow the links (you can see the commit history there). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: icon-themes/colibre icon-themes/colibre_dark icon-themes/colibre_dark_svg icon-themes/colibre_svg
icon-themes/colibre/cmd/32/viewformasgrid.png |binary icon-themes/colibre/cmd/lc_dbqueryopen.png |binary icon-themes/colibre/cmd/sc_importfromfile.png |binary icon-themes/colibre_dark/cmd/32/ar/outlinebullet.png |binary icon-themes/colibre_dark/cmd/32/attributepagesize.png |binary icon-themes/colibre_dark/cmd/32/autooutline.png |binary icon-themes/colibre_dark/cmd/32/dataimport.png |binary icon-themes/colibre_dark/cmd/32/dataprovider.png |binary icon-themes/colibre_dark/cmd/32/dataproviderrefresh.png |binary icon-themes/colibre_dark/cmd/32/dbclearquery.png |binary icon-themes/colibre_dark/cmd/32/dbformdelete.png |binary icon-themes/colibre_dark/cmd/32/dbformedit.png |binary icon-themes/colibre_dark/cmd/32/dbformopen.png |binary icon-themes/colibre_dark/cmd/32/dbformrename.png |binary icon-themes/colibre_dark/cmd/32/dbnewform.png |binary icon-themes/colibre_dark/cmd/32/dbnewquery.png |binary icon-themes/colibre_dark/cmd/32/dbnewquerysql.png |binary icon-themes/colibre_dark/cmd/32/dbnewreport.png |binary icon-themes/colibre_dark/cmd/32/dbquerydelete.png |binary icon-themes/colibre_dark/cmd/32/dbqueryedit.png |binary icon-themes/colibre_dark/cmd/32/dbqueryopen.png |binary icon-themes/colibre_dark/cmd/32/dbqueryrename.png |binary icon-themes/colibre_dark/cmd/32/dbreportdelete.png |binary icon-themes/colibre_dark/cmd/32/dbreportedit.png |binary icon-themes/colibre_dark/cmd/32/dbreportopen.png |binary icon-themes/colibre_dark/cmd/32/dbreportrename.png |binary icon-themes/colibre_dark/cmd/32/dbviewforms.png |binary icon-themes/colibre_dark/cmd/32/dbviewqueries.png |binary icon-themes/colibre_dark/cmd/32/dbviewreports.png |binary icon-themes/colibre_dark/cmd/32/deletepage.png |binary icon-themes/colibre_dark/cmd/32/dsbformletter.png |binary icon-themes/colibre_dark/cmd/32/duplicatepage.png |binary icon-themes/colibre_dark/cmd/32/editframeset.png |binary icon-themes/colibre_dark/cmd/32/executereport.png |binary icon-themes/colibre_dark/cmd/32/expandpage.png |binary icon-themes/colibre_dark/cmd/32/exportdirecttoepub.png |binary icon-themes/colibre_dark/cmd/32/exportto.png |binary icon-themes/colibre_dark/cmd/32/formatgroup.png |binary icon-themes/colibre_dark/cmd/32/formatungroup.png |binary icon-themes/colibre_dark/cmd/32/formdesigntools.png |binary icon-themes/colibre_dark/cmd/32/formproperties.png |binary icon-themes/colibre_dark/cmd/32/framelinecolor.png |binary icon-themes/colibre_dark/cmd/32/freeline.png |binary icon-themes/colibre_dark/cmd/32/freeline_unfilled.png |binary icon-themes/colibre_dark/cmd/32/gotopage.png |binary icon-themes/colibre_dark/cmd/32/helplinesmove.png |binary icon-themes/colibre_dark/cmd/32/importfromfile.png |binary icon-themes/colibre_dark/cmd/32/insertframe.png |binary icon-themes/colibre_dark/cmd/32/insertmasterpage.png |binary icon-themes/colibre_dark/cmd/32/insertpage.png |binary icon-themes/colibre_dark/cmd/32/masterpage.png |binary icon-themes/colibre_dark/cmd/32/modifyframe.png |binary icon-themes/colibre_dark/cmd/32/outlinefont.png |binary icon-themes/colibre_dark/cmd/32/outlinemode.png |binary icon-themes/colibre_dark/cmd/32/pagemargin.png
[Libreoffice-bugs] [Bug 75471] Newly opened LibO document frames stay in background (i. e. LibO does not get focus)
https://bugs.documentfoundation.org/show_bug.cgi?id=75471 --- Comment #83 from Maxim Egorushkin --- The issue still persists in Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.4 on KDE Neon 5.24. No other application suffers from such a bug, only LibreOffice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148028] export creates huge pdf size, by about factor 100: 10 MB instead of 100 kB.
https://bugs.documentfoundation.org/show_bug.cgi?id=148028 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Component|Writer |Printing and PDF export -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103378 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||148028 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148028 [Bug 148028] export creates huge pdf size, by about factor 100: 10 MB instead of 100 kB. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148028] export creates huge pdf size, by about factor 100: 10 MB instead of 100 kB.
https://bugs.documentfoundation.org/show_bug.cgi?id=148028 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Keywords||filter:pdf Blocks||103378 CC||79045_79...@mail.ru Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103378 [Bug 103378] [META] PDF export bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148031] Navigating from footnote to footnote
https://bugs.documentfoundation.org/show_bug.cgi?id=148031 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Roman Kuznetsov <79045_79...@mail.ru> --- In 7.3 version we got a feature to navigate by footnotes in Navigator. Just update your LibreOffice to current 7.3.1 version Close as duplicate of bug 144788 *** This bug has been marked as a duplicate of bug 144788 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148081] Copyable version info (for non-releases?) should include build date
https://bugs.documentfoundation.org/show_bug.cgi?id=148081 --- Comment #3 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #1) > I disagree that build date is a useful information. While dailies are > *usually* built at the date that reflects the current head, it is not so > e.g. for bibisect builds, and generally is not required to be synchronized. Ok, then, make it the date of the built branch then. The point is that when I look at my build info, and some build info pasted into a bug page here, I want to know which one is earlier than the other and by how much; and I would also like to know how old each of them are individually. > I suggest instead to add a linkifier to Bugzilla, so that when a build hash > appears, it is represented as a link, and would simplify checking the date, > along with other relevant info. It would also simplify providing the links > when one bibisects, since today one needs to copy-paste the source hash, > *and* also the link, to allow others to navigate to the commit easily. But the linkifier doesn't work when you get email. Nor does it work in your own LO installation. So, while it may be a good idea, I still want the build date / built branch HEAD date. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148068] Record Macro does not record inserting sheets
https://bugs.documentfoundation.org/show_bug.cgi?id=148068 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- (In reply to Timur from comment #0) > Note3: Record Macro works with dispatch and doesn't really create proper > code, so it should be rewritten completely. Workaround could be using MRI > extension. So may be just disable it at all? =) Btw, today it has an experimental status -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85811] [META] Main menu bar bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=85811 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||148073 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148073 [Bug 148073] Consider renaming menu item "Search Commands" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 148073] Consider renaming menu item "Search Commands"
https://bugs.documentfoundation.org/show_bug.cgi?id=148073 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||85811 CC||79045_79...@mail.ru Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=85811 [Bug 85811] [META] Main menu bar bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 148073] Consider renaming menu item "Search Commands"
https://bugs.documentfoundation.org/show_bug.cgi?id=148073 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||85811 CC||79045_79...@mail.ru Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=85811 [Bug 85811] [META] Main menu bar bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148073] Consider renaming menu item "Search Commands"
https://bugs.documentfoundation.org/show_bug.cgi?id=148073 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- I personally disagree, but added UX team -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 148073] Consider renaming menu item "Search Commands"
https://bugs.documentfoundation.org/show_bug.cgi?id=148073 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- I personally disagree, but added UX team -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 148075] LibreOffice crashes when opening certain large files (which worked with other versions)
https://bugs.documentfoundation.org/show_bug.cgi?id=148075 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||79045_79...@mail.ru --- Comment #2 from Roman Kuznetsov <79045_79...@mail.ru> --- Please attach your problem file here -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109324] [META] Calculate bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109324 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||148076 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148076 [Bug 148076] calculations in Calc stop working -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148076] calculations in Calc stop working
https://bugs.documentfoundation.org/show_bug.cgi?id=148076 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||109324 Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||79045_79...@mail.ru --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- Please write here info from LibreOffice's Help->About dialog and attach your file Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109324 [Bug 109324] [META] Calculate bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103378 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||148079 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148079 [Bug 148079] Headers and Footers are being duplicated on conversion from .docx to .pdf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103266] [META] Command line bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103266 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Depends on||148079 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148079 [Bug 148079] Headers and Footers are being duplicated on conversion from .docx to .pdf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148079] Headers and Footers are being duplicated on conversion from .docx to .pdf
https://bugs.documentfoundation.org/show_bug.cgi?id=148079 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||103266, 103378 CC||79045_79...@mail.ru Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103266 [Bug 103266] [META] Command line bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=103378 [Bug 103378] [META] PDF export bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
