[Libreoffice-bugs] [Bug 153560] Rename "chapter" to "heading" in Insert Field (Document tab)
https://bugs.documentfoundation.org/show_bug.cgi?id=153560 --- Comment #11 from sdc.bla...@youmail.dk --- Created attachment 185594 --> https://bugs.documentfoundation.org/attachment.cgi?id=185594&action=edit test file to demonstrate "rule" for Numbering by Chapter (In reply to sdc.blanco from comment #10) > 3. I now have the hypothesis that "level" in "Numbering by Chapter" for > caption numbers follows the same (≤) rule The attachment provides some empirical support for that hypothesis. It also has some instructions that shows if the specified level is not found, then the first heading paragraph (at the top of the document) is used -- no matter what level (i.e., a new problem/bug?). And the same effect/rule also seems to be happening with the CI widget in user-defined index (which also has an "Evaluate up to level" ... (see bug 153710). It starts to look like there is a consistent "rule" used across the different situations (with index, variable, caption), but I guess not so surprising, given that they are all using a variable field. (but again, this is all empirical discovery, have not tried to follow the source code.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153837] Regional settings for French Canada standards are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=153837 Mike Kaganski changed: What|Removed |Added URL||https://lists.freedesktop.o ||rg/archives/libreoffice/202 ||3-February/08.html --- Comment #2 from Mike Kaganski --- See also: https://lists.freedesktop.org/archives/libreoffice/2023-February/08.html and https://wiki.documentfoundation.org/Faq/Writer/LinuxDefaultPageSize -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153837] Regional settings for French Canada standards are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=153837 Buovjaga changed: What|Removed |Added Component|Base|LibreOffice Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #1 from Buovjaga --- Please copy and paste here the contents of your Help - About (LibreOffice - About on macOS) by clicking the copy button. This allows us to know more about your system. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153818] Removed tables reappear after loading of document
https://bugs.documentfoundation.org/show_bug.cgi?id=153818 Buovjaga changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #8 from Buovjaga --- László has been making many fixes and improvements to change tracking regularly, so would be interesting to hear, if you reproduce the problem with the latest unstable https://dev-builds.libreoffice.org/daily/master/current.html If the bug still exists, then the next step would be to check, if a code change causing it can be found: https://wiki.documentfoundation.org/QA/Bibisect Unfortunately it can take dozens of gigabytes of disk space in order to investigate. I am available for helping with the process via screensharing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153710] "Evaluate up to level" for Chapter Info for User-Defined Index shows only top level or all levels
https://bugs.documentfoundation.org/show_bug.cgi?id=153710 --- Comment #1 from sdc.bla...@youmail.dk --- I believe that what is happening in the attachment is: there are no headings with outline level (2-5) between the position of Table 1 and the top of the document, so it only uses the first heading that is encountered, which in the attachment is level 1. If the outline level of the first heading is changed to a value between 2 and 5, then this is the heading number that will appear in the (updated index). Or if a heading with outline level between 2 and 5 is inserted between the first (outline level 1) heading and the level 6 heading (before the table), then this heading number will be used. In short, the rule between used by "Evaluate up to level" option is show the contents of the first immediately preceding paragraph that has an outline level less than or equal to (≤) the number entered in the "evaluate...level" spinbox. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153814] many "configitem.cxx:423: ignoring XHierarchicalNameAccess ColorSchemes" warnings at startup
https://bugs.documentfoundation.org/show_bug.cgi?id=153814 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Stéphane Guillou (stragu) --- Thanks Julien, you're right, a fresh profile fixed it. I thought it could have been related to the unnamed theme in bug 153794 but doesn't look like it. Marking as WFM for now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140879] [META] Console noise
https://bugs.documentfoundation.org/show_bug.cgi?id=140879 Bug 140879 depends on bug 153814, which changed state. Bug 153814 Summary: many "configitem.cxx:423: ignoring XHierarchicalNameAccess ColorSchemes" warnings at startup https://bugs.documentfoundation.org/show_bug.cgi?id=153814 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=89606 Dieter changed: What|Removed |Added Depends on||143157 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143157 [Bug 143157] Alphabetical index field: on mouse-over include keys in tooltips -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143157] Alphabetical index field: on mouse-over include keys in tooltips
https://bugs.documentfoundation.org/show_bug.cgi?id=143157 Dieter changed: What|Removed |Added Version|unspecified |7.1.3.2 release Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Blocks||89606 --- Comment #7 from Dieter --- For me that's a reasonable enhancement request: Steps: 1. Open attachment 185543 2. Move cursor at the right of grey index mark before "excavation" (sidenote: very difficult make toltip appear. A better result is reached, if word is selected when creating a ne index entry) Actual result: Tooltip "excavations" Enhancement: Tooltip: "Keston > excavations" => NEW Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=89606 [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153840] [Calc] Copying huge(?) data by Ctrl-C caused BSOD in Win11 with hardware acceleration on
https://bugs.documentfoundation.org/show_bug.cgi?id=153840 --- Comment #1 from Franklin Weng --- Created attachment 185593 --> https://bugs.documentfoundation.org/attachment.cgi?id=185593&action=edit test sample file which caused BSOD on win11 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153840] New: [Calc] Copying huge(?) data by Ctrl-C caused BSOD in Win11 with hardware acceleration on
https://bugs.documentfoundation.org/show_bug.cgi?id=153840 Bug ID: 153840 Summary: [Calc] Copying huge(?) data by Ctrl-C caused BSOD in Win11 with hardware acceleration on Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: frank...@goodhorse.idv.tw Description: Reported by users here: https://ask.libreoffice.org/t/calc-7-5-0-3-for-windows-bsod/88511 In Calc 7.5.0.3, when copying a huge amount of data would cause BSOD in Windows 11, the error message was "page_fault_in_nonpaged_area". The tested ods file will be attached soon. In the ods file, column A-D are pure data, column E-F are formulas. When enabling the "Use hardware acceleration" in Tools - Options - LibreOffice - View, selecting cells including column E-F (for example, select A1:F32376) and hitting Ctrl-C would cause BSOD in Win11. Not happening in the following condition: - Selecting fewer data (for example, E1:F10) - Not selecting cells from column E and F (for example, selecting A1:D32376) - check "Force Skia software rendering" - In version 7.4.5.1, no such problem even enabling hardware acceleration Not happening in Linux (tested in Debian testing, but in my own box). Steps to Reproduce: 1. Open the attached file 2. Select data cell A1:F32376 3. Hit Ctrl-C Actual Results: Blue Screen of Death with message "page_fault_in_nonpaged_area" Expected Results: OS not crashed Reproducible: Always User Profile Reset: No Additional Info: Problematic version: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: zh-TW (zh_TW); UI: zh-TW Calc: CL threaded Non-problematic version: Version: 7.4.5.1 (x64) / LibreOffice Community Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: zh-TW (zh_TW); UI: zh-TW Calc: CL Graphic card information: NVIDIA GeForce GTX 1060 Driver version: 528.49 OS information: Windows 11 Professional 22H2 Installed: 2022/9/30 OS build: 22621.1265 體驗 Windows Feature Experience Pack 1000.22638.1000.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122755] [META] Formulae in Writer tables bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=122755 Dieter changed: What|Removed |Added Depends on||153422 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153422 [Bug 153422] Writer Table Formula Evaluation Errors -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153422] Writer Table Formula Evaluation Errors
https://bugs.documentfoundation.org/show_bug.cgi?id=153422 Dieter changed: What|Removed |Added Blocks||122755 CC||dgp-m...@gmx.de Version|3.3.0 release |7.4.5.1 release Whiteboard| QA:needsComment| --- Comment #3 from Dieter --- Tested with Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded Steps 1. Open attachment 185240 2. In empty table cell C1 enter a number between -2 and 2 3. Click into another cell or outside table 4. Compare results in column C with expected results at buttom of page I can see, that results differ from expected results, but since I'm not familiar with such formulars I can't asses, which results are correct. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122755 [Bug 122755] [META] Formulae in Writer tables bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153079] [Feature request] -Update Index- add option to update pages only (similar to MS Office option)
https://bugs.documentfoundation.org/show_bug.cgi?id=153079 Dieter changed: What|Removed |Added CC||yao.houpho...@ensible.de --- Comment #4 from Dieter --- *** Bug 153550 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153550] Formatting: It's not possible to update only the page numbers in "table of contents"
https://bugs.documentfoundation.org/show_bug.cgi?id=153550 Dieter changed: What|Removed |Added Resolution|--- |DUPLICATE Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de Status|UNCONFIRMED |RESOLVED --- Comment #2 from Dieter --- *** This bug has been marked as a duplicate of bug 153079 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107965] Apply a font color to multiple cells doesnt colorize all text
https://bugs.documentfoundation.org/show_bug.cgi?id=107965 --- Comment #25 from Kevin --- Hi - Yes, this bug is still easily reproducible with the spreadsheet and steps in the first comment, like almost every one I reported on the topic of formatting in Calc. The reason I stopped regularly beta-testing was frustration. Calc fixed many of the most annoying things in Excel; that was all that was needed, but for some reason Calc introduced a whole system of graphics bugs that were never in Excel. The poster child for this complaint is Calc's approach of taking the border between two cells and treating it as if it were two borders, invisible to the user, with one controlled by editing one cell and one by editing the other. There is no way to know which formatting aspect is part of which cell. None of this is in Excel. At one point I was spending so much time working on a project in Calc and reporting these bugs and just getting the most arrogant uncaring non-responses. If you love software, this is just heartbreaking. It was such a great idea to have an open source version of Excel without the myriad hated bugs that everyone suffered through and then to unnecessarily add a whole complex of new bugs! WHY? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153606] macOS app icon is not properly integrated
https://bugs.documentfoundation.org/show_bug.cgi?id=153606 --- Comment #33 from alexandre burton --- i find the floating proposal takes a nice position in the dock. it asserts it's identify while playing within the rules. the guidelines don't require the icon to be pure square; they mention a "rounded rectangle" shape, provide guidelines and safe areas, etc. while they take the starting position of working with "full bleed squares", they give the example of iMovie as an icon that "breaks" the usual shape while maintaining graphical logic: https://developer.apple.com/design/human-interface-guidelines/foundations/app-icons/images/app-icon-consistent-shape_2x.png -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153839] Exporting to xhtml results in most of the tags and content in one single line
https://bugs.documentfoundation.org/show_bug.cgi?id=153839 --- Comment #2 from Franklin Weng --- Created attachment 185592 --> https://bugs.documentfoundation.org/attachment.cgi?id=185592&action=edit Exported HTML file by 4.0.6.2 Most of the content are in one single line. No newline after most of the html tags. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153839] Exporting to xhtml results in most of the tags and content in one single line
https://bugs.documentfoundation.org/show_bug.cgi?id=153839 --- Comment #1 from Franklin Weng --- Created attachment 185591 --> https://bugs.documentfoundation.org/attachment.cgi?id=185591&action=edit Exported HTML file by 3.6.7.2. The contents are split into multiple lines. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153839] New: Exporting to xhtml results in most of the tags and content in one single line
https://bugs.documentfoundation.org/show_bug.cgi?id=153839 Bug ID: 153839 Summary: Exporting to xhtml results in most of the tags and content in one single line Product: LibreOffice Version: 4.0.6.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: frank...@goodhorse.idv.tw Description: When exporting the document into xhtml format, almost all the tags, including , , , , , ... etc don't have a newline \n (and/or carriage return \r) after them, so most of the content are in one single line. It didn't affect the result in a browser, but a lot more difficult if we need to manually maintain the xhtml file. Steps to Reproduce: 1. Save a document (or export it) as a xhtml file 2. 3. Actual Results: Most of the content are in one single line. Expected Results: Should split into multiple lines by each tag. It's easier to maintain manually when necessary. Reproducible: Always User Profile Reset: No Additional Info: In 3.6.7.2 (版本 3.6.7.2 (組建 ID：e183d5b)) the tags and contents are split into multiple lines. Since 4.0.6.2 (版本 4.0.6.2 (組建 ID：2e2573268451a50806fcd60ae2d9fe01dd0ce24), the second oldest version I installed in my system) it started becoming in all single line. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153822] After a period of time with libreoffice on in dark mode windows, the menu background changes to a dark colour.
https://bugs.documentfoundation.org/show_bug.cgi?id=153822 steve changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |FIXED Version|7.5.0.3 release |7.4.5.1 release --- Comment #2 from steve --- (In reply to m.a.riosv from comment #1) > Please test with > https://downloadarchive.documentfoundation.org/libreoffice/old/7.5.1.2/ > > If it doesn't work, please test disabling Skia > Menu/Tools/Options/LibreOffice/View - Graphics Output Oh thanks, it does work properly in version 7.5.1.2! Sorry to bother you( •̀ ω •́ )✧ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153515] Incorrect handling of FullScreen mode (Writer and Calc) parsing ooSetupFactoryWindowAttributes, LO module jumps to 0, 0 position on relaunch
https://bugs.documentfoundation.org/show_bug.cgi?id=153515 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149907] Standard Filter demands change on "Value" field, otherwise it does not update results
https://bugs.documentfoundation.org/show_bug.cgi?id=149907 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153550] Formatting: It's not possible to update only the page numbers in "table of contents"
https://bugs.documentfoundation.org/show_bug.cgi?id=153550 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153548] F4 Absolute Cell Referencing not working in specific circumstances
https://bugs.documentfoundation.org/show_bug.cgi?id=153548 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 Bug 102847 depends on bug 82380, which changed state. Bug 82380 Summary: Wrong "Reached the end of the document" text with 'Find Next' and 'Find Previous' https://bugs.documentfoundation.org/show_bug.cgi?id=82380 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153818] Removed tables reappear after loading of document
https://bugs.documentfoundation.org/show_bug.cgi?id=153818 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153818] Removed tables reappear after loading of document
https://bugs.documentfoundation.org/show_bug.cgi?id=153818 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 82380] Wrong "Reached the end of the document" text with 'Find Next' and 'Find Previous'
https://bugs.documentfoundation.org/show_bug.cgi?id=82380 --- Comment #13 from QA Administrators --- Dear Prathapmuruganandam, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 82380] Wrong "Reached the end of the document" text with 'Find Next' and 'Find Previous'
https://bugs.documentfoundation.org/show_bug.cgi?id=82380 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150186] Version 7.3.5 - Crashing on New Document
https://bugs.documentfoundation.org/show_bug.cgi?id=150186 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150186] Version 7.3.5 - Crashing on New Document
https://bugs.documentfoundation.org/show_bug.cgi?id=150186 --- Comment #8 from QA Administrators --- Dear Gene, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147598] Continuous crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=147598 --- Comment #13 from QA Administrators --- Dear DErik, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145558] reproducible Crash: VBA insert graphic, save, crash
https://bugs.documentfoundation.org/show_bug.cgi?id=145558 --- Comment #6 from QA Administrators --- Dear daniel.heiserer, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144508] Detached side menu off-screen can't be returned to visible area
https://bugs.documentfoundation.org/show_bug.cgi?id=144508 --- Comment #8 from QA Administrators --- Dear noses, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97935] FILESAVE, FORMATTING. Format of cells containing text with several formats is corrupted when saving as xls, xlsx
https://bugs.documentfoundation.org/show_bug.cgi?id=97935 --- Comment #19 from QA Administrators --- Dear Fran, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94284] Calc does not export Charts to XLS with axis set to start or end (see Comment 8)
https://bugs.documentfoundation.org/show_bug.cgi?id=94284 --- Comment #19 from QA Administrators --- Dear Ilya, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93512] Non-modal dialogs automatically open on startup if LO is closed when they are open
https://bugs.documentfoundation.org/show_bug.cgi?id=93512 --- Comment #11 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92999] EDITING: Context Menu off the screen upon scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=92999 --- Comment #5 from QA Administrators --- Dear Carlos Marques, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92552] Contex menu behavior editing Cell content is inconsistent.
https://bugs.documentfoundation.org/show_bug.cgi?id=92552 --- Comment #7 from QA Administrators --- Dear Wolfgang Jäger, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89060] Lines move when focusing into text box (see comment 12)
https://bugs.documentfoundation.org/show_bug.cgi?id=89060 --- Comment #16 from QA Administrators --- Dear Chris King, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140651] Combined shape (group) changes position after undo deletion of one of the elements
https://bugs.documentfoundation.org/show_bug.cgi?id=140651 --- Comment #6 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38803] Import keybindings for macros
https://bugs.documentfoundation.org/show_bug.cgi?id=38803 --- Comment #9 from QA Administrators --- Dear Björn Michaelsen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140618] Calc: Problem with macro for on/off Automatic Spell Checking
https://bugs.documentfoundation.org/show_bug.cgi?id=140618 --- Comment #5 from QA Administrators --- Dear Kamil Landa, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140173] paragraph properties do not spread across cells in a table - libreoffice writer
https://bugs.documentfoundation.org/show_bug.cgi?id=140173 --- Comment #4 from QA Administrators --- Dear Titus Chirila, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132300] Abbreviations :XX: for autocorrection do not work in French
https://bugs.documentfoundation.org/show_bug.cgi?id=132300 --- Comment #8 from QA Administrators --- Dear Silvain Dupertuis, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123706] FILEOPEN DOCX Position of line breaks is different in Word and Writer with Hungarian locale
https://bugs.documentfoundation.org/show_bug.cgi?id=123706 --- Comment #6 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.
[Libreoffice-bugs] [Bug 123634] Calc does not adjust columns correctly when they are frozen
https://bugs.documentfoundation.org/show_bug.cgi?id=123634 --- Comment #6 from QA Administrators --- Dear hunta...@gmail.com, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118262] Use of Print Options is not Transparent
https://bugs.documentfoundation.org/show_bug.cgi?id=118262 --- Comment #7 from QA Administrators --- Dear Harald Koester, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107965] Apply a font color to multiple cells doesnt colorize all text
https://bugs.documentfoundation.org/show_bug.cgi?id=107965 --- Comment #24 from QA Administrators --- Dear Kevin, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153838] Wrong page numbering on 'Only right'/'Only left' page styles.
https://bugs.documentfoundation.org/show_bug.cgi?id=153838 --- Comment #1 from sebastian.j...@hotmail.com --- Created attachment 185590 --> https://bugs.documentfoundation.org/attachment.cgi?id=185590&action=edit Example document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153560] Rename "chapter" to "heading" in Insert Field (Document tab)
https://bugs.documentfoundation.org/show_bug.cgi?id=153560
--- Comment #10 from sdc.bla...@youmail.dk ---
(In reply to sdc.blanco from comment #9)
> The two formats ("heading number"; "heading number without separator") use
> the immediately prior heading, where the "up to level" option controls how
> many levels of the heading number are displayed.
Correct description of appearance, but for wrong reason!
> other two formats for the "Heading" field type ("heading contents"; and
> "heading number and contents").
> Display the heading contents for the first prior heading whose outline level
> is less than or equal (≤) than the number specified in "up to level".
This is the correct reason.
> Furthermore, with "heading number and contents", unlike the "number"
> formats, there is no control over how many outline levels of the heading
> number shown.
False issue. I misinterpreted the levels option as controlling how many levels
are shown (which is empirically correct, but an artifact of how the "prior
numbered heading" is selected). The option shows the number and contents of
the first header that satisfies the (≤) rule.
> An immediate hypothesis is that the "content" cases are a bug
Possibly.
To summarize:
1. The "level" control has the same behavior for all four formats of the
"Heading" field type.
2. Regardless of format, the field selects the first previous heading that has
an outline level equal or less than the value that is specified in the "level"
spinbox. (maybe that is the bug? already filed: Bug 147004) If deemed to be
a bug, then "up to level" should be changed to: "outline level".
3. I now have the hypothesis that "level" in "Numbering by Chapter" for
caption numbers follows the same (≤) rule (which may also be a bug, if it does
not use the same code), but I could not "see" that problem before now (with my
empirical method), because that dialog only shows numbers, not contents.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153838] New: Wrong page numbering on 'Only right'/'Only left' page styles.
https://bugs.documentfoundation.org/show_bug.cgi?id=153838 Bug ID: 153838 Summary: Wrong page numbering on 'Only right'/'Only left' page styles. Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sebastian.j...@hotmail.com Description: When applying a Side-only page style, e. g. selecting 'Only right' on Page Style > Page > Page layout, page numbers are all odds when continuous numbering was expected. Same with 'Only left', numbering is all even. Steps to Reproduce: 1. Create or modify a style so it's only a left/right side page (Page Style > Page > Page layout > Select 'Only left' or 'Only right'). Also activate header or footer. 2. Apply style to page 3. In the activated header or footer, insert Page Number (Insert > Page Number) 4. Insert multiple pages with the same style, via automatic or manual page-break without page numbering change. 5. Observe the odd behaviour. Actual Results: Page numbers where only even for 'Left only' option, or odd for 'Right only'. Expected Results: A continuous numbering. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.5.1 / LibreOffice Community Build ID: 5b836ae11a8f2f3ddf6e88bcd7da796d725223ae CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: es-PY (es_PY.UTF-8); UI: en-US Calc: threaded Probably related to bug 117231 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93904] Strange Behaviour of Fields->Document->Chapter->Level
https://bugs.documentfoundation.org/show_bug.cgi?id=93904 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||9302 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129302] FORMATTING:chapter name field in header does not reflect first chapter in current page
https://bugs.documentfoundation.org/show_bug.cgi?id=129302 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=93 ||904 --- Comment #19 from sdc.bla...@youmail.dk --- (In reply to jeanmarczambon from comment #12) > A typical case is a document which first page starts with different heading > levels (see attachment): Or this related case (bug 93904, comment 3), where both outline level 1 and outline level 2 headings are desired in the header for all pages. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129302] FORMATTING:chapter name field in header does not reflect first chapter in current page
https://bugs.documentfoundation.org/show_bug.cgi?id=129302 --- Comment #18 from sdc.bla...@youmail.dk --- Some points of clarification: 1. The attachment 156451 corresponds to the description in the OP. That is, a Chapter (document) field type is inserted. (It is not a cross-reference as discussed in comment 2, comment 6, and comment 7). 2. There is no "level" setting for a cross-reference, and cross-references would not work in this context, because they would continue to refer to the same heading. 3. In part, the OP seems to reflect a misunderstanding of the function of the "level" attribute for the Chapter field type - by assuming (reasonably, but incorrectly) that the "level" specifies the outline level of the "Chapter name" to be displayed. (this is a documentation problem, which is being addressed, e.g., bug 153560 comment 9). 4. The test case in attachment 156451 is focused on the first page. There may be a bug in the actual behavior of "Chapter" field types when inserted in the Header on the first page of a document (see bug 93904, comment 6), which could obscure understanding/diagnosis of the problem, but even if that bug was addressed, it would not address the main issue in the OP. 5. The main (and genuine) problem of the OP is raised in comment 5 When a new level 2 chapname appears in middle of page, it only start to show on the FOLLOWING page. but there is a critical ambiguity here. What if two new headings with outline level 2 appear on the same page, which one should be shown in the header? (this point is raised in comment 10) 6. comment 12 has some great examples (plausible use cases), which I believe are impossible to achieve with the Chapter field type for the following two reasons. Two main showstoppers: a. It is not possible to specify very precisely (except for outline level 1) what outline level to use for the field. b. The Header does not "read forward" to pick up the header on the page where it appears. (This is also the complaint of the OP). [side note: The field in the Header does "read forward" if a new page starts with a heading, whose outline level is within the "level" range specified for the field.] Maybe those two problems (a) and (b) should be separated into two different tickets, if they do not exist already. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153836] Spellcheck not working
https://bugs.documentfoundation.org/show_bug.cgi?id=153836 Beth Metzler changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #2 from Beth Metzler --- I have restarted in Safe Mode and spell check is still not working correctly. It will only check the sentence that the cursor is at. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153837] New: Regional settings for French Canada standards are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=153837 Bug ID: 153837 Summary: Regional settings for French Canada standards are missing Product: LibreOffice Version: 3.5.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nouvel.aubergi...@gmail.com Description: French LibreOffice installed in Quebec is set to follow European paper standards when Quebec standards are the same as North American standards. This applies to printing paper sizes and the modified Qwerty keyboard layout. I also need a set of all FRENCH LO templates with "US letter" etc. paper sizes. Steps to Reproduce: 1. This is a regional language and standards issue that was missed by LO. 2. Quebec uses North American standards as is used by NAFTA. 3. Please indicate where French templates with US paper sizes can be downloaded and installed for Quebec and French Canada users? Actual Results: Default templates are in A4 paper size for French language versions for Canada. Expected Results: n/a Reproducible: Always User Profile Reset: No Additional Info: n/a -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153822] After a period of time with libreoffice on in dark mode windows, the menu background changes to a dark colour.
https://bugs.documentfoundation.org/show_bug.cgi?id=153822 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Please test with https://downloadarchive.documentfoundation.org/libreoffice/old/7.5.1.2/ If it doesn't work, please test disabling Skia Menu/Tools/Options/LibreOffice/View - Graphics Output -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153824] Text Not Visible: When Selecting a Cell to Include in Equation, Text for Said Cell is Hidden Behind Highlight
https://bugs.documentfoundation.org/show_bug.cgi?id=153824 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Please test modifying the option for Skia in Menu/Tools/Options/LibreOffice/View - Graphics Output -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149907] Standard Filter demands change on "Value" field, otherwise it does not update results
https://bugs.documentfoundation.org/show_bug.cgi?id=149907 ady changed: What|Removed |Added Summary|Condition operater (like|Standard Filter demands |">") on the Standard Filter |change on "Value" field, |can not be Updated once |otherwise it does not |added |update results -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153833] [Impress] Copy-pasting table changes its size (height)
https://bugs.documentfoundation.org/show_bug.cgi?id=153833 m.a.riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW --- Comment #5 from m.a.riosv --- Reproducible with Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded The problem seems to be in the first two rows. The ones changing their height. Cut & Paste shows the same issue. It is really much worse in master. It changes from Predeterminado_1_1 style to Default Drawing Style Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ab20dba30769a5a52830220daa347772485db6a2 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93904] Strange Behaviour of Fields->Document->Chapter->Level
https://bugs.documentfoundation.org/show_bug.cgi?id=93904 --- Comment #6 from sdc.bla...@youmail.dk --- I believe the general "rule" when using format "Chapter name" or "Chapter number and name" is: Show contents of the first immediately preceding paragraph that has an outline level less than or equal to (≤) the number entered in the "Level" spinbox. (bug 147004, comment 11) It appears that this rule is also what Stefan has discovered in his results 1.) and 2.) Meanwhile attachment 118401 seems to demonstrate a special corner case, where the rule seems to be: When a Chapter (document) field, with format "Chapter name" is inserted on the first page, then show the contents of the first heading (with any outline level), regardless of what "level" is set for the field. This actual result happens if the field is in the Header (Stefan's case) or simply inserted at the beginning of a document. That seems like a bug -- and maybe this ticket could be used for that particular case (if others can confirm). Tested with: 7.2.7.2 and Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c41e872ed248f804249ecf4d65c4afc2e426e329 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138414] In Draw, number of decimal points in dimension lines is not applied
https://bugs.documentfoundation.org/show_bug.cgi?id=138414 --- Comment #8 from Petr Tichý --- The bug is still present in version 7.5.0.3 (X86_64) / LibreOffice Community. Setting of decimal point is not respected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153836] Spellcheck not working
https://bugs.documentfoundation.org/show_bug.cgi?id=153836 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Please test in safe mode, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92805] Field type "chapter" generates wrong text if its actual level has not been used yet
https://bugs.documentfoundation.org/show_bug.cgi?id=92805 --- Comment #9 from sdc.bla...@youmail.dk --- (In reply to Dieter from comment #8) > You can solve the problem if you assign first level of chapter numbering to > PS "Heading 2" with Tools => Chapter Numbering. Update fileds (F9) and > everything works as expected. Cool solution -- but probably the preferred solution would be to use the "Level" control for the field. Open "minimal test case" (attachment 117302), edit field in Header of "Left Page" Page Style. Change "level" from "1" to "2". I believe this gives the expected result in the OP => WFM (in 7.2.7.2) or NAB (if you can test with 4.4.4.3-3) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149907] Condition operater (like ">") on the Standard Filter can not be Updated once added
https://bugs.documentfoundation.org/show_bug.cgi?id=149907 ady changed: What|Removed |Added Keywords||regression --- Comment #16 from ady --- @Rainer, most of the info is/was already posted in comment 7 and in the "see also" field. Currently this is repro since LO 7.3 up until current 7.6 alpha+. >From the release notes for LO 7.3 (see [1]), there are at least 3 items related to filtering features in Calc (i.e. potential suspects for origin of regression): * Support Color Filter in "Standard Filter" dialog tdf#143103 (Samuel Mehrbrodt, allotropia) * Queries and filters using some text-based operations such as 'contains' now properly work even with numeric data core commit 0d1971a8 (Luboš Luňák, Collabora) * Improved speed for filtering by Autofilter tdf#133835, tdf#133867, tdf#133996 (Noel Grandin, Luboš Luňák, Collabora) [1]: https://wiki.documentfoundation.org/ReleaseNotes/7.3#Calc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153560] Rename "chapter" to "heading" in Insert Field (Document tab)
https://bugs.documentfoundation.org/show_bug.cgi?id=153560
sdc.bla...@youmail.dk changed:
What|Removed |Added
Status|RESOLVED|NEW
Resolution|FIXED |---
--- Comment #9 from sdc.bla...@youmail.dk ---
New problem discovered in relation to "Up to level"
The two formats ("heading number"; "heading number without separator") use the
immediately prior heading, where the "up to level" option controls how many
levels of the heading number are displayed.
(at present the tooltip/extended tip and help is written in this way)
The new discovery is in relation to the other two formats for the "Heading"
field type ("heading contents"; and "heading number and contents").
Based on extensive experiments, my hypothesis for its rule:
Display the heading contents for the first prior heading whose outline level is
less than or equal (≤) than the number specified in "up to level".
For example, if inserted field has an "up to level" of "5", then the first
immediately prior paragraph with level 5 or less is shown (i.e., any
immediately prior headings with outline level 6 or greater are ignored). This
behavior contrasts with the "number" formats, which would select the first
heading (regardless of outline level).
(attachment 185589 gives a demonstration, which can be used for testing)
Furthermore, with "heading number and contents", unlike the "number" formats,
there is no control over how many outline levels of the heading number shown.
Before trying to make further adjustments in help/tips, let me check what is
the "intended" behavior here?
An immediate hypothesis is that the "content" cases are a bug (and a new ticket
should be filed), it is hard (for me) to imagine a use case that would need
this "feature?"
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114039] [META] Fields dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114039 Bug 114039 depends on bug 153560, which changed state. Bug 153560 Summary: Rename "chapter" to "heading" in Insert Field (Document tab) https://bugs.documentfoundation.org/show_bug.cgi?id=153560 What|Removed |Added Status|RESOLVED|NEW Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153836] New: Spellcheck not working
https://bugs.documentfoundation.org/show_bug.cgi?id=153836 Bug ID: 153836 Summary: Spellcheck not working Product: LibreOffice Version: 7.5.0.3 release Hardware: Other OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: abodro...@gmail.com Description: Since I've downloaded LibreOffice 7.5.0.3 the spell check feature is not working at all. It only checks the first sentence and then freezes. I have also lost the saved dictionary that I had from all of my previous versions. Steps to Reproduce: 1.Type in a paragraph of 3 or more sentences. 2.Run the spell check feature (press F7 or Tools then Spelling) 3. Actual Results: I have typed two different documents (one 7 pages and one 5 pages) and attempted to perform the spell check it goes to the first sentence of the page and then freezes. Expected Results: For the spell check to start at the first word of the document and go through the document finding any misspellings or grammatical errors and allow me to change them to the correct spelling with either my input from my keyboard or choosing an option given by the program. Reproducible: Always User Profile Reset: No Additional Info: I have been using this program (which I love) to type journals of my grandmother. These journals go from 1976 through 2019 (about a week before her death) and I have finished all of the 1970's, 1980's, 1990's, and am through August 2002 in the other (older) versions of LibreOffice and have not had an issue with the spell check until this version. I have September 2002 and October 2002 that I have done in this new version and the spell check just does not work. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147004] 'Chapter' field should only show the paragraph preceding the field that has the same outline level as the level setting for the field
https://bugs.documentfoundation.org/show_bug.cgi?id=147004 sdc.bla...@youmail.dk changed: What|Removed |Added Attachment #177831|0 |1 is obsolete|| --- Comment #11 from sdc.bla...@youmail.dk --- Created attachment 185589 --> https://bugs.documentfoundation.org/attachment.cgi?id=185589&action=edit Test file to demonstrate the effect of the "level" control Marking previous comment as no-value, because of (possible) new discovery,and this comment replaces comment 5 (which is now marked as obsolete). Attached file gives demonstration of "actual" behavior of "level" spinbox, when type "Chapter" field uses format "chapter name" or "chapter number and name". The rule is: Show contents of the first immediately preceding paragraph that has an outline level less than or equal to (≤) the number entered in the "outline level" spinbox. Meanwhile, a different rule is operative when the formats are "chapter number" and "chapter number without separator". In that case, the rule is: use the immediately prior heading, where the "level" option controls how many levels of the heading number are displayed. (bug 153560 updates the help and tips in relation to these formats). Trying to clarify the discrepancy between how the "level" control operates with the different formats (starting in bug 153560 comment 9). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153833] [Impress] Copy-pasting table changes its size (height)
https://bugs.documentfoundation.org/show_bug.cgi?id=153833 --- Comment #4 from gmoll...@us.es --- LO 3.5.7.2 is ok. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153833] [Impress] Copy-pasting table changes its size (height)
https://bugs.documentfoundation.org/show_bug.cgi?id=153833 --- Comment #3 from gmoll...@us.es --- In version LO Impress 6.0.3.2 the size changes very little, but it does. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153835] New: Libre Text editor crashes while typing and auto recover does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=153835 Bug ID: 153835 Summary: Libre Text editor crashes while typing and auto recover does not work Product: LibreOffice Version: 7.4.0.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jazz17...@gmail.com Description: I downloaded a pdf bank statement to Libre Text Editor (LTE) which of course does not keep the tabs and paragraphs. This was a 4-page file in LTE. While manually entering tabs and paragraphs (about an 1/2 hours' time worth) LTE locks up. I leave it alone and wait. After 20-30 seconds LTE crashes. When I reopened and confirmed for it to recover it did not recover any of the tabs and paragraphs I have been typing for over 1/2 hour. Recommend expanding the buffer size for recovering files. Also add auto save option so LTE saves every few minutes. Actual Results: download a pdf bank statement file and paste multiple lines to 4-5 page Libre Text Editor (LTE) (notice tabs and paragraphs are not pasted). Manually enter in tabs and paragraphs Expected Results: LTE crashes Reproducible: Sometimes User Profile Reset: No Additional Info: Stored all my last keys I typed for the past hour+ into a temp file. Upon restarting LTE attempted to recover, but it did not have any of my keystrokes for the past hour. Unknow what version Properties Details only shows 7.4.Ink and this is not listed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153834] Ajout d'une fonction récepteur "=" dans un dessin "Carré" ou "Rectangle" ou "Zone de texte" dans LibreOffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=153834 Palongo changed: What|Removed |Added Version|7.5.0.0 beta1+ |7.5.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153834] New: Ajout d'une fonction récepteur "=" dans un dessin "Carré" ou "Rectangle" ou "Zone de texte" dans LibreOffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=153834 Bug ID: 153834 Summary: Ajout d'une fonction récepteur "=" dans un dessin "Carré" ou "Rectangle" ou "Zone de texte" dans LibreOffice Calc Product: LibreOffice Version: 7.5.0.0 beta1+ Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: palongo@gmail.com Description: Ajouter la fonction "=" pour qu'un zone de texte pourra recevoir un donnée venant d'une cellule d'un même feuille de calcule que l'objet ou non. C'est dire un objet dessiner dans Calc (en particulier une zone de texte) pourra recevoir un donnée "TEXT" à l'aide de la bare de formule en utilisant la signe "=" inserer dans l'objet. C'est très utile pour dessiner une tableau de bord dynamique et interactive sur Calc. Après une analyse Croiser Dynamique. Steps to Reproduce: 1.Insérer un Tableau Croisé Dynamique Dans une nouvelle feuille., faites une analyse et inserer des diagrammes. 2.Dessiner votre espace de tableau de bord en inserant des objets dessins et des zones de texte pour recevoir les resultat de l'analyse. 3.Copier les diagrammes du TCD dans votre espace tableau de bord. Mais pour le moment, on ne peut pas récupérer les données du TCD pour les insérer dans une zone de texte dans le tableau de bord. Et ce que je voudrais faire. Actual Results: Un zone de texte ne peut pas recevoir un formule ou fonction "=" Expected Results: Je voudrais qu'un zone de texte pourra recevoir un donnée à l'aide de la barre de formule en utilisant la signe "=". C'est très utile pour dessiner un tableau de bord dynamique et interactive sur Calc. Reproducible: Couldn't Reproduce User Profile Reset: No Additional Info: Ce fonctionnalité permet de élaborer un tableau de bord dynamique et interactive. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153833] [Impress] Copy-pasting table changes its size (height)
https://bugs.documentfoundation.org/show_bug.cgi?id=153833 --- Comment #2 from gmoll...@us.es --- It doesn't happen to me in the first version of LO: 3.3 running on Win7 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153833] [Impress] Copy-pasting table changes its size (height)
https://bugs.documentfoundation.org/show_bug.cgi?id=153833 --- Comment #1 from gmoll...@us.es --- Created attachment 185588 --> https://bugs.documentfoundation.org/attachment.cgi?id=185588&action=edit Impress file with the table for copy-pasting -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153833] New: [Impress] Copy-pasting table changes its size (height)
https://bugs.documentfoundation.org/show_bug.cgi?id=153833 Bug ID: 153833 Summary: [Impress] Copy-pasting table changes its size (height) Product: LibreOffice Version: 7.4.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gmoll...@us.es Description: In some table in Impress when copying and pasting it changes its height. In others not. That is why I am attaching a file with a table where I indicate its height so that you can copy and paste it and see if it changes. We have tried several people and only one did not, others with Linux Mint 20.3 XFCE, Fedora 37 KDE, with Windows 6.1 Service Pack 1 Build 7601, with different versions of LO, 7.4.5.1, 7.5.0.3, 7.4.4.2, installed from repositories and from flathub (flatpak). Steps to Reproduce: 1.Open the attached file 2.select the table 3.Copy 4.Deselect the table 5.Paste the table 6.The new table is more higher Actual Results: The new table is more higher Expected Results: The new table is identical to old table Reproducible: Always User Profile Reset: Yes Additional Info: It doesn't happen to everyone, it does to the majority and it always happens to them. If I create another table, it no longer happens to it. Maybe this table is imported from another powerpoint presentation. The problem is that I use the expand-animations plugin that allows to convert the presentation to a pdf, each change creates a new slide but if it changes the table when copying it doesn't look good. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147004] 'Chapter' field should only show the paragraph preceding the field that has the same outline level as the level setting for the field
https://bugs.documentfoundation.org/show_bug.cgi?id=147004 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3560 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153560] Rename "chapter" to "heading" in Insert Field (Document tab)
https://bugs.documentfoundation.org/show_bug.cgi?id=153560 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||7004 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153560] Rename "chapter" to "heading" in Insert Field (Document tab)
https://bugs.documentfoundation.org/show_bug.cgi?id=153560 sdc.bla...@youmail.dk changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114039] [META] Fields dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114039 Bug 114039 depends on bug 153560, which changed state. Bug 153560 Summary: Rename "chapter" to "heading" in Insert Field (Document tab) https://bugs.documentfoundation.org/show_bug.cgi?id=153560 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147004] 'Chapter' field should only show the paragraph preceding the field that has the same outline level as the level setting for the field
https://bugs.documentfoundation.org/show_bug.cgi?id=147004 --- Comment #10 from sdc.bla...@youmail.dk --- @Dieter - I think this ticket is NAB (or a "documentation" problem, which should be fixed now with bug 153560). The actual behavior of "level" is to use the immediately prior heading, where the "level" option is to control how many levels of the heading number are displayed. (The UI control is now relabeled "Up to level", and the tooltip/extended tip and help page are updated.) Not sure how to "resolve" this ticket. I do not know if you want to file a new ticket in relation to your comment 8. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153832] New: Save-as glitch - Loading a document and saving it at another location all text gets deleted.
https://bugs.documentfoundation.org/show_bug.cgi?id=153832 Bug ID: 153832 Summary: Save-as glitch - Loading a document and saving it at another location all text gets deleted. Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: frvinc...@gmail.com Description: I opened a word document and saved it in a new location. I then went to that location and opened it only to discover all text had been deleted - graphics remained. I opened the original and again saved in a new location, but in native Libre Office format. I then went to that location and opened it and all the text was there. I saved as word 97-2003 document, exited and loaded the document and the text had disappeared. Steps to Reproduce: 1.Open a word 97-2003 doc 2.Save-as in a new location 3.Open the doc in new location 4.All text is gone - graphics remain. Actual Results: Lost all text Expected Results: Exact duplicate of original doc Reproducible: Always User Profile Reset: No Additional Info: I do not know enough to add more info. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153831] Disfonctionnement des animations dans LibreOffice Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=153831 Palongo changed: What|Removed |Added Version|7.5.0.0 beta1+ |7.5.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153560] Rename "chapter" to "heading" in Insert Field (Document tab)
https://bugs.documentfoundation.org/show_bug.cgi?id=153560 --- Comment #8 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/9b4f3d78786ba6b1d014dfb6075b3245cd5f7bf2 tdf#153560 update changes "Chapter"->"Heading"; "Level"->"Up to level" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153831] New: Disfonctionnement des animations dans LibreOffice Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=153831 Bug ID: 153831 Summary: Disfonctionnement des animations dans LibreOffice Impress Product: LibreOffice Version: 7.5.0.0 beta1+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: palongo@gmail.com Description: Plusieurs annimations ne sont pas opérationnel ou elles fontionnes mal. Et lorsqu'on applique plusieurs animations et des objets ou images en supperposition dans un Diapo. Lors du lancement du Diapo, certains objets ou images n'apparaissent pas ou apparaissent mal. Ainsi que l'apparence du diapo n'est pas lisse, elle est pixialisé. Souvant, l'aniamtion se coincé. Steps to Reproduce: 1.Appliquer une ou des animations sur une ou des objets tells qu'un Dessin ou image dans Impress. 2.Lancer le Diaporama, puis oberver que l'aniamtion est coincé. Ainsi que l'apparition de certain objet est perturbé. 3. Actual Results: L'animation est coincé, l'image est flou et pixialisé. Des dessins n'apparaissent pas. Expected Results: Lancer un Diapo bien animé avec un qualité d'iamge 4K ou HD au moins. Reproducible: Always User Profile Reset: No Additional Info: Lancer l'animation sans coincé. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153829] Crash du programme LibreOffice Calc lors de la personalisation de l'arrière plan d'un Diagramme.
https://bugs.documentfoundation.org/show_bug.cgi?id=153829 Palongo changed: What|Removed |Added Version|7.5.0.0 alpha0+ |7.5.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153829] New: Crash du programme LibreOffice Calc lors de la personalisation de l'arrière plan d'un Diagramme.
https://bugs.documentfoundation.org/show_bug.cgi?id=153829 Bug ID: 153829 Summary: Crash du programme LibreOffice Calc lors de la personalisation de l'arrière plan d'un Diagramme. Product: LibreOffice Version: 7.5.0.0 alpha0+ Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: palongo@gmail.com Description: Après insertion d'un Diagramme. On veut personaliser le fond, la forme et la couleur du graphique. Mais lorsqu'on touche l'arrière-plan, surtout en changeant le fond en types "Dégradé" ou "Bitmap". Le va être figé puis crash. Disparu du bureau. Steps to Reproduce: 1.Insérer un graphique dans calc, choisissez Diagramme en baton ou autre. 2.Modifier l'arrière-plan, changer en mode "Dégradé" ou "Supprimer pour être "Transparent". 3.Et en faisant ça, le programme va être figé et va disparaitre du bureau. Actual Results: Crash et redemarage automatique ou non du programme LibreOffice Calc. Expected Results: Que je pourrais changer et personnaliser mon graphique Calc. Reproducible: Always User Profile Reset: No Additional Info: Les graphiques dans Calc sont très rigide et peu modifiable. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153827] Crash à l'ouverture du programme
https://bugs.documentfoundation.org/show_bug.cgi?id=153827 Palongo changed: What|Removed |Added Version|7.5.0.0 alpha0+ |7.5.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153828] New: Lagging with GTK
https://bugs.documentfoundation.org/show_bug.cgi?id=153828 Bug ID: 153828 Summary: Lagging with GTK Product: LibreOffice Version: 7.5.0.3 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gerald.driss...@gmail.com Description: LibreOffice Writer has lagged key input with VLC=GTK3 and Nvidia (as well as HIDPI). No problem with SAL_USE_VCLPLUGIN gen or SAL_USE_VCLPLUGIN kf5 Steps to Reproduce: 1.Start Libre Office with VCL gtk3 2.pressing a key multiple times Actual Results: Key input is lagging. Especially when changing the input language to RTL and/or when editing tables. Expected Results: There should not be any delay, especially, when the document is new and empty. Reproducible: Always User Profile Reset: Yes Additional Info: I use Nvidia driver 525 and have deactivated hardware acceleration, window effects, etc. No difference. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153827] New: Crash à l'ouverture du programme
https://bugs.documentfoundation.org/show_bug.cgi?id=153827 Bug ID: 153827 Summary: Crash à l'ouverture du programme Product: LibreOffice Version: 7.5.0.0 alpha0+ Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: palongo@gmail.com Description: Après double clique sue le programme LibreOffice. Il ne réagit pas. Pourtant, plusieurs tâches sur ce programme sont après exécutés dans la gestion de tâche windows. En effet, il consomme trop de mémoire. Puis le programme demande toujours de redemarer en lide sans echec. Steps to Reproduce: 1.Démarer LibreOffice ou ouvrir un fichier existant directement. 2.Pas de réponse, voir la boite de dialogue de la gestion de tâche, trouver LibreOffice, puis "Arrêter la tâche une par une, puis qu'il y en a plusieurs". 3.Redemarer LibreOffice en mode sans échec en reinitialisant tous les paramettre personalisés, c'est sa demande. Actual Results: LibreOffice ouvert mais perte de certaine fonctionalité et des paramettres personalisées. Expected Results: LibreOffice ouvert mais perte de certaine fonctionalité et des paramettres personalisées. Reproducible: Sometimes User Profile Reset: Yes Additional Info: Juste ouvert après le demarage. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147075] Window goes to 1x2 pixel size when moving
https://bugs.documentfoundation.org/show_bug.cgi?id=147075 Buovjaga changed: What|Removed |Added CC||nickefo...@gmail.com Version|7.5.0.3 release |7.3.0.0.alpha1+ --- Comment #9 from Buovjaga --- (In reply to nickeforos from comment #8) > Hi > > this issue still exists and is bothering. I'm not sure when it exactly > appears. Sometimes appears when I just open Calc or when I try to move the > window. The window appears often as a small line, as shown in the attachment > of michael.vanderf...@gmail.com or as small rectangle. In both cases it > cannot be often resized by using the mouse. Ok, but from you as well as Michael, we still need the contents of your Help - About. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123396] LO Writer automatically replaces SVGs embedded in (F)ODT files with an embedded low-resolution PNGs and drops the SVGs from the documents
https://bugs.documentfoundation.org/show_bug.cgi?id=123396 --- Comment #14 from adrlop...@disroot.org --- Hello. As other users have already commented, this error is quite serious. Randomly, some original .svg are lost when saving the file in another format and they are replaced by low quality .png. Regards! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147075] Window goes to 1x2 pixel size when moving
https://bugs.documentfoundation.org/show_bug.cgi?id=147075 nickefo...@gmail.com changed: What|Removed |Added OS|All |Linux (All) Hardware|All |x86-64 (AMD64) Version|7.3.0.0.alpha1+ |7.5.0.3 release --- Comment #8 from nickefo...@gmail.com --- Hi this issue still exists and is bothering. I'm not sure when it exactly appears. Sometimes appears when I just open Calc or when I try to move the window. The window appears often as a small line, as shown in the attachment of michael.vanderf...@gmail.com or as small rectangle. In both cases it cannot be often resized by using the mouse. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 68695] EDITING: Comments cannot be resized while editing - missing squares around the comment/note
https://bugs.documentfoundation.org/show_bug.cgi?id=68695 --- Comment #79 from joe --- Yeah sorry folks, not to look a gift horse in the mouth, but it's ridiculous that this has not worked for so long -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153515] Incorrect handling of FullScreen mode (Writer and Calc) parsing ooSetupFactoryWindowAttributes, LO module jumps to 0, 0 position on relaunch
https://bugs.documentfoundation.org/show_bug.cgi?id=153515 V Stuart Foote changed: What|Removed |Added Whiteboard| QA:needsComment| Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153826] New: PROBLEM W/ CREATED FIELD
https://bugs.documentfoundation.org/show_bug.cgi?id=153826 Bug ID: 153826 Summary: PROBLEM W/ CREATED FIELD Product: LibreOffice Version: unspecified Hardware: PowerPC OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dav...@yahoo.com Using libreoffice v 7.4.5.1 on windows 11, found a bug. The created value in file / properties displays as 00/00/, 00:00:00 Wile the corresponding field produces " " i.e. nothing. But other apps do Show a valid date, e.g. Windows file explorer: 1/27/2023 6:23 pm. This is one of two files that show this behavior -- but I have not done an exhaustive search. -R. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150236] Does not open full screen, ooSetupFactoryWindowAttributes not being filled ( steps in comment 21 ) ( LibreOffice 7.4 only )
https://bugs.documentfoundation.org/show_bug.cgi?id=150236 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3515 -- You are receiving this mail because: You are the assignee for the bug.
