[Bug 104867] Impress does not compress repeated(copied) images with Minimize Presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=104867 Buovjaga changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=98259 Bug 98259 depends on bug 157649, which changed state. Bug 157649 Summary: Dialog button accelerators should work without Alt key on Windows https://bugs.documentfoundation.org/show_bug.cgi?id=157649 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158545] UI: Original size button in image properties -> position and size tab doesn't restore original size for paper size exceeding images in Writer (and breaks image ratio)
https://bugs.documentfoundation.org/show_bug.cgi?id=158545 --- Comment #6 from Miklos Vajna --- (In reply to Heiko Tietze from comment #4) > Miklos, Mike: any insights why Writer prevents to exceed the page size? One reason my be consistency. Writer defaults to capturing drawing objects inside the page frame. sw/source/core/doc/DocumentSettingManager.cxx:76 has a compat setting named DoNotCaptureDrawObjsOnPage to decide if we want this capturing or not, capturing is on by default. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107830] [META] DOCX (OOXML) paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107830 Bug 107830 depends on bug 158999, which changed state. Bug 158999 Summary: Incorrect rendering of empty paragraph with escapement set to superscript https://bugs.documentfoundation.org/show_bug.cgi?id=158999 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158992] "Spotlight" Should Only Number/Color Styles That Actually Appear in Document
https://bugs.documentfoundation.org/show_bug.cgi?id=158992 Jim Raykowski changed: What|Removed |Added Keywords||needsUXEval --- Comment #6 from Jim Raykowski --- (In reply to Tex2002ans from comment #5) > (In reply to Jim Raykowski from comment #4) > > Hi Tex2002ans, > > > > Does the attached demo track with your proposal? > > Yes, Jim! That's EXACTLY how I imagined it! :P Alright then, let's see what advise UX might have. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 104238] [META] Impress image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=104238 Bug 104238 depends on bug 104867, which changed state. Bug 104867 Summary: Impress does not compress repeated(copied) images with Minimize Presentation https://bugs.documentfoundation.org/show_bug.cgi?id=104867 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 104867] Impress does not compress repeated(copied) images with Minimize Presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=104867 Maxim Britov changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #10 from Maxim Britov --- Fixed. Tested with LO 7.5.9.2 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159010] New: FIREBIRD: Text in queries will be followed by many spaces
https://bugs.documentfoundation.org/show_bug.cgi?id=159010 Bug ID: 159010 Summary: FIREBIRD: Text in queries will be followed by many spaces Product: LibreOffice Version: 7.6.4.1 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de Created attachment 191747 --> https://bugs.documentfoundation.org/attachment.cgi?id=191747&action=edit Testdatabase - execute queries in Tools → SQL. Let you show the output. Open the attached database. Go to Tolls → SQL. Press "Show output of "select" statements. Run SELECT "ID", 'Street' "S", "Street", 'PC' "P", "Postcode", "Town" FROM "tbl_address" You will see the folloing output: 1,Street ,Pappelallee 13a,PC ,67891,Nowhere, Direct input for text content will be followed by Spaces, which expands the text to 4* (2 charcters → 8 charactes with spaces …) Run SELECT "ID", TRIM ( BOTH FROM 'Street' ) "S", "Street", TRIM ( BOTH FROM 'PC' ) "P", "Postcode", "Town" FROM "tbl_address" and the spaces have been gone. The 2 queries will contain the code for this also. Detected this problem while exporting queries into *.txt (*.xml) files. Seems it is connected to the behavior of Firebird with character lengths. It had been a problem some times ago. The character length for Firebird in LO had been moved down from 32.767 bytes to 8.191 chars for UTF8 code (32.767/4 = 8.191). Detected this here in all installed versions of LO, special LO 7.6.4.1 on OpenSUSE Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 116643] Crash when playing PPTX slide with MP4 video (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=116643 Buovjaga changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #19 from Buovjaga --- (In reply to Matt K from comment #18) > I'm not able to reproduce a crash or freeze on Windows 11 with the following > build: > > Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community > Build ID: 205dd919179f34815d7e16c8dc73d2a7efd34535 > CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: > win > Locale: en-US (en_US); UI: en-US > Calc: threaded > > The slide transitions are a little laggy, but I was able to view the full > show. Is this a Linux only issue (marking NEEDINFO)? Also, it seems LO > doesn't support mp4 video via Insert->Audio or Video... > > So, is this bug to prevent the crash by preventing an mp4 from playing, or > is it to implement support for mp4? It still hangs with the steps from comment 7 on kf5, gtk3 and gen. I am able to Alt-Tab away from the slideshow and kill LibreOffice. With gtk3 and gen, I saw the video play for about 1 second before freezing. mp4 container format is supported and I don't think we want to drop support for it. I am not sure of the root cause here. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158992] "Spotlight" Should Only Number/Color Styles That Actually Appear in Document
https://bugs.documentfoundation.org/show_bug.cgi?id=158992 --- Comment #5 from Tex2002ans --- (In reply to Jim Raykowski from comment #4) > Hi Tex2002ans, > > Does the attached demo track with your proposal? Yes, Jim! That's EXACTLY how I imagined it! :P -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145298] Keyboard Shortcuts partially unassignable with LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=145298 Dieter changed: What|Removed |Added URL|https://shake-shack-menu.in | |fo/shake-shack-schaumburg/ | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145298] Keyboard Shortcuts partially unassignable with LibreOffice Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=145298 shakeshackmenu01 changed: What|Removed |Added URL||https://shake-shack-menu.in ||fo/shake-shack-schaumburg/ --- Comment #12 from shakeshackmenu01 --- This popular burger chain is known for its high-quality ingredients and made-to-order burgers, fries, and shakes. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158997] Calc Format>Columns>Optimal Width [OK] causes some columns to be too narrow
https://bugs.documentfoundation.org/show_bug.cgi?id=158997 --- Comment #10 from ady --- Please note that it also depends on Font type, Font size and Zoom factor. For instance, use Liberation Mono as font > no repro. It also depends on content. For instance, in attachment 191723, change cell F2 to contain "111" (without quotes) and it is easier to reproduce, but change the content to "888" (without quotes) and repeat the procedure; then the content is seen (not the "###"). Same goes for cell B2, "11" makes it easier to repro, but with "88", no repro in that cell. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158890] FORMATTING: Custom number format trailing 0 replaced with figure space
https://bugs.documentfoundation.org/show_bug.cgi?id=158890 --- Comment #7 from ady --- I just performed a test. Whether it is of any utility or validity, IDK. 1. In Calc: A1: =1&UNICHAR(HEX2DEC(2007))&1 A2: =1&UNICHAR(HEX2DEC(20))&1 Note that the result is text containing U+2007 and U+0020 respectively, not a formatted numeric value using "?" as part of its number format code. 2. Select both cells and copy them. 3. Open some simple text editor. On MS Windows this could be notepad.exe. 4. Paste the previously-copied cells into the text editor. 5. For the text editor, select the (previously-pasted) text and apply a basic font that doesn't support U+2007. On MS Windows, this could be, for instance, the old "Courier" (not to be confused with "Courier New"). The result in the text editor shows a special symbol in place of the original U+2007 character. IDK whether this procedure shows some kind of potential problem when either exporting or importing data when the rendered characters would include U+2007 (instead of the common space character U+0020). I just wanted to share the results, just in case. I still don't know what other spreadsheet tools do (or rather, how the result is rendered) with the "?" format code when using "proportional" fonts. This is important, so users won't complain about seeing different rendered results (or exported formats, such as in PDFs or HTMLs). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158787] Slowness of LibreOffice available on the Microsoft Store
https://bugs.documentfoundation.org/show_bug.cgi?id=158787 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158963] LibreWriter lags when spread across multiple screens.
https://bugs.documentfoundation.org/show_bug.cgi?id=158963 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113123] [META] PDF import filter in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=113123 Bug 113123 depends on bug 151788, which changed state. Bug 151788 Summary: Imported Arabic/Persian text from PDF should go through unshaping Algorithm https://bugs.documentfoundation.org/show_bug.cgi?id=151788 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 99746] [META] PDF import filter in Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=99746 Bug 99746 depends on bug 151788, which changed state. Bug 151788 Summary: Imported Arabic/Persian text from PDF should go through unshaping Algorithm https://bugs.documentfoundation.org/show_bug.cgi?id=151788 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 43808] [META] Right-To-Left and Complex Text Layout language issues (RTL/CTL)
https://bugs.documentfoundation.org/show_bug.cgi?id=43808 Bug 43808 depends on bug 151788, which changed state. Bug 151788 Summary: Imported Arabic/Persian text from PDF should go through unshaping Algorithm https://bugs.documentfoundation.org/show_bug.cgi?id=151788 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 151788] Imported Arabic/Persian text from PDF should go through unshaping Algorithm
https://bugs.documentfoundation.org/show_bug.cgi?id=151788 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 151788] Imported Arabic/Persian text from PDF should go through unshaping Algorithm
https://bugs.documentfoundation.org/show_bug.cgi?id=151788 --- Comment #5 from QA Administrators --- Dear Hossein, 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 156173] Footnotes were changed by LOW converted to Endnotes with Footnote formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=156173 --- Comment #2 from QA Administrators --- Dear Peter Donnelly, 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 155523] Color Palette Drop List Empty
https://bugs.documentfoundation.org/show_bug.cgi?id=155523 --- Comment #5 from QA Administrators --- Dear Ossama Nasser, 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 144087] Finder screen is "blocked" on Mac - Unable to see my desktop when LO in fullscreen mode
https://bugs.documentfoundation.org/show_bug.cgi?id=144087 --- Comment #7 from QA Administrators --- Dear David Aguirre, 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 88032] EDITING: Anomalies when copying field definition rows between tables in design view
https://bugs.documentfoundation.org/show_bug.cgi?id=88032 --- Comment #10 from QA Administrators --- Dear James B. Byrne, 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 104867] Impress does not compress repeated(copied) images with Minimize Presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=104867 --- Comment #9 from QA Administrators --- Dear Maxim Britov, 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 159009] New: UI: Calc text in first row disappears when right-clicking in cell then clicking on column header
https://bugs.documentfoundation.org/show_bug.cgi?id=159009 Bug ID: 159009 Summary: UI: Calc text in first row disappears when right-clicking in cell then clicking on column header Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: matt...@gmail.com Description: Calc text in first row disappears when right-clicking in cell then clicking on column header Steps to Reproduce: 1.Open Calc and type "foox" in cell A1 2.Double click inside cell A1 such that "foox" is completely highlighted, then right click on the word such that the spell check context menu pops up 3.Click on the Column Header for A Actual Results: Observe the word disappears visually from the cell, but it is still "there". Expected Results: Word should still be visible after right-click and column header click. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 97438] URLs are not escaped by Punycode and are susceptible to IDN attacks
https://bugs.documentfoundation.org/show_bug.cgi?id=97438 Matt K changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Bug 116643] Crash when playing PPTX slide with MP4 video (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=116643 Matt K changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #18 from Matt K --- I'm not able to reproduce a crash or freeze on Windows 11 with the following build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 205dd919179f34815d7e16c8dc73d2a7efd34535 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded The slide transitions are a little laggy, but I was able to view the full show. Is this a Linux only issue (marking NEEDINFO)? Also, it seems LO doesn't support mp4 video via Insert->Audio or Video... So, is this bug to prevent the crash by preventing an mp4 from playing, or is it to implement support for mp4? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 75057] [META] OOXML Chart object issues
https://bugs.documentfoundation.org/show_bug.cgi?id=75057 Aron Budea changed: What|Removed |Added Depends on||137691 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=137691 [Bug 137691] FILEOPEN: Data table is missing number formatting: shows "25" instead of "$250,000" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 137691] FILEOPEN: Data table is missing number formatting: shows "250000" instead of "$250,000"
https://bugs.documentfoundation.org/show_bug.cgi?id=137691 Aron Budea changed: What|Removed |Added Blocks||75057 Status|REOPENED|NEW Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=75057 [Bug 75057] [META] OOXML Chart object issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107830] [META] DOCX (OOXML) paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107830 Aron Budea changed: What|Removed |Added Depends on||158999 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158999 [Bug 158999] Incorrect rendering of empty paragraph with escapement set to superscript -- You are receiving this mail because: You are the assignee for the bug.
[Bug 132157] [META] BigPtrArray::Index2Block undo crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=132157 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||158740 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158740 [Bug 158740] Crash at undo -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158740] Crash at undo
https://bugs.documentfoundation.org/show_bug.cgi?id=158740 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEW Severity|normal |critical Crash report or||["BigPtrArray::Index2Block( crash signature||int) const"] Version|24.2.0.0 beta1+ |7.6.4.1 release Blocks||132157 Ever confirmed|0 |1 --- Comment #2 from Stéphane Guillou (stragu) --- It is inconsistent and took a few tries, but I have managed to reproduce in: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 960e37af28807ed1b376e26c4504ab755a81dfd5 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 24.2.0.0.beta1 (X86_64) / LibreOffice Community Build ID: 5f390384195b7264c6e52add9e90a39790285249 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded In 7.6, I get the "BigPtrArray::Index2Block(int) const" signature: https://crashreport.libreoffice.org/stats/crash_details/2eb5b579-5a80-45d0-b1a0-4b76469bdcbc Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=132157 [Bug 132157] [META] BigPtrArray::Index2Block undo crashes -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159007] Moving a grouped object to a different layer makes it disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=159007 Stéphane Guillou (stragu) changed: What|Removed |Added Regression By||Caolán McNamara -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159007] Moving a grouped object to a different layer makes it disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=159007 --- Comment #3 from Stéphane Guillou (stragu) --- (In reply to m_a_riosv from comment #2) > Sorry @Stéphane, how do you drag on the controls layer? See https://help.libreoffice.org/7.6/en-US/text/sdraw/guide/layer_move.html You need to click and hold (without moving) until the icon changes. Then you can drag to the layer tab. It's not the easiest feature to discover! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158732] deb packages don't use the maximum force for xz compression
https://bugs.documentfoundation.org/show_bug.cgi?id=158732 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO Whiteboard| QA:needsComment| --- Comment #1 from Stéphane Guillou (stragu) --- Thanks Jérôme. Do you know what difference it makes in the time needed to decompress such packages, and overall install times? Could you test that too? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 96886] Allow to change mouse pointer into a "laser pointer" during slide show
https://bugs.documentfoundation.org/show_bug.cgi?id=96886 Stéphane Guillou (stragu) changed: What|Removed |Added CC||mii...@protonmail.com --- Comment #12 from Stéphane Guillou (stragu) --- *** Bug 158756 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158756] Instead of click to change slide...
https://bugs.documentfoundation.org/show_bug.cgi?id=158756 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED Whiteboard| QA:needsComment| CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- If I understand well, you are after the same as the two-way laser tool requested in bug 96886. Marking as a duplicate. Thanks! *** This bug has been marked as a duplicate of bug 96886 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 62366] SLIDESHOW: Pen on the presenter console
https://bugs.documentfoundation.org/show_bug.cgi?id=62366 Stéphane Guillou (stragu) changed: What|Removed |Added Hardware|x86-64 (AMD64) |All CC||stephane.guillou@libreoffic ||e.org OS|Windows (All) |All Version|7.3.7.2 release |4.0.1.2 release --- Comment #18 from Stéphane Guillou (stragu) --- Also in: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 960e37af28807ed1b376e26c4504ab755a81dfd5 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded (@Aurélien: please keep the Version field at the earliest affected, and the Hardware/OS fields to the more general values if already set.) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155876] [LOCALHELP] - Calc - Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155876 --- Comment #58 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/4ff59004ff1d7506eebad27eed13c9d55419cacd tdf#155876 UI cmds Calc-Sheet menu (44) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155876] [LOCALHELP] - Calc - Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155876 --- Comment #59 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/ada03f41bc98b77aafbb36b45c9302993519eac2 tdf#155876 UI cmds Calc-Sheet menu (45) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108430] [META] Mouse cursor bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108430 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||132546 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=132546 [Bug 132546] Mouse pointer is visible in slide show, can't hide it despite "mouse pointer visible" being off -- You are receiving this mail because: You are the assignee for the bug.
[Bug 132546] Mouse pointer is visible in slide show, can't hide it despite "mouse pointer visible" being off
https://bugs.documentfoundation.org/show_bug.cgi?id=132546 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|LO Impress: Mouse pointer |Mouse pointer is visible in |is visible while slide |slide show, can't hide it |demonstration, can't hide |despite "mouse pointer |it |visible" being off Blocks||108430 CC||stephane.guillou@libreoffic ||e.org --- Comment #5 from Stéphane Guillou (stragu) --- Reproduced in recent trunk build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 960e37af28807ed1b376e26c4504ab755a81dfd5 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108430 [Bug 108430] [META] Mouse cursor bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155876] [LOCALHELP] - Calc - Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155876 --- Comment #57 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/73ef8f77eaad5dcd54d4422740b82e50c9e0ccd0 tdf#155876 UI cmds Calc-Sheet menu (43) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155876] [LOCALHELP] - Calc - Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155876 --- Comment #56 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/1f0087d58b480cf603dcb58fe0e83fadb8cc726d tdf#155876 UI cmds Calc-Sheet menu (42) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 108430] [META] Mouse cursor bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108430 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|142272 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142272 [Bug 142272] Mouse Pointer Not Disappearing -- You are receiving this mail because: You are the assignee for the bug.
[Bug 132546] LO Impress: Mouse pointer is visible while slide demonstration, can't hide it
https://bugs.documentfoundation.org/show_bug.cgi?id=132546 Stéphane Guillou (stragu) changed: What|Removed |Added CC||c319ch...@aol.com --- Comment #4 from Stéphane Guillou (stragu) --- *** Bug 142272 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103610] [META] Slide show (presentation mode) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103610 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|142272 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142272 [Bug 142272] Mouse Pointer Not Disappearing -- You are receiving this mail because: You are the assignee for the bug.
[Bug 142272] Mouse Pointer Not Disappearing
https://bugs.documentfoundation.org/show_bug.cgi?id=142272 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks|103610, 108430 | Status|NEW |RESOLVED Resolution|--- |DUPLICATE CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- Already tracked in bug 132546, marking as duplicate. *** This bug has been marked as a duplicate of bug 132546 *** Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103610 [Bug 103610] [META] Slide show (presentation mode) bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=108430 [Bug 108430] [META] Mouse cursor bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103030] [META] Navigator sidebar deck and floating window (also "Target in Document")
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||158763 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158763 [Bug 158763] Input focus does not move into Calc comment from the Navigator under GTK3 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101216] [META] Calc comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=101216 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||158763 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158763 [Bug 158763] Input focus does not move into Calc comment from the Navigator under GTK3 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158763] Input focus does not move into Calc comment from the Navigator under GTK3
https://bugs.documentfoundation.org/show_bug.cgi?id=158763 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEW Blocks||101216, 103030 Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Confirmed as in bug 158514 comment 9. Thanks! Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101216 [Bug 101216] [META] Calc comment bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=103030 [Bug 103030] [META] Navigator sidebar deck and floating window (also "Target in Document") -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158764] Icons rendered with black borders
https://bugs.documentfoundation.org/show_bug.cgi?id=158764 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Whiteboard| QA:needsComment| --- Comment #1 from Stéphane Guillou (stragu) --- Can't reproduce on Ubuntu with: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Nor with gen VCL plugin. Can the user share: - the full info from Help > About LibreOffice - which desktop environment and OS them are in use Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158790] unable to open ods files in Google Drive on Android devices due to MIME type
https://bugs.documentfoundation.org/show_bug.cgi?id=158790 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org URL||https://askubuntu.com/quest ||ions/1236632/cant-open-ods- ||file-i-created-and-saved-in ||-google-drive-no-applicatio ||n-for-a Keywords||needsDevAdvice --- Comment #1 from Stéphane Guillou (stragu) --- Thanks for the report. Can you please attach sample files? (One created with LO viewer, with the application/vnd.oasis.opendocument.spreadsheet mimetype, and the one with the extra "x-"? Just to clarify: 1. You create an ODS with LO Viewer, save it, the mimetype is correct 2. You open and save the same file with LO desktop (7.6.4.1): the mimetype gets the extra "x-" 3. Such file can't be opened in the mobile apps but can on desktop. Is that correct? Related: - https://askubuntu.com/questions/1236632/cant-open-ods-file-i-created-and-saved-in-google-drive-no-application-for-a - https://stackoverflow.com/questions/68488973/in-which-cases-the-mimetypes-of-google-docs-changes - https://phabricator.kde.org/D9706 Looks like it's Google Drive that modifies the mimetype of the file, assuming it's a non-standard mimetype even though it is listed by IANA: https://www.iana.org/assignments/media-types/media-types.xhtml See this documentation: https://developers.google.com/drive/api/guides/ref-export-formats Only ODS is affected; ODT and ODP don't get the extra "x-". In any case, LO Viewer should still open files with such a mimetype, so maybe something to also change on our end. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158992] "Spotlight" Should Only Number/Color Styles That Actually Appear in Document
https://bugs.documentfoundation.org/show_bug.cgi?id=158992 --- Comment #4 from Jim Raykowski --- Created attachment 191746 --> https://bugs.documentfoundation.org/attachment.cgi?id=191746&action=edit Demo of proposed enhancement Hi Tex2002ans, Does the attached demo track with your proposal? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158792] Crash when closing (sometimes)
https://bugs.documentfoundation.org/show_bug.cgi?id=158792 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Keywords||haveBacktrace --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report. Do you use the LanguageTool extension? There are other crashes on KDE with that extension, e.g. bug 154978 and other listed in its See Also. If you have extensions installed, you could test if the crash still happens in Safe Mode (Help > Restart in safe mode). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159008] Autorecovery files are hard deleted when you say no to saving the current open document and cannot be found even with data recovery software
https://bugs.documentfoundation.org/show_bug.cgi?id=159008 Jeff changed: What|Removed |Added Summary|Autorecovery files are hard |Autorecovery files are hard |deleted when you say no to |deleted when you say no to |saving the current open |saving the current open |document|document and cannot be ||found even with data ||recovery software -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159008] New: Autorecovery files are hard deleted when you say no to saving the current open document
https://bugs.documentfoundation.org/show_bug.cgi?id=159008 Bug ID: 159008 Summary: Autorecovery files are hard deleted when you say no to saving the current open document Product: LibreOffice Version: 7.5.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jcol...@gmail.com Description: When you close a libreoffice calc document and click "do not save changes", libreoffice calc does a hard delete of some sort on the autorecovery files in the Backups path of Libreoffice. The files are no longer recoverable using data recycle bin or even data recovery software as they should be if the files were just normally deleted. It's like they never existed. This is a problem if you make a mistake and click no in the save dialog box. Using windows 11. Steps to Reproduce: 1.open file in libreoffice calc for example 2.Make change to a cell 3.Wait for auto backup to occur and confirm file in backups folder 4.Close libreoffice calc and do not save changes. 5.check backups folder autobackup file is gone. 6.try recycle bin or data recovery software and the files will not show up. Actual Results: backup autorecovery files are all gone Expected Results: Be able to recover the files with data recovery software Two possible solutions: 1)different method to delete the files in the backup folder when you close without saving so that there is some way to recover the backups 2)Change libreoffice to keep backup files for x days and clean up old ones on startup. On a normal close of a libreoffice file where someone cooses to not save the document, rename the autorecovery files so they don't impact the next time libreoffice wants to create them when the file is opened. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-CA (en_CA); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107243] [META] Locale keyboard shortcut issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107243 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||158767 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158767 [Bug 158767] [German-UI] Shortcut Cmd+O opens Template Manager and not File Open menu (macOS) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 98290] [META] Better shortcuts on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=98290 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||158767 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158767 [Bug 158767] [German-UI] Shortcut Cmd+O opens Template Manager and not File Open menu (macOS) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158767] [German-UI] Shortcut Cmd+O opens Template Manager and not File Open menu (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=158767 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEW Whiteboard| QA:needsComment| Blocks||98290, 107243 Summary|[German-UI] Shortcut Cmd+O |[German-UI] Shortcut Cmd+O |opens Template Manager and |opens Template Manager and |not File Open menu |not File Open menu (macOS) Component|Draw|LibreOffice --- Comment #3 from Stéphane Guillou (stragu) --- Thanks Dennis. Reproduced with: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 2; OS: Mac OS X 13.2.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: de-DE Calc: threaded Not specific to when closing Draw: I can also open the Start Center, close it and then Cmd + O. Same result. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98290 [Bug 98290] [META] Better shortcuts on macOS https://bugs.documentfoundation.org/show_bug.cgi?id=107243 [Bug 107243] [META] Locale keyboard shortcut issues -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158991] Text in rotated shape is cut when Skia is disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=158991 raal changed: What|Removed |Added CC||kha...@libreoffice.org, ||r...@post.cz Keywords|bibisectRequest |bibisected, bisected Regression By||Khaled Hosny --- Comment #5 from raal --- This seems to have begun at the below commit in bibisect repository/OS win-24.2. Adding Cc: to Khaled Hosny ; Could you possibly take a look at this one? Thanks e41627b044a142281048a640cb7e2c2c1405b755 is the first bad commit commit e41627b044a142281048a640cb7e2c2c1405b755 Author: Norbert Thiebaud Date: Sat Jul 22 21:37:12 2023 -0700 source sha:dfe42e756b37642355356a6035081f4473609832 154388: vcl: Use HarfBuzz to get glyph bounding rectangle | https://gerrit.libreoffice.org/c/core/+/154388 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155876] [LOCALHELP] - Calc - Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155876 --- Comment #55 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/461a95979023ee810210b0b69d8497ba8f585dfd tdf#155876 UI cmds Calc-Sheet menu (41) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 117085] [META] Compress image dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=117085 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||158780 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158780 [Bug 158780] Image compression dialog should grey out Resolution fields if "Reduce image resolution" is not ticked (comment 7) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158780] Image compression dialog should grey out Resolution fields if "Reduce image resolution" is not ticked (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=158780 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|Image compression in|Image compression dialog |IMPRESS is no longer|should grey out Resolution |functional (FORMATTING |fields if "Reduce image |bug). |resolution" is not ticked ||(comment 7) Blocks||117085 Hardware|ARM |All Status|NEEDINFO|NEW See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6929 OS|macOS (All) |All Component|Impress |UI Keywords||bibisected, bisected, ||implementationError CC||heiko.tietze@documentfounda ||tion.org Version|7.4.0.3 release |7.4.0.0 alpha0+ --- Comment #7 from Stéphane Guillou (stragu) --- (In reply to Patrick from comment #6) > Of course, it would have been better if all the respective selection > switches were grey out to make me as a user aware that this functionality is > deactivated. In fact, when I check the box, and then uncheck it again, it > appears greyed out. But unfortunately, not initially ... I agree with you that the UI should be better here. I can reproduce also on Linux that the Resolution fields are not greyed out when the dialog is opened and the box is not ticked. Reproduced in: Version: 7.4.7.2 / LibreOffice Community Build ID: 723314e595e8007d3cf785c16538505a1c878ca5 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e71934471442a8bbba7e661d3ebe5f708627c5d6 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Same with gen VCL plugin. In 7.3, the box was ticked by default. The issue started with Heiko's 90546b02d70cb9a9c3ee88428d99635a2f7eb22a for bug 146929 (build commit [f1aae7b6f6d5d2667bf8841b912456cfce5925e6] in the linux-64-7.4 bibisect repo). Let's refocus this report. Heiko, can you please have a look? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=117085 [Bug 117085] [META] Compress image dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159007] Moving a grouped object to a different layer makes it disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=159007 --- Comment #2 from m_a_riosv --- Sorry @Stéphane, how do you drag on the controls layer? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159007] Moving a grouped object to a different layer makes it disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=159007 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- I'm not able to make it disappear. I can drag out of the page, but the circle remains. And visible in the navigator. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e0f710ad29d33acda3c1b77d7a0980ca9ae2e3d1 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 158712] Crash with bookmarks menu extension
https://bugs.documentfoundation.org/show_bug.cgi?id=158712 Stéphane Guillou (stragu) changed: What|Removed |Added Crash report or||["typelib_typedescriptionre crash signature||ference_release","libc.so.6 ||","accessibility::Accessibl ||eGridControlTable::getAcces ||sibleChild(long)","libc-2.3 ||1.so"] Keywords||bibisectRequest, regression Version|7.6.4.1 release |5.0.0.5 release --- Comment #3 from Stéphane Guillou (stragu) --- Thanks for the link. Already in 5.0.0.5, with steps in comment 1, it crashes with the message: type coercion failed: TYPE is not supported! However, it does not crash in 4.0.0.3. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158997] Calc Format>Columns>Optimal Width [OK] causes some columns to be too narrow
https://bugs.documentfoundation.org/show_bug.cgi?id=158997 --- Comment #9 from m_a_riosv --- It happens only with optimal with 0,00 with 0,01 works fine. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158997] Calc Format>Columns>Optimal Width [OK] causes some columns to be too narrow
https://bugs.documentfoundation.org/show_bug.cgi?id=158997 m_a_riosv changed: What|Removed |Added Keywords||bibisectRequest, regression --- Comment #8 from m_a_riosv --- First version where I can reproduce the issue. Version: 6.4.7.2 (x64) Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: GL; VCL: win; Locale: es-ES (es_ES); UI-Language: en-US Calc: CL Last working for me: Version: 6.0.7.2 (x64) Build ID: 78c12ce5f2b8960f18b204a7ea82f971769f1679 CPU threads: 16; OS: Windows 10.0; UI render: GL; Locale: es-ES (es_ES); Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Bug 99648] [META] Improve Layer Handling
https://bugs.documentfoundation.org/show_bug.cgi?id=99648 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||159007 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159007 [Bug 159007] Moving a grouped object to a different layer makes it disappear -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159007] New: Moving a grouped object to a different layer makes it disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=159007 Bug ID: 159007 Summary: Moving a grouped object to a different layer makes it disappear Product: LibreOffice Version: 24.2.0.0 alpha0+ Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Keywords: bibisected, bisected, regression Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org CC: caolan.mcnam...@collabora.com Blocks: 99648 Created attachment 191745 --> https://bugs.documentfoundation.org/attachment.cgi?id=191745&action=edit sample ODG Steps: 1. Open attachment 2. Double-click on circle "2" to enter group 3. Long-click and drag-and-drop circle "2" onto the Controls layer to move it to that layer Result: object disappears (but can be seen when drag-and-dropped) Repro in recent trunk build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 960e37af28807ed1b376e26c4504ab755a81dfd5 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Also with gen VCL plugin. Bibisected with linux-64-24.2 to first bad build commit [97a48f557a3a2079bbdd45065fa0f3b1028b816d] which points to: commit 313be607903a381830600c0a60b2e299fcaec685 author Caolán McNamara Wed Aug 02 17:16:17 2023 +0100 committer Caolán McNamara Thu Aug 03 12:15:58 2023 +0200 Related: cool#6911 opt to skip SdrObject::GetViewContent() when possible Reviewed-on: https://gerrit.libreoffice.org/c/core/+/155269 Caolán, can you please have a look? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=99648 [Bug 99648] [META] Improve Layer Handling -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158506] LibreOffice Writer: Special Characters (in color) that are inserted above text titles, previously printed in color, but now print only in black.
https://bugs.documentfoundation.org/show_bug.cgi?id=158506 --- Comment #2 from Timur --- This is reproducible. But I do not think it was ever printed in color. Emojis and symbols were not printed at all, now they are black. This may be bug 105488. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159000] WRITER: Insert Special Characters menu window only shows a part of available characters in certain fonts (But accessible through Unicode)
https://bugs.documentfoundation.org/show_bug.cgi?id=159000 --- Comment #5 from Kati L. --- Created attachment 191744 --> https://bugs.documentfoundation.org/attachment.cgi?id=191744&action=edit Screenshot showing a section of the special characters that are shown Some of the special characters do appear within the menu window, and did already at the point when the forced substituting to another font was still in effect. Most of the characters I need are actually here (including the Latin Small Letter A with a breve, which was the biggest issue for a long while), but I would still be happier if the full range of the available combining diacritics were available. As another point, the same combinations found here as pre-formed combined characters do also work in the intended way as separate Unicode typing applications, for instance in the case of the double acute accent over small Latin o. I've tested the both methods (inserting from the menu window and inserting as typed Unicode[alt+x]), and they work. The separate combining diacritic and the letter aren't replaced by the pre-formed combination character here, at least presumedly, since they can be turned back and forth to Unicode and characters through the same [alt+x] combo key? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159006] New: Font size change during Japanese input
https://bugs.documentfoundation.org/show_bug.cgi?id=159006 Bug ID: 159006 Summary: Font size change during Japanese input Product: LibreOffice Version: 7.4.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: koutei-r@posteo.de Description: Whenever you use different font sizes in one line and enter Japanese characters, the size of the input preview is different from the size you actually selected. Steps to reproduce: 1. Select 48 pt as your font size, enter any Japanese character, preferably a kanji. 2. Enter a space character and another Japanese character, select the latter and change its font size to 24 pt. 3. Try to enter another Japanese character after it. Expected behaviour: When entering Japanese characters, the preview when selecting your kanji/kana spelling as well as the output should be at 24 pt. Actual behaviour: The input preview switches back to 48 pt, the output will be at 24 pt. Reproducibility: Always. In some documents that were created before the 7.4 update, the size of the preview changes in a different way (not necessarily the size of the first character in each line). Either way it’s never the selected size, occasionally happens in new lines as well. User profile reset: No difference, tested it on a factory-fresh system as well. OS: Windows 10/11; Linux Mint 21 64-bit Last stable version: 7.3.7.2 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158997] Calc Format>Columns>Optimal Width [OK] causes some columns to be too narrow
https://bugs.documentfoundation.org/show_bug.cgi?id=158997 m_a_riosv changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #7 from m_a_riosv --- (In reply to David Lynch from comment #6) > . > Format>Columns>Optimal Width > *** Change 0.20 cm to 0.00 cm [OK] *** > Two cells, B2, F2 not wide enough: show "#"'s. This case I can reproduce Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 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 158877] Non-corrective Autoformat settings can't just be placed under AutoCorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=158877 Eyal Rozenberg changed: What|Removed |Added Blocks||158876 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158876 [Bug 158876] Autocorrect options are very confusing and difficult to use -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158876] Autocorrect options are very confusing and difficult to use
https://bugs.documentfoundation.org/show_bug.cgi?id=158876 Eyal Rozenberg changed: What|Removed |Added Depends on||158877 --- Comment #2 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #1) > Duplicate of bug 158877, or vice versa. At least partially. Let's say this one depends on that one. i.e. if 158877 was resolved somehow, that would reduce the severity of the general problem I complain about here. > While some options might be not easy to understand I think the alternative > is worse. But there isn't such as thing as _the_ alternative. There's a design space of the UI for these different options, plus the text labels of labels in each point of that design space. A specific example: If we separated content-changing options, and displayed them so as to indicate and differentiate what gets replaced and with what - that will certainly be an improvement, almost regardless of what phrasing we choose. > The alternative could be some illustration with the drawback that you scroll > through a huge dialog. Illustrations are one option of several. And even if we consider illustrations/examples - those could be per-setting collapsible (and collapsed by default); or visible only in a tooltip. > In the end I see no immediate issue with the dialog. Do you have support for > your view? Like most bugs I file, not at this time, but I'm sure there would be. I'll try to get some sock puppets, but even without them, you're dismissing this too quickly... Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158877 [Bug 158877] Non-corrective Autoformat settings can't just be placed under AutoCorrect -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159000] WRITER: Insert Special Characters menu window only shows a part of available characters in certain fonts (But accessible through Unicode)
https://bugs.documentfoundation.org/show_bug.cgi?id=159000 --- Comment #4 from Kati L. --- Created attachment 191743 --> https://bugs.documentfoundation.org/attachment.cgi?id=191743&action=edit The window showing the missing combining diacritics' place The full range of diacritics appear here, but they all are of the non-combining kind that stands alone, separately -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159000] WRITER: Insert Special Characters menu window only shows a part of available characters in certain fonts (But accessible through Unicode)
https://bugs.documentfoundation.org/show_bug.cgi?id=159000 --- Comment #3 from Kati L. --- (In reply to Mike Kaganski from comment #1) > (In reply to Kati L. from comment #0) > > Example: the double acute accent found in the menu is [U+02dd]. The correct, > > combining acute accent ought to be [U+030b]. The actual combining diacritics > > can't be found anywhere in the available selection in the Insert Special > > Characters menu window - but, when typing them in the text in their Unicode > > form followed by the combination key [alt+x], does bring out the correct > > combined characters (the vowel with the diacritic correctly above it) - in > > the used font, as a cherry on top. Therefore, they have to exist in the data > > of the font files, so who don't they show in the menu window? > > This is misconception. Your text has the font set to your choice. The > controls display it. But specific glyphs that you request might come from a > different - substitution - font. It appears that I wasn't still being meticulous enough, even if I thought that I'd been way too nitpicky. I'm aware of this fact. I just forgot to mention that, too, in my list of several other options. I attached a screencapture to demonstrate that certain combinations indeed do exist within the font, whereas other characters are substituted with the equivalents from another font. I believe I already described this feature here: " [This actually used to be an issue in the older versions of LO Writer (the one I had in use, about three years ago), as well as the reverted character appearing in the default application font, instead of the document default font or the selected font inside that text block. (As an anecdote, some of these strange reversions still appear in certain older drafts of my texts, retained in the PDF conversions made for the sake of easier proofreading, as a funny throwback.)]" The forced reversion / substitution no longer is an issue where the said characters actually exist within the font. Even in these cases (in the older versions of this software), they did, and the problem seemed to arise from having converted a document to .odt from .doc, or opening a document originally written in MSWord in LOWrite and saving it as .odt. Somehow, it didn't recognize the characters, even if the font remained the same in both formats and original softwares where the documents were written. But, like said, this no longer is an issue as long as the characters actually do exist in the used font. So, in the case of my complaints, the fonts do appear in the intended font, once I use the Unicode entering technique. They don't seem (falsely) to exist, within the entire set of characters in the Insert Special Character menu window. Will attach another screenshot of the said window. Sorry it doesn't appear as a picture in this thread, I reached the extent of my data skills at this time of the night, but was so frustrated by the misconception of my assumed misconception that I decided to return here and clarify the matter. Sorry. I'm an incurable geek, and I get needlessly annoyed when something that should be relatively effortless suddenly requires extensive work just in order to type in a single character. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 94989] ENHANCEMENT: Select all text with the same formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=94989 --- Comment #20 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #19) > (In reply to Tex2002ans from comment #18) > > - Right-Click on colored box > "Select All Same Style". > Well, the point of styles is to apply everywhere. No need to select :-). Not sure whether you meant this as a joke, but - you do need to select if you want to do something with that content (other than make changes to the named style). You can: * Delete all of it * Remove DF in it. * Switch it to another style * Apply some DF to it * Cut or copy it * Make it into a bulleted or numbered list * Word-count it * Just get an impression of where it's used as you scroll through the text, especially when you zoom out and if what you've selected is not a named style but some style+DF - then also * Define a new named style based on it > > - "Surgical Editing" > How about some piece of text where italic is used for Emphasis and another > for Caption. I think the F&R way is more surgical than some probability > method. 1. (Perhaps Tex2000Ans mis-spoke, but) this bug is not about being surgical, it's about selecting _everything_ and then looking at what you've selected or doing things with the selection or parts of it. 2. F&R is not a (surgical) editing tool. You can switch out of the dialog, do an edit, then continue, but that's not convenient and it's difficult to intuit what the dialog will do when you get back into it and click next. 3. F&R for is effectively inaccessible like I've already argued. > MSO might look smart in some cases but fails in complex scenarios. 1. Please elaborate. 2. It is useful in many common scenarios, like the ones > How about forwarding this topic for an extension? Maybe the author of > AltSearch is interested. "Make it an extension" is the little brother of "let's describe things better in documentation"... :-( No, we want this in vanilla LibreOffice. I will concede, however, that in MSO, we use this feature just to inspect which content has the style, while in LO we have the style spotlight, which offers this functionality to a certain degree, for named styles. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 114441] Convert use of sal_uLong to better integer types
https://bugs.documentfoundation.org/show_bug.cgi?id=114441 --- Comment #78 from Commit Notification --- gilssonn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/1cca19ad9701f4104ba6764802712387c29f28e3 tdf#114441 Convert use of sal_uLong to better integer types It will be available in 24.8.0. 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 159000] WRITER: Insert Special Characters menu window only shows a part of available characters in certain fonts (But accessible through Unicode)
https://bugs.documentfoundation.org/show_bug.cgi?id=159000 --- Comment #2 from Kati L. --- Created attachment 191742 --> https://bugs.documentfoundation.org/attachment.cgi?id=191742&action=edit Screenshot of some example characters Here's an example of the characters that are found, or aren't found in the font. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 86483] FEATURE REQUEST: Implement different default templates per locale
https://bugs.documentfoundation.org/show_bug.cgi?id=86483 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard|target:7.5.0 target:24.2.0 |target:7.5.0 target:24.2.0 ||inReleaseNotes:24.2 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146466] Inconsistent choices of borders between toolbar and sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=146466 Stéphane Guillou (stragu) changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Severity|normal |enhancement OS|Linux (All) |All Keywords||needsUXEval Hardware|x86-64 (AMD64) |All --- Comment #6 from Stéphane Guillou (stragu) --- Situation hasn't changed in: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 960e37af28807ed1b376e26c4504ab755a81dfd5 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Marking as an enhacenemt rather than a bug though. UX/Design team, what do you think about unifying the two widgets, for simplification and consistency? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158890] FORMATTING: Custom number format trailing 0 replaced with figure space
https://bugs.documentfoundation.org/show_bug.cgi?id=158890 --- Comment #6 from misc.li...@heplist.com --- (In reply to ady from comment #5) > (In reply to Eike Rathke from comment #4) > > > There's nothing to preserve. It's a display time rendering thing for a > > format code and either gets changed or not. > > If it gets changed, what would happen when the specific font in use doesn't > include the U+2007 FIGURE SPACE character? Fallback to the normal space > character? > > I fear the negative consequences, as expressed in comment 3, including the > possible difference in rendering. As far as I can tell, Calc will fallback to a font in the OS that does include the character. For example, if your cell is in FontX but that font does not include character Y, then Calc renders everything but character Y in FontX but grabs that one missing character from FontZ that does have it. As much as I have been trying to break Calc's rendering off-and-on in the last few days (even trying to test it with [almost] all of the original fonts released with Win 3.1), it appears to be surprisingly robust. No ugly box characters (etc.) so far for any unavailable obscure characters that I have tested. The characters from other fonts Calc falls back on seem to be very similar in size to the requested font, too. It looks like almost everyone will have a font to fall back on to grab 0x2007 (figure space) from. The FileFormat . Info website lists several fonts that support 0x2007. Among those fonts listed are Arial, Arial Unicode, Calibri, Cambria, Consolus, DejaVu, Doulos, Gentium, Liberation Sans, Linux Libertine, Lucida Sans, Palatino Linotype, Roboto, Segoe UI, Source Code, Source Sans, Tahoma, and Times New Roman. I think that pretty much covers Linux, Windows, and Mac. I think some of these fonts are also installed when LibreOffice is installed (Gentium, DejaVu, and few others). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159005] FILESAVE PPTX: Open-Save-Reload changes colors of slide elements
https://bugs.documentfoundation.org/show_bug.cgi?id=159005 --- Comment #4 from Alex Heuer --- Created attachment 191741 --> https://bugs.documentfoundation.org/attachment.cgi?id=191741&action=edit Screenshot of test.pptx after opening, saving, closing, and reopening the file -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159005] FILESAVE PPTX: Open-Save-Reload changes colors of slide elements
https://bugs.documentfoundation.org/show_bug.cgi?id=159005 --- Comment #3 from Alex Heuer --- Created attachment 191740 --> https://bugs.documentfoundation.org/attachment.cgi?id=191740&action=edit Screenshot of test file before saving and reopening The column in 2031 already differs from the original screenshot as there are values printed inside the column -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159005] FILESAVE PPTX: Open-Save-Reload changes colors of slide elements
https://bugs.documentfoundation.org/show_bug.cgi?id=159005 --- Comment #2 from Alex Heuer --- Created attachment 191739 --> https://bugs.documentfoundation.org/attachment.cgi?id=191739&action=edit Original slide how it looks when opened with MS PowerPoint 365 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155957] Recent and Favourite Special Characters lists' preview doesn't match what is inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=155957 --- Comment #11 from Stéphane Guillou (stragu) --- Created attachment 191738 --> https://bugs.documentfoundation.org/attachment.cgi?id=191738&action=edit results of comment 8 steps, with unicode-compliant fonts (In reply to V Stuart Foote from comment #9) > That is actually expected. > > Unfortunately decimal 61473 or hex U+F021 is a glyph from the fonts Private > Use Area -- no *reliable* font fall back can occur. In Wingding it is a left > downward pencil, in Webdings it is a spider, in Symbol it is an exclamation > mark. > > Dingbat glyphs from Winding or Webdings have mostly been mapped out to > Unicode. [1] so should not be needed or used in preparing documents. And that's also the point I make in comment 6. I only used the dingbat example to make the issue easier to see, but we could also show the problem with a pair of unicode-compliant fonts, for example using Benjamin first and then trying to insert that same recent character in a Liberation Serif paragraph, using the same steps as in comment 8. (See result in attached screenshot) A user might like to use such a stylised "A" as a symbol for whatever reason, and using the dialog makes it look like that's indeed what will be inserted. But you end up with the Liberation Serif "A" instead. I just noticed something that adds to the inconsistency: the toolbar dropdown differs in behaviour when compared to the dialog. At step 3, try instead to use the Recent list in the toolbar dropdown. You'll see that the Benjamin "A" is indeed inserted. So to me, there are clearly two issues to solve: A) Using the dialog, the Recent/Favourite lists and the large Preview show a glyph that doesn't match what will be insterted B) Using the toolbar dropdown Recent/Favourite lists has a different result to using the dialog's Recent/Favourite lists. (tested using 7.6.4) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159005] FILESAVE PPTX: Open-Save-Reload changes colors of slide elements
https://bugs.documentfoundation.org/show_bug.cgi?id=159005 --- Comment #1 from Alex Heuer --- Created attachment 191737 --> https://bugs.documentfoundation.org/attachment.cgi?id=191737&action=edit Test file to reproduce issue -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159005] New: FILESAVE PPTX: Open-Save-Reload changes colors of slide elements
https://bugs.documentfoundation.org/show_bug.cgi?id=159005 Bug ID: 159005 Summary: FILESAVE PPTX: Open-Save-Reload changes colors of slide elements Product: LibreOffice Version: 7.6.4.1 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: evilph...@phishtank.de Description: Similar to this bug: https://bugs.documentfoundation.org/show_bug.cgi?id=157783 opening a pptx file and then saving it without modifying anything breaks colors of some elements and garbles embedded graph. The problem only occurs with the embedded graph present. The embedded graph was inserted via Excel and might have its own color scheme. A hypothesis of mine is that during loading somehow the two color schemes get mixed up. Steps to Reproduce: 1.Open attached file 2.Save attached file 3.Open attached file again Actual Results: Re-opened file has color changes and the embedded graph is garbled Expected Results: No change at all as nothing is modified, the file is just re-saved Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 24; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: de-DE (en_US.UTF-8); UI: en-US Ubuntu package version: 4:7.6.4-0ubuntu0.22.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155957] Recent and Favourite Special Characters lists' preview doesn't match what is inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=155957 --- Comment #10 from V Stuart Foote --- (In reply to V Stuart Foote from comment #9) > =-ref-= > [1] https://unicode.org/L2/L2011/11052r-wingding.pdf sorry here is the better ref, wef Unicode 7.0: https://www.unicode.org/L2/L2012/12368-n4384.pdf -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159004] New: Bug reporting address for KDE Crash Handler
https://bugs.documentfoundation.org/show_bug.cgi?id=159004 Bug ID: 159004 Summary: Bug reporting address for KDE Crash Handler Product: LibreOffice Version: 7.6.2.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ddascalescu+freedesk...@gmail.com Created attachment 191736 --> https://bugs.documentfoundation.org/attachment.cgi?id=191736&action=edit screenshot LO crashes every time I close Calc, but there's no bug reporting address to report the crash. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159003] Macro: non-functional positioning X,Y of Dialog window if parent document is minimized
https://bugs.documentfoundation.org/show_bug.cgi?id=159003 Kamil Landa changed: What|Removed |Added Summary|Non-functional positioning |Macro: non-functional |X,Y of Dialog window if |positioning X,Y of Dialog |parent document is |window if parent document |minimized |is minimized -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159003] New: Non-functional positioning X, Y of Dialog window if parent document is minimized
https://bugs.documentfoundation.org/show_bug.cgi?id=159003 Bug ID: 159003 Summary: Non-functional positioning X,Y of Dialog window if parent document is minimized Product: LibreOffice Version: 24.8.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kam...@post.cz Created attachment 191735 --> https://bugs.documentfoundation.org/attachment.cgi?id=191735&action=edit document with macro and Dialog Click the button or run the macro Module1>ShowDlg in attached document. The window with document will be minimized and Dialog will be shown at top-left corner of screen instead at coordinates X,Y in method .setPosSize() According to https://ask.libreoffice.org/t/positionx-positiony-no-longer-working-for-dialog-position-on-screen/100029 It seems it is regression on Windows (7.4.7.2 seems OK), under Linux it is probably functional. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e0f710ad29d33acda3c1b77d7a0980ca9ae2e3d1 CPU threads: 8; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: cs-CZ Calc: CL threaded Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 8; OS: Windows 10.0 Build 17763; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: cs-CZ Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155957] Recent and Favourite Special Characters lists' preview doesn't match what is inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=155957 V Stuart Foote changed: What|Removed |Added CC||kha...@libreoffice.org --- Comment #9 from V Stuart Foote --- (In reply to Stéphane Guillou (stragu) from comment #8) > > My steps with a dingbat font, to make the issue more obvious: > 1. Insert with special character dialog the Wingdings pencil character > (decimal: 61473). > 2. Go to new paragraph, make sure it uses Liberation Serif (for example by > applying the Default Paragraph Style) > 3. Open Special Character dialog, see that the Recent Characters shows the > pencil character. Click on it: the preview also shows the pencil. Click > Insert. > > Result: some point glyph is inserted instead (decimal: 1). The character > shown in the dialog (recent/favourite lists, preview) does not match what is > inserted. That is actually expected. Unfortunately decimal 61473 or hex U+F021 is a glyph from the fonts Private Use Area -- no *reliable* font fall back can occur. In Wingding it is a left downward pencil, in Webdings it is a spider, in Symbol it is an exclamation mark. Dingbat glyphs from Winding or Webdings have mostly been mapped out to Unicode. [1] so should not be needed or used in preparing documents. For example The Wingding 61473/F021 lower left pencil is Unicode U+1F589 LOWER LEFT PENCIL; and covered in "Symbola" or "Segoe UI Symbol" as examples. =-ref-= [1] https://unicode.org/L2/L2011/11052r-wingding.pdf -- You are receiving this mail because: You are the assignee for the bug.
[Bug 137691] FILEOPEN: Data table is missing number formatting: shows "250000" instead of "$250,000"
https://bugs.documentfoundation.org/show_bug.cgi?id=137691 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=82 ||218 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158890] FORMATTING: Custom number format trailing 0 replaced with figure space
https://bugs.documentfoundation.org/show_bug.cgi?id=158890 --- Comment #5 from ady --- (In reply to Eike Rathke from comment #4) > There's nothing to preserve. It's a display time rendering thing for a > format code and either gets changed or not. If it gets changed, what would happen when the specific font in use doesn't include the U+2007 FIGURE SPACE character? Fallback to the normal space character? I fear the negative consequences, as expressed in comment 3, including the possible difference in rendering. -- You are receiving this mail because: You are the assignee for the bug.
