[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 160898, which changed state. Bug 160898 Summary: Crash selecting all (Ctrl+A) in a temporarily visible paragraph under a table inside a table https://bugs.documentfoundation.org/show_bug.cgi?id=160898 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107200] [META] Writer table and cell selection issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107200 Bug 107200 depends on bug 160898, which changed state. Bug 160898 Summary: Crash selecting all (Ctrl+A) in a temporarily visible paragraph under a table inside a table https://bugs.documentfoundation.org/show_bug.cgi?id=160898 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141578] Libreoffice unusable with different scale factors used for different screens in multimonitor setup (on kf5/qt5/qt6 vcl + wayland)
https://bugs.documentfoundation.org/show_bug.cgi?id=141578 --- Comment #61 from Michael Weghorn --- (In reply to typingcat from comment #58) > In my case, I have two monitors: 1080p (secondary) and 4K (main), and LO > looks normal on the 1080p, and looks tiny on the 4K. So, "moving the window > to that screen" is not really a good workaround, because I have to work on > the small secondary monitor. Unless... there is a way to choose on which of > the two monitors LO can look normal? I just tested with QT_SCALE_FACTOR as described in my comment 49, but that by itself doesn't work. What works in my tests is forcing to run on XWayland in addition, e.g. setting environment variables QT_QPA_PLATFORM=xcb QT_SCALE_FACTOR=1.5 when starting LO. (You'll need to adjust the scale factor depending on your screen settings.) (In reply to htky from comment #60) > (Sorry for double comment, using Bugzilla for the first time :) ) Don't worry. :) > I have found an interesting case regarding this issue depending on when > external monitor is plugged in. > When the monitor is plugged in while session is already running, LO will > scale normally on the primary monitor and be zoomed in on the external > display. Now when the session is started with external monitor plugged in > already, LO will scale normally on the external monitor and be zoomed out on > primary display. > You can see this in attachment 193920 [details] It doesn't behave like that on my Debian testing (Plasma 5 still), maybe it's different with Plasma 6 or some other aspect plays a role in addition. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160900] New: Inconsistency in Retaining Automatic Line Break Setting in LibreOffice Calc (xlsx Format)
https://bugs.documentfoundation.org/show_bug.cgi?id=160900 Bug ID: 160900 Summary: Inconsistency in Retaining Automatic Line Break Setting in LibreOffice Calc (xlsx Format) Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jmag...@gmail.com Created attachment 193934 --> https://bugs.documentfoundation.org/attachment.cgi?id=193934&action=edit sample_of_wrap_problem In cells containing text created by formulas in an xlsx format file, the formatting for automatic line breaks is not retained. 1,Open LibreOffice Calc. 2,Open a sample document. 3,Open the format dialog for cell A5 and enable automatic line break. 4,Save the file (in xlsx format). 5,Close the file. 6,Reopen the file. Expected behavior: The automatic line break setting for the cell should be retained. Actual behavior: The automatic line break setting for the cell is not retained. This behavior occurred in LibreOffice 24.0.0 and 24.2.2. However, it did not occur in LibreOffice 7.6.4. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160873] Usability: "OLE Object" probably not familiar language (Menu: Insert/OLE Object)
https://bugs.documentfoundation.org/show_bug.cgi?id=160873 --- Comment #5 from Heiko Tietze --- (In reply to jan d from comment #0) > Possible Solutions: Dissolve the OLE-Menu point and pull the items in the > main insert menu. That makes the Insert menu too large; keep in mind that we have to support small screens. It might work if we use just "Object" and hide all less frequently used items there, including what is now under "OLE Objects". But that brings us to the question which ones are less frequently used. And we have to consider the sub item "OLE Object...". (In reply to Stéphane Guillou (stragu) from comment #1) > "Linked or Embedded Objects" +1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160899] Candy: Enabling Master Elements results in shapes with default blue background
https://bugs.documentfoundation.org/show_bug.cgi?id=160899 --- Comment #3 from Gabor Kelemen (allotropia) --- Created attachment 193933 --> https://bugs.documentfoundation.org/attachment.cgi?id=193933&action=edit The issue is visible after the master elements are enabled -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160899] Candy: Enabling Master Elements results in shapes with default blue background
https://bugs.documentfoundation.org/show_bug.cgi?id=160899 --- Comment #2 from Gabor Kelemen (allotropia) --- Created attachment 193932 --> https://bugs.documentfoundation.org/attachment.cgi?id=193932&action=edit The master elements are disabled initially -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160657] Improve how Writer Navigator Headings are displayed when alphabetically sorted
https://bugs.documentfoundation.org/show_bug.cgi?id=160657 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from Heiko Tietze --- +1 for flat. The current implementation is broken anyway since it places H2 from the second chapter wrongly under the first (eg. the "formatted dummy text", extension #132). I think the opposite to "Sort Alphabetically" is not as clear as Show/Hide, or the like, to use just one checkbox. We better put the options (o) Sequentially and ( ) Alphabetically in a "Sort" menu. It also allows to add later other criteria such as ( ) Length or ( ) Complexity (kinda ironic, IIRC I was against the alphabetical sorting). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160899] Candy: Enabling Master Elements results in shapes with default blue background
https://bugs.documentfoundation.org/show_bug.cgi?id=160899 --- Comment #1 from Gabor Kelemen (allotropia) --- Created attachment 193931 --> https://bugs.documentfoundation.org/attachment.cgi?id=193931&action=edit Filling the header - footer info in the example file -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159375] Opening Tools > Options dialog takes too long
https://bugs.documentfoundation.org/show_bug.cgi?id=159375 --- Comment #16 from Heiko Tietze --- (In reply to kolAflash from comment #15) > When using the search feature I think it doesn't matter at which point > you've to wait (when loading the options or when starting the search). As long it wont feel broken. My first idea is to run the initialization in the background aka threaded. If that wont help and if you continue with the no-init-but-wait-on-first-search idea, please indicate the loading process for example with a throbber in the input field. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103314] [META] Templates bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103314 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||160899 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160899 [Bug 160899] Candy: Enabling Master Elements results in shapes with default blue background -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160899] New: Candy: Enabling Master Elements results in shapes with default blue background
https://bugs.documentfoundation.org/show_bug.cgi?id=160899 Bug ID: 160899 Summary: Candy: Enabling Master Elements results in shapes with default blue background Product: LibreOffice Version: 7.2.0.4 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com Blocks: 103314 Created attachment 193930 --> https://bugs.documentfoundation.org/attachment.cgi?id=193930&action=edit Example file from Impress When the Candy template is used and the master elements are enabled, the corresponding textboxes have a default blue background instead of a transparent one. 1. Open attached file, or a new document from the Candy template 2. Go to the second slide on the left Slide pane (this works on the first) 2. Slide - Master Elements, check the boxes -> At the bottom of the slide text boxes with default blue background appear Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5740d3fa83e9725a2771e5f00ba4aaf9965f0be2 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: hu-HU (hu_HU.UTF-8); UI: en-US Calc: threaded already looks like this in 7.2 when the Candy template was added. Other templates don't seem to have this behavior, such as the Portfolio template which also has disabled Master elements on its first master slide. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103314 [Bug 103314] [META] Templates bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160697] Writer opens blank window temporarily at launch
https://bugs.documentfoundation.org/show_bug.cgi?id=160697 Michael Weghorn changed: What|Removed |Added Ever confirmed|0 |1 CC||m.wegh...@posteo.de Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Michael Weghorn --- I don't notice that but maybe it's just happening too fast. Is this on X11 or Wayland? If it's on Wayland: Does this also happen when you start LibreOffice with environment variable QT_QPA_PLATFORM=xcb set to force LibreOffice to use Qt's xcb/X11 integration instead? Can you please copy the version info from "Help" -> "About LibreOffice" here? If it's Wayland-only, this may be due to the hide/show cycle introduced in order to be able to use app-specific window icons, see commit commit cea0371ac77145ad1f3db7e558c279aeed6f4d00 Author: Michael Weghorn Date: Mon Feb 12 14:09:45 2024 +0100 tdf#125934 qt: Support module-specific window icons on Wayland I've mentioned that problem in [1] earlier: > It obviously has the side-effect that the window disappears for a short > amount of time and it still feels a bit like a workaround to me. The way forward for a proper solution would IMHO require new API in Qt as mentioned in that Qt issue. [1] https://bugreports.qt.io/browse/QTBUG-77182?focusedId=774291&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-774291 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 118765] [META] MathML bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=118765 Bug 118765 depends on bug 75930, which changed state. Bug 75930 Summary: IMPORT MathML: some characters are missing https://bugs.documentfoundation.org/show_bug.cgi?id=75930 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 75930] IMPORT MathML: some characters are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=75930 Mike Kaganski changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #15 from Mike Kaganski --- Fixed in 6.1 by commit bf46b46a1d734348096936284fb8a76e977936d0 (Moving XSAXDocumentBuilder2 to use XFastDocumentHandler:, 2018-03-14) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160800] Libreoffice App in F-Droid outdated
https://bugs.documentfoundation.org/show_bug.cgi?id=160800 Michael Weghorn changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #2 from Michael Weghorn --- (In reply to Michael Weghorn from comment #1) > Versions are published on F-Droid as well, but there's currently an > infra/connectivity issue causing the F-Droid build to fail, see > https://gitlab.com/fdroid/fdroiddata/-/merge_requests/14775#note_1843871640 . > This will hopefully be fixed when the tarballs have been migrated to a new > server. Server migration is done and the latest F-Droid build succeeded: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/14775#note_1889440186 New versions should show up in F-Droid automatically, but it might take a few days until they're available. Closing as WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 144687] ISLEAPYEAR gives FALSE for years displaying Feb 29th
https://bugs.documentfoundation.org/show_bug.cgi?id=144687 --- Comment #4 from Mike Kaganski --- Still repro using Version: 24.2.3.1 (X86_64) / LibreOffice Community Build ID: fc604d5980a783e74808a001f1918a603d920494 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: en-GB (ru_RU); UI: en-GB Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108226] [META] PPTX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=108226 Bug 108226 depends on bug 148616, which changed state. Bug 148616 Summary: FILEOPEN PPTX A certain POTX template is slow to open https://bugs.documentfoundation.org/show_bug.cgi?id=148616 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 87409] Inserting manual page break does not work with bullets and numbering with the cursor at the very beginning of the line
https://bugs.documentfoundation.org/show_bug.cgi?id=87409 --- Comment #12 from J_A --- Hello, This bug is still present in the latest version and master build Tested using: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded and Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bc7501d30ab9a3a5edec66d2f0022177f85d6127 CPU threads: 16; OS: Windows 10 (10.0 build 19045); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160898 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160898 [Bug 160898] Crash selecting all (Ctrl+A) in a temporarily visible paragraph under a table inside a table -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107200] [META] Writer table and cell selection issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107200 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160898 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160898 [Bug 160898] Crash selecting all (Ctrl+A) in a temporarily visible paragraph under a table inside a table -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160898] Crash selecting all (Ctrl+A) in a temporarily visible paragraph under a table inside a table
https://bugs.documentfoundation.org/show_bug.cgi?id=160898 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||137202 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=137202 [Bug 137202] SEGFAULT if window closed shortly after reload -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 137202, which changed state. Bug 137202 Summary: SEGFAULT if window closed shortly after reload https://bugs.documentfoundation.org/show_bug.cgi?id=137202 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Bug 134161] CPU at 100% after opening a particular spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=134161 --- Comment #13 from Stéphane Guillou (stragu) --- *** Bug 137202 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 137202] SEGFAULT if window closed shortly after reload
https://bugs.documentfoundation.org/show_bug.cgi?id=137202 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE CC||stephane.guillou@libreoffic ||e.org Version|7.1.0.0.alpha0+ |7.0.0.3 release Blocks||133092 Crash report or||["SfxViewFrame::UpdateDocum crash signature||ent_Impl"] --- Comment #6 from Stéphane Guillou (stragu) --- Reproduced with 7.0.0.3 with signature "SfxViewFrame::UpdateDocument_Impl" (as in comment 4): https://crashreport.libreoffice.org/stats/crash_details/3725a3b2-936a-4858-b182-9bce941d1792 Not reproduced in 7.1.0.3 nor in recent daily build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ce454f382d0d005dd3de021c7820be3ffa0bb582 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Bibisected the fix with linux-64-7.1 repo to first good build [4477bc3a11a32feb31378f49d0eb7b9db0f9c5d6] which is: commit a5b3211f072d982e1ee136e864f153836c76a5ca author Xisco Fauli Thu Nov 05 20:35:09 2020 +0100 committer Xisco Fauli Fri Nov 06 09:53:04 2020 +0100 tdf#134161: Revert "tdf#132137 Rename Default Style in Calc." Reviewed-on: https://gerrit.libreoffice.org/c/core/+/105381 Indeed, it started with 95f0a01a943961db415b6d036b6b4e1e54292716 ([6daa1cb2d5626be1ef9341eb15170a2bea8f02b5] in linux-64-7.0 bibisect repo). Marking as duplicate. (But wondering if there would be other sluggish sample files where this would be reproducible?) *** This bug has been marked as a duplicate of bug 134161 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160898] New: Crash selecting all (Ctrl+A) in a temporarily visible paragraph under a table inside a table
https://bugs.documentfoundation.org/show_bug.cgi?id=160898 Bug ID: 160898 Summary: Crash selecting all (Ctrl+A) in a temporarily visible paragraph under a table inside a table Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: All Status: UNCONFIRMED Keywords: bisected, regression Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com Created attachment 193929 --> https://bugs.documentfoundation.org/attachment.cgi?id=193929&action=edit Table in table 1. Create a table in a text document 2. Inside that table's cell, create another table (see that there is no paragraphs shown in the outer cell, beside the paragraphs inside the inner table) 3. When the cursor is inside that inner table, press Arrow Down key, and eventually arrive to a place outside the inner table, but inside the outer cell (the hidden paragraph, shown temporarily when the cursor travels there) 4. Press Edit->Select All (Ctrl+A) => crash since version 7.6.0. Regression after commit d81379db730a163c5ff75d4f3a3cddbd7b5eddda (tdf#154877 sw: generalise ExtendedSelectAll(), 2023-05-09) The attached file contains a simple reproducer. Just press Arrow Down key twice, to arrive into the described temporarily shown paragraph, then Ctrl+A. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160657] Improve how Writer Navigator Headings are displayed when alphabetically sorted
https://bugs.documentfoundation.org/show_bug.cgi?id=160657 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160647] LO Writer 7.6.5.2 (and most anterior versions) cannot be used on wide screen monitors due to extreme performance issues
https://bugs.documentfoundation.org/show_bug.cgi?id=160647 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160509] Modal Window on FILEOPEN for Read-Only (e.g. out of an eMail) SECOND file is hidden behind
https://bugs.documentfoundation.org/show_bug.cgi?id=160509 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160626] Selecting a style in the toolbar list sends it at the bottom of the list
https://bugs.documentfoundation.org/show_bug.cgi?id=160626 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160710] Clarify "Save Document as URL"
https://bugs.documentfoundation.org/show_bug.cgi?id=160710 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160705] FILESAVE PDF/UA Table caption does not wrap the table as seen in the PAC tool
https://bugs.documentfoundation.org/show_bug.cgi?id=160705 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160647] LO Writer 7.6.5.2 (and most anterior versions) cannot be used on wide screen monitors due to extreme performance issues
https://bugs.documentfoundation.org/show_bug.cgi?id=160647 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160647] LO Writer 7.6.5.2 (and most anterior versions) cannot be used on wide screen monitors due to extreme performance issues
https://bugs.documentfoundation.org/show_bug.cgi?id=160647 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157319] LibreOffice after version 7.5.0.3 Refuses To Install On Window 11 Pro.
https://bugs.documentfoundation.org/show_bug.cgi?id=157319 --- Comment #3 from QA Administrators --- Dear j...@joeschafer.com, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157319] LibreOffice after version 7.5.0.3 Refuses To Install On Window 11 Pro.
https://bugs.documentfoundation.org/show_bug.cgi?id=157319 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156692] Crashing after update, no auto-save
https://bugs.documentfoundation.org/show_bug.cgi?id=156692 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 149715] MAILMERGE Data Source not Updated For Email Mail Merge (Filtering and Modifying Data Source Has No Effect)
https://bugs.documentfoundation.org/show_bug.cgi?id=149715 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156692] Crashing after update, no auto-save
https://bugs.documentfoundation.org/show_bug.cgi?id=156692 --- Comment #8 from QA Administrators --- Dear Kevin Neff, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102998] [META] Mail merge bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102998 Bug 102998 depends on bug 149715, which changed state. Bug 149715 Summary: MAILMERGE Data Source not Updated For Email Mail Merge (Filtering and Modifying Data Source Has No Effect) https://bugs.documentfoundation.org/show_bug.cgi?id=149715 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 124620] SVG Export: Only one bullet point is exported
https://bugs.documentfoundation.org/show_bug.cgi?id=124620 --- Comment #6 from QA Administrators --- Dear Samuel Mehrbrodt (allotropia), 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.
[Bug 149715] MAILMERGE Data Source not Updated For Email Mail Merge (Filtering and Modifying Data Source Has No Effect)
https://bugs.documentfoundation.org/show_bug.cgi?id=149715 --- Comment #5 from QA Administrators --- Dear mworks, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158059] saving a spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=158059 --- Comment #2 from QA Administrators --- Dear Greg Smith, 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.
[Bug 94487] Pivot Table: Fields list doesn't update
https://bugs.documentfoundation.org/show_bug.cgi?id=94487 --- Comment #12 from QA Administrators --- Dear Rafael Strozi, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 84687] UI: Property mapping - deletion is neither registered nor effective
https://bugs.documentfoundation.org/show_bug.cgi?id=84687 --- Comment #13 from QA Administrators --- Dear pierre-yves samyn, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 81999] FILEOPEN: XLSX: self-contained filtered pivot table. Lost pivot table.
https://bugs.documentfoundation.org/show_bug.cgi?id=81999 --- Comment #9 from QA Administrators --- Dear raal, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 75930] IMPORT MathML: some characters are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=75930 --- Comment #14 from QA Administrators --- Dear Mike Kaganski, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 47688] Handling of "Record changes", "Show changes" and save status inconsistent
https://bugs.documentfoundation.org/show_bug.cgi?id=47688 --- Comment #7 from QA Administrators --- Dear Matthew Francis, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148570] FILEOPEN RTF Paragraph before section break has its hidden linebreaks after the break
https://bugs.documentfoundation.org/show_bug.cgi?id=148570 --- Comment #3 from QA Administrators --- Dear Gabor Kelemen (allotropia), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145131] Wrong operations MINUTE() function
https://bugs.documentfoundation.org/show_bug.cgi?id=145131 --- Comment #7 from QA Administrators --- Dear Jerzy Moruś, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 144687] ISLEAPYEAR gives FALSE for years displaying Feb 29th
https://bugs.documentfoundation.org/show_bug.cgi?id=144687 --- Comment #3 from QA Administrators --- Dear Mike Kaganski, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 132409] Relative isn't unchecked in Image Properties dialog after reset button is pressed
https://bugs.documentfoundation.org/show_bug.cgi?id=132409 --- Comment #4 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 143406] FILESAVE DOCX Grouped shapes Contour wrap is not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=143406 --- Comment #8 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 131760] Commands related to styles miscategorized in customization dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=131760 --- Comment #23 from QA Administrators --- Dear Kenneth Hanson, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 131388] File save fails when network document is opened on another machine
https://bugs.documentfoundation.org/show_bug.cgi?id=131388 --- Comment #5 from QA Administrators --- Dear Samuel Mehrbrodt (allotropia), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 128426] Swapping two commands' keyboard shortcuts is not easy
https://bugs.documentfoundation.org/show_bug.cgi?id=128426 --- Comment #6 from QA Administrators --- Dear Ming Hua, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113734] FILEOPEN DOC: Table border settings read incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=113734 --- Comment #8 from QA Administrators --- Dear Gabor Kelemen (allotropia), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113680] FILEOPEN XLS Named Ranges in form controls are dropped on open
https://bugs.documentfoundation.org/show_bug.cgi?id=113680 --- Comment #7 from QA Administrators --- Dear Michael 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107986] EDITING: The original size will decrease after using compression
https://bugs.documentfoundation.org/show_bug.cgi?id=107986 --- Comment #11 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159385] Crash at undo of RTF Paste
https://bugs.documentfoundation.org/show_bug.cgi?id=159385 --- Comment #7 from Esteban --- If I follow all the steps with the original Attachment 179694 I get a crash. However, if I create a new writer document, copy all the contents of the original attachment into the new one and then repeat the steps I do not get a crash. Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|151086 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151086 [Bug 151086] Writer crashes when insert SVG image with default anchor set to As Character (STR: comment 4 + comment 10) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151086] Writer crashes when insert SVG image with default anchor set to As Character (STR: comment 4 + comment 10)
https://bugs.documentfoundation.org/show_bug.cgi?id=151086 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE CC||stephane.guillou@libreoffic ||e.org Blocks|133092 | Crash report or||["IsAnchoredObjShown(SwText crash signature||Frame const ||&,SwFormatAnchor const ||&)","GetFrameOfModify(SwRoo ||tFrame const ||*,sw::BroadcastingModify ||const ||&,SwFrameType,SwPosition ||const ||*,std::pair ||const *)","libswlo.so"] Status|NEW |RESOLVED --- Comment #14 from Stéphane Guillou (stragu) --- The two crash signatures reported by csongor are: - "IsAnchoredObjShown(SwTextFrame const &,SwFormatAnchor const &)" - "GetFrameOfModify(SwRootFrame const *,sw::BroadcastingModify const &,SwFrameType,SwPosition const *,std::pair const *)" I reproduced in 24.2.2 with uninformative signature "libswlo.so": https://crashreport.libreoffice.org/stats/crash_details/43fb0764-039a-408d-8090-78f0dc8ec3dc The issue is the same as described in bug 159379, which is already fixed in master and the upcoming 24.2.4. I verified with comment 4 steps and: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2f5ab5b8e7bd7dd06e00153abb77a69e5d192dd2 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Marking as duplicate, thanks everyone! *** This bug has been marked as a duplicate of bug 159379 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 119352] [META] Language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=119352 Bug 119352 depends on bug 151830, which changed state. Bug 151830 Summary: Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI) https://bugs.documentfoundation.org/show_bug.cgi?id=151830 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI)
https://bugs.documentfoundation.org/show_bug.cgi?id=151830 Mike Kaganski changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 154602] Scrolling using keyboard very slow (GTK3) with 4K monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=154602 --- Comment #19 from Jeff Fortin Tam --- Created attachment 193928 --> https://bugs.documentfoundation.org/attachment.cgi?id=193928&action=edit Sysprof 46 capture screenshot - CPU usage -- You are receiving this mail because: You are the assignee for the bug.
[Bug 154602] Scrolling using keyboard very slow (GTK3) with 4K monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=154602 --- Comment #18 from Jeff Fortin Tam --- Created attachment 193927 --> https://bugs.documentfoundation.org/attachment.cgi?id=193927&action=edit Sysprof 46 capture screenshot - graphics marks -- You are receiving this mail because: You are the assignee for the bug.
[Bug 154602] Scrolling using keyboard very slow (GTK3) with 4K monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=154602 --- Comment #17 from Jeff Fortin Tam --- Created attachment 193926 --> https://bugs.documentfoundation.org/attachment.cgi?id=193926&action=edit Sysprof 46 capture screenshot - flamegraph -- You are receiving this mail because: You are the assignee for the bug.
[Bug 154602] Scrolling using keyboard very slow (GTK3) with 4K monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=154602 --- Comment #16 from Jeff Fortin Tam --- Created attachment 193925 --> https://bugs.documentfoundation.org/attachment.cgi?id=193925&action=edit Sysprof 46 performance profiling capture Let me put some objective measurements into the mix here with a profiling measurement using Sysprof. I reproduced this by using the provided CSV sample above and pressing-and-holding the down arrow button on the keyboard of a 4K HiDPI (@ 2x) Intel Kabylike laptop running Wayland GNOME on Fedora 39, with the Flatpak flathub version of LibreOffice: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 8; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Flatpak Calc: threaded I will attach screenshots of the essentials of that sysprof capture. My naïve observations: * The overwhelming majority of time/efforts are spent in "PaintHelper" and "SdrPaintView" functions and the like, which ultimately spend a ton of time doing cairo_paint and cairo_fill everywhere. * It seems to be single-threaded, as per the CPU usage graphs. My gut feeling: it's probably spamming the backend as fast and often as keyboard input events are coming, without any throttling/smoothing. I don't think it makes sense for the app to be trying to respond to every event, 600 times per second (the 25-seconds sysprof recording shows 15 thousand function calls...). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151830] Save as text with coding utf-8 destroys all non-ascii characters, replacing with question mark (Norwegian Norsk bokmål UI)
https://bugs.documentfoundation.org/show_bug.cgi?id=151830 Adolfo Jayme Barrientos changed: What|Removed |Added Whiteboard||target:24.8.0 target:24.2.4 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||136971 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136971 [Bug 136971] Crash in: swlo.dll while using Basic macro to delete a character while cursor is in a textbox -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103494] [META] Textbox bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103494 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||136971 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136971 [Bug 136971] Crash in: swlo.dll while using Basic macro to delete a character while cursor is in a textbox -- You are receiving this mail because: You are the assignee for the bug.
[Bug 136971] Crash in: swlo.dll while using Basic macro to delete a character while cursor is in a textbox
https://bugs.documentfoundation.org/show_bug.cgi?id=136971 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard||target:24.8.0 target:24.2.1 ||target:7.6.5 Status|NEW |RESOLVED CC||matt...@gmail.com, ||stephane.guillou@libreoffic ||e.org Blocks||103494, 133092 Resolution|--- |FIXED Version|4.1 all versions|Inherited From OOo See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||2810 --- Comment #10 from Stéphane Guillou (stragu) --- Reproduced in OOo 3.3 and LO 7.5.9. Not reproduced anymore in: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Bibisect fix with linux-64-24.2 to first good build [b497d3d200aad6a5946b4d5fcc50742b71521fc3] which points to a72dad4e4c0d41b61e453919401fcefc8e5e9b43 which is a cherrypick of: commit 19062c98da5b2e9edc7a99068fa06a83c7578826 author Matt K Thu Jan 11 20:37:01 2024 -0600 committerMike Kaganski Sat Jan 13 18:21:02 2024 +0100 tdf#132810 Prevent crashes with gallery objects Reviewed-on: https://gerrit.libreoffice.org/c/core/+/161950 Thanks Matt! Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103494 [Bug 103494] [META] Textbox bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 136971, which changed state. Bug 136971 Summary: Crash in: swlo.dll while using Basic macro to delete a character while cursor is in a textbox https://bugs.documentfoundation.org/show_bug.cgi?id=136971 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103494] [META] Textbox bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103494 Bug 103494 depends on bug 136971, which changed state. Bug 136971 Summary: Crash in: swlo.dll while using Basic macro to delete a character while cursor is in a textbox https://bugs.documentfoundation.org/show_bug.cgi?id=136971 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107659] [META] Macro bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107659 Bug 107659 depends on bug 136971, which changed state. Bug 136971 Summary: Crash in: swlo.dll while using Basic macro to delete a character while cursor is in a textbox https://bugs.documentfoundation.org/show_bug.cgi?id=136971 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103437] [META] Animation deck/tab of the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=103437 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||142816 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142816 [Bug 142816] Object Animation and Slide Transition's Automatic Preview settings are not saved directly in profile -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103444] [META] Slide transition deck/tab of the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=103444 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||142816 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142816 [Bug 142816] Object Animation and Slide Transition's Automatic Preview settings are not saved directly in profile -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107636] [META] User profile (user data/settings) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107636 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||142816 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142816 [Bug 142816] Object Animation and Slide Transition's Automatic Preview settings are not saved directly in profile -- You are receiving this mail because: You are the assignee for the bug.
[Bug 109362] [META] Custom/object animation bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109362 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|142816 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142816 [Bug 142816] Object Animation and Slide Transition's Automatic Preview settings are not saved directly in profile -- You are receiving this mail because: You are the assignee for the bug.
[Bug 142816] Object Animation and Slide Transition's Automatic Preview settings are not saved directly in profile
https://bugs.documentfoundation.org/show_bug.cgi?id=142816 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks|109362 |103437, 103444, 107636 Summary|Automatic effect preview|Object Animation and Slide |does not persist after |Transition's Automatic |crash |Preview settings are not ||saved directly in profile CC||stephane.guillou@libreoffic ||e.org --- Comment #6 from Stéphane Guillou (stragu) --- Confirmed that killing LO after deactivating the animation preview results in setting not saved. Same with the automatic preview of Slide Transitions. For comparison, I tried with Display Grid turned on, and the settings is indeed saved even when killing LO. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ce454f382d0d005dd3de021c7820be3ffa0bb582 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103437 [Bug 103437] [META] Animation deck/tab of the sidebar https://bugs.documentfoundation.org/show_bug.cgi?id=103444 [Bug 103444] [META] Slide transition deck/tab of the sidebar https://bugs.documentfoundation.org/show_bug.cgi?id=107636 [Bug 107636] [META] User profile (user data/settings) bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=109362 [Bug 109362] [META] Custom/object animation bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 124300] Crash after toggling Hidden in character style a couple of times or doing Update all
https://bugs.documentfoundation.org/show_bug.cgi?id=124300 --- Comment #27 from Stéphane Guillou (stragu) --- (In reply to Stéphane Guillou (stragu) from comment #25) > my suggestion is closing as "works for me" and > open now reports as needed. Done for layout loop in bug 160897. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 149131] A particular master document with comments is sluggish
https://bugs.documentfoundation.org/show_bug.cgi?id=149131 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0897 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 124300] Crash after toggling Hidden in character style a couple of times or doing Update all
https://bugs.documentfoundation.org/show_bug.cgi?id=124300 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0897 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103164] [META] Footnote and Endnote bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103164 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160897 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160897 [Bug 160897] FILEOPEN: layout loop, freeze in master document linked to subdocument -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160897] New: FILEOPEN: layout loop, freeze in master document linked to subdocument
https://bugs.documentfoundation.org/show_bug.cgi?id=160897 Bug ID: 160897 Summary: FILEOPEN: layout loop, freeze in master document linked to subdocument Product: LibreOffice Version: 7.6.3.1 rc Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Keywords: bibisected, bisected, perf, regression Severity: major Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org CC: michael.st...@allotropia.de Blocks: 101280, 103164 Steps: 1. Download attachment 103519 and attachment 103520 2. Open the .odm Result: layout loop, console showing warnings including: warn:sw.layout:251020:251020:sw/source/core/layout/wsfrm.cxx:3084: footnote frame on different page than ref frame? warn:legacy.osl:277213:277213:sw/source/core/layout/layact.cxx:589: LoopControl_1 in SwLayAction::InternalAction warn:legacy.osl:277437:277437:sw/source/core/layout/layact.cxx:770: LoopControl_3 in Interrupt formatting in SwLayAction::InternalAction warn:sw.layout:277213:277213:sw/source/core/layout/layouter.cxx:190: Looping Louie: Stage 1! Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f4ef5435df5560e6b6b061ce4053c71e2819bf51 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: x11 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Also on Windows. Bibisected with linux-64-7.6 repo to first bad build [7c9b5f75e3646ec0a55465033fc7c64d13302c28] which points to 5b3fcbf23773ea8d039185dec2b9704981833473 which is a cherrypick of: commit c303981cfd95ce1c3881366023d5495ae2edce97 author Michael Stahl Wed Aug 23 15:50:59 2023 +0200 committer Michael Stahl Thu Aug 24 12:43:25 2023 +0200 tdf#156724 sw: layout: fix tables not splitting due to footnotes differently Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155988 Michael, can you please have a look? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101280 [Bug 101280] [META] Layout loops https://bugs.documentfoundation.org/show_bug.cgi?id=103164 [Bug 103164] [META] Footnote and Endnote bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101280] [META] Layout loops
https://bugs.documentfoundation.org/show_bug.cgi?id=101280 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160897 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160897 [Bug 160897] FILEOPEN: layout loop, freeze in master document linked to subdocument -- You are receiving this mail because: You are the assignee for the bug.
[Bug 124300] Crash after toggling Hidden in character style a couple of times or doing Update all
https://bugs.documentfoundation.org/show_bug.cgi?id=124300 --- Comment #26 from Stéphane Guillou (stragu) --- (In reply to Stéphane Guillou (stragu) from comment #25) > - comment 24 (dbg build crash on update all): >- can't test in recent trunk build because of the layout loop This eventually settled to a manageable rate, no crash after Update All. However, still looping with: warn:legacy.osl:278015:278015:sw/source/core/layout/layact.cxx:589: LoopControl_1 in SwLayAction::InternalAction warn:sw.layout:278015:278015:sw/source/core/layout/wsfrm.cxx:3084: footnote frame on different page than ref frame? ...ad nauseam. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101280] [META] Layout loops
https://bugs.documentfoundation.org/show_bug.cgi?id=101280 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||124300 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=124300 [Bug 124300] Crash after toggling Hidden in character style a couple of times or doing Update all -- You are receiving this mail because: You are the assignee for the bug.
[Bug 124300] Crash after toggling Hidden in character style a couple of times or doing Update all
https://bugs.documentfoundation.org/show_bug.cgi?id=124300 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||perf Crash report or||["SwFrame::GetPhyPageNum()" crash signature||,"SwFrame::FindFootnoteBoss ||Frame(bool)"] Resolution|--- |WORKSFORME Status|NEW |RESOLVED Blocks||101280 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||2081 CC||stephane.guillou@libreoffic ||e.org --- Comment #25 from Stéphane Guillou (stragu) --- Testing all with gen VCL plugin: - comment 0 steps (unhide -> hide): - repro in 7.4.0.3 with signature "SwFrame::FindFootnoteBossFrame(bool)": https://crashreport.libreoffice.org/stats/crash_details/213df40a-f967-4d5c-8150-fe0fdfe67d8f - repro in 7.6.6 with signature "SwFrame::GetPhyPageNum() const": https://crashreport.libreoffice.org/stats/crash_details/028918da-1c92-4436-8856-c21cb5fcef3c - in 24.2 and a recent daily build: no crash anymore. However, poor perf and daily build's console flooded with a loop of warnings that include: warn:sw.layout:251020:251020:sw/source/core/layout/wsfrm.cxx:3084: footnote frame on different page than ref frame? warn:legacy.osl:277213:277213:sw/source/core/layout/layact.cxx:589: LoopControl_1 in SwLayAction::InternalAction warn:legacy.osl:277437:277437:sw/source/core/layout/layact.cxx:770: LoopControl_3 in Interrupt formatting in SwLayAction::InternalAction warn:sw.layout:277213:277213:sw/source/core/layout/layouter.cxx:190: Looping Louie: Stage 1! - comment 10 + comment 14 steps (update links): - repro in 7.4.0.3 with signature "SwFrame::FindFootnoteBossFrame(bool)": https://crashreport.libreoffice.org/stats/crash_details/d3eea219-f10d-4cbc-94c3-36568f6add15 - no crash anymore in 7.6.6, 24.2.2 and current daily build, but remains frozen for a while / very sluggish after updating links, one core at 100%. In daily build, flood of warnings as described above. - comment 15 / comment 21 steps (delete table row): - repro in 7.4 and 7.5: https://crashreport.libreoffice.org/stats/crash_details/5076ae70-c6ba-4c5b-a76b-23612cd7e645 - however, not reproduced in 7.6.6 anymore. - comment 24 (dbg build crash on update all): - can't test in recent trunk build because of the layout loop Given that (at least) all the non-debug crashes are now gone, and the variety of cases described, my suggestion is closing as "works for me" and open now reports as needed. Daily build used: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f4ef5435df5560e6b6b061ce4053c71e2819bf51 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: x11 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101280 [Bug 101280] [META] Layout loops -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108014] [META] Writer character style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108014 Bug 108014 depends on bug 124300, which changed state. Bug 124300 Summary: Crash after toggling Hidden in character style a couple of times or doing Update all https://bugs.documentfoundation.org/show_bug.cgi?id=124300 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 124300, which changed state. Bug 124300 Summary: Crash after toggling Hidden in character style a couple of times or doing Update all https://bugs.documentfoundation.org/show_bug.cgi?id=124300 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101280] [META] Layout loops
https://bugs.documentfoundation.org/show_bug.cgi?id=101280 Bug 101280 depends on bug 124300, which changed state. Bug 124300 Summary: Crash after toggling Hidden in character style a couple of times or doing Update all https://bugs.documentfoundation.org/show_bug.cgi?id=124300 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160894] When I utilize the "optimal height" feature to adjust row heights in CALC the screen goes crazy
https://bugs.documentfoundation.org/show_bug.cgi?id=160894 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m_a_riosv --- Not repro on Windows Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160893] XLOOKUP problem with date as text
https://bugs.documentfoundation.org/show_bug.cgi?id=160893
m_a_riosv changed:
What|Removed |Added
CC||miguelangelrv@libreoffice.o
||rg
--- Comment #1 from m_a_riosv ---
Created attachment 193924
--> https://bugs.documentfoundation.org/attachment.cgi?id=193924&action=edit
Sample file with XLOOKUP and MATCH
It seems to have the same differences as MATCH().
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: f4ef5435df5560e6b6b061ce4053c71e2819bf51
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded
Excel
$71,29 $86,92 =XLOOKUP("2024-01-15";A2:A4;B2:B4;"no invoice";0;2)
33,12 no invoice =XLOOKUP(DATE(2024;1;15);A2:A4;B2:B4;"no invoice";0;2)
$71,29 $86,92 =XLOOKUP(T("2024-01-15");A2:A4;B2:B4;"no invoice";0;2)
33,12 no invoice =XLOOKUP(45306;A2:A4;B2:B4;"no invoice";0;2)
$3,00 $2,00 =MATCH("2024-01-15";A2:A4;0)
1 #N/A=MATCH(DATE(2024;1;15);A2:A4;0)
$3,00 $2,00 =MATCH(T("2024-01-15");A2:A4;0)
1 #N/A=MATCH(45306;A2:A4;0)
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 66209] inserting/deleting rows: data integrity problem when data for "non-active" charts are updated
https://bugs.documentfoundation.org/show_bug.cgi?id=66209 --- Comment #45 from Esteban --- Tested following the steps in comment 32, bug is still being reproduced. Version: 7.3.7.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.3.7-0ubuntu0.22.04.4 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160892] "Write Error. Error in writing sub-document SfxBaseModel::storeSelf: 0x70c23..."
https://bugs.documentfoundation.org/show_bug.cgi?id=160892 --- Comment #4 from rgz92 --- Are you just giving info about the file for others or making a point? I have other documents with >10K images that work fine. This document isn't even 40% done. I don't see anything unreasonable here. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160892] "Write Error. Error in writing sub-document SfxBaseModel::storeSelf: 0x70c23..."
https://bugs.documentfoundation.org/show_bug.cgi?id=160892 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m_a_riosv --- No issue on Windows with: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded It is a huge file with more than four thousand images. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160896] New: Cell Column & Row Base
https://bugs.documentfoundation.org/show_bug.cgi?id=160896
Bug ID: 160896
Summary: Cell Column & Row Base
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: BASIC
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: junkyardma...@frontier.com
Description:
Cell and range properties and methods should be one based (1) not zero based
(0).
When counting things in that exist in the physical world the first item is 1,
not 0. Whether it be marbles or rows and columns.
For example
.getCellByPosition(1,1) ' Should return A1 (first row and column) not B2
(second row and column)
.getCellRangeByName("A1").CellAddress.Row ' Should return 1 (first row),
not 0
.getCellRangeByName("A1").CellAddress.Column' Should return 1 (first
column), not 0
Steps to Reproduce:
1.Self evident in description
2.
3.
Actual Results:
Self evident in description
Expected Results:
Self evident in description
Reproducible: Always
User Profile Reset: No
Additional Info:
Cell and range properties and methods should be one based (1) not zero based
(0).
When counting things in that exist in the physical world the first item is 1,
not 0. Whether it be marbles or rows and columns.
For example
.getCellByPosition(1,1) ' Should return A1 (first row and column) not B2
(second row and column)
.getCellRangeByName("A1").CellAddress.Row ' Should return 1 (first row),
not 0
.getCellRangeByName("A1").CellAddress.Column' Should return 1 (first
column), not 0
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 160887] "Pairwise kerning" with "Transparency" creates obstructive white artefact
https://bugs.documentfoundation.org/show_bug.cgi?id=160887 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Please attach a sample file, reduce the size as much as possible without private information, and paste the information in Menu/Help/About LibreOffice, there is a copy icon. -- You are receiving this mail because: You are the assignee for the bug.
