[Libreoffice-bugs] [Bug 151715] Tabbed UI: opening a read-only file (XLS or XLSX from mail) and switching to edit, buttons remain disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=151715 Buovjaga changed: What|Removed |Added URL|https://www.myexamcollectio | |n.com/DES-4122-vce-question | |s.htm | Status|VERIFIED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149783] FILESAVE: ODT: xml:id attribute missing from numbered lists
https://bugs.documentfoundation.org/show_bug.cgi?id=149783 Buovjaga changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |NOTABUG --- Comment #8 from Buovjaga --- Would have been nice to get a reply to (In reply to Miklos Vajna from comment #4) > Are you aware of any cases where that xml:id is referenced, but we don't > write it? But let's close as notabug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154038] UI: Wrong line spacing value in sidebar properties editor
https://bugs.documentfoundation.org/show_bug.cgi?id=154038 --- Comment #5 from Jim Raykowski --- It seems impress and writer require different stuff for calculating fixed line spacing values. Here is a patch that seems to produce expected values for both: https://gerrit.libreoffice.org/c/core/+/154665 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156362] FILEOPEN PPTX: connector lines show much thinner / fainter than in Office 365
https://bugs.documentfoundation.org/show_bug.cgi?id=156362 --- Comment #7 from Gerald Pfeifer --- (In reply to Stéphane Guillou (stragu) from comment #5) > Was the file created in Office 365? If so, what is the width setting > used for such a line? It's (part of) an older file I got from a third party who definitely created it using Microsoft Office (more likely on a Mac than Windows). > And you said "vertical" but I assume you meant "horizontal"? Yes, those horizontal lines. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156394] DES-4122 Exam Vce Questions
https://bugs.documentfoundation.org/show_bug.cgi?id=156394 myexamcollection changed: What|Removed |Added URL||https://www.myexamcollectio ||n.com/DES-4122-vce-question ||s.htm -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156394] New: DES-4122 Exam Vce Questions
https://bugs.documentfoundation.org/show_bug.cgi?id=156394 Bug ID: 156394 Summary: DES-4122 Exam Vce Questions Product: Document Liberation Project Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: wahici3...@nmaller.com For those getting ready to take the DES-4122 certification test, https://www.myexamcollection.com/DES-4122-vce-questions.htm are an invaluable resource. These practise tests are made to give students access to actual exam questions and scenarios so they may prepare and become familiar with the structure and subject matter of the real examination. Candidates can evaluate their knowledge, pinpoint areas that need work, and increase their confidence before the exam day by using the DES-4122 Exam Dumps. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151715] Tabbed UI: opening a read-only file (XLS or XLSX from mail) and switching to edit, buttons remain disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=151715 myexamcollection changed: What|Removed |Added URL||https://www.myexamcollectio ||n.com/DES-4122-vce-question ||s.htm -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156392] Bugzilla
https://bugs.documentfoundation.org/show_bug.cgi?id=156392 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org Status|UNCONFIRMED |RESOLVED Resolution|--- |MOVED --- Comment #1 from Buovjaga --- Requests about Bugzilla should either be filed to the upstream bug tracker https://bugzilla.mozilla.org/ (Product: Bugzilla) or to our Redmine: https://wiki.documentfoundation.org/QA/BugReport#Not_all_bugs_go_to_Bugzilla -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156393] Bugzilla
https://bugs.documentfoundation.org/show_bug.cgi?id=156393 Buovjaga changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||ilmari.lauhakangas@libreoff ||ice.org Resolution|--- |MOVED --- Comment #2 from Buovjaga --- Requests about Bugzilla should either be filed to the upstream bug tracker https://bugzilla.mozilla.org/ (Product: Bugzilla) or to our Redmine: https://wiki.documentfoundation.org/QA/BugReport#Not_all_bugs_go_to_Bugzilla -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155270] [ Calc - 7.5.3.2 (X86_64) / LibreOffice Community ] [ 3x issues identified while using Pivot table, 2x EDITING / FORMATTING and 1x UI ]
https://bugs.documentfoundation.org/show_bug.cgi?id=155270 --- Comment #6 from ady --- (In reply to James from comment #5) > What does PT mean in this context? Lets assume it is a Pivot Table, and that the request is to attach an ods file that includes a Pivot Table in order for others to review the steps, the results, and then try to replicate the problem(s). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 156369] Tripple-Clicking causes jumping to the end of paragraph.
https://bugs.documentfoundation.org/show_bug.cgi?id=156369 V Stuart Foote changed: What|Removed |Added Ever confirmed|1 |0 Status|NEW |UNCONFIRMED --- Comment #4 from V Stuart Foote --- Not a bug, it is and enhancement request under UX review. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 156369] Tripple-Clicking causes jumping to the end of paragraph.
https://bugs.documentfoundation.org/show_bug.cgi?id=156369 V Stuart Foote changed: What|Removed |Added Ever confirmed|1 |0 Status|NEW |UNCONFIRMED --- Comment #4 from V Stuart Foote --- Not a bug, it is and enhancement request under UX review. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148828] FILEOPEN PPTX text box padding is too large in SmartArt
https://bugs.documentfoundation.org/show_bug.cgi?id=148828 Aron Budea changed: What|Removed |Added Attachment #179812|application/zip |application/vnd.openxmlform mime type||ats-officedocument.presenta ||tionml.presentation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148828] FILEOPEN PPTX text box padding is too large in SmartArt
https://bugs.documentfoundation.org/show_bug.cgi?id=148828 Aron Budea changed: What|Removed |Added OS|Windows (All) |All CC||aron.bu...@gmail.com Hardware|x86-64 (AMD64) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155270] [ Calc - 7.5.3.2 (X86_64) / LibreOffice Community ] [ 3x issues identified while using Pivot table, 2x EDITING / FORMATTING and 1x UI ]
https://bugs.documentfoundation.org/show_bug.cgi?id=155270 --- Comment #5 from James --- >What you are trying to do?, please add the PT to the file. At the time of submitting the bug report, I had a collection of dates that were not being converted to ISO 8601 seemingly even after removing ' from the input. >please add the PT to the file. What does PT mean in this context? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156376] Pressing F1 while hovering a menu entry does not work in gtk3 or kf5
https://bugs.documentfoundation.org/show_bug.cgi?id=156376 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #2 from Michael Weghorn --- (In reply to Rafael Lima from comment #0) > I believe it should work in all backends. Is this fixable in gtk3 and kf5? gtk3 and kf5 are using native Gtk/Qt menus, so making this work might require hooking into their key event handling, but should probably be doable. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153131] Copy causes Calc to Freeze on Windows 11
https://bugs.documentfoundation.org/show_bug.cgi?id=153131 --- Comment #28 from ysui2...@gmail.com --- I can't reproduce this with windows 11 Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156393] Bugzilla
https://bugs.documentfoundation.org/show_bug.cgi?id=156393 --- Comment #1 from James --- Created attachment 188487 --> https://bugs.documentfoundation.org/attachment.cgi?id=188487=edit screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156393] New: Bugzilla
https://bugs.documentfoundation.org/show_bug.cgi?id=156393 Bug ID: 156393 Summary: Bugzilla Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: user2...@proton.me Description: It would be useful if CloneThisBug, could have options under it to detail how in-depth it will be. As it currently only seems to capture the Component and hardware inputs. Steps to Reproduce: N/A Actual Results: N/A 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 156316] Position and Size command is not working properly in Writer RC1.
https://bugs.documentfoundation.org/show_bug.cgi?id=156316 --- Comment #2 from ysui2...@gmail.com --- I can't reproduce this with windows11, Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156370] Assigning a paragraph style causes the cursor jumps back to section title
https://bugs.documentfoundation.org/show_bug.cgi?id=156370 Buovjaga changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #2 from Buovjaga --- Works without jumps here as well. Please copy and paste to a comment the info from your Help - About dialog by clicking the copy button. NixOS Version: 7.5.4.1 (X86_64) / LibreOffice Community Build ID: 50(Build:1) CPU threads: 16; OS: Linux 6.3; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156392] New: Bugzilla
https://bugs.documentfoundation.org/show_bug.cgi?id=156392 Bug ID: 156392 Summary: Bugzilla Product: LibreOffice Version: unspecified Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: user2...@proton.me Description: It would be more ideal if the "Severity" menu was a set of text boxes rather than a drop down menu. Steps to Reproduce: N/A Actual Results: N/A 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 156318] LibreOffice hangs when floating table tries to break
https://bugs.documentfoundation.org/show_bug.cgi?id=156318 --- Comment #5 from ysui2...@gmail.com --- I can't reproduce this with Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156391] Writer | Mail Merge Error
https://bugs.documentfoundation.org/show_bug.cgi?id=156391 --- Comment #1 from James --- Created attachment 188486 --> https://bugs.documentfoundation.org/attachment.cgi?id=188486=edit screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156391] New: Writer | Mail Merge Error
https://bugs.documentfoundation.org/show_bug.cgi?id=156391 Bug ID: 156391 Summary: Writer | Mail Merge Error Product: LibreOffice Version: 5.4.6.2 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: user2...@proton.me Description: Unable to send an email via Mail Merge, it would be ideal if I could have an option to delegate the email transmission aspects to my Mail Transfer Agent (MTA) which in this case is Thunderbird. Steps to Reproduce: 0. Write up a mail merge "file" with an associated contact database. 1. Click on "Send Mail Messages" 2. Select "To: Email Address" 3. If desired, enter a subject line. 4. Select "Send as: Plain Text" 5. Click on "Send Documents" Actual Results: A redacted error log is included below. : (550, b'5.7.1 Authentication is required to use this service', 'EMAIL'), traceback follows File "C:\Program Files\LibreOffice\program\mailmerge.py", line 262, in sendMailMessage self.server.sendmail(sendermail, truerecipients, msg.as_string()) File "C:\Program Files\LibreOffice\program\python-core-3.8.16\lib\smtplib.py", line 885, in sendmail raise SMTPSenderRefused(code, resp, from_addr) Expected Results: Email is sent Reproducible: Always User Profile Reset: No Additional Info: Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-NZ (en_NZ); UI: en-US Calc: CL threaded Tools -> Options -> Libre Office Writer -> Mail Merge Email -> Test Settings (screenshot will be attached.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154758] Changing the resolution computes the new size incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=154758 --- Comment #5 from ysui2...@gmail.com --- I can't reproduce this. It doesn't allow me to set it to 300*300 Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156390] Writer | How to edit an expression within a table is not obvious.
https://bugs.documentfoundation.org/show_bug.cgi?id=156390 --- Comment #1 from James --- Created attachment 188485 --> https://bugs.documentfoundation.org/attachment.cgi?id=188485=edit Example -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156390] New: Writer | How to edit an expression within a table is not obvious.
https://bugs.documentfoundation.org/show_bug.cgi?id=156390 Bug ID: 156390 Summary: Writer | How to edit an expression within a table is not obvious. Product: LibreOffice Version: 5.4.6.2 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: user2...@proton.me Description: N/A Steps to Reproduce: 0. Open a fresh document. 1. Create a new table. 2. Reference a row within an expression e.g. = + 1 which correctly renders 2. Actual Results: Hovering on shows me the formula, = + 1 Expected Results: There is some means to edit for the formula outside of re-creation. Reproducible: Always User Profile Reset: No Additional Info: Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-NZ (en_NZ); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156389] Writer | Header and the entire document does not support Table variables.
https://bugs.documentfoundation.org/show_bug.cgi?id=156389 --- Comment #1 from James --- Created attachment 188484 --> https://bugs.documentfoundation.org/attachment.cgi?id=188484=edit example -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156389] New: Writer | Header and the entire document does not support Table variables.
https://bugs.documentfoundation.org/show_bug.cgi?id=156389 Bug ID: 156389 Summary: Writer | Header and the entire document does not support Table variables. Product: LibreOffice Version: 5.4.6.2 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: user2...@proton.me Description: (0) - Header and the entire document does not support Table variables. Steps to Reproduce: (0) 0. Open a fresh document. 1. Create a table with at least two rows (example will be attached. 2. Create a header with a valid reference which works from within side another table. e.g which is simply 1. Actual Results: (0) Header "Version: " is only recognized within . Expected Results: (0) Header "Version: 1.0.0" 1.0.0 Reproducible: Always User Profile Reset: No Additional Info: Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-NZ (en_NZ); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156351] border error when docx floating table breaks to two pages because of caption above
https://bugs.documentfoundation.org/show_bug.cgi?id=156351 --- Comment #5 from ysui2...@gmail.com --- I didn't reproduce the bug successfully. After I inserted the caption, the table moved down slightly. It was a little bit out of the border of the first page but still on the first page. It didn't go to the second page. Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156388] New: Calc | "Protect Spreadsheet structure" input does not persist past the current session.
https://bugs.documentfoundation.org/show_bug.cgi?id=156388 Bug ID: 156388 Summary: Calc | "Protect Spreadsheet structure" input does not persist past the current session. Product: LibreOffice Version: 5.4.6.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: user2...@proton.me Description: "Protect Spreadsheet structure" input does not persist past the current session. Steps to Reproduce: 0. Create a new worksheet. 1. Top options menu -> Tools 2. Click on "Protect Spreadsheet structure" 3. Supply an input. A "blank" password is a valid trigger. 4. Save as ".xlsx" and then exit. 6. Re-open and repeat step 1 to see that "Protect Spreadsheet structure" has not been saved. Actual Results: "Protect Spreadsheet structure" input does not persist past the current session. Expected Results: "Protect Spreadsheet structure" input persists past the current session. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-NZ (en_NZ); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156366] Writer: Double-lined charaters do not wrap lines correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=156366 ysui2...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from ysui2...@gmail.com --- I reproduced this bug successfully. Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 --- Comment #60 from slotxowin --- สำหรับใครที่ยังไม่รู้จัก สล็อตโชคชนะเป็นเกมคาสิโนออนไลน์ที่ได้รับความนิยมอย่างแพร่หลาย กลุ่มผู้คนที่สนใจกับการเสี่ยงโชคและความตื่นเต้นมักจะหันมาสนใจเกมนี้ สล็อตโชคชนะนั้นเป็นเกมที่มีความง่ายในการเล่น คุณไม่จำเป็นต้องมีทักษะพิเศษหรือความรู้พิเศษในการเล่นเกมคาสิโน ทำให้เป็นที่นิยมสำหรับทุกช่วงวัย นักเล่นคนหนุ่มสาวคนใหม่หัดเล่น หรือนักพนันที่เก่งควบคู่กับกาลเวลาว่างๆ ก็เป็นอย่างดี https://slotxowin.org/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149783] FILESAVE: ODT: xml:id attribute missing from numbered lists
https://bugs.documentfoundation.org/show_bug.cgi?id=149783 --- Comment #7 from Michelle --- Apologies for the delay. We ended up implementing a workaround for this behavior in our system to meet our requirements. Please feel free to close this one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136745] File names with spaces cant be downloaded
https://bugs.documentfoundation.org/show_bug.cgi?id=136745 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 156164] MCGR 3D renders border with wrong color
https://bugs.documentfoundation.org/show_bug.cgi?id=156164 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 156382] table border display at the top of pages
https://bugs.documentfoundation.org/show_bug.cgi?id=156382 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152621] The formula editor does not render vectors properly
https://bugs.documentfoundation.org/show_bug.cgi?id=152621 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 156382] table border display at the top of pages
https://bugs.documentfoundation.org/show_bug.cgi?id=156382 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152621] The formula editor does not render vectors properly
https://bugs.documentfoundation.org/show_bug.cgi?id=152621 --- Comment #4 from QA Administrators --- Dear jdb1o...@gmail.com, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151062] The UI flickering and lagging in GTK3. The Page following scroll from style format when it scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=151062 --- Comment #5 from QA Administrators --- Dear sidanan926, 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 152428] inserting an image into a writer file prevents further editing of the document
https://bugs.documentfoundation.org/show_bug.cgi?id=152428 --- Comment #6 from QA Administrators --- Dear Steve Garry, 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 151062] The UI flickering and lagging in GTK3. The Page following scroll from style format when it scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=151062 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 109232] [META] Special character dialog and toolbar group button bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109232 Bug 109232 depends on bug 148487, which changed state. Bug 148487 Summary: when you try to insert a special character, Libre Office closes https://bugs.documentfoundation.org/show_bug.cgi?id=148487 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148388] LibreOffice (either Writer, or Calc, etc.) side panel flicker behaviour on Linux AMD64 (GFX stack or OpenGL issue)
https://bugs.documentfoundation.org/show_bug.cgi?id=148388 --- Comment #4 from QA Administrators --- Dear Dubravko Mario Radic, 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 148487] when you try to insert a special character, Libre Office closes
https://bugs.documentfoundation.org/show_bug.cgi?id=148487 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 148487] when you try to insert a special character, Libre Office closes
https://bugs.documentfoundation.org/show_bug.cgi?id=148487 --- Comment #10 from QA Administrators --- Dear Kenou, 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 148388] LibreOffice (either Writer, or Calc, etc.) side panel flicker behaviour on Linux AMD64 (GFX stack or OpenGL issue)
https://bugs.documentfoundation.org/show_bug.cgi?id=148388 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 147173] Impress Presentation Crash when I increase the font size too fast in a >10mb document
https://bugs.documentfoundation.org/show_bug.cgi?id=147173 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 147173] Impress Presentation Crash when I increase the font size too fast in a >10mb document
https://bugs.documentfoundation.org/show_bug.cgi?id=147173 --- Comment #5 from QA Administrators --- Dear desolation0451, 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 153123] Change smtp password in LO-Writer for mail merge e-mail
https://bugs.documentfoundation.org/show_bug.cgi?id=153123 --- Comment #2 from QA Administrators --- Dear MickGe, 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 153027] LibreOffice Writer arbitrarily inserts first clipboard entry when using mouse wheel to scroll through document.
https://bugs.documentfoundation.org/show_bug.cgi?id=153027 --- Comment #3 from QA Administrators --- Dear Doug, 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 149783] FILESAVE: ODT: xml:id attribute missing from numbered lists
https://bugs.documentfoundation.org/show_bug.cgi?id=149783 --- Comment #6 from QA Administrators --- Dear Michelle, 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 151500] very very slow on qt 5.15.6
https://bugs.documentfoundation.org/show_bug.cgi?id=151500 --- Comment #6 from QA Administrators --- Dear kde-yyds, 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 149060] CONFIGURATION: View > Toolbars > Customize... causes crash, initiates document recovery
https://bugs.documentfoundation.org/show_bug.cgi?id=149060 --- Comment #9 from QA Administrators --- Dear bugzilla.irg220228, 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 144983] Wrong umlaut behaviour in linux
https://bugs.documentfoundation.org/show_bug.cgi?id=144983 --- Comment #7 from QA Administrators --- Dear software.v9onn, 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 142123] Charts/Graph in Calc don't allow full Text Formating of Legends and Axes Titles.
https://bugs.documentfoundation.org/show_bug.cgi?id=142123 --- Comment #2 from QA Administrators --- Dear prashantchanchal...@gmail.com, 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 96321] FORMATTING: in imported doc or docx, rendered underlines lines (top/bottom border) do not appear evenly spaced
https://bugs.documentfoundation.org/show_bug.cgi?id=96321 --- Comment #9 from QA Administrators --- Dear Marco Ciampa, 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 92936] FILESAVE: HSQLDB:Inserting big image in a form destroys all input since last opening of *.odb-file
https://bugs.documentfoundation.org/show_bug.cgi?id=92936 --- Comment #23 from QA Administrators --- Dear Robert Großkopf, 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 143263] A cropped animating GIF image is slightly jumping around in presentation mode
https://bugs.documentfoundation.org/show_bug.cgi?id=143263 --- 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 143238] Numbering lost after cut/paste in the same document
https://bugs.documentfoundation.org/show_bug.cgi?id=143238 --- Comment #4 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143262] GIF image stops animating in edit mode after cropping (does work in presentation mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=143262 --- Comment #4 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143179] Field in Dialog: Color of background isn't shown when executing dialog (Linux gtk3 or kf5)
https://bugs.documentfoundation.org/show_bug.cgi?id=143179 --- Comment #5 from QA Administrators --- Dear Robert Großkopf, 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 135904] Spelling correct: Ignore word has no undo step
https://bugs.documentfoundation.org/show_bug.cgi?id=135904 --- Comment #7 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 143150] Brackets [] for bibliography reference lost on DOCX import (fine with DOC)
https://bugs.documentfoundation.org/show_bug.cgi?id=143150 --- Comment #4 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122614] Regarding an edited style, while AutoUpdate is checked, it is not applied to new style created using method's steps 'New Style from Selection', 'New Style...'.
https://bugs.documentfoundation.org/show_bug.cgi?id=122614 --- Comment #6 from QA Administrators --- Dear ricky.tigg, 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 121132] Draw and Impress default templates clobber each other
https://bugs.documentfoundation.org/show_bug.cgi?id=121132 --- Comment #10 from QA Administrators --- Dear wpeaton4, 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 107913] Text animation order wrong for hyperlinked text
https://bugs.documentfoundation.org/show_bug.cgi?id=107913 --- Comment #9 from QA Administrators --- Dear Timur, 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 105367] FILESAVE Bibliography not saved properly in doc and docx
https://bugs.documentfoundation.org/show_bug.cgi?id=105367 --- Comment #24 from QA Administrators --- Dear Kamil Páral, 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 156387] New: Menus Not Displayed on Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=156387 Bug ID: 156387 Summary: Menus Not Displayed on Wayland Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: milton...@gmail.com OS: Manjaro KDE Plasma 5.27.6 Libreoffice: 7.5.4.2 Flatpak Global Menus are not displaying in LO and Plasma, leaving LO without any menus. Specifically in Calc. Had to revert to X11 and they displayed normally. Tried the Manjaro Gnome Desktop and the menus displayed as expected, although as a standard menu bar in the window of the application and not as global menus as done in Plasma. I have also seen this behavior using the official repository LO installation. (Reason for using the flatpak was to solve the issue with LO taskbar application icons not displayed in Wayland and KDE with the official repository installation. The flatpak did correct this issue, by the way.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156369] Tripple-Clicking causes jumping to the end of paragraph.
https://bugs.documentfoundation.org/show_bug.cgi?id=156369 --- Comment #3 from vicxp0518 --- (In reply to V Stuart Foote from comment #1) > Don't see the point, if you are making a selection of a text paragraph (with > quad-click; triple selects sentence, double selects single word) are you > editing or not? > > I prefer to see the end of a selection that I've just made and for the view > port to follow the position of the edit cursor, and not to retain the view > port with the edit cursor positioned off screen. > > And, this is consistent. If you select a sentence that extends out of > current view the cursor advances to the end of the sentence and the view > will also adjust. > > Paragraph selection does the same, advancing view port to track the edit > cursor--that is preferred for effective editing UX. > > IMHO => WF Lol exactly I've neither no idea why I love to triple-click at something freqently, especially during *deep thinking* between typing. This's true, the concentration works as far as me feel so. The *deep thinking* is the key reason why I would recommend this - you simply don't want your text fly away while you are staring and brain parsing at it. Anyway, considering Word and Pages do hold screen position, maybe, just say, they've also realized this, too? That some users just love to select while reading? Something phsycological? While another point, I don't think it's very neccessary to scroll to the end of the paragraph while user triple clicking at a paragraph. What will they actually do next? Applying format? Deleting it? It'll be better WYSIWIG if screen holds its original position, isn't it? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-ux-advise] [Bug 156369] Tripple-Clicking causes jumping to the end of paragraph.
https://bugs.documentfoundation.org/show_bug.cgi?id=156369 --- Comment #3 from vicxp0518 --- (In reply to V Stuart Foote from comment #1) > Don't see the point, if you are making a selection of a text paragraph (with > quad-click; triple selects sentence, double selects single word) are you > editing or not? > > I prefer to see the end of a selection that I've just made and for the view > port to follow the position of the edit cursor, and not to retain the view > port with the edit cursor positioned off screen. > > And, this is consistent. If you select a sentence that extends out of > current view the cursor advances to the end of the sentence and the view > will also adjust. > > Paragraph selection does the same, advancing view port to track the edit > cursor--that is preferred for effective editing UX. > > IMHO => WF Lol exactly I've neither no idea why I love to triple-click at something freqently, especially during *deep thinking* between typing. This's true, the concentration works as far as me feel so. The *deep thinking* is the key reason why I would recommend this - you simply don't want your text fly away while you are staring and brain parsing at it. Anyway, considering Word and Pages do hold screen position, maybe, just say, they've also realized this, too? That some users just love to select while reading? Something phsycological? While another point, I don't think it's very neccessary to scroll to the end of the paragraph while user triple clicking at a paragraph. What will they actually do next? Applying format? Deleting it? It'll be better WYSIWIG if screen holds its original position, isn't it? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-bugs] [Bug 156386] New: External Linked Files Unable to Break Link
https://bugs.documentfoundation.org/show_bug.cgi?id=156386 Bug ID: 156386 Summary: External Linked Files Unable to Break Link Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: milton...@gmail.com Breaking a link in Calc does not work. Behavior 1. Open a Calc file with a linked file 2. Allow updating the file when the security warning appears 3. Menu > Edit > Links to External Files... 4. Click "Break Link" 5. Close the dialog box 6. Save and close the file 7. Reopen the file 8. Notice the external link is still linked Expected Behavior That when the external file link is broken, that the file link be broken and written to file when the file is saved. The user must use Excel to remove linked files. Not ideal. Literally, this bug has been around for years. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 70618] Rows modified by spellchecking function
https://bugs.documentfoundation.org/show_bug.cgi?id=70618 Terrence Enger changed: What|Removed |Added Keywords||dataLoss --- Comment #14 from Terrence Enger --- I still see the problem in LibreOffice delivered with debian-sid: Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 8; OS: Linux 6.3; UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Debian package version: 4:7.5.5~rc2-1 Calc: threaded I am adding keyword dataLoss. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: cui/source
cui/source/options/optsave.cxx |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 896f19764abf9301169bf9631877bdae075edde4
Author: Justin Luth
AuthorDate: Wed Jul 19 20:16:40 2023 -0400
Commit: Justin Luth
CommitDate: Thu Jul 20 03:26:49 2023 +0200
tdf#156308 autosave: re-listening to config, no restart requests
The reason the restart request was added was because of the
broken config. Now that the config is correct again,
the listener notices the enable change and turns AutoSave on/off
immediately. So there is no need to prompt the user to restart
after modifying the setting in Tools - Options.
Change-Id: I0c775964ce5d9f860b0ce320db86d8db7226a489
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/154663
Tested-by: Jenkins
Reviewed-by: Justin Luth
diff --git a/cui/source/options/optsave.cxx b/cui/source/options/optsave.cxx
index b60fe8da2594..e63bab701926 100644
--- a/cui/source/options/optsave.cxx
+++ b/cui/source/options/optsave.cxx
@@ -281,7 +281,7 @@ bool SvxSaveTabPage::FillItemSet( SfxItemSet* rSet )
{
rSet->Put( SfxBoolItem( SID_ATTR_AUTOSAVE,
m_xAutoSaveCB->get_active() ) );
-bModified = bRequestRestart = true;
+bModified = true;
}
if ( m_xWarnAlienFormatCB->get_state_changed_from_saved() )
{
[Libreoffice-bugs] [Bug 117930] FILESAVE; Error while exporting document to XHTML
https://bugs.documentfoundation.org/show_bug.cgi?id=117930 --- Comment #16 from Terrence Enger --- In LibreOffice delivered with debian sid ... Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 8; OS: Linux 6.3; UI render: default; VCL: gtk3 Locale: en-CA (en_CA.UTF-8); UI: en-US Debian package version: 4:7.5.5~rc2-1 Calc: threaded I still receive msgbox Error saving the document docx1: General Error. General input/output error. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155630] Deduplicate copy/paste code
https://bugs.documentfoundation.org/show_bug.cgi?id=155630 --- Comment #11 from Dave Gilbert --- Here's some notes from potential dupes I'd found if someone else would like to attack them. Note you probably need to check these things with people who know the relevant code, this is just me noticing things: a) Import GDI/PDF svx/source/svdraw/svdfmtf.cxx and svx/source/svdraw/svdpdf.cxx have ImpSdrGDIMetaFileImport::InsertObj and ImpSdrPdfImport::InsertObj which are big and almost identical. It feels like you could make a base class and share large chunks of those two. You can trigger it by inserting a pdf into a draw document, right clicking and selecting 'break'. My only worry is that this PDF import seems entirely separate from the loading PDF files at startup; so maybe that['s what really needs merging - not dug yet. b) Unicode character tools in sw/source/core/text/portlay.cxx and editeng/source/editeng/impedit3.cxx These have been explicitly copied between them; I wonder if they can be shared? (In particular all the isBehChar and related stuff). -- You are receiving this mail because: You are the assignee for the bug.
Re: Build failed inside skia module on openSUSE 15.4-x64 with skia m116
Hi Noel, because I got no response to my answer of your questions I'd like to ask if you need some further information to work on the issue. Regards, Andreas Am 16.07.23 um 20:35 schrieb Andreas Mantke: Hi Noel, Am 16.07.23 um 20:28 schrieb Noel Grandin: what kind of build is this? debug/release? and what version of gcc? rpm -qa | grep gcc gave me: gcc7-c++-7.5.0+r278197-4.30.1.x86_64 gcc-info-7-3.9.1.x86_64 gcc-c++-7-3.9.1.x86_64 gcc-7-3.9.1.x86_64 libgcc_s1-12.3.0+git1204-15.1.10.1.x86_64 libstdc++6-devel-gcc7-7.5.0+r278197-4.30.1.x86_64 gcc7-7.5.0+r278197-4.30.1.x86_64 gcc7-info-7.5.0+r278197-4.30.1.noarch libgcc_s1-32bit-12.3.0+git1204-15.1.10.1.x86_64 It's the build from LibreOffice source branch master. I run a regular build without debug symbols. Regards, Andreas -- ## Free Software Advocate ## Plone add-on developer ## My blog:http://www.amantke.de/blog
[Libreoffice-bugs] [Bug 156361] Skia regression: semi-transparent .svg in .odp fails to render
https://bugs.documentfoundation.org/show_bug.cgi?id=156361 --- Comment #9 from Patrick Luby --- (In reply to Noel Grandin from comment #8) > which simplifies to > > r = 1 - s - sa*d > > which is not something Skia has a SkBlendMode for, so no easy fix. Your formula looks much closer to what I could come up with. Also, I realized my proposal in https://bugs.documentfoundation.org/show_bug.cgi?id=156361#c6 won't work since a VirtualDevice is initially filled with opaque white (which renders as white) and its AlphaMask is also filled with opaque white (which makes the VirtualDevice transparent). So, the alpha channel in the VirtualDevice is immediately out of sync with its AlphaMask. So, my understanding is that the AlphaMask starts as all white (transparent) and reflects the cumulatively drawn areas as gray or black. I haven't been able to come up with a blending algorithm for this, but it was what I was trying to do in https://bugs.documentfoundation.org/show_bug.cgi?id=156361#c4. Effectively, I think I want to repeat the drawing to the VirtualDevice but draw all white instead of the bitmap. I no longer think that all of the copying and inverting in that comment are needed. So, below is what I am thinking of replacing mpAlphaVDev->BlendBitmap(aTR, rAlpha) with: mpAlphaVDev->mpGraphics->BlendAlphaMasks(aTR, /* no bitmap */, *pSalAlphaBmp, *pSalAlphaBmp2, *this)) BlendAlphaMasks() would be basically be a copy of the code block in BlendAlphaBitmap() at vcl/skia/gdiimpl.cxx:1326 with the following changes: 1. Fill the surface with SK_ColorBLACK before blending 2. Blend the alpha masks the same, no change there 3. Blend the blended alpha masks with SK_ColorWHITE instead of a bitmap 4. Invert the surface with kDifference to get black == opaque and white == transparent Thoughts? I can try coding this in the next couple of days and see if it fixes anything. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156337] PDF export security tab is disabled and does not tell what is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=156337 Henrik Gebauer changed: What|Removed |Added Severity|normal |enhancement --- Comment #6 from Henrik Gebauer --- Oh.. Now I see the message I was looking for is right in the screenshot I posted (-> no encryption because of PDF/A). But the message is grayed out so it never appeared to me it could contain useful information. I will reduce the importance of this bug report to "enhancement". I suggest to enhance the message to make it more visible. Two suggestions are in the modified screenshots. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156337] PDF export security tab is disabled and does not tell what is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=156337 --- Comment #5 from Henrik Gebauer --- Created attachment 188483 --> https://bugs.documentfoundation.org/attachment.cgi?id=188483=edit proposed change (2) or a combination of both suggestions -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156337] PDF export security tab is disabled and does not tell what is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=156337 --- Comment #4 from Henrik Gebauer --- Created attachment 188482 --> https://bugs.documentfoundation.org/attachment.cgi?id=188482=edit proposed change (1) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Bug 107237 depends on bug 156098, which changed state. Bug 156098 Summary: Writer: "Insert - Page number" button missing in Tabbed https://bugs.documentfoundation.org/show_bug.cgi?id=156098 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156098] Writer: "Insert - Page number" button missing in Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=156098 Justin L changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Justin L --- It is in 24.2, but I won't backport to 7.6 because the icon is still missing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: sw/uiconfig
sw/uiconfig/swriter/ui/notebookbar.ui | 57 -- 1 file changed, 48 insertions(+), 9 deletions(-) New commits: commit e823cd380a2ad38cbc7598c7393752f6398cb24f Author: Justin Luth AuthorDate: Thu May 4 12:26:15 2023 -0400 Commit: Justin Luth CommitDate: Thu Jul 20 00:59:34 2023 +0200 tdf#86630 sw page number wizard: add to notebookbar layout tab I think putting this in layout makes the most sense, since Title page is already there, and these are all page style tasks. The other possible location is Insert. Title page is here also. I'd suggest putting it under Title page, and moving Fields above Section Change-Id: I6f432af3726b44b4fb7554fc73e343959cfe2d0d Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151398 Reviewed-by: Justin Luth Tested-by: Jenkins diff --git a/sw/uiconfig/swriter/ui/notebookbar.ui b/sw/uiconfig/swriter/ui/notebookbar.ui index adbae8224cd2..f902206817c0 100644 --- a/sw/uiconfig/swriter/ui/notebookbar.ui +++ b/sw/uiconfig/swriter/ui/notebookbar.ui @@ -6261,6 +6261,45 @@ + +True +True +center +True +both +True +3 + + +True +.uno:PageNumberWizard + + +False +True + + + + +False +True +1 + + + + +False +True +7 + + + + +True +False +center +True + True False @@ -6316,7 +6355,7 @@ False True -1 +0
[Libreoffice-bugs] [Bug 147938] Crash in: msvcp140.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=147938 --- Comment #16 from Gabor Kelemen (allotropia) --- The crashing on open started with https://git.libreoffice.org/core/+/4532845e22c10f252840887e55002307227b2390 author Michael Stahl Thu Jul 26 14:12:53 2018 +0200 committer Michael Stahl Wed Sep 19 10:18:20 2018 +0200 sw_redlinehide_2: add *another* flag to DocumentRedlineManager Before this the conversion back to table (last step of comment #14) was successful. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156337] PDF export security tab is disabled and does not tell what is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=156337 --- Comment #3 from Henrik Gebauer --- Thank you for the reply. But the "Set Passwords..." button is disabled as well (see screenshot). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156337] PDF export security tab is disabled and does not tell what is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=156337 --- Comment #2 from Henrik Gebauer --- Created attachment 188481 --> https://bugs.documentfoundation.org/attachment.cgi?id=188481=edit screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156380] FORMATTING: images in cells should autoshrink to cell size, same as Excel behavior
https://bugs.documentfoundation.org/show_bug.cgi?id=156380 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #1 from Regina Henschel --- Please attach a small file which has this problem. That makes it easier to investigate the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150308] Track changes: Top border disappears when deleting top table row with track changes record ON and show OFF
https://bugs.documentfoundation.org/show_bug.cgi?id=150308 --- Comment #4 from Commit Notification --- László Németh committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/0eb44f8c6ad764d8c2d044603f8f2aa84e3c7892 tdf#150308 sw: fix missing top table border after hidden table rows It will be available in 7.6.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150308] Track changes: Top border disappears when deleting top table row with track changes record ON and show OFF
https://bugs.documentfoundation.org/show_bug.cgi?id=150308 Commit Notification changed: What|Removed |Added Whiteboard|target:24.2.0 |target:24.2.0 ||target:7.6.0.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'libreoffice-7-6' - sw/source
sw/source/core/layout/paintfrm.cxx |8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) New commits: commit 0eb44f8c6ad764d8c2d044603f8f2aa84e3c7892 Author: László Németh AuthorDate: Tue Jul 18 16:41:52 2023 +0200 Commit: László Németh CommitDate: Thu Jul 20 00:31:37 2023 +0200 tdf#150308 sw: fix missing top table border after hidden table rows First visible line of a table with preceding hidden deleted rows hid also the top border of the table, if the inner horizontal row borders drawn only by bottom-only borders (like in the default table style). Note: re-use an existing workaround to show the missing line, see commit 3a4b7c3555f2ffb4e89502bb04ff063d8c08f628 "fdo#39415: sw: fix collapsing border painting more:" Note: layout testing doesn't work, because of the missing calculation with the width of the enabled border of the row frame. Also there is a problem with metafile testing (empty meta file?). Change-Id: Ia8476a2ec592be1dc36e0ea71c10a71c257c29e0 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/154595 Tested-by: Jenkins Reviewed-by: László Németh (cherry picked from commit 379acb934164e673b708d0f3ec6b3ec046c8d73f) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/154612 Tested-by: László Németh diff --git a/sw/source/core/layout/paintfrm.cxx b/sw/source/core/layout/paintfrm.cxx index 47e56b390712..0a43dbb587ab 100644 --- a/sw/source/core/layout/paintfrm.cxx +++ b/sw/source/core/layout/paintfrm.cxx @@ -2804,6 +2804,8 @@ void SwTabFramePainter::FindStylesForLine( Point& rStartPoint, /** * Special case: #i9860# * first line in follow table without repeated headlines + * Special case: tdf#150308 + * first visible line of a table with preceding hidden deleted rows */ static bool lcl_IsFirstRowInFollowTableWithoutRepeatedHeadlines( SwTabFrame const& rTabFrame, SwFrame const& rFrame, SvxBoxItem const& rBoxItem) @@ -2812,7 +2814,11 @@ static bool lcl_IsFirstRowInFollowTableWithoutRepeatedHeadlines( dynamic_cast(rFrame.GetUpper()); return (pThisRowFrame && (pThisRowFrame->GetUpper() == ) -&& rTabFrame.IsFollow() +&& ( rTabFrame.IsFollow() +// tdf#150308 first table row isn't equal to the table row of the first +// row frame of the first table frame: there are invisible deleted rows +// in Hide Changes mode before the first visible table row +|| rTabFrame.GetTable()->GetTabLines().front() != pThisRowFrame->GetTabLine() ) && !rTabFrame.GetTable()->GetRowsToRepeat() && ( !pThisRowFrame->GetPrev() || static_cast(pThisRowFrame->GetPrev())
[Libreoffice-bugs] [Bug 147938] Crash in: msvcp140.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=147938 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com --- Comment #15 from Gabor Kelemen (allotropia) --- Went for another round of bibisect, started with this: https://git.libreoffice.org/core/+/f609eba8b979620dc8f1c4a47d710360f8aae9e6 author Michael Stahl Tue Oct 09 14:49:23 2018 +0200 committer Michael Stahl Thu Nov 15 15:09:58 2018 +0100 sw_redlinehide_3: convert even more SwAccessibleParagraph functions Before this even opening the example files crashed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155939] LibreOffice-7.5.4.2 Writer hangs when changing language of text
https://bugs.documentfoundation.org/show_bug.cgi?id=155939 Stéphane Guillou (stragu) changed: What|Removed |Added CC||j22...@gmail.com --- Comment #11 from Stéphane Guillou (stragu) --- *** Bug 156385 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 156385] crash when changing language of all text
https://bugs.documentfoundation.org/show_bug.cgi?id=156385 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- Thank you J22Gim. This is most likely bug 155939, which is fixed in 7.5.5. Please feel free to confirm that it does work in that new version (at the bottom of the page): https://www.libreoffice.org/download/download-libreoffice/ *** This bug has been marked as a duplicate of bug 155939 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153119] Crash on paste
https://bugs.documentfoundation.org/show_bug.cgi?id=153119 Stéphane Guillou (stragu) changed: What|Removed |Added Crash report or||["DelFullParaMoveFrames(SwD crash signature||oc&, SwUndRng const&, ||SwRedlineSaveDatas ||const&)"] CC||stephane.guillou@libreoffic ||e.org Version|7.6.0.0 alpha0+ |7.3.7.2 release --- Comment #5 from Stéphane Guillou (stragu) --- Adding crash signature for good measure. Crash report for 7.5.5.2: https://crashreport.libreoffice.org/stats/crash_details/e0ef61ce-4916-41f9-9d30-1f57c5cb1579 Also in 7.3.7.2: https://crashreport.libreoffice.org/stats/crash_details/dc369695-34ae-4912-aa5e-f72d55bdee7e -- You are receiving this mail because: You are the assignee for the bug.
Week #7 Report - GSoC 2023 - Search Field in Options
Hi all. > Summary of Week #7 Report - GSoC 2023 - "Search Field in Options" project - New patchsets submitted (patchsets 10 - 14): https://gerrit.libreoffice.org/c/core/+/152519 - String extraction location moved to workdir/UIOptions/* - Extracted files includes a lot of underscores ( _ ) that might block search functionality. To prevent this issue, all underscores were removed. - extraction works with $ make uioptions Thanks. -- Regards, Bayram Çiçek
[Libreoffice-bugs] [Bug 156385] crash when changing language of all text
https://bugs.documentfoundation.org/show_bug.cgi?id=156385 j22...@gmail.com changed: What|Removed |Added CC||j22...@gmail.com --- Comment #1 from j22...@gmail.com --- Created attachment 188480 --> https://bugs.documentfoundation.org/attachment.cgi?id=188480=edit debugging info This is the log file, generated by gdb -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156385] New: crash when changing language of all text
https://bugs.documentfoundation.org/show_bug.cgi?id=156385
Bug ID: 156385
Summary: crash when changing language of all text
Product: LibreOffice
Version: 7.5.4.2 release
Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: j22...@gmail.com
Description:
Writer crashes when I try to set all text to English.
I have a file (originally DOCX, saved as ODT) with 4-5 pages of text (Spanish
mixed with English). I want to set the language of the entire document to
English.
I can set 'selected text' and 'paragraph' to English, but when I try with "all
text", Writer hangs (and I have to kill it).
I tried debugging with GDB: weirdly, I can open the file and work otherwise
'normally', but when I try to open it using backtrace ('lowriter --backtrace')
Writer never really opens (although I see the border of a window with the title
of the file during a second before it crashes and disappears again).
This may mean I will need also guidance with debugging.
I attach the gdbtrace.log file.
Steps to Reproduce:
This happens when I try to set Enlish as language for All text via Tools >
Language > For all text > English.
- it happens only for this file (it works well with a brand-new ODT)
- it happens only for "all text" option. The "selected text" and "paragraph"
works fine.
Actual Results:
Also, when I try to debug (lowriter --backtrace) I can not reproduce the
problem because in this case Writer does not even start! BUT, there is no
problem if I start Writer in the 'normal' ways (eg lowriter from console or
Writer in my applications menu)
Expected Results:
Maybe I am doing something wrong with the debugging as well? What else can I do
to diagnose this?
Reproducible: Always
User Profile Reset: No
Additional Info:
Version: 7.5.4.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 4:7.5.4~rc2-0ubuntu0.22.04.1~lo1
Calc: threaded
--
You are receiving this mail because:
You are the assignee for the bug.
