[Bug 160053] LibreOfficePortable 7.6 crashes after switching to another window and afterwards returning to LOP - FILESAVE
https://bugs.documentfoundation.org/show_bug.cgi?id=160053 Naresh changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Naresh --- Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded Hi Ingo, I was unable to preproduce this error. Steps: Open a new Draw document create a 10 pages with images, clipart, text switch over to other windows and do some actions and come back after add a text in the document Result: I was able to add the text to the document. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160100] Callout COPY loses formatting, pasted position makes useless.
https://bugs.documentfoundation.org/show_bug.cgi?id=160100 --- Comment #6 from Naresh --- Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-IN (en_IN); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160100] Callout COPY loses formatting, pasted position makes useless.
https://bugs.documentfoundation.org/show_bug.cgi?id=160100 --- Comment #5 from Naresh --- Created attachment 193307 --> https://bugs.documentfoundation.org/attachment.cgi?id=193307=edit screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160100] Callout COPY loses formatting, pasted position makes useless.
https://bugs.documentfoundation.org/show_bug.cgi?id=160100 --- Comment #4 from Naresh --- Hi Ian Eales, I am unable to reproduce this error. Steps I tried: create a chart create a callout add text in callout copy and paste callout Result: was able to move and edit the second callout. attaching screenshot for reference. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160231] Images in Calc get lost (steps in comment 18)
https://bugs.documentfoundation.org/show_bug.cgi?id=160231 MB changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #21 from MB --- @stephane.guillou It is very important to understand that with my steps all the image groups in the document get lost, not only on row 106. And the target is to find an even better reproduction methodology that will make these images get lost without any resize of them. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160231] Images in Calc get lost (steps in comment 18)
https://bugs.documentfoundation.org/show_bug.cgi?id=160231 --- Comment #20 from MB --- @stephane.guillou Unfortunately I completely disagree with you and I was really upset sawing that you marked this bug as duplicate. Let me explain. First of all did you notice that with my methodology many images (which are in fact groups) get lost and the problem is not only "image" at row 106? Secondly, In my everyday usage of the file I never resize or move images, they are all in the middle of their cells anchored there and I never touch them. But after some edits and saves this happens again. People asked me to create a methodology to replicate the issue for them to see it and I searched for it showing a methodology but this doesn't mean this is the real problem. It's just a way to see with your own eyes the proof that there is an issue. My bug report here so refers to the random lost of "images" (which proved to be image groups) when editing the file, not when resizing the images. If you mark this as duplicate the issue here is closed and all the info that comes with it. I spent too much time on this to accept your last comment as the same as my issue. What you describe is another issue. If you find the reason why the group of images are lost without any resize of them just by editing the document, I may accept that it is related... -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160329] Image anchored to cell ends up in wrong cell after using autofilter sort, depending on hidden rows
https://bugs.documentfoundation.org/show_bug.cgi?id=160329 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0369 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160369] Group anchored to cell moves to next cell at save (+ visual left behind, so seems unselectable)
https://bugs.documentfoundation.org/show_bug.cgi?id=160369 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0329 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147420] Images anchored to a cell and selected with AUTOFILTER are not displaying or PRINTING correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=147420 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=16 | |0231| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160231] Images in Calc get lost (steps in comment 18)
https://bugs.documentfoundation.org/show_bug.cgi?id=160231 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |7420| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160369] Group anchored to cell moves to next cell at save (+ visual left behind, so seems unselectable)
https://bugs.documentfoundation.org/show_bug.cgi?id=160369 --- Comment #3 from Stéphane Guillou (stragu) --- (In reply to Stéphane Guillou (stragu) from comment #0) > If the document is reloaded, group is back in correct cell. ... but if the document is saved as _second_ time, the wrong position sticks. See duplicate bug 160231 comment 18, where this started. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160231] Images in Calc get lost (steps in comment 18)
https://bugs.documentfoundation.org/show_bug.cgi?id=160231 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED Summary|Images in Calc get lost |Images in Calc get lost |even in the newest version |(steps in comment 18) |of Libreoffice 24.2.0.3 | --- Comment #19 from Stéphane Guillou (stragu) --- (In reply to MB from comment #18) > Finally, I managed to find the exact steps to reproduce the issue!! For these steps at least, the underlying issue is that the cell anchor changes on save. I could reproduce as described, but trying to find a smaller set of steps, I found: 1. Open attachment 193145 2. Go to row 106 3. Save Result: group is now anchored to cell C107, even though its top-left corner is still in cell C106. Clicking the group does not seem to work, one has to click below, as if it was moved down. A reload of the file brings it back to cell C106. However, a _second_ save will make the object stay at cell C107 - so I think that's the essence of it, regardless of the extra intermediate steps you listed: saving twice makes the wrong anchor stick, with the obvious consequences when further manipulating the file. Note that resizing an object can move its anchor to a different cell, but it usually happens transparently and instantaneously (anchor is where top left corner is; happens as soon as resizing is finished. In this case, no resizing is needed. I've reported this 7.1 regression in the new bug 160369, for clarity. Marking this report as a duplicate. *** This bug has been marked as a duplicate of bug 160369 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160369] Group anchored to cell moves to next cell at save (+ visual left behind, so seems unselectable)
https://bugs.documentfoundation.org/show_bug.cgi?id=160369 Stéphane Guillou (stragu) changed: What|Removed |Added CC||myrbourf...@gmail.com --- Comment #2 from Stéphane Guillou (stragu) --- *** Bug 160231 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 35694] "Page number" automatic field stops counting before last page if offset >0 (see comment 22)
https://bugs.documentfoundation.org/show_bug.cgi?id=35694 --- Comment #77 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #76) Page number mechanism in Writer is connected to e.g. ToC, and its numbers. Any "A user who chooses to [Insert | Page Number] does not want to insert the number of another page", which implies use of offset to modify (even for display) the number of *current* page, tries to introduce inconsistency. And of course, this leads to greater confusion. I strongly believe, that there must *not* be any mechanics that allow *that* outside of the normal page break mechanism. OTOH, any improvements in the page breaks properties in that regards are welcome. The current page field may be changed e.g. like this: remove the offset from the field completely; and introduce another field kind, "page reference", which would have the offset. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 35694] "Page number" automatic field stops counting before last page if offset >0 (see comment 22)
https://bugs.documentfoundation.org/show_bug.cgi?id=35694 --- Comment #77 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #76) Page number mechanism in Writer is connected to e.g. ToC, and its numbers. Any "A user who chooses to [Insert | Page Number] does not want to insert the number of another page", which implies use of offset to modify (even for display) the number of *current* page, tries to introduce inconsistency. And of course, this leads to greater confusion. I strongly believe, that there must *not* be any mechanics that allow *that* outside of the normal page break mechanism. OTOH, any improvements in the page breaks properties in that regards are welcome. The current page field may be changed e.g. like this: remove the offset from the field completely; and introduce another field kind, "page reference", which would have the offset. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 130435] Crash in: ScRecursionHelper::PushFormulaGroup(ScFormulaCell *)
https://bugs.documentfoundation.org/show_bug.cgi?id=130435 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0368 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160368 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160368 [Bug 160368] Crash on save after deleting sheet -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108912] [META] Sheet-level bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108912 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160368 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160368 [Bug 160368] Crash on save after deleting sheet -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107943] [META] Save bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107943 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160368 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160368 [Bug 160368] Crash on save after deleting sheet -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160368] Crash on save after deleting sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=160368 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||bibisectRequest, ||haveBacktrace, regression See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||0435 Blocks||108912, 133092, 107943 CC||stephane.guillou@libreoffic ||e.org Version|7.6.5.2 release |6.2.0.3 release Severity|normal |critical Crash report or||["ScFormulaGroupCycleCheckG crash signature||uard::ScFormulaGroupCycleCh ||eckGuard(ScRecursionHelper& ||, ||ScFormulaCell*)","ScRecursi ||onHelper::PushFormulaGroup" ||] --- Comment #6 from Stéphane Guillou (stragu) --- Reproduced with: - 6.2.0.3, with "ScRecursionHelper::PushFormulaGroup": https://crashreport.libreoffice.org/stats/crash_details/b3abd5d1-0599-4ecf-93aa-4e6fdaadb61c - 7.0.0.3, same: https://crashreport.libreoffice.org/stats/crash_details/a46f2520-7b8a-4a53-b1db-b5864c58e658 - 7.3.0.3, with signature "ScFormulaGroupCycleCheckGuard::ScFormulaGroupCycleCheckGuard(ScRecursionHelper&, ScFormulaCell*)": https://crashreport.libreoffice.org/stats/crash_details/693cd29c-7efa-46fb-986f-e9af472bb229 - 7.6.5.2, same: https://crashreport.libreoffice.org/stats/crash_details/ffe18139-799b-4745-b4dd-b3fee563fe59 And recent trunk build: Version: 24.2.2.1 (X86_64) / LibreOffice Community Build ID: bf759d854b5ab45b6ef0bfd22e51c6dc4fb8b882 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded No repro in 6.1.0.3 -> regression. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107943 [Bug 107943] [META] Save bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108912 [Bug 108912] [META] Sheet-level bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 152336] Improve CSV field separator detection/behavior when several separators are selected on import
https://bugs.documentfoundation.org/show_bug.cgi?id=152336 --- Comment #10 from Mike Kaganski --- (In reply to Eyal Rozenberg from comment #9) > I would assume that if I save a file in a certain format, the specifics > would be independent of the input filtering, and only respect the format's > spec (and whatever defaults I have chosen the app to abide by if the spec is > flexible). Thus I would expect a TSV to be saved with tabs and a CSV with > commas even if, say, the input was parsed so as to separate fields by spaces. This may be a preference of some; but I claim, that at least for CSV, this would be a minority's preference; and the majority-to-minority ratio here will be HUGE. Most people who use Calc to edit CSVs will need Calc to retain the original file's structure; especially taking into account, that all "specs" in CSV are application-specific (and there is a *informational memo* RFC, reflecting some suggestions, but not binding). "Application-specific" here relates to the workflow (generation/consuming applications), not to the editing application in the middle. And a workflow of "normalization" of heterogenously-generated CSVs will be a minority of use cases. -- You are receiving this mail because: You are the assignee for the bug.
Re: Is anybody using LO's JavaScript editor window?
On 26.03.2024 5:55, Thorsten Behrens wrote: any recollection of anyone ever using live-editing of JS in LibreOffice? Here is a list of Ask topics with "JavaScript" in title: https://ask.libreoffice.org/search?q=JavaScript%20in%3Atitle%20order%3Alatest IMO, it is best to provide a better language compliance, sacrificing the editor if unavoidable; the IDE could catch up later, even as an extension, like with Python's APSO. -- Best regards, Mike Kaganski
[Bug 160369] Group anchored to cell moves to next cell at save (+ visual left behind, so seems unselectable)
https://bugs.documentfoundation.org/show_bug.cgi?id=160369 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Regression By||Regina Henschel Blocks||160370 Status|UNCONFIRMED |NEW --- Comment #1 from Stéphane Guillou (stragu) --- "new" as per bibisect. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160370 [Bug 160370] [META] Grouped objects -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160370] [META] Grouped objects
https://bugs.documentfoundation.org/show_bug.cgi?id=160370 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160369 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160369 [Bug 160369] Group anchored to cell moves to next cell at save (+ visual left behind, so seems unselectable) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160370] [META] Grouped objects
https://bugs.documentfoundation.org/show_bug.cgi?id=160370 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108640] [META] Object meta bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108640 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160370 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160370 [Bug 160370] [META] Grouped objects -- You are receiving this mail because: You are the assignee for the bug.
[Bug 150826] [META] RTF Grouped shapes/images issues
https://bugs.documentfoundation.org/show_bug.cgi?id=150826 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||160370 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160370 [Bug 160370] [META] Grouped objects -- You are receiving this mail because: You are the assignee for the bug.
[Bug 136328] [META] DOCX Grouped shape related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136328 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||160370 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160370 [Bug 160370] [META] Grouped objects -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160370] New: [META] Grouped objects
https://bugs.documentfoundation.org/show_bug.cgi?id=160370 Bug ID: 160370 Summary: [META] Grouped objects Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org Depends on: 136328, 150826 Blocks: 108640 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108640 [Bug 108640] [META] Object meta bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=136328 [Bug 136328] [META] DOCX Grouped shape related issues https://bugs.documentfoundation.org/show_bug.cgi?id=150826 [Bug 150826] [META] RTF Grouped shapes/images issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107943] [META] Save bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107943 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160369 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160369 [Bug 160369] Group anchored to cell moves to next cell at save (+ visual left behind, so seems unselectable) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160369 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160369 [Bug 160369] Group anchored to cell moves to next cell at save (+ visual left behind, so seems unselectable) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160369] New: Group anchored to cell moves to next cell at save (+ visual left behind, so seems unselectable)
https://bugs.documentfoundation.org/show_bug.cgi?id=160369 Bug ID: 160369 Summary: Group anchored to cell moves to next cell at save (+ visual left behind, so seems unselectable) Product: LibreOffice Version: 7.1.0.0.alpha1+ Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Keywords: bibisected, bisected, regression Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org CC: noelgran...@gmail.com, rb.hensc...@t-online.de Blocks: 87740, 107943 Steps: 1. Open attachment 193145 2. Go to C106 3. Click the group of pictures (see that it is anchored to cell C106) 4. Save (don't reload) Result: the group's handles and the anchor indicator are now in cell C107. If the selection is still active, one can move the object and the view refreshes. If it isn't active, the user has no idea why the visible group in C106 is not selectable (and it even isn't selectable by clicking blindly in its new position). If the document is reloaded, group is back in correct cell. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1344e6261a1d856c71eca1e0cc29215a586bf335 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Same for gen VCL plugin, same on Windows 11. Started in 7.1. History: - linux-64-7.1 bibisect repo, build [14085ca9b4d968e12730ae717ab0232a980eb4cf], commit bba0cd79984875124f8d43d05d4cdb7f63517e77: group moved to cell C107 on save, restored on reload. commit bba0cd79984875124f8d43d05d4cdb7f63517e77 author Regina Henschel Thu Nov 19 21:16:33 2020 +0100 committer Regina Henschel Fri Nov 20 10:17:17 2020 +0100 Replace matrix translate with object Move Reviewed-on: https://gerrit.libreoffice.org/c/core/+/106189 - linux-64-7.4 bibisect repo, build [52fa65a60081b2bc10aba220778b8daaabf9bdfb], commit 9a850dd9f3c221660b6259bdfd64a77343f2256c: group moved, but the pictures remain visible in cell C106. commit 9a850dd9f3c221660b6259bdfd64a77343f2256c author Noel GrandinWed Jan 12 10:27:38 2022 +0200 committer Noel GrandinWed Jan 12 14:45:30 2022 +0100 used cache value in ViewObjectContact::getPrimitive2DSequence (2nd attempt) Reviewed-on: https://gerrit.libreoffice.org/c/core/+/128319 Regina, can you please have a look? Noel, thought you might be interested in how your commit ties in. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=87740 [Bug 87740] [META] Anchor and text wrapping bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=107943 [Bug 107943] [META] Save bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160123] LibreOffice does not start
https://bugs.documentfoundation.org/show_bug.cgi?id=160123 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|FIXED |WORKSFORME --- Comment #3 from Stéphane Guillou (stragu) --- Thanks for reporting back. Marking as "works for me" as "fixed" is when a fixing patch has been identified. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151007] When opening a CSV file, default to CSV-spec-compliant options
https://bugs.documentfoundation.org/show_bug.cgi?id=151007 QA Administrators changed: What|Removed |Added Whiteboard|needsUXAdvice |needsUXAdvice |QA:needsComment | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160153] c.s.s.util.PathSettings: WrappedTargetRuntimeException with attribute "Storage"
https://bugs.documentfoundation.org/show_bug.cgi?id=160153 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160186] Changing Table Auto value or Entry required results in full libreoffice suite crash
https://bugs.documentfoundation.org/show_bug.cgi?id=160186 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160186] Changing Table Auto value or Entry required results in full libreoffice suite crash
https://bugs.documentfoundation.org/show_bug.cgi?id=160186 --- Comment #9 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156934] After update to 7.6 extensions are not listed anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=156934 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156934] After update to 7.6 extensions are not listed anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=156934 --- Comment #7 from QA Administrators --- Dear ThP, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156936] Cannot overlay text over a .jpg in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=156936 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156936] Cannot overlay text over a .jpg in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=156936 --- Comment #3 from QA Administrators --- Dear Thomas Krauser, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 82624] FILESAVE: Images inserted as link are stored in file, not as link, when saving as RTF
https://bugs.documentfoundation.org/show_bug.cgi?id=82624 --- Comment #8 from QA Administrators --- Dear FABIO AUGUSTO, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157155] Display of same document in multiple windows in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=157155 --- Comment #4 from QA Administrators --- Dear kaesezeh, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Bug 143192] 'Format' Basic function doesn't handle Null values
https://bugs.documentfoundation.org/show_bug.cgi?id=143192 --- Comment #3 from QA Administrators --- Dear Mike Kaganski, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 100506] Addition ability to copy result of search in dialogue Find
https://bugs.documentfoundation.org/show_bug.cgi?id=100506 --- Comment #16 from QA Administrators --- Dear Roman Kuznetsov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 131555] Cannot set cell borders from VBA macro
https://bugs.documentfoundation.org/show_bug.cgi?id=131555 --- Comment #5 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160363] Context Menus take over 1.5 minutes to display
https://bugs.documentfoundation.org/show_bug.cgi?id=160363 m_a_riosv changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #3 from m_a_riosv --- I don't why you have gone for the long way. Restart in Safe Mode is easy and quick. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160368] Crash on save after deleting sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=160368 --- Comment #5 from m_a_riosv --- Not reproduced without 'Force Skia software rendering' Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1344e6261a1d856c71eca1e0cc29215a586bf335 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Not reproduced without 'Skia' Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1344e6261a1d856c71eca1e0cc29215a586bf335 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160347] Missing spaces in documents
https://bugs.documentfoundation.org/show_bug.cgi?id=160347 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #11 from Stéphane Guillou (stragu) --- (In reply to michaelweigelt from comment #5) > Created attachment 193290 [details] > test document excerpt in .docx format Still no reproduced with: Version: 24.2.2.1 (X86_64) / LibreOffice Community Build ID: bf759d854b5ab45b6ef0bfd22e51c6dc4fb8b882 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Opening it warns me of missing hyphenation data for German. I installed https://extensions.libreoffice.org/en/extensions/show/german-de-de-frami-dictionaries to by able to hyphenate, and still not reproduced. I also tried saving and reloading the file with both 7.6.5.2 and 24.2.2.2. What do you use for hyphenation? Any particular settings? Please also test in safe mode (Help > Restart in safe mode) to see if it is linked to your user profile. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159373] Crash in: ScTable::HasAttrib(short,long,short,long,HasAttrFlags)
https://bugs.documentfoundation.org/show_bug.cgi?id=159373 --- Comment #20 from Stéphane Guillou (stragu) --- Julien, could you please close this report as "resolved - fixed" and open a follow-up report with a short summary of what remains to be fixed? Probably the best way forward. Thanks Telesto. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160363] Context Menus take over 1.5 minutes to display
https://bugs.documentfoundation.org/show_bug.cgi?id=160363 --- Comment #2 from teob6...@yahoo.com --- Had to reinstall 24.2. This time I did NOT remove the older version via MSFT Programs removal. I installed it with with older version remaining on his system, but to a different folder. This install told me twice a restart is required and it did it for me. So, I did a CUSTOM install so I could change folders and keep 5.2.9 in old folder. This install fixed the error, whereas the previous 24.2 install where I removed older LibreOffice first did NOT fix the problem. Difference? The RESTART I believe. This install specifically told me a RESTART was needed and forced me to do it. The previous try did NOT ask me to restart. Anyway, all is good and no SAFE mode testing is required. Thanks for your help.! Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 8; OS: Windows 10.0 Build 22631; 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.
Re: Error Compiling LibreOffice Core on Debian 12 - x64
Hi, On Mon, Mar 25, 2024 at 5:51 PM Michael Weghorn wrote: > Renaming one of the enums could be one approach, e.g. the one defined in > vcl/inc/regband.hxx to something like "RegionBandLineType". (Just a > first thought when skimming over the file, I don't otherwise know the > involved code.) The types in cgmtypes.hxx could also be changed to enum class and added into a namespace to prevent conflicts as those are all local to CGM filter anyway. Tomaž
[Bug 160368] Crash on save after deleting sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=160368 --- Comment #4 from Armondo Lopez --- Thank you for reporting the bug. I can confirm that the bug is present in Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded as well as Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
Re: Is anybody using LO's JavaScript editor window?
Hi y'all, Stephan Bergmann wrote: > Now, how widespread is the use of this edit window feature for JavaScript, > actually? > I'm not aware of any extension using JS (except for ancient demo code). The beanshell bits are sort of useful though, since they allow rapid prototyping of Java UNO code - if that's not affected, I see only upsides in this change. Hossein, any recollection of anyone ever using live-editing of JS in LibreOffice? Cheers, -- Thorsten signature.asc Description: PGP signature
[Bug 159993] Newline+tab on bullet list start typing on next line after clicking on last character
https://bugs.documentfoundation.org/show_bug.cgi?id=159993 Armondo Lopez changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from Armondo Lopez --- Thank you for reporting the bug. I can confirm that the bug is present in Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: db4def46b0453cc22e2d0305797cf981b68ef5ac CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded as well as Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a2265e8faa099d9652efd12392c2877c2df1d1eb CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160368] Crash on save after deleting sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=160368 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m_a_riosv --- Not reproducible: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded neither with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1344e6261a1d856c71eca1e0cc29215a586bf335 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160368] Crash on save after deleting sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=160368 Telesto changed: What|Removed |Added Ever confirmed|0 |1 OS|Linux (All) |All Status|UNCONFIRMED |NEW CC||tele...@surfxs.nl --- Comment #2 from Telesto --- Confirm Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b38974391e8d4bf0d450abfaa86bbccbe1022995 CPU threads: 8; OS: macOS 14.3; UI render: Skia/Raster; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160329] Image anchored to cell ends up in wrong cell after using autofilter sort, depending on hidden rows
https://bugs.documentfoundation.org/show_bug.cgi?id=160329 Regina Henschel changed: What|Removed |Added Attachment #193301|0 |1 is obsolete|| --- Comment #6 from Regina Henschel --- Created attachment 193306 --> https://bugs.documentfoundation.org/attachment.cgi?id=193306=edit Small Example all images anchored to cell My fault. Image D in the example was anchored to page. The new upload should have it correct. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160368] Crash on save after deleting sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=160368 --- Comment #1 from Vlad-Mihai --- Created attachment 193305 --> https://bugs.documentfoundation.org/attachment.cgi?id=193305=edit gdb trace -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160368] New: Crash on save after deleting sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=160368 Bug ID: 160368 Summary: Crash on save after deleting sheet Product: LibreOffice Version: 7.6.5.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vladmihais...@gmail.com Created attachment 193304 --> https://bugs.documentfoundation.org/attachment.cgi?id=193304=edit Spreadsheet that crashes if one sheet except PROBLEM is deleted and file saved Steps to reproduce: a) load bug.ods b) delete one sheet for example "a" - except the one called "PROBLEM" c) save -> this crashes for me (see gdbtrace.log). Based on the trace, this seems similar to https://bugs.documentfoundation.org/show_bug.cgi?id=130435#c3 As with the mentioned bug, originally the spreadsheet was quite complex and with sensitive information, but I deleted all the sheets contents (could not delete the sheets as it would trigger the bug), and changed their names. Does not seem to matter which sheet I delete (tried 3-4). Bug also happens if I change the value in cell F8 in sheet "PROBLEM" (but might be because of autosave) The sheet in question was created by duplicating another sheet in the same file, and doing some edits (deleting couple of columns and rows and changing a couple of formulas) but nothing too fancy. I am using Arch Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160367] A dialog tab for managing name/alternative label and description is lacking in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=160367 Telesto changed: What|Removed |Added CC||heiko.tietze@documentfounda ||tion.org Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160367] New: A dialog tab for managing name/alternative label and description is lacking in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=160367 Bug ID: 160367 Summary: A dialog tab for managing name/alternative label and description is lacking in Calc Product: LibreOffice Version: 24.8.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: A dialog tab for managing name/alternative label and description is lacking in Calc Steps to Reproduce: 1. Open Calc 2. Add some image into it.. 3. Search for a dialog equivalent to Image Properties Options tab in Writer. You have to object name and the alternative text separately Actual Results: It's hard to manage image properties image name; image text; image alternative text It's currently also bit confusing: is image alternative text in Calc the same as description field in the writer dialog? Expected Results: A single dialog which gives access to all? Reproducible: Always User Profile Reset: No Additional Info: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b38974391e8d4bf0d450abfaa86bbccbe1022995 CPU threads: 8; OS: macOS 14.3; UI render: default; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160366] New: Cannot set language
https://bugs.documentfoundation.org/show_bug.cgi?id=160366 Bug ID: 160366 Summary: Cannot set language Product: LibreOffice Version: 24.2.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: p.wibber...@btinternet.com Description: In Writer, 'Tools'.'Language'.'For Selection' shows English(UK) checked. 'Tools'.'Language'.'For Paragraph' shows English(UK) unchecked, and trying to check it merely closes the menu. 'For All Text' is the same as 'For Paragraph'. Selecting 'Tools'.'Spelling' shows Text language as "[None]", with the only other option in the drop down menu being "English(USA)". Spellchecking doesn't work. NB 'Tools'.'Options'.'Languages and Locales'.'General' shows 'User Interface', 'Locale setting' and 'Default Languages for Documents'.'Western' are all "English (UK)" or "Default-English(UK)" Steps to Reproduce: 1.Open new or existing document and select menu options, as in Description, above 2. 3. Actual Results: As Description Expected Results: Spell-checking should work, using English(UK) Reproducible: Always User Profile Reset: No Additional Info: 'Tools'.'Options'.'Languages and Locales'.'General' shows 'User Interface', 'Locale setting' and 'Default Languages for Documents'.'Western' are all "English (UK)" or "Default-English(UK)" I have noticed this problem only since upgrading to Neon 6.0 and Libreoffice 24.2 from 7.6(?). The problem remains if I restart in Safe Mode. Version: 24.2.1.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 4:24.2.1~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
core.git: vcl/inc vcl/unx
vcl/inc/unx/i18n_cb.hxx |2 +-
vcl/unx/generic/app/i18n_cb.cxx |4 +---
2 files changed, 2 insertions(+), 4 deletions(-)
New commits:
commit 24aed4f9a5f6351d9153c96e3d1d1aa68028c0d0
Author: Stephan Bergmann
AuthorDate: Mon Mar 25 18:54:05 2024 +0100
Commit: Stephan Bergmann
CommitDate: Mon Mar 25 23:34:33 2024 +0100
Avoid -Werror,-Wcast-function-type-mismatch, remove unused int return
> vcl/unx/generic/app/i18n_ic.cxx:225:51: error: cast from 'int (*)(XIC,
XPointer, XPointer)' (aka 'int (*)(_XIC *, char *, char *)') to 'XIMProc' (aka
'void (*)(_XIM *, char *, char *)') converts to incompatible function type
[-Werror,-Wcast-function-type-mismatch]
> 225 | maPreeditStartCallback.callback =
reinterpret_cast(PreeditStartCallback);
> |
^~~
Change-Id: I94d1d0042516a01f8597bc65895042ddae76c98b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165291
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann
diff --git a/vcl/inc/unx/i18n_cb.hxx b/vcl/inc/unx/i18n_cb.hxx
index 4b498f387820..497875236c5d 100644
--- a/vcl/inc/unx/i18n_cb.hxx
+++ b/vcl/inc/unx/i18n_cb.hxx
@@ -28,7 +28,7 @@ extern "C" {
// xim callbacks
void PreeditDoneCallback ( XIC ic, XPointer client_data, XPointer call_data);
-int PreeditStartCallback( XIC ic, XPointer client_data, XPointer call_data);
+void PreeditStartCallback( XIC ic, XPointer client_data, XPointer call_data);
void PreeditDrawCallback ( XIC ic, XPointer client_data,
XIMPreeditDrawCallbackStruct *call_data );
void PreeditCaretCallback( XIC ic, XPointer client_data,
diff --git a/vcl/unx/generic/app/i18n_cb.cxx b/vcl/unx/generic/app/i18n_cb.cxx
index c17c01a4d225..d4efcf34fd55 100644
--- a/vcl/unx/generic/app/i18n_cb.cxx
+++ b/vcl/unx/generic/app/i18n_cb.cxx
@@ -34,7 +34,7 @@
// i. preedit start callback
-int
+void
PreeditStartCallback ( XIC, XPointer client_data, XPointer )
{
preedit_data_t* pPreeditData =
reinterpret_cast(client_data);
@@ -43,8 +43,6 @@ PreeditStartCallback ( XIC, XPointer client_data, XPointer )
pPreeditData->eState = PreeditStatus::Active;
pPreeditData->aText.nLength= 0;
}
-
-return -1;
}
// ii. preedit done callback
[Bug 160329] Image anchored to cell ends up in wrong cell after using autofilter sort, depending on hidden rows
https://bugs.documentfoundation.org/show_bug.cgi?id=160329 --- Comment #5 from Telesto --- Created attachment 193303 --> https://bugs.documentfoundation.org/attachment.cgi?id=193303=edit Screencast (In reply to Regina Henschel from comment #4) Strange: Hiding the row of image B is already buggy in my case, without touching sort column Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b38974391e8d4bf0d450abfaa86bbccbe1022995 CPU threads: 8; OS: macOS 14.3; UI render: Skia/Raster; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160356] Calc should support hidden Named Expressions as well
https://bugs.documentfoundation.org/show_bug.cgi?id=160356 Rafael Lima changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | --- Comment #1 from Rafael Lima --- Proposed patch here: https://gerrit.libreoffice.org/c/core/+/165239 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160365] Writer: unable to turn off "text boundaries" for frames
https://bugs.documentfoundation.org/show_bug.cgi?id=160365 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||1253 Status|UNCONFIRMED |ASSIGNED Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 131253] Frames are displayed around images even though Object boundaries is unchecked, as Text boundaries control it
https://bugs.documentfoundation.org/show_bug.cgi?id=131253 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0365 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 131253] Frames are displayed around images even though Object boundaries is unchecked, as Text boundaries control it
https://bugs.documentfoundation.org/show_bug.cgi?id=131253 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0365 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 129905] Cannot turn off section boundaries with Options-Application Colors
https://bugs.documentfoundation.org/show_bug.cgi?id=129905 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0365 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160365] New: Writer: unable to turn off "text boundaries" for frames
https://bugs.documentfoundation.org/show_bug.cgi?id=160365 Bug ID: 160365 Summary: Writer: unable to turn off "text boundaries" for frames Product: LibreOffice Version: 7.6.0.0 alpha0+ Hardware: All OS: All Status: UNCONFIRMED Keywords: bibisected, bisected, regression Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jl...@mail.com CC: jl...@mail.com, rafael.palma.l...@gmail.com Created attachment 193302 --> https://bugs.documentfoundation.org/attachment.cgi?id=193302=edit 131253_through.docx: gray border seen around background image. When you have an image (or other frame) in the document, it has a thin border around it unless View - Text boundaries is turned off. Starting in 7.6, that option no longer turns off the border. commit 79811c27f34d3e752de1bc3959605c5d58ac2365 Author: Rafael Lima on Tue Jan 24 17:54:11 2023 + tdf#129905 Create toggle for Section boundaries -- You are receiving this mail because: You are the assignee for the bug.
[Bug 129905] Cannot turn off section boundaries with Options-Application Colors
https://bugs.documentfoundation.org/show_bug.cgi?id=129905 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0365 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160329] Image anchored to cell ends up in wrong cell after using autofilter sort, depending on hidden rows
https://bugs.documentfoundation.org/show_bug.cgi?id=160329 --- Comment #4 from Regina Henschel --- Created attachment 193301 --> https://bugs.documentfoundation.org/attachment.cgi?id=193301=edit Small Example I can reproduce the problem with the smaller example of the attachment. It has images A B C D E so you can easily see to which row the image belongs. Hide row of image B and then sort column A the opposite direction. The images have still the correct anchor cell after sorting, but the offset to the anchor is wrong. I have no idea about the reason. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160186] Changing Table Auto value or Entry required results in full libreoffice suite crash
https://bugs.documentfoundation.org/show_bug.cgi?id=160186 --- Comment #8 from cont...@bluesanta.io --- I'll try to get a debug build going with backtrace. Can't do it right this moment, but will try soon. -- You are receiving this mail because: You are the assignee for the bug.
core.git: sw/source
sw/source/ui/index/cnttab.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 02609da5ee8188cb00fc0b97052d2cc8d2576900 Author: Julien Nabet AuthorDate: Mon Mar 25 13:59:06 2024 +0100 Commit: Julien Nabet CommitDate: Mon Mar 25 22:43:20 2024 +0100 Related tdf#160351: the field name can be shorter than two symbols Change-Id: Ieb6b78b3f9802e66de642a9e708b11c55c0d9a11 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165285 Tested-by: Jenkins Reviewed-by: Julien Nabet diff --git a/sw/source/ui/index/cnttab.cxx b/sw/source/ui/index/cnttab.cxx index f07cf8ab2883..535dc298dd5a 100644 --- a/sw/source/ui/index/cnttab.cxx +++ b/sw/source/ui/index/cnttab.cxx @@ -3140,7 +3140,7 @@ void SwTokenWindow::InsertAtSelection(const SwFormToken& rToken) //use the first two chars as symbol OUString sTmp(SwAuthorityFieldType::GetAuthFieldName( static_cast(aToInsertToken.nAuthorityField))); -pButton->SetText(sTmp.copy(0, 2)); +pButton->SetText(sTmp.copy(0, std::min(sTmp.getLength(), sal_Int32(2; } pButton->Check();
[Bug 160362] Syntax Highlighting Support
https://bugs.documentfoundation.org/show_bug.cgi?id=160362
--- Comment #1 from `{third: "Beedell", first: "Roke"}`{.JSON5}
<1c4cm...@rokejulianlockhart.addy.io> ---
This is for adding the plumbing necessary to support multiple syntax
highlighters in the (plain text) editor, if that support doesn't already exist
(I don't see any evidence of it).
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 160123] LibreOffice does not start
https://bugs.documentfoundation.org/show_bug.cgi?id=160123 vak...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|NEEDINFO|RESOLVED --- Comment #2 from vak...@gmail.com --- Tried it again today to get the backtrace but I couldn't reproduce the bug anymore. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160364] New: soffice --convert-to gives "Secure coding is not enabled for restorable state!" warning
https://bugs.documentfoundation.org/show_bug.cgi?id=160364 Bug ID: 160364 Summary: soffice --convert-to gives "Secure coding is not enabled for restorable state!" warning Product: LibreOffice Version: 24.2.1.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: loic_m...@worldonline.fr Description: Hello, MacOS Sonoma 14.3.1 (23D60) LibreOffice 24.2.1.2 I convert .doc files to .pdf by commande line with soffice for years now. I recently saw this warning on the standard error : 2024-03-25 22:09:01.466 soffice[20499:4374017] WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES. The PDF file stills gets created. Converting the same .doc file to .txt produces the same warning. Loïc Steps to Reproduce: 1. Concert .doc file to .pdf of .txt with commande line soffice 2. 3. Actual Results: The pdf file is created, but a warning occurs. Expected Results: No warning should occur Reproducible: Always User Profile Reset: No Additional Info: This happened after I upgrades Libre Office to the latest version. I don't remember which version I had previously, but it what a least 2 ou 3 years old. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 112629] [META] Character content panel of the Properties deck/tab of the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=112629 BogdanB changed: What|Removed |Added Depends on||159168 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159168 [Bug 159168] Character style: "No Character Style" won't be shown when "Applied Styles" is chosen -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159168] Character style: "No Character Style" won't be shown when "Applied Styles" is chosen
https://bugs.documentfoundation.org/show_bug.cgi?id=159168 BogdanB changed: What|Removed |Added Summary|Character style: "No|Character style: "No |Character Style" won't be |Character Style" won't be |shown when "Applied Styles" |shown when "Applied Styles" |is chosen. |is chosen Blocks||112629 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112629 [Bug 112629] [META] Character content panel of the Properties deck/tab of the sidebar -- You are receiving this mail because: You are the assignee for the bug.
Libtre Office License Statement
All of my past & future contributions to LibreOffice may be licensed under the MPLv2/LGPLv3+ dual license.
[Bug 101258] [META] Bibliography bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101258 BogdanB changed: What|Removed |Added Depends on||144607 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144607 [Bug 144607] Bibliography database option does not open when selected -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160363] Context Menus take over 1.5 minutes to display
https://bugs.documentfoundation.org/show_bug.cgi?id=160363 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Please test in safe mode, Menu/Help/Restart in Safe Mode Please paste here the information on Menu/Help/About LibreOffice (There is an icon to copy) -- You are receiving this mail because: You are the assignee for the bug.
core.git: sc/source
sc/source/ui/view/tabview.cxx |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) New commits: commit 0581190bc4e5502d93aa695365e7bf82b23d1ecf Author: Caolán McNamara AuthorDate: Mon Mar 25 10:20:12 2024 + Commit: Caolán McNamara CommitDate: Mon Mar 25 21:35:30 2024 +0100 cid#1594675 Logically dead code Change-Id: Icaf621e7a2e163f969ac7b6a1d6d04bf9251ea56 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165277 Tested-by: Jenkins Reviewed-by: Caolán McNamara diff --git a/sc/source/ui/view/tabview.cxx b/sc/source/ui/view/tabview.cxx index e809ceb11249..79bd6d1e67ff 100644 --- a/sc/source/ui/view/tabview.cxx +++ b/sc/source/ui/view/tabview.cxx @@ -1154,10 +1154,12 @@ void ScTabView::ScrollHdl(ScrollAdaptor* pScroll) aHelpStr = ScResId(STR_ROW) + " " + OUString::number(nScrollPos + 1); +// note that bLayoutRTL is always false here, because bLayoutRTL depends on bHoriz + // show quicktext always inside sheet area -aRect.SetLeft( bLayoutRTL ? (aPos.X() + aSize.Width() + 8) : (aPos.X() - 8) ); +aRect.SetLeft(aPos.X() - 8); aRect.SetTop( aMousePos.Y() ); -nAlign = (bLayoutRTL ? QuickHelpFlags::Left : QuickHelpFlags::Right) | QuickHelpFlags::VCenter; +nAlign = QuickHelpFlags::Right | QuickHelpFlags::VCenter; } aRect.SetRight( aRect.Left() ); aRect.SetBottom( aRect.Top() );
[Bug 160363] New: Context Menus take over 1.5 minutes to display
https://bugs.documentfoundation.org/show_bug.cgi?id=160363 Bug ID: 160363 Summary: Context Menus take over 1.5 minutes to display Product: LibreOffice Version: 24.2.1.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: teob6...@yahoo.com Description: LibreOffice WRITER only...version 24.2 With Writer open, selecting any item from upper tool bar (FILE EDIT VIEW ... HELP) should open the context menu for that entry. Libre Office WRITER only does NOT open the context menu until over 1.5 minutes later for any of the items in the tool bar. This happens, I repeat, only for WRITER in version 24.2. I am not a LibreOffice user myself, but rebuilt a new PC system for a visually impaired person who is a LIbreOffice person. I had to download the latest version in install it, which was 24.2, on 2/29/24. Today, my friend called about a different problem, but it was clearly related to using LibreOffice, so I checked it out. The WRITER had this issue, which caused him a lot of headaches since he can't see anything lower than 400% magnified and couldn't tell what was going on. I first did a REPAIR installation function, but it did not alter it to correct anything and then a removal and reinstall of 24.2 which also did not resolve the issue. So, I went to a back level 7.5.9 version and it resolved the issue! Restating, look only at version 24.2 WRITER. A side note is that when I did build his new system I put the Right-Click Windows 10 hack in to replace the Windows 11 context menu. I can't understand why Microsoft tried to simplify, but in his case, complicate things by putting what he needs in a second context menu off the 1st one! But, maybe this hack is involved in the version 24.2 not working properly. Good luck. Steps to Reproduce: 1.Do NOT set up LibreOffice to load at system start up 2.Once system running, open Writer 3.Go to one of the too bar entries, like FILE, VIEW, EDIT, or any of them 4. Ciick on it and you will wait a long time seeing No Reponse 5. Once a menu appears, after 1.5 minutes for us, menus will now open correctly for all entries on tool bar Actual Results: No Response Expected Results: immediate opening of context menu Reproducible: Always User Profile Reset: No Additional Info: Everything reported above. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160359] Navigation Sidebar glitched and/or not working, only in Windows 11 (not a problem in Ubuntu 20.02 linux)
https://bugs.documentfoundation.org/show_bug.cgi?id=160359 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Please test in safe mode, Menu/Help/Restart in Safe Mode Please paste here the information on Menu/Help/About LibreOffice (There is an icon to copy) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 35694] "Page number" automatic field stops counting before last page if offset >0 (see comment 22)
https://bugs.documentfoundation.org/show_bug.cgi?id=35694 --- Comment #76 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #70) > Generally, "ApplyOffset(GetNumberOf(CurrentPage()), N )" implies a numeric > "page number", which is not a requirement. It isn't? Page numbers are numbers, and numbers are numeric, aren't they? If you're referring to the styling of the number, i.e. A B C or i ii iii vs 1 2 3, that's just formatting; the offset applies to the number itself, not its formatted form. > Any such arithmetics will not give you > a *number*, but a "page number" - thus, the only sensible thing is > "GetNumberOf(ApplyOffset(CurrentPage(), N))". I have argued above that it is not a sensible thing. A user who chooses to [Insert | Page Number] does not want to insert the number of another page. For doing that, they would [Insert | Cross Reference]. (By the way, if a user does [Insert | Field], the dialog clearly separates "Cross Reference" from where we get the page number. But then, within the "Document" tab, in the "Select" column, we have "Page Number", "Previous Page", "Next Page". This suggests that we do get cross-ref-type fields on this pane; but it also suggests that the way to refer to another page is through the "Select" box, not through the Offset field, and that "Page Number" itself will only be the current page's number, not the number of any other page) > And we are back to the wording. It should be fixed. If you want to fix the UI so that Page Numbers are not necessarily numbers, you have to rework: 1. Some items on the Insert menu 2. The [Insert | Field] dialog <- which makes that assumption in multiple ways, including by have a number sequence choice box 3. The Insert Page Numbers dialog ... and I wonder whether replacing Page Numbers with something else will be a positive development for our users. Although I still don't know what you intend to replace "Page Number" with, so maybe it won't be that bad? :-\ > Now we have a *different* field, namely, Insert Formula field, We do? I can't find it on the Insert menu, nor in the Insert Field dialog. Anyway, this could certainly be a basis for getting the "ApplyOffset(GetNumberOf(CurrentPage()), N )" effect. If we take that direction, then I believe the UI for [Insert | Page Number] would have to be rebased on this formula mechanism to begin with. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 35694] "Page number" automatic field stops counting before last page if offset >0 (see comment 22)
https://bugs.documentfoundation.org/show_bug.cgi?id=35694 --- Comment #76 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #70) > Generally, "ApplyOffset(GetNumberOf(CurrentPage()), N )" implies a numeric > "page number", which is not a requirement. It isn't? Page numbers are numbers, and numbers are numeric, aren't they? If you're referring to the styling of the number, i.e. A B C or i ii iii vs 1 2 3, that's just formatting; the offset applies to the number itself, not its formatted form. > Any such arithmetics will not give you > a *number*, but a "page number" - thus, the only sensible thing is > "GetNumberOf(ApplyOffset(CurrentPage(), N))". I have argued above that it is not a sensible thing. A user who chooses to [Insert | Page Number] does not want to insert the number of another page. For doing that, they would [Insert | Cross Reference]. (By the way, if a user does [Insert | Field], the dialog clearly separates "Cross Reference" from where we get the page number. But then, within the "Document" tab, in the "Select" column, we have "Page Number", "Previous Page", "Next Page". This suggests that we do get cross-ref-type fields on this pane; but it also suggests that the way to refer to another page is through the "Select" box, not through the Offset field, and that "Page Number" itself will only be the current page's number, not the number of any other page) > And we are back to the wording. It should be fixed. If you want to fix the UI so that Page Numbers are not necessarily numbers, you have to rework: 1. Some items on the Insert menu 2. The [Insert | Field] dialog <- which makes that assumption in multiple ways, including by have a number sequence choice box 3. The Insert Page Numbers dialog ... and I wonder whether replacing Page Numbers with something else will be a positive development for our users. Although I still don't know what you intend to replace "Page Number" with, so maybe it won't be that bad? :-\ > Now we have a *different* field, namely, Insert Formula field, We do? I can't find it on the Insert menu, nor in the Insert Field dialog. Anyway, this could certainly be a basis for getting the "ApplyOffset(GetNumberOf(CurrentPage()), N )" effect. If we take that direction, then I believe the UI for [Insert | Page Number] would have to be rebased on this formula mechanism to begin with. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 160360] Syntax Highlighting for Markdown
https://bugs.documentfoundation.org/show_bug.cgi?id=160360
`{third: "Beedell", first: "Roke"}`{.JSON5}
<1c4cm...@rokejulianlockhart.addy.io> changed:
What|Removed |Added
Depends on||160362
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=160362
[Bug 160362] Syntax Highlighting Support
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 97638] Beanshell Editor: Add syntax highlighting
https://bugs.documentfoundation.org/show_bug.cgi?id=97638
`{third: "Beedell", first: "Roke"}`{.JSON5}
<1c4cm...@rokejulianlockhart.addy.io> changed:
What|Removed |Added
Depends on||160362
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=160362
[Bug 160362] Syntax Highlighting Support
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 43089] Syntax highlighting for Math
https://bugs.documentfoundation.org/show_bug.cgi?id=43089
`{third: "Beedell", first: "Roke"}`{.JSON5}
<1c4cm...@rokejulianlockhart.addy.io> changed:
What|Removed |Added
Depends on||160362
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=160362
[Bug 160362] Syntax Highlighting Support
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 160362] New: Syntax Highlighting Support
https://bugs.documentfoundation.org/show_bug.cgi?id=160362 Bug ID: 160362 Summary: Syntax Highlighting Support Product: LibreOffice Version: unspecified Hardware: All URL: https://ask.libreoffice.org/t/does-syntax-highlighting -exist-as-a-feature/103940?u=rokejulianlockhart OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: 1c4cm...@rokejulianlockhart.addy.io Blocks: 43089, 97638, 160360 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=43089 [Bug 43089] Syntax highlighting for Math https://bugs.documentfoundation.org/show_bug.cgi?id=97638 [Bug 97638] Beanshell Editor: Add syntax highlighting https://bugs.documentfoundation.org/show_bug.cgi?id=160360 [Bug 160360] Syntax Highlighting for Markdown -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160361] New: Export Preview Support
https://bugs.documentfoundation.org/show_bug.cgi?id=160361 Bug ID: 160361 Summary: Export Preview Support Product: LibreOffice Version: 24.2.1.2 release Hardware: All URL: https://ask.libreoffice.org/t/can-i-have-a-side-by-sid e-export-preview/103941?u=rokejulianlockhart OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: 1c4cm...@rokejulianlockhart.addy.io As https://ask.libreoffice.org/t/can-i-have-a-side-by-side-export-preview/103941?u=rokejulianlockhart explains: > https://github.com/microsoft/vscode-docs/blob/463630e70436308da191b917656571c7afb78797/docs/getstarted/userinterface.md#side-by-side-editing > explains how this is accomplished in VS Code. > > Relevantly, if/when https://bugs.documentfoundation.org/show_bug.cgi?id=94978 > and/or https://bugs.documentfoundation.org/show_bug.cgi?id=160360 is/are > implemented, this shall become *especially* important to me, although I also > export ODT files directly as HTML, so that would be too. > > However, it obviously isn't limited to languages which comparable editors > support, nor even plain text files — I'd frequently like to be able to > preview PDF export of an ODT file. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160360] Syntax Highlighting for Markdown
https://bugs.documentfoundation.org/show_bug.cgi?id=160360
`{third: "Beedell", first: "Roke"}`{.JSON5}
<1c4cm...@rokejulianlockhart.addy.io> changed:
What|Removed |Added
Summary|Syntax Highlighting for |Syntax Highlighting for
|Markdown. |Markdown
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 94978] [Request] Save as Markdown
https://bugs.documentfoundation.org/show_bug.cgi?id=94978
`{third: "Beedell", first: "Roke"}`{.JSON5}
<1c4cm...@rokejulianlockhart.addy.io> changed:
What|Removed |Added
See Also||https://bugs.documentfounda
||tion.org/show_bug.cgi?id=16
||0360
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 160360] New: Syntax Highlighting for Markdown.
https://bugs.documentfoundation.org/show_bug.cgi?id=160360 Bug ID: 160360 Summary: Syntax Highlighting for Markdown. Product: LibreOffice Version: 24.2.1.2 release Hardware: All URL: https://bugs.documentfoundation.org/show_bug.cgi?id=43 089#c0 OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: 1c4cm...@rokejulianlockhart.addy.io Markdown can already be edited as plain text, and if https://bugs.documentfoundation.org/show_bug.cgi?id=94978 is implemented, shall become an exportable format. Consequently, syntax highlighting is the sole important feature absent for it to be easily modifiable too. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 43089] Syntax highlighting for Math
https://bugs.documentfoundation.org/show_bug.cgi?id=43089
`{third: "Beedell", first: "Roke"}`{.JSON5}
<1c4cm...@rokejulianlockhart.addy.io> changed:
What|Removed |Added
See Also||https://bugs.documentfounda
||tion.org/show_bug.cgi?id=16
||0360
--
You are receiving this mail because:
You are the assignee for the bug.
core.git: download.lst
download.lst |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) New commits: commit a80258e11282c78ab3867c96e4c2575e83c5482b Author: Xisco Fauli AuthorDate: Mon Mar 25 13:45:24 2024 +0100 Commit: Xisco Fauli CommitDate: Mon Mar 25 20:43:29 2024 +0100 mariadb connector: upgrade to release 3.3.8 Change-Id: I21cf511a2b6c040d4a64ca720606af9312130045 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165284 Tested-by: Jenkins Reviewed-by: Xisco Fauli diff --git a/download.lst b/download.lst index d35bd6300748..2b033727c322 100644 --- a/download.lst +++ b/download.lst @@ -446,8 +446,8 @@ LXML_TARBALL := lxml-4.9.2.tgz # three static lines # so that git cherry-pick # will not run into conflicts -MARIADB_CONNECTOR_C_SHA256SUM := 975a9a862fed80f84e0206373f7ef05537aada5b65d99b71b36ab892b44240bf -MARIADB_CONNECTOR_C_TARBALL := mariadb-connector-c-3.3.7-src.tar.gz +MARIADB_CONNECTOR_C_SHA256SUM := f9f076b4aa9fb22cc94b24f82c80f9ef063805ecd6533a2eb5d5060cf93833e8 +MARIADB_CONNECTOR_C_TARBALL := mariadb-connector-c-3.3.8-src.tar.gz # three static lines # so that git cherry-pick # will not run into conflicts
core.git: download.lst
download.lst |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) New commits: commit c6d791e3d2577498affec491876a0afa441be002 Author: Xisco Fauli AuthorDate: Mon Mar 25 10:56:38 2024 +0100 Commit: Xisco Fauli CommitDate: Mon Mar 25 20:42:40 2024 +0100 nss: upgrade to release 3.99 Change-Id: I77ccc45854b2d0aecc288f471d94c81ad9089f85 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165273 Tested-by: Xisco Fauli Reviewed-by: Xisco Fauli diff --git a/download.lst b/download.lst index f7cacf0c43aa..d35bd6300748 100644 --- a/download.lst +++ b/download.lst @@ -477,8 +477,8 @@ MYTHES_TARBALL := mythes-1.2.5.tar.xz # three static lines # so that git cherry-pick # will not run into conflicts -NSS_SHA256SUM := 59bb55a59b02e4004fc26ad0aa1a13fe8d73c6c90c447dd2f2efb73fb81083ed -NSS_TARBALL := nss-3.98-with-nspr-4.35.tar.gz +NSS_SHA256SUM := 5f29fea64b3234b33a615b6df40469e239a4168ac0909106bd00e6490b274c31 +NSS_TARBALL := nss-3.99-with-nspr-4.35.tar.gz # three static lines # so that git cherry-pick # will not run into conflicts
[Bug 131253] Frames are displayed around images even though Object boundaries is unchecked, as Text boundaries control it
https://bugs.documentfoundation.org/show_bug.cgi?id=131253 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #5 from Justin L --- Created attachment 193300 --> https://bugs.documentfoundation.org/attachment.cgi?id=193300=edit 131253_through.docx: wrap none/through images shouldn't display a text boundary line (In reply to Heiko Tietze from comment #3) > Whether object or not, the text ends here. And the point is, View > Text > Boundary disables the thin grey lines => NAB. The text does not "end here" if the frame is wrap through (or wrap none). Note that the page's text boundaries are also not (fully) boxed in (when "show formatting marks" is turned off), just a few angle brackets are shown. It is EXTREMELY disconcerting to the user to have a border around their image, and even more so since it does not work consistently (bug 134869). I propose that the frame's "text boundaries" should only show when formatting marks are turned on. -- You are receiving this mail because: You are on the CC list for the bug.
