[Bug 100566] INTEROPERABILITY: cross reference fields can't show text spanning several paragraphs
https://bugs.documentfoundation.org/show_bug.cgi?id=100566 Mike Kaganski changed: What|Removed |Added Summary|DOCX: multiline bookmarks |INTEROPERABILITY: cross |rendered wrong |reference fields can't show ||text spanning several ||paragraphs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157724] GPG key cannot be selected in (macOS appstore MAS version)
https://bugs.documentfoundation.org/show_bug.cgi?id=157724 --- Comment #4 from Alex Thurgood --- (In reply to steve from comment #3) > The MacGPG version you checked was probably installed separately. LO comes > with gpgme, and an outdated version of that. > > @Sebastian: Could you try the standalone download and if key selection works > as expected in version 7.6.4? > https://www.libreoffice.org/download/download-libreoffice/ With the standalone version, e.g. daily master build: Version: 24.8.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 467eeda66ee444c846fcd89da1fe064dd06daa9d CPU threads: 8; OS: macOS 14.2.1; UI render: Skia/Raster; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded GPG key selection and signing works for me at least with: GPG Tools Version 1.12 (1800) However, it still doesn't work with LibreOffice from the MAS: Version: 7.5.9.2 (AARCH64) / LibreOffice Community Build ID: cdeefe45c17511d326101eed8008ac4092f278a9 CPU threads: 8; OS: Mac OS X 14.2.1; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded No GPG keys are detected or selectable under: LibreOffice Preferences > Identity > Encryption No possibility to enter a path to the Certificate manager exists under : LibreOffice Preferences > Security Basically, this is non-functional in the Mac AppStore version. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159188] High resolution problem of Position and size dialogue
https://bugs.documentfoundation.org/show_bug.cgi?id=159188 Buovjaga changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #5 from Buovjaga --- (In reply to gladys from comment #4) > Hello Buovjava, > my resolution is 1600 * 900 and my scale 100% Ok, then your screen is not suitable for testing this issue and we have to wait for someone with a HiDPI screen to test it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158249] Document with one landscape page doesn't switch back to portrait when PRINTING.
https://bugs.documentfoundation.org/show_bug.cgi?id=158249 --- Comment #8 from gmoll...@us.es --- You don't need print, only view the preview in the windows where you choice the printer (not in preview print). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158249] Document with one landscape page doesn't switch back to portrait when PRINTING.
https://bugs.documentfoundation.org/show_bug.cgi?id=158249 gmoll...@us.es changed: What|Removed |Added CC||gmoll...@us.es --- Comment #7 from gmoll...@us.es --- The error is if the page type is Letter, because if you use A4 the print is correct. In version LO 3.3 is well. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159188] High resolution problem of Position and size dialogue
https://bugs.documentfoundation.org/show_bug.cgi?id=159188 --- Comment #4 from gladys --- Hello Buovjava, my resolution is 1600 * 900 and my scale 100% -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159612] Digital signing of Writer documents using X.509 compliant signatures fails silently on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=159612 --- Comment #1 from Alex Thurgood --- Added link to bug 94903, as it seems that they relate to the same problem, but Miklos preferred them to be separately identified. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 94903] Digital Signatures are not working with 64-Bit LibreOffice 5.0.2.2 and 32-Bit LibreOffice 5.2.x in Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=94903 Alex Thurgood changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9612 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159612] Digital signing of Writer documents using X.509 compliant signatures fails silently on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=159612 Alex Thurgood changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=94 ||903 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159557] Have stopped responding! (LO v24.2)
https://bugs.documentfoundation.org/show_bug.cgi?id=159557 --- Comment #13 from Klexus --- Julien: I'm not sure if I can handle that scheme. I'm not that technical. Just a regular intermediate user. Telesto: For me it seems very identical. He also use(d) v7.6.4.1 and it's the same problem with me. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153626] Unable to sign with existing digital signature, and inconsistent UI for digital signature in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153626 --- Comment #12 from Alex Thurgood --- This bug report sounds like a DUP of bu 156352, which is marked as resolved fixed in current master daily build. @Fonzie : can you give this a try with daily build from at least Feb 7th and report back ? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108988] [META] Validity-related bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108988 Bug 108988 depends on bug 159595, which changed state. Bug 159595 Summary: Data validation without error check allows to enter data other than defined https://bugs.documentfoundation.org/show_bug.cgi?id=159595 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156352] macOS: Save as > Encrypt with GPG key results in hang / crash
https://bugs.documentfoundation.org/show_bug.cgi?id=156352 Alex Thurgood changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||3626 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153626] Unable to sign with existing digital signature, and inconsistent UI for digital signature in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=153626 Alex Thurgood changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6352 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156352] macOS: Save as > Encrypt with GPG key results in hang / crash
https://bugs.documentfoundation.org/show_bug.cgi?id=156352 --- Comment #23 from Alex Thurgood --- (In reply to Alex Thurgood from comment #22) > (In reply to Patrick Luby from comment #16) > > > > > Your fix works in my local master build. The GPGTools rows are now no longer > > empty and clicking on them no longer crashes. > > > > The fix should be in tomorrow's (05 February 2024) nightly master build. > > @steve's last crash log looks like another case of tdf#152524 so I think we > > can mark this bug as resolved/fix and, if @steve still gets tdf#152524 style > > crashes, we can continue investigation in that bug. > > I can confirm that I now see a list of the certificates including my GPG > keys in the Certificate Manager. > > Tested with (master from 07/02) > Version: 24.8.0.0.alpha0+ (AARCH64) / LibreOffice Community > Build ID: 467eeda66ee444c846fcd89da1fe064dd06daa9d > CPU threads: 8; OS: macOS 14.2.1; UI render: Skia/Raster; VCL: osx > Locale: fr-FR (fr_FR.UTF-8); UI: en-US > Calc: threaded I forgot to add that I can also sign the Writer document with one of the GPG keys and obtain a digitally signed document. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156352] macOS: Save as > Encrypt with GPG key results in hang / crash
https://bugs.documentfoundation.org/show_bug.cgi?id=156352 --- Comment #22 from Alex Thurgood --- (In reply to Patrick Luby from comment #16) > > Your fix works in my local master build. The GPGTools rows are now no longer > empty and clicking on them no longer crashes. > > The fix should be in tomorrow's (05 February 2024) nightly master build. > @steve's last crash log looks like another case of tdf#152524 so I think we > can mark this bug as resolved/fix and, if @steve still gets tdf#152524 style > crashes, we can continue investigation in that bug. I can confirm that I now see a list of the certificates including my GPG keys in the Certificate Manager. Tested with (master from 07/02) Version: 24.8.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 467eeda66ee444c846fcd89da1fe064dd06daa9d CPU threads: 8; OS: macOS 14.2.1; UI render: Skia/Raster; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159612] New: Digital signing of Writer documents using X.509 compliant signatures fails silently on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=159612 Bug ID: 159612 Summary: Digital signing of Writer documents using X.509 compliant signatures fails silently on macOS Product: LibreOffice Version: 24.8.0.0 alpha0+ Master Hardware: ARM OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ipla...@tuta.io Description: 1) Create a new Writer document, type some text in it, and save normally. 2) Now try and digitally sign the document with a X.509 compliant digital signature (I have a number of them provided by different providers for work, e.g. the European Patent Office, CertEurope (eIDAS token), World Intellectual Property Organisation. 3) Call up the Certificate Manager from the digital signatures dialog, and select a certificate. This is supposed to digitally sign the Writer document. 4) The user is returned to the document Digital Signaures dialog in which, in the event of a successful signature, the used signature included in the document is displayed in a list and the validity of that signature is indicated. In my case, that Digital Signature list window has a blank, selectable entry, i.e. you can see that there is supposed to be something in the digital signature list associated with the document, but the detail of what that signature is does not appear. A mouse hover over the blank entry calls the popup help "Lists the digital signatures for the current document." The document isn't signed at all. There is no change to the status of the document as evidenced by the Save button in the toolbar, and the dialog still shows an active "Sign" and "Start Certificate Manager" buttons. If I click on the "Sign" button in this state, I get a repeatable crash, and the recovery dialog is started. Steps to Reproduce: See description above. Actual Results: The digital signing functionality fails to work, the Writer document is never signed. Additionally, a reproducible crash can be made to occur by trying to use the "Sign" button in the pseudo-empty list of digital signatures. Expected Results: The digital signing functionality should work with X.509 certs provided by professional organisations. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 24.8.0.0.alpha0+ (AARCH64) / LibreOffice Community Build ID: 467eeda66ee444c846fcd89da1fe064dd06daa9d CPU threads: 8; OS: macOS 14.2.1; UI render: Skia/Raster; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159461] Dialog "XML Filter Settings" is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=159461 --- Comment #9 from Commit Notification --- Noel Grandin committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/83b173b9eacccf00aa7f51214fb2e3d464acf80f tdf#159461 deadlock in Dialog "XML Filter Settings" It will be available in 7.6.6. 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.
[Bug 159461] Dialog "XML Filter Settings" is broken
https://bugs.documentfoundation.org/show_bug.cgi?id=159461 Commit Notification changed: What|Removed |Added Whiteboard|target:24.8.0 target:24.2.1 |target:24.8.0 target:24.2.1 ||target:7.6.6 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157042] [Linux only] Calc crashes when closed in rtl::str::release<_rtl_uString>(_rtl_uString*) (steps in comment 27)
https://bugs.documentfoundation.org/show_bug.cgi?id=157042 --- Comment #38 from Commit Notification --- Xisco Fauli committed a patch related to this issue. It has been pushed to "libreoffice-24-2": https://git.libreoffice.org/core/commit/dd7a69068b8f92052b45a60014e6f6ed689c2947 tdf#157042: Revert "re-apply "optimize ConfigurationProperty::get()"" It will be available in 24.2.1. 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.
[Bug 157042] [Linux only] Calc crashes when closed in rtl::str::release<_rtl_uString>(_rtl_uString*) (steps in comment 27)
https://bugs.documentfoundation.org/show_bug.cgi?id=157042 Commit Notification changed: What|Removed |Added Whiteboard|target:7.6.5|target:7.6.5 target:24.2.1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159188] High resolution problem of Position and size dialogue
https://bugs.documentfoundation.org/show_bug.cgi?id=159188 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #3 from Buovjaga --- (In reply to gladys from comment #2) > Hello Stefan, > > Thank you for reporting the bug. Unfortunately I can't reproduce in > > Calc: CL threadedVersion: 7.6.4.1 (X86_64) / LibreOffice Community > Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 > CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: > win > Locale: en-GB (en_GB); UI: en-GB > Calc: CL threaded Gladys: what was the resolution of your screen and what was your display scaling? In Stefan's case, I assume he has display scaling of 200% or more. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159541] Dark background colour ignores fix font color
https://bugs.documentfoundation.org/show_bug.cgi?id=159541 --- Comment #10 from Tomaz Vajngerl --- (In reply to Heiko Tietze from comment #9) > Tomaz, you made some changes for the mentioned Calc method in > https://gerrit.libreoffice.org/c/core/+/154061. Please advise how to proceed. I didn't look into this issue - yet. My change here was mostly refactoring as we called one GetFont method, which does 2 things - prepares the font and color. But in some cases we only cared about the font and in other cases only about the font color. When we were only interested about the font we called GetFont with SC_AUTOCOL_BLACK (which always changed AUTO to black). I changed this to 2 methods fillFontOnly and fillColor (and fillFont that does both) and then call fillFontOnly() when we were not interested in the color. Maybe I did a mistake at refactoring? It is possible... -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146530] Writer converts JPG images to PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=146530 Mike Kaganski changed: What|Removed |Added Status|RESOLVED|NEW Ever confirmed|0 |1 Resolution|DUPLICATE |--- --- Comment #3 from Mike Kaganski --- An own problem, unrelated to bug 138981. In this case, LibreOffice itself controls the content of the clipboard after the program exits. There is no native Windows Clipboard format for JPEG; it could possibly be workarounded by a custom format for JPEG, but then the problem doesn't stop, because there should also be an indication which of the *several* raster formats is the original one ... likely not worth the trouble. Anyway, doers decide. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 144070] Filesave DOCX / DOC / ODT: Abnormal increase in size because no-DPI JPEG image saved as large PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=144070 Mike Kaganski changed: What|Removed |Added Status|RESOLVED|NEW Resolution|DUPLICATE |--- --- Comment #9 from Mike Kaganski --- An own problem, completely unrelated to bug 138981. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 116082] [META] Image issues related to image DPI
https://bugs.documentfoundation.org/show_bug.cgi?id=116082 Bug 116082 depends on bug 144070, which changed state. Bug 144070 Summary: Filesave DOCX / DOC / ODT: Abnormal increase in size because no-DPI JPEG image saved as large PNG https://bugs.documentfoundation.org/show_bug.cgi?id=144070 What|Removed |Added Status|RESOLVED|NEW Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.
[Bug 55004] backup copy fails when using share / samba (if nobrl cifs mount option not used)
https://bugs.documentfoundation.org/show_bug.cgi?id=55004 --- Comment #55 from Roman --- > > Now, in addition to that, I have noticed that out of two Samba servers I > have, the issue is reproducible only with ONE of them. They are different: > one is Samba on Debian server, another one is Synology NAS. When I put the > file on that NAS, the problem does not occur. Both are mounted in identical > way on the client machine. Please clarify the connection type cifs disks and the line itself in full for comparison. And it’s not clear which problem exists and which doesn’t? Просьба пожалуйста уточнить тип подключения cifs диски и саму строку полностью для сравнения. И не ясно какая проблема есть, какой нет? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135659] Images positioned wrongly after paste RTF, undo, regular paste
https://bugs.documentfoundation.org/show_bug.cgi?id=135659 Aron Budea changed: What|Removed |Added Summary|Images positioned wrongly |Images positioned wrongly |after paste RFT undo|after paste RTF, undo, |regular paste |regular paste -- You are receiving this mail because: You are the assignee for the bug.
[Bug 138981] The JPG property lost on copy/paste from clipboard (not-libreOffice internal clipboard) causing image being pasted as "unknown format" resulting in JPG to PNG conversion on save
https://bugs.documentfoundation.org/show_bug.cgi?id=138981 --- Comment #13 from Mike Kaganski --- (In reply to Telesto from comment #10) > *** Bug 146530 has been marked as a duplicate of this bug. *** (In reply to Telesto from comment #11) > *** Bug 144070 has been marked as a duplicate of this bug. *** Please don't add duplicates that aren't duplicates. This specific bug 138981 is about the *hypothetical* possibility to "detect" the original file format from the data put to clipboard on a specific OS (Windows) by an *unspecified* browser, when you copy an *unspecified* image using *unspecified* method (do you right-click the image and use an item like "copy the image to clipboard"? select the web page content starting before the image, ending after, and Ctrl+C?). This *might* be possible to improve, by analyzing HTML format that the browser puts into the clipboard; possibly browser-specific and/or OS-specific. E.g., opening https://i.imgur.com/BCftIFD.jpeg in Chrome, right-clicking it in the browser, and copying, gives these formats in my Win11's clipboard: PNG; CF_DIB5; CF_BITMAP; CF_DIB; and HTML Format, the latter only containing a fragment with the image URL. Only the latter allows to discover the source of the file, and thus, to keep the original bytes. Bug 146530 is about the content of the clipboard after closing LibreOffice itself. This is a different thing; there is no "HTML source" of the image in the clipboard; and here, the clipboard does not contain JPEG at all - just because Windows clipboard has no pre-defined standard format for JPEG images. There could be a workaround. It could be completely different on other OSes (but that would depend on the raster format preferrence; I can imagine that PNGs would always be preferred over lossy formats, when there's no way to discover what was the original format; so that would also need to provide some custom clipboard format, unusable by anything except LibreOffice, just in anticipation of users who close the program, then open it again ... even if this is implemented, it's completely different). And finally, Bug 144070 is absolutely unrelated to clipboard. It is just about some internal problem, related to a specific JPEG file in the document. E.g., if you try with a document created for bug 146530, and save it as DOCX, the resulting file will still contain a JPEG, so this is something specific. Marking all these as duplicates effectively made them hidden, and prevents people from working on these. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135659] Images positioned wrongly after paste RFT undo regular paste
https://bugs.documentfoundation.org/show_bug.cgi?id=135659 --- Comment #9 from Mike Kaganski --- Note that the bisection pointed to commit 8f8b31abd02876c3601e343b8b3274754f8a61b6, which introduced the compatibility flag to properly wrap text in MS formats; but the real problem was that pasting such an MS format (RTF) also modified the target's compat settings, so the later paste of ODF format produced a different result. In a sense, this would still be problematic, if you try to paste not into a new document after the RTF-paste-and-undo dance, but directly into an opened Word document (say, DOCX). It may need an own report. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 102593] [META] Paste bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102593 Bug 102593 depends on bug 135659, which changed state. Bug 135659 Summary: Images positioned wrongly after paste RFT undo regular paste https://bugs.documentfoundation.org/show_bug.cgi?id=135659 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135659] Images positioned wrongly after paste RFT undo regular paste
https://bugs.documentfoundation.org/show_bug.cgi?id=135659 Mike Kaganski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #8 from Mike Kaganski --- Fixed by 2d0a87f97e2c9ac50cd6ce329ca8256daf94ead4. *** This bug has been marked as a duplicate of bug 151974 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159470] Spelling and Language support in LibreOffice Writer unusable
https://bugs.documentfoundation.org/show_bug.cgi?id=159470
--- Comment #13 from Alexander Dietz ---
Here is a suggestion about the "language" menu how I could imagine how it can
be improved. Not sure how hard it would be to implement, but it seems more
consistent. I also would be available to test this or a related feature...
The suggestion is for the submenus
“Tools” → “Language” → “For Section”
“Tools” → “Language” → “For Paragraph”
“Tools” → “Language” → “For all text”
1. They all should work the same. That means a checkmark at the beginning
indicates the selected language attribute for the selected part.
2. As far as I know for "paragraph" and "all text" you do not have a checkmark
as it might take a longer time for larger text to apply a language attribute to
the "paragraph" or "all text". Maybe a popup can ask the user if he/she wants
to apply the language attributes which can take a longer time (>10 seconds).
3. Also as far as I know the languages shown in the “Tools” → “Language” are
"suggested" languages, i.e. based on the words used in these parts. That is
fine, but an indication if this suggested language is installed or not would be
really great. And if a language is not installed a click on that language would
open the language installer for this specific language.
Example
German (Germany) CLICK TO INSTALL
English (UK) INSTALLED
English (US) INSTALLED
i.e. really complete information in the list of languages clearly visible to
the user.
4. When a language is shown as "installed", it should be checked beforehand if
that language really is installed. I had some issues with some "German {de}"
language but it seem to had some issues, i.e. when selected it did not check
anything. So it maybe was not or incorrectly installed?
Let me know any questions or how I can help with testing ...
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 147953] Autosize text frame stops working
https://bugs.documentfoundation.org/show_bug.cgi?id=147953 --- Comment #16 from Mike Kaganski --- *** This bug has been marked as a duplicate of bug 151974 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151728] Pasting text from various programs silently changes various compatibility settings in Writer without the possibility of undoing it
https://bugs.documentfoundation.org/show_bug.cgi?id=151728 Mike Kaganski changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |7953| CC||loma...@gmail.com --- Comment #12 from Mike Kaganski --- *** Bug 147953 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147953] Autosize text frame stops working
https://bugs.documentfoundation.org/show_bug.cgi?id=147953 Mike Kaganski changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |1728| Resolution|WORKSFORME |DUPLICATE --- Comment #15 from Mike Kaganski --- *** This bug has been marked as a duplicate of bug 151728 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159554] Red vs. Orange background - BackgroundParaOverDrawings True vs. False
https://bugs.documentfoundation.org/show_bug.cgi?id=159554 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1974, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2158 --- Comment #3 from Mike Kaganski --- (In reply to Tex2002ans from comment #2) > - On Copy/Paste to new document, trying to carry over these compatibility > flags becomes a nightmare (and has caused many large regressions in the > past). Right. Carrying compat flags was accidentally happening in the past, and became visible after commit a7d9837a8aa6d1233f4c21e4db5d32428a3ffc58, and caused bugs 151974, 151728, 152158 (see bug 151728 comment 4). It was fixed by commit 2d0a87f97e2c9ac50cd6ce329ca8256daf94ead4. Carrying flags would mean that, while the copied data would look as it was in the source, the *already existing text* in the target document could suddenly change its formatting. It is the sad outcome of having compatibility flags at all; and we indeed try hard to allow working with external formats, with their differences in behavior. The problem here is invisibility of the compatibility flag(s) to user. Making flags accessible is of course important, but even when we add that flag to the Options->Writer->Compatibility, will anyone really find out that some specific (of tens, potentially hundreds) flag there is responsible for the difference? MS Word adds a "[Compatibility Mode]" decoration to the document's title bar. Would it help? Maybe. Yet, given the huge amount of compat flags, it is easily possible, that both of your documents are is "compatibility modes" (i.e., some of the compatibility flags are in non-default state), but in *different* compatibility modes... -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159608] PivotTables (and charts) behaving erratically
https://bugs.documentfoundation.org/show_bug.cgi?id=159608 --- Comment #6 from ehar...@gmail.com --- Right. That is the file from after the errors occurred. I will recreate it and attach it tomorrow. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106661] CTRL + mouse/scrollwheel zoom does not work in print preview, on upgrade now forcing user profile reset
https://bugs.documentfoundation.org/show_bug.cgi?id=106661 --- Comment #19 from Mike Kaganski --- (In reply to V Stuart Foote from comment #18) > Cleared (renamed) old profile from 7.6.4, allowing a new 24.2.0 profile to > be built and retest mousewheel zoom for the Print Preview. With new profile, > no issue with the zoom in or out. It would be nice to try to nail down which setting(s) cause the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159605] CPU cycles on file-open increased with factor 4
https://bugs.documentfoundation.org/show_bug.cgi?id=159605 --- Comment #3 from Telesto --- FWIW: the file shows but is unresponsive for editing until the loading finishes -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158089] Crash when using undo command while using macros
https://bugs.documentfoundation.org/show_bug.cgi?id=158089 --- Comment #7 from Matt K --- I tried to bibisect the bug using https://bibisect.libreoffice.org/win32-5.3, but the bug seems to be timing related and does not occur consistently, so I could not get a valid result. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106661] CTRL + mouse/scrollwheel zoom does not work in print preview, on upgrade now forcing user profile reset
https://bugs.documentfoundation.org/show_bug.cgi?id=106661 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156706] libre office calc macro screen record error
https://bugs.documentfoundation.org/show_bug.cgi?id=156706 --- Comment #2 from QA Administrators --- Dear yolcumehmet, 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 159188] High resolution problem of Position and size dialogue
https://bugs.documentfoundation.org/show_bug.cgi?id=159188 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159348] Highlight cell does not repaint on when window is maximized
https://bugs.documentfoundation.org/show_bug.cgi?id=159348 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 87058] column label functions do not update after inserting rows below title - needs save and reload including a hard recalc
https://bugs.documentfoundation.org/show_bug.cgi?id=87058 --- Comment #16 from QA Administrators --- Dear aaker, 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 156690] When LibreOffice Calc is maximized, UI moves behind the action bar (i.e. GNOME dock)
https://bugs.documentfoundation.org/show_bug.cgi?id=156690 --- Comment #4 from QA Administrators --- Dear shiv.baratam, 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 130321] Cannot focus on Frame dragged into Header area until anchor changed "to page"
https://bugs.documentfoundation.org/show_bug.cgi?id=130321 --- Comment #4 from QA Administrators --- Dear sdc.blanco, 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 103069] Context synonyms menu does not show tags available on the corresponding thesaurus
https://bugs.documentfoundation.org/show_bug.cgi?id=103069 --- Comment #5 from QA Administrators --- Dear Tiago Santos, 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 159611] New: Explain the weird version jump in the release notes
https://bugs.documentfoundation.org/show_bug.cgi?id=159611 Bug ID: 159611 Summary: Explain the weird version jump in the release notes Product: LibreOffice Version: 24.2.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ddascalescu+freedesk...@gmail.com CC: olivier.hal...@libreoffice.org The jump from v7 to v24 seems weird, and it's not explained in the release notes at https://wiki.documentfoundation.org/ReleaseNotes/24.2 Others have noticed it as well: - https://www.elevenforum.com/t/libreoffice-version-jump-seems-odd.22080/ - https://ask.libreoffice.org/t/why-are-recent-dev-builds-for-version-24-x/92449 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159608] PivotTables (and charts) behaving erratically
https://bugs.documentfoundation.org/show_bug.cgi?id=159608 --- Comment #5 from m_a_riosv --- There is no PT on Felicia, only the values of a PT, no option for PT right-clicking on that cells. The same with the PT on Graphs. In weekly report there are more than two PT not only two. Maybe those that should have been on Graphs and Felicia. Could you try creating a file from scratch, and saving every new PT, to test if there is something wrong? Do you know that it is possible to create PT chart?: https://help.libreoffice.org/latest/en-US/text/scalc/guide/pivotchart.html?DbPAR=CALC#bm_id541525139738752 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158089] Crash when using undo command while using macros
https://bugs.documentfoundation.org/show_bug.cgi?id=158089 --- Comment #6 from Matt K --- In latest master, the example file crashes for me when I try to load the document (sometimes it requires high CPU load, sometimes it just crashes without much CPU load), so it is not so easy to debug. Perko, can you please try to delete some of the macros and see if it reproduces, maybe you can isolate where the problem is that way. Please provide a sample document with a smaller set of macros. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159581] Calc version 24.2.0.3 page format crash after opening existing xlsx file - fals row height and char color in some combination
https://bugs.documentfoundation.org/show_bug.cgi?id=159581 Justin L changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | Hardware|x86-64 (AMD64) |All -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159589] Math baseline alignment doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=159589 --- Comment #9 from Regina Henschel --- Duplicate to bug 159302? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159607] RegEx based search should apply to entire document, not just current paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=159607 V Stuart Foote changed: What|Removed |Added Summary|Bugs should be fixed and|RegEx based search should |not turned into "expected |apply to entire document, |behavior" to avoid that.|not just current paragraph CC||vsfo...@libreoffice.org Severity|normal |enhancement Alias|document, entire, for, | |RegEx, Search | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159609] Formula object is no longer vertically centered within a sentence
https://bugs.documentfoundation.org/show_bug.cgi?id=159609 V Stuart Foote changed: What|Removed |Added Component|Writer |Formula Editor -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159302] Formula OLE in a line of text or its full height frame is now misaligned vertically, due to change of sm map units
https://bugs.documentfoundation.org/show_bug.cgi?id=159302 V Stuart Foote changed: What|Removed |Added CC||chiensy...@hotmail.com --- Comment #11 from V Stuart Foote --- *** Bug 159609 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159609] Formula object is no longer vertically centered within a sentence
https://bugs.documentfoundation.org/show_bug.cgi?id=159609 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- Thanks for filing, known issue with map units for the Math formula editor please follow in the dupe. *** This bug has been marked as a duplicate of bug 159302 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159608] PivotTables (and charts) behaving erratically
https://bugs.documentfoundation.org/show_bug.cgi?id=159608 --- Comment #4 from ehar...@gmail.com --- Created attachment 192441 --> https://bugs.documentfoundation.org/attachment.cgi?id=192441=edit I recreated this file after the prior file had the errors. The tab "Felicia" is the individual user report I had created separately for each employee in the data. The errors repeated so I stopped. Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; 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 159610] Used "Frame Styles" Not Appearing in Styles Sidebar with "Applied Styles" Selected
https://bugs.documentfoundation.org/show_bug.cgi?id=159610 m_a_riosv changed: What|Removed |Added Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW --- Comment #2 from m_a_riosv --- Reproducible Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 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 + Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4d381b54d1c598c181b4a21a8bf0db86eb4668d1 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159608] PivotTables (and charts) behaving erratically
https://bugs.documentfoundation.org/show_bug.cgi?id=159608 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m_a_riosv --- Please attach a sample file, reduce the size as much as possible without private information, and paste the information in Menu/Help/About LibreOffice, there is a copy icon. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159607] Bugs should be fixed and not turned into "expected behavior" to avoid that.
https://bugs.documentfoundation.org/show_bug.cgi?id=159607 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|NEW |UNCONFIRMED Ever confirmed|1 |0 --- Comment #4 from m_a_riosv --- Please don't set up your own reports as NEW, some else must do it, well except you are going to fix it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159605] CPU cycles on file-open increased with factor 4
https://bugs.documentfoundation.org/show_bug.cgi?id=159605 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m_a_riosv --- Open instantly for me with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4d381b54d1c598c181b4a21a8bf0db86eb4668d1 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159606] My sparklins are gone after closing (saving) the document
https://bugs.documentfoundation.org/show_bug.cgi?id=159606 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #5 from m_a_riosv --- What file format do you use to save? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159610] Used "Frame Styles" Not Appearing in Styles Sidebar with "Applied Styles" Selected
https://bugs.documentfoundation.org/show_bug.cgi?id=159610 Tex2002ans changed: What|Removed |Added Blocks||103427 CC||rayk...@gmail.com, ||Tex2002ans+LibreOffice@gmai ||l.com --- Comment #1 from Tex2002ans --- CCing Jim on this (since he does a lot of Styles/sidebar work). Also adding "Sidebar-Styles" metabug. - - - Oh, and Bug #159554 was where I first found it 3 days ago. I was messing with the "ODT file with Frames" that user submitted, and was trying to spot anything strange with the formatting. - I always have "Applied Styles" on, so when I saw 0 Frames showing, I didn't think anything of it. - Maybe thought it was made using Direct Formatting. When I looked a little closer though, and: - Flicked on "All Styles" I saw the user actually DID use Frame Styles. - - - I was also able to do this with my own fresh ODT document too: 0. Open fresh ODT. 1. Insert > Frame > Frame Interactively. 2. Drag a rectangle onto the document. 3. View > Styles (F11) - To make Styles sidebar appear. 4. Along the icons at very top of sidebar: - Click "Frame Styles" button. 5. In sidebar: - Right-Click > New... 6. In "Organizer" tab: - Give my new Frame Style a name. - Press OK. 7. In document: - Left-Click/Select my frame. 8. In Styles sidebar: - Double-Click on my newly created Frame Style. Then I could: - Go from "All Styles" -> "Applied Styles" in the dropdown. and my newly created Frame Style does not appear either. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103427 [Bug 103427] [META] Styles and Formatting sidebar deck and floating window -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103427] [META] Styles and Formatting sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103427 Tex2002ans changed: What|Removed |Added Depends on||159610 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159610 [Bug 159610] Used "Frame Styles" Not Appearing in Styles Sidebar with "Applied Styles" Selected -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158653] Comment commands in Calc's menus need to be rearranged
https://bugs.documentfoundation.org/show_bug.cgi?id=158653 --- Comment #5 from ady --- I am not convinced that changing the menus for Comments is the best path forward. The standard menus in Calc are grouped mostly by action (e.g. Edit/View/Insert), not so much by type of object. Older users are used to the current menus. Are there any spreadsheet tools that have these comment-related commands grouped in a different way than Calc? We also have several other ways to access the same actions, especially since some recent changes that added more comment-related actions from the cell's context menu and from the Navigator. This lowers the relevance of modifying the menus. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159610] New: Used "Frame Styles" Not Appearing in Styles Sidebar with "Applied Styles" Selected
https://bugs.documentfoundation.org/show_bug.cgi?id=159610 Bug ID: 159610 Summary: Used "Frame Styles" Not Appearing in Styles Sidebar with "Applied Styles" Selected Product: LibreOffice Version: 24.2.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tex2002ans+libreoff...@gmail.com Description: When there are Frame Styles used inside a document, choosing: - "Hierarchical" shows them all. - "All Styles" shows them all. - "Applied Styles" shows 0. - Even if Frames exist and are used within a document. I first noticed this while debugging another document (+ trying to test new "Spotlight" feature). Steps to Reproduce: 0. Download attachment #192386 + Open "right.odt". - It is a ZIP file with 2 ODTs inside. - It uses a Frame Style called "StatBlock-Narrow-Background". Then: 1. View > Styles (F11) - Styles sidebar appears. 2. Along the icons at very top of sidebar: - Click "Frame Styles" button. 3. In the dropdown at the very bottom of sidebar: - Change from "Hierarchical" or "All Styles" -> "Applied Styles". Actual Results: "Applied Styles" has 0 Frame Styles showing. Expected Results: "Applied Styles" should show the actual Frame Styles currently used inside the document. In this specific case: - StatBlock-Narrow-Background Reproducible: Always User Profile Reset: No Additional Info: Tested in this version: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 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 - - - Note: LO IS seeing/detecting that the Style exists if you have "All Styles" or "Hierarchical" selected. During Step 3: - Choose "All Styles". 4. Inside the document: - Click on the border of the frame. - You'll see "StatBlock-Narrow-Background" highlight itself in the sidebar. So it looks to be detecting fine... just not transferring that information over to the "Applied Styles" version. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159597] Bold selection over a text line deletes a line
https://bugs.documentfoundation.org/show_bug.cgi?id=159597 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m_a_riosv --- Please test in safe mode, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158653] Comment commands in Calc's menus need to be rearranged
https://bugs.documentfoundation.org/show_bug.cgi?id=158653 --- Comment #4 from ady --- (In reply to Eyal Rozenberg from comment #3) > There's no "Edit Comment" on the menus, I think. We have it in the context > menu, but that's not supposed to change. In LO 7.6 we have menu Sheet > Cell Comments > Edit / Hide / Show / Delete / Delete All Comments. Quote from comment 0: 'there is "Sheet - Cell Comments" that appear to host the remaining comment commands'. The Insert and View menus include every kind of artifact that could be inserted or shown/hidden (respectively) in a spreadsheet (including Comments). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159409] Dialog Properties bigger then screen
https://bugs.documentfoundation.org/show_bug.cgi?id=159409 --- Comment #5 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #4) > Is this some facet of os/DE scaling in place? To clarify: raal, can you please check whether your display is scaled-up somehow? Using your physical monitor, or using your desktop environment settings? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 55004] backup copy fails when using share / samba (if nobrl cifs mount option not used)
https://bugs.documentfoundation.org/show_bug.cgi?id=55004 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2463 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159581] Calc version 24.2.0.3 page format crash after opening existing xlsx file - fals row height and char color in some combination
https://bugs.documentfoundation.org/show_bug.cgi?id=159581 raal changed: What|Removed |Added Regression By||Justin Luth CC||jl...@mail.com, ||r...@post.cz OS|Windows (All) |All Keywords||bibisected, bisected, ||regression --- Comment #12 from raal --- This seems to have begun at the below commit in bibisect repository/OS linux-64-24.2. Adding Cc: to Justin Luth ; Could you possibly take a look at this one? Thanks b3c14523e3d622babc44ea6b0bc7e5c24eb14c00 is the first bad commit commit b3c14523e3d622babc44ea6b0bc7e5c24eb14c00 Author: Jenkins Build User Date: Tue Jul 11 19:46:40 2023 +0200 source sha:d15c4caabaa21e0efe3a08ffbe145390e802bab9 140260: tdf#123026 xlsx import: recalc optimal row height on import | https://gerrit.libreoffice.org/c/core/+/140260 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159609] New: Formula object is no longer vertically centered within a sentence
https://bugs.documentfoundation.org/show_bug.cgi?id=159609 Bug ID: 159609 Summary: Formula object is no longer vertically centered within a sentence Product: LibreOffice Version: 24.2.0.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: chiensy...@hotmail.com Description: For Writer 24.2.0.3 (X86_64), when a formula object is inserted as a character within a sentence, instead of being vertically centered as before, the object is vertically aligned at the top. As an example, in the old version, the formula object was displayed as below. +---+ The result of the expression | x + 2 | is 3. +---+ In the new version, the object is displayed as The result of the expression +---+ is 3. | x + 2 | +---+ Please let me know if this is a bug, or if there is a setting which I can modify. Thanks. Steps to Reproduce: 1. In a Writer document, write a sentence. 2. Insert a formula object within the sentence. 3. Create any mathematical expression in the object. Actual Results: The formula object IS NOT vertically centered within the sentence. Expected Results: The formula object should be vertically centered within the sentence. Reproducible: Always User Profile Reset: No Additional Info: Version 24.2.0.3 (X86_64) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159539] Setting paragraph direction is not possible in LibreOffice viewer experimental editor
https://bugs.documentfoundation.org/show_bug.cgi?id=159539 Hossein changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |hoss...@libreoffice.org |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158653] Comment commands in Calc's menus need to be rearranged
https://bugs.documentfoundation.org/show_bug.cgi?id=158653 --- Comment #3 from Eyal Rozenberg --- I wouldn't mind collecting all Comment-related menu items into an Edit | Comments submenu. No strong opinion either way though. (In reply to Heiko Tietze from comment #2) > What could be the home of "Edit comment" or "Delete all comments"? There's no "Edit Comment" on the menus, I think. We have it in the context menu, but that's not supposed to change. "Delete all comments" fits nicely under Edit | Comments, I think. Or am I misunderstanding your question? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 38261] Better Find with regular expressions
https://bugs.documentfoundation.org/show_bug.cgi?id=38261 --- Comment #28 from Adalbert Hanßen --- It works, but not very stable. From time to time it issues error messages and you end up in a macro definition screen. Also AltSearch is terribly slow. The AltSearch functionality including its ability to store and to reapply stored search patterns plus the ability to uses PCRE regex expressions with all quantifiers (see comment 25) plus the ability to search for character styles, paragraph styles and son on should be in LO Writer itself. The syntax and the way storing/retrieving search patterns should follow the model from AltSearch 1.4.2. That's designed very well. But it has been realized not so well. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159608] PivotTables (and charts) behaving erratically
https://bugs.documentfoundation.org/show_bug.cgi?id=159608 --- Comment #2 from ehar...@gmail.com --- More info on the related PivotTable problem: the PivotTable I recreated is already dead, after saving, closing, and re-opening the workbook. I am unable to click any of the drop down lists in the PivotTable, it functions like any other table. HOWEVER, I can right click and get to the PivotTable menu, so I clicked Properties and I can see that the Destination reference has changed. It is still to Selection and the cell is the same but again, the sheet name is the previous sheet in the list (the one positioned directly before this one). So I had entered and am looking at "$Felicia.$A$8" but now the PivotTable Properties read "$Levels.$A$8". These problems ALL follow a common pattern. Part of the references for PivotTables and for Charts are being replaced with the name of the previous sheet. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159557] Have stopped responding! (LO v24.2)
https://bugs.documentfoundation.org/show_bug.cgi?id=159557 --- Comment #12 from Telesto --- bug 159604 describes the same issue, IMHO. Both have the same locale and UI language (Locale: nb-NO (nb_NO); UI: nb-NO): coincidence? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159608] PivotTables (and charts) behaving erratically
https://bugs.documentfoundation.org/show_bug.cgi?id=159608 --- Comment #1 from ehar...@gmail.com --- After additional testing: the charts issue appears to be this. The references in the ranges for the Data Series entries DO change. The cells are the same, but the reference begins with the sheet name of the previous sheet. so what was entered as "$Felicia.$J$13:$J$18" changes to "$Levels.$J$13:$Felicia.$J$18" and this happens every time the workbook is saved, closed, and reopened (I used the File - Recent Documents menu to retrieve it). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159604] LibreOffice crashes every time I use Writer.
https://bugs.documentfoundation.org/show_bug.cgi?id=159604 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9557 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159557] Have stopped responding! (LO v24.2)
https://bugs.documentfoundation.org/show_bug.cgi?id=159557 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9604 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159156] Enhancement request : Freeze Zoom as a global LibreOffice preference
https://bugs.documentfoundation.org/show_bug.cgi?id=159156 --- Comment #14 from Eyal Rozenberg --- I want to consider three actionable things we could do in tackling this issue: 1. Add support for locking the zoom factor 2. Add support for ignoring zoom-in/zoom-out indications coming from the keyboard (through the desktop environment or windowing system I suppose?) 3. Introduce mechanism for unifying/harmonizing aspects of zoom-related behavior, such as zoom lock or ignoring trackpad zoom indications - or add zoom lock to an existing mechanism of haromizing across modules. I am ignoring the issue of the usability/configurability of the Reset-Zoom-to-100%, because that really should be a separate bug, if at all. I also suggest that consideration of (3.) be deferred until we have settled this matter at the per-module level. And it is certainly of much lower significance/priority than a per-module solution to this problem, as at worst - one could make a few per-module settings. So, we're left with (1.) and (2.) ; OP did not actually ask for (2.), but that is something I believe we should offer. That way, the user can still intentionally change the zoom through the menus, and it's just the unintentional scroll-zooming which will go away. Otherwise, when the user wants to change the zoom, they'll need to do three things: unlock, change, lock. Cumbersome. If (2.) was out of the question I'd be ok with (1.), but I really don't think that should be necessary. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159607] Bugs should be fixed and not turned into "expected behavior" to avoid that.
https://bugs.documentfoundation.org/show_bug.cgi?id=159607 --- Comment #3 from -t --- (In reply to -t from comment #2) > importance should be changed to major since this has been a problem for a > substantial number of users for over two decades over 10 years, not 20 lol -- You are receiving this mail because: You are the assignee for the bug.
[Bug 38261] Better Find with regular expressions
https://bugs.documentfoundation.org/show_bug.cgi?id=38261 -t changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9607 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159607] Bugs should be fixed and not turned into "expected behavior" to avoid that.
https://bugs.documentfoundation.org/show_bug.cgi?id=159607 -t changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=38 ||261 Hardware|IA64 (Itanium) |Other OS|Windows (All) |All -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159607] Bugs should be fixed and not turned into "expected behavior" to avoid that.
https://bugs.documentfoundation.org/show_bug.cgi?id=159607 --- Comment #2 from -t --- importance should be changed to major since this has been a problem for a substantial number of users for over two decades -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159607] Bugs should be fixed and not turned into "expected behavior" to avoid that.
https://bugs.documentfoundation.org/show_bug.cgi?id=159607 -t changed: What|Removed |Added URL||https://extensions.libreoff ||ice.org/en/extensions/show/ ||alternative-dialog-find-rep ||lace-for-writer -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159607] Bugs should be fixed and not turned into "expected behavior" to avoid that.
https://bugs.documentfoundation.org/show_bug.cgi?id=159607 --- Comment #1 from -t --- Created attachment 192440 --> https://bugs.documentfoundation.org/attachment.cgi?id=192440=edit Notepad++ example of "Extended Mode" search Explained at https://npp-user-manual.org/docs/searching/#extended-search-mode -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159608] New: PivotTables (and charts) behaving erratically
https://bugs.documentfoundation.org/show_bug.cgi?id=159608 Bug ID: 159608 Summary: PivotTables (and charts) behaving erratically Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ehar...@gmail.com Description: Okay, so I've been using LibreOffice for over a decade and I was a Microsoft Excel User Expert (and trainer) before that. I've extensively tested this issue, but I cannot figure out why it's happening. It has been happening through several updates but only over the last year or so. Before that, these workbooks I created and the related tables and charts worked fine for nearly 10 years. Here are the details. I created a data table (named range on a separate sheet) and then I created a PivotTable from the named range on another sheet (the report, if you will). In addition to that, I created a graph that uses the PivotTable ranges as the Data Ranges for the graph. Initially, everything looks great. Issue #1: After saving the document, the Charts are completely messed up. Issue #1.1 The data was appended to the Categories. Specifically, the categories were dates and were all listed first with no graph data, then the graph data was listed with blank categories. This happened to ALL the graphs in the sheet in exactly the same way. So I went back into the Data Ranges for the chart but they are all pointing to the correct data ranges with the correct data in them. Clicking OK after checking changes nothing. FIX: Reselect the exact same ranges and then click OK. Fixes the charts every time. Issue #1.2: The Names of the Data Ranges are messed up. Specifically, the Names are from several cells concatenated to each other. For example, if the Name was supposed to be a person's name, say "Sam", the Name suddenly changes to "Sam Jane Date". This all seems arbitrary, but looks like it is the data from several adjacent cells. Again, checking the reference in Data Ranges shows that the reference is pointing only to one cell and the correct cell. Nothing has changed from when I originally input the reference. Again, clicking OK does nothing but reselecting the same exact reference and then clicking OK does fix the issue immediately. Issue #2: The Filter on the PivotTable disappears. Specifically, whatever was selected in the Filter remains as the data in the cell but the drop down list goes away and the cell is just a normal cell. All the other drop down lists and related functionality disappear as well: Data cannot be clicked, etc. All the PivotTable formatting remains AND right clicking inside the table shows the PivotTable menu. However, if you go back to Properties and try to recreate the PivotTable, you get the warning that data exists and should you overwrite it? Clicking YES will replace the PivotTable but now with a completely unusable table (i.e., the PivotTable is now gone). I cannot find the trigger for these errors. They have happened BEFORE I have closed the document and AFTER saving the document. They have happened AFTER reopening the document. I tried updating LibreOffice, closing the program completely, rebooting, and then creating a brand new document and completely recreating the document from scratch. After just a few minutes, the errors happened again. Steps to Reproduce: 1. Create a named range on a sheet with multiple columns of data 2. Create a PivotTable on a separate sheet referencing the named range 3. Create a Chart based on the PivotTable 4. I cannot figure out whether the PivotTable needs to be Filtered, mine is. 5. I cannot figure out what triggers the error. After working with the workbook, adding additional sheets, saving, reopening, etc, the problems all occur. Some occurred immediately after saving the document and before I had even closed it. Actual Results: Already mentioned in the outline above Expected Results: Already mentioned in the outline above Reproducible: Always User Profile Reset: No Additional Info: Already mentioned in the outline above -- You are receiving this mail because: You are the assignee for the bug.
[Bug 126513] BackgroundParaOverDrawings missing in compatibility settings
https://bugs.documentfoundation.org/show_bug.cgi?id=126513 Tex2002ans changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9554 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159554] Red vs. Orange background - BackgroundParaOverDrawings True vs. False
https://bugs.documentfoundation.org/show_bug.cgi?id=159554 Tex2002ans changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||mikekagan...@hotmail.com, ||Tex2002ans+LibreOffice@gmai ||l.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||6513 Ever confirmed|0 |1 --- Comment #2 from Tex2002ans --- I can confirm this on: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 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 - - - The root cause was a compatibility setting called: - BackgroundParaOverDrawings The "Right" file had: - BackgroundParaOverDrawings = true The "Wrong" file had: - BackgroundParaOverDrawings = false where: - Right = Red background - Wrong = Orange/Peach background (+ slightly different formatting) - - - Note #1: Me and Mike Kaganski live-debugged this one together a few days ago, so I am CCing him. - - - Note #2: Adding "Bug #126513" to See Also, based on Kaganski's detective-work. >From what he was telling me, I believe it was: - A setting that is possible to READ, but currently no way for LO to actually tweak/change/adjust after. - On Copy/Paste to new document, trying to carry over these compatibility flags becomes a nightmare (and has caused many large regressions in the past). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159607] Bugs should be fixed and not turned into "expected behavior" to avoid that.
https://bugs.documentfoundation.org/show_bug.cgi?id=159607 -t changed: What|Removed |Added Alias||Search, entire, document, ||for, RegEx -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159607] Bugs should be fixed and not turned into "expected behavior" to avoid that.
https://bugs.documentfoundation.org/show_bug.cgi?id=159607 -t 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 159607] Bugs should be fixed and not turned into "expected behavior" to avoid that.
https://bugs.documentfoundation.org/show_bug.cgi?id=159607 -t changed: What|Removed |Added Version|7.4.7.2 release |7.4.6.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159607] New: Bugs should be fixed and not turned into "expected behavior" to avoid that.
https://bugs.documentfoundation.org/show_bug.cgi?id=159607 Bug ID: 159607 Summary: Bugs should be fixed and not turned into "expected behavior" to avoid that. Product: LibreOffice Version: 7.4.7.2 release Hardware: IA64 (Itanium) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: t.ritzie...@gmail.com Description: The documentation states "A search using a regular expression will work only within one paragraph. To search using a regular expression in more than one paragraph, do a separate search in each paragraph." THIS IS A BUG, not a feature, and needs to be fixed, since A REGULAR EXPRESSION MAY INCLUDE ONE OR MANY PARAGRAPH BREAKS. Obviously this is an archaic way of avoiding a bug, or limitation, that prevented the search feature from working correctly when CR/LFs were encountered. Steps to Reproduce: 1.Open help file:///C:/Program%20Files/LibreOffice/help/en-US/text/swriter/guide/search_regexp.html?=WRITER=WIN 2. Observe tip: "A search using a regular expression will work only within one paragraph. To search using a regular expression in more than one paragraph, do a separate search in each paragraph." 3. Fail. Because your intended search "Find" includes a line break in the middle. Actual Results: Search online in vain for a workaround. Find one AltSearch extension, 5 years out of date, unsupported on current LO version. Expected Results: I expect to be able to form a search term that is supported by MS Word and/or Notepad++. Reproducible: Always User Profile Reset: No Additional Info: It should support searching an entire document even when regular expressions are used. Optimally it should support searching an entire document when using a Boost regular expression engine. At the very least it should support searching an entire document when using BASIC EXTENDED CODES, please see https://npp-user-manual.org/docs/searching/#extended-search-mode for examples. Also see https://github.com/notepad-plus-plus/notepad-plus-plus and https://extensions.libreoffice.org/en/extensions/show/alternative-dialog-find-replace-for-writer -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155303] Asking for a new functionality: to draw or handwrite in Impress or Write
https://bugs.documentfoundation.org/show_bug.cgi?id=155303 puigp...@gmail.com changed: What|Removed |Added CC||puigp...@gmail.com --- Comment #2 from puigp...@gmail.com --- Created attachment 192439 --> https://bugs.documentfoundation.org/attachment.cgi?id=192439=edit Example of what I mean with tap to draw (request for Libre Office) The request is to be able to prepare some slides and to add some underlining, some handwriting, etc, on my slides or document. Power Point has this feature,it is a pity tha tLibr eOffice does not have it. It would be very useful to prepare the slides for my physics classes... Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159557] Have stopped responding! (LO v24.2)
https://bugs.documentfoundation.org/show_bug.cgi?id=159557 Julien Nabet changed: What|Removed |Added Keywords||wantBacktrace --- Comment #11 from Julien Nabet --- Would it be possible you retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace) Information in a bt may provide hints about root cause. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159557] Have stopped responding! (LO v24.2)
https://bugs.documentfoundation.org/show_bug.cgi?id=159557 --- Comment #10 from Klexus --- I have been annoyed by this bizarre issue and find it strange that no one else have this problem as it also happens exactly the same to my secondary desktop computer which is a AMD Phenom, DDR2 with Windows 10 Home x64. I can't use either 7.6.4 or 24.2, but no problem with 7.5.9. I do experince that it works good on some computers and not good on others. Would like to provide a video of this (if it's allowed): https://www.youtube.com/watch?v=9wokX_qPFEQ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159597] Bold selection over a text line deletes a line
https://bugs.documentfoundation.org/show_bug.cgi?id=159597 ady changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
